Resolution | This problem is fixed in 7.0.2 P05 and 7.1.0 as the new aveksaWFArchitect.ear file has built in JVM parameters ${wp-client-hostname} and ${wp-client-hostport} that can be used to specify the hostname and ports of each node. As of 7.1.1 we can leverage an additional parameter, ${wp-client-protocol}.
Note: The values provided for the parameters ${wp-client-hostname}, ${wp-client-hostport}, and ${wp-client-protocol} do not have to be reachable from the end users' browsers. They have to be reachable locally from where the aveksaWFArchiect.ear is deployed to where the aveksa.ear is deployed, which in most cases is the same server.
To resolve this issue follow the steps below:
- If you are on 7.0.2, apply 7.0.2 P05+ or upgrade to 7.1.0.
- If you cannot apply 7.0.2 P05+ or upgrade to 7.1.0, first follow the steps under the Workaround section before proceeding further.
- Follow one of the steps below, per your application server to set up these JVM parameters.
WildFly
- Login as the oracle user via SSH to a server that hosts the Identity Governance & Lifecycle WildFly application (in case of cluster environments, you need to do this for each server).
- Edit one of the following files as per you setup:
- Standalone environment: /home/oracle/wildfly/bin/standalone.conf
- Clustered environment: /home/oracle/wildfly/bin/domain.conf
- Add the following line to the very end of the file:
JAVA_OPTS="$JAVA_OPTS -Dwp-client-hostname=<Your Identity Governance & Lifecycleinternal server hostname> -Dwp-client-hostport=<Your internal Identity Governance & Lifecycle server HTTP port> " (7.1.1 only) additionally, you can add: -Dwp-client-protocol=<protocol> WebSphere
- In the WebSphere console, to select the server, click Servers > Server types > WebSphere application servers and select the server.
- Choose the server used for RSA Identity Governance & Lifecycle.
- Under the Configuration tab, select Server Infrastructure > Java and Process Management > Process Definition.
- Under Additional Properties, select Java Virtual Machine.
- Enter the following under Generic JVM Arguments:
-Dwp-client-hostname=<Your internal RSA Identity Governance & Lifecycle server hostname> -Dwp-client-hostport=<Your internal RSA Identity Governance & Lifecycle server HTTP port> (7.1.1+) -Dwp-client-protocol=<protocol>
- Save to the master configuration.
-Dwp-client-hostname=<Your internal Identity Governance & Lifecycle server hostname> -Dwp-client-hostport=<Your internalIdentity Governance & Lifecycle server HTTP port> (7.1.1+) -Dwp-client-protocol=<protocol>
- After completing the JVM settings described above, restart the WebLogic application server.
|
Workaround | On any 7.0.2 patch before P05, you would first need to edit the aveksaWFArchitect.ear file and modify the default URLs to the add the above JVM parameters, then deploy the newly modified aveksaWFArchitect.ear file on your application server.
- You can do the following steps on any machine on which the Java Development Kit 1.7 (JDK 1.7) is installed, and also on which you correctly configured the PATH environmental variables. Use the Java Tutorial on CLASS and CLASS PATH for reference. The below example uses Windows.
- Use any application (for example, 7Zip) to extract the RSA Identity Governance & Lifecycle software/patch .tar file to any directory; A directory named Packages is used for the following example.
- Create a working directory, new_ear, for example.
- Copy the aveksaWFArchitect.ear file from the extracted tar directory in step 2 to the new_ear directory.
- Create two temporary directories under new_ear. For example, ear_dir and jar_dir.
- Open the Windows command prompt (cmd.exe).
- Use the following commands to unzip the aveksaWFArchitect.ear in the temporary ear directory named ear_dir:
cd ear_dir jar -xvf ..\aveksaWFArchitect.ear
 - Use the following commands in the command prompt to unzip <ear_dir>\APP-INF\lib\acmConfig.jar in the temporary jar directory named jar_dir:
cd ..\jar_dir jar -xvf ..\ear_dir\APP-INF\lib\acmConfig.jar
 - Use any text editor (preferably Notepad++) to modify the property values for serverContextPath and client.connect.URL in the properties file <jar_dir>\workpoint-client.properties as follows:
serverContextPath = http://${wp-client-hostname}:${wp-client-hostport}/wpServices client.connect.URL = http://${wp-client-hostname}:${wp-client-hostport}/wpServices/xml
- Save the changes to workpoint-client.properties, and close the file.
- Use the following commands in the command prompt to rebuild the modified acmConfig.ear:
cd jar_dir jar uvfm ..\ear_dir\APP-INF\lib\acmConfig.jar META-INF\MANIFEST.MF *
 - Use the following commands in the command prompt to rebuild the modified aveksaWFArchitect.ear:
cd ..\ear_dir jar uvfm ..\aveksaWFArchitect.ear META-INF\MANIFEST.MF *
 - The aveksaWFArchitect.ear in the new_ear directory now has been updated with the changes. You can now follow the steps in the RSA Identity Governance & Lifecycle 7.0.2 Installation Guide specific to your application server, RSA Identity Governance & Lifecycle 7.0.2 - Configuring WildFly Clustering or contact RSA Support to deploy the new aveksaWFArchitect.ear file.
- Follow the above steps under Resolution to set the values of the newly added JVM parameters.
|