UPDATED Release notes: Version 23.01.01 of BMC AMI Common Enterprise Service

Make sure that:

• The JAVA_HOME environment variable is set to the Java 11 path.
• The Path environment variable is set to JAVA_HOME\bin.

To upgrade via the Update Center or the Installer

1. (If upgrading via Update Center) After initiating the upgrade process, wait for some time and then access CES in a new browser tab to verify that the CES UI loads successfully. If the UI does not load, it means that your Java 11 parameters are not properly configured. 

2. (Recommended) Set the JAVA_HOME variable at the system level, to point to Java 11.

   Warning

   Important

   If you are not able to set the JAVA_HOME variable at the system level, go to your installation folder and perform the following steps:

   1. In the CollectSupportFiles.bat file, modify JAVA_PGM=%JAVA_HOME%\bin\java.exe to JAVA_PGM=<Java11Path>\bin\java.exe.
   2. After a successful upgrade, add the JAVA_HOME path in the following variables residing in the CES_service.ini file:
      • jrepath=%JAVA_HOME%
        (For example, jrepath=C:\Program Files\Java\jdk-11)
      • path=%JAVA_HOME%\bin;%PATH%
        (For example, path=C:\Program Files\Java\jdk-11\bin;%PATH%)

3. In the installation folder, open the CES_service.ini file, and right after param02 = -XX:MaxPermSize=256m, add the following new parameter:
   -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory
   Refer to the highlighted sections in the sample file snippet to do so.

   params = 16
   param00 = -Xms256m 
   param01 = -Xmx1536m 
   param02 = -XX:MaxPermSize=256m
   param03 = -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory
   param04 = -Dosgi.instance.area=$APP_DATA_DIR$/workspace
   param05 = -DAppDataDir=$APP_DATA_DIR$
   param06 = -Djetty.base=$APP_DATA_DIR$/jetty
   param07 = -Dlog.data.path=$APP_DATA_DIR$/workspace/logs
   param08 = -Dosgi.parentClassLoader=boot
   param09 = -Declipse.log.level=INFO
   param10 = -jar
   param11 = $USER_INSTALL_DIR$/plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar
   param12 = -clean
   param13 = -noRegistryCache
   param14 = -application
   param15 = com.compuware.webapps.application

4. Restart the CES service and upgrade your database when prompted.

Make sure that:

• The JAVA_HOME environment variable is set to the Java 11 path.
• The Path environment variable is set to JAVA_HOME/bin.

To upgrade via the Update Center or the Installer

1. (If upgrading via Update Center) After initiating the upgrade process, wait for some time and then access CES in a new browser tab to verify that the CES UI loads successfully. If the UI does not load, it means that your Java 11 parameters are not properly configured. Then, for CES to run with Java 11, edit the CESEMN file and configure the parameters as follows:
   
   1. Modify the value of JAVA_HOME and set it to the Java 11 home directory (for example, export JAVA_HOME=/usr/lpp/java/J11.0_64).
   2. Update the value of JAVA_FONTS; you need export JAVA_FONTS when using Strobe Insight reports.
      Identify the path of Java fonts. (If Java 8 is installed, this is available in the Java 8 lib/fonts directory.) Add the Java 8 fonts path to JAVA_FONTS (for example, export JAVA_FONTS=/usr/lpp/java/J8.0_64/lib/fonts).
   3. Add the following lines to configure LIBPATH to include Java 11 libraries:
      1. LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin
         
      2. LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib
         
      3. LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/default
      4. LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/j9vm
      5. export LIBPATH
   4. In the CESEMN.PARMLIB file, in the DEFS="-Xms256m -Xmx1536m" parameter, change the value of the max heap size of the JVM from 1.5 GB (-Xmx1536m) to 4 GB (-Xmx4096m).
      Hence, change DEFS="-Xms256m -Xmx1536m" to DEFS="-Xms256m -Xmx4096m".

   5. In the CESEMN.PARMLIB file, right after DEFS="$DEFS -Dlog.data.path=${APP_DATA_DIR}/workspace/logs", add the following new parameter:
      JAXBV="org.eclipse.persistence.jaxb.JAXBContextFactory"
      DEFS="$DEFS -Djavax.xml.bind.context.factory=${JAXBV}"
      Refer to the highlighted sections in the sample file snippet to do so.

      #---REQUIRED--- custom CES definitions for the runtime environment
      DEFS="$DEFS -Dosgi.instance.area=${APP_DATA_DIR}/workspace"
      DEFS="$DEFS -DAppDataDir=${APP_DATA_DIR}"
      DEFS="$DEFS -Dlog.data.path=${APP_DATA_DIR}/workspace/logs"
      JAXBV="org.eclipse.persistence.jaxb.JAXBContextFactory"
      DEFS="$DEFS -Djavax.xml.bind.context.factory=${JAXBV}"
      DEFS="$DEFS -Dosgi.parentClassLoader=boot"
      DEFS="$DEFS -Declipse.log.level=INFO"
      DEFS="$DEFS -Dorg.osgi.framework.bootdelegation=*"
      DEFS="$DEFS -Dcom.ibm.jsse2.overrideDefaultTLS=true"

