The Palantir Foundry Connector 2.0 for SAP Applications ("Connector") is shipped as an SAP add-on to be installed via SAINT (SAP Add-On Installation Tool). The add-on is delivered in SAR format with the following filename pattern: FOUNDRY-SAPCONN-INST-SP00SPXX.SAR
SP00SPXX represents the installation files from SP00 to SPXX where XX is the support package level.
If the Connector is being installed on BW/4HANA or S/4HANA, include Attribute Change Packages in the installation. As of SP22, these packages are included in the installation file.
These are the high-level steps required to setup the Connector:
SAINT.SU01.or
Ensure that the following SAP note has been read and the relevant steps followed where applicable:
2645739 - ABAP Add-On OCS package is not digitally signed000 with a user authorized to use SAINT.SAINT transaction.FOUNDRY-SAPCONN-INST-SP00SPXX.SAR to the SAP Server; select Installation package > Load Packages > From Front End.For some SAINT/SPAM versions, SPAM or SAINT settings can impact the installation process. Disable the Signature check not possible, SAP note 2520826 is not implemented item under the Checks during import section. Note that for some SPAM versions, this item has no description at all, but should still be disabled.
PALANTIR and PALCONN.If warnings are flagged during the installation, follow the steps described in the warning message to resolve. In most cases, warning messages can be ignored for Connector and Remote Agent installations. In particular, the warning message with the heading "Open Data Extraction Requests" can be ignored because the installation does not make changes to DDIC structures and therefore will not cause open data extraction requests to terminate.
The Connector Post Installation Wizard simplifies the setup activities after Connector add-on installation. To perform post-installation and configuration, login to the main client (not 000). The Post Installation Wizard can be accessed either using transaction code /n/PALANTIR/POST_INST or from the Connector menu (transaction code: /n/PALANTIR/).
There are 10 steps which can be run together or individually. To finish the installation, all steps need to be enabled. If this is not an SLT installation, disable Create SLT configuration. SLT configuration is detailed in step 7.
The performing user needs sufficient authorization to assign required authorization roles to the Foundry technical user. This process is similar to maintaining a user via the SU01 transaction code. If the user assignment is done separately, disable Assign Roles to Foundry User and Perform Healthcheck.
This step runs a background program which fixes SAP packages in the Connector Object Directory. This correction program can be run at any time with no adverse side effects.
This step activates two Connector services that are required for data transfer. Note that this can be done manually with the SICF transaction code if desired. The two services are:
/default_host/sap/palantir/default_host/sap/opu/odata/palantirThe Connector has its own set of roles which are imported during installation. These roles stay in an ungenerated status after installation. If desired, mass generation of these roles can be done manually with the PFCG transaction code using Utilities > Mass Generation.
/PALANTIR/CONTENT_BEX_ALL/PALANTIR/CONTENT_CDS_ALL/PALANTIR/CONTENT_HANA_ALL/PALANTIR/CONTENT_DM_ALL/PALANTIR/CONTENT_EXT_ALL/PALANTIR/CONTENT_FUNCTION_ALL/PALANTIR/CONTENT_INFOPROV_ALL/PALANTIR/CONTENT_SLT_ALL/PALANTIR/CONTENT_TABLE_ALL/PALANTIR/CONTENT_TCODE_ALL/PALANTIR/DEBUG_USER/PALANTIR/MONITORING/PALANTIR/OAUTH_CLIENT/PALANTIR/SERVICE_SLT/PALANTIR/SERVICE_SLT_740/PALANTIR/SERVICE_USERAll Palantir roles in step 3 will be assigned to the SAP user that is defined in the selection screen.
If this step generates error messages about role assignment, inability to retrieve user details or lack of authorization, this suggests that the user running the Post Installation Wizard does not have sufficient permission. In this case, follow the suggestions in the error messages to correct the user's authorization and run the program again.
If this step generates error messages that suggest the Foundry user is locked, contact the owner of the lock to have it removed before running the program again.
Resource check and continuous resource check parameters can be set via these selections. Default values are in the selection screen and can be changed according to your requirements. When the program is run with this selection, the Connector parameters will be modified according to the selected parameters. These parameters can also be maintained using transaction code /n/PALANTIR/PARAM.
Learn about performance parameters.
This step verifies ICM settings, hostname and ports (for HTTP and HTTPS), and creates URLs that can be used to test the connection.
This step is only relevant if the connection is via an SAP SLT Replication Server.
If the Connector is installed on top of an SAP SLT instance, a new SLT configuration (ODP) can be created by the Post-Installation Wizard. You can also create an SLT configuration using the LTRC transaction code.
The parameters of an SLT configuration are as follows:
| Parameter | Description |
|---|---|
Context Name | Unique configuration name. |
Context Description | Context Description that will be shown to the user in SAP transaction LTRC and in Foundry. |
Data Transfer Jobs | Number of data transfer jobs. |
Initial Load Jobs | Number of jobs for initial loads. |
Calculation Jobs | Number of calculation jobs for initial load range calculations. |
Authorization Group | No Authorization Group by default. |
Replication Mode | 1 - Real Time (Default); 2 - Time Interval; 3 - Time Schedule; 4 - On Demand. |
Source RFC Destination | Logical Destination - RFC Destination name of Source System. |
Read from Single Client | Enable if data will be read from a single client. |
Allow Multiple Usage | Enable if multiple usage is allowed. |
The Connector has various metrics to measure health in the installed SAP system. The connector performs health checks in the following categories:
AGENT: Checks RFC connection and source system authorizations. Only relevant for remote connections via a gateway.AUTHORIZATION: Checks whether the Foundry user has any missing authorization in SM53.CONNECTOR: Checks whether the Connector housekeeping job is scheduled in the system.ROLE: Checks the Foundry user's roles and authorization profiles.SLT: Checks whether SLT configuration is correct and healthy; for example, whether BADI_Implementation is active, Context is active, SLT housekeeping job is scheduled, or source system connection is working.After installation, it is important to check if the Connector is running properly by conducting connectivity tests with a web browser. The required URLs are generated by the Post-Installation Wizard.
There are several different tests available. The first and second test are synchronous calls to the Connector service; the third and fourth are for batch extraction.
table object type.table object type.After running the program with Source Definition in Foundry checked, a new tab, “Source Definition”, will be shown with details for the source configuration in Foundry.
More details can be found in Authorization roles.
The Connector has the following performance parameters to avoid unwanted system load when the system resources are insufficient to serve Foundry. These settings are compared with ST06 values.
The default parameter values listed below are for a fresh install of the latest connector version.
MEMORY_FREE: Free memory percentage. If this percentage is lower than the system default or user-defined value, extraction stops. Connector default is 5%.CPU_IDLE: CPU idle percentage. Connector default is 5%.CPU_USER: CPU utilization by user transactions. Connector default is 80%.CPU_LOAD: Total CPU utilization. Connector default is 80%.ST06 key figures are served by SAP to the Connector. If Enhanced Monitoring for virtualization is activated, the operating system-specific information is enriched by virtualization-specific information. This may affect ST06 figures and misguide the Connector. Refer to SAP OSS Article 2266266 for further details.
Initial system defaults are deliberately conservative. If you wish to override them to be more permissive, maintain via the /n/PALANTIR/PARAM transaction.
The following parameters are used to enable or disable resource checks:
| Param Id | Param Name | Param Values | Default | Description |
|---|---|---|---|---|
SYSTEM | CPU_CHECK | TRUE / FALSE | TRUE | Enables or disables CPU checks. |
SYSTEM | MEMORY_CHECK | TRUE / FALSE | TRUE | Enables or disables MEMORY checks. |
SYSTEM | RESOURCE_CHECK | TRUE / FALSE | TRUE | Enables or disables RESOURCE checks. If FALSE, all checks are disabled; if TRUE, other parameters (CPU_CHECK and MEMORY_CHECK) are checked. |
SYSTEM | CONTINUOUS_RESOURCE_CHECK | TRUE / FALSE | TRUE | Enables resource checks for all requests (init and all paging requests). If FALSE, resource checks are only carried out for the init request. |
SYSTEM | PROCESS_CHECK | TRUE / FALSE | TRUE | Enables checks on the minimum number of permitted work processes; works in conjunction with PROCESS_MIN_BG and PROCESS_MIN_DIA. |
SYSTEM_THRESHOLD | PROCESS_MIN_BG | numeric | 1 | Minimum required number of background process available on the SAP Application Server. |
SYSTEM_THRESHOLD | PROCESS_MIN_DIA | numeric | 1 | Minimum required number of dialog process available on the SAP Application Server. |
To check the actual values and parameter values, you can use the system object and resource function from a browser:
https://<sap-server>:<port>/sap/palantir/system?obj=resource
Note that this URL is an SAP system URL; you should ensure that this resource is accessible.
Output will be of this format:
MSGTYP MSGTXT
S Current CPU_LOAD value : 0,01 | system threshold value : 95,00
S Current CPU_USER value : 1,00 | system threshold value : 0,01
S Current CPU_IDLE value : 99,00 | system threshold value : 5,00
S Current free memory percentage : 24,22 | system threshold value : 11,00
S Current PROCESS_MIN_BG value : 5 | system threshold value : 2
S Current PROCESS_MIN_DIA value : 9 | system threshold value : 2
S Resource check is Active
S CPU Load check is Active
S Memory consumption check is Active
S Process availability check is Active