Use SAPODA to generate RFC-enabled function-specific business
object definitions and RFC Server-specific business object handlers
for each RFC-enabled function you want to support. You can use the
generated files with minimal modifications.
The only edit you must make is specifying the name of the
destination collaboration in the verb application-specific
information of the server verb.
- When InterChange server (ICS) is the integration broker, this
information is required because a collaboration cannot explicitly
subscribe to an event that is pushed to the connector. Therefore,
the RFC Server-specific business object handler must determine the
appropriate destination collaboration from the business object's
metadata, and then instantiate the collaboration.
- When a message broker is the integration broker, a dummy value
is required for the RFC Server-specific business object handler to
process the event correctly.
- Important:
- If the RFC-enabled function that you are using does not contain
a simple field attribute, and SAPODA has created a Dummy_key
attribute as the key attribute, do not modify the values of this
attribute.
After the business object definition and its corresponding RFC
Server-specific business object handler are generated, you must add
the business object definition to your WebSphere business
integration system's runtime environment.
The RFC Server-specific business object handler files are:
- RFC-EnabledFunctionName.java
- RFC-EnabledFunctionName.class
For example, given the BAPI_PO_CREATE RFC-enabled
function and a user-specified prefix of sap_, SAPODA
generates the following:
- sap_bapi_po_create (business object definition that
includes all child business objects)
- Bapi_po_create.java
- Bapi_po_create.class
- Important:
- You can modify the name of the generated business object as
well as the name of its child business objects. To do so, you must
edit the definition as a text file rather than in Business Object
Designer. If you do change a business object's name, ensure that
you also modify all references to the names that you change. Also,
if you modify the names of the generated.class file for
the business object handler, you must maintain the changes for the
server verb application-specific information for the associated
business object.
