iWay Application Adapter for MySAP

In this section:

Reference:

MySAP ERP is the latest implementation of the SAP Enterprise Reporting and Planning product. Releases are numbered ECC (Enterprise Central Component) 5 and 6.

There are two MySAP listeners that are available for configuration in iWay Service Manager:


Top of page

x
Reference: MySAP-AS Listener Properties

The following table lists and describes the MySAP-AS listener properties. For instructions on creating a listener, see Configuring Listeners.

Property Name

Property Description

Accepts non-XML (flat) only

If true, listener expects flat (non-XML). Preparsers do not run.

Client (required)

Client number defined for the MySAP application for client communications.

User (required)

Valid user ID for the MySAP application.

Password (required)

Valid password defined to the MySAP server.

Authentication mode (required)

Specifies how the connection is validated.

  • Password (default)

    Use the value specified in the Password field.

  • Logon ticket (SSO2)

    Specify the User to be $MYSAPSSO2$ and pass the base64 encoded ticket as the Password property.

  • Logon ticket (X509)

    Specify the User to be $X509CERT$ and pass the base64 encoded certificate as the password property.

System

Gateway host (required)

The name of a MySAP Gateway server.

Gateway service (required)

The service name, which is usually a compound of the service name and system number.

Program ID of the server (required)

A unique program identifier that has been specified on the MySAP Gateway server (case sensitive).

Application Server (required)

The host name or IP address for the computer that is hosting the MySAP application.

System number (required)

The system number defined to MySAP for client communications.

Security

SNC mode

Flag for activating SNC.

SNC partner

The application server's SNC name.

SNC level

The level of protection to use for the connection.

SNC name

The SNC name.

SNC library path

The path and file name of the external library.

Advanced

IDOC Format

Specifies the IDOC format.

  • XML (default)
  • XML-CDATA-ENVELOPED
  • NATIVE-IDOC

IDOC release

The version in which the IDOC definition was released.

IDOC release provider

Specifies where the adapter will get the release information.

  • IDOC DOCREL field (default

    Uses the information in the IDOC header.

  • SAP release

    Retrieves the information from the user account logon.

  • user input

    Uses the value in the IDOC release field to retrieve the information.

SAP trace

Traces SAP Java connector and RFC libraries. This option is disabled by default.

Processing Mode

Specifies the processing mode to use for your channel.

  • REQUEST (default)
  • REQUEST_RESPONSE

Execution Time Limit

Time limit for document execution (in seconds) before it is terminated.

Multithreading

Indicates the number of worker threads (documents or requests) that iWay Service Manager can handle in parallel. A value greater than 1 enables the listener to handle a second request while an earlier request is still being processed.

Maximum threads

Parallel threads can grow to this count automatically on demand.

Note: An asterisk in the console indicates a required property.



x
Reference: MySAP-MS Listener Properties

The following table lists and describes the MySAP-MS listener properties. For instructions on creating a listener, see Configuring Listeners.

Property Name

Property Description

Accepts non-XML (flat) only

If true, listener expects flat (non-XML). Preparsers do not run.

Client (required)

Client number defined for the MySAP application for client communications.

User (required)

Valid user ID for the MySAP application.

Password (required)

Valid password defined to the MySAP server.

Authentication mode (required)

Specifies how the connection is validated.

  • Password (default)

    Use the value specified in the Password field.

  • Logon ticket (SSO2)

    Specify the User to be $MYSAPSSO2$ and pass the base64 encoded ticket as the Password property.

  • Logon ticket (X509)

    Specify the User to be $X509CERT$ and pass the base64 encoded certificate as the password property.

System

Gateway host (required)

The name of a MySAP Gateway server.

Gateway service (required)

The service name, which is usually a compound of the service name and system number.

Program ID of the server (required)

A unique program identifier that has been specified on the MySAP Gateway server (case sensitive).

Message Server (required)

The host name or IP address for the computer that is hosting the MySAP application.

R/3 name (required)

System ID of the MySAP system.

Server group

Logon group of the message server. This value is case-sensitive.

Security

SNC mode

Flag for activating SNC.

SNC partner

The application server's SNC name.

SNC level

The level of protection to use for the connection.

SNC name

The SNC name.

SNC library path

The path and file name of the external library.

Advanced

IDOC Format

Specifies the IDOC format.

  • XML (default)
  • XML-CDATA-ENVELOPED
  • NATIVE-IDOC

IDOC release

The version in which the IDOC definition was released.

IDOC release provider

Specifies where the adapter will get the release information.

  • IDOC DOCREL field (default

    Uses the information in the IDOC header.

  • SAP release

    Retrieves the information from the user account logon.

  • user input

    Uses the value in the IDOC release field to retrieve the information.

SAP trace

Traces SAP Java connector and RFC libraries. This option is disabled by default.

Processing Mode

Specifies the processing mode to use for your channel.

  • REQUEST (default)
  • REQUEST_RESPONSE

Execution Time Limit

Time limit for document execution (in seconds) before it is terminated.

Multithreading

Indicates the number of worker threads (documents or requests) that iWay Service Manager can handle in parallel. A value greater than 1 enables the listener to handle a second request while an earlier request is still being processed.

Maximum threads

Parallel threads can grow to this count automatically on demand.

Note: An asterisk in the console indicates a required property.



x
Operating Modes

The adapter supports two operating modes:


Top of page

x
Communication Modes

The adapter supports two communication modes:

The adapter offers metadata browsing and schema creation for services and events. The service mode is used for all metadata functions.


Top of page

x
Run-time Interface and Document Style

The adapter supports the following application interfaces and document styles as both Service and Event:

The RFC API wrapped by the SAP JCO is the supported interface type.


Top of page

x
Service Operation

The adapter makes a service connection to the ERP instance via the JCO. The standard method of operation for service operation is to browse the metadata of an interface object (BAPI/RFC/ALE) and to create an XML schema from the selected object. The XML schema is then used to create an XML instance populated with application specific data to produce a correct result set. If the results are incorrect the adapter produces either a java exception or an error document, depending on user selection.


Top of page

x
Event Operation

Via the JCO, the adapter accepts a registered server program connection from the SAP gateway. The adapter then listens for events sent to the adapter destination, and processes the document. The adapter can operate in either synchronous or asynchronous event mode. In synchronous mode, the adapter passes off the results to a user defined function or adapter on the local application server, waits for the result, and passes the result back to MySAP ERP. In asynchronous event mode, the adapter produces a document with the data sent to it by the MySAP ERP application module.


Top of page

x
Transaction Modes

The adapter supports the SAP transactional Remote Function call protocol (TRFC). The transaction is automatic for each service or event operation. The adapter can also support multiple ALE transactions in one call (Collected IDOC) either Service or Event. Multiple BAPI/RFC calls can be embedded in a single document to achieve a sequence of events in one transaction.


iWay Software