RepoInstance is not selected properly.

Hi ,

the configuration (.xml) file created using tibant tool is not the same as the configuration file generated using appmange tool. Please find the two files attached (GSI.xml generated through appmange, GSI-dev.xml generated through TIBAnt ). Also we are getting the error when we try to deploy through TIBAnt where as the same ear file is deployed properly through tibco administrator GUI. Error message shown below:

2011 Dec 29 19:41:50:512 GMT -8 Error [ApplicationConfiguration] AESDKJ-0000 [main] com.tibco.infra.repository.OperationFailedException: Can not find server to connect
     at com.tibco.pof.admindomain.impl.BwServerDeploymentPlugIn.createRepoClientOnRemoteRepoInstance(BwServerDeploymentPlugIn.java:857)
     at com.tibco.pof.admindomain.impl.BwServerDeploymentPlugIn.onDeploy(BwServerDeploymentPlugIn.java:477)
     at com.tibco.pof.admindomain.impl.ApplicationConfigurationImpl.a(ApplicationConfigurationImpl.java:1002)
     at com.tibco.pof.admindomain.impl.ApplicationConfigurationImpl.a(ApplicationConfigurationImpl.java:753)
     at com.tibco.pof.admindomain.impl.ApplicationConfigurationImpl.deploy(ApplicationConfigurationImpl.java:592)
     at com.tibco.pof.admindomain.impl.ApplicationConfigurationImpl.deploy(ApplicationConfigurationImpl.java:573)
     at com.tibco.administrator.command.data.application.Application.deploy(Application.java:832)
     at com.tibco.administrator.command.tool.ApplicationManagement.if(ApplicationManagement.java:551)
     at com.tibco.administrator.command.tool.ApplicationManagement.action(ApplicationManagement.java:452)
     at com.tibco.administrator.command.tool.ApplicationManagement.a(ApplicationManagement.java:305)
     at com.tibco.administrator.command.tool.ApplicationManagement.loopThroughBatchTask(ApplicationManagement.java:296)
     at com.tibco.administrator.command.tool.ApplicationManagement.task(ApplicationManagement.java:203)
     at com.tibco.administrator.command.tool.ApplicationManagement.main(ApplicationManagement.java:157)

2011 Dec 29 19:42:36:263 GMT -8 Error [com.tibco.administrator.command.data.application.Application] AESDKJ-0000 [main] Deployed status is Server plugin failed
2011 Dec 29 19:42:36:263 GMT -8 Error [com.tibco.administrator.command.data.application.Application] AESDKJ-0000 [main] Name=STGWREPO1 Action=Call TIBCO Hawk Agent (STGW) Status=Success
2011 Dec 29 19:42:36:279 GMT -8 Error [com.tibco.administrator.command.data.application.Application] AESDKJ-0000 [main] Name=GSI-A1 Action=Deploy Engine on Client Status=com.tibco.infra.repository.OperationFailedException: Repository instance STGW-GSI is not found
     at com.tibco.infra.repository.RepoFactory.newClient(RepoFactory.java:3262)
     at com.tibco.infra.repository.RepoFactory.newClient(RepoFactory.java:3153)
     at com.tibco.tra.tsm.plugin.TSMComponentDeploy.testRepoUrlConnection(TSMComponentDeploy.java:1912)
     at com.tibco.tra.tsm.plugin.TSMEngineDeploy.addRepourlProperties(TSMEngineDeploy.java:120)
     at com.tibco.tra.tsm.plugin.TSMEngineDeploy.createTra(TSMEngineDeploy.java:85)
     at com.tibco.tra.tsm.plugin.TSMBwEngineDeploy.createTra(TSMBwEngineDeploy.java:62)
     at com.tibco.tra.tsm.plugin.TSMBwEngineDeploy.beginAction(TSMBwEngineDeploy.java:38)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.beginPerformAction(MutableAdminDomainImpl.java:788)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.deploy(MutableAdminDomainImpl.java:689)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.deployListInternal(MutableAdminDomainImpl.java:917)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.deployOnClient(MutableAdminDomainImpl.java:849)
     at com.tibco.tra.tsm.TSM.deploy(TSM.java:2802)
     at com.tibco.tra.tsm.TSM$1.run(TSM.java:3169)
     at java.lang.Thread.run(Thread.java:662)

