Unwired Orchestrator supports XML and Formatter-based wire formats. When defining a messaging service using the New Service Wizard, additional information is required if you are working with non-XML files.
Formatter-defined wire formats must be imported into Unwired Orchestrator using the Import Wizard>New Era of Networks format Resource selection. This import adds an XSD file and the required nnfie resource file to the project. See Importing Wire Formats. This imported XSD is used to define Notification and One-Way messaging services.
To output Formatter-based wire format messages, a One-Way service must be defined using an XSD that was generated from an nnfie file. The definition must also specify the output format. When you are defining a One-Way service to produce formatter-defined wire format output messages, enable Custom Wire Format as the wire format type on the Wire Format Details page. When you select Custom Wire Format, three additional fields are required:
Output format name. This name must be the Normalized version of the target output format name.
Formatter map name, if a map was used in the Formatter.
Locale. See Supported Locales.
You must also select the encoding to be used with wire formats. By default, the encoding is set to UTF-8. A complete list is provided in Supported Code Sets. On the Message Options page, you have the option of specifying values for the OPT_APP_GROUP and OPT_MSG_TYPE message header fields of output messages.
To parse Formatter-based wire format messages, a Notification operation must be defined using an XSD that was generated from an nnfie file. When defining a Notification operation using an XSD that was generated from an nnfie file, the input message is always wire format so no wire format details are necessary.
Note: The supported encoding list displays IANA names when the sybfmt wire format type is selected and New Era of Networks encoding names when the XML wire format type is selected.