33 Configuring Service and Reference Binding Components

This chapter describes how to configure properties for Web service and JCA adapter service and reference binding components that are included in SOA composite applications. Binding components are network protocols and services that connect the SOA platform with the outside world.

This chapter includes the following topic:

Section 33.1, "Configuring Service and Reference Binding Component Properties"

For more information about binding components, see the following documentation:

Note:

You cannot configure message header properties for direct binding components that invoke a SOA composite application through a remote RMI call. For this reason, the Properties tab does not display for direct binding components.

33.1 Configuring Service and Reference Binding Component Properties

You can configure message header properties for the service and reference binding components included in a deployed SOA composite application.

To configure service and reference binding component properties:

Access this page through one of the following options:

From the SOA Infrastructure Menu...	From the SOA Folder in the Navigator...	From the SOA Composite Menu...
Select Services and References. Select a specific service or reference. Click the Properties tab.	Right-click soa-infra. Select Services and References. Select a specific service or reference. Click the Properties tab.	Select Services/Reference Properties. Select a specific service or reference. Click the Properties tab.

The following binding component properties appear for a Web service.

Description of the illustration bc_properties.gif

The following binding component properties appear for a file adapter. Depending upon your selection of JCA adapter, different parameters display for configuring.

Description of the illustration bc_properties2.gif

Change properties based on your selection of binding component. See sections Section 33.1.1, "Configuring Properties for Web Services" and Section 33.1.2, "Configuring Properties for Oracle JCA Adapters" for available properties.

Note:
To see adapter header properties and their values on this page, ensure that you change the value of the Audit Level property from Production (the default) to Development in the SOA Infrastructure Common Properties page. If this property is set to Production, the properties and their values do not display.

33.1.1 Configuring Properties for Web Services

Table 33-1 describes the properties available for a Web service binding component.

Table 33-1 Web Service Properties

Service, Reference, or Endpoint	Property Name	Description
Service	REST Enabled	Enable or disable the Web services port to accept messages in Representational State Transfer (REST) format.
Service	WSDL Enabled	Enable or disable the WSDL of the Web service.
Service	Metadata Exchange Enabled	Enable or disable a metadata exchange of the Web service.
Service	Endpoint Test Enabled	Enable or disable an endpoint test of the Web service.
Service	Logging Level	Select the level of logging to perform on the Web service.
Service	Maximum Request Size	Enter the maximum request size of the Web service. A value of `-1` indicates the size is unlimited.
Service	Unit of Maximum Request Size	Select the request unit of the Web service (either bytes, kilobytes, megabytes, or gigabytes).

33.1.2 Configuring Properties for Oracle JCA Adapters

Note that if you manually add a nonregistered JCA binding level property in the composite.xml file, then you cannot subsequently edit that property or also any other registered properties for that service or reference through the Oracle Enterprise Manager Console.

Table 33-2 Types of JCA Adapters

Property Type Description Restrictions

Property Type	Description	Restrictions
Activation specification and interaction specification	Activation specification properties operate as services and interaction specification properties operate as references in a SOA composite application.	Do not add or remove these properties. You can only change their values. These properties require the adapter endpoint to be recycled. These types of properties are also dependent upon other properties. If you attempt to add one of these properties, you have no way of knowing which dependent properties must also be added.
Endpoint	These are tuning-related properties that are not exposed through the activation or interaction specification properties, such as specifying time outs, thresholds, maximum intervals, and so on.	There are no restrictions on adding, removing, or changing endpoint properties. The adapter is notified when these properties are added, removed, or changed, but it does not require redeployment. Note that you cannot add or remove `jca.retry.*` endpoint properties without redeploying the composite. However, you can change these properties by using the Oracle Enterprise Manager Console without redeploying the composite.

Activation specification and interaction specification

Activation specification properties operate as services and interaction specification properties operate as references in a SOA composite application.

Do not add or remove these properties. You can only change their values.

These properties require the adapter endpoint to be recycled. These types of properties are also dependent upon other properties. If you attempt to add one of these properties, you have no way of knowing which dependent properties must also be added.

Endpoint

These are tuning-related properties that are not exposed through the activation or interaction specification properties, such as specifying time outs, thresholds, maximum intervals, and so on.

There are no restrictions on adding, removing, or changing endpoint properties. The adapter is notified when these properties are added, removed, or changed, but it does not require redeployment.

Note that you cannot add or remove jca.retry.* endpoint properties without redeploying the composite. However, you can change these properties by using the Oracle Enterprise Manager Console without redeploying the composite.

This section includes the following topics:

Section 33.1.2.1, "Oracle AQ Adapter"
Section 33.1.2.2, "Oracle Database Adapter"
Section 33.1.2.3, "Oracle File Adapter"
Section 33.1.2.4, "Oracle FTP Adapter"
Section 33.1.2.5, "Oracle JMS Adapter"
Section 33.1.2.6, "Oracle MQ Series Adapter"
Section 33.1.2.7, "Oracle Socket Adapter"
Section 33.1.2.8, "Oracle JCA Adapters Endpoint Properties"

33.1.2.1 Oracle AQ Adapter

Table 33-3 describes the properties available for the Oracle AQ Adapter.

Table 33-3 Oracle AQ Adapter Properties

Service, Reference, or Endpoint	Property Name	Description
Service	`DequeueTimeOut`	Sets the dequeue timeout interval.
Service	`ConnectionRetryDelay`	Sets the connection retry interval.
Service	`adapter.aq.dequeue.threads`	Number of dequeue threads.
Service	`jca.retry.count`	Number of retries to post the message.
Service	`jca.retry.interval`	Time interval between message retries.
`Service`	`QueueName`	Indicates the AQ queue name.
`Service`	`DatabaseSchema`	Database schema name that hosts the queue.
`Service`	`SchemaValidation`	Validates the message payload.
`Service`	`ObjectFieldName`	Specifies ADT entry used as a payload. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
`Service`	`PayloadHeaderRequired`	Specifies if ADT entries except for payload are accessible.
`Service`	`DequeueCondition`	Specifies the expression to dequeue messages.
`Service`	`Consumer`	Specifies the consumer of a queue.
`Service`	`MessageSelectorRule`	Specifies the message selector to dequeue messages.
`Service`	`StreamPayload`	Specifies if payload is streamed or not.
`Service`	`Correlation`	Specifies a correlation criterion or search criterion for the dequeue operation. For the enqueue operation, the value becomes the correlation of the message sent to AQ.
Reference	`Username`	Identifies a user name requesting access to a secure environment or program, such as an Oracle database or Oracle Applications system.
Reference	Responsibility	Specifies a collection of functions within Oracle E-Business Suite. Each user is assigned one or more responsibilities to allow access to the appropriate functions and data.
Reference	`QueueName`	Indicates an AQ queue name.
Reference	`DatabaseSchema`	Indicates the Database schema name that hosts the queue.
Reference	`ObjectFieldName`	Specify the ADT entry to use as a payload. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Reference	`PayloadHeaderRequired`	Specify if ADT entries except for payload is accessible.
Reference	`RecipientList`	Specify recipient of the messages.
Reference	`Correlation`	Specifies a correlation criterion or search criterion for the dequeue operation. For the enqueue operation the value becomes the correlation of the message sent to AQ.

