Troubleshooting: Software AG webMethods

Table 1. Troubleshooting Software AG webMethods
Problem	Description	Solution
Error when synchronizing packages with the following message: `com.wm.app.b2b.client.ServiceException: com.wm.app.b2b.server.ServiceException: [ISS.0085.9150]` Cannot perform the operation without List ACL on package XXXXXX	The user that is specified in the configuration of the physical webMethods server needs to have permissions to read/list the packages that are present on the server.	The current configuration can be seen in Developer by opening the package and viewing the properties; under there is a List ACL entry with a group specified. The user that you configure in Rational® Integration Tester must be a member of this group.
A Java™ heap space error occurs when you synchronize packages.	If the package to be synchronized is large, it can require more memory than is available to Rational® Integration Tester.	To control the number of services for which metadata is retrieved from webMethods at one time when you are synchronizing, set the system property greenhat.wmis.schemaSync.chunkSize in the JVM Arguments field on the Application page of Library Manager. For example, to specify a chunk size of 50 webMethods services, enter `-Dgreenhat.wmis.schemaSync.chunkSize=50`. For more information about using Library Manager, see Working with the Library Manager. If this property is not specified, Rational® Integration Tester attempts to retrieve all the data at once.
Error when recording and fields are discarded	XML doc and XML nodes types are not supported when you record webMethods events. These fields are represented as internal references on the server and Rational® Integration Tester is unable to produce a string representation for them.	When such fields are encountered, they are discarded and an error is logged on the server.
You might see any of the following errors: Messages are not captured in the Recording Studio Test subscriber actions does not receive messages Stubs do not receive events The webMethods Integration Server log has the following entry: [ISP.0090.0004E] com.greenhat.wm.pipeline.GHTRecordingFilter.sendEventRecord -- Failed to send recorded event. Recovering. : java.net.ConnectException: Connection refused: connect	The connection details are sent by Rational® Integration Tester to the server. When events are triggered, the server makes a new connection to Rational® Integration Tester and sends the events using the TCP connection. In this case, the network connection from the webMethods server to Rational® Integration Tester cannot be made. If the communication fails, the Rational® Integration Tester package on the server is designed to delete any active event handlers. This results in active tests, stubs or recording sessions to stop working.	Restart any tests, stubs and recordings in Rational® Integration Tester to recreate the necessary event monitors on the server. You can fix the TCP port number that is used for the connection. By default, the port number is randomly chosen during the Rational® Integration Tester startup. Use a fixed port to aid debugging and prevent any issues with firewalls blocking the traffic. To set the port number, run the Library Manager and configure webMethods server port. Restart Rational® Integration Tester to use the fixed value.

Error when synchronizing packages with the following message:

com.wm.app.b2b.client.ServiceException: com.wm.app.b2b.server.ServiceException:
[ISS.0085.9150]

Cannot perform the operation without List ACL on package XXXXXX

The user that is specified in the configuration of the physical webMethods server needs to have permissions to read/list the packages that are present on the server.

The current configuration can be seen in Developer by opening the package and viewing the properties; under there is a List ACL entry with a group specified. The user that you configure in Rational® Integration Tester must be a member of this group.

A Java™ heap space error occurs when you synchronize packages.

If the package to be synchronized is large, it can require more memory than is available to Rational® Integration Tester.

To control the number of services for which metadata is retrieved from webMethods at one time when you are synchronizing, set the system property greenhat.wmis.schemaSync.chunkSize in the JVM Arguments field on the Application page of Library Manager. For example, to specify a chunk size of 50 webMethods services, enter -Dgreenhat.wmis.schemaSync.chunkSize=50. For more information about using Library Manager, see Working with the Library Manager.

If this property is not specified, Rational® Integration Tester attempts to retrieve all the data at once.

Error when recording and fields are discarded

XML doc and XML nodes types are not supported when you record webMethods events. These fields are represented as internal references on the server and Rational® Integration Tester is unable to produce a string representation for them.

When such fields are encountered, they are discarded and an error is logged on the server.

You might see any of the following errors:

Messages are not captured in the Recording Studio
Test subscriber actions does not receive messages
Stubs do not receive events
The webMethods Integration Server log has the following entry: [ISP.0090.0004E] com.greenhat.wm.pipeline.GHTRecordingFilter.sendEventRecord -- Failed to send recorded event. Recovering. : java.net.ConnectException: Connection refused: connect

The connection details are sent by Rational® Integration Tester to the server. When events are triggered, the server makes a new connection to Rational® Integration Tester and sends the events using the TCP connection.

In this case, the network connection from the webMethods server to Rational® Integration Tester cannot be made. If the communication fails, the Rational® Integration Tester package on the server is designed to delete any active event handlers. This results in active tests, stubs or recording sessions to stop working.

Restart any tests, stubs and recordings in Rational® Integration Tester to recreate the necessary event monitors on the server.
You can fix the TCP port number that is used for the connection. By default, the port number is randomly chosen during the Rational® Integration Tester startup. Use a fixed port to aid debugging and prevent any issues with firewalls blocking the traffic. To set the port number, run the Library Manager and configure webMethods server port. Restart Rational® Integration Tester to use the fixed value.