IBM BJ0NJML Integration Guide - Page 47
Object Structure Identification
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 47 highlights
Synchronous Inbound Integration Processing 2 You can use the following code to invoke the Enterprise JavaBean to process the enterprise service message synchronously: public byte{} processExternalDataSync(byte[] extData, String serviceName, String sender) A client can use the Java Naming and Directory Interface name of the Enterprise JavaBean (ejb/maximo/remote/enterpriseservice) to look up the Enterprise JavaBean reference and to invoke the method. The client also needs the following settings: Access to the Home and Remote class files Access to the J2EE jar files for the server The URL of the server that hosts the Enterprise JavaBean The context factory class name The client code must instantiate the default IntialContext object. The context derives the provider URL and the context factory from the environment. 3 The integration framework checks that the external system and enterprise service are valid an enabled. If the verification fails, the integration framework notifies the sender of the error and does not process the message. TIP To see if an external system is enabled, go to the System tab in the External Systems application. To see if an enterprise service is valid and enabled, go to the Enterprise Services tab in the External Systems application. Object Structure Identification Summary The integration framework identifies the object structures that are associated with the enterprise service and creates a copy of the message for each object structure. The following activities identify the object structures that are associated with the message: 1 The integration framework retrieves the record from the inbound queue. 2 The integration framework identifies the enterprise service from the retrieved record. 3 The enterprise service definition lists the object structures used by the processing service. 4 The integration framework creates one copy of the enterprise service for every object structure that is associated with the enterprise service. The processing sequence that is associated with the object structure specifies the sequence in which the subsequent object structure processing is to be performed on the enterprise service. Inbound Integration Processing 33