A run script could look like this....
#!/bin/sh
java -Xmx1536m -classpath \
jars/rapiddeploy- orchestration.jar:\
jars/rapiddeploy-remoting- jsch.jar:\
jars/rapiddeploy-core-plugins- prd-ibm-websphere7.jar:\
jars/rapiddeploy-core-plugins- prd-ibm-websphere85.jar:\
jars/rapiddeploy-core-plugins- tools-maven.jar:\
jars/rapiddeploy-remoting- remoting.jar:\
jars/rapiddeploy-core-plugins- prd-ibm-websphere8.jar:\
jars/rapiddeploy-ext-wmq-jar. jar \
com/midvision/rapiddeploy/ domain/task/core/DefaultBatch \
definition=mv-rapiddeploy- orchestration.xml \
log4j=log4j.properties \
name=RD-TEST \
server=10.1.1.20 \
environment=autowas \
instance= RapidDeployTestInstance \
application=my_application \
deployFile=tars/rd-test.tar \
taskflowLock=rd-test.lock
Structure of the RD runtime
/home/autowas/rapid-deploy
builds/ This is where RD unpacks the tar
jars/ The RD runtime jars
mv-rapiddeploy-orchestration. xml The main orchestration file
run-rd.sh* A script to invoke RD (example above)
tars/ Where I placed my custom tar (structure below)
unpack/ Where I unpack the tar to manipulate contents during test
Structure RD expects in a tar
db_libs/
_Documentation
install.dat
integrators.txt
j2ee/ This is where all the "deployment" files live
jenkinsbuild.log
lib/
log4j.properties
midvision-deploy- orchestration.xml
midvision-jee-deploy- orchestration.xml The main sub orchestration file
mv-rapiddeploy-orchestration. xml Not sure why this is duplicated here
scripts/
SharedLibraries/
url_libs/
No comments:
Post a Comment