Smarts NCM: Error running runCmd.sh : ERROR [com.powerup.configmgr.util.commandline.CommandController] com/emc/clb/clbBridge/JavaAMSCallbackInterface java.lang.NoClassDefFoundError: com/emc/clb/clbBridge/JavaAMSCallbackInterface
Article ID: 330973
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
Cannot run runCmd.sh i.e. upon execution of any command under this framework an error is received and the script fails eg:
The script cannot find the class JavaAMSCallbackInterface
Cannot run runCmd.sh i.e. upon execution of any command under this framework an error is received and the script fails eg:
cmd > exportCredentials global
Error:com/emc/clb/clbBridge/JavaAMSCallbackInterface
The script cannot find the class JavaAMSCallbackInterface
Environment
VMware Smart Assurance - NCM
Cause
The JavaAMSCallbackInterface class is missing from the jar files in the Class Path.
In this example, the jar file that contains the JavaAMSCallbackInterface class is called LBINI.jar
In this example, the jar file that contains the JavaAMSCallbackInterface class is called LBINI.jar
Resolution
Edit the runCmd.sh file:
>vi tools/bulk-import/runCmd.sh
Go to the classpath to see how it is defined: (refer to screenshot also)
java -classpath $CLASSPATH $LIBRARY_PATH $LOGIN_OPTION $JNDI_OPTION $MAIN_CLASS $USER $PASS
It references the variable CLASSPATH.
Here we have CLASSPATH defined as follows:
In here we see that the jars are defined in the $APPSERVER_JARS variable. It is here we will add the new jar file:
Changing:
>vi tools/bulk-import/runCmd.sh
Go to the classpath to see how it is defined: (refer to screenshot also)
java -classpath $CLASSPATH $LIBRARY_PATH $LOGIN_OPTION $JNDI_OPTION $MAIN_CLASS $USER $PASS
It references the variable CLASSPATH.
Here we have CLASSPATH defined as follows:
CLASSPATH="$VOYENCE_HOME/tools/bulk-import:$VOYENCE_HOME/tools/bulk-import/CommandLineUtil.jar:$APPSERVER_JARS:$CONTROLDAEMON_JARS:$JBOSS_CLIENT_JARS:."
In here we see that the jars are defined in the $APPSERVER_JARS variable. It is here we will add the new jar file:
Changing:
APPSERVER_JARS="$APP_SERVER_DIR/deploy/1vc.sar/VoyenceControlServer.jar:$APP_SERVER_DIR/deploy/1vc.sar/vc-security-jmx.sar:$APP_SERVER_DIR/lib/postgresql-8.2-504.jdbc3.jar:$APP_SERVER_DIR/deploy/1vc.sar/LB.jar:$APP_SERVER_DIR/deploy/1vc.sar/LBImpl.jar"
to
to
APPSERVER_JARS="$APP_SERVER_DIR/deploy/1vc.sar/VoyenceControlServer.jar:$APP_SERVER_DIR/deploy/1vc.sar/vc-security-jmx.sar:$APP_SERVER_DIR/lib/postgresql-8.2-504.jdbc3.jar:$APP_SERVER_DIR/deploy/1vc.sar/LB.jar:$APP_SERVER_DIR/deploy/1vc.sar/LBImpl.jar:$APP_SERVER_DIR/deploy/1vc.sar/LBJNI.jar"
Save and close the runCmd.sh
Please note to make sure there is a copy of the LBJNI.jar file $APP_SERVER_DIR/deploy/1vc.sar before running the script.
If you cannot locate a copy of this jar file, please contact Customer Support
Save and close the runCmd.sh
Please note to make sure there is a copy of the LBJNI.jar file $APP_SERVER_DIR/deploy/1vc.sar before running the script.
If you cannot locate a copy of this jar file, please contact Customer Support
Additional Information
Please note to make sure there is a copy of the LBJNI.jar file $APP_SERVER_DIR/deploy/1vc.sar before running the script.
If you cannot locate a copy of this jar file, please contact Customer Support
If you cannot locate a copy of this jar file, please contact Customer Support
Feedback
Yes
No
Powered by
