Java Errors when using the Test Connection feature in Primavera P6 Administrator

28

Jul 2016

Java Errors when using the Test Connection feature in Primavera P6 Administrator

Issue:
Java Errors when using the Test Connection feature in Primavera P6 Administrator while testing connection from Directory Services or Database Eventing (Primavera Deployed on Weblogic)
Sample Screenshots of errors:
b511


Resolution:

While Configuring Directory Services for Database Eventing, most likely you want to test the connection using the “Test Connection” feature in the P6 Administrator Thick client (Right click and select Test Connection).  Oracle Documentation is pretty clear in terms of how to configure the Directory Services and Eventing but they simply forgot to mention that if we need to use the Test Connection feature in the P6 Administrator we need to copy the wlfullclient.jar in to $PRIMAVERA_HOME/lib directory and update the CLASSPATH in adminpv.sh or adminpv.cmd file.

 

If you already have a wlfullclient.jar in any other environments running on the same version of weblogic, you can copy it otherwise follow the below instructions to generate your own wlfullclient.jar and then copy it to the $PRIMAVERA_HOME/lib directory

 

Steps to generate the wlfullclient.jar  (Oracle Documentation)

 

Use the following steps to create a wlfullclient.jar file for a client application:

  1. Change directories to the server/lib directory.

cd WL_HOME/server/lib

  1. Use the following command to create wlfullclient.jar in theserver/lib directory:

java -jar ../../../modules/com.bea.core.jarbuilder_X.X.X.X.jar

where X.X.X.X is the version number of the jarbuilder module in the WL_HOME/server/lib directory. For example:

java -jar ../../../modules/com.bea.core.jarbuilder_1.0.1.0.jar

  1. You can now copy and bundle the wlfullclient.jar with client applications
  2. Add the wlfullclient.jar to the client application’s classpath.

After you generate the wlfullclient.jar, copy it to the $PRIMAVERA_HOME/lib directory and update the classpath to include the jar.

 

Your updated classpath should like below

“%JAVA_COMMAND%\java” -classpath “%PVLIBDIR%/prm-console.jar;%PVLIBDIR%/prm-bpm-common.jar;%PVLIBDIR%/prm-common.jar;%PVLIBDIR%/resource_strings.jar;%PVLIBDIR%/prm-infr.jar;%PVLIBDIR%/prm-bo-admin.jar;%PVLIBDIR%/prm-initializer.jar;%PVLIBDIR%/ojdbc6.jar;%PVLIBDIR%/spring.jar;%PVLIBDIR%/sqljdbc.jar;%PVLIBDIR%/xml-apis.jar;%PVLIBDIR%/xercesImpl.jar;%PVLIBDIR%/xalan.jar;%PVLIBDIR%/serializer.jar;%PVLIBDIR%/commons-logging.jar;%PVLIBDIR%/log4j.jar;%PVLIBDIR%/mail.jar;%PVLIBDIR%/jide-common.jar;%PVLIBDIR%/jide-grids.jar;%PVLIBDIR%/prm-enm.jar;%PVLIBDIR%/wlfullclient.jar” -Dadmin.workingDir=”%PV_HOME%” -Dadmin.console=”n” %PRIMAVISION_OPTS% com.primavera.admintool.AdminApp

 

After the Copy, the Test Connection Feature should work fine and you should see the below screens.

b512

References:

http://docs.oracle.com/cd/E17266_01/English/Technical_Documentation/Event_Handling/Using%20Events%20with%20P6.pdf

http://docs.oracle.com/cd/E11035_01/wls100/client/jarbuilder.html

Post Your Thoughts

Your email address will not be published. Required fields are marked *