IBM BJ0NJML - Service And Asset Management - Inbound Integration Process Initiation; Messages in the Inbound Queues

Asynchronous Inbound Integration Processing
Inbound Integration Processing 21
Inbound Integration Process Initiation
Summary An external system can use the following methods to send asynchronous
messages to the system:
Messages in the Inbound Queues
HTTP Post and
Enterprise Beans
The following steps describe the initiation of inbound processing using the
integration framework:
1 A servlet provides the ability for external systems to post messages to the
system using HTTP or HTTPS. You can use the following URL to post the
messages to enterprise services that process messages asynchronously:
hostname:port/meaweb/esqueue/extsysname/entservname
 extsysname is the name of the external system.
 entservname is the name of the enterprise service.
2 J2EE™ clients can invoke Enterprise JavaBeans that are written according to
the Sun Microsystems
®
, Inc., J2EE client specification.
You can use the following code to invoke the Enterprise JavaBean to process
the enterprise service message asynchronously:
public byte{} processExternalDataAsync(byte[] extData, String
serviceName, String sender)
Method Availability
XML that uses the integration
framework that uses HTTP Post,
Enterprise JavaBean (EJB) Invocation,
Web service invocation
All external systems with enabled
enterprise services.
Enterprise services must support an
operation other than QUERY.
Data import feature, that uses XML or
flat files
External systems with enabled
enterprise services.
The enterprise service object structure
must support flat structures for flat
file processing.
Interface tables External systems with enabled
enterprise services.
Enterprise service object structure
must support flat structures.
Data import cron task External systems with enabled
enterprise services.
Enterprise service object structure
must support flat structures.