33.1.2.2 Oracle Database Adapter

Table 33-4 describes the properties available for the Oracle Database Adapter.

Table 33-4 Oracle Database Adapter Properties

Service, Reference, or Endpoint	Property Name	Description
Service	`DescriptorName`	The key into the TopLink metadata indicating the root relational table. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Service	`QueryName`	The key into the TopLink metadata indicating the named query to execute, with predefined where clause and parameters. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Service	`MappingsMetaDataUR`	In conjunction with `MappingsMetaDataURL` the path to the TopLink metadata file which describes how a database schema has been mapped to a particular predefined XML schema. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Service	`MappingsMetaDataUR`	Indicates the path to the TopLink metadata file which describes how a database schema has been mapped to an XML schema. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Service	`OXMappingsMetaDataURL`	In conjunction with `MappingsMetaDataURL` the path to the TopLink metadata file which describes how a database schema has been mapped to a particular predefined XML schema. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Service	`PollingInterval`	Indicates the number of seconds between queries to the database for new events.
Service	`MaxRaiseSize`	Indicates the maximum number of XML records that can be raised at a time to Oracle BPEL Process Manager or the activation listener.
Service	`PollingStrategy`	Indicates the method in which events are raised from the database. Also known as `AfterReadStrategy`. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Service	`MarkReadColumn`	Indicates status column used by LogicalDeletePollingStrategy, for indicating which rows have been processed.
Service	`MarkUnreadValue`	The status of unprocessed rows.
Service	`MarkReservedValue`	The status of rows reserved by this polling instance.
Service	`MarkReadValue`	The status of processed rows.
Service	`SequencingTableName`	For example, the `DB_ADAPTER_SEQUENCING`.
Service	`SequencingTableKeyColumn`	For example, `TABLE_NAME`. This column holds the primary keys of the various sequences stored.
Service	`SequencingTableValueColumn`	For example, `LAST_READ_ID`. This is the column that holds the value of the last processed sequence value.
Service	`SequencingColumn`	For example, `SCOTT.EMP.EMP_ID`. This is the monotonically increasing column on the polled table.
Service	`SequencingColumnType`	For example, the `java.math.BigDecimal, java.sql.Timestamp`. The type of sequence counter used.
Service	`SequencingTableKey`	For example, the `SCOTT.EMP`. This is the key into the sequencing helper table, usually the name of the table being polled.
Service	`ShouldCacheSequenceValue`	For `SequencingPollingStrategy`, the `lastReadId` can be kept in-memory so it does not have to be read at the start of each polling interval.
Service	`ShouldWriteSequenceValue`	For `SequencingPollingStrategy`, the `lastReadId` can be kept in-memory and only written out to disk or a database when the process, application server, or both are shut down.
Service	`DeleteDetailRows`	For the delete polling strategy, this indicates whether to delete detail rows and master rows after XML records have been read.
Service	`SequencingDataSourceName`	For `ExternalSequencingPollingStrategy`.
Service	`SequencingIsXADataSource`	For `ExternalSequencingPollingStrategy`.
Service	`UseBatchDestroy`	Deletes or updates multiple processed rows with a single Data Manipulation Language (DML) statement.
Service	`DelayCommit`	Indicates whether to delay the commit/destroy action until all rows picked up (across multiple `maxTransactionSize` units) have been processed.
Service	`PollForChildUpdates`	Indicates whether an update to a detail row must result in the master row and all its details being picked up for processing.
Service	`ShouldOrderRows`	For `SequencingPollingStrategy`, there may be cases where you do not want to order the rows by the sequence value.
Service	`NumberOfThreads`	Indicates the number of transactional threads to be used by the database adapter.
Service	`FetchSize`	Indicates the JDBC level cursor fetch size.
Service	`MaxBatchWritingSize`	Indicates the JDBC level statements per batch statement.
Service	`DeleteFromCursor`	Indicates the JDBC level delete while iterating over ResultSet.
Service	`UseDirectSQL`	Enables performance optimization in certain cases.
Service	`ReturnSingleResultSet`	Reads from multiple joined tables in a single SQL select rather than many and returns a single giant result set.
Service	`MaxTransactionSize`	Maximum number of rows to raise as part of one database transaction.
Service	`SequencingFileName`	For FileSequencingPollingStrategy only. The file contains a single value, the last read sequence value / updated time. Timestamps appear in ISO format.
Service	`SchemaValidation`	Validates the xml against the xml schema before raising it. Can only happen if the auto-generated has been hand-edited, that is, to add restrictions. Invalid records are rejected.
Service	`EnableStreaming`	Allows LOBs and multirecord XML files to be streamed through SAX events, allowing only a small part of payload to be kept in memory at a time.
Reference	`DescriptorName`	The key into the TopLink metadata indicating the root relational table. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Reference	`OutputCompletedXml`	Indicates if this interaction execution have an output message that is the input message with primary keys set.
Reference	`MappingsMetaDataURL`	The path to the `toplink.xml` file that describes how a database schema has been mapped to an XML schema. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Reference	`OXMappingsMetaDataURL`	In conjunction with `MappingsMetaDataURL` the path to the TopLink metadata file which describes how a database schema has been mapped to a particular predefined XML schema. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Reference	`GetActiveUnitOfWork`	Operations within the same JTA transaction use the same TopLink Session and connection, and writes occur together on JTA commit.
Reference	`DmlType`	Indicates the type of Data Modify Language (DML) operation (merge, insert, update, delete, write).
Reference	`OutputCompletedXml`	Does this interaction execute have an output message which is the input message with primary keys set. Useful when assigning primary keys on insert.
Reference	`OptimizeMerge`	Sets some properties to improve performance of the merge. For one, if multiple objects are merged, the read queries to check existence and load database versions into memory for comparison are performed as a single query, using an `in()` clause on the primary key.
Reference	`DetectOmissions`	Indicates whether to differentiate between null and not there in the input XML. The difference between `<director />` (omission) and `<director xsi:nil=\"true\"/>` (null).
Reference	`MaxBatchWritingSize`	The JDBC level statements per batch statement.
Reference	`UseDirectSQL`	Enables performance optimization in certain cases.
Reference	`QueryName`	The key into the TopLink metadata indicating the named query to execute, with predefined `where` clause and parameters.
Reference	`IsQueryByExample`	The query is generated dynamically on each invoke, based on matching the example input xml record.
Reference	`ReturnSingleResultSet`	An advanced feature that influences how many total selects TopLink uses when querying against multiple related tables (that is, Master-Detail). Safest is the default (one per table); setting to true that attempts one total, by outer joining all related selects into a single result set.
Reference	`CursorWindowSize`	How many records to return at a time when selecting a huge number of rows in a single query.
Reference	`EnableStreaming`	Allows LOBs and multirecord XMLs to be streamed through SAX events, allowing only a small part of payload to be kept in memory at a time.
Reference	`SqlString`	The SQL to execute in the pure SQL interaction. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Reference	`IsTransactional`	Indicates whether the pure SQL being executed is a write that must occur within transaction boundaries.
Reference	`QueryTimeout`	Indicates the JDBC level `queryTimeout` setting. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Reference	`MaxRows`	Indicates the JDBC level `maxRows` setting. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Reference	`SchemaName`	The schema of the stored procedure to execute.
Reference	`PackageName`	The package of the stored procedure to execute.
Reference	`ProcedureName`	The procedure of the stored procedure to execute.
Reference	`Overload`	Further identifies the stored procedure to execute (in case of overloading) by the expected number of parameters.
Reference	`QueryTimeout`	Indicates the JDBC level queryTimeout setting.

