We can migrate a Configuration from the IBM WebSphere (full profile) application server to Red Hat JBoss Enterprise Application Platform (JBoss EAP) application server. Currently, the migration is supported for the following versions:
- WebSphere (full profile) versions 7/8/8.5 to JBoss EAP version 6.3
Migration of Configuration without application exporting
- Start WebSphere (full profile) version 7.0/8.0/8.5 application server.
- Start BMC MIddleware Automation version 8.6.
- Create a Snapshot of the current WebSphere Configuration.
- Ensure that the WebSphere Configuration Snapshot contains application elements.
- Right-click the created Snapshot and select Migrate Configuration.
- In the Migrate Configuration dialog, click the ‘…’ button next to Source Server Profile, and select the server profile of your source WebSphere application server.
- From the Target Application Server list, select JBoss EAP 6.3.
- Clear the Export applications check box, and then click Next.
- Enter the name for the migrated Configuration, and click Next.
- Select the Node(s) migration migration mode, and click Next. The Nodes filter screen displays.
- Select the nodes you want to migrate, or selects the Migrate all nodes check box, and click Next. The Servers filter screen, that lists all servers that belongs to the selected on previous screen clusters displays. If you did not select any clusters, then the complete list of node servers displays.
- Select the servers you want to migrate, or selects the Migrate all servers check box, and click Next. The Applications filter screen, that lists all the applications that belongs to selected servers displays.
- Select the applications that you want to migrate, or selects the Migrate all applications check box, and then click Next. The Summary screen, that contains information about configuration, selected nodes, servers, applications etc displays.
- Click Finish. The transformation process is started. Status view displays the migration log output.
Post-migration configuration
The migrated Configuration is created. It contains the application elements that use tokens as values for the sourcePath attribute. You can view all the information about preconditions, transformations and tokens create during migration in the Migration report.
To finalize the migration, follow the next steps:
- Open the target JBoss EAP version 6.3 Configuration and de-tokenize it.
- Install the Configuration on the JBoss EAP 6.3.
Migration of Configuration with application exporting
- Start WebSphere (full profile) version 7.0/8.0/8.5 application server.
- Start BMC MIddleware Automation version 8.6.
- Create a Snapshot of the current WebSphere Configuration.
- Ensure that the WebSphere Configuration Snapshot contains application elements.
- Right-click the created Snapshot and select Migrate Configuration.
- In the Migrate Configuration dialog, click the ‘…’ button next to Source Server Profile, and select the server profile of your source WebSphere application server.
- From the Target Application Server list, select JBoss EAP 6.3.
- Select the Export applications check box, and then click Next.
- Enter the name for the migrated Configuration, and click Next.
- Select the Node(s) migration migration mode, and click Next. The Nodes filter screen displays.
- Select the nodes you want to migrate, or selects the Migrate all nodes check box, and click Next. The Servers filter screen, that lists all servers that belongs to the selected on previous screen clusters displays. If you did not select any clusters, then the complete list of node servers displays.
- Select the servers you want to migrate, or selects the Migrate all servers check box, and click Next. The Applications filter screen, that lists all the applications that belongs to selected servers displays.
- Select the applications that you want to migrate, or selects the Migrate all applications check box, and then click Next. The Summary screen, that contains information about configuration, selected nodes, servers, applications etc displays.
- Click Finish. The transformation process is started. Status view displays the migration log output.
Post-migration configuration
All the applications from the source Configuration that were selected during filtering are exported to the migrated configuration folder (migration folder). The migrated Configuration is created, and it contains application elements that use the paths to the exported applications in the migration folder as values for the sourcePath attribute. You can view all the information about preconditions, transformations and tokens create during migration in the Migration report.
- To finalize the migration, follow the next steps:
- Open the target JBoss EAP version 6.3 Configuration and de-tokenize it.
- Install the Configuration on the JBoss EAP 6.3.
Migration of custom Configuration templates
You can migrate the packaged Config template that contains resources needed by your application. For example: JDBS providers, JMS providers, Mails sessions, etc.
- Right-click the created packaged Configuration template and select Migrate Configuration.
- In the Migrate Configuration dialog, click the ‘…’ button next to Source Server Profile, and select the server profile of your source WebSphere application server.
- From the Target Application Server list, select JBoss EAP 6.3.
- Enter the name for the migrated Configuration, and click Next.
- Select the Packaged Configuration migration mode, and click Next. The Summary screen displays.
- Click Finish. The transformation process is started. Status view displays the migration log output.
Post-migration configuration
- To finalize the migration, follow the next steps:
- Open the target JBoss EAP version 6.3 Configuration and de-tokenize it.
- Install the Configuration on the JBoss EAP 6.3.