Accessing Message Data in IBM APP Connect
If we want to access, the contents of a message, for reading or writing, use the structure and arrangement of the elements in the tree that is created by the parser from the input bitstream of IBM App Connect
The above Block Diagram represents How the Message transfer through the entire Message flow. If any Environment Message is declared in the flow, it will be run the entire flow. If any local environment message is declared, it will transfer to the next required node only.
The OutputRoot is used when we need to send or transfer the message from the present compute node to another node or another flow or Response. While using OutputRoot we will get the properties of the message also.
Ex: SET OutputRoot.JSON.Data.Response=‘outputRoot_Response’;
The InputRoot is used when we need to take an input message into Compute node. That input message maybe comes from another node or another flow or any third-party tools like SOAP_UI etc.,
Ex: SET OutputRoot=InputRoot;
It is accept the entire Input message, which is given to the node, and we cannot use part of the input message. The InputBody will be in the form of BLOB format.
Ex: SET OutputRoot.BLOB.BLOB=InputBody;
The Root is used in the Database or Filter nodes to handle the Message. Here we can handle the message with the Database. We cannot create an output message in these nodes. We can use compute node to create an output message.
IF Root.JSON.Data.inComingMessage=‘filter’ THEN
The InputProperties is helping to access the properties of the incoming messages. That incoming message maybe comes from another node or another flow or any third party tool like Postman, SOAP_UI, etc.,
Properties Of message:
MessageSet, MessageType, MessageFormat, Encoding, CodedCharSetId, Transactional, Persistence, CreationTime, ExpirationTime, Priority, ReplyIdentifier, ReplyProtocol, Topic, ContentType, IdentitySourceType, IdentitySourceToken, IdentitySourcePassword, IdentitySourceIssuedBy, IdentityMappedType, IdentityMappedToken, IdentityMappedPassword, IdentityMappedIssuedBy.
Ex: SET OutputRoot.Properties =InputProperties;
We can also handle the Properties by using InputRoot.Properties also:
Ex: SET OutputRoot.properties=InputRoot.Properties;
The Environment helps to store the message in the Environment variable and is used in any location in the entire message flow. The Environment tree lives the Entire message flow.
Ex: SET Environment.varaiblename=‘Stored_Message_in_EnvironmentVaraible’;
The InputLocalEnvironment that is helps to handle the message of the incoming nodes that contain messages in the local environment.
When we need to use the message Transfers from one node to another node we will use the outputlocalEnvironment we can transfer, the message but the user cannot see the output local environment message at Response End.
Ex: SET OutputLocalEnvironment=InputLocalEnvironment;
The InputDestinationList is helping to handle the incoming destination list which is present in the local environment.
Which is the local environment property. We can route the destination of the message to another node
The inputExceptionList is when we need to handle the exception message in compute node then we use the InputexceptionList. By this Input Exception List, we can transfer the exception list.
When we want to transfer the Exception list from the present node to another node then we use the OutputExceptionList.
Ex: SET OutputExceptionList=InputExceptionList;