USE CASES

1. Configuring JAVA prior the DWP Catalog Installation
2. Updating and configuring JAVA after the DWP Catalog Installation - Switching to OpenJDK11
3. Most of these instructions would also work for DWP.

CONSIDERATIONS

• OpenJDK11 is the only OpenJDK version that we actually support for the DWP Catalog, at this moment. This can change in the future, please, keep an eye on the Compatibility Matrix for more details.
• Do not use Open 1.7 or OpenJDK 1.8 or any other.
• BMC started supporting OpenJDK11 from 20.02 and beyond versions

PREREQUISITES

• Install OpenJDK11. This needs to be done as root: 

yum-config-manager --enable rhel-7-server-optional-rpms

yum install java-11-openjdk-devel

NOTE: there are other ways to install it. Contact your sysadmin for more info.


Finding out which JAVA versions are installed and which JAVA is being used.

1.  Run the next commands:  alternatives --config java 

                     Below is an example:
 

• The one with the plus sign is the JAVA that is being used on this Linux Server.
• Select OpenJDK11
• Note that you can change that value at any give time.
• Set JAVA_HOME as follows:                                                     

                  2.  Create a soft link from your current JAVA to /usr/java/latest

                       Example:    ln   -s  /usr/lib/jvm/java-11-openjdk-11.0.3.7-0.el7_6.x86_64       /usr/java/latest

Update below bash profile

This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.


USE CASE I. Configuring JAVA prior the DWP Catalog Installation  - BEST PRACTICE
 

1.   Create a soft link from your current JAVA to /usr/java/latest prior installing DWP Catalog to avoid most of these steps.  That way, you would only need to update the soft link each time you upgrade JAVA and not the config files.

   
          Example:    ln   -s  /usr/lib/jvm/java-11-openjdk-11.0.3.7-0.el7_6.x86_64       /usr/java/latest

Have in mind:

•    You need root/sudo permissions to perform any changes related to JAVA on any environment - if you don't feel confident about doing this, contact your sysadmin for further instructions.
•    If you do the above prior the DWP Catalog install, you would only have to specify /usr/java/latest  as the JAVA Home Path for the options.txt file
   

              -J BMC_JAVA_JRE_64_BIT_HOME_PATH=/usr/java/latest

•  You need to update /opt/bmc/digitalworkplace/bin/arserverd after the installation is done and comment this value out. Example:

           jvm.option.22=-XX:+UseParNewGC   to
          #jvm.option.22=-XX:+UseParNewGC

• After doing above step, have in mind that you will also need to renumber the other JAVA Options. 

          Example - Original File
 

          Example - Updated File
   

• Restart the DWP Catalog by running ./dwpcontroller stop and ./dwpcontroller start
• If the server comes up as expected, this means that the changes were performed correctly.

Notes: You can run ps -efa | grep java to confirm all the Catalog processes are running using the /usr/java/latest path



USE CASE II. Updating and configuring JAVA after the DWP Catalog Installation - - Switching to OpenJDK11 (works for any other Oracle JRE version too)


A) Don't want to update the java path in the config files and want to use a newer java version that is pointing it to the old java home value.

• Install openJDK11. See above.
• Extra: copy jre 1.8 cacerts to openjdk11 cacerts
• Confirm your current java version by running alternatives --config java
• Take note of that java path, i.e. -> /usr/java/jre1.8.0_181-amd64       (no need to copy the full string, remove /bin/java)
• Switch to OpenJDK11 by selecting OpenJDK11 from the list (when running alternatives --config java)
• If you have SSL in place, you might want to take a backup of your current CA Cert files prior executing below step. This way, you won't have to recreate all the certificates and import certs from scratch.
• Uninstall the JRE file by running

• Create a symbolic link: new OpenJDK11 directory pointing to the Java that you just deleted (see bullet 3), example:

• This way you won't have to update all the config files, but you have to take note of this change.
• Perform the steps in the "Have in mind" section
• Restart dwpcontroller and confirm the application comes up with no issues

A) Need to update the java path in the config files, use a symbolic link and update the all the config files with command line and not one by one.

Install OpenJDK11

1. Extra: copy jre 1.8 cacerts to openjdk11 cacerts
2. Run alternatives --config java
3. Select OpenJDK11 from the list that was displayed on the previous steps
4. Update or create a symbolic link from openjdk11 directory to /usr/java/latest.     
5. Update JAVA home by running export JAVA_HOME=/usr/latest/java
6. Update JAVA PATH in all the DWP Catalog config files

• Find out what the current DWP Catalog Java Path is by doing the following 

• Replace the path by running below commands. NOTE – we are assuming that no more that one JAVA Path is being used, if there is more than one in the config files, you will need to run below commands multiple times until all the old entries are replaced by the new one

All of the above require a DWP Catalog Restart when done.

Note: If SSL is in place, also consider updating the jetty-http.xml ca certs directory and the user_group_sync.sh JAVA info.
Check KA 000133376 for that.