Skip to Content

How to update JRE/JDK for Tomcat7 on BI 4.1.x Platform

The high-level steps required:

  • Stop SIA & Tomcat
  • Check JDK/JRE version being used prior to upgrade
  • Install jdk-7u67-windows-x64.exe in simple and short path like c:\jdk
  • Installed the JRE option in path c:\jdk\jre
  • Update Tomcat JAVA settings to point to new path
  • Created Windows Parameters
    • JRE_HOME   point to  c:\jdk
    • JAVA_HOME  point to c:\jdk
  • Restart Windows and check JDK/JRE version
  • Restart Tomcat only
  • Validate Tomcat works fine then start SIA

Step 1: Stop SIA & Tomcat

Launch Central Configuration Manager and STOP SIA & Tomcat

BI41x_JDK_Update_00.png

Step 2: Stop SIA & Tomcat

Check current version on JDK/JRE being used by Tomcat

C:\SAP BusinessObjects\Tomcat\bin>version

Using CATALINA_BASE:   “C:\SAP BusinessObjects\tomcat”

Using CATALINA_HOME:   “C:\SAP BusinessObjects\tomcat”

Using CATALINA_TMPDIR: “C:\SAP BusinessObjects\tomcat\temp”

Using JRE_HOME:        “C:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\”

Using CLASSPATH:       “C:\SAP BusinessObjects\tomcat\bin\bootstrap.jar;C:\SAP BusinessObjects\tomcat\bin\tomcat-juli.jar”

Server version: Apache Tomcat/7.0.32

Server built:   Oct 3 2012 08:51:20

Server number:  7.0.32.0

OS Name:        Windows Server 2008 R2

OS Version:     6.1

Architecture:   amd64

JVM Version:    6.1.058

JVM Vendor:     SAP AG

C:\SAP BusinessObjects\tomcat\bin>

  BI41x_JDK_Update_02_BI414.png

  

Step 3: Install jdk-7u67-windows-x64.exe

Install JDK-7u67-widnows-x64.exe and do CUSTOM install

  BI41x_JDK_Update_05.png

Change JDK path to c:\jdk

  BI41x_JDK_Update_07.png

BI41x_JDK_Update_09.png

   
   Change JRE path to c:\jdk\jre

BI41x_JDK_Update_10.png

BI41x_JDK_Update_12.png

Step 4: Update Tomcat Java Path

Update Tomcat Java path

BEFORE:

Java Virtual Machine:

c:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\\jre\bin\server\jvm.dll

Java Classpath:

c:\SAP BusinessObjects\tomcat\bin\bootstrap.jar;c:\SAP BusinessObjects\tomcat\bin\tomcat-juli.jar;c:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\lib\tools.jar

  BI41x_JDK_Update_03.png

   

AFTER:

Java Virtual Machine:

C:\jdk\jre\bin\server\jvm.dll

Java Classpath:

c:\SAP BusinessObjects\tomcat\bin\bootstrap.jar;c:\SAP BusinessObjects\tomcat\bin\tomcat-juli.jar;C:\jdk\lib\tools.jar

  BI41x_JDK_Update_16.png

Step 5: Create Windows System Variables

Create NEW Windows System Variables

JAVA_HOME c:\jdk

JRE_HOME   c:\jdk

  BI41x_JDK_Update_15.png

RESTART WINDOWS for new System Variables to take effect.

Step 6: Restart Tomcat and check version

After restarting Windows and start TOMCAT only !!

  • Check Tomcat version

C:\SAP BusinessObjects\Tomcat\bin>version

Using CATALINA_BASE:   “C:\SAP BusinessObjects\tomcat”

Using CATALINA_HOME:   “C:\SAP BusinessObjects\tomcat”

Using CATALINA_TMPDIR: “C:\SAP BusinessObjects\tomcat\temp”

Using JRE_HOME:        “c:\jdk”

Using CLASSPATH:       “C:\SAP BusinessObjects\tomcat\bin\bootstrap.jar;C:\SAP BusinessObjects\tomcat\bin\tomcat-juli.jar”

Server version: Apache Tomcat/7.0.32

Server built:   Oct 3 2012 08:51:20

Server number:  7.0.32.0

OS Name:        Windows Server 2008 R2

OS Version:     6.1

Architecture:   amd64

