uCosminexus Service Platform, Basic Development Guide

[Contents][Glossary][Index][Back][Next]

6.2 Creating Message Format Definition Files

This section describes the methods to create and set the message format definition files that form the basis of data transformation definitions. It also explains notes related to message format definition files and binary message formats.

Organization of this section
(1) Creating message format definition files
(2) Setting message format definition files
(3) Notes on creating message format definition files
(4) Points to be considered for binary message format for which a separator is set
(5) Points to be considered for message format of optional format (any format)

(1) Creating message format definition files

Create a message format definition file that becomes the basis for defining data transformation. A message format definition file is required for the transformation-source and for the transformation-destination. For details about the types of message format definition files and creation methods, see 4. Creating Message Formats.

For details about the message format definition file used for defining data transformation, see 2.6.5 Scoping of XML schema.

(2) Setting message format definition files

Set up the created message format definition files in the Service Adapter Definition screen or the Business Process Definition screen. For details about the Service Adapter Definition screen and the Business Process Definition screen, see 5.3 Defining Adapter Contents and 5.3 Defining Business Process Contents, respectively.

(3) Notes on creating message format definition files

Format of a message format definition file
The message format definition file used for defining data transformation must satisfy the conditions described in 2.6.5 Scoping of XML schema. For details on schema conditions, see 2.6.5 Scoping of XML schema.

Elements not displayed on the window
For the elements annotation, appinfo, documentation, and notation, there is no tree display in the transformation-source schema tree viewer and the conversion destination schema tree viewer.

Window display of sequence element and choice element
The transformation-source and destination schema tree viewers display the sequence element or choice element as follows according to the contents of the XML schema to be defined.
  • #(sequence)
    Displays the sequence element (compositor) wherein the occurrence count is fixed as once under the sequence element or choice element.
  • #(choice)
    Displays the choice element (compositor) wherein the occurrence count is fixed as once under the sequence element or choice element.
  • #anonymous
    Displays the sequence element, choice element or all element (compositor) wherein the occurrence count is not fixed as once.

(4) Points to be considered for binary message format for which a separator is set

When using binary message format for which separator is set, you must take note of following points.

(5) Points to be considered for message format of optional format (any format)

When you set optional format (any format) in the message format definition file, part of settings is ignored.

Following table describes the settings that are ignored.

Table 6-1 TableSettings ignored in case of optional format (any format)

Target component Ignored settings
TP1/RPC reception Independent definition file (cscurecptp1rpc.properties)
  • urecp-tp1rpc.dt-skip
Independent definition file (csc_owncodeconvert.properties)
  • All settings
TP1 adapter HCSC server runtime definition file (cscsvconfig.properties)
  • xmltelegram-maxcache-num
  • telegram-validation
  • xmltelegram-namespace-complement
  • telegram-undefined-character-code
Independent definition file (csccustomadapter.properties)
  • custom-adapter.dt-skip
Independent definition file (csc_owncodeconvert.properties)
  • All settings
HTTP adapter
General custom adapter