Migration Framework 10.15 | Upgrading Software AG Products On Premises | Upgrade the Asset Build Environment, Deployer, or Application Platform (Deprecated) | Upgrade Application Platform (Deprecated) | Complete the Upgrade | Upgrade from 9.9, 9.10, or 9.12: Complete the WmTomcat Web Applications Migration
 
Upgrade from 9.9, 9.10, or 9.12: Complete the WmTomcat Web Applications Migration
1. Remove the dependency of each web application on WmTomcat. For each migrated Integration Server package, go to the new_Software AG_directory/IntegrationServer/instances/instance_name/migrated_package directory, open the manifest.v3 file in a text editor, remove the line below, and then save the file.
<value name="WmTomcat">...</value>
2. The URL for the migrated web applications is different from the URL for the original web applications; the port number changes, and the /web segment is removed (for example, the old URL http://localhost:5555/web/MyPackage/index.jsp becomes http://localhost:8072/MyPackage/index.jsp). Notify your users and update your software components that depend upon the URL.
3. Each web application was migrated as a war ZIP file. If you want to reduce the time it takes the Tomcat servlet container to start, go to the new_Software AG_directory/profiles/instance_name/workspace/webapps directory and extract the war files from each ZIP file into the webapps directory.
4. If you have direct calls to the Integration Server API com.wm.app.b2b.server.Service.doInvoke( ) in the JSP page for a web application, replace them with <webm:invoke/> custom tags. For instructions, see the Application Platform documentation.