2. Start the CES service by running the CESBATCH job and open CES in a browser. You will be prompted to upgrade your database.

Make sure that:

• The JAVA_HOME environment variable is set to the Java 11 path.
• The Path environment variable is set to JAVA_HOME\bin.

To upgrade via the Update Center or the Installer

1. (If upgrading via Update Center) After initiating the upgrade process, wait for some time and then access CES in a new browser tab to verify that the CES UI loads successfully. If the UI does not load, it means that your Java 11 parameters are not properly configured. 

2. (Recommended) Set the JAVA_HOME variable at the system level, to point to Java 11.

   Warning

   Important

   If you have not set the JAVA_HOME variable at the system level, perform the following steps to set the Java path to Java 11:

   1. Identify the location of Java 11 JDK/JRE.
      For example, Java 11 location path = /usr/lib/jdk11/
   2. Edit the following files and set JAVA_HOME to /usr/lib/jdk11.
      • In the CollectSupportFiles.sh file, modify JAVA_PGM=${JAVA_HOME}/bin/java to JAVA_PGM=/usr/lib/jdk11/bin/java
      • In the execces.sh file, modify JAVA_HOME to JAVA_HOME=/usr/lib/jdk11/
      • In the execcesSystemD.sh file, modify JAVA_HOME to JAVA_HOME=/usr/lib/jdk11/

3. In the execces.sh file, right after ARGS="$ARGS -Dosgi.instance.area=$CESDATA_HOME/workspace", add the following new argument: ARGS="$ARGS -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory"
   Refer to the highlighted sections in the sample file snippet to do so.

   {
   #---------------------------------#
   # dynamically build the classpath #
   #---------------------------------#
   LOCALCLASSPATH=

     case $CMD in
       start)
           ARGS="$ARGS -Djava.awt.headless=true"
           ARGS="$ARGS -Dosgi.instance.area=$CESDATA_HOME/workspace"
           ARGS="$ARGS -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory"
           ARGS="$ARGS -DAppDataDir=$CESDATA_HOME"
           ARGS="$ARGS -Dlog.data.path=$CESDATA_HOME/workspace/logs"
           ARGS="$ARGS -Dosgi.parentClassLoader=boot"
           ARGS="$ARGS -Declipse.log.level=INFO"
           ARGS="$ARGS -Dorg.osgi.framework.bootdelegation=*"
           ARGS="$ARGS -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.StandardParserConfiguration"
           export ARGS
           su $CES_USER -c 'nohup java $ARGS -jar $CES_HOME/plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar -noRegistryCache -clean -application com.compuware.webapps.application &'
           ;;
       stop)
           ARGS="$ARGS -DAppDataDir=$CESDATA_HOME"
           export ARGS
           su $CES_USER -c '          java $ARGS -cp "$CES_HOME/plugins/*" ${ARGS} com.compuware.Compuware.util.ShutCES $PORTNUM'
           ;;
     esac
   }

   execCES()
   {
       ARGS="$ARGS -Djava.awt.headless=true"
       ARGS="$ARGS -Dosgi.instance.area=$CESDATA_HOME/workspace"
       ARGS="$ARGS -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory"
       ARGS="$ARGS -DAppDataDir=$CESDATA_HOME"
       ARGS="$ARGS -Dlog.data.path=$CESDATA_HOME/workspace/logs"
       ARGS="$ARGS -Dosgi.parentClassLoader=boot"
       ARGS="$ARGS -Declipse.log.level=INFO"
       export ARGS        
       su $CES_USER -c 'nohup java $ARGS -jar $CES_HOME/plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar -noRegistryCache -clean -application com.compuware.webapps.application >>$CESDATA_HOME/ces/logs/$CMD.log  2>&1 &' 
   }

   CMD=$1
   export CMD