33.1.2.3 Oracle File Adapter

Table 33-5 describes the properties available for the Oracle File Adapter.

Table 33-5 Oracle File Adapter Properties

Service, Reference, or Endpoint	Property Name	Description
Service	`PhysicalDirectory`	Specifies the physical directory for the File/FTP adapter.
Service	`UseHeaders`	Set to `true` if the File/FTP adapter must publish metadata, for example, file name, directory name, last modified data, file size and exclude the payload. This is typically used in large payload scenarios where-in you simply want to use the inbound adapter as a notifier.
Service	`Recursive`	If set to `true`, the File/FTP adapter processes files recursively in sub-directories.
Service	`PhysicalArchiveDirectory`	Directory where the inbound File/FTP adapter archives files after they have been processed successfully.
Service	`PhysicalErrorArchiveDirectory`	Indicates the directory where the inbound File/FTP adapter archives files in case of failures, such as translation errors, and errors during publish.
Service	`DeleteFile`	If set to true, the File/FTP adapter deletes the file after it has been processed.
Service	`IncludeFiles`	Indicates the regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is processed by the File/FTP adapter.
Service	`ExcludeFiles`	Indicates the regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is excluded and not processed by the File/FTP adapter.
Service	`PollingFrequency`	This parameter specifies how often does the File/FTP adapter wake up to look for files in the inbound directory. It is specified in seconds.
Service	`MinimumAge`	This parameter specifies the time interval after which a file should be picked up for processing. For example, this enables a large file to be completely copied into the 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, set the minimum age of pollable files to five minutes. If a file is detected in the input directory and its modification time is less than 5 minutes older than the current time, the file is not retrieved because it is still potentially being written to.
Service	`PublishSize`	This parameter indicates that a file contains multiple messages and specifies how many messages should be processed simultaneously. For example, if a certain file has 11 records and this parameter is set to 2, then the file is processed 2 records at a time and the final record is processed in the 6th iteration.
Service	`Lenient`	If set to `true`, then the File adapter does not complain if it does not have enough permission to read/write to the inbound directory. By default, this is set to false.
Service	`TriggerFilePhysicalDirectory`	The directory path where the File/FTP adapter looks for the trigger files.
Service	`TriggerFile`	The name of the trigger file that causes the inbound File/FTP adapter to activate.
Service	`TriggerFileStrategy`	This parameter defines the strategy that the File/FTP adapter uses to look for the specified trigger file in trigger file directory. The acceptable values are `EndpointActivation`, `EveryTime`, or `OnceOnly`.
Service	`MaxRaiseSize`	This parameter specifies the maximum number of files that the File/FTP adapter submits for processing in each polling cycle. For example, if the inbound directory has 1000 files and this parameter is set to 100 and the polling frequency is one minute, then the File/FTP adapter submits 100 files every minute.
Service	`DirectorySeparator`	When you choose multiple directories, the generated JCA files use `\";\"` as the separator for these directories. However, if you want, you can change the separator to something else. If you do so, manually add `DirectorySeparator=\"<<chosen separator>>\"` in the generated JCA file. For example, to use a comma (`,`) as the separator, you must first change the separator to `\",\"` in the physical directory and then add `DirectorySeparator=\",\"` in the JCA file.
Service	`AsAttachment`	If set to `true`, it causes the inbound file to be published as an attachment.
Service	`CharacterSet`	Set it to the Character Set for the attachment. This parameter is not used internally by the File/FTP adapter and it is meant for third party applications that process the attachments published by the File/FTP adapter.
Service	`Encoding`	Set it to the encoding for the attachment. This parameter is not used internally by the File/FTP adapter and it is meant for third party applications that process the attachments published by the File/FTP adapter.
Service	`ContentType`	Set it to the Mime-Type for the attachment. This parameter is not used internally by the File/FTP adapter and it is meant for third party applications that process the attachments published by the File/FTP adapter.
Service	`ListSorter`	Specifies the sorter that the File/FTP adapter use to sort files in the inbound. You can set this parameter to `\"oracle.tip.adapter.file.inbound.listing.TimestampSorterAscending\"` or `\"oracle.tip.adapter.file.inbound.listing.TimestampSorterDescending\"`. You can also plug in your own sorter by writing a class that implements `\"java.util.Comparator\"`.
Service	`SingleThreadModel`	If the value is true, the File/FTP adapter poller processes files in the same thread. In other words, it does not use the global in-memory queue for processing.
Service	`ThreadCount`	If this parameter is available, the adapter creates its own processor threads rather than depending on the global thread pool processor threads (by default, four of them). In other words, this parameter partitions the in-memory queue and each composite application gets its own in-memory queue. If the `ThreadCount` is set to `\"0\"`, then it behaves in the same manner as the single thread model. If `ThreadCount` is set to `\"-1\"`, then it starts using the global thread pool. The maximum for this property is `40`.
Service	`recoveryInterval`	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/wake ups to check if the physical directory has been created and is accessible.
Reference	`PhysicalDirectory`	Specifies the physical directory for the file/FTP adapter.
Reference	`NumberMessages`	Specifies the outbound file naming convention used.
Reference	`ElapsedTime`	This parameter is used for outbound batching. When the time specified elapses, the outgoing file is created. The parameter is of type String and is not mandatory. The default value is `1`.
Reference	`FileSize`	Indicates if an opaque schema is being used.
Reference	`FileNamingConvention`	This parameter is for the naming convention for the outbound write operation file.
Reference	`FileName`	Use this parameter to specify a static single file name during the write operation.
Reference	`Append`	Setting this parameter to `\"true\"` causes the File/FTP adapter to append to a file on the outbound. If the file does not exist, a new file is created.
Reference	`UseStaging`	If `\"true\"`, then the outbound File/FTP adapter writes translated data to a staging file and afterward it streams the staging file to the target file. If `\"false\"`, then the outbound File/FTP adapter does not use an intermediate staging file.
Reference	`ConcurrentThreshold`	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 hence must to be guarded as it might cause starvation in other applications/threads. The maximum is `100` (same as the maximum for `dspMaxThreads` in BPEL).
Reference	`SequenceName`	Specifies the Oracle database sequence name to be used if you have already configured the outbound File/FTP adapter for high availability.
Reference	`oracle.tip.adapter.file.mutex`	Set it to the class name that specifies the mutex you want to use for the outbound write operation. This class must extend the "`oracle.tip.adapter.file.Mutex`" abstraction.
Reference	`serializeTranslation`	If set to `\"true\"`, then the translation step is serialized using a semaphore. The number of permits for semaphore (guarding the translation step) comes from `ConcurrentThreshold` parameter (above). If `\"false\"`, then the translation step occurs outside the semaphore.
Reference	`inMemoryTranslation`	This parameter is applicable only if `UseStaging` is `\"false\"`. If set to `\"true\"`, then the translation step occurs in-memory that is, an in-memory byte array is created. If set to `\"false\"`, then the adapter creates an output stream to the target file (FTP, FTPS and SFTP included) and allows the translator to translate and write directly to the stream.
Reference	`DeleteFile`	If set to `\"true\"`, the File/FTP adapter deletes the file after it has been processed.
Reference	`IgnoreZeroByteFile`	Set it to true if you do not want the File/FTP adapter to throw an exception during the outbound read operation if the file could not be found. This parameter is ignored if the schema for the inbound file is anything other than "Opaque".
Reference	`IncludeFiles`	Indicates the regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is processed by the File/FTP adapter.
Reference	`ExcludeFiles`	Includes the regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is excluded and not processed by the File/FTP adapter.
Reference	`Recursive`	If set to `true`, the File/FTP adapter processes files recursively in sub-directories.
Reference	`MaxRaiseSize`	This parameter specifies the maximum number of files that the File/FTP adapter submits for processing in each polling cycle. For example, if the inbound directory has 1000 files and this parameter is set to 100 and the polling frequency is one minute, then the File/FTP adapter submits 100 files every minute.
Reference	`DirectorySeparator`	When you choose multiple directories, the generated JCA files use `\";\"` as the separator for these directories. However, if you want, you can change the separator to something else. If you do so, manually add `DirectorySeparator`=\"<<chosen separator>>\" in the generated JCA file. For example, to use a comma (`,`) as the separator, you must first change the separator to `\",\"` in the Physical directory and then add `DirectorySeparator=\",\"` in the JCA file.
Reference	`SourceFileName`	The source file for the File I/O operation.
Reference	`SourcePhysicalDirectory`	The source directory for the File I/O operation.
Reference	`SourceType`	Set this to `\"native\`" if the source file is native and `\"xml\"` if the source file is XML.
Reference	`SourceSchema`	Set it to the schema for the source file.
Reference	`SourceSchemaRoot`	Set it to the root element name for the source file.
Reference	`TargetFileName`	Indicates the target file for the File I/O operation.
Reference	`TargetPhysicalDirectory`	Indicates the target directory for the File I/O operation.
Reference	`TargetType`	Set this to `\"native\"` if the target file is native and `\"xml\"` if the source file is XML.
Reference	`TargetSchema`	Set it to the schema for the target file.
Reference	`TargetSchemaRoot`	Set it to the root element name for the target file.
Reference	`Xsl`	Set it to the XSL transformer between the source and target.
Reference	`Type`	Set it \"`COPY`\",\"`MOVE`\", or \"`DELETE`\".
Reference	`BatchSize`	Set it to the batch size for the batching transformation.
Reference	`ChunkSize`	Specifies the number of outbound messages.

