Skip to main content

Automated remote deployment of Webcenter ear to our development enviroment



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
  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

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

ADF odd error : ADFC-10001: cannot instantiate class

Running one of my adf pages with some code in the construtor O got the following error: JspServlet error: Servlet unable to dispatch to the following requested page: The following exception occurred:javax.faces.FacesException: javax.faces.FacesException: oracle.adf.controller.ControllerException: ADFC-10001: cannot instantiate class 'za.co.test.adf.ops.view.common.form.TestBean' I was adding a partial target to my page in the constructor which is a no no - remove the line AdfFacesContext.getCurrentInstance().addPartialTarget(getResultTable()); and all was well again. Note: this can also be caused by any error in the bean constructor.