SAPMEINT Database Transporter

The SAPMEINT_DB_TRANS activity sends messages from SAP ME to SAPMEINT through a database table monitored by SAPMEINT. When SAPMEINT discovers a new message, a preconfigured workflow is triggered to process the message and sends it to SAP ERP.

For example, if you need to send a message to SAP ERP when an SFC number is completed, you attach the SAPMEINT_DB_TRANS activity to the POST execution point of the completeSFC service method. When an SFC number is completed the completeSFC method is executed and the message is sent to the SAPMEINT workflow.

Note Note

This activity is restricted to synchronous execution to ensure that if there is a failure during message transport, the overall business process fails.

End of the note.

Prerequisites

You have configured the SAPMEINT workflows for the messages (see SAPMEINT Workflow Configuration).

Options

The following table describes options that you can set to change the behavior of this activity:

Option	Description
MESSAGE_DESTINATION	The Java Naming and Directory Interface (JNDI) name of the data source where the SAPMEINT_ME_MESSAGE table is located The default value: jdbc/jts/SAPMEINTXA
MESSAGE_KEY	The lookup key the transporter uses to retrieve a message provided by another service extension. Note MESSAGE_KEY is applicable only when MESSAGE_SOURCE is set to SERVICE_EXTENSION. End of the note. The default value: com.sap.me.collaboration.sap.MIIMessageDBTransportActivity.MESSAGE_KEY
MESSAGE_SOURCE	The source of the content transported in the message SERVICE_EXTENSION (Default): The message is provided by another service extension attached to the same extension point as this transporter. The service extension providing the message must be configured to execute before the transporter. API_INPUT: The service method input converted to the XML format API_RESULT: The service method output converted to the XML format

Option

Description

MESSAGE_DESTINATION

The Java Naming and Directory Interface (JNDI) name of the data source where the SAPMEINT_ME_MESSAGE table is located

The default value: jdbc/jts/SAPMEINTXA

MESSAGE_KEY

The lookup key the transporter uses to retrieve a message provided by another service extension.

Note Note

MESSAGE_KEY is applicable only when MESSAGE_SOURCE is set to SERVICE_EXTENSION.

End of the note.

The default value: com.sap.me.collaboration.sap.MIIMessageDBTransportActivity.MESSAGE_KEY

MESSAGE_SOURCE

The source of the content transported in the message

SERVICE_EXTENSION (Default): The message is provided by another service extension attached to the same extension point as this transporter. The service extension providing the message must be configured to execute before the transporter.

API_INPUT: The service method input converted to the XML format

API_RESULT: The service method output converted to the XML format