Installation and Upgrade > Windchill ESI > Installing and Configuring Windchill ESI in an SAP Environment > Using the Middleware Installation and Configuration Utility > Performing Post Installation Steps > Manually Deploying the ESI EAR
  
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 SAP instances you may need to manually deploy the newly generated EAR.
To manually deploy the EAR using the TIBCO Administrator 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_SAP_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 ESISAPAdapterConfiguration.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 - SAP then:
• i2607 is the domain name
• SAP is the deployment name
8. In the Configuration Builder window click SAP. This is the application name.
9. Click the Advanced tab.
10. Modify the ESIJMS and ESISAPAdapter variable groups and the ESIDirectory variable. For more information see Windchill ESI Preferences, Distribution Target Attributes and Global Variable Groups
* 
Ensure that
• "/" is used as a path separator and that the ESIDirectory path is terminated by "/" .
• <ESISAPAdapter/SystemID>/.<ESISAPAdapterClient> is appended to the value of the global variable ESIJMS/DataResponseQueue.
• The JMS URL in ESIJMS/JNDIContextURL and ESISAPAdapter/JMSProviderURL, has the relevant hostname instead of “localhost”.
11. Click Save.
12. Click <$Hostname$> > Process Archive under Process Archive.par.
13. Increase the Heap Size, Set Maximum Heap Size (MB) and Java Thread Stack Size (KB) to 512 or higher.
14. Click Save.
15. Click TIBCO Administrator GUI > Application Management > <ApplicationName> > Configuration > ESISAPAdapterConfiguration.aar > Advanced > adr3.maxconnections and set the existing value to a higher value (for example, 6), then add adr3.locale to UTF8.
16. Click Save.
17. ClickDeploy and then OK.
* 
If the EAR was deployed manually you need to configure the EMS appropriately.