Can't Enable Process Model
The following errors can occur when attempting to enable a process model:
We often see the following error, when trying to enable a process model:
2006-01-12 00:14:47 CET [MON.0119.1501D] Error checking portal privilege:
java.lang.NullPointerException
at electric.util.license.License.isInternalLicense(Unknown Source) at electric.registry.Registry.getReference(Unknown Source)
at electric.registry.Registry.getProxy(Unknown Source)
This error is caused by having older glue or fabric (now servicenet) jar files still defined in the system classpath. The Integration Server About page - Server classpath provides details about the additional jars being included in the system classpath. Cleaning the system classpath and rebooting the machine generally resolves this error.
See also Process Engine Troubleshooting - Cannot Enable Model. of
How can I delete process instances with a status of "Started":
If you want to delete process instances with a status of "Started", first you need to stop them:
Stopping a Process Instance
You stop a process from the Monitoring > Business > Process Instances > Process Instance Detail page.
1. Display detailed information for the process instance that you want to stop.
2. On the Process Instance Information tab on the Process Instance Detail page, click Stop.
After the instance is stopped, in order to clean up those instances, as described in "webMethods Monitor User's Guide" you have three options: Archiving or Deleting Logged Data from My webMethods Archiving or Deleting Logged Data using Built-in Services Archiving or Deleting Logged Data using Stored
Procedures
In particular, you can use the following Built-in service:
pub.monitor.archive:processArchive
Archives or deletes process data and control data (such as resubmit actions) from the WMCONTROL, WMCUSTOMFIELDDEFINITION, WMCUSTOMPROCESSDATA, WMPROCESS, WMPROCESSASSOC, WMPROCESSDEFINITION, WMPROCESSIMAGE, WMPROCESSRECENT, WMPROCESSSTEP,
WMSTEPDEFINITION, and WMSTEPTRANSITIONDEFINITION tables in the Process Audit Log database component, and archives or deletes process related service data from the WMSERVICEACTIVITYLOG, WMSERVICE, and WMERROR tables in the IS Core Audit Log database component.
Specifically, the service archives or deletes the following:
• Process log entries, input pipelines, error data, and runtime values for user specified input and output document fields.
• Referenced processes, process related service data (services, service error data, and user defined messages).
• Process control data (resubmit, suspend, and resume actions).
Service
Integration Monitoring cannot display the Audit services.
First make sure there are no errors displayed when you click on Integration Monitoring. Any exceptions/errors could be a result of improper configuration.
If there are no errors, and the services being audited are still not shown in Integration Monitoring services, then there could be a different issue.
Make sure the WMSERVICE table is populated with records when you execute an Integration Server service that is auditing enabled.
When you perform archive or delete operations on the Integration Server core audit data, Integration Server calls a database stored procedure and connects to the Integration Server database by using the connection configured in IS JDBC pool. The stored procedure will copy (or delete) the core audit data.
Integration Server will then connect to the archiving database by using the connection configured in JDBC pool (Archiving functional alias) and insert the data to the archiving database/schema (if you choose to archive data).
Since the Process and Archiving database schemas are different entities, you need to configure separate JDBC pool aliases to point to the different database schemas.
If you are using the same JDBC pool for both Integration Server and Archiving, the stored procedure will actually disable the database triggers described in the following paragraphs.
Depending on whether you are archiving IS Core Audit or Process Audit, the stored procedure will disable the triggers accordingly.
For Service Archive, the stored procedure disables the trigger, WMSERVICE_RAIU (WMSERVICE table)
This trigger will actually copy the Service data from the WMSERVICE table to another related service data table called WMSERVICEASSOC which is used by MWS to display the audited services. Thus when this trigger is disabled, service data is not copied to the related table, and this could be one reason that you are unable to view the services under Integration Monitoring.
For Process Archive, the stored procedure disables the following three triggers:
WMPRCSSSSC_RAIU (WMPROCESSASSOC table) WMPRCSS_RAIU (WMPROCESS table)
WMSERVICE_RAIU (WMSERVICE table)
The three triggers will actually copy process data to another related process data which are used to view process instances in MWS when a new process instance is created. Thus when the triggers are disabled, process data cannot be copied to other related process tables and this is why you are unable to view process instances in MWS.
A workaround to view new process instances in MWS is to re-enable the following triggers in the IS database:
WMPRCSSSSC_RAIU (WMPROCESSASSOC table) - (For Process Instances monitoring issue) WMPRCSS_RAIU (WMPROCESS table) - (For Process Instances monitoring issue)
WMSERVICE_RAIU (WMSERVICE table) - (For both Process Instances and Services monitoring issue)
Executing Monitor built-in service throws a ClassCastException
Running this service WmMonitor/pub.monitor.process.model:getModelList in 8.0.1 throws the following exception:
$errorInfo $errorDump com.wm.monitor.util.MonitorException:
Could not retrieve model list: java.lang.ClassCastException: java.lang.Long cannot be cast to java.sql.Timestamp at
com.wm.monitor.app.Model.getModelList(Model.java:746) at pub.monitor.process.model.getModelList
This is a known issue in Monitor 8.0. Please apply MON_8.0_SP1_Fix1 (or latest) to resolve this issue.
Can't Resubmit a Service
The following problems might occur when resubmitting a service:
When resubmitting several failed instances with MWS the limit of the max connections parameter in the JDBC Pool alias defined for the processAudit is a constraint. If n is the maximum number of connections, it seems that it is possible to resubmit n-2 process instances. Resubmitting more than this can consume the JDBC connections.
If you try to resubmit only one instance more you get the following error:
2008-03-25 18:10:39 CET [ISC.0088.0001E] SOAPException: [ISS.0088.9134] Exception occurred while processing the body of the message
2008-03-25 18:10:42 CET [MON.0119.0042E] Failed in trying to resubmit all: java.sql.SQLException: no connection returned from pool [ProcessAudit]
2008-03-25 18:10:42 CET [MOD.0120.0000D] java.sql.SQLException: no connection returned from pool [ProcessAudit]
MON_7-0_SP2_Fix7, Monitor_7-1_Fix3, or Monitor_7-1-2_Fix1 (or latest) will help to resolve the issue in releasing the Connection correctly.
General recommendations
Document Logging not working in 8.0
Check the following if you find that document logging is not working:
• IS is configured with JDBC Pools for IS Core Audit.
• IS is configured with Messaging -> Broker settings.
• WmLogUtil package is enabled and Running.
• Document Type Logging is enabled in the Broker. In MWS Admin -> Messaging -> Broker Servers -> Servers. Click on the Broker in the list where you have this document type defined. You will see a check box with label Document type logging. Select this check box.
• In MWS Admin -> Messaging -> Client Groups -> Integration Server -> Log Publish -> Pick the document type and add it to this list.
• Check the Last Published column for that document type to make sure it has the correct time-stamp when the document was last published to the Broker.
This confirms that the document type gets published to Broker fine, and only auditing is an issue.
• While configuring Document Logging, there will be two client's created by name ISClientPre-fix_LogOnPublish and ISClientPrefix_LogOnAck. Please go to ISClientPreISClientPre-fix_LogOnPublish -> Go to Subscriptions tab, where you will see the list of Document types for that Broker. Select the document type that you would like to log, and click the Add Subscription button.
Issues in Service Audit/Process Audit
At times, you see the service/process auditing works for a while and suddenly stops auditing further in 8.0.1
This is a known issue. Please apply the IS_8.0_SP1_Core_Fix5 (or latest) to resolve this issue.
If the issue still persists, please contact SAG Global Support.
Fixes
Software AG suggests reviewing the latest fixes, which are available the Empower website. Because fixes are cumulative, readme files will provide the details about issues that are fixed by previous fixes as well.
Readme files also contain the information about the fix requirements and installation instructions.
Software AG strongly recommends installing the latest maintenance release. New fixes will only be provided on top of the latest maintenance release. For example, assume that the current maintenance release of 7.1 is SP2 (that is, 7.1.2). In this case new fixes will only be delivered on top of 7.1.2; no new fixes ill be created for 7.1.1.