User Guide > Designing and Executing Processes > Using Scripts in Processes > Managing Queue Message Objects
Was this helpful?
Managing Queue Message Objects
Message objects are named memory storage locations that can be used to temporarily store data at run time. The objects consist of a buffer that is used to hold a message body and a container of user and application defined message properties. Once a message object is created, it stays in existence until the transformation or process ends.
There are three methods for using message objects:
• Using the DJMessage URI scheme - The body of a message object can be accessed using a URI with the format djmessage:///name, where name is the message object to be accessed. This URI scheme can be used anywhere that other URIs are used, including as the source or target for a transformation, and in the file functions, such as FileRead and FileWrite. URIs can also be used in the steps in a process, such as in the source file in a Validator or XSLT step. If a message object is specified as the target of an operation, and the message object does not exist, it is created. If a message object is specified as the source of an operation, and the message object does not exist, an error occurs.
• Specifying a message name in step - When a GetMessage or PutMessage action is selected for a step type, you must specify a name for the message object to be used for the action. For the GetMessage actions, if the message object does not exist, it is created and if it exists, then the message properties are deleted and it’s body is cleared. For the PutMessage actions, if the message object does not exist, an error occurs. For more information, see GetMessage Method and PutMessage Method.
• Using scripting - For information on the methods used for accessing message objects in the scripting language, see DJMessage Object Type.
Last modified date: 12/03/2024