Installing a new instance of Endevor Webservices 18.0.12 but the script ENWSIns.sh failed.
Release : 18.0
Component : CA Endevor Software Change Manager
The client had few errors in the configuration that were addressed before the problem reported was solved:
1 - The client was running under Java version 7 and Tomcat version 7, which are unsupported.
2 - The client specified CCSDPDIR as the target Tomcat directory with CLEAN_ENDEVOR_TOMCAT_INSTANCE as Y, which was erasing where the job was placed.
3 - The default and maximum memory of the Java Virtual Machine (JVM) that the client has in his systems was not enough to perform the instruction: $JAVA_HOME/bin/java -jar "$ENDEVOR_SOFTWARE_DIR/tpv/Validate.jar" -c "$ENDEVOR_SOFTWARE_DIR/tpv/tomcat/webapps/EndevorService.war.md5", which runs the md5 file from Validate.jar in the JVM and check for the ENWSWAR file in the same directory. This code validates that the Installation has been performed successfully and without problems.
1 - Check that the Java version is 8 or higher and Tomcat is 8.5.32 or higher. The version the client is using in the ENWSInstallOptions.properties file.
2 - Check that SET CCSDPDIR in the WSTOMCCS job points to a different path than the target library if CLEAN_ENDEVOR_TOMCAT_INSTANCE is set as Y.
3- Increase the maximum memory used for the JVM. Use of command java -Xms -Xmx, which specifies the default memory and the maximum memory for JVM respectively. In this particular case java -Xms64m -Xmx256m was used where -Xms64m is 64MB and -Xmx256m is 256MB. The default memory of the JVM can be checked in UNIX using the command java -XshowSettings:vm. The client fixed the issue by specifying $JAVA_HOME/bin/java -Xms64m -Xmx256m -jar "$ENDEVOR_SOFTWARE_DIR/tpv/Validate.jar" -c "$ENDEVOR_DEPLOY_TOMCAT/webapps/EndevorService.war.md5"