33.1.2.4 Oracle FTP Adapter

Table 33-6 describes the properties available for the Oracle FTP Adapter.

Table 33-6 Oracle FTP Adapter Properties

Service, Reference, or Endpoint	Property Name	Description
Service	`timestampOffset`	This parameter is used by the FTP adapter to tackle time zone issues, typically to convert the time difference between the ftp server and the system on which the ftp adapter is running to millisecond.
Service	`PhysicalDirectory`	This parameter specifies the physical directory for the File/FTP adapter.
Service	`UseHeaders`	Set to `\"true\"` if the File/FTP adapter must publish metadata, for example, file name, directory name, last modified data, file size and exclude the payload. This is typically used in large payload scenarios where-in you simply want to use the inbound adapter as a notifier.
Service	`FileType`	Set it to either `\"ascii\"` or `\"binary\"` depending on the requirement.
Service	`Recursive`	If set to `\"true\"`, the File/FTP adapter processes files recursively in sub-directories.
Service	`PhysicalArchiveDirectory`	Directory where the inbound File/FTP adapter archives files after they have been processed successfully.
Service	`PhysicalErrorArchiveDirectory`	Indicates the directory where the inbound File/FTP adapter archives files in case of failures, such as translation errors, and errors during publish.
Service	`UseRemoteArchive`	Set this parameter to `\"true\"` to notify the FTP adapter that the archival directory is on the same FTP server. If set to `\"false\"`, the FTP adapter uses a local file system folder for archival.
Service	`UseNlst`	Set this parameter to `\"true\"` if you need the FTP Adapter to use the `\"NLST\"` FTP command instead of the `\"LIST\"` that the adapter uses by default.
Service	`DeleteFile`	If set to `\"true\"`, the File/FTP adapter deletes the file after it has been processed.
Service	`IncludeFiles`	Indicates the regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is processed by the File/FTP adapter.
Service	`ExcludeFiles`	Indicates the Regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is excluded and not processed by the File/FTP adapter.
Service	`PollingFrequency`	This parameter specifies how often does the File/FTP adapter wake up to look for files in the inbound directory. It is specified in seconds.
Service	`MinimumAge`	This parameter specifies the time interval after which a file should be picked up for processing. For example, this enables a large file to be completely copied into the 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, set the minimum age of pollable files to five minutes. If a file is detected in the input directory and its modification time is less than 5 minutes older than the current time, the file is not retrieved because it is still potentially being written to.
Service	`PublishSize`	This parameter indicates that a file contains multiple messages and specifies how many messages should be processed simultaneously. For example, if a certain file has 11 records and this parameter is set to 2, then the file is processed 2 records at a time and the final record is processed in the 6th iteration.
Service	`TriggerFilePhysicalDirectory`	The directory path where the File/FTP adapter looks for the trigger files.
Service	`TriggerFile`	The name of the trigger file that causes the inbound File/FTP adapter to activate.
Service	`TriggerFileStrategy`	This parameter defines the strategy that the File/FTP adapter uses to look for the specified trigger file in trigger file directory. The acceptable values are `EndpointActivation`, `EveryTime` or `OnceOnly`.
Service	`MaxRaiseSize`	This parameter specifies the maximum number of files that the File/FTP adapter submits for processing in each polling cycle. For example, if the inbound directory has 1000 files and this parameter is set to 100 and the polling frequency is one minute, then the File/FTP adapter submits 100 files every minute.
Service	`DirectorySeparator`	When you choose multiple directories, the generated JCA files use `\";\"` as the separator for these directories. However, if you want, you can change the separator to something else. If you do so, manually add `DirectorySeparator`=\"<<chosen separator>>\" in the generated JCA file. For example, to use a comma (`,`) as the separator, you must first change the separator to `\",\"` in the Physical directory and then add `DirectorySeparator`=\",\" in the JCA file.
Service	`AsAttachment`	If set to `\"true\"`, it causes the inbound file to be published as an attachment.
Service	`CharacterSet`	Set it to the Character Set for the attachment. This parameter is not used internally by the File/FTP adapter and it is meant for third party applications that process the attachments published by the File/FTP adapter.
Service	`Encoding`	Set it to the Encoding for the attachment. This parameter is not used internally by the File/FTP adapter and it is meant for third party applications that process the attachments published by the File/FTP adapter.
Service	`ContentType`	Set it to the Mime-Type for the attachment. This parameter is not used internally by the File/FTP adapter and it is meant for third party applications that process the attachments published by the File/FTP adapter.
Service	`ListSorter`	Specifies the sorter that the File/FTP adapter use to sort files in the inbound. You can set this parameter to \"`oracle.tip.adapter.file.inbound.listing.TimestampSorterAscending`\" or \"`oracle.tip.adapter.file.inbound.listing.TimestampSorterDescending`\". You can also plug in your own sorter by writing a class that implements `\`"`java.util.Comparator`\".
Service	`SingleThreadModel`	If the value is true, the File/FTP adapter poller processes files in the same thread. In other words, it does not use the global in-memory queue for processing.
Service	`ThreadCount`	If this parameter is available, the adapter creates it's own processor threads rather than depending on the global thread pool processor threads (by default 4 of them). In other words, this parameter partitions the in-memory queue and each composite application gets its own in-memory queue. If the `ThreadCount` is set to `\"0\"`, then it behaves in the same manner as the `SingleThreadModel`. If the `ThreadCount` is set to `\"-1\"`, then it starts using the global thread pool. The maximum for this property is `40`.
Service	`recoveryInterval`	Used by the inbound adapter to configure the `recoveryInterval` in case of errors. For example, if the `PhysicalDirectory` is non-existent, then the adapter uses this value to perform periodic sleep/wakeups to check if the `PhysicalDirectory` has been created and is accessible.
Service	j`ca.message.encoding`	This parameter is used to override the encoding specified in the NXSD schema for the inbound File/FTP adapter.
Service	`oracle.tip.adapter.file.debatching.rejection.quantum`	This property lets you control the size of a rejected message for the inbound File/FTP adapter partner link. For example, if you set it to `\"100\"`, it causes the File/FTP adapter to reject 100 lines from the file since the actual file is too large.
Service	`useFileSystem`	This parameter is used by the inbound File/FTP adapter during read-only polling in a clustered environment. Setting it to `\"true\"` causes the adapter to use the file system to store metadata about files that have been already processed. Setting it to `\"false\"` causes the adapter to use a database table.
Service	`oracle.tip.adapter.file.timeout.recoverpicked.minutes`	Used by the inbound high-av adapter when using `\"FILEADAPTER_IN\"` as the coordinator. Remember that when a file is first claimed (enqueued) by a node for processing `FILE_PROCESSED` column in `FILEADAPTER_IN` is set to `\"0\"`. At a later point in time, when one of the decoupled Processor threads picks up the file for processing, the value of `FILE_PROCESSED` column is updated from `\"0\"` to `\"1\"`. And when the file is processed completely, the `FILE_PROCESSED` column is updated from `\"1\"` to `\"2\"`. However, if the processor thread picks up a file but the node crashes before it could process the file, then the file is never processed. This parameter is used to `\"undo\"` the pick operation. The adapter does this by deleting the entries in `FILEADAPTER_IN` table that have been picked up but not processed within the value specified here.
Service	`oracle.tip.adapter.file.timeout.recoverunpicked.minutes`	Used by the inbound high-av adapter when using `\"FILEADAPTER_IN\"` as the coordinator. Remember that when a file is first claimed by a node for processing `FILE_PROCESSED` column in `FILEADAPTER_IN` is set to `\"0\"`. At a later point in time, when the decoupled-Processor thread picks up the file for processing, the value of `FILE_PROCESSED` column is updated from `\"0\"` to `\"1\"`. And when the file is processed completely, the `FILE_PROCESSED` column is updated from `\"1\"` to `\"2\"`. If the node crashes when the `FILE_PROCESSED` is still `\"0\"`, it means that the file is enqueued by a node (this means no other nodes can pick this one up). However, it also means that the decoupled processor threads have still not picked this one for processing. This parameter is used to `\"undo\"` the `claim(enqueue_` operation. The adapter does this by deleting the entries in `FILEADAPTER_IN` table that have been claimed (for example, `FILE_PROCESSED ==\"0\"`), but not picked up until now.
Service	`purgeIntervalMillis`	Defines how often would the poller thread purge control files for read-only polling scenarios. Defaults to 5 days.
Service	`oracle.tip.adapter.file.highavailability.maxRetryInterval`	Number of milliseconds after which the inbound File/FTP adapter retries to establish database connection in distributed polling scenarios.
Service	`oracle.tip.adapter.file.highavailability.maxRetry`	Number of times that the inbound File/FTP adapter retries to establish database connection in distributed polling scenarios.
Service	`oracle.tip.adapter.file.rejectOriginalContent`	Setting to `\"true\"` causes the File/FTP adapter to reject the original actual content. If set to `\"false\"`, the adapter rejects the XML data created because of to the translation step.
Service	`notifyEachBatchFailure`	Setting to `\"true\"` causes the File/FTP adapter to call the Notification Agent's `onBatchFailure` every time an error occurs in a de-batching scenario. If set to `\"false\"`, the File/FTP adapter calls `onBatchFailure` only once after all messages in the de-batching scenario.
Reference	`PhysicalDirectory`	Directory Path for the File/FTP adapter.
Reference	`FileType`	Set it to either `\"ascii\"` or `\"binary\"` depending on the requirement.
Reference	`NumberMessages`	This parameter is used for outbound batching. The outgoing file is created when the number of messages condition is met. The parameter is of type String and is not mandatory. The default value is `1`.
Reference	`ElapsedTime`	This parameter is used for outbound batching. When the time specified elapses, the outgoing file is created. The parameter is of type String and is not mandatory. The default value is `1`.
Reference	`FileSize`	This parameter is used for outbound batching. The outgoing file is created when the file size condition is met. The parameter is of type String and is not mandatory. The default value is `1000` KB.
Reference	`FileNamingConvention`	This parameter is for the naming convention for the outbound write operation file.
Reference	`FileName`	Use this parameter to specify a static single file name during the write operation.
Reference	`Append`	Setting this parameter to `\"true\"` causes the File/FTP adapter to append to a file on the outbound. If the file does not exist, a new file is created.
Reference	`UseStaging`	If `\"true\"`, then the outbound File/FTP adapter writes translated data to a staging file and afterward it streams the staging file to the target file. If `\"false\"`, then the outbound File/FTP adapter does not use an intermediate staging file.
Reference	`ConcurrentThreshold`	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 hence must to be guarded as it might cause starvation in other applications/threads. The maximum is `100` (same as the maximum for `dspMaxThreads` in BPEL).
Reference	`SequenceName`	Specifies the Oracle database sequence name to be used if you have already configured the outbound File/FTP adapter for high availability.
Reference	`oracle.tip.adapter.file.mutex`	Set it to the class name that specifies the mutex you want to use for the outbound write operation. This class must extend `\"oracle.tip.adapter.file.Mutex\"` abstraction.
Reference	`serializeTranslation`	If set to `\"true\`", then the translation step is serialized using a semaphore. The number of permits for semaphore (guarding the translation step) comes from ConcurrentThreshold parameter (above). If `\"false\"`, then the translation step occurs outside the semaphore.
Reference	`inMemoryTranslation`	This parameter is applicable only if `UseStaging` is `\"false\"`. If set to `\"true\"`, then the translation step occurs in-memory that is, an in-memory byte array is created. If set to `\"false\"`, then the adapter creates an output stream to the target file (FTP, FTPS and SFTP included) and allows the translator to translate and write directly to the stream.
Reference	`FileType`	Set it to either `\"ascii\"` or `\"binary\"` depending on the requirement.
Reference	`UseRemoteArchive`	Set this parameter to `\"true\"` to notify the FTP adapter that the archival directory is on the same FTP server. If set to `\"false\"`, the FTP adapter uses a local file system folder for archival.
Reference	`DeleteFile`	If set to `\"true\"`, the File/FTP adapter deletes the file after it has been processed.
Reference	`IgnoreZeroByteFile`	Set it to `\"true\"` if you do not want the File/FTP adapter to throw an exception during the outbound read operation if the file could not be found. This parameter is ignored if the schema for the inbound file is anything other than `\"Opaque\"`.
Reference	`IncludeFiles`	Indicates the regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is processed by the File/FTP adapter.
Reference	`ExcludeFiles`	Indicates the regex pattern against which the filenames are matched. If the name of a certain file matches this pattern, it is excluded and not processed by the File/FTP adapter.
Reference	`Recursive`	If set to `\"true\"`, the File/FTP adapter processes files recursively in subdirectories.
Reference	`MaxRaiseSize`	This parameter specifies the maximum number of files that the File/FTP adapter submits for processing in each polling cycle. For example, if the inbound directory has `1000` files and this parameter is set to `100` and the polling frequency is one minute, then the File/FTP adapter submits `100` files every minute.
Reference	`DirectorySeparator`	When you choose multiple directories, the generated JCA files use `\";\"` as the separator for these directories. However, if you want, you can change the separator to something else. If you do so, manually add `DirectorySeparator=\"<<chosen separator>>\"` in the generated JCA file. For example, to use a comma (`,`) as the separator, you must first change the separator to `\",\"` in the Physical directory and then add `DirectorySeparator=\",\"` in the JCA file.
Reference	`UseNlst`	Set this parameter to `\"true\"` if you need the FTP adapter to use the `\"NLST\"` FTP command instead of `\"LIST\"` that the adapter uses by default.
Reference	`timestampOffset`	This parameter is used by the FTP adapter to tackle time zone issues, typically to convert the time difference between the FTP server and the system on which the FTP adapter is running to millisecond.
Reference	`SourceFileName`	Indicates the source file for the File I/O operation.
Reference	`SourcePhysicalDirectory`	Indicates the source directory for the File I/O operation.
Reference	`SourceType`	Set this to `\"native\"` if the source file is native and `\"xml\"` if the source file is xml.
Reference	`SourceSchema`	Set it to the schema for the source file.
Reference	`SourceSchemaRoot`	Set it to the root element name for the source file.
Reference	`TargetFileName`	Indicates the target file for the File I/O operation.
Reference	`TargetPhysicalDirectory`	The target directory for the File I/O operation.
Reference	`TargetType`	Set this to `\"native\"` if the target file is native and `\"xml\"` if the source file is xml.
Reference	`TargetSchema`	Set it to the schema for the target file.
Reference	`TargetSchemaRoot`	Set it to the root element name for the target file.
Reference	`Xsl`	Set it to the XSL transformer between the source and target.
Reference	`Type`	Set it to either `\"ascii\"` or `\"binary\"` depending on the requirement.
Reference	`BatchSize`	Set it to the batch size for the batching transformation.
Reference	`SourceIsRemote`	Set it to `\"false\"` to notify the FTP adapter that the source for the I/O operation is a local file system as opposed to remote FTP server.
Reference	`TargetIsRemote`	Set it to `\"false\"` to I/O notify the FTP adapter that the target for the I/O operation is a local file system as opposed to remote FTP server.
Reference	`ChunkSize`	Set it to the `ChunkSize` for the chunked interaction operation.

