Versions Compared

Old Version 1

changes.mady.by.user Kalpana Malladi

Saved on

compared with

New Version Current

changes.mady.by.user Kalpana Malladi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article

Table of Contents
minLevel1
maxLevel2
absoluteUrltrue

...

You can use this account type to connect <Snap Pack name> SAP Snaps with data sources that use <Account Type Name> account.

Prerequisites

  • Valid client ID.

  • Valid tenant URL.

  • ...

  • ...

Limitations

Known Issues

  • Supports only reading JSON files.

  • ....

Account Settings

<Insert image here>

...

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.

...

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 default login behavior of the JCo library changed. 

  • The default value of property jco.client.snc_sso was changed from 0 to 1 (enabled).

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.

Panel
bgColor#EAE6FF

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

...

Info

  • Asterisk (*): Indicates a mandatory field.

  • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( (blue star) ): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( (blue star) ): Indicates that you can add fields in the fieldset.

  • Remove icon ( (blue star) ): Indicates that you can remove fields from the fieldset

...

Field Name

Field Type

Field Dependency

Description

Description

Label*

Default Value: None
Example:

Label

 SAP Load Balanced JCo Account

String

Specify a unique and meaningful label for the account instance

Username*

Default Value:

 ELT Database Account

 N/A
Example:

 ELT RS Account

Field 1*

Default Value: 
Example: 

String

Debug mode checkbox is not selected.

Field 2

Default Value: 
Example: 

String

None

Admin

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

  • Field 2

  • Field 3

Specify the SAP username for the account.

For SAP SNC authentication, Username is not required for authentication through SAP SNC.

Password

Default Value: N/A
Example: p@s*w&8k!#l98

String

Specify a password for the username.

For SAP SNC authentication, Password is not required for authentication through SAP SNC.

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 to use corresponding to jco.client.

Message server*

Default Value: N/A
Example: saptest.mycloud.com

String

Specify the SAP message server address corresponding to jco.client.mshost.

System ID*

Default Value: N/A
Example: EH4

String

Specify the SAP system ID of the SAP system corresponding to the jco.client.r3name.

Logon group

Default Value: N/A
Example: SLTEST

String

Specify the SAP logon group of the load balanced connections which is identifying a set of SAP application servers corresponding to jco.client.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.

Note

We recommend you to use a value less than 100 as too many connections may impact the JCC performance.

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


Default Value: N/A
Example: /H/saprouter.hostname/S/1244/H/hostname/S/7244

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

Checkbox

Activates the JCo traces to get more information that can help analyze the connection-related errors.

Reload Metadata on Validate

Default Value: Deselected

Checkbox

Select this checkbox to clear the JCo Metadata cache on the Snaplex 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. 

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

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.

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.

...

...

Endpoint Doc Link 1

...

Endpoint Doc Link 2

...

Endpoint Doc Link 3

...

SnapLogic Glossary

...

Getting Started with SnapLogic

...

Pipeline failed to prepare.

SnapCcException: Not starting pipeline as pipeline has prepare error. "{57df90cf-a994-43ab-8caa-91b24d3e2300

Dependent native library not found or could not be resolved.

Could not initialize the account <account-name>.

  1. Copy the updated native library:

    • For Linux, copy the updated native library libsapjco3.so file to the /opt/snaplogic/ldlib folder on every node in the Snaplex.

    • For Windows, copy the updated native library sapjco3.dllfile to the C:\opt\Snaplogic\ldlib folder on every node in the Snaplex.
      Note: For Snaplexes with multiple nodes, make sure to install the library on every node.

  2. Restart all the nodes in the Snaplex.

Could not initialize account.

[com-snaplogic-snaps-sap-jcoaccount_2-438rc27664]:

Native library sapjco3 is an older version. The library found/opt/snaplogic/ldlib/libsapjco3.so has version "753.811", but the required version is at least 753.1324.

Ensure that the required native library is installed on each node of the snaplex.

Snap Pack History

Multiexcerpt include macro
macro_uuidd22a91e1-9468-49f8-be99-55f579cc4a95
nameSAP SPH
templateDataeJyLjgUAARUAuQ==
pageSAP Snap Pack
addpanelfalse

Related Content