Enterprise Administration > Windchill ESI > Administering Windchill ESI in an SAP Environment > Guidelines for Monitoring, Diagnosing, and Resolving Problems > Diagnosing Problems > Categorizing Problems: Key Areas of Focus for Troubleshooting > TIBCO Problems > BusinessWorks Problems
  
BusinessWorks Problems
• Verify that all required TIBCO services are running. Process engines do not start if the following required services are not running:
◦ TIBCO Administrator <version> (Domain name)
◦ TIBCO HAWK Agent (Domain name)
• Verify the existence and contents of required Windchill ESI BusinessWorks application properties and configuration files:
◦ ESIEMailMessageLookups.properties
◦ ESIDefaults.properties
◦ ESIErrorHandlingCodes.properties
◦ ESILookups.properties
◦ ESIMessageLookups.properties
◦ FilesToRead_SAP.properties
• Verify that the BusinessWorks JMS client is connecting to the TIBCO EMS server
• Verify all other EMS-related configuration
• Isolate any Java Virtual Machine (JVM) issues, such as unsupported versions or memory overflow errors
• Verify that the Windchill ESI components are deployed to the correct domain
• Verify the ESI business logic configuration and deployment settings, including the global variable values
* 
You must restart the process engine for new global variable values to take effect.
• Validate the configuration settings in the TRA file
• Validate the BusinessWorks Administrator server configuration by:
◦ Authorizing user accounts
◦ Making sure that multiple repositories with the same Rendezvous configuration (network, service, and daemon) on the same subnet have unique names, regardless of the BusinessWorks administration domain
◦ Ensuring that the server-based repository (.dat) files are not deleted directly. To properly delete a server-based project from an administration domain, follow these steps:
▪ Undeploy the project (this removes all of the .tra and .cmd files)
▪ Stop the administration server service
▪ Delete the contents of <Tibco_Home>/tra/domain/<Domain_Name>/application/<Application_Name>/working folder
▪ Restart the administration server service
* 
The meaning of <Application_Name> in the above referenced path may be understood from the fact that the deployment name of an application is of the form <Domain_Name>-<Application_Name>.
• Isolate any issues with internationalization or locale configuration settings. Check out the following:
◦ com_infoengine_locale attribute in the JMS header of Windchill ESI messages
◦ ESISAPAdapter/Locale global variable
◦ Default and cross-referencing lookup file entries used in data mapping