Configure a UTF-16 Server

Prerequisites

Before you start configuring your UTF-16 Server, make sure that in the Topography workbench, you have entered your operating system in the definition of the Host of the  Rule Engine. By default, the operating system is set to Windows.

UTF-16 and Finance objects

You can enter Unicode characters in the fields of the following Finance objects:

  • Business-Field, Aggregation-Rule, Financial-Tag, Transformation-Domain, Processing-Context-In, Processing-Context-Out,
    • Label
    • Description
  • Financial-Procedure, Financial-Event, AccountingIntegrator Enabler Server
    • Name
    • Label
    • Description
  • Input-Event Business-Document, Input/Output-Event Business-Document
    • Label
    • Leaf element labels
    • Description
  • Table
    • Label
    • Table entries content
    • Description
  • Variable
    • Label
    • Initial value
    • Description
  • Balancing Rule
    • Label
    • Balancing Set label
    • Description
  • Transformation Rule
    • Label
    • Pre-calculation label
    • Pre-calculation comments
    • Pre-calculation condition comment
    • Financial-Case label
    • Financial-Case description
    • Output-Event label
    • Output-Event description
    • Output-Event comments
    • Description
  • Enrichment Rule, Mapping Template
    • Label
    • Description
    • Comments
  • Audit Rule
    • Label
    • Audit Traces label
    • Description
  • Input-Event
    • Label
    • Segment Types label
    • Phases label
    • Description

Broadcast in disconnected mode

A container can be deployed on several Rule Engines and there is no way of knowing in advance the operating system or encoding type of the target  Rule Engine.

When the container is created, the Folder encoding attribute of the objects is stored in the product.xml file. If the object Folder uses UTF-16, the container contains the movements files (mvt.mvt and ctx.mvt) generated in little-endian and big-endian formats.

When the container is deployed, if the encoding does not correspond to what is expected, deployment is stopped.

Examples

Restrictions of use

Mapping expressions

You are not allowed to use Unicode characters to create a mapping expression. You can, however, enter your UTF-16 expression in the Initial value of a Variable then use this Variable in your mapping expression.

Packed data

You are not allowed to use packed data in UTF-16 Folders. You can however, copy or import packed data but the object will not be checked.

Table objects

In a UTF-16 folder, a Table object argument cannot exceed 110 characters. If it does, the object will not be checked.

Related Links