Implementing iProcess Suite in an International Environment with Native Encoding
When implementing the iProcess Suite in an international environment, you need to consider the flow of data between the individual iProcess products that make up the iProcess Suite. Each iProcess product that needs to communicate with an external application needs to be configured to use the same character set as the external application.
An overview of steps you need to follow is:
| 1. | Identify which iProcess products you are using and the physical locations of those products. The components that require configuration for encoding are: |
| — | your host system locale |
| — | iProcess Engine database encoding |
| — | iProcess Email Plug-in |
| — | iProcess Workspace (Browser) |
| — | iProcess Technology Plug-ins |
| — | iProcess Web Services Plug-in |
| — | LDAPCONF Utility |
| 2. | On the machines that are hosting the iProcess product components, check that host system locales are using the correct character sets. |
| 3. | Set the encoding attributes for each component. See the Installation or user guides supplied with each component for information on how to do this. |
| 4. | Non-XML files (such as XFR or Abox files) are always converted from the encoding specified by the system locale. The environment variable SW_FILE_ENCODING does not work in native mode. |