Upgrade JBoss EAP cluster from 7.4.10 to 7.4.23 for AEM Forms on JEE upgrade-jboss-eap-cluster-from-7-4-10-to-7-4-23
Overview overview
When you upgrade a JBoss EAP cluster from version 7.4.10 to 7.4.23 for AEM Forms on JEE, additional configuration is required beyond the standalone upgrade steps. Cluster-specific settings such as cache locators, master-slave authentication, host bindings, and domain controller configuration must be updated on the new JBoss installation.
Applies to applies-to
This article applies to:
- AEM Forms on JEE running on JBoss EAP 7.4.10 in a cluster environment
- Master-slave JBoss EAP configurations on Windows and Linux
Prerequisites prerequisites
Complete all steps in Upgrade JBoss EAP from 7.4.10 to 7.4.23 for AEM Forms on JEE, including copying the connection URL, username, and password from the existing installation to the new configuration files.
Steps steps
Perform the following additional cluster-specific steps:
Update domain.conf.bat update-domain-conf-bat
-
In your
domain.conf.bat, add the locators information from your existing setup to the new file:code language-text set "JAVA_OPTS=%JAVA_OPTS% -Doak.documentMK.maxServerTimeDiffMillis=-1" set "JAVA_OPTS=%JAVA_OPTS% -Dadobe.cache.cluster-locators=<ip-address-master>[22345],<ip-address-slave>[22345]" set "JAVA_OPTS=%JAVA_OPTS% -DentityExpansionLimit=10000"
Configure master-slave authentication configure-master-slave-authentication
-
Create a new user for master-slave authentication on the master node.
-
On the slave nodes, update the user password in
host.xml:code language-xml <server-identities> <secret value="Y2hhbmdlaXQ="/> </server-identities>
Update IP addresses in host.xml update-ip-addresses-in-host-xml
-
Update the IP addresses for both master and slave nodes in
host.xml:code language-xml <interfaces> <interface name="management"> <inet-address value="${jboss.bind.address.management:<ip-address>}"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:<ip-address>}"/> </interface> </interfaces>
Remove deployments from domain configuration remove-deployments-from-domain-configuration
-
Ensure that there is no
<deployments>section in the newdomain_<db>.xmlfile. -
Do not copy the following block from the existing configuration:
code language-xml <deployments> <deployment name="adobe-forms-ivs-jboss.ear" runtime-name="adobe-forms-ivs-jboss.ear"/> <deployment name="adobe-livecycle-cq-author.ear" runtime-name="adobe-livecycle-cq-author.ear"/> <deployment name="adobe-livecycle-jboss.ear" runtime-name="adobe-livecycle-jboss.ear"/> <deployment name="adobe-livecycle-native-jboss-x86_win32.ear" runtime-name="adobe-livecycle-native-jboss-x86_win32.ear"/> <deployment name="adobe-livecycle-native-jboss-x86_win64.ear" runtime-name="adobe-livecycle-native-jboss-x86_win64.ear"/> <deployment name="adobe-output-ivs-jboss.ear" runtime-name="adobe-output-ivs-jboss.ear"/> <deployment name="adobe-workspace-client.ear" runtime-name="adobe-workspace-client.ear"/> </deployments>
Update driver class in domain configuration update-driver-class-in-domain-configuration
-
Update the driver class section in
domain_<db>.xmlbased on your database engine:MSSQL:
code language-xml <xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>Oracle:
code language-xml <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
Update domain controller on slave nodes update-domain-controller-on-slave-nodes
-
Update the domain controller block on the slave node in
host.xmlwith the master IP address, port9999, usernameslave1, and realmManagementRealm:code language-xml <remote host="<ip-address>" port="9999" username="slave1" realm="ManagementRealm"/>
Update jboss-cli.xml update-jboss-cli-xml
- Update the
<host>entry injboss-cli.xmlon both the master and slave nodes.