Functional Ack Handled Automatically

An indicator of whether Oracle SOA Suite for healthcare integration automatically generates the functional acknowledgment (FA) for inbound HL7 messages. Select this option to automatically generate the FA; inbound FA messages are consumed when this option is selected.

Clear this property if you do not want to automatically generate the FA document. The back-end application (middleware) must generate the FA and provide it to Oracle SOA Suite for healthcare integration as an outbound message. When this property is deselected, inbound FA documents are passed back to the back-end application.

If the document does not require an FA (as indicated by the endpoint-level setting), then this property is ignored. This property is selected by default.

If the FA is marked as expected in an endpoint, then the message is placed into the MSG_WAIT_FA state and the back-end application is expected to generate the FA and push it to Oracle SOA Suite for healthcare integration as an outbound message back to the partner.

When Functional Ack Handled Automatically is not selected, Notify Inbound Functional Acks must also be deselected in order for the inbound FA to be sent to the back-end application. If Notify Inbound Functional Acks is selected and Functional Ack Handled Automatically is deselected, the incoming functional acknowledgment generates only a notification and the FA document itself is not sent back to the back-end application.

The following limitations apply when generating the FA from the back-end application:

• The FA is correlated with the original message based on the ReferToMsgID value set in the enqueue properties. The FA is correlated based on control numbers also.

• If the FA indicates that there was an error in the received message, the status of the correlated message is not updated to indicate an error. The correlated message is updated to MSG_COMPLETE.

These limitations are not present when the FA is generated by Oracle SOA Suite for healthcare integration (that is, when this property is selected).

Functional Ack Internal Properties

An indicator of whether to generate the internal properties structure in the functional acknowledgment using the original message internal properties.

By default, this property is deselected, which means that the functional acknowledgment uses the original message-internal properties.

Notify Inbound Functional Acks

An indicator of whether Oracle SOA Suite for healthcare integration sends an acknowledgment notification to the application when a functional acknowledgment is received. Select this property to send the acknowledgment notification.

When Functional Ack Handled Automatically is not selected, Notify Inbound Functional Acks must also not be selected in order for the inbound FA to be sent to the back-end application. If Notify Inbound Functional Acks is selected and Functional Ack Handled Automatically is not selected, the incoming functional acknowledgment generates only a notification and the FA document itself is not sent back to the back-end application.

Log Payload

An indicator of whether to log the payload in a diagnostic log. When this property is selected, the payload is logged, but this also depends on the log level setting. Error messages are logged by default. Payload logging is useful for diagnostic purposes, but might be undesirable for security reasons. By default, this property is not selected.

Note: You must set the log-level setting in the Enterprise Management console to TRACE to be able to log payloads. The available log-level settings are TRACE, NOTIFICATION, INCIDENT_ERROR, ERROR, and WARNING.

Exception Queue

A JMS internal delivery channel for the host to use as the exception queue. Exception notifications are sent to the queue name you specify here. A null value for this parameter means that exceptions are sent to the default JMS queue (B2B_IN_QUEUE).

Notification Queue

A JMS internal delivery channel for the host to use as the notification queue. System level notifications (at the endpoint level) are sent to this queue. A null value for this parameter means that exceptions are sent to the default JMS queue (B2B_IN_QUEUE).

The events that are notified:

• Outbound Case: When the skip message limit is reached, endpoint is paused

• Inbound Case: When there is a parse failure or a message validation error, endpoint is paused or connection is reset,

To enable the notification of the system events, a new Server property must be added in the Oracle Fusion Middleware Enterprise Manager Control console. The property, hc.mllp.EnableEventNotification, takes the values true or false to enable and disable notification respectively. If the value is not set, by default the notification for system events is not enabled.

Generic Message Type

An indicator of whether Oracle SOA Suite for healthcare integration need to ignore the HL7 trigger event. By default, this property is selected and set to true.

Outbound Dispatcher Count

The number of dispatchers used for handling the outbound messages. This is used in message sequencing.

Inbound Dispatcher Count

The number of dispatchers used for handling the inbound messages. This is used in message sequencing.

Partial Batch Commit Size

The number of records to be committed when there is a large number of business messages for a message exchange.

Enable BAM

An indicator of whether to send runtime information to Oracle BAM. For more information, see Monitoring Instance Message Data With Oracle BAM in Using Oracle B2B .

BAM Polling Interval

The polling interval in minutes for Oracle BAM. This is ignored if Oracle BAM is not enabled.

Ignore Correlation

An indicator of whether to ignore correlation errors when an acknowledgment is received and correlation fails. Acknowledgments are correlated to the actual business message of the sender. If the correlation fails, an exception is generated and the acknowledgment processing stops. To ignore the correlation in this case and continue processing the acknowledgment, select this property. By default, this property is not selected.

Callout Directory

The directory for the callout JAR file location (if you do not use the default callout). The callout directory path cannot end with a forward or backward slash (/ or \).

The default file location, /MyCalloutDir, is retained after purging the metadata repository.

SSL Private Key Password

The private key password to decrypt the public key of the private key - public key pair in case of secured data exchange by using SSL/TLS. You can leave this field blank if the password is same as the Keystore Password. This setting is retained after purging the metadata repository.

Large Payload Size

The large payload size, in bytes. The default value is 2,000,000 (2MG).

Large Payload Directory

The directory to store large payloads. The default directory is /tmp. For Windows-based systems, change the directory to an appropriate directory, such as C:\temp.

Location

The path where the keystore for managing trusted certificates and private-public key pairs are stored. For a two-way authentication, you require to configure two keystores, one at the client side to store server certificates and the keys, and the other at the server side to store client certificates and keys.

Password and Confirm Password

The password to access the keystore.