Support for JBoss EAP 7.2.x and WildFly 15.x
Support for JBoss EAP 7.2.x and WildFly 15.x
If your existing Identity Portal deployment uses JBoss EAP 6.4 or WildFly 8.2 as application server, we recommend migrating to the supported versions - JBoss EAP 7.2.x or WildFly 15.x using the Migration Tool.
The minimum supported WildFly version for migration is 15.0.1.The supported migrations are,
- JBoss EAP 6.4 to JBoss EAP 7.2.x
- WildFly 8.2 to WildFly 15.x
For a successful migration to JBoss EAP 7.2.x or WildFly 15.x, you must complete the following tasks:
Post migration to the supported JBoss/WildFly application server, upgrade of Identity Portal deployment from 14.2 to 14.3 is not supported.
Pre-requisites
Before running the migration tool, ensure that the following pre-requisites are met on each of the cluster nodes.
- Install JBoss EAP 7.2.x or WildFly 15.x on the existing Identity Portal server.
- For WildFly 15.0.x, download v1.5.0 binary distribution of the JBoss Server Migration Tool from the JBoss Server Migration Tool GitHub repository. For JBoss EAP 7.2 GA, the tool is already part of the GA distribution installed in Step 2.
Run the Migration Tool
Run the migration tool on each of the cluster nodes by following the given steps:
- Shut down the Identity Portal server.
- From the command line, navigate to the location where you had downloaded and extracted Symantec Migration Tool.
- RunSymantec_migrate_tool.batfor Windows andSymantec_migrate_tool.shfor Linux with the following arguments:Symantec_migrate_tool.bat/sh -s “<Location where the existing JBoss EAP 6.4 or WildFly 8.2 is installed>” -t “<Location where JBoss EAP 7.2.x or WildFly 15.x is installed>”Note:(For Windows Only) If the folders in the application server installed path contains a space (For example, Program Files), ensure that you replace the space with the equivalent short name (For example, PROGRA~1). You can rundir /xcommand to find the equivalent short names for the folders. For example:C:\JBossMigration>Symantec_migrate_tool.bat -s “C:\PROGRA~1\wildfly-8.2.1.Final” -t “C:\wildfly-15.0.1.Final\"
- (For WildFly Only) When prompted to enter the “Absolute Path of the Migration tool to use", enter the location of the JBoss Server Migration Tool that you had downloaded as part of step 4 in the pre-requisites section.
- On a successful migration, you should see a success message on the screen. In case of a failure, try running the migration tool again. If the issue persists, open a support case.
Post-Migration Tasks
Post-migration, ensure that you complete the following tasks on each of the cluster nodes.
- Copy the fine-tune configurations from<JBoss EAP 6.4/WildFly 8.2_Home>/bin/standalone.conf.bat/shto<JBoss EAP 7.2.x/WildFly 15.x_Home>/bin/standalone.conf.bat/sh.
- (Applicable only when the keystore/certificate files are placed in the JBoss/WildFly configuration directory)If using SSL, ensure that you copy the keystore/certificate files from<JBoss EAP 6.4/WildFly 8.2_Home>/standalone/configurationto<JBoss EAP 7.2.x/WildFly 15.x_Home>/standalone/configuration.
- Start the Identity Portal server.
(Optional) Run WildFly as a Service
To run WildFly as a service, follow the procedures in the given links: