All the usual undeploy / stop start code worked remotely but unfortunately the deploy was not going as planned - I wanted to set the MDS info on deployment so it was time for a new plan.
So this time on our build server would call WLST to deploy our web center app on the development weblogic enviroment.
Wlst commands I used:
Connect
connect('weblogic','bobsentme', ''t3://remote.wl:7001')
Stop
shutdown('ManagedServer1', force='true')
Start
start(start('WC_Cluster', 'Cluster', 't3://remote.wl:7001'));
Deploy
archive = getMDSArchiveConfig(fromLocation='/tmp/pathto.ear')
archive.setAppMetadataRepository(repository='mds-CustomDS', partition='dev_partition', type='DB', jndi='jdbc/mds/CustomDS')");
archive.save()
deploy(appName='OurAppName', path='/tmp/pathto.ear', targets='WC_Cluster', stageMode='stage', upload='true')
undeploy('OurAppName')
Disconnect
disconnect('true')
Scripts: to get the classpath and environment variables correct I run the wlst.sh command and echo'ed the classpath and JAVA_OPTS and pulled them into my file not elegant but it did work.
Things still to do:
- Use a secure connection t3s
- Move from script to use wlst directly
- Call setWLenv or something to setup the classpath and java opts for me
Something like:
/opt/Oracle/Middleware/wlserver_10.3/server/bin/setWLSEnv.sh
/opt/Oracle/Middleware/oracle_common/common/bin/setHomeDirs.sh
/opt/Oracle/Middleware/oracle_common/common/bin/setWlstEnv.sh
Comments
Post a Comment