IBM E02HMLL-I Implementation Guide - Page 144
Completing, configuration, Using, Connector, Configurator, Express, globalized, environment
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 144 highlights
v In a directory that you specify. v In stand-alone mode, as a file with a *.cfg extension in a directory folder. For details about using projects in System Manager, and for further information about deployment, see the User Guide for IBM WebSphere Business Integration Server Express. Completing the configuration After you have created a configuration file for a connector and modified it, make sure that the connector can locate the configuration file when the connector starts up. To do so, open the startup file used for the connector, and verify that the location and file name used for the connector configuration file match exactly the name you have given the file and the directory or path where you have placed it. Using Connector Configurator Express in a globalized environment Connector Configurator Express is globalized and can handle character conversion between the configuration file and the integration broker. Connector Configurator Express uses native encoding. When it writes to the configuration file, it uses UTF-8 encoding. Connector Configurator Express supports non-English characters in: v All value fields v Log file and trace file path (specified in the Trace/Log files tab) The drop list for the CharacterEncoding and Locale standard configuration properties displays only a subset of supported values. To add other values to the drop list, you must manually modify the \Data\Std\stdConnProps.xml file in the product directory. For example, to add the locale en_GB to the list of values for the Locale property, open the stdConnProps.xml file and add the line in boldface type below: String ja_JP ko_KR zh_CN zh_TW fr_FR de_DE it_IT es_ES pt_BR en_US en_GB en_US 132 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide