Other Configuration Problems

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 > Other Configuration Problems

Verify following settings while manually deploying the EAR:

• DataResponse Queue name: Should have the <SystemID>.<Client> (like PT3.800) appended to it.

• JMS URL in ESIJMS and ESISAPAdapter group: Should have the hostname and not localhost.

• Java Max Heap Size and Java Thread Stack Size settings: These should be more than 512 MB and 512 KB respectively.

• Set TIBCO Administrator GUI > Application Management > <ApplicationName> > Configuration > ESISAPAdapterConfiguration.aar > Advanced > adr3.maxconnections to a higher value (for example, 6) and set adr3.locale to UTF8.

Now deploy the application, but do not start the services.

EMS: Run following commands in a JMS Administration window to configure JMS. Replace <DataResponse>, <EAI User> and <WCESI User> with the applicable values; for example com.ptc.windchill.esi.DataResponse.PT2.800, ESISYS and WCESI.

• create queue <DataResponse>

• setprop queue <DataResponse> secure

• grant queue <DataResponse> <EAI User> receive

• grant queue <DataResponse> <WC ESI User> send

• setprop factory QueueConnectionFactory url=tcp://<JMSServer>:7222

• commit

Now start the services.