Enabling the SAP application for the connector

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.

Setting up event distribution

Load balancing distributes event and business object request processing across multiple connectors. The IBM WebSphere Business Integration Adapter for mySAP.com 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:

  1. Go to IBM CrossWorlds Station (transaction /n/CWLD/HOME).
  2. Click the Configuration tab, and then click the Event Distribution button.
  3. Click the New Entries button (F5), and in the New Entries window, enter the business object name, connector name, and integration broker name.
  4. Enter a number in the counter field for each business object. The combination of the business object and counter provides a unique key for the event distribution table. The counter can be any number up to six digits.
Note:
In a test environment, you may have multiple users testing the same business object that is subscribed to by multiple connectors. If each user wants only a certain event for that business object, then you can specify a user name to differentiate between which event is passed to the combination of which connector and which integration broker. In the User (Event Trigger) field, enter the appropriate user name for the business objects. For information on how the WebSphere business integration system identifies each unique instance of a message broker, see Event request.

Setting up event filtering

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.

Note:
You must have developer privileges to make changes because the code needs to be recompiled.

To view or modify the include program /CWLD/TRIGGERING_RESTRICTIONS:

  1. Go to IBM CrossWorlds Station (transaction /n/CWLD/HOME).
  2. Click the Configuration tab, and then click the Event Restriction button.

Setting up event priority

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.

Note:
For information on how the WebSphere business integration system identifies each unique instance of a message broker, see Event request

To set the priority of an event:

  1. Go to IBM CrossWorlds Station (transaction /n/CWLD/HOME).
  2. Click the Configuration tab, and then click the Event Distribution button.
  3. Fill in the Priority column with a value between 1 and 99 for the appropriate business object.

Increasing log tablespace size

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.

Verifying number ranges for transport objects

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:

  1. Go to transaction SNRO.
  2. Populate the Object field with the object name (for example, /CWLD/EVT).
  3. Click Number Ranges, and then click Intervals.

Attention: If you reinstall the 4_Primary or 4_Delivery connector transport in an installation where events have already been generated, new events may be created using existing event IDs. To prevent this problem, turn off logging by going to the Configuration tab in IBM CrossWorlds Station, and then truncate the log completely before reimporting the connector transport file. Once the connector transport file has been successfully loaded, turn logging back on. For more information on truncating the event log, see Setting up truncation of the event log.

Copyright IBM Corp. 1997, 2004