IBM E02HMLL-I Implementation Guide - Page 143
Saving, configuration
![]() |
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 143 highlights
Resources The Resource tab allows you to set a value that determines whether and to what extent the connector agent will handle multiple processes concurrently, using connector agent parallelism. Not all connectors support this feature. If you are running a connector agent that was designed in Java to be multi-threaded, you are advised not to use this feature, since it is usually more efficient to use multiple threads than multiple processes. Setting trace/log file values When you open a connector configuration file or a connector definition file, Connector Configurator Express uses the logging and tracing values of that file as default values. You can change those values in Connector Configurator Express. To change the logging and tracing values: 1. Click the Trace/Log Files tab. 2. For either logging or tracing, you can choose to write messages to one or both of the following: v To console (STDOUT): Writes logging or tracing messages to the STDOUT display. Note: You can only use the STDOUT option from the Trace/Log Files tab for connectors running on the Windows platform. v To File: Writes logging or tracing messages to a file that you specify. To specify the file, click the directory button (ellipsis), navigate to the preferred location, provide a file name, and click Save. Logging or tracing message are written to the file and location that you specify. Note: Both logging and tracing files are simple text files. You can use the file extension that you prefer when you set their file names. For tracing files, however, it is advisable to use the extension .trace rather than .trc, to avoid confusion with other files that might reside on the system. For logging files, .log and .txt are typical file extensions. Data handlers The data handlers section is available for configuration only if you have designated a value of JMS for DeliveryTransport and a value of JMS for ContainerManagedEvents. Adapters that make use of the guaranteed event delivery enable this tab. See the descriptions under ContainerManagedEvents in the Standard Properties appendix for values to use for these properties. Saving your configuration file After you have created the configuration file and set its properties, you need to deploy it to the correct location for your connector. Save the configuration in an ICL project, and use System Manager to load the file into InterChange Server Express. The file is saved as an XML document. You can save the XML document in three ways: v From System Manager, as a file with a *.con extension in an Integration Component Library, or Chapter 7. Configuring connectors 131
![](/manual_guide/products/ibm-e02hmlli-implementation-guide-69bfebe/143.png)