Using iProcess Suite With a Multi-Byte Character Encoding Environment

The following diagram shows the iProcess Suite in an environment that uses one multi-byte native character set.

In this example:

•

When text is entered in Japanese into the external application the data is encoded using UTF-8. UTF-8 is used to send the data from the external application to the web server.

•

The web server converts the data from UTF-8 to Shift-JIS (native encoding) and sends the data to iProcess Engine.

•

The iProcess Engine inserts the data into the iProcess Database.

•

The iProcess Database stores the data as Shift-JIS (native encoding).

Note that:

•

iProcess Engine supports a variety of character sets as its native character encoding. However, iProcess Engine still needs to handle data in other encodings. Therefore, iProcess Engine provides the functionality to convert different character encodings into its native character encoding.

•

It does not matter if the machines hosting the iProcess Database, iProcess Engine, and iProcess Web Services Server and Client Plug-ins are all in separate locations to the machines hosting the external applications.