33.1.2.5 Oracle JMS Adapter

Table 33-7 describes the properties available for the Oracle JMS Adapter.

Table 33-7 Oracle JMS Adapter Properties

Service, Reference, or Endpoint	Property Name	Description
Service	`adapter.jms.encoding`	Set the encoding to be used by JMS inbound adapter.
Service	`adapter.jms.receive.timeout`	Set the receive timeout interval.
Service	`adapter.jms.retry.interval`	Set the interval JMS adapter would retry.
Service	`adapter.jms.registration.interval`	Set the registration interval.
Service	`adapter.jms.receive.threads`	Set the number of receive threads.
Service	`JMSReplyToDestinationProperties`	Set the reply to destination.
Service	`JMSReplyUseMessageIdForCorrelation`	Whether message id is necessary for correlation. Valid values are 'true' or 'false'.
Service	`JMSReplyUseCorrelationIdForCorrelation`	Whether correlation id is necessary for correlation. Valid values are `true` or `false`.
Service	`suppressHeaders`	Whether to bypass headers or not. Valid values are `true` or `false`.
Service	`JMSReplyPropagateJMSExpiration`	Whether a reply message is created with a TTL value of other than 0 which is the default value in a request reply scenario. Valid values are `true` or `false`.
Service	`minimumDelayBetweenMessages`	A throttling parameter (in milliseconds) that adds a brief sleep between each inbound posted message, thus slowing down the message inflow.
Reference	`requestReply.useCorrelation`	Whether correlation is necessary in a request reply scenario. Valid values are `true` or `false`.
Reference	`requestReply.cacheReceivers`	Whether correlation is necessary in a request reply scenario. Valid values are `true` or `false`.
Reference	`DestinationName`	Name of JMS physical destination.
Reference	`PayloadType`	Indicates the JMS Message type.
Reference	`DeliveryMode`	Set JMS delivery mode. Delivery Modes supported by JMS API are `PERSISTENT` and `NON_PERSISTENT`.
Reference	`TimeToLive`	Indicates the message lifetime in milliseconds.
Reference	`Priority`	Indicates the JMS message priority.
Reference	`PayloadEntry`	Specify the `MapMessage` entry to use as the payload.
Reference	`AttachmentList`	Specify `MapMessage` entry to use as the payload and publish as an attachment.
Reference	`RequestDestinationName`	Indicates the name of JMS physical destination.
Reference	`ReplyDestinationName`	Indicates the name of JMS physical destination.
Reference	`AllowTemporaryReplyDestination`	Allows creation of temporary destination for receiving messages.
Reference	`DurableSubscriber`	Indicates the unique name of durable subscription within a client identifier.
Reference	`MessageSelector`	Message selector expression used for message selection when delivering message to Destination.
Reference	`ReplyTimeout`	Indicates the `Timeout` to receive a reply message.

33.1.2.6 Oracle MQ Series Adapter

Table 33-8 describes the properties available for the Oracle MQ Series Adapter.

Table 33-8 Oracle MQ Series Adapter Properties

Service, Reference, or Endpoint	Property Name	Description
Service	`MessageType`	Indicates the message type of outbound/dequeue message.
Service	`QueueName`	Indicates the name of inbound/outbound queue.
Service	`UseMessageEncodingForTranslation`	Set to true if characterSet from header is used while translation.
Service	`InboundThreadCount`	Indicates the number of threads used in inbound.
Service	`BackoutQueueName`	Indicates the name of a backout queue where rejected message would go.
Service	`BackoutQueueManagerName`	Indicates the name of the backout queue manager where the rejected message goes.
Service	`MaximumBackoutCount`	Indicates the number of times adapter would retry before sending the message to a backout queue.
Service	`BackoutInterval`	Indicates the interval between a retry for a backout message.
Service	`jca.message.encoding`	This encoding value overwrites any encoding specified, either in MQMD or in a schema file.
Service	`UseMessageEncodingForTranslation`	Set to `\"true\"` if `characterSet` field of MQMD is to be used for translation in inbound. If set to `\"false\"` the translator uses the encoding from the schema file. You can use the `jca.message.encoding` property to overwrite any encoding specified, either in MQMD or in the schema file
Service	`FallbackReplyToQueueName`	Indicates the `Fallback` Reply To queue name.
Service	`FallbackReplyToQueueManagerName`	Indicates the `Fallback` Reply To queue manager name.
Service	`Priority`	Indicates the priority of the reply/outbound message.
Service	`Expiry`	Indicates the expiry time for the reply/outbound message.
Service	`Persistence`	Indicates the persistence of the reply/outbound message.
Service	`Feedback`	Indicates the feedback code of the reply/outbound message. Note that you cannot edit this property in the Oracle Enterprise Manager Console.
Service	`MessageFormat`	Indicates the format of the reply/outbound message.
Service	`OnDeliveryFailure`	Indicates the behavior of adapter if reply/outbound message delivery fails.
Service	`SegmentIfRequired`	Indicates the segmentation property for the message.
Service	`CopyPersistenceFromInbound`	Indicates the copy persistence from inbound message to reply message in a Sync Req-Res(inbound) scenario.
Service	`PropagateExpiryInterval`	Indicates the propagate expiry interval from the inbound message to the reply message in a Sync Req-Res(inbound) scenario.
Service	`QueueName`	Indicates the name of the inbound/outbound queue.
Service	`GetMessageOptions`	Indicates the Get message options for an outbound dequeue scenario.
Service	`FilterByMsgId`	Indicates the Message ID to be used for filtering.
Service	`FilterByCorrelId`	Indicates the correlation ID to be used for filtering.
Service	`FilterByGroupId`	Indicates the Group ID to be used for filtering.
Service	`FilterByMsgSeqNumber`	Indicates the message sequence number to be used for filtering.
Service	`FilterByMsgSeqNumber`	Indicates the message sequence number to be used for filtering.
Reference	`QueueName`	Indicates the name of the inbound/outbound queue.
Reference	`DistributionList`	Indicates the distribution list where the message goes.
Reference	`PartialDeliveryForDL`	Set to `false` if the message must go to all the queues in the DL. Otherwise, it is set to `true`.
Reference	`SecondaryQueueManagerName`	Indicates the name of the secondary queue manager.
Reference	`MessageFormat`	Indicates the format of the reply/outbound message.
Reference	`ReplyMessageId`	Indicates the correlation scheme for the message ID to be set.
Reference	`ReplyCorrelationId`	Indicates the correlation scheme for the correlation ID to be set.
Reference	`MessageId`	Indicates the correlation scheme for the outbound message.
Reference	`CorrelationId`	Indicates the correlation scheme for the outbound message.
Reference	`ReportCOA`	Indicates the COA report to be set on the message.
Reference	`ReportCOD`	Indicates the COD report to be set on the message.
Reference	`ReportException`	Indicates the exception report to be set on the message.
Reference	`ReportExpiry`	Indicates the expiration report to be set on the message.
Reference	`ReportPAN`	Indicates if `PAN` is required.
Reference	`ReportNAN`	Indicates if `NAN` is required.
Reference	`FallbackReplyToQueueName`	Indicates the `Fallback` Reply To queue name.
Reference	`FallbackReplyToQueueManagerName`	Indicates the `Fallback` Reply To queue manager name.
Reference	`Priority`	Indicates the priority of the reply/outbound message.
Reference	`Expiry`	Indicates the expiry time for the reply/outbound message.
Reference	`Persistence`	Indicates the persistence of the reply/outbound message.
Reference	`Feedback`	Indicates the feedback code of the reply/outbound message.
Reference	`ReplyToQueueName`	Indicates the ReplyToQueue to be set on the message. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console.
Reference	`ReplyToQueueManagerName`	Indicates the ReplyToQueueManager to be set on the message. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console
Reference	`OnDeliveryFailure`	Indicates the behavior of adapter if reply/outbound message delivery fails.
Reference	`SegmentIfRequired`	Indicates the segmentation property for the message.
Reference	`PartialDeliveryForDL`	Set to `true` if partial delivery to DistributionList is allowed. Otherwise, it is set to `false`.
Reference	`SyncSolicitReqRes`	Set to `true` if it is a Sync Req-Res(outbound) scenario. Otherwise, it is set to `false`. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console.
Reference	`ResponseOpaqueSchema`	Set to `true` if a reply/report message in a Sync Req-Res scenario has an opaque schema.
Reference	`ResponseWaitInterval`	Indicates the wait time for the reply/report to arrive.
Reference	`ResponseNoMessageAllowed`	Set to `true` if no message is allowed as a reply/report after specified wait interval.
Reference	`ResponseGetMessageOptions`	Indicates the Get message options for a reply/report.
Reference	`ResponseQueueOpenOptions`	Indicates the open options for a reply/report queue.
Reference	`PutMessageOptions`	Indicates the Put message options.
Reference	`QueueOpenOptions`	Indicates the open options for the queue. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console.
Reference	`UseMessageEncodingForTranslation`	Set to true if `characterSet` from the header is used while in translation.
Reference	`DynamicQueueName`	Indicates the dynamic queue name.
Reference	`AlternateUserID`	Indicates the alternate user ID.
Reference	`WaitInterval`	Indicates the wait interval for the outbound dequeue.
Reference	`NoMessageAllowed`	Set to `true` if no message is allowed in the outbound dequeue scenario after a specified wait interval.
Reference	`UseMessageEncodingForTranslation`	Set to `\"true\"` if the `characterSet` field of MQMD is to be used for translation in the inbound direction. If set to `\"false\"`, the translator uses the encoding from the schema file. You can use the `jca.message.encoding` property to overwrite any encoding specified, either in MQMD or in the schema file.

33.1.2.7 Oracle Socket Adapter

Table 33-9 describes the properties available for the Oracle Socket Adapter.

Note:

Properties such as TransMode and XSLT, which are not listed in Table 33-9, are displayed in the Properties tab. However, you cannot edit properties that are not listed in Table 33-9. Making changes to noneditable properties makes the composite invalid and would require remodeling of the composite.

Table 33-9 Oracle Socket Adapter Properties

Service, Reference, or Endpoint	Property Name	Description
Service	`Port`	The port on which the inbound socket adapter listens for incoming socket connections.
Service	`Encoding`	Indicates the character encoding of the native data. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console.
Service	`ByteOrder`	Indicates the byte order of the native data as bigEndian or littleEndian. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console.
Reference	`Host`	Indicates the host to which the outbound socket adapter opens a socket connection.
Reference	`Port`	Indicates the port to which the outbound socket adapter tries to connect.
Reference	`Encoding`	Indicates the character encoding of the native data. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console.
Reference	`ByteOrder`	Indicates the byte order of the native data as bigEndian or littleEndian. Note that you cannot edit this property in Oracle Enterprise Manager Fusion Middleware Control Console.

33.1.2.8 Oracle JCA Adapters Endpoint Properties

Table 33-10 describes the endpoint properties available for the Oracle JCA Adapters.

