Siebel Performance Tuning Guide > Tuning Siebel EAI for Performance > Best Practices for Siebel EAI Tuning >
Other Best Practices for Siebel EAI
Review the following issues for applicability to your deployment, for optimizing Siebel EAI performance:
- Check disks on the machine. Do a preliminary test on the queue manager you are using to see how many sends and corresponding receivers it can support per second (use multiple drivers). Queue vendors such as IBM WebSphere MQ provide test programs you can use to drive these and determine how much the queue itself can scale. The speed of the disks on the machine is important.
- Optimize messages. In the messages, reference only the columns you require.
- Create smaller business components. Messages might use only a small portion of the actual business components.
Create copies of the business components you are using. In the copies, keep active all fields used by the optimized integration object or otherwise used for correctly processing of messages (like the visibility fields or status fields). Deactivate all other fields. Also deactivate the join definitions and multi-value links (MVLs) that are not needed for processing of the messages.
The original business components are often large and complex and contain elements you will not need for your integration purposes. Use the smaller business components and business objects and links created when creating the optimized integration object.
Business components may have fields with Force Active set to TRUE. Check this property for fields in the business components, using Siebel Tools. If the fields are not needed, set Force Active to FALSE.
- Set user property All Mode Sort to FALSE. Set the user property All Mode Sort to FALSE for optimized business components (if not already set). Do this only for the smaller business components created for use with Siebel EAI, because this user property changes the order in which rows are retrieved—which might not be appropriate or normal clients. For more information about All Mode Sort, see Siebel Developer's Reference.
- Optimize database queries. Review queries generated by the receiver process and verify that they are optimized.
- Turn off logging. Turn off server-side logging that you do not require.