IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Email > Reference > Outbound configuration properties

Resource adapter properties

A resource adapter contains properties such as the adapter ID and logging and tracing options specific to the adapter. You can set the logging and tracing properties using the external service wizard during adapter configuration. You can set or change any of the properties using the Process Administrative Console.

The following table lists and describes the resource adapter properties. A more detailed description of each property is provided in property details tables that follow the table. For information about how to read the property details tables in the sections that follow, see Guide to information about properties.

Resource adapter properties
In the wizard In the Process Administrative Console Description
Adapter ID

AdapterID

Identifies the adapter instance for PMI events and for logging and tracing.

Disguise user data as "XXX" in log and trace files HideConfidentialTrace Specifies whether to disguise potentially sensitive information by writing X strings instead of user data in the log and trace files.
(Not available) Enable HA support

Do not change this property.


Adapter ID (AdapterID)

This property identifies a specific deployment or instance of the adapter.

Adapter ID details
Required Yes
Default 001
Property type String
Usage This property identifies the adapter instance in the log and trace files, and also helps identify the adapter instance while monitoring adapters. The adapter ID is used with an adapter-specific identifier, EMARA, to form the component name used by the Log and Trace Analyzer tool.

For example, if the adapter ID property is set to 001, the component ID is EMARA001.

If you run multiple instances of the same adapter, ensure that the first eight characters of the adapter ID property are unique for each instance so that you can correlate the log and trace information to a particular adapter instance. By making the first seven characters of an adapter ID property unique, the component ID for multiple instances of that adapter is also unique, allowing you to correlate the log and trace information to a particular instance of an adapter.

For example, when you set the adapter ID property of two instances of WebSphere Adapter for Email to 001 and 002. The component IDs for those instances, EMARA001 and EMARA002, are short enough to remain unique, enabling you to distinguish them as separate adapter instances. However, instances with longer adapter ID properties cannot be distinguished from each other. If you set the adapter ID properties of two instances to Instance01 and Instance02, you will not be able to examine the log and trace information for each adapter instance because the component ID for both instances is truncated to EMARAInstanc.

For inbound processing, the value of this property is set at the resource adapter level. For outbound processing, the value can be set both at the resource adapter level and the managed connection factory level. After you use the external service wizard to configure the adapter for outbound processing, you can set the resource adapter and managed connection factory properties independently. If you use the IBM Integration Designer assembly editor or the administrative console to reset these properties, ensure that you set them consistently, to prevent inconsistent marking of the log and trace entries.

Globalized Yes
Bidi supported No


Disguise user data as "XXX" in log and trace files (HideConfidentialTrace)

This property specifies whether to replace user data in log and trace files with a string of X's to prevent unauthorized disclosure of potentially sensitive data.

Disguise user data as "XXX" in log and trace files details
Required No
Possible values

True
False

Default False
Property type Boolean
Usage If you set this property to True, the adapter replaces user data with a string of X's when writing to log and trace files.

For inbound processing, the value of this property is set at the resource adapter level. For outbound processing, the value can be set both at the resource adapter level and the managed connection factory level. After you use the external service wizard to configure the adapter for outbound processing, you can set the resource adapter and managed connection factory properties independently. If you use the IBM Integration Designer assembly editor or the administrative console to reset these properties, ensure that you set them consistently, to prevent inconsistent marking of the log and trace entries.

Globalized No
Bidi supported No


Enable high availability support (enableHASupport)

Do not change this property. It must be set to true.

Outbound configuration properties


Related concepts:

Inbound processing

Outbound processing


Related tasks:

Setting deployment and runtime properties for inbound processing

Setting deployment and runtime properties for simple email data type

Setting deployment and runtime properties for generic email data type

Setting deployment and runtime properties for user-defined data type

Configure the module using the simple email data type

Configure the module using the generic email data type

Configure the module using the user-defined data type


Related reference:

Guide to information about properties

Connection properties for the external service wizard

Managed connection factory properties

Interaction specification properties