Manually Deploying the ESI EAR
By default MICU deploys the ESI EAR. However, in some cases, as when you are deploying custom business logic, or supporting multiple Oracle instances you may need to manually deploy the newly generated EAR.
To manually deploy the EAR using the TIBCO Administrator Graphical User Interface use the following procedure:
1. In a browser window login to the TIBCO Administrator in GUI mode using http://<Administratorhostname>:8426. For example: http://localhost:8426
2. In the TIBCO Administrator click Application Management.
3. Click New Application.
4. Browse to and select the following EAR:
◦ <TIBCO_Home/esi/ear/ESI_ORA_TIB_5_6_EAR_10_0_<BuildNumber>.ear”
5. Click OK.
6. Ensure that ProcessArchive.par displays the target as a BusinessWorks host machine, and that ESIOMAdapterConfiguration.aar displays the target as AdapterHostMachine.
7. Click Save.
|
The deployment name string can only be modified from the "-" symbol on. The string content before that symbol is the domain name. For example, if the Deployment Name text box displays i2607 - Oracle Apps then:
• i2607 is the domain name
• Oracle Apps is the deployment name
|
8. In the Configuration Builder window click Oracle. This is the application name.
9. Click the Advanced tab.
|
Ensure that:
• "/" is used as a path separator and that the ESIDirectory path is terminated by "/" .
• ESIOMAdapter/Datasource” is appended to ESIJMS/DataResponseQueue name
• JMS url in ESIJMS/JNDIContextURL has hostname instead of “localhost”.
|
11. Click Save.
12. Click > .
13. Increase the Heap Size, Set Maximum Heap Size (MB) and Java Thread Stack Size (MB) to 512.
14. Click Save.
15. ClickDeploy and then OK.