Skip to content

Commit

Permalink
small edits for style consistency
Browse files Browse the repository at this point in the history
  • Loading branch information
@EllenWehrle
EllenWehrle committed Sep 27, 2022
1 parent 883bbe7 commit 83eb701
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 12 deletions.
Binary file modified articles/.DS_Store
View file
Binary file not shown.
24 changes: 12 additions & 12 deletions articles/sap-integration/env-variables-connection-refs.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -41,21 +41,21 @@ SAP has multiple connection parameters, and manually entering the parameters int

| Property | Description |
|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| AppServerHost | The hostname of the SAP Application Server. |
| AppServerService | The service name or port number of the specific SAP Application Server to connect to (Optional for connection type (Logon) A - Application Server). |
| AppServerHost | The hostname of the SAP application Server. |
| AppServerService | The service name or port number of the specific SAP application server to connect to (Optional if connection type (Logon) is A - Application Server). |
| Client | The SAP client ID to connect to the SAP system. The SAP backends' client (or 'Mandant') into which to log in. It is a number ranging from 000 to 999. |
| LogonGroup | The Logon Group for the SAP System, from which the Message Server shall select an Application Server (Only available if connection type (Logon) is B - Message Server (Group)). |
| LogonType | The type of logon to the SAP System, either Application Server Logon (Type A) or Group Logon (Type B aka Message Server). Allowed values: ApplicationServer and Group. |
| MessageServerHost | The hostname of the SAP System's Message Server (central instance) aka R3 System Name (Mandatory if connection type (Logon) is B - Message Server (Group)). |
| MessageServerService | The Service Name (as defined in etc/services) or the Port Number under which the Message Server is listening for load-balancing requests (Mandatory if connection type (Logon) is B - Message Server (Group) and System ID is not present). |
| LogonGroup | The logon group for the SAP system, from which the message server selects an application server (Only available if connection type (Logon) is B - Message Server (Group)). |
| LogonType | The type of logon to the SAP system. The allowed values are either Application Server Logon (Type A) or Group Logon (Type B, AKA Message Server).|
| MessageServerHost | The hostname of the SAP system's message server (central instance) aka R3 system name (Mandatory if connection type (Logon) is B - Message Server (Group)). |
| MessageServerService | The service name (as defined in etc/services) or the port number under which the message server is listening for load-balancing requests (Mandatory if connection type (Logon) is B - Message Server (Group) and system ID is not present). |
| SncCertificate | The X.509 certificate in Base64 encoded form, without the begin or end certificate tags. |
| SncMyName | The installed SNC solution usually knows its own SNC name. For solutions supporting multiple identities, you may need to specify the identity to be used for this destination/server (optional). |
| SncLibraryPath | Name or path of the SNC library to be used. With the OnPremises Data Gateway, the path can be an absolute or relative to the NCo library. |
| SncPartnerName | The backends' SNC name (Required when Logon Type is Application Server). |
| SncQop | Quality of Service to be used for SNC communication of this destination/server. The allowed values: Authentication, Integrity, Privacy, Default, and Maximum. |
| SncLibraryPath | The name or path of the SNC library to be used. With the on-premises data gateway, the path can be an absolute or relative to the NCo library. |
| SncPartnerName | The backends' SNC name (Required when type of logon is Application Server). |
| SncQop | The quality of service to be used for SNC communication of this destination/server. The allowed values are Authentication, Integrity, Privacy, Default, and Maximum. |
| SncSso | The SNC SSO specifies whether to use SNC identity or credentials provided on RFC level. |
| SystemId | The SAP system's three-letter system ID (Mandatory if connection type (Logon) is B - Message Server (Group) and Message Server Service is not present). |
| SystemNumber | The SAP System's System Number. It is a number ranging from 00 to 99 (Mandatory if connection type (Logon) is A - Application Server). |
| SystemId | The SAP system's three-letter system ID (Mandatory if connection type (Logon) is B - Message Server (Group) and message server service is not present). |
| SystemNumber | The SAP system's system number. It's a number ranging from 00 to 99 (Mandatory if connection type (Logon) is A - Application Server). |
| UseSnc |
||

Expand All @@ -67,7 +67,7 @@ Environment variables can be used in solution cloud flows since they are availab

### Known issue

If an environment variable is updated after it has been used in a flow, the updated values will not be used the next time the flow runs. The _flow must be edited or resaved_ for the updated values in the environment variable to take effect.
If an environment variable is updated after it has been used in a flow, the updated values will not be used the next time the flow runs. **The flow must be edited or resaved** for the updated values in the environment variable to take effect.

### See also

Expand Down

0 comments on commit 83eb701

Please sign in to comment.