This document describes how to migrate an earlier version of EntireX to version 9.6 under UNIX or Windows. EntireX version 9.6 can only be installed in parallel to an existing EntireX version. In this scenario you can migrate user data from one installation to the other easily, using the steps described here. The information applies to both UNIX and Windows systems; any differences are described explicitly.
This document covers the following topics:
Note:
In this document, source refers to an earlier EntireX installation,
and target refers to the current EntireX version 9.6.
The broker attribute files are located at <inst_dir>/EntireX/config/etb. Follow the steps below to migrate broker data from one installation to the other:
To migrate broker data
Stop all running EntireX brokers in both the source and target installations. EntireX brokers from other installations and platforms are not affected.
Stop all running RPC Servers that are registered to EntireX brokers in source or target installations. This also includes remote RPC servers or RPC servers from other EntireX installations if these RPC servers are registered with the brokers to be shut down.
Stop the Broker Administration Service/Daemon.
Under UNIX:
Stop the UNIX broker admin service, using the script
EntireX/bin/sagnetbsrv
| where | n | is a number in both installations, e.g. "sag2etbsrv stop". |
Under Windows:
From the Control Panel in both installations, choose
Note:
The first installation does not have a number to identify it. The second and subsequent installations are appended with (2),
(3) etc.
Copy all relevant directories of defined brokers from source to target installation. These directories - one for each broker - are located under <inst_dir>/EntireX/config/etb.
Note:
Copy the complete directories, not just the attribute
files.
Check the broker attribute files for path names and adapt them to the target installation.
Restart the Broker Administration Service/Daemon.
Under UNIX:
Start the broker admin service for both installations, for example
with command
sag2etbsrv start
Under Windows:
From the Control Panel, restart the Software AG EntireX Broker
Service for both installations.
Following the above steps, autostart settings and user credentials are not migrated. Apply these manually in the new installation. When you restart the Broker Administration service, all brokers will be shown. Readjust the autostart settings and user credentials, using System Management Hub.
You do not need to move Broker definitions (attribute file etc.) that are stored outside the EntireX installation directory. Simply makes sure when you start a broker stored externally that the broker executable from version 9.6 is used. This may apply to your scripts or when you start a broker manually.
Authorization rules cannot be migrated and must be reentered in the new installation. You can readjust them using System Management Hub.
You can migrate manually all RPC servers of the source installation that are visible in System Management Hub and maintained using System Management Hub.
To migrate RPC servers
Copy the file <inst_dir>/EntireX/config/rpc.server.properties from source to target installation.
In this file, adapt path names that reference your source installation to your target installation.
Paths of RPC servers other than the source installation can remain unchanged.
Please note the following when migrating Web services to a more recent version of EntireX:
Artifacts such as XMM or AAR files can be reused without regeneration.
Make sure Web Services Stack and EntireX are on the same level.
Modify your scripts (for example the start script of the XML/SOAP RPC Server) so that they use the new versions of the relevant JAR files of Web Services Stack and EntireX.
This section applies to migrations from EntireX version 8 and above. For EntireX version 7, see Migrating XML/SOAP Components from EntireX Version 7.n in the XML/SOAP Wrapper documentation.
This section covers the following topics:
Update the start script to set the paths to current installation. If the properties file contains a path to the configuration file, you may need to adjust the path. The properties and configuration files can be used as before. See Configuration File for the XML/SOAP RPC Server under UNIX | Windows for more information.
Update the start script to set the paths to current installation.
Save your Web services (AAR files) and modified configuration files (i.e. axis2.xml). You do not need to re-generate your Web services (AAR files). If the configuration was modified, perform the same modifications for the new installation and restart Software AG Web Server. Redeploy the web services (AAR files).
Note:
The new installation will use another port by default, which means that the Web clients need to be adjusted.
Save your Web services (AAR files) and modified configuration files (i.e. axis2.xml). You do not need to re-generate your Web services (AAR files). For deployment of file wsstack.war and copying file entirex.jar to Web Services Stack, see the separate Web Services Stack documentation, also available under webMethods Product Documentation on the Software AG Documentation website.
If configuration was modified, perform the same modifications for new installation and restart the Web server. Redeploy the Web services (AAR files).
EntireX Workbench is part of the Eclipse-based Software AG Designer.
We recommend you import existing projects into a new workspace of your target installation. We do not recommend reusing an existing Eclipse workspace. This may damage data or result in strange behavior.
This section describes how to import the projects of Software AG Designer from an earlier version into the workspace of the new Software AG Designer 9.6, then redeploy the Web services to the new Web Services Stack 9.6. It covers the following topics:
Notes:
Before you migrate your old projects, you can optionally migrate your existing preferences to your new 9.6 installation.
To migrate the preferences to the new workspace (optional)
Open Software AG Designer 9.6 and point to a new 9.6 workspace. Accept the default "workspace96" or specify another one.
Export your preferences before upgrading:
Start the old version of Software AG Designer with the old workspace.
Choose . In the Select panel, chose and click .
In the To preference file field, specify the EPF (Eclipse Process Framework) file to which you want to export your preferences, then click .
Import these preferences to the new workspace:
Start Software AG Designer 9.6 with the new workspace.
Choose . In the Select panel, choose and click .
In the From preference file field, specify the EPF file to which you exported your preferences, then click .
To import projects into Software AG Designer 9.6
Choose . In the Select panel, choose and click .
In the panel, choose and go to the old workspace. The projects appear in the Projects box. Select the projects to import into Software AG Designer 9.6.
Choose and click .
To redeploy the Web services
Select an AAR file and from the context menu choose .
Select the correct URL that points to the Web Services Stack 9.6 installation.
