webMethods Migration from 7.1.3 to 9.7 - Implementation Challenges

Hello there,

We would be migrating our existing wM 7.1.3 platform to wM 9.7. I would like to see if anyone out there had any challenges and appreciate if you could share your experience in wM 9.7


Dear Ramesh,

It’s better to go through empower portal to get the details from end to end.

Below are the major issues found for the 9.7 release, for some of them core fixes are available on the empower.

  1. After a remote Integration Server connection is created and a successful connection is established, if the remote server connection settings are changed (for example, if a different port number is specified), Integration Server does not create a new session when subsequent connection attempts are made. As a result, Integration Server Administrator indicates that subsequent connections are successful, even if the revised remote server settings are incorrect (for example, if the revised port number is not valid).

  2. When Integration Server is acting as an HTTP client, it retains the HTTP cookies from the remote server. If two users connect to the same remote server, they use the same set of cookies.
    Since the session ID is often stored in a cookie, this can result in the two users using the same session on the remote server. Each user should use a unique session when connecting to a remote server.

  3. When a trigger service uses a transacted JMS connection alias, and that service sends JMS messages using the pub.jms:send service to a different transacted connection alias, the sessions on the JMS provider are not closed. As a result, connection attempts are refused because channel and process limits are reached.

  4. The number of active stateful sessions becomes high because sessions created by the Platform Manager were not being cleaned up upon disconnect but were not being removed from memory until the session time out limit elapsed. This issue was introduced by PIE-30630 which is included in Integration Server 9.7 and included in IS_9.6_Core_Fix1 or IS_9.6_Core_Fix2.

  5. The “ls” FTP command does not return the list of files in a directory if the FTP Client is connected to an FTPS listener in Integration Server in PASSIVE mode.

  6. Web service descriptor does not use user-defined prefixes for fault and handler document types. When creating a consumer web service descriptor or a WSDL first provider web service descriptor, the user creating the web service descriptor can specify namespace prefixes to replace the prefixes used in the WSDL document. However, Integration Server was not using the user-defined prefixes for the IS document types generated for fault or handlers messages.

  7. During startup, Integration Server issues a ClassCastException and fails to start. During startup, Integration Server fails to initialize InvokeManager from the invokemanager.cnf configuration file located at IntegrationServer_directory\instances\default\config directory and issues a ClassCastException. This issue occurs only if a custom invoke chain processor is configured in the invokemanager.cnf file.

Kindly list others after you analyzed.


As already mentioned by others in other posts, there is no direct migration path for this.

Make sure you have the latest 7.1.3 installed.
Than you will have to do an interim migration to 9.5 (latest one for which an migration path from 7.1.3 exists).
After that you can migrate to 9.7 or what ever you like.


Thanks for sharing. I will list any we experience.