A Oracle JCA Adapter Properties
This appendix describes the JCA and binding properties that are applicable to Oracle JCA Adapters.
A normalized message is simplified to have only two parts: properties and payload. In Oracle BPEL Process Manager and Oracle Mediator, you can access, manipulate, and set headers with varying degrees of user interface support. For example, you can preserve a file name from the source directory to the target directory by propagating it through message headers.
Oracle JCA adapters transmit header information through Normalized Message properties (with the exception of the Oracle JCA Adapter for AQ's payload header).
Binding properties are message header properties for the service and reference binding components included in a deployed SOA composite application.
If you are configuring newly created adapters in Reference Configuration mode, you can modify JCA Adapter endpoint properties directly in the Adapter Configuration Wizard. See JCA Endpoint Properties in the Adapter Configuration Wizard.
This appendix includes the following sections:
For more information, see Configuring Service and Reference Binding Components in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
JCA Endpoint Properties in the Adapter Configuration Wizard
Beginning with Release 12c (12.2.1.4), you can create either a Reference Configuration domain or a Classic domain on the Templates screen in the Configuration Wizard during installation. A Reference Configuration domain guards servers from running into out-of-memory, stuck threads, endpoint connectivity, and database issues. A Reference Configuration domain supports SOA, OSB, and B2B topologies. The templates in these products include Reference Configuration in their names, and are the default templates listed in the Configuration Wizard for these products.
Developing a SOA or Service Bus project in Reference Configuration mode means that you enable Reference Configuration settings in JDeveloper so that new adapters that you create in the application will have special JCA endpoint properties defined in their source files. You can modify these properties directly in the Adapter Configuration Wizard for projects newly created in Release 12c (12.2.1.4). The changes are updated in the corresponding target file.
Note:
You will not see JCA Endpoint Properties screens in the Adapter Configuration Wizard for projects migrated from previous releases even if you have enabled Reference Configuration settings in adapters in JDeveloper.For more information about the Reference Configuration domain and settings, see:
- For SOA projects:
-
Selecting the Configuration Template for Oracle SOA Suite in Installing and Configuring Oracle SOA Suite and Business Process Management
-
Configuring a Reference Configuration Domain in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
- Developing SOA Projects in Reference Configuration Mode in Developing SOA Applications with Oracle SOA Suite
-
- For Service Bus projects:
-
Selecting the Configuration Templates for Oracle Service Bus in Installing and Configuring Oracle Service Bus
-
Configuring a Reference Configuration Domain in Administering Oracle Service Bus
-
Developing Service Bus Projects in Reference Configuration Mode in Developing Services with Oracle Service Bus
-
Table A-1 JCA Properties in the Adapter Configuration Wizard
Property | Adapter | Inbound | Outbound | Target File |
---|---|---|---|---|
|
File Adapter |
|
|
JCA file
|
MQ Adapter |
|
|
JCA file
|
|
DB Adapter |
|
|
JCA file
|
|
JMS Adapter |
|
|
composite.xml - as binding properties
|
|
AQ Adapter |
|
|
composite.xml - as binding properties
|
|
|
JMS Adapter File and FTP Adapter |
|
|
composite.xml - as binding properties
|
|
DB Adapter (Polling Only) |
|
|
JCA file
|
|
File Adapter (Write Only) |
|
|
JCA file
|
|
File Adapter (Read Only) |
|
FileAdapter (Chunked Read only)
|
JCA file
|
|
All Adapters |
|
|
composite.xml - as binding properties
|
|
All Adapters |
|
|
composite.xml - as binding properties
|
|
File Adapter |
|
|
JCA file
|
Detailed information related to adapter properties such as descriptions and recommended values is provided in the topics for each adapter.
Generic Oracle JCA Adapter Properties
Table A-2 describes the properties applicable to all Oracle JCA Adapters.
For properties specific to each of the Oracle JCA Adapters, see:
Table A-2 JCA Properties for all Oracle JCA Adapters
Property | Description |
---|---|
|
An optional When set to the name of the WSDL associated with the adapter's JCA file, Oracle Service Bus can automatically resolve the WSDL to allow bulk import of JCA files and related WSDL and schemas. The following example shows the <adapter-config name="FulfillmentBatch" adapter="Jms Adapter" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata" wsdlLocation="FulfillmentBatch.wsdl" > ... </adapter-config> |
Generic Oracle JCA Adapter Binding Properties
Table A-3 describes the binding properties applicable to all Oracle JCA Adapters.
For properties specific to each of the Oracle JCA Adapters, see:
Table A-3 Generic Oracle JCA Adapters Binding Properties
Property | Description |
---|---|
|
Deprecated, because each adapter now natively supports multithreading. However, the property still works and controls how many instances of a particular inbound JCA activation agent will be spawned. The property can thus be used to increase concurrency. The |
|
Set to |
|
Set to |
|
Indicates the retry interval growth factor as a positive integer. |
|
Indicates maximum number of retries before rejection. |
|
Indicates interval in seconds between retries. |
|
Indicates maximum value of retry interval |
|
Is the upper limit of the entire accumulated duration of all retries; that is, a hard limit. |
|
Default is Note that |
|
In a Clustered High Availability environment, setting this property to |
|
The interval between snapshot reports. |
|
If set to |
|
Default is |
Oracle AQ Adapter Properties
The following tables describe the properties applicable to the Oracle AQ Adapter:
-
Table A-4 JCA Properties for Oracle AQ Adapter
-
Table A-5 JCA Properties for Oracle AQ Adapter: Normalized Properties
-
Table A-6 Binding Properties for Oracle AQ Adapter
For properties applicable to all Oracle JCA Adapters, see Generic Oracle JCA Adapter Properties.
For more information, see Oracle AQ Adapter in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
Table A-4 JCA Properties for Oracle AQ Adapter
Property | Description |
---|---|
|
The name of the AQ Queue being read from or written to. |
|
The schema where the queue resides. If not specified, the schema of the current connection is used. |
|
When this property is set to |
|
When this property is set to |
|
Specify the consumer name or names that are the intended recipients for the messages enqueued by the adapter. The message remains in the queue until all recipients have dequeued the message. If the field is left empty, then all the currently active consumers are recipients. |
|
Applicable only for multiconsumer queues. If specified, only the messages targeted for the particular consumer are made available for processing. |
|
This property is used to identify the field containing the business payload if the queue is an ADT queue. You can specify an attribute of ADT to constitute a payload or an entire ADT to represent payload. In former case the 'ObjectFieldName' should be same as the attribute name of the ADT. In latter case this property is not specified. |
|
Only applicable if the |
|
When a dequeue is performed from a multiconsumer queue, it is sometimes necessary to screen the messages and accept only those that meet certain conditions. These conditions can be based on payload or queue header values and is specified using |
|
This property is valid for dequeue operations only. Enter a Boolean expression similar to the |
|
You can assign an identifier to each message, thus providing a means to retrieve specific messages at a later time. The value to enter is agreed upon between the enqueuing sender and the dequeuing receiver for asynchronous conversations. This can be overridden on a per message basis through the normalized message property, |
|
This property exposes a configurable control mechanism through which you can specify the payload size threshold in the adapter layer. The messages that have sizes beyond the configured threshold limit are rejected. If this property is not configured, it does not impose any restriction on the size of messages. |
Table A-5 JCA Properties for Oracle AQ Adapter: Normalized Properties
Property | Description |
---|---|
|
The number of failed attempts at dequeuing the message. |
|
User-assigned correlation ID. |
|
The number of seconds after which the message is available for dequeuing. |
|
The time at which the message was enqueued. |
|
The exception queue name. |
|
The number of seconds before the message expires. This parameter is an offset from the |
|
The hexadecimal representation of the message ID for the dequeued message. |
|
The hexadecimal representation of the original message ID. |
|
Priority of the message. A smaller number indicates a higher priority. The priority can be any number. The default value is zero. |
|
The list of recipients for this message, separated by commas. This overrides |
|
Contains string or DOM of current headers (XML DOM representation of payload headers.) |
Table A-6 Binding Properties for Oracle AQ Adapter
Property | Description |
---|---|
|
The time for which the Oracle AQ Adapter waits before trying to re-create a connection after a connection is lost. The default value is 15s. |
|
It is the interval after which the |
|
Specifies the number of poller threads that are created when an endpoint is activated. The default value is 1. |
Coherence Adapter Properties
The following tables describe the properties applicable to the Coherence Adapter:
Table A-7 Coherence Adapter JCA Properties
Property | Description | Default Value |
---|---|---|
|
Identifies a particular Coherence cache to be used for a particular operation. A non-retriable error occurs when the Cache as specified by the entry |
None |
|
Identifier for a Cache Entry. |
None |
|
Identifies the java type of the value to be used as the key (currently any simple type from java.lang package). |
None |
|
Fully qualified class name that identifies the object stored to/retrieved from cache. When you indicates to store XML into cache, you do not need to specify |
None |
|
Used to specify the subset of cache that the operation should be applied to. The filter expression is based on CohQL and support use of bind variables. |
None |
|
Specifies the number of items to be returned when a query operation is executed. It is only applicable for cache operations associated with remote caches. |
None |
|
The number of milliseconds until the cache entry will expire. It is only applicable for cache operations associated with non-transactional caches. |
|
|
The name of the index to be added to the cache. To create an index on the attribute ' |
None |
|
Boolean that specified whether contents of indexed information is ordered or not. |
|
|
Indicates the name of the Metadata mapping file that helps in POJO to. XML and XML to POJO conversion. |
None |
|
The operation to be carried out on the Cache identified by |
None |
|
Boolean that allows for only Cache identifiers (keys) to be returned when a Query operation is performed |
False |
Table A-8 Coherence Adapter Normalized Properties
Property | Description |
---|---|
|
Name of the Cache to be used for Coherence operations. This overrides ' |
|
Identifies a cache entry. This overrides ' |
|
Specify the filter to be used when performing Coherence operations. This overrides ' |
Table A-9 Coherence Adapter Connection Factory Properties
Name | Description | Value |
---|---|---|
|
Specifies the JNDI name of connection factory provided by |
|
|
Name of the cache service to be associated with the connection. |
Leave blank for Remote cache |
|
Location of cache configuration file that defines the cache and extend client settings |
- |
|
Specifies if the classloader used for cache operations is based on the domain classes as bundled with the composite or based on the Values are If
|
|
|
Specifies if the Extend Proxy is a standalone or running as part of WLS server. If false, it is a standalone Extend Proxy; otherwise not. Applicable only for the Remote Case. |
|
|
Specifies the location of domain classes that will be used for the cache operations. |
- |
Oracle Database Adapter Properties
The following tables describe the properties applicable to the Oracle Database Adapter:
-
Table A-10 JCA Properties for Oracle Database Adapter: Instance Properties
-
Table A-11 JCA Properties for Oracle Database Adapter: Normalized Message Properties
For properties applicable to all Oracle JCA Adapters, see Generic Oracle JCA Adapter Properties.
For more information, see:
-
Oracle Database Adapter in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
-
Normalized Message Properties in Developing SOA Applications with Oracle SOA Suite.
Table A-10 JCA Properties for Oracle Database Adapter: Instance Properties
Property | Description |
---|---|
|
Either this property or xADataSource name is a mandatory property, or both. Refers to the JNDI name ( |
|
The default value is |
|
This is a mandatory property. This points to the type of database being connected to. The suggested values for this property are:
You also can give the full package and class name of a subclass of |
|
The default value is |
|
The default value is |
|
The default value is |
XADataSourceName |
This is a mandatory property. It specifies the JNDI name ( |
Table A-11 JCA Properties for Oracle Database Adapter: Normalized Message Properties
Property | Description |
---|---|
|
Inbound/Outbound. |
|
Outbound. |
|
Outbound. You cannot assign values to the |
|
Outbound. When set, specifies |
|
Outbound. When set, specifies |
|
Outbound. Values are |
|
Outbound. When set, specifies |
|
Outbound. Set to define the roles associated with the proxy user. The value should be a |
|
Outbound. When set, specifies |
|
Outbound. You cannot assign values to the |
|
Outbound. |
Footnote 1
For more information, see Proxy Authentication Support.
Oracle File and FTP Adapters Properties
The following tables describe the properties applicable to the Oracle File and FTP Adapters:
-
Table A-12 JCA Properties for Oracle File and FTP Adapters
-
Table A-13 JCA Properties Specific to Oracle FTP Adapter
-
Table A-14 Binding Properties for Oracle File and FTP Adapters
-
Table A-15 Binding Properties Specific to Oracle FTP Adapter
-
Table A-16 JCA Properties for Oracle File Adapter: Normalized Properties
-
Table A-17 JCA Properties for Oracle FTP Adapter: Normalized Properties
For properties applicable to all Oracle JCA Adapters, see Generic Oracle JCA Adapter Properties.
Table A-12 JCA Properties for Oracle File and FTP Adapters
Property | Description |
---|---|
|
If set to The file name can be specified either in the JCA file for the outbound operation or
in the |
|
If set to |
|
The batch size for the batching transformation. |
|
The character set for the attachment. This property is not used internally by the Oracle File and FTP Adapters, and it is meant for third-party applications that process the attachments published by the Oracle File and FTP Adapters. |
|
The chunk size for the chunked interaction operation. This property is applicable only to BPEL. Do not set it in Oracle Service Bus. |
|
The maximum number of translation activities that can be allowed to execute in parallel for a particular outbound scenario. The translation step during the outbound operation is CPU-intensive and must be guarded because it might cause other applications or threads to starve. The maximum value is |
|
The mime-type of the attachment. This property is not used internally by the Oracle File and FTP Adapters, and it is meant for third-party applications that process the attachments published by the Oracle File and FTP Adapters. |
|
If set to |
|
When you choose multiple directories, the generated JCA files use semicolon ( |
|
Used for outbound batching. When the time specified elapses, the outgoing file is
created. The property is of type |
|
The encoding used for the attachment. This property is not used internally by the Oracle File and FTP Adapters, and it is meant for third-party applications that process the attachments published by the Oracle File and FTP Adapters. |
|
Specifies the pattern for types of files to be excluded during polling. The property
is of type |
|
Specifies a static single file name during the write operation. |
|
This property is used for the naming convention for the outbound write operation file. |
|
Used for outbound batching. The outgoing file is created when the file size
condition is met. The property is of type |
|
Specifies the pattern for types of files to pick up during polling. The property is of
type |
|
Works in conjunction with deployment validation. If the inbound directory cannot be
read or written to, then the adapter throws a failure and rolls back
the deployment. However, if set to |
|
Specifies the sorter that the Oracle File and FTP Adapters use to sort files in inbound. You can set this property to either:
|
|
Specifies the logical directory where the inbound Oracle File and FTP Adapters
archive files in case of failures such as errors encountered during
translation or publishing. The property is of type
If not specified, the default archive directory is used. The default
archive directory is typically under the control directory
|
|
Specifies the logical directory in which to archive successfully processed files. The
property is of type |
|
Specifies the logical input directory to be polled. The property is of type
|
|
Specifies the maximum number of files that the Oracle File or FTP Adapter submits
for processing in each polling cycle. For example, if the inbound
directory has 1000 files and Recommended value for |
|
Specifies the minimum age of files to be retrieved. This specification enables a large file to be completely copied into the input directory before it is retrieved for processing. The age is determined by the last modified time stamp. For example, if you know that it takes three to four minutes for a file to be written, then set the minimum age of pollable files to five minutes. If a file is detected in the input directory and its modification time is within five minutes of the current time, then the file is not retrieved because it is still potentially being written to. |
|
Used for outbound batching. The outgoing file is created when the number of messages
condition is met. The property is of type |
|
Specifies the physical directory where the inbound Oracle File and FTP Adapters
archive files in case of failures such as errors encountered during
translation or publishing. The property is of type
If not specified, the default archive directory is used. The default
archive directory is typically under the control directory
|
|
Specifies where to archive successfully processed files. The property is of type
|
|
Specifies the physical input directory or directories to be polled. The property is
of type |
|
Specifies how often to poll a given input directory for new files. The property is
of type Recommended value for |
|
This property indicates whether the file contains multiple messages and how many
messages to publish to the BPEL process at a time. The property is
of type For example, if a certain file has 11 records and this property is set to 2, then the file processes 2 records at a time and the final record is processed in the sixth iteration. Recommended values for For debatching to work, the XML schema of File Adapter also needs to
support debatching. For example, if the FileAdapter schema has
|
|
If set to |
|
Specifies the Oracle database sequence name to be used if you have configured the outbound Oracle File or FTP Adapter for High Availability. |
|
If set to |
|
The source file for the File I/O operation. |
|
The source directory for the File I/O operation. |
|
Set to the schema for the source file. |
|
Set to the root element name for the source file. |
|
Set to |
|
The target file for the File I/O operation. |
|
The target directory for the File I/O operation. |
|
The schema for the target file. |
|
The root element name for the target file. |
|
Set to |
|
If this property is available, then the adapter creates its own processor threads rather than depend on the global thread pool processor threads (by default, 4 of them). In other words, this property partitions the in-memory queue and each composite application gets its own in-memory queue.
Recommended value for |
|
The name of the trigger file that activates the inbound Oracle File or FTP Adapter. |
|
The directory path where the Oracle File or FTP Adapter looks for the trigger files. |
|
Defines the strategy that the Oracle File or FTP Adapter uses to look for the
specified trigger file in the trigger file directory. The acceptable
values are |
|
Set to |
|
Defines where an error is archived during an Inbound Read. During an Inbound Read
operation, if a malformed XML file is read, the malformed file
results in an error. The errored file is by default sent to the
remote file system for archival. The errored file can be archived at
a local file system by specifying the useRemoteErrorArchive property
in the jca file and setting that property to false. The default
value for this property is |
|
If set to This is typically used in large payload scenarios where the inbound adapter is used as a notifier. |
|
If set to |
|
Set to the XSL transformer between the source and the target. |
Table A-13 JCA Properties Specific to Oracle FTP Adapter
Property | Description |
---|---|
|
Set to either |
|
Set to |
|
Set to |
|
If set to |
|
If set to |
Table A-14 Binding Properties for Oracle File and FTP Adapters
Property | Description |
---|---|
|
Lets you control the behavior of the inbound Oracle File Adapter during the polling operation. If set to |
|
If set to |
|
Limits the number of levels the File/FTP adapter recurses into input directory to poll for files |
|
Applicable only if |
|
Overrides the encoding specified in the NXSD schema for inbound Oracle File and FTP Adapters. |
|
If set to |
|
Lets you control the size of rejected messages for inbound Oracle File and FTP
Adapter partner link. For example, if you set it to
|
|
Number of times that inbound Oracle File and FTP Adapters retry to establish a database connection in distributed polling scenarios. |
|
Number of milliseconds after which inbound Oracle File and FTP Adapters retry to establish a database connection in distributed polling scenarios. |
|
Set to the class name that specifies the mutex for the outbound write operation. This
class must extend the |
|
If set to |
|
Used by the inbound highly available adapter when using
And when the file is processed completely, the The table Set the property to a large value like |
|
Used by the inbound highly available adapter when using
|
|
Used by the inbound adapter to configure the recovery interval in case of errors. For example, if the physical directory is nonexistent, then the adapter uses this value to perform periodic sleep or wakeup checks to check whether the physical directory has been created and is accessible. |
|
If set to |
|
Used by inbound Oracle File and FTP Adapters
during read-only polling in a clustered environment.If set to
|
Table A-15 Binding Properties Specific to Oracle FTP Adapter
Property | Description |
---|---|
|
Used by the Oracle FTP Adapter to handle time zone issues, typically to convert the time difference between the FTP server and the system on which the Oracle FTP Adapter is running to millisecond. |
|
Defines the time-out for the control socket to the FTP server. Specified in milliseconds. |
Table A-16 JCA Properties for Oracle File Adapter: Normalized Properties
Property | Description |
---|---|
|
Specifies the name of the file read from the inbound directory or written to the outbound directory. |
|
Specifies the name of the directory from which file is read from or written to. |
|
Specifies the size of the file published from the inbound Oracle File Adapter. |
|
Specifies a unique identifier for the file being published from the inbound adapter. |
|
If a file has multiple messages and de-batching is used, then this normalized property specifies the message (record) number from the same batch. In this case, the |
|
Used with chunked interaction. It is used to find out if the end of file is reached. |
Table A-17 JCA Properties for Oracle FTP Adapter: Normalized Properties
Property | Description |
---|---|
|
Specifies the name of the file read from the inbound directory or written to the outbound directory. |
|
Specifies the name of the directory from which file is read from or written to. |
|
Specifies the size of the file published from the inbound Oracle File Adapter. The size can be zero. |
|
Specifies a unique identifier for the file being published from the inbound Oracle FTP Adapter. |
|
If a file has multiple messages and de-batching is used, then this normalized property specifies the message (record) number from the match batch. In this case, the |
Oracle JMS Adapter Properties
The following tables describe the properties applicable to the Oracle JMS Adapter:
-
Table A-18 JCA Properties for Oracle JMS Adapter
-
Table A-19 JCA Properties for Oracle JMS Adapter: Normalized Properties
-
Table A-20 Binding Properties for Oracle JMS Adapter
For properties applicable to all Oracle JCA Adapters, see Generic Oracle JCA Adapter Properties.
For more information, see Oracle JMS Adapter in Administering Oracle SOA Suite and Oracle Business Process Management Suite
Table A-18 JCA Properties for Oracle JMS Adapter
Property | Description |
---|---|
|
This property is applicable for a synchronous request-reply scenario. When set to |
|
Only applicable when dealing with message of type |
|
Represents the delivery mode to use. The message producer's default delivery mode is |
|
The name of the queue or topic being read from or written to. |
|
Name used to identify a durable subscription. When working with durable subscriptions ensure that ClientID is also specified in addition to |
|
When this property is set to |
|
A string whose syntax is based on a subset of the SQL92 conditional expression syntax and lets you specify the messages adapter is interested in, by using header field references and property references. Only messages whose header and property values match the selector are delivered. |
|
Only applicable when dealing with messages of type |
|
This property exposes a configurable control mechanism through which you can specify the payload size threshold in the adapter layer. The messages that have sizes beyond the configured threshold limit are rejected. If this property is not configured, it does not impose any restriction on the size of messages |
|
This property specifies the type of JMS message that is being dequeued or enqueued by the adapter. For Map messages the value is |
|
Represents priority for this message. The message producer's default priority is 4. This can be overridden on a per message basis using normalized message property |
|
This property is applicable for a synchronous request-reply scenario and specify the name of destination for receiving a reply. |
|
This property is applicable for a synchronous request-reply scenario and specifies the timeout for receiving a reply in milliseconds. The default value is |
|
This property is applicable for a synchronous request-reply scenario and specifies the name of destination for sending a message. |
|
Represents the message's lifetime (in milliseconds). The message producer's default time to live is unlimited; the message never expires. A value of |
|
Specifies the use of the Unit-of-Order feature. The WebLogic Server Unit-of-Order feature enables a message producer or group of message producers acting as one, to group messages into a single unit that is processed sequentially in the order the messages were created. |
|
Deprecated. The only value of this property supported in the current version is false. A value of |
Table A-19 JCA Properties for Oracle JMS Adapter: Normalized Properties
Property | Description |
---|---|
|
This property specifies the destination to which the message is sent, and is set by the JMS producer. |
|
This property represents the properties that define the context used to look up the destination object to which the message must be sent |
|
This property is set by both producers and consumers for linking the response message with the request message. This is an optional attribute. |
|
This property specifies the JMS message type. |
|
This is an optional attribute that indicates the destination to which a message reply must be sent. |
|
This property is used by the consumer to set a priority number between 0 and 9. Larger numbers represent a higher priority. |
|
This property specifies the duration of the message before the expiration. When a message's expiration time is reached, the JMS provider should discard it. |
|
This property is set to |
|
This property is specifies a unique message identifier. The exact scope of uniqueness is provider-defined. |
|
This property indicates whether a message is being redelivered. If a client receives a message with the |
|
This property is specifies the time when the message was handed off to the JMS provider to be sent. |
|
This property represents any custom (application-specific) properties of the message. The supported properties conforms to the one allowed according to JMS specification. If an invalid property value is specified, the adapter warns the user (captured in the log files) and ignores the invalid property. |
|
This property represents any |
|
This property overrides the value specified using the property |
|
Use this Normalized Property to get the Unit of order value set on the Inbound JMS Message in the receive activity of BPEL. |
Table A-20 Binding Properties for Oracle JMS Adapter
Property | Description |
---|---|
|
This property is superseded by the newer property |
|
This property can be set to When You do not see this property in the JDeveloper user interface as a binding property on the Service side. You must manually add the property in the
|
|
This property specifies the number of poller threads that are created when an endpoint is activated. The default is Retaining the default value as a higher value or value higher than the |
|
This property specifies the timeout value used for the synchronous receive call. It is the time after which |
|
This property is not supported anymore. |
|
This property is used by the inbound connection retry layer. The time for which the Oracle JMS Adapter waits before trying to re-create a connection after a connection is lost. The default value is |
|
This property specifies whether to declaratively impose custom property settings on Destination objects received during inbound request/reply scenarios. |
|
This property specifies whether to whether you want to use a correlation ID for correlation. Values are |
|
This property specifies whether to whether you want to use a message ID for correlation. Values are |
|
This property specifies if the reply message TTL is set to 0 (message never expires) or some specified value related to message expiration. The default value is |
|
If the same small number of JMS receivers are used for the same request destination repeatedly, then set this property to |
|
This property is applicable for a synchronous request-reply scenario. If set to |
|
This property is used to bypass headers. For scenarios in which a composite does not use or produce the headers, set to |
LDAP Adapter Properties
The following tables describe the properties applicable to the LDAP Adapter:
-
Table A-21 LDAP Adapter Connection Properties
-
Table A-22 LDAP Adapter JCA Artifacts for Entry Change Notification
-
Table A-23 LDAP Adapter JCA Artifacts for Change Log Notification
-
Table A-24 LDAP Adapter JCA Artifacts for Search Operation
-
Table A-25 LDAP Adapter DSML JCA Artifacts
-
Table A-26 LDAP Adapter Delete Operation JCA Artifacts
-
Table A-27 LDAP Adapter Add Operation JCA Artifacts
-
Table A-28 LDAP Adapter Modify Operation JCA Artifacts
-
Table A-29 LDAP Adapter ModifyDN Operation JCA Artifacts
Table A-21 LDAP Adapter Connection Properties
Property | Allowed Values | Description |
---|---|---|
|
Name or IP address of the host machine. |
Machine where the LDAP server is hosted. |
|
|
|
|
JDBC datasource JNDI where RCU schema is installed. This data store is used to persist the last change number. This property value is useful for last incremental synchronization scenario. (It is required to use if the LDAP adapter must be used on the inbound direction). |
JNDI string location pointing to a valid XA data source. |
|
Sets the operation timeout. If the response is not received by the Directory Server in the timeout period, the operation will be abandoned and an exception will be raised. |
|
|
secret |
Not required |
|
||
|
Key management protocol, not required. |
|
|
|
If mentioned, the client will blindly trust any certificated that the server might present. Required only if |
|
The JSSE provider name. |
|
|
Integer value |
Port where the LDAP service is running on the host. |
|
|
Indicates that LDAP adapter should use SSL to secure communication with the directory server. The server must be configured to listen in SSL mode and the value for the port argument must be one where the server is listening for SSL based connections. |
|
|
Use start TLS extended operation to secure communication with a directory server over a non-encrypted channel. Port in this case is listening for clear-text LDAP Connections. |
|
|
If mentioned, the client will blindly trust any certificated that the server might present. |
|
Must be mentioned if one of |
Specifies path to the JKS trust store file that the client use for server authentication. |
|
Specifies the password needed to access the trust store contents. In most cases, no trust store password is required. This should not be used in conjunction with the trust store password file option. |
|
|
Set the protocol version enabled for secure connections with the directory server. The protocol must be supported by the SSL Context. |
|
|
A String. Uses the default set of SSL cipher suites provided by the server's JVM. List of comma separated cipher suites allowed by the jsse provider. |
Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication. |
Table A-22 LDAP Adapter JCA Artifacts for Entry Change Notification
Property Name | Allowed Values | Description |
---|---|---|
|
Valid DN under which events should be reported. |
Notify events under this entry. |
|
Restricted string with value in: |
Scope of event source under the configured basedn. |
|
Value in
|
If |
|
Valid string representation of LDAP filter. |
Advanced filter condition. Events that satisfy the given filter condition only will be published by the adapter. |
|
CSV list of all the attributes to return as part of the event. |
- |
|
String |
Attributes delimiter can be explicitly defined in case the default delimiter ',' is not appropriate. |
|
|
When set to |
|
Positive integer. Default = |
Maximum number of entries returned as part of a search operation. This can be configured on the DS side as well. Lower of the two values will take effect. |
|
Integer value specifying a page size. Note: |
Maximum number of events that should be published in a page. |
|
Integer value in seconds. Default = |
Maximum time the server should wait before returning the results. |
|
String value: one of |
Persistent search option has been deprecated in the first release. |
|
Integer value in seconds. Default = |
Polling interval before conducting subsequent searches for new events. |
Table A-23 LDAP Adapter JCA Artifacts for Change Log Notification
Property Name | Allowed Values | Description |
---|---|---|
|
Integer value in seconds. Default = |
Polling interval before conducting subsequent searches for new events. |
|
Value in
Note that |
If |
|
String value in |
|
|
Integer value in seconds. Default = |
Maximum time the server should wait before returning the results. |
|
Integer value in seconds. Default = |
Maximum number of events that should be published in one trip. |
|
Integer value specifying a page size. Note that |
- |
Table A-24 LDAP Adapter JCA Artifacts for Search Operation
Property Name | Allowed Values | Description |
---|---|---|
|
Restricted string with value in:
|
Behavior for handling alias entries while processing the search. |
|
Restricted string with value in:
By default, the LDAP adapter ignores all referral suggestions unless explicitly asked to follow or throw exception. |
Alternate locations where additional entries may be searched/matched as part of a search request. |
|
Positive integer. Default = |
Number of alternate locations participating in search referrals. |
|
|
When set to |
|
String value, delimited list of all the attributes that must be returned as part of this search response. |
The default delimiter is ' Only names attributes will be included as part of search response. |
|
String |
attributes delimiter can be explicitly defined in case the default delimiter ' |
|
Restricted string with value in: |
Defines the search scope. This has to be defined at service deployment to control malignant search request from controlling server resources. |
|
Integer value in seconds. Default = |
Maximum number of entries returned as part of a search operation. This can be configured on the DS side as well. Lower of the two values will take effect. |
|
Integer value in seconds. Default = |
Maximum time in seconds the server should wait before returning the results. |
|
|
When set to |
Table A-25 LDAP Adapter DSML JCA Artifacts
Property Name | Allowed Values | Description |
---|---|---|
|
Integer value. Default = |
DSML contains a batch request. This batch request can potentially contain millions of LDAP operation requests. This property is used to control the maximum number of permissible operation requests that can be passed to the LDAP adapter through a single DSML batch request. |
Table A-26 LDAP Adapter Delete Operation JCA Artifacts
Property | Allowed values | Description |
---|---|---|
|
String |
To pass in one or more controls along with the operation. |
|
|
A delete operation fails if the entry to delete doesn't exist in the target DS. This exception can be suppressed by specifying this condition on the interaction specification. |
Table A-27 LDAP Adapter Add Operation JCA Artifacts
Property | Allowed values | Description |
---|---|---|
|
|
Add operation fails if the entry to add already exist in the target DS. This exception can be suppressed by specifying this property on the interaction specification. |
|
CSV String |
Comma- separated list of all |
Table A-28 LDAP Adapter Modify Operation JCA Artifacts
Property | Allowed values | Description |
---|---|---|
|
String |
To pass in one or more controls along with the operation. |
Table A-29 LDAP Adapter ModifyDN Operation JCA Artifacts
Property | Allowed values | Description |
---|---|---|
|
String |
To pass in one more controls along with the operation. |
|
|
- |
Oracle MQ Series Adapter Properties
The following tables describe the properties applicable to the Oracle MQ Series Adapter:
-
Table A-30 JCA Properties for Oracle MQ Series Adapter
-
Table A-31 JCA Properties for Oracle MQ Series Adapter: Normalized Properties
-
Table A-32 Connection Properties for Oracle MQ Series Adapter
-
Table A-33 Binding Properties for Oracle MQ Series Adapter
For properties applicable to all Oracle JCA Adapters, see Generic Oracle JCA Adapter Properties.
For more information, see Oracle MQ Adapter in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
Table A-30 JCA Properties for Oracle MQ Series Adapter
Property | Description |
---|---|
|
This property specifies the name of the MQ Queue for sending or retrieving messages. |
|
This property specifies the type of message: Normal, Request, Reply, or Report |
|
This property specifies the type of MQ message format, such as Default, and Request/Reply. |
|
This property specifies the message priority. Its value ranges from |
|
This property is used to set the message persistence. The message persists when this property is set to |
|
This property is used when message delivery fails. The default value is |
|
This property is used for partial delivery to a distribution list. The default value is |
|
This property is used when the size of the message is larger than the maximum limit set on the queue. The default value is |
|
This property specifies the time after which the message would be removed by the Queue Manager. The default value is |
|
This property specifies the name of the queue to which the reply or report must be sent. |
|
If this property is set, a confirmation on arrival report is sent to the |
|
If this property is set, a confirmation on delivery report is sent to the replyto queue on arrival of a message in the destination queue. The default value is |
|
If this property is set, an exception report is sent to the replyto queue when message delivery to the destination queue fails. The default value is |
|
If this property is set, an expiry report is sent to the replyto queue when a message sent to the destination queue expires. The default value is |
|
This property specifies the waiting interval for dequeuing the message in outbound MQ queue. |
|
This property is used to generate a Message Id for a reply or a report message. By default a new Message Id is generated. |
|
This property is used to generate a correlation Id for a reply or a report message. By default the message Id of the request message is used as the correlation Id. |
|
This property specifies the queue open options to use while accessing the queue. |
|
This property specifies the queue manager for the enqueue queue. Use this property only when the outbound enqueue queue resides outside the inbound queue manager. |
|
This property is used to specify a backout queue to which rejected messages from an inbound queue are to be sent. |
|
This property is used to specify the queue manager for the backout queue. Use this property only when the Backout Queue resides outside the inbound queue manager. |
|
This property is used to specify the maximum backout retry count after which rejected message is sent to the backout queue. |
|
This property is used to specify intervel between the backout retries. The default value is 5 seconds. |
|
This property is used to specify the number of backout retries. The default value is 3. |
|
This property is used for sending the report to the Normal Message Queue. |
|
This property is used when the Primary Queue Manager specified in JNDI connection cannot access the queue. |
|
This property is used to specify the elements of the distribution list for enqueuing the message. |
|
This property specifies which messages must be retrieved from the MQ queue. Only messages whose headers and properties match the selection criteria are retrieved. |
|
This property, set to true, configures the adapter to process all messages as attachment. |
|
This property is optional and should only be specified if the "AsAttachment" property is set to true. It defines the character set of the attachment and is meant for third-party applications that process the attachments published by the Oracle MQ Series Adapter. |
|
This property is optional and should only be specified if the "AsAttachment" property is set to true. It defines the encoding of the attachment and is meant for third-party applications that process the attachments published by the Oracle MQ Series Adapter. |
|
This property is optional and should only be specified if the "AsAttachment" property is set to true. It defines the content type of the attachment and is only meant for third-party applications that process the attachments published by the Oracle MQ Series Adapter. |
|
This property is optional and a value should only be provided if you want to segment the message into a custom size. The value should be in the following format - integerValue[M/K/B], where M stands for Megabytes, K for Kilobytes and B for Bytes. For example, 230K, 4M, 512B. |
|
This property defines the amount of time in milliseconds which the adapter should wait before trying to reconnect once the MQ Queue Manager is down. |
|
This property should always be used in conjunction with the |
|
This property should always be used in conjunction with the "ExponentialBackOff" property. This property is used for capping the "ExponentialBackOff" time interval. For example, if the "ExponentialBackOff" is set to 2 and "MaxExponentialBackOffCount" to 7 then the adapter retries at intervals of 2, 4, 8, 16, 32, 64, 128, 128, 128… seconds. |
|
The boolean property can be used to specify whether dynamic response queues should be used rather than a permanent ReplyToQueue. If set to true, then |
|
The model queue name based on which the dynamic response queues should be created for retrieving the reply message. |
|
This property specifies the wait interval for which the adapter waits for the response message to arrive on the reply queue. |
|
This property is used to reduce the MQ header information. The property can be added to |
|
This parameter specifies how often the inbound MQ Adapter must poll messages on the MQ queue. The parameter is of type |
Table A-31 JCA Properties for Oracle MQ Series Adapter: Normalized Properties
Property | Description |
---|---|
|
Inbound/Outbound. Accounting token information of the message. A hexadecimal-encoded string. |
|
Inbound/Outbound. Provides additional information about the Identity of the message or its originator. Accepts any string. |
|
Outbound. Wait interval for the response message to arrive on the reply queue. Accepts integer value in miliseconds. |
|
Inbound/Outbound. Provides additional information about the origin of this message. Accepts any string. |
|
Inbound/Outbound.Count of the number of times the message has previously been returned by an MQQueue.get() call as part of a unit of work, and subsequently backed out. Accepts zero and positive integer values. |
|
Inbound/Outbound. Correlation identifier of the message to be retrieved/ to be put. Accepts a hexadecimal-encoded string. |
j |
Inbound/Outbound. Representation used for numeric values in the application message data. Accepts NORMAL and REVERSED. |
j |
Inbound/Outbound. representation used for numeric values in the application message data. Accepts NORMAL, REVERSED and S390 |
|
Inbound/Outbound. A message's expiry time has elapsed, and it is eligible to be discarded by the queue manager. Accepts NEVER or a non- Inbound/Outbound.negative integer value |
|
Inbound/Outbound. Used with a message of type MQC.MQMT_REPORT to indicate the nature of the report. Accepts any string. |
|
Inbound/Outbound. application defined feedback.Accepts any string. |
|
Inbound/Outbound. Format name used by the sender of the message to indicate the nature of the data in the message to the receiver.Accepts following formats NONE, ADMIN, CHANNEL_COMPLETED, CICS, CMD1, CMD2, DEAD_LETTER_HDR, DIST_HDR, EVENT, IMS, IMS_VAR_STRING, MD_EXTN, PCF, REF_MSG_HDR, RF_HDR_1, RF_HDR_2, STRING, TRIGGER, WORK_INFO_HDR, XMIT_Q_HDR |
|
Inbound/Outbound. Byte string that identifies the message group to which the physical message belongs. Accepts hexadecimal-encoded string. |
|
Inbound/Outbound. Specifies if the message belongs to a group. Accepts true, false. |
|
Inbound/Outbound. Specifies if the message is the last message of the group. Accepts true, false |
|
Inbound/Outbound. Specifies if the message is a segment. Accepts true, false |
|
Inbound/Outbound. Specifies if message is the last segment. Accepts true, false |
|
Inbound/Outbound. Message identifier of the message to be retrieved/ to be put. Accepts hexadecimal encoded string |
|
Inbound/Outbound. Sequence number of a logical message within a group. Accepts non- Inbound/Outbound.negative integer value |
|
Inbound/Outbound. Indicates the type of the message. Accepts any string. |
|
Inbound/Outbound. Application -defined message type. Accepts any string. |
|
Inbound/Outbound. The offset of data in a physical message from the start of a logical message. Accepts non- Inbound/Outbound.Negative integer value. |
|
Inbound/Outbound. Original length of a segmented message. Accepts non-Negative integer value Inbound/Outbound |
|
Inbound/Outbound. message persistence. Accepts true, false, AS_Q_DEF |
|
Inbound/Outbound. Message priority. Accepts 0- Inbound/Outbound.9, AS_Q_DEF |
|
Inbound/Outbound. Name of the application that Put the message. Accepts any string |
|
Inbound/Outbound. Type of application that Put the message. Accepts any string. |
|
Inbound/Outbound. User-defined Put application type. Accepts any string. |
|
Inbound/Outbound. Time and date that the message was Put. Accepts year:month:date, year:month:date:hour:minute, year:month:date:hour:minute:second |
|
Inbound/Outbound. Name of the queue manager to which reply or report messages should be sent. Accepts any sting. |
|
Inbound/Outbound. Name of the queue to which reply or report messages should be sent. Accepts any string |
|
Inbound/Outbound. scheme to generate the CorrelationId of reply or report message. Accepts PASS_CORREL_ID, COPY_MSG_ID |
|
Inbound/Outbound. Scheme to generate the MessageId of reply or report message. Accepts NEW_MSG_ID, PASS_MSG_ID |
|
Inbound/Outbound. Specifies the content of COA report. Accepts WITH_NO_DATA, WITH_PARTIAL_DATA, WITH_FULL_DATA |
|
Inbound/Outbound. Specifies the content of COD report. Accepts WITH_NO_DATA, WITH_PARTIAL_DATA, WITH_FULL_DATA |
|
Inbound/Outbound. Specifies the content of the Exception report. Accepts WITH_NO_DATA, WITH_PARTIAL_DATA, WITH_FULL_DATA |
|
Inbound/Outbound. Specifies the content of the Expiry report. Accepts WITH_NO_DATA, WITH_PARTIAL_DATA, WITH_FULL_DATA |
|
Inbound/Outbound. Specifies if the incoming/outgoing message is NAN or not. Accepts true, false |
|
Inbound/Outbound. specify if incoming/outgoing message is PAN or not. Accepts true, false |
|
Inbound/Outbound. |
|
Accepts DISCARD, DEADLETTERQUEUE |
|
Inbound/Outbound. Struct id of MQMD. Accepts any string |
|
Inbound/Outbound. User who originated this message. Accepts any string. |
|
Inbound/Outbound. Version of MQMD. Accepts VERSION_1, VERSION_2 |
|
Outbound. Correlation identifier of the message retrieved in Async req-reply scenario. Accepts hexadecimal encoded string |
|
Outbound. Message identifier of the messageretrieved in Async req-reply scenario. Accepts hexadecimal-encoded string. |
|
Outbound. Message Type of the message retrieved in Async req-reply scenario. Accepts any string. |
|
Outbound. NAN report option of the message retrieved in the Async req-reply scenario. Aceepts true, false |
|
Outbound. PAN report option of the message retrieved in the Async req-reply scenario. Accepts true, false |
|
Outbound. ReplyToQueueManager of the message retrieved in the Async req-reply scenario. Accepts any string. |
|
Outbound. ReplyToQueue of the message retrieved in the Async req-reply scenario. Accepts any string. |
|
Outbound. Correlation scheme, for generation of CorrelationId, of the message retrieved in Async req-reply scenario. Accepts PASS_CORREL_ID, COPY_MSG_ID |
|
Outbound. Correlation scheme, for generation of MessageId, of the message retrieved in Async req-reply scenario. Accepts NEW_MSG_ID, PASS_MSG_ID |
|
Outbound. Queue Manager for outbound queue. Accepts any string |
|
Outbound. Queue name of outbound queue. Accepts any string. |
Table A-32 Connection Properties for Oracle MQ Series Adapter
Property | Description |
---|---|
|
Name of the host computer. |
|
Port number to be used. |
|
Set it to the server connection channel to be used. |
|
A valid queue manager name. |
|
Set |
ClientEncoding |
Character encoding used by the client. |
|
Location of the connection factory. |
|
Operating system used by the host computer. |
|
Algorithm used by the key store. |
|
This value is the keystore where Oracle MQ Series Adapter has its private keys. This is required when an adapter must authenticate itself to the MQ Series server. |
|
This value is the password that is required to access keystore. |
|
The name of the keystore provider. |
|
This is the location where the adapter keeps its trusted certificates information. This information is required when an adapter must authenticate to the MQ Series server. |
|
This property specifies the password of the Trust Store location. |
|
This property specifies the type of the key store. |
|
Key Management Algorithm. |
|
A distinguished name pattern. If |
|
The true or false value for this property means that the Oracle MQ Series Adapter is SSL enabled or SSL disabled. |
|
This property is used if credential mapping is not set. |
|
This is the password to connect to the queue manager. This property is used if credential mapping is not set. |
|
This property is used to enable or disable XA transactions. If set to |
|
This is the |
SecurityExit |
This is the |
|
This is the |
|
The value is a path to the CCDT file which should be used by the MQ Series Adapter for client connection details. |
|
The name of the key store under the given stripe. Used when KeyStoreType is set to "kss". |
|
The name of the stripe within which key store is created. Used when KeyStoreType is set to |
|
The name of the stripe within which trust store is created. Used when TrustStoreType is set to |
|
Algorithm used by the trust store. |
|
The name of the trust store under the given stripe. Used when TrustStoreType is set to kss. |
|
The name of the trust store provider. |
|
This property specifies the type of the trust store. |
Table A-33 Binding Properties for Oracle MQ Series Adapter
Property | Description |
---|---|
|
This property is used to specify the name of the inbound MQ queue. |
|
This property is used for dequeuing the messages with binary zero value. The default value for this property is |
MSMQ JCA Adapter Properties
The following tables describe the properties applicable to the MSMQ JCA Adapter:
-
Table A-34 MSMQ Adapter JCA Properties
-
Table A-35 MSMQ Adapter Normalized Properties
-
Table A-36 MSMQ Adapter Binding Properties
-
Table A-37 MSMQ Adapter Connection Factory Properties
Table A-34 MSMQ Adapter JCA Properties
Property | Description | Default Value | Required |
---|---|---|---|
|
Indicates if the message will be sent to a public queue, private queue or a group of queues as identified by the distribution list name. The values are:
|
None |
Yes |
|
Name of the MSMQ queue. |
None |
Yes, if
|
|
The string that identifies a
|
None |
Yes, if
|
|
Boolean that allows for Active Directory Path to be used to identify a public queue instead of queue name. This property is applicable when |
|
Applicable only to
|
|
Boolean that allows for Direct Format name to be used for public and private queues. |
|
- |
|
Priority can be set to any
integer value between |
|
- |
|
A time limit (in seconds) for
the message to be retrieved from the target queue. The value is
assigned to |
|
- |
|
Specifies express
(non-persistent) or recoverable (persistent) messaging. Express
messaging provides faster throughput. Recoverable messaging
guarantees that the message will be delivered even if a computer
crashes while the message is en route to the queue. The values are:
|
|
- |
|
The operation to be carried
out.The values are: |
None |
Yes |
|
Values are
|
|
Yes |
|
Boolean that enables payload to be streamed. Applicable only for inbound dequeue process. |
|
- |
Table A-35 MSMQ Adapter Normalized Properties
Property Name | Description | Direction |
---|---|---|
|
The time when a message is sent. |
Inbound |
|
A message's priority. This
overrides |
Inbound/Outbound |
|
The time limit (in seconds)
for the message to be retrieved from the target queue. This
overrides |
Inbound/Outbound |
|
The time limit (in seconds) for the message to reach the queue. Message Queuing uses the enterprise-wide setting for the time-to-reach-queue interval if none is specified here. |
Inbound/Outbound |
|
Identifies the message using an MSMQ-generated message identifier. |
Inbound |
|
Values can be
|
Inbound/outbound |
|
The length of the message body in bytes. |
Inbound |
|
The time when the message arrived at the queue. |
Inbound |
Table A-36 MSMQ Adapter Binding Properties
Property Name | Description |
---|---|
|
The time (in milliseconds) that Message Queuing will wait for a message to arrive before starting another poll-cycle. The default value is one second (1). |
|
Number of poller threads
that will be initialized when endpoint activation occurs. When
specified, the value of
|
The following table lists MSMQ Adapter Connection Factory Properties.
Table A-37 MSMQ Adapter Connection Factory Properties
Property Name | Description | Default |
---|---|---|
|
IP Address of the MSMQ host. |
This value can be the host name and the IP address can be given as the value for the Host property. |
|
Indicates if the connection
factory will allow for native access or not. Values are
[ |
|
|
Indicates if the connection
will participate in a transaction when sending and receiving a
message. Values are |
|
|
Identifies a user |
- |
|
Password for the user specified. |
- |
|
Domain of the MSMQ host. |
- |
Oracle Socket Adapter Properties
For properties applicable to all Oracle JCA Adapters, see Generic Oracle JCA Adapter Properties.
For more information, see Oracle Socket Adapter in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
Table A-38 JCA Properties for Oracle Socket Adapter
Property | Description |
---|---|
|
Byte order of the remote computer being communicated with. |
|
If |
|
Character encoding used by the remote computer. |
|
In case of outbound, the computer name on which the socket server is running, to which you want to connect. In case of inbound, it is always |
|
In case of outbound, it is the port number on which a socket server is running, to which the adapter is connecting. In case of inbound, it is the port number on which the socket adapter listens for incoming connections. |
|
If |
|
Mechanism for defining the protocol. Set to |
|
If |
|
Service side only. Name of the javascript file used for handling the request side communication. Use when |
|
Service side only. Name of the javascript file used for handling the response side communication. Use when |
|
Reference side only. Name of the javascript file used for outbound communication. Use when |
|
By default this property is set to Additionally, NIO is supported only for non-SSL connections. |
UMS JCA Adapter Properties
The following tables describe the properties applicable to the UMS Adapter:
-
Table A-39 UMS Adapter Activation Spec Properties
-
Table A-40 UMS Adapter Interaction Spec Properties
-
Table A-41 UMS Adapter Message Headers
-
Table A-42 UMS Adapter Mime-Part Message Headers
-
Table A-43 UMS Adapter Proprietary Headers
Table A-39 UMS Adapter Activation Spec Properties
Property Name | Description |
---|---|
|
Name of the Java class that defines custom logic for a message filtering or any other check. This class is a concrete implementation of the |
|
The number of inbound poller or listener threads. |
|
Specifies how the adapter will receive messages from UMS. Set to |
|
Address from which to receive incoming messages. One or more comma separated email address for the |
|
Email support is provided for receiving and sending outgoing messages. |
|
Polling interval in seconds for poller consume mode. |
|
Specifies one or more message filters. A single filter would comprise a Java Pattern String to match the incoming message against, along with the field type and the action ( |
Table A-40 UMS Adapter Interaction Spec Properties
Property Name | Description |
---|---|
|
Email support for only receive and sending outgoing messages. |
|
Subject of outgoing message. |
|
Sender addresses of outgoing message. |
|
One or more recipient addresses. |
|
Reply-to address. |
|
One or more cc addresses for email delivery. |
|
One or more bcc addresses for email delivery. |
|
|
Table A-41 UMS Adapter Message Headers
Header Field Name | Minimum Occurrence | Maximum Occurrence | Mapped Adapter Header Field Name |
---|---|---|---|
|
0 |
1 |
|
|
0 |
unlimited |
|
|
0 |
unlimited |
|
|
0 |
unlimited |
|
|
0 |
1 |
|
|
0 |
unlimited |
j |
|
0 |
unlimited |
|
|
0 |
unlimited |
|
|
0 |
unlimited |
|
|
1 |
1 |
j |
|
1 |
1 |
|
|
0 |
1 |
|
|
0 |
1 |
|
|
0 |
1 |
|
|
0 |
1 |
|
|
0 |
1 |
j |
|
0 |
1 |
|
|
0 |
1 |
|
|
0 |
1 |
|
|
0 |
1 |
|
|
0 |
unlimited |
|
|
0 |
unlimited |
|
Table A-42 UMS Adapter Mime-Part Message Headers
Header Field Name | Mapped Adapter Header Field Name | Notes |
---|---|---|
|
|
Applicable to all channels. For SMS and IM, the current supported type is |
|
|
- |
|
|
- |
|
|
- |
|
|
- |
|
|
- |
|
|
Any other mime header field hat begins with the string
|
MIME-Version |
|
- |
Table A-43 UMS Adapter Proprietary Headers
Header Name | Description |
---|---|
|
More than one proprietary header can be added in the following format:
( |