Performance Tuning Guide > Tuning Siebel EAI for Performance >

Best Practices for Siebel EAI Tuning

This section describes best practices for maintaining acceptable performance using Siebel EAI.

General guidelines are followed by recommendations specific to Siebel EAI features such as IBM WebSphere MQ (formerly MQSeries) Transport adapter, HTTP Inbound Transport adapter, EAI Siebel Adapter, virtual business components, and Workflow Process Manager used with Siebel EAI.

Follow these general guidelines to improve overall performance for data integration and throughput of Siebel Business Applications:

  • Try to minimize round trips between systems. For example, if an integration needs to request three pieces of data, do not send a request for one piece of data, wait for the response, and then send the next request. If you need multiple pieces of data, gather the data in a single request.
  • Try to keep processing in a single session wherever possible, to avoid having to make calls between server components.
  • Within a session, try to minimize the nesting of calls between components such as workflow, scripting, and the EAI Siebel Adapter. For example, use a workflow process to sequence the calling of business services and keep scripting code in self-contained steps. Workflow subprocesses can be used to package together commonly called sequences of services.
  • Use alternatives to scripting, where possible. If you use scripting, use it minimally and economically and apply documented guidelines. For more information, see Best Practices for Siebel Scripting.
  • Configure business components, business services, caching, and other application functionality that supports integration processing to obtain optimal performance. For more information, see other sections in this chapter and see Tuning Customer Configurations for Performance.
  • Perform capacity planning for all servers that support integration processing. Siebel Expert Services may be consulted for sizing reviews.
  • Try to represent the incoming external data in the same code page and encoding that the Siebel application uses internally (UCS-2). This eliminates the need to use the Transcode business service in your workflow process, thus improving performance.

The following sections discuss specific technologies and what you can do to improve performance in each area.

Performance Tuning Guide