JVM Version:    1.7.0_67-b01

JVM Vendor:     Oracle Corporation

C:\SAP BusinessObjects\tomcat\bin>

  BI41x_JDK_Update_18.png

  • Now that Tomcat is fully working
  • Start SIA
13 Comments
You must be Logged on to comment or reply to a post.
  • Thanks for sharing this article. Could the Apache Tomcat 7 stop unexpectedly by not upgrading the JRE/JVM? I am running into this issue and have not updated it yet.

    Please let me know what are the prons and cons of performing these steps.

    Thanks,

    Rene

  • The title is misleading, you’re not upgrading JRE/JRK for BI Platform, you’re changing JVM used by Tomcat.
    That’s it.
    This is generic and not part of BI Platform.

    JVM used by BI Platform is updated via BI Platform maintenance (patching)

  • Hi Ajay,

    Thanks for sharing.

    Some questions:

    – Why did you choose the Oracle JDK/JRE 7 and not the SAPJVM 7?

      By default Tomcat is using a SAPJVM, as the BIP does.

      Do you see any advantages/disadvantages/possible issues by using one or the other?

    – How often do you recommend to update the Tomcat JVM?

      Install every update release? Update it when updating the BIP to minimize testing?

      Only if it contains critical security fixes (which is true for the most cases…)?

      Other ideas?

    – We’ve updated the Tomcat JVM to SAPJVM 7, but we didn’t set the system variables
      JAVA_HOME and JRE_HOME, because it caused issues with some self-developed java
      programs running on our BIP.

      Do you see any problems in this case?

      The only thing which is a bit strange is that I see Tomcat is using SAPJVM 7 (7.1.019)
      when checking the Server status via the browser, but the ..\tomcat\bin\version
      command tells it’s still using JVM 6.1.044 (which is the default SAPJVM delivered with the
      BIP installation).

      And it tells JRE_HOME is set to

      “D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\”

      even if the system variable is not set, as stated above and the Java Virtual Machine path
      in the Tomcat Administration GUI (tomcat7w.exe) is set correctly to use the SAPJVM 7.

      Which info is correct?

    Krgds

    Moritz

    • Moritz,

         You answers below:

      1. Java & MySQL was originally owned by SUN Systems but then got bought out by Oracle.  Oracle now owner of ALL JAVA, SAP is creating an OEM version.  Also keep in mind that Tomcat is owned by Jakarta but SAP update an OEM version to be used by BOBJ.

      2. Updates depends on security issue being advised at the SUN Java site (see links below).

      Java Security Resource Center

      Critical Patch Updates and Security Alerts

      3. If you DO NOT update &/or add the system variables, Tomcat running at command level does level still uses OLD path until system variables has been updated.  Updating the system variables DOES NOT effect BOBJ Platform.  BOBJ JRE/JVM is updated by installing BOBJ Service packs.

      Regards,

      Ajay

      • Hi Ajay,

        Thanks for your reply.

        1. This was not the answer to my question 🙂

        2. OK, so as far as I understand, you do updates based on security issues only.

        3. I just checked our running tomcat7.exe with Process Explorer and it uses the JVM given in the Tomcat admin tool.

        For me this is command line level?! Or what do you mean exactly?

        Therefore it’s still not clear for me for which scenario this could cause problems and why I have different results when checking the Server Status via the Tomcat Manager webapp or using the Tomcat version command.

        Yes, the system variables don’t affect the BIP itself, but as stated before, custom coded java programs running on the BIP, which is reproducable (true for JAVA_HOME only).

        Wouldn’t it be enough to just set JRE_HOME in our case?

        I’ve not seen that Tomcat is using JAVA_HOME anywhere.

        Yes, I know that it’s not allowed to change the BIP JVM manually and that this is updated by the SPs…

        Krgds

        Moritz

        • Mortitz,

          1. I put the original JAVA instead of an OEM version.

          3. If update as suggest you will find the JAVA at command prompt will be the same version within Tomcat Manager.   You need to set TWO environment variables JAVA_HOME / JRE_HOME.  See screen-shots above.

          If you have any further problems, I suggest you create SAP support message

          Regards,

          Ajay

  • Is there any added advantage to performance by this?

     

    Also, i rtried it on our sandbox, after changing Java kerberos sso is not longer working, the log says invalid license