Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Getting Started : Complex Application Deployment

Complex Application Deployment
In a more complex scenario an application may require fault tolerant options, alerts, TIBCO Hawk rulebases, and so on defined. While you could define these options in the deployment configuration file that is generated by the AppManage utility, it is recommended you configure the options in TIBCO Administrator and use AppManage to generate the deployment configuration file from the application itself.
1.
   buildear -ear /dbtrigger.archive
            -o c:\ears\deployment\dbtrigger.ear
            -p c:\tibco\projects\dbtrigger
2.
Start the TIBCO Administrator GUI and import the EAR file, then configure the application with deployment options. See the TIBCO Administrator User’s Guide for information. Exit TIBCO Administrator after the deployment options are set.
3.
The AppManage utility creates the deployment configuration file based on information in the application you configured in the TIBCO Administrator GUI. The -out option provides the name and location of the deployment configuration file that will be generated by the AppManage utility. The -app option identifies the application in the given administration domain to use. The -template option is used so that substitution variables are created for each machine tag.
   AppManage -export -out c:\ears\deployment\dbtrigger.xml
       -app dbtrigger -domain tp001 -user admin -pw admin -template
 
4.
Before editing the file, copy it and name it based on the application and domain into which the application will be deployed. Open the new file and change the <machine> XML tags to the name of the machine on which the processes run. For example:
   <services>
      <bw name="Process Archive.par">
         <enabled>true</enabled>
         <bindings>
            <binding name="">
               <machine>%%Process Archive.par-machine%%</machine>
            .
            .
            .
         <bindings>
            <binding name="">
               <machine>%%deuxiemeprocess.par-machine%%</machine>
            .
            .
            .
5.
After you have set the machine bindings, you can upload and deploy the application in one operation. The following command uploads the EAR file and the deployment configuration file into the tp003 domain. The -deploy option specifies that the application should be deployed. The -ear option specifies the EAR file to load and the -deployConfig option specifies the name and location of the deployment configuration file to use. The -app option provides the application name. Note that the application name and domain names are case sensitive.
   AppManage -deploy -ear c:\ears\deployment\dbtrigger.ear
             -deployconfig c:\ears\deployments\dbtrigger_tp003.xml
             -app dbtrigger -domain tp003 -user admin -pw admin

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved