You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 9
Next »
In this article
Overview
You can use this account type to connect SAP Snaps with data sources that use the SAP Load Balanced JCo account. The SAP Load Balanced JCo Account is used to connect to a message server (MSHOST - Message Server Host). Learn more about SAP Configuration.
Prerequisites
None
Known Issue
In version 4.28 (main14627), the SAP Snap Pack's bundled JCo library was upgraded to 3.1.4. Prior to that, version 3.0.6 was used.
In version 3.0.21 of SAP:
The above changes will impact your pipelines if you use a username/password for RFC login. Login would work with the SAP Snap Pack versions before 4.28 but will fail with versions 4.28 or later.
The following workarounds can help mitigate the issues:
Add the jco.client.snc_sso JCo property with a value of 0 (disabled). If the account still fails with a "Name or password is incorrect (repeat logon)
" error, even after adding this property, then reach out to the SAP team to enable the option "Permit Password Logon SAP GUI" for that specific user.
Select the Permit Password Logon for SAP GUI (User-Specific) checkbox as shown below:
The permit password option is effective only if the profile parameter snc/accept_insecure_gui
is set to U. (Unsecure login is permitted for specific users).
Account Settings
The SAP Load Balanced JCo Account is used to connect to a message server.
Field Name | Field Type | Description |
Label* Default Value: None Example: SAP Load Balanced JCo Account_unUsed | String | Specify a unique and meaningful label for the account instance |
Username* Default Value: N/A Example: snap_user | String | Specify the SAP username for the account.
For SAP SNC authentication, Username is not required for authentication through SAP SNC. See Advanced JCo Properties for more details.
|
Password Default Value: N/A Example: <Encrypted> | String | Specify a password for the username.
For SAP SNC authentication, Password is not required for authentication through SAP SNC. See Advanced JCo Properties for more details.
|
Language* Default Value: N/A Example: EN | String | Specify the SAP language code. |
Client* Default Value: N/A Example: 800 | String | Specify the SAP client. |
Message server* Default Value: N/A Example: sap2.wftcloud.com | String | Specify the SAP message server address. |
System ID* Default Value: N/A Example: EH6 | String | Specify the SAP system ID. |
Logon group Default Value: N/A Example: SLENG | String | Specify the SAP logon group. |
Peak limit* Default Value: N/A Example: 5 | Integer | Specify the maximum number of active connections that you can create simultaneously for a destination. |
Connection pool capacity* Default Value: N/A Example: 1 | Integer | Specify the maximum number of idle connections to be kept open by the destination. No connection pooling takes place when the value is 0. |
Router string | String | Specify the SAP Router string required for making connections to systems that are behind the 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. |
Enable trace Default Value: Deselected Example: Selected | Checkbox | Activates the JCo traces to get more information that can help analyze the connection-related errors. |
Reload Metadata on Validate Default Value: Deselected Example: Selected | Checkbox | Select this checkbox to clear the JCo Metadata cache on the plex node before validating the account. |
Advanced JCo properties | 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
|
Property name Default value: None Example: jco.client.user , jco.client.passwd , jco.client.cert1 | String/Expression/Suggestion | Specify the name of the JCo parameter to be passed for SAP SNC authentication. Alternatively, select the parameter from the Suggestions drop-down list. |
Property value Default value: None Example: johndoe , pass*word#4 | Integer/Expression | 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. |
Account Encryption
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. |
---|
Enhanced Encryption | 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
|
---|
Snap Pack History
Click to view/expand
Release | Snap Pack Version | Date | Type | Updates |
---|
4.29 Patch | 429patches16637 | 07 Jul 2022 | Latest | Fixed an issue with the SAP IDoc Write Snap where the Snap wrote the same TID, Document_number, and so on for the different output documents though the I_DOCNUM array contained all the document numbers that are returned from SAP table. Now, the Snap writes different TID, Document_number for different output documents along with the I_DOCNUM array that contains all the document numbers. Fixed an issue with SAP Execute and SAP IDoc Write Snaps where the output preview did not include the original document.
|
4.29 Patch | 429patches16113 | 07 Jun 2022 | Latest | Fixed an issue with SAP Execute Snap where the Snap incorrectly handled connection exceptions for 104-JCO_ERROR_SYSTEM_FAILURE . Previously, the Snap captured only the output document without the error. Now, the Snap correctly captures both the output and error. |
4.29 | main15993 | 14 May 2022 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.29 | main15993 | 14 May 2022 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.28 | main14627 | 12 Feb 2022 | Stable | Upgraded the Java Native Library used by the SAP Java Connector (JCo) to version 3.1. Breaking change for Pipelines containing Snaps from the SAP Snap Pack with Java Native Library This upgrade may cause your existing Pipelines to break if they contain Snaps from the SAP Snap Pack. You must manually upgrade your SAP Java Connector (JCo) Native Library to version 3.1.4 for these Pipelines to run successfully. See SAP Configurations for more information.
|
4.27 Patch | 427patches13992 | 12 Jan 2022 | Latest | |
4.27 Patch | 427patches12999 | 23 Nov 2021 | Latest | Enhanced SAP RFC Listener, SAP IDoc Listener and SAP IDoc Document Listener Snaps with a new field set Advanced JCo Server Properties that allows you to configure Java Connector (JCo) server-related attributes. |
4.27 | main12833 | 13 Nov 2021 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.26 | main11181 | 14 Aug 2021 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.25 Patch | 425patches10571 | 04 Aug 2021 | Latest | Renamed the RFC Listener Snap as SAP RFC Listener Snap. |
4.25 | main9554 | 08 May 2021 | Stable | Introduced the SAP RFC Listener Snap that facilitates Remote Function Calls (RFCs) between two SAP systems. The Snap simulates an RFC server and listens to the incoming RFC calls infinitely. Subsequently, the Snap generates output documents either from the import parameters or triggers a child Pipeline. Business applications can use the RFC mechanism to communicate and exchange information (in predefined formats) with other systems. |
4.24 | main8556 | 13 Feb 2021 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.23 | main7430 | 14 Nov 2020 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.22 Patch | 422patches7378 | 05 Nov 2020 | Latest | Enhances the SAP Execute Snap to process the structure that contains nested Table Type fields in the output document by recursively parsing them into a Map or a List set. |
4.22 Patch | 422patches6796 | 30 Sep 2020 | Latest | Fixes the JCO_ERROR_REQUEST_CANCELLED (connection is closed) error in SAP Execute Snap that occurs even when the session is active after 10 minutes. |
4.22 Patch | 422patches6601 | 16 Sep 2020 | Latest | Enhances SAP Execute and SAP IDoc Write Snaps by introducing the following fields: |
4.22 Patch | 422patches6597 | 11 Sep 2020 | Latest | Enhances the SAP Execute Snap by introducing the following two fields: |
4.22 | main6403 | 12 Sep 2020 | Stable | |
4.21 | snapsmrc542 | 09 May 2020 | Stable | Enhances the SAP Execute Snap to add a new field, Output date time as Text, which enables you to output date and time as a String data type instead of a DateTime object. |
4.20 Patch | sap8811 | 20 Apr 2020 | Latest | Updates the SAP IDoc Write Snap with the following: Fixes the stack overflow error that occurs while retrying to write the IDoc to the SAP server. Adds inbound success codes to the default value which otherwise only indicates the IDoc being created. Enhances the error messages for a better user experience.
|
4.20 | snapsmrc535 | 08 Feb 2020 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.19 | snaprsmrc528 | 14 Nov 2019 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.18 | snapsmrc523 | 10 Aug 2019 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.17 | ALL7402 | 11 Jun 2019 | Latest | Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers. |
4.17 | snapsmrc515 | 11 Jun 2019 | Latest | Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box. |
4.16 | snapsmrc508 | 16 Feb 2019 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.15 | snapsmrc500 | 15 Dec 2018 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.14 | snapsmrc490 | 11 Aug 2018 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.13 | snapsmrc486 | 12 May 2018 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.12 | snapsmrc480 | 17 Feb 2018 | Stable | Added the retry connection and error routing mechanism to the SAP Execute, SAP iDOC Read, SAP iDOC Write, SAP iDOC Document Listener and SAP iDOC Listener Snaps. Updated the SAP Account with Enable trace property to analyse the connection related errors.
|
4.11 Patch | sap4514 | 18 Jan 2018 | Latest | Addressed an issue with the SAP iDoc Listener and iDoc Document Listener Snaps where the pipeline takes a longer time to stop while performing a manual trigger. |
4.11 Patch | sap4342 | 11 Dec 2017 | Latest | |
4.11 | snapsmrc465 | 11 Nov 2017 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.10 | snapsmrc414 | 12 Aug 2017 | Stable | Added SAP account to connect to a message server, SAP Load Balanced JCo Account. |
4.9 Patch | sap3246 | 08 Jul 2017 | Latest | Added SAP account to connect to MSHOST (JCo Load Balanced account). Addressed an issue with SAP BAPI call appending duplicate fields to object SAP Execute: Support for "table-type" fields added Addressed an issue in SAP Execute: Changing parameter metadata not imported
|
4.9 Patch | sap3233 | 08 Jul 2017 | Latest | Addressed an issue with SAP Execute failing to call BAPI with integer request parameter |
4.9 | snapsmrc405 | 13 May 2017 | Stable | Introduced the SAP IDoc Document Listener Snap in this release. |
4.8 | snapsmrc398 | 11 Feb 2017 | Stable | Info tab added to accounts. |
4.7 | snapsmrc382 | 23 Nov 2016 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.6 | snapsmrc362 | 13 Aug 2016 | Stable | Upgraded with the latest SnapLogic Platform release. |
4.5.1 | snapsmrc344 | 18 May 2016 | Stable | Upgraded with the latest SnapLogic Platform release. |