Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Managing TEXT Messages : Adding a Message Type to a Message Group

Adding a Message Type to a Message Group
To add a message type to a message group, perform the following steps:
1.
2.
Click New Message Type.
The Operation Type list is displayed with Notification selected. The Type selection cannot be modified because only Notification transactions are supported.
Synchronous request-response transactions are not supported by the TEXT protocol.
3.
You can configure the new massage type with the following tabs:
Notification Message Type
To configure the message type, enter information into the following tabs, then click Save:
General Tab
This tab allows you to configure the message type format on inbound and the raw data included in the message:
Delimited   This format defines files that contain a consistent delimiter all throughout the file.
Positional   This format defines files that have a defined position (or size) for each field in the file
Guideline Tab
This tab allows you to configure message guidelines and validator profiles. Click change to select the guideline file associated with this message type.
You can select the file type: File Reference or Uploaded File.
For Uploaded File, click Browse to select a configuration file from the local file system.
Load a guideline file, such as Positional_4040_850.sef.
None   Select when this type of translation is not used
TEXT to EDI   Select for the TEXT files to be converted to X12 or to EDIFACT protocol. To perform this conversion, the trading partner must enable both the TEXT and the X12 or EDIFACT protocol.
See also TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide, "TEXT to EDI Conversion."
Note   For any request that is being sent from the private process to TIBCO BusinessConnect for TEXT documents, an appropriate OperationID must be specified instead of EDI/Outbound.
Schema Tab
Message schemas are used to integrate TIBCO BusinessConnect EDI Protocol powered by Instream with back office systems. If the back office systems are implemented with TIBCO ActiveMatrix BusinessWorks, these message schemas can also be loaded into TIBCO Designer/TIBCO Business Studio at design-time to generate process definitions that send messages defined in TIBCO BusinessConnect EDI Protocol powered by Instream. This tab allows you to configure schemas and map files.
Click change to select the schema file associated with this message type. You can select the file type: File Reference or Uploaded File.
For Uploaded File, click Browse to select a configuration file from the local file system.
Load a message schema, such as Positional_4040_850.xsd.
The fixed value T-LAYOUT is used since all TEXT guidelines use LAYOUT as the root element in EDISIM Standards Editor.
Load a map file, such as Positional_4040_850_FX.map.
Load a map file, such as Positional_4040_850_XF.map.
Load a map file, such as PO_Positional_X12_4040_850.map.
Outbound Action
Name the new message type for the outbound action. Direction: Initiator to Responder (preset).
Inbound Action
Name the new message type for the inbound action. Direction: Responder to Initiator (preset).

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved