IBM BJ0NJML Integration Guide - Page 36
External Systems application., message contains multiple instances of a document, for example
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 36 highlights
Asynchronous Inbound Integration Processing A client can use the Java Naming and Directory Interface (JNDI) 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 the enterprise service are valid and 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. TIP To see if an enterprise service is valid and enabled, go to the Enterprise Services tab in the External Systems application. 4 If the verification is successful, the integration framework identifies the inbound JMS queue that is assigned to the selected enterprise service and external system. TIP To find the location of that queue, go to the System tab in the External Systems application. 5 The integration framework writes the message to the inbound queue. If the message contains multiple instances of a document, for example, if a single message contains ten person records, the application writes the single message, not ten individual messages, to the queue. If one of the referred records has a processing error, a complete message processing exception is identified and none of the other records are committed to the database. 6 The integration framework updates the JMS message header with the external system and enterprise service names. Data Import The following steps describe the initiation of inbound processing that uses the data import feature. 1 The integration framework checks that the external system and the enterprise service are valid and enabled. If you are importing flat files, the integration framework also checks that the enterprise service object structure supports flat structures. 22 Integration Guide