Confirm Required
|
Select this check box to publish an IDoc confirmation message report when the SAP system receives an IDoc from the adapter service.
This check box is cleared by default.
An IDoc confirmation message report can include:
- Track Information of the message received
- Business Key of the message received
- Transaction ID generated by SAP system when receiving the IDoc
- IDoc number and status generated by the SAP system
By default, the
adr3.idocNumAndStatusIncluded property is set to
ON, which indicates the IDoc number and status are included in the IDoc confirmation message report. And this configuration is only available to the tRFC protocol.
Take note of the following when enabling IDoc message publishing:
Note: This field is available only when the service type is Request-Response Service (one-way only) or Subscription Service.
|
Destination
|
Select a way to log IDocs from the following options:
IDocs have to be logged to files or be saved to a destination or a subject in the following situations:
- For Publication Service or Subscription Service services, the destinations of the received IDocs is not in the valid destination list in the
Advanced tab.
- For Subscription Service services, an exception occurs from a SAP application that is returned from the SAP system. In this case, the data might be manually changed in the file and replayed later using a TIBCO ActiveMatrix BusinessWorks process.
Note: This field is available only when the service type is Publication Service or Subscription Service.
|
Format
|
Select a format for the IDoc files from the following options:
- None
Only the actual IDoc data is written to the file. No metadata is provided.
- XML
The IDoc is written to the file in XML format and the metadata for the function module, the adapter instance, invoked is used when writing to the file.
This option is selected by default.
Note: This field is available only when you select
Log to file from the
Destination list.
|
Log IDoc to Directory
|
Specify the directory to store the IDoc files.
If you leave this field blank, the IDoc files can either be logged to the current working directory or the directory specified in the
adr3.idocLogDirectory property.
The precedence of the directory is:
- The
adr3.IDocLogDirectory property
- The
Log IDoc to Directory field
- Working directory
The format of IDoc file name is
IDocType_DateTimeStamp_IDocCount.IDoc.
Note: This field is available only when you select
Log to file from the
Destination list.
|
Endpoint Reference
|
Click
to select a endpoint used by log RFC.
You can click
to clear this field.
Note: This field is available only when the service type is Request-Response Service (one-way only).
|
Client Connection Reference
|
Click this link to configure the client connection pool used by the adapter service in the
Connection Pools tab.
If you want to change the client connection pool for the adapter service, click
to select a client connection pool.
You can click
to clear this field.
Note: This field is available only when the service type is Subscription Service or Request-Response Invocation Service.
|
Thread Count
|
Specify the number of threads.
The default value is
1, which is the minimum value.
Note: This field is available only when the service type is Subscription Service or Request-Response Service.
|
qRFC Queue Name
|
Specify the name of the qRFC queue.
If you leave this field blank, inbound IDocs are tRFC. The Subscription Service service can either be configured to use tRFC or qRFC, but not both.
Note: This field is available only when the service type is Subscription Service.
|