Switching from IBM JDK to Oracle JDK for Vibe 4 in SLES

Vibe 4.x.x can be installed with IBM JDK 8 or with Oracle JDK 8. If you want to use a SSL connection between your Micro Focus Vibe site and a WebDAV server, and if the WebDAV server has a self-signed certificate rather than a certificate provided by a certificate authority, you must use the Oracle JDK. The existing Vibe functionality for handling self-signed certificates is not compatible with the way the IBM JDK handles self-signed certificates. We recommend that you use the Oracle JDK with your Vibe install.

If you have already installed Vibe with the IBM JDK and you now wish to switch to the recommended Oracle JDK, please follow the steps below. Please refer to the Vibe 4 installation documentation for steps on how to install Vibe 4 and Java.

Note: Vibe requires a Java Development Kit (JDK), not a Java Runtime Environment (JRE), in order to run properly. See here for system requirements of Vibe 4.

For the purpose of this TID we are assuming the following locations for Vibe 4 and the JDKs. Please change locations according to your system installations.

Vibe application location: /opt/novell/teaming
Vibe installer location: /vibeinstaller/vibe403
Oracle JDK location: /vibejdk/jdk8oracle/jdk1.8.0_161
IBM JDK location: /vibejdk/jdk18ibm/ibm-java-x86_64-80


1.  Stop Vibe
/etc/init.d/teaming stop

2.  Run Vibe Installer
cd /vibeinstaller/vibe403
./installer-teaming.linux

Choose option "3. Reconfigure settings" when prompted after accepting the license.
Continue through the prompts until you reach:
Path to JDK version 1.8.0 or higher [/vibejdk/jdk18ibm/ibm-java-x86_64-80]:

Enter your Oracle JDK location here
/vibejdk/jdk8oracle/jdk1.8.0_161

Continue through the rest of the prompts and apply changes.

3.  Now edit file /opt/novell/teaming/apache-tomcat/conf/server.xml

Look for section that starts like:

<Connector port="8443" ...... ciphers="HIGH:!3DES:!EXP:!aNULL:!MD5" algorithm="IbmX509"/>

Remove element algorithm="IbmX509" so it becomes like
<Connector port="8443" ...... ciphers="HIGH:!3DES:!EXP:!aNULL:!MD5"/>

Save and exit.

4.  Start Vibe
/etc/init.d/teaming start

If after starting Vibe you are unable to access it in the browser and an error appears in appserver.log or catalina.out file which looks like

21-Mar-2018 13:23:14.146 SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler ["http-nio2-8443"]
 java.security.NoSuchAlgorithmException: IbmX509 KeyManagerFactory not available
        at sun.security.jca.GetInstance.getInstance(GetInstance.java:159)
        at javax.net.ssl.KeyManagerFactory.getInstance(KeyManagerFactory.java:137)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:612)
        at org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:546)
        at org.apache.tomcat.util.net.Nio2Endpoint.bind(Nio2Endpoint.java:313)

Please recheck and ensure that server.xml file was correctly edited as shown in step 3 above and Vibe was restarted.