IBM BJ0NJML Integration Guide - Page 290
Invoke Method, IMConstants.ENDPOINTNAME, public byte[] invokeMap <String, Object>, MboRemote
![]() |
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 290 highlights
Integration Module Invocation The property IMConstants.ENDPOINTNAME contains the name of the endpoint that is associated with in the operational management product, integration module, and logical management operation relationship. In most cases, the endpoint property is the value that the process management product passes to the integration module. However, in unusual cases, the action class overwrites the configured endpoint. If a credential mapper is configured, the get service invoker utility methods call the credential mapper to retrieve the USERNAME and PASSWORD that is used for endpoint communication. These properties are returned by the utility methods in a map that is identified by the property IMConstants.ENDPOINTPROPS. The caller can overwrite any endpoint properties by adding them to this map. Before the action class calls the integration module, it must populate the source object with the logical management operation input fields. The action class then passes the source object data to the integration module with the mapping that is returned by the get service invoker utility method. The action class provides the logical management operation response object to the integration module when necessary. The logical management operation response object requires attributes. The action class must ensure that the response object has the logical management operation attributes. The attributes can be persistent or nonpersistent. The response object typically contains the source object data. Invoke Method The integration framework provides some invoke methods that the caller uses to invoke an integration module. Invoke methods use properties to determine what object data is returned to the caller. The properties also determine what action is taken on the returned data and how the integration framework communicates with the caller. The service invoker interface has four invoke method signatures: T public byte[] invoke(Map metaData, MboRemote sourceMbo, MboRemote targetMbo, String endPointName) T public byte[] invoke(Map metaData, MboRemote sourceMbo, MboSetRemote targetMboSet, int action, String endPointName) T public byte[] invoke(Map metaData, MboSetRemote sourceMboSet, MboRemote targetMbo, String endPointName) T public byte[] invoke(Map metaData, MboSetRemote sourceMboSet, MboSetRemote targetMboSet, int action, String endPointName) 276 Integration Guide
![](/manual_guide/products/ibm-bj0njml-integration-guide-77e799f/290.png)