Collectives on Stack Overflow. Learn more. Asked 1 year ago. Active 1 year ago. Viewed times. Tomer Shetah 7, 6 6 gold badges 21 21 silver badges 34 34 bronze badges. Add a comment. Active Oldest Votes. Morag Hughson 6, 15 15 silver badges 41 41 bronze badges. JasonE JasonE 2, 9 9 silver badges 7 7 bronze badges.
The static configuration overrides dynamic queuing. Name of the reply queue manager, for example, myQueueManager. This sets dynamically the queue manager for the response sent by Siebel CRM.
You can set a MQMD message header for the Siebel application by specifying it as a property in a property set on the outbound side. Whereas on the inbound side, the MQMD message header of the response is exposed to the user as a property on the output property set. On the inbound side, you can have the supported MQMD message headers as part of the output property set without having to do extra steps to see these MQMD message headers.
Send within the workflow, input arguments are added that can modify MQMD headers. The input XML contains values for headers and message body fields, which are parsed, and respective values are set on MQ message. The MQ message will then be sent to MQ queue. This option does not define any structure for input message. The input message is set on the message body as a single string field. Only one RFH2Header is added to the message. Click this button to launch editor to define the fields of the message.
Figure Editor to define fields in message. The editor contains a table with Tag Name and Data Type columns. The schema for input XML is built based on the fields defined here. All the elements are defined as string type and hence, the schema does not validate content of element with appropriate data type.
Structure identifier. This field should strictly contain 4 characters. If there are more than 4 characters, content after 8 th character is pruned by the component. If there are less than 8 characters required additional blank spaces are padded at the end by the component.
The character set identifier of the data that follows the last NameValueData field; it does not apply to character data in the MQRFH2 structure itself. The format name of the data that follows the last NameValueData field. This field should strictly contain 8 characters. If there are more than 8 characters content after 8 th character is pruned by the component. A variable-length character string containing data encoded using an XML-like syntax. Figure Sample Event Process.
When the Text Type is set to Raw Text there is no schema defined for the input. The input message text is written MQ message body as a single String field.
Figure Fields defined for message body. Figure Schema when only fields of message body are defined. The Input XML should have all the fields and should strictly follow the order. MQMD headers are not explicitly set by the component.
All the fields defined are added as child elements under MessageBody in the same order in which these fields are defined in CPS and all the MQMD headers selected are added as child elements under Message Header in the same order in which these headers are defined in CPS. If Message Header element is not present MQMD headers are not explicitly set by the component and it behaves exactly like the case where only the fields of message body are defined.
The output message text contains a single String field. When the Text Type is set to Parse Message, the output schema varies based on the configuration of structure and headers.
When only fields of message body are defined in Structure dialog. All the fields defined are added as child elements under MessageBody in the same order in which these fields are defined in CPS. All rights reserved. Pre-built Microservices eStudio Dashboard. Icon This section can be skipped if the queue to which messages are sent is already created.
Icon Order of the fields is important and the order of the rows in this table defines the order of fields in the MQ message. Move Up and Move Down buttons are used to reorder the fields. Add and Delete buttons are used to add or remove the fields. If the order of elements defined in Structure editor differs from order of fields in MQ message or if there are additional fields defined in Structure editor or if some of the fields present in the MQ message are not defined in the Structure editor, one of the following happens: error when building output message from MQ message.
0コメント