Specifying code pages per input type

If an input connector receives different types of input (XML, page formatted, etc.), and if the input types are encoded using different code pages, you can specify one code page per input type. See the Design Center documentation for information about filter chains per input type.

To specify the code pages

1	Create a filter chain, or use an existing filter chain.

2	Open the filter chain.

3	In the filter chain editor, right-click the flow bar and select Add Filter > Codepage Filter. A new code page filter is added to the flow bar.

4	From the Code page drop-down list, select the appropriate code page.

5	Save the filter chain and close the filter chain editor.

6	Repeat steps 1 through 5 for each input type and code page.

7	In the Project browser, right-click the Project node and select Project Export Settings. The Project Export Settings dialog opens.

8	Select the InputAnalyzer tab.

9	In the Available connectors list, select the connector.

10	For each input type in the Input Analyzer settings list, click the Select a Filter Chain icon and browse to and select the filter chain that contains the code page filter for the input type.

Note:

If you connect a code page filter to the connector in both the Platform and in the Project Export Settings dialog, the StreamServer will not start.

To specify the byte order for UCS-2 encoded data

For the UTF-16 encoding schemes, each character code unit is represented by two bytes. When you select UCS-2 as code page, you must also specify how the bytes are ordered for each code unit – most significant byte first or last.

From the Byte order drop-down list, select the appropriate option.

Option	When to select
Most significant byte first (Big Endian)	When the input is encoded using the encoding schemes UTF-16BE (big endian without byte order mark) or UTF-16 (big endian with or without byte order mark)
Most significant byte last (Little Endian)	When the input is encoded using the encoding schemes UTF-16LE (little endian without byte order mark) or UTF-16 (little endian with byte order mark).

Example 3

Code page filters in the Runtime configuration.

In this example the input connector receives ISO 8859-15 encoded page formatted data, and ISO 8859-2 encoded XML formatted data. A code page filter with the code page ISO 8859-15 is connected to the PageIN branch, and a code page filter with the code page ISO 8859-2 is connected to the XMLIN branch.