...
In this article
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
...
Overview
You
...
must create an
...
- Your private project folder: This folder contains the pipelines that will use the account.
- Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
- The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.
Required Permissions in SAP Account
...
*
(an asterisk) OR 16
...
Warning |
---|
Depending on what BAPI method or which IDoc type is used in the Pipeline, you may need to extend the permissions in your SAP account. |
Account Configuration
In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for SAP:
...
SAP account to connect to data sources that you want to use in your Pipelines. You can configure your SAP accounts in SnapLogic using either the Designer or the Manager.
Snap-Account Compatibility
...
Note |
---|
|
Account Types
SAP JCo Account
...
title | Account Settings |
---|
...
Label
...
Username
Specify a SAP username.
Note | ||
---|---|---|
| ||
Username is not required for authentication through SAP SNC. See Advanced JCo Properties for more details. |
Password
Specify a password for the username.
Note | ||
---|---|---|
| ||
Password is not required for authentication through SAP SNC. See Advanced JCo Properties for more details. |
Language*
...
Client*
...
Application server*
...
System number*
...
Peak limit
...
Specify the maximum number of active connections that can be created simultaneously for a destination.
Note |
---|
Recommended value could be <100 as too many connections may impact JCC performance. |
Default value: 5
...
Connection pool capacity
...
Router string
...
Specify the SAP Router string required for making connections to systems that are behind a SAP Router. An SAP router string contains a chain of SAP routers with their port numbers, and has the form (/H/<host>[/S/<port>][/W/<password, if provided>])+
.
For more information on router strings, see Router Strings in SAP Help.
...
Activates the JCo traces to get more information that can help analyzing the connection related errors.
Default value: Not selected
...
Select this checkbox to clear the JCo Metadata cache on the plex node before validating the account.
Default value: Not selected
...
This field set enables you to specify JCo parameters and respective values for SAP Secure Network Communications (SNC) authentication.
Only one JCo parameter can be specified in each row. Click to add a new row in this table and define the values accordingly.
This field set comprises the following fields:
- Property name
- Property value
Note | ||
---|---|---|
| ||
Leave the Username and Password fields blank while passing values in the form of JCo properties, as part of SAP SNC authentication. |
...
Specify the name of the JCo parameter to be passed for SAP SNC authentication. Alternatively, select the parameter from the Suggestions drop-down list.
Default value: None
Example: jco.client.user
, jco.client.passwd
, jco.client.cert1
...
Specify the value for the JCo parameter needed for SAP SNC authentication. If you have the JCo parameters defined at a Pipeline-level, pass the Pipeline parameter names as expressions.
Default value: None
Example: johndoe
, pass*word#4
Account Encryption
...
If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.
...
If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account.
Account:
- High: Password
- Medium + High: Username, password
- Low + Medium + High: Username, password, Application Server, System number
SAP Load Balanced JCo Account
...
title | Account Settings |
---|
The SAP Load Balanced JCo Account is used to connect to a message server.
Label*
...
Username*
Specify a SAP username for the account.
Note | ||
---|---|---|
| ||
Username is not required for authentication through SAP SNC. See Advanced JCo Properties for more details. |
Password
Specify a password for the username.
Note | ||
---|---|---|
| ||
Password is not required for authentication through SAP SNC. See Advanced JCo Properties for more details. |
...
Language*
...
Client*
...
Message server*
...
System ID*
...
Logon group
...
Peak limit*
...
Specify the maximum number of active connections that you can create simultaneously for a destination.
Note |
---|
Recommended value could be <100 as too many connections may impact JCC performance. |
Default value: 5
...
Connection pool capacity*
...
Router string
...
Specify the SAP Router string required for making connections to systems that are behind a SAP Router. An SAP router string contains a chain of SAP routers with their port numbers, and has the form (/H/<host>[/S/<port>][/W/<password, if provided>])+
.
For more information on router strings, see Router Strings in SAP Help.
...
Activates the JCo traces to get more information that can help analyzing the connection related errors.
Default value: Not selected
...
Select this checkbox to clear the JCo Metadata cache on the plex node before validating the account.
Default value: Not selected
...
This field set enables you to specify JCo parameters and respective values for SAP Secure Network Communications (SNC) authentication.
Only one JCo parameter can be specified in each row. Click to add a new row in this table and define the values accordingly.
This fieldset comprises the following fields:
- Property name
- Property value
Note | ||
---|---|---|
| ||
Leave the Username and Password fields blank while passing their values in the form of JCo properties, as part of SAP SNC authentication. |
...
Specify the name of the JCo parameter to be passed for SAP SNC authentication. Alternatively, select the parameter from the Suggestions drop-down list.
Default value: None
Example: jco.client.user
, jco.client.passwd
, jco.client.cert1
...
Specify the value for the JCo parameter needed for SAP SNC authentication. If you have the JCo parameters defined at a Pipeline-level, pass the Pipeline parameter names as expressions.
Default value: None
Example: johndoe
, pass*word#4
Account Encryption
...
If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.
...
If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account.
Account:
- High: Password
- Medium + High: Username, password
- Low + Medium + High: Username, password, Application Server, System number
SAP Configurations
Installing JCO Library
Install the SAP Java Connection (JCO) library for this Snap Pack to work.
Windows
- In all nodes of the Snaplex, install
sapjco3.dll
in %SL_ROOT%\ldlib (usually, c:\opt\Snaplogic\ldlib). - Upload the
sapjco3.jar
file into the project that you want to use for SAP integration. - Set the Windows PATH variable to point to c:\opt\Snaplogic\ldlib. Restart the Snaplex (JCC).
If an MSHOST is configured, add
sapms<SystemID><MSHOSTPort>/tcp, for example:
to %WINDIR%\System32\drivers\etc\services.sapmsABA 3301/tcp
,
Linux
- In all nodes of the Snaplex, install
libsapjco3.so
in $SL_ROOT/ldlib (usually /opt/Snaplogic/ldlib). - Install
libsapjco3.jnilib
in $SL_ROOT/ldlib (usually /opt/Snaplogic/ldlib). - Upload the
sapjco3.jar
file into the project that you want to use for SAP integration. Restart the Snaplex (JCC). - If an MSHOST is configured, add
sapms<SystemID><MSHOSTPort>/tcp
, for example:
to /etc/services. For example,sapmsABA 3301/tcp
,sapmsABA 3301/tcp
.
Note |
---|
Please update the following native library files under $SL_ROOT/ldlib/: a) libsapjco3.so for Linux-based JCC nodes. |
BAPI and IDoc Integration
BAPI (Business Application Programming Interface) and IDoc (Intermediate Document) are different interfaces that SAP ERP provides to enable business-data exchange across SAP and non-SAP platforms.
BAPI is a library of functions stored on the SAP platform that can be called by SAP or non-SAP platforms to perform specific operations. All related data is exchanged immediately and not stored anywhere during transit. SnapLogic uses the RFC (Remote Function Call) protocol provided by the SAP Java Component to call BAPI remotely.
IDocs, on the other hand, are formatted data containers that can be transferred between SAP platforms or non-SAP platforms. IDocs are stored in database tables on the SAP side, and can be sent to a receiver system using their ALE technology.
The SAP Execute Snap is calls a BAPI function, while the IDoc (Document) Listener, IDoc Read and IDoc Write Snaps use IDocs to integrate with SAP.
Configuring SAP for BAPI Integration
There is no additional configuration required for standard BAPI integration other than ensuring that the configured SAP user has sufficient roles/privileges to access and invoke the desired BAPIs. If the standard functions do not meet your integration requirements, you must design and implement a custom function according to your needs.
Configuring SAP for IDoc Integration
The following configurations are required in SAP to send or receive IDocs.
Set up the logical system and distribution model, and generate the partner profile. For more information, see SAP Help: Implementation - IDoc Interface/ALE - SAP Library and SCN Welcome | SCN.
- Add a logical system using transaction code SALE.
- Create/Change the distribution model using transaction code SALE or BD64.
- You may either create a new model view or edit an existing one. Then add sender/receiver (Logical System) and message types.
- Generate partner profiles. Use the transaction code we20.
Additional SAP Configuration for Outbound IDoc Integration
The following configurations are required in SAP to send outbound IDocs to the SnapLogic SAP account.
- Register the external program in the SAP gateway by editing the reginfo file. For additional information, see Gateway Security Files secinfo and reginfo.
- Import reginfo in Gateway using the transaction code SMGW.
- Create RFC Destination of Type = 'T' (TCP/IP). For additional information, see SAP JCo Server Programming.
- Check the gateway monitor to ensure that the connection is registered correctly.
- Create a port using transaction code WE21.
Local TID Database Configuration (Outbound IDoc Only)
...
✔ | ✔ | |
✔ | ✔ | |
✔ | ✔ | |
✔ | ✔ | |
✔ | ✔ | |
✔ | ✔ |
Configuring SAP Accounts Using SnapLogic Designer
Drag an SAP Snap to the Canvas and click the Snap to open its settings. Click the Account tab. You can now either use an existing account or create a new one.
Selecting an existing account
SnapLogic organizes and displays all accounts to which you have access, sorting them by account type and location. To select an existing account:
In the Account tab, click the Expand icon to view the accounts to which you have access, and select the account that you want to use.
Click the Save icon.
Creating an account
In the Account tab, click Add Account below the Account Reference field.
Select the Location where you want to create the account, select the SAP Account Type, and click Continue. The Add Account dialog window associated with the account type is displayed.
Configure the settings relevant to your account. Learn more about SAP JCo Account and SAP Load Balanced JCo Account.
Click Validate to verify the account if the account type supports validation.
Click Apply to complete configuring the SAP account.
Info |
---|
Enter additional information on this account in the Notes field of the Info tab. This will help you–and other users–understand the purpose of the account, especially if there are multiple accounts of the same type. |
Configuring SAP Accounts Using SnapLogic Manager
You can use Manager to create accounts without associating them immediately with Pipelines.
Accounts in SnapLogic are associated with projects. You can use accounts created in other projects only if you have at least Read access to them.
In the left pane, browse to the project for which you want to create the account and click > Account > SAP, followed by the appropriate account type. The Create Account dialog associated with the selected account type is displayed.
Repeat steps 3 through 5 in the Creating an account section.
Required Permissions in the SAP Account
Authorization Object | Parameter | Expected Value |
---|---|---|
|
|
|
|
| |
|
| |
|
|
|
|
| |
|
| |
|
| |
|
|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Related Links