2011 Dec 29 19:42:36:279 GMT -8 Error [com.tibco.administrator.command.data.application.Application] AESDKJ-0000 [main] Name=GSI-A2 Action=Deploy Engine on Client Status=com.tibco.infra.repository.OperationFailedException: Repository instance STGW-GSI is not found
     at com.tibco.infra.repository.RepoFactory.newClient(RepoFactory.java:3262)
     at com.tibco.infra.repository.RepoFactory.newClient(RepoFactory.java:3153)
     at com.tibco.tra.tsm.plugin.TSMComponentDeploy.testRepoUrlConnection(TSMComponentDeploy.java:1912)
     at com.tibco.tra.tsm.plugin.TSMEngineDeploy.addRepourlProperties(TSMEngineDeploy.java:120)
     at com.tibco.tra.tsm.plugin.TSMEngineDeploy.createTra(TSMEngineDeploy.java:85)
     at com.tibco.tra.tsm.plugin.TSMBwEngineDeploy.createTra(TSMBwEngineDeploy.java:62)
     at com.tibco.tra.tsm.plugin.TSMBwEngineDeploy.beginAction(TSMBwEngineDeploy.java:38)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.beginPerformAction(MutableAdminDomainImpl.java:788)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.deploy(MutableAdminDomainImpl.java:689)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.deployListInternal(MutableAdminDomainImpl.java:917)
     at com.tibco.pof.admindomain.impl.MutableAdminDomainImpl.deployOnClient(MutableAdminDomainImpl.java:849)
     at com.tibco.tra.tsm.TSM.deploy(TSM.java:2802)
     at com.tibco.tra.tsm.TSM$1.run(TSM.java:3169)
     at java.lang.Thread.run(Thread.java:662)

2011 Dec 29 19:42:36:279 GMT -8 Info [Application] AESDKJ-0000 [main] [Manage applications] The application "GMS - Guest Services Interface/AutoDeploy-TEST/GSI" has been deployed by "rbade".
2011 Dec 29 19:42:36:279 GMT -8 Info [com.tibco.administrator.command.tool.ApplicationManagement] AESDKJ-0000 [main] [ GMS - Guest Services Interface/AutoDeploy-TEST/GSI ]: Failed. Please check log file
     at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:551)
     at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:401)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
     at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
     at org.apache.tools.ant.Task.perform(Task.java:348)
     at org.apache.tools.ant.Target.execute(Target.java:390)
     at org.apache.tools.ant.Target.performTasks(Target.java:411)
     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
     at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
     at org.apache.tools.ant.Main.runBuild(Main.java:809)
     at org.apache.tools.ant.Main.startAnt(Main.java:217)
     at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
     at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Caused by: C:\BW-deployment\TIBant-bin-v4\tibant.xml:1706: Initializing ...
Finished initialization
Deploying application ...
Deployed status is Server plugin failed
Finished deploying application
[ GMS - Guest Services Interface/AutoDeploy-TEST/GSI ]: Failed. Please check log file

Thanks in advance.

Reddeppa

GSI.xml
GSI-dev.xml

Tom Howard January 04, 2012 20:24

Hi Reddeppa,

TIBant creates configuration xml files by applying a supplied set of properties to a template xml file extracted from an ear file (using AppManage). The idea being that by setting the appropriate properties, you can get the output you desire. If there is a specific part of the configuration you are trying to achieve and are having problems with, please let us know.

Often it is quite difficult to make that first switch to using properties (instead of manual deployments or editing configuration xml files directly). To make it easier, TIBant has a `extract-properties` macro, which can be used to generated the appropriate properties from an existing (or exported) configuration XML file.

Please let us know how you go.

reddeppa maddipatla January 13, 2012 20:41

Hi Tom,

Thanks for your update.

If you go through the configuration xml file given in the attachment. we can notice one thing, "<repoInstanceName>" tag is not present. But if you generate a configuration xml file by exporting it from admin using appmange, it contains this tag.

Conclusion is , <repoInstanceName> tag is not present if you generate configuration file from an ear file. Thats where I am struck, appmanage is trying to find the Repository instance , in my case it is STGW-GSI , to deploy and failing at that step.

I was just looking basic things here. I have an ear file with me and I want to deploy using TIBAnt. Please let me know how to overcome the above error?

Thanks,

reddeppa maddipatla January 13, 2012 20:57

One more point to add, TIBAnt is using only appmanage Batch commands, Did it have other standalone commands like to deploy single file?

Tom Howard January 15, 2012 21:21

Please set a property named `repoInstanceName` to the value you want it to have and then include the property in the propertyset passed into `configure-ear` using the `deployment-properties-refid` attribute.

BTW I've just noticed that the documentation for the `repoInstanceName` property is incorrect. The "Node Mapped To" is `/application/repoInstanceName`. I've created a documentation defect for this at https://windyroad.assembla.com/spaces/tibant/tickets/104-documentation-for-node-mapped-to-is-incorrect-for-repoinstancename

Tom Howard January 15, 2012 21:22

TIBant uses AppManage in batch mode for all deployments, even if the batch size is one.

RepoInstance is not selected properly.

5 comments