You cannot add or remove the endpoint properties without redeploying the composite. However, you can change the endpoint properties by using the Oracle Enterprise Manager Console without redeploying the composite.

Table 33-10 Oracle JCA Adapters Endpoint Properties

Direction (Inbound/Outbound)	Property Name	Description
Inbound	`activationInstances`	This property can increase the number of polling (Worker) threads for any inbound JCA resource adapter. It is only meant to help increase concurrency (scalability) for adapters, which do not natively support multi threading. Since most of the adapters included with Fusion Middleware natively support multithreading, this setting would mostly be useful to third party (custom) JCA adapters, which do not natively support multi threading. Set this property to the number of threads that is required for a particular JCA Service (endpoint).
Inbound	`UseWorkManager`	By default, JCA adapters use the standard Fusion Middleware WebLogic WorkManager for starting polling (Worker) threads. However, if you want a particular JCA service (endpoint) to use custom (user-defined) WorkManager, then this property enables you to specify the name of such a custom WorkManager. The WorkManager is only used to start the JCA Service (endpoint) for which this property has been defined.
Inbound	`rejectUncorrelatedMessages`	When native correlation is used to correlate an inbound asynchronous message with a previous outbound message (by way of defining a callback interface (for a reference) or by a mid process receive (in BPEL)) the JCA framework normally always try to post the message to the composite, whether the inbound message can be correlated or not. By setting this property to `true`, the JCA framework rejects a message, which cannot be correlated (when native correlation is active).
Inbound	`jca.retry.count`	Indicates the maximum number of retries before rejection.
Inbound	`jca.retry.interval`	Indicates the time interval between retries (measured in seconds).
Inbound	`jca.retry.backoff`	Indicates the retry interval growth factor (positive integer).
Inbound	`jca.retry.maxInterval`	Indicates the maximum value of retry interval; that is, a cap if backoff is greater than `1`.
Outbound	`jca.retry.count`	Indicates the maximum number of retries before throwing retryable error condition back to invoking service engine.
Outbound	`jca.retry.interval`	Indicates the time interval between retries (measured in seconds).
Outbound	`jca.retry.backoff`	Indicates the retry interval growth factor (positive integer).
Outbound	`jca.retry.maxInterval`	Indicates the maximum value of retry interval; that is, a cap if the backoff is greater than `1`.
Outbound	`jca.retry.maxPeriod`	Indicates the maximum total retry period. Retries do not occur longer than the value specified in this parameter.

The following examples show how to specify the endpoint properties in the composite.xml file in Oracle JDeveloper:

Example 1: Specifying Endpoint Properties - Inbound
Example 2: Specifying Endpoint Properties - Outbound

Example 1: Specifying Endpoint Properties - Inbound

<service name="Inbound">
  <interface.wsdl interface="http://xmlns...#wsdl.interface(Inbound_PortType)"/>
  <binding.jca config="Inbound_db.jca">
    <property name="jca.retry.interval">5</property>
    <property name="jca.retry.interval">1</property>
    <property name="jca.retry.backoff">2</property>
    <property name="jca.retry.maxInterval">6</property>
  </binding.jca>
</service>

Notice that the inbound property jca.retry.maxPeriod is not supported (like it is in outbound).

Example 2: Specifying Endpoint Properties - Outbound

<reference name="Outbound">
  <interface.wsdl interface="http://xmlns...#wsdl.interface(Outbound_PortType)"/>
  <binding.jca config="Outbound_jms.jca">
    <property name="jca.retry.count">5</property>
    <property name="jca.retry.interval">1</property>
    <property name="jca.retry.backoff">2</property>
    <property name="jca.retry.maxInterval">6</property>
    <property name="jca.retry.maxPeriod">30</property>
  </binding.jca>
</reference>

33.1.3 Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration

If a reference binding component of the SOA composite application is integrated with Oracle Service Registry (OSR), you can change the endpoint reference and service key in the General section of this page.

The UDDI ServiceKey field automatically displays the value of binding.ws property="oracle.soa.uddi.serviceKey" from the composite.xml file if you selected to use UDDI for run-time resolution of the endpoint.

You can edit the UDDI ServiceKey field after the SOA composite application has been deployed to either:

Change the value as needed
Add it to a composite that did not use UDDI for run-time endpoint resolution.

The Endpoint Address field represents the endpoint location as defined with the ws.binding endpointURI property in the composite.xml file. The Endpoint Address field is not filled in after the SOA composite application has been deployed, but can override the endpoint location in the concrete WSDL.

The endpoint location order of precedence is as follows:

Dynamically set the binding oracle.soa.uddi.serviceKey at run time in the UDDI ServiceKey field.
Dynamically set the binding property endpointURI at run time in the Endpoint Address field.
Use the binding property value for oracle.soa.uddi.serviceKey in the composite.xml file (viewable and editable in Oracle Enterprise Manager Fusion Middleware Control Console).
Use the binding property value for endpointURI in the composite.xml file (viewable and editable in Oracle Enterprise Manager Fusion Middleware Control Console).
Use the location specified in the concrete WSDL.

Figure 33-1 provides shows both fields.

Figure 33-1 Endpoint Reference and Service Key Properties

Description of "Figure 33-1 Endpoint Reference and Service Key Properties"

In the UDDI ServiceKey field, change the service key to use during run time.
In the Endpoint Address field, enter the endpoint address to use during run time.

You can edit both fields. The value for one field is selected and used based on what you selected in the UDDI Deployment Options dialog during design time. The changes to these fields are persisted in the composite.xml file during run time.

For information about design-time tasks such as how to publish a business service, create a connection to the UDDI registry, and configure a SOA project to invoke a service from the registry, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

For information about how to set the inquiry URL during run time, see Section 3.1, "Configuring SOA Infrastructure Properties."

33.1.3.1 Configuring Caching of WSDL URLs

Caching of endpoint WSDL URLs occurs by default during run time. If an endpoint WSDL URL is resolved using the orauddi protocol, subsequent invocations retrieve the WSDL URLs from cache, and not from OSR. You can increase the amount of time that the endpoint WSDL URL is available in cache for inquiry by the service key with the UddiCacheLifetime property. This property invalidates the cache at specified time intervals. The default value is 86400 seconds. The minimum value is 300 seconds.

To configure endpoint caching of WSDL URLs:

From the SOA Infrastructure menu, select Administration > System MBean Browser.
Select Application Defined MBeans > oracle.as.soainfra.config > Server: soa_server1 > SoaInfraConfig > soa-infra > Attributes.
Click the UddiCacheLifetime property on the right side of the page.
Enter a value.
Click Apply.