Filter
Top Products
ApplicationName
Name that uniquely identifies the connector’s application. This name is used by
the system administrator to monitor the WebSphere business integration system
environment. This property must have a value before you can run the connector.
BrokerType
Identifies the integration broker type that you are using. If you are using an ICS
connector, this setting must be ICS.
CharacterEncoding
Specifies the character code set used to map from a character (such as a letter of
the alphabet, a numeric representation, or a punctuation mark) to a numeric value.
Note: Java-based connectors do not use this property. A C++ connector currently
uses the value ASCII for this property. If you previously configured the
value of this property to ascii7 or ascii8, you must reconfigure the
connector to use either ASCII or one of the other supported values. To
determine whether a specific connector is written in Java or C++, see the
installing and configuring chapter of its adapter guide.
Important: By default only a subset of supported character encodings display in
the drop list. To add other supported values to the drop list, you must
manually modify the \Data\Std\stdConnProps.xml file in the product
directory. For more information, see the appendix on Connector
Configurator.
Attention: Do not run a non-internationalized connector against InterChange
Server version 4.1.1 if you cannot guarantee that only ISO Latin-1 data will be
processed.
The default value is ascii.
ConcurrentEventTriggeredFlows
Determines how many business objects can be concurrently processed by the
connector controller for event delivery. Set the value of this attribute to the number
of business objects you want concurrently mapped and delivered. For example, set
the value of this property to 5 to cause five business objects to be concurrently
processed. The default value is 1.
Setting this property to a value greater than 1 allows a connector controller for a
source application to simultaneously map multiple event business objects, and to
simultaneously deliver them to multiple collaboration instances. Setting this
property to enable concurrent mapping of multiple business objects can speed
delivery of business objects to a collaboration, particularly if the business objects
use complex maps. Increasing the arrival rate of business objects to collaborations
can improve overall performance in the system.
Note: To implement concurrent processing for an entire flow (from a source
application to a destination application) also requires that the collaboration
be configured to use multiple threads and that the destination application’s
application-specific component be able to process requests concurrently. To
configure the collaboration, set its Maximum number of concurrent events
property high enough to use multiple threads. For an application-specific
component to process requests concurrently, it must be either
38 Adapter for i2 User Guide