In this article
| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 2 |
|---|
| absoluteUrl | true |
|---|
|
...
You can use this account type to connect <Snap Pack name> SAP Snaps with data sources that use <Account Type Name> the SAP Load Balanced JCo account.
Prerequisites
Valid client ID.
Valid tenant URL.
...
...
Limitations
Limitations
None
Known Issues
...
Supports only reading JSON files.
...
None
Account Settings
<Insert image here>
| Appsplus panel macro confluence macro |
|---|
| data | {"features":["title","icon","rounded","collapsible","border"],"title":"Documenting Fields Based On Data Type/UI Element","titleColor":"#000000","titleColorBG":"#ff5c30","titleSize":"14","titleBold":true,"titleItalic":false,"titleUnderline":false,"lozenge":"Hot stuff","lozengeColor":"#172B4D","lozengeColorBG":"#fff0b3","height":200,"panelPadding":12,"panelColor":"#172B4D","panelColorBG":"#FFFFFF","borderColor":"#ff5c30","borderRadius":3,"borderStyle":"solid","borderWidth":1,"icon":"editor/info","iconPrimary":"#FFFFFF","iconSecondary":"#0052CC","newMacro":false} |
|---|
|
**Delete Before Publishing** Choose from the following sentences to document specific field types. Drop-down lists/Option Buttons (radio buttons): You must list the LoV and describe them if their meaning isn't apparent. In this case, format the LoV in italics, regular font for the LoV's description. In either case, list the LoVs as a bullet list. <State what the should do in this field>. The available options are: <bullet list of LoVs>
Specify the Salesforce API to be used. The available options are:... Select the <category> that you want to use. Available options are...
* Option 1<italicized>. <third person singular form of the verb>
* Option 2<italicized>. <third person singular form of the verb>
Select the API that you want to use. Available options are:
Bulk API. Sends the Snap execution request details as a bulk API call.
REST API. ...
OR
Select one of the three following modes in which the Snap executes:
* Validate & Execute. Performs limited execution of the Snap and generates a data preview during Pipeline validation, then performs full execution of the Snap (unlimited records) during Pipeline runtime.
* Execute only. Performs full execution of the Snap during Pipeline execution without generating preview data.
* Disabled. Disables the Snap and all Snaps downstream from it.
Check boxes: If selected, <Snap behavior>.
If selected, an empty file is written when the incoming document has no data. If selected, <behavior>. If not selected/Otherwise, <behavior>
Use "If not selected" if the first sentence is long.
If selected, the Snap uses the file path value as is. Otherwise, the Snap uses the file path value in the URL.
If selected, an empty file is written when the incoming document has empty data. If there is no incoming document at the input view of the Snap, no file is written regardless of the value of the property. Select to <action>
Use this if the behavior is binary. Either this or that, where the converse behavior is apparent/obvious.
Select to execute the Pipeline during validation.
Text Fields Describe what the user shall specify in this field. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc.
Enter the name for new account.
Specify the account ID to use to log in to the endpoint.
Required if IAM Role is selected.
Do not use this field if you are using batch processing.
Numeric Text Fields Describe what the field represents/contains. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc. Include special values that impact the field's behavior as a bullet list.
The number of records in a batch.
The number of seconds for which you want the Snap to wait between retries.
The number of seconds for which the Snap waits between retries.
Use the following special values:
* 0: Disables batching.
* 1: Includes all documents in a single request.
Notes in field descriptions Confluence’s new editor does not allow nesting of most macros inside another macro, especially the Note/Alert/Warning/Info (Panel) macros inside a table macro and Excerpt macros inside Expand or Panel Macro+ macros. So, as a workaround use the Footnotes approach as mentioned below: Assign numbers at the Note locations in the form of follow through phrases like See Note 2 below this table. or such. Add your Notes---an appropriate Note/Alert/Warning/Info (Panel) macro---immediately below the macro (for example, Table macro) beginning the content with the corresponding number assigned.
|
| Info |
|---|
Asterisk ( * ): Indicates a mandatory field. Suggestion icon (  ): Indicates a list that is dynamically populated based on the configuration. Expression icon ( ): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic. Add icon ( ): Indicates that you can add fields in the fieldset. Remove icon ( ): Indicates that you can remove fields from the fieldset.
|
...
Field Name
...
Field Type
...
Field Dependency
...
Description
Default Value:
Example:
Label*
Default Value: ELT Database Account
Example: ELT RS Account
...
String
...
None.
Specify a unique label for the account.
...
Field set
Specify advanced parameters that you want to include in the request.
This field set consists of the following fields:
Field 1*
Default Value:
Example:
...
String
...
Debug mode checkbox is not selected.
Field 2
Default Value:
Example:
...
String
...
None.
Troubleshooting
...
Error
...
Reason
...
Resolution
...
Account validation failed.
...
The Pipeline ended before the batch could complete execution due to a connection error.
...
Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.
...
Related Links
...
Endpoint Doc Link 1
...
Endpoint Doc Link 2
...
Endpoint Doc Link 3
...
SnapLogic Glossary
...
Getting Started with SnapLogic
...
| Info |
|---|
Asterisk (*): Indicates a mandatory field. Suggestion icon (): Indicates a list that is dynamically populated based on the configuration. Expression icon ( ): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic. Add icon ( ): Indicates that you can add fields in the fieldset. Remove icon ( ): Indicates that you can remove fields from the fieldset
|
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 | String | Specify a unique and meaningful label for the account instance |
|---|
Username* Default Value: N/A
Example: SAP User | String | Specify the SAP username for the account. | Note |
|---|
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: lkj(83@%_sd | String | Specify a password for the username. | Note |
|---|
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* | String | Specify the SAP message server address. |
|---|
System ID* | String | Specify the SAP system ID. |
|---|
Logon group | String | Specify the SAP logon group. |
|---|
Peak limit* | Integer | 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* | 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 | Checkbox | Activates the JCo traces to get more information that can help analyze the connection-related errors. Default value: Not selected |
|---|
Reload Metadata on Validate | Checkbox | Select this checkbox to clear the JCo Metadata cache on the plex node before validating the account. Default value: Not selected |
|---|
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
| Note |
|---|
For SAP SNC authentication Leave the Username and Password fields blank while passing their values in the form of JCo properties, as part of SAP SNC authentication. |
|
|---|
Property name | 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. Default value: None
Example: jco.client.user, jco.client.passwd, jco.client.cert1 |
|---|
Property value | 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. Default value: None
Example: johndoe, pass*word#4 |
|---|
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
| Expand |
|---|
| title | 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. |
|
