Prepare the Old Installation
1. In the old webMethods OneData, go to the Home > Administer > Job Center page. On the Filter page, for each job type, filter by Active or Pending Active. If a job has one of these statuses, terminate the job or wait for it to complete.
2. If you are using JMS with webMethods OneData, go to the old_Software AG_directory/profiles/ODE/webapp/onedata/WEB-INF/lib directory and back up all client jar files required for JMS providers.
3. If you are using Kerberos authentication with webMethods OneData, back up your Kerberos-based SSO configurations and files. The table below lists the directories that contain the Kerberos-based SSO configurations and files to back up.
old_Software AG_directory/ | Files to Back Up |
profiles/ODE/configuration/tomcat/conf | server.xml |
profiles/ODE/configuration | custom_wrapper.conf and jaas.config |
profiles/ODE/workspace/webapps/onedata/WEB-INF | web.xml |
profiles/ODE/configuration/com.softwareag. platform.config.propsloader | All com.softwareag.jaas. realm.pid-SSO_realm_name |
4. Shut down the old installation.
If the product is running | Take this action... |
As a Windows service | Shut down from the Windows Services window. Services are listed as Software AG product release. |
As a Windows application | Shut down from the Windows start menu. Applications are listed as Software AG > Stop Servers > product . |
On a UNIX system | Use the shut down instructions in the product documentation for your old release. |
Note:
It is especially important to shut down all old webMethods OneData instances that connect to database components you are going to migrate.
5. If your old and new installations are on different machines, create a ZIP file of the old product installation to use as the migration source. The instructions in this section use the Java Archive tool to create the ZIP file. Specify the location of the Java Archive tool in the JAVA_HOME and PATH system variables on the machine that hosts the old product installation. The tool is located in the Software AG_directory/jvm/jvm/bin directory. On some systems, the lower-level jvm directory name includes additional information, such as /jvm/jvm160_32, or /jvm/jvm170, or /jvm/jvm_64.
a. On the product’s old machine, open a command window or shell.
b. Go to the Software AG directory that contains the old product and enter this command:
jar cfM ZIP_file_name.zip install/products profiles/ODE/bin/onedata/config/*
c. Copy the product’s ZIP file to any directory on the machine that hosts the new product.
Important:
If using FTP to copy, use the binary file transfer mode\type. If you use another mode\type, the ZIP file might become corrupted.