VERIFIED SOLUTION i
X

Requirements for Vault 6.1 Java ServiceWeb2

UPDATED: September 18, 2017


What versions of Tomcat and Java JRE can be used with the 6.1m0p120 version of Vault Java Client ServiceWeb2?


For 6.1 SW2, we tested on TOMCAT 6 + JRE5.  (this is what the documentation states as the requirements)
 
But Engineering thinks it should be OK under JRE6 or JRE7.
 
This is because SW2 is using Vault Java API (e2Vault.jar), and servlet libs.
 
for e2Vault.jar is using basic Java net lib, so it should be OK for any JRE 5 or later versions.
 
For servlet, we supply servlet lib, you can use ENDORSED solution to use the servlet lib.
 
 
 
please see below the notes of ServiceWeb2-Deployment.txt under docs\ when you get the package of SW2 :
 
 
######################################################
#the files included in distribution packages
 
1. j2ee_libs.jar is including below libs:
javaee-api-5.jar
servlet-api-2.4.jar
 
2. log4j-1.2.16.jar is for logging lib used in ServiceWeb2
 
3. ServiceWeb2.war is the war file can be deployed in a web-server.
 
 
 
######################################################
#TOMCAT deployment
 
1. remove the old ServiceWeb2.war and related files:
<TOMCAT>\conf\Catalina\localhost\ServiceWeb2.xml
<TOMCAT>\work\Catalina\localhost\ServiceWeb2\
<TOMCAT>\webapps\ServiceWeb2\
<TOMCAT>\webapps\ServiceWeb2.war
 
2. other libs
ServiceWeb2.war is already including log4j-1.2.16.jar.
sometime, <TOMCAT> is includng different j2ee API libs. 
If this is the case and ServiceWeb2 isn't compatible with the j2ee API libs inside TOMCAT, 
please unzip j2ee_libs.jar (jar -xvf j2ee_libs.jar), and copy to <TOMCAT>\endorsed\.
If there is no dir named <TOMCAT>\endorsed, please create one first,
and then copy the files.
 
3. copy the newest ServiceWeb2.war to <TOMCAT>\webapps\
or you can use the TOMCAT administrator manager to deploy ServiceWeb2.war
 
4. start TOMCAT : <TOMCAT>\bin\startup.bat
 
 
######################################################
#JBoss deployment
 
1. remove the old ServiceWeb2.war and related files.
 
2. copy ServiceWeb2.war to <JBOSS 4>\server\default\deploy\
or copy ServiceWeb2.war to <JBOSS 5>\server\default\deploy\
or copy ServiceWeb2.war to <BOSS 7>\standalone\deployments\
or you can JBOSS administrator manager to deploy ServiceWeb2.war
 
3. start JBOSS : <JBOSS>\bin\run.bat
 
 
 
######################################################
# test for log4j lib under different web-servers
#
 
web-server <======> SW2.war with log4j, can-work <==========> SW2.war no log4j, can-work
 
TOMCAT-6.0.23 <==========> loading OK, YES <==========> endorsed\log4j-1.2.16.jar, YES
TOMCAT-7.0.12 <==========> loading OK, YES <==========> endorsed\log4j-1.2.16.jar, YES
TOMCAT-7.0.40 <==========> loading OK, YES <==========> endorsed\log4j-1.2.16.jar, YES
 
JBOSS-4.2.1 <==========> loading errors, YES <==========> no need to copy, YES
JBOSS-5.1.0 <==========> loading error, YES <==========> no need to copy, YES
JBOSS-7.0.2 <==========> loading OK, YES <==========> endorsed\log4j-1.2.16.jar, YES
JBOSS-7.1.1 <==========> loading OK, YEs <==========> endorsed\log4j-1.2.16.jar, YES
 
Websphere 8.5 <==========> loading OK, YES <==========> java\jre\lib\endorsed\log4j-1.2.16.jar , YES 

Downloads

  • No Downloads