Verb processing

Note:
This section pertains to the connector when it acts as a client. The verb-processing issues described here do not apply when the connector runs as a server.

The connector processes business objects passed to it by a broker based on the verb for each business object.

When the connector framework receives a request from the broker, it calls the doVerbFor() method of the business-object-handler class associated with the business object definition of the request business object. The role of the doVerbFor() method is to determine the verb processing to perform, based on the active verb of the request business object. It obtains information from the request business object to build and send requests for operations to the application.

When the connector framework passes the request business object to doVerbFor(), this method retrieves the business object ASI and invokes the BO handler, which in turn reads the verb ASI and translates it into a series of callable functions. The verb ASI is an ordered list of the methods that need to be called for that verb. The order in which the calls are made is critical to the successful processing of the object.

If the verb ASI is blank, the BO handler searches for a method with populated parameters and calls that. Only one method can be populated; otherwise, if multiple methods are populated yet the verb ASI is blank, the connector logs an error and returns a FAIL code. For details about error processing, see Error handling.

The connector does not support any specific verbs, but using the ODA, the user can configure custom verbs. The standard, pre-existing verbs are Create, Retrieve, Update, and Delete. These can be given whatever semantic meaning you provide through the Object Discovery Agent (ODA) running in Business Object Designer. For details about using the ODA to assign a method call sequence to a verb, see Creating and modifying business objects.

Note:
You can specify two pre-defined functions in the verb ASI: LoadFromProxy and WriteToProxy. Their purpose is to synchronize a business object's simple attributes to a CORBA object's public properties.

Copyright IBM Corp. 1997, 2003