4. In the execcesSystemD.sh file, right after ARGS="$ARGS -Dosgi.instance.area=$CESDATA_HOME/workspace", add the following new argument: ARGS="$ARGS -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory"
5. Restart the CES server and refresh your browser.

After you complete the CES installation process, perform the following steps:

1. In the execcesSystemD.sh file, right after ARGS="$ARGS -Dosgi.instance.area=$CESDATA_HOME/workspace", add the following new argument: ARGS="$ARGS -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory"
2. Restart the CES server and refresh your browser.

Database configuration for Db2

For more information, see Planning.

The upgrade to CES version 23.01.01 for z/OS Db2 includes an ALTER TABLE with a CLOB column. The z/OS Db2 upgrade script does not have the SET CURRENT RULES='STD' command. Because of this, the Webhooks UI in CES does not display as expected.

If your Db2 subsystem uses SET CURRENT RULES='DB2', perform the following additional steps:

• If you have not upgraded the database:
  1. Download the DDL file from the Database settings page in CES.
  2. Insert SET CURRENT RULES='STD'; before the ALTER TABLE statement for the CES_API_NOTIFICATIONS table with a CLOB column.
  3. Save the DDL and run it. 
     The AUX tablespace, table, and index are created for the new CLOB column.
• If you have already upgraded the database with the SET CURRENT RULES='DB2' command:
  1. You must get additional Create statements to complete the database upgrade. Refer to the following script and modify the highlighted text to suit your environment.
     • In <CustomerTablespace>, specify a new name for the tablespace.
     • In <CustomerDatabase>, specify your existing database name.
     • In <CustomerSchema>, specify your existing schema name.

     • In <8KBufferPoolName> and <4KBufferPoolName>, specify the bufferpool based on your database configuration.

       SET CURRENT RULES='STD';

       
       

       CREATE LOB TABLESPACE "<CustomerTablespace>" IN "<CustomerDatabase>"
       BUFFERPOOL <8KBufferPoolName>
       LOCKSIZE ANYCLOSE NO LOG NO ;

       
       

       CREATE AUXILIARY TABLE "<CustomerSchema>"."CES_ACSRF_02826900"
       IN "<CustomerDatabase>"."<CustomerTablespace>"
       STORES "<CustomerSchema>"."CES_API_NOTIFICATIONS"
       COLUMN "CSRF_BODY" PART 1;

       
       

       CREATE UNIQUE INDEX "<CustomerSchema>"."ICES_ACSRF_2826900"
       ON "<CustomerSchema>"."CES_ACSRF_02826900"
       FREEPAGE 0 PCTFREE 10GBPCACHE NONEBUFFERPOOL <4KBufferPoolName>
       COPY NOCLOSE NO;

  2. Save the DDL and run it.