Systems, Applications, and Products (SAP) for data processing is an industry leading enterprise software solution that is widely used among product and process oriented enterprises for finance, operations, HR and many other aspects of a business. SAP ERP solutions provide reliable and efficient platforms to build and integrate enterprise or business-wide data and information systems with ease.
...
| Property | Description |
|---|---|
| Gateway host |
| Gateway service |
| Program ID of the server |
| You can enable or disable the RFC trace |
jco.server.repository_destination | Name of the .dest file. For example, if the .dest file is SAPSYS01.dest , set this to SAPSYS01 . |
jco.server.params | Arbitrary parameters for RFC library |
| SNC name |
| SNC level of security (1-9) |
| Path to the SNC library |
| Name of the profile file used during start-up |
| Determines whether or not you connect in unicodemode (1=true, 0=false) |
| Maximum server start-up delay time in seconds |
jco.server.connection_count | Number of SAP to ESB connections |
jco.server.name | Name of the server configuration. This needs to be the same as the name provided in the SAP configuration in SAP.. |
| Info | ||
|---|---|---|
| ||
You can obtain the values for these properties from your SAP system administrator. |
...
Following are descriptions of the SAP client properties that can be defined in the message context with axis2-client scope when using WSO2 ESB as a SAP client to send messages. These properties can be added in <ESB_HOME>/repository/conf/axis2/axis-client.xml file:
| Property | Description |
|---|---|
transport.sap.xmlMapper | The key of custom IDOC XML mapper to use. This key should be defined in the transport.sap. customXMLMappers parameter. If no key is specified the default IDoc XML mapper will be used. |
transport.sap. xmlParserOptions | The options for the default IDoc XML parser to be used in the default IDoc XML mapper. Multiple options can be combined using the bitwise OR "|" operator. The possible parser options are as follows: PARSE_ACCEPT_ONLY_XMLVERSION_10 3328 |
...
Following are descriptions of the proxy level listener parameters that can be defined in a proxy configuration when using WSO2 ESB as a SAP server:
| Parameter | Description |
|---|---|
transport.sap.serverName | The name of the server containing the JCO server configuration. |
transport.sap. enableErrorListener | Set this to enable the default error listener. If this is used together with the transport.sap. customErrorListener parameter, the custom error listener will be used. |
transport.sap. enableTIDHandler | Set this to enable the transaction handler to handle transactions that are received from a SAP system. Transactional applications must provide a custom implementation using the transport.sap. customTIDHandler parameter. |
transport.sap. customTIDHandler | The fully qualified class name for the custom TID handler implementing JCoServerTIDHandler. |
transport.sap.connections | The number of registered connections managed by the server instance. The default value is 1 and the maximum value is 100. |
transport.sap. customErrorListener | The fully qualified class name for the custom error listener implementing JCoServerErrorListener. |
transport.sap. customExceptionListener | The fully qualified class name for the custom exception listener implementing JCoServerExceptionListener. |
...
Troubleshooting
Given below are general troubleshooting guidelines.
...