Pattern parameter | M | C | Default | Description |
---|---|---|---|---|
Adapter component name | Yes | No | idocpassthrough.inadapter |
The adapter component name. This name is also the name of the SAPConnection configurable service that is created. |
Host name | Yes | No |
Specifies the IP address or the name of the application server host to which the adapter logs on. You must set the value to a valid SAP server host name or IP address. |
|
RFC program ID | Yes | No |
The remote function call (RFC) identifier under which the adapter registers in the SAP gateway. This value must match the Program ID that is registered in SAP (transaction SM59). |
|
Gateway host | Yes | No |
The host name of the SAP gateway. The default value is an empty string, which signifies that an SAP gateway is not used when the adapter connection is made. |
|
Gateway service | Yes | No | sapgw00 |
The identifier of the gateway on the gateway host that carries out the RFC services. The default value is an empty string, which signifies that an SAP gateway service is not used when the adapter connection is made. Enter a valid SAP gateway server identifier. |
Client | Yes | No | 100 |
The client number of the SAP system to which the adapter connects. If you do not specify a value for this property, the default value is 100, which matches the default SAP client. Set this property to the required SAP client number, which must be a three-digit integer in the range 000 - 999. |
System number | Yes | No | 00 |
The system number of the SAP application server. If you do not specify a value for this property, the default value is 00, which matches the default SAP system number. Set this property to the required SAP system number, which must be a two-digit integer in the range 00 - 99. |
Number of listeners | Yes | No | 1 |
The number of RFC connections that are established to SAP by the .inadapter component. This number corresponds to the maximum number of RFC or transactional RFC (tRFC) calls from SAP that can be handled concurrently by the adapter. |
Pattern parameter | M | C | Default | Description |
---|---|---|---|---|
SAP sapjco3.jar file | Yes | No | sapjco3.jar |
This pattern parameter defines the location of the SAP JCO JAR file. |
System library file (sapjco3.dll or sapjco3.so) | Yes | No | sapjco3.dll |
This pattern parameter defines the location of the SAP system library file (librfc32.dll or librfccm.so). |
Pattern parameter | M | C | Default | Description |
---|---|---|---|---|
Logging required | No | No | Cleared |
This pattern parameter determines whether the pattern instance includes the code for logging. If Logging required is cleared, the logging subflow is not included. If Logging required is selected, a logging subflow is included in the message flow and values must be set for Log queue manager and Log queue. |
Log queue manager | No | Yes |
This pattern parameter defines the queue manager for logging. It can be left blank if the broker queue manager is used for logging. This parameter is required only if Logging required is selected. |
|
Log queue | No | Yes | LOG |
This pattern parameter defines the queue for logging. This parameter is required only if Logging required is selected. |
Pattern parameter | M | C | Default | Description |
---|---|---|---|---|
Error message required | No | No | Selected |
This pattern parameter defines whether the pattern application creates the message flow elements to create error messages. This parameter is required only if Error message required is selected. If Error message required is selected, values must be set for Error queue manager and Error queue. |
Error queue manager | No | Yes |
This pattern parameter defines the queue manager for error messages. It can be left blank if the broker queue manager is used for logging. |
|
Error queue | No | Yes | ERROR |
This pattern parameter defines the queue for error messages. This parameter is required only if Error message required is selected. |
Pattern parameter | M | C | Default | Description |
---|---|---|---|---|
Broker schema | No | No | mqsi |
If a broker schema is specified, all message flows and ESQL files are created within that schema. If no schema is specified, the default broker schema is used. |
Flow prefix | No | No |
If set, this prefix is added to the beginning of all message flow names. |
|
Flow suffix | No | No |
If set, this suffix is added to the end of all message flow names. |
|
Queue prefix | No | No |
If set, this prefix is added to the beginning of all queue names. If default queue names are used, the prefix, suffix, or both, must be set to identify queue names for each pattern instance. |
|
Queue suffix | No | No |
If set, this suffix is added to the end of all queue names. If default queue names are used, the prefix, suffix, or both, must be set to identify queue names for each pattern instance. |
|
Short description | No | No |
This description is added to the Short description property of all message flows that are generated. |
|
Long description | No | No |
This description is added to the Long description property of all message flows that are generated. |
All the pattern parameters are listed with their default values.
The column headed M indicates whether the property is mandatory. The column headed C indicates whether the property is configurable, meaning that you can change the value when you add the message flow to the broker archive (BAR) file.
Where no default is indicated the default value is an empty string.