If you’re configuring data exchange via RFC/SNC by calling an SAP function module with the SAP JavaConnector, the properties in the table must be added.
Note: To invoke function modules with the SAP JavaConnector, the required native libraries from
SAP need to be available. These must be downloaded from the SAP Support Portal for the
current system architecture.
| Property | Description |
|---|---|
| genericXchange.rfc.sap.system.1.job.enabled | Sets if data exchange for a Job approachJob should be enabled for the configuration (1) or not. In case of Behaviour approach usage, this setting has no effect. Example value: true or false (default). |
| genericXchange.rfc.sap.system.1.job.cronExpression | The CRON expression used for the job. Example value: 0 0/1 * 1/1 * ? *. |
| genericXchange.rfc.sap.system.1.name | An arbitrary value for the current configuration. Should not contain special characters. Must be unique across all available configurations. Recommendation: This should contain the name of the connected SAP system. Example value: NSP SAP System or SAP Cloud System. |
| genericXchange.rfc.sap.system.1.host | The IP address of the SAP server or the SAP Router string. Example value: 192.168.112.112, sap.mydomain.com, or /H/80.112.112.112/H/192.168.112.112/S/3201. |
| genericXchange.rfc.sap.system.1.systemNumber | The SAP system number. Example value: 00 or 01. |
| genericXchange.rfc.sap.system.1.client | The SAP client used to log in to the SAP system. Example value: 100 or 800. |
| genericXchange.rfc.sap.system.1.user | SAP system user used for the login. Example value: ALFR3SC0. |
| genericXchange.rfc.sap.system.1.password | Password for the SAP user. Either plain-text or use encrypted password. See the Using encrytped password chapter in the Alfresco Content Connector for SAP Applications documentation for more. Example value: H3ll0W0rlD112! or ENC(XbfE4Z112==). |
| genericXchange.rfc.sap.system.1.language | The SAP system language used to login. Example value: EN or DE. |
Note: For both, OData and RFC/SNC, it is possible to have up to 100 separate
configurations, where each can invoke a separate configuration file in Content
Services. This can be accomplished by duplicating all properties above and
increasing the number within the key names.