After installing the connector and configuring the standard and connector-specific configuration properties, you have the option of modifying the event handling and logging capabilities for the connector from within the SAP application.
Load balancing distributes event and business object request processing across multiple connectors. The connector can handle only one transaction at a time. However, you can process multiple events and business objects at the same time if you set up multiple connectors to handle specific business objects. For more information on setting up multiple connectors, see Installing multiple connectors.
To set up event distribution for multiple connectors:
The configuration table in the SAP application cannot accommodate all modifications. Therefore, the adapter provides an ABAP include program that can be modified to filter events. This program, /CWLD/TRIGGERING_RESTRICTIONS, is called from within the event trigger /CWLD/ADD_TO_QUEUE, to enable additional filtering of events.
To view or modify the include program /CWLD/TRIGGERING_RESTRICTIONS:
You can set the priority of an event to be processed based on its importance. By setting the priority of each combination of business object, integration broker, and connector, you can delay a connector's retrieval of an event. For example, if you set the priority of an event to 10, the connector polls the event table ten times before retrieving the event. So, if the connector polls the event table every 5 seconds, the connector picks up the event after 50 seconds. Each time the connector polls, the priority value is reduced by one until the event is retrieved and processed.
To set the priority of an event:
The connector's log tables are located, by default, in the tablespace named PSAPUSER1D, and the indexes are located in tablespace PSAPUSER1I. The PSAPUSER1D and PSAPUSER1I SAP application tablespaces, which are reserved for customer use, are typically small. Because of the default size, these tablespaces can fill up quickly, depending on the level of activity and the logging level of the SAP installation for the adapter.
To view the current size of these tablespaces, go to transaction DB02, and then click the Current Sizes button. The volume of events captured by the WebSphere business integration system determines the size needed for these tablespaces.
If the default sizes are too small, ask the SAP database administrator to modify them.
There are four objects for the WebSphere business integration system that must have an adequate number range within the SAP application. When the transports are installed, the following objects and their default number ranges are set:
Verify that the associated number ranges are set correctly. To view the number ranges: