AppSpecificInfo for the server verb of the top-level business object

The connector uses the value of the server verb's application-specific information in the top-level business object to call the appropriate RFC Server-specific business object handler and to determine the destination collaboration for event processing. The value of the AppSpecificInfo property for the server verb specifies:

The format is as follows:

AppSpecificInfo = bapi.server.BOHandler;Collab=CollaborationName

where BOHandler is the name of the class and CollaborationName is the name of the destination collaboration.

SAPODA automatically adds the application-specific information for the server verb in top-level business object. For the value of the business object handler's classname, it uses the name of the RFC-enabled function. It does not provide a value for the collaboration name parameter. Therefore, you must manually add the name of the collaboration.

Important:
When a message broker is the integration broker, a dummy value must be provided for the collaboration name parameter. The RFC Server-specific business object handler requires a value for this parameter to process the event successfully.
Note:
There is a one-to-one relationship between the WebSphere business object for SAP and the RFC Server-specific business object handler. The business object handler class files must exist in the \connectors\SAP\bapi\server directory.
Important:
You must include the value server before the business object handler name to identify that the RFC Server-specific business object handler acts as a server.

For example if you are supporting the BAPI_PO_CREATE RFC-enabled function and the destination collaboration is called POCollab, then the verb application-specific information is as follows:

AppSpecificInfo =bapi.server.Bapi_po_create;Collab=POCollab 
 

Copyright IBM Corp. 1997, 2004