Page History

...

The jar file to use is present in two forms (http://archiva.sos:8080/archiva/repository/sos/com/sos-berlin/sos-commons-cli/2.0.0-SNAPSHOT/)forms 

• sos-commons-cli-2-0-0-SNAPSHOT.jar
  • this is a standard jar file 
  • using this jar needs to get the complete classpath set from the outside 
• sos-commons-cli-2-0-0-SNAPSHOT-jar-with-dependencies.jar
  • this is a fat/uber jar file
  • using this jar needs no classpath at all

The filename of the jar file should be changed through the setup, so that customers will later only have to call sos-commons-cli.jar or a different desired name in either way (external classpath in agent, without classpath in the controller)

For testing purpose the jar files are internally available in archiva http://archiva.sos:8080/archiva/repository/sos/com/sos-berlin/sos-commons-cli/2.0.0-SNAPSHOT/ . The files in archiva have an additional timestamp and a build id in their filenames.

java -jar sos-commons-cli.jar com.sos.cli.ExecuteRollOut --token=73bfc4b8-3f15-44b9-a75b-cdb44aec8f4b --joc-uri=http://sp.sos:3333 --san="sp.sos, sp" --subject-dn="CN=sp, OU=development, O=SOS, C=DE, L=Berlin, S=Berlin" --target-keystore=C:/sp/devel/js7/testing/CLI/controller/withHTTP/https-keystore.p12 --target-keystore-type=PKCS12 --target-keystore-pass=jobscheduler --target-keystore-entry-pass=jobscheduler --target-truststore=C:/sp/devel/js7/testing/CLI/controller/withHTTP/https-truststore.p12 --target-truststore-type=PKCS12 --target-truststore-pass=jobscheduler --key-alias=sp --ca-alias="sp root ca"

...