Prepare the Old My webMethods Server Installation
- Install the latest product fixes on the old My webMethods Server, then start the old My webMethods Server.
- Local configuration files for MWS overwrite configuration files, stored in the database.
Go to old_Software
AG_directory/MWS/server/instance_name/config to check for any custom configuration files you do not
want to migrate and delete them from the old installation.
For more information about editing custom configuration settings for IBM My webMethods Server, see Administering IBM My webMethods Server.
- If your old installation includes custom JVM settings in the custom_wrapper.conf file,
make sure you review the latest Java release notes for your Java version, and delete any
properties that are no longer supported by your Java distribution from the
custom_wrapper.conf file.Note:
The PermSize and MaxPermSize JVM properties are no longer supported with the current Java distribution. If your old installation uses custom values for that property, remove the PermSize and MaxPermSize settings from the custom_wrapper.conf file.
- 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. - 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.
- On the old machine, open a command window or
shell, go to the old_Software
AG_directory/MWS/bin/migrate or old_Software AG_directory /MWS/bin
directory, depending on which old release you have, and run the command below. The
command creates a ZIP file named mws.zip in old_Software
AG_directory/MWS/bin/migrate directory.
ZIP-mws.{bat|sh}
- 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.
- On the old machine, open a command window or
shell, go to the old_Software
AG_directory/MWS/bin/migrate or old_Software AG_directory /MWS/bin
directory, depending on which old release you have, and run the command below. The
command creates a ZIP file named mws.zip in old_Software
AG_directory/MWS/bin/migrate directory.