Enterprise Data Catalog Scanner Configuration Guide > Configuring Business Intelligence Resources > SAP BW/4HANA
  

SAP BW/4HANA

SAP BW/4HANA is an enterprise data warehouse platform that captures, stores, and consolidates enterprise data.

Objects Extracted

The SAP BW/4HANA resource extracts metadata from the following assets in an SAP BW/4HANA data source:
Note: If the asset type does not include lineage, hierarchy, categories, and relationship information, you cannot view the following tabs in the Catalog:

Permissions to Configure the Resource

To configure SAP BW/4HANA, perform the following tasks:
  1. 1. Install Scanner transports.
  2. 2. Configure a user-authorization profile.
Installing Scanner Transports
To extract metadata from SAP BW/4HANA, you must import the Scanner transports that Enterprise Data Catalog uses to extract metadata from SAP BW/4HANA. The transports are located in the SAP_Scanner_Binaries.zip file that is downloaded from the Informatica installer location.
Configuring User-Authorization Profiles
The SAP Business Warehouse administrator needs to create the product and development user authorization profiles. The following table describes the user authorization profiles:
Authorization Object
Description
Class
Field Values
S_RFC
Authorization check for RFC access
Cross Application Authorization Objects
ACTVT: 16 (Execute)
RFC_NAME:
DDIF_FIELDINFO_GET
RFCPING
RFC_GET_FUNCTION_INTERFACE
RFC_METADATA_GET
ZINFA_BW4H_FG
RFC_TYPE : FUGR, FUNC
S_RS_COMP
Business explorer components
Business Warehouse
ACTVT : 03,16 RSINFOAREA: * (Full Authorization)
RSINFOCUBE: * (Full Authorization)
RSZCOMPID: * (Full Authorization)
RSZCOMPTP: Full Authorization
S_RS_COMP1
Business explorer components: Enhancements to the owner
Business Warehouse
ACTVT : 03,16
RSZCOMPID: * (Full Authorization)
RSZOWNER: * (Full Authorization)
RSZCOMPTP: * (Full Authorization)

Prerequisites

  1. 1. Disable Catalog Service.
  2. 2. Download the sapjco3.jar file, and then copy the file to the following location: <Install_directory>/services/CatalogService/access/WEB-INF/lib.
    3. Note: The SAP Java Connector version supported is 3.1.4.
  3. 3. Download the libsapjco3.so file and copy the file to the following location: <Install_directory>/services/shared/bin.
  4. 4. Create a SAPJCO.zip file and add the following file to the first level directory of the .zip file: libsapjco3.so
  5. 5. Copy the .zip file to the following location: <Install_directory>/services/CatalogService/ScannerBinaries
  6. 6. Enable Catalog Service.

Prerequisites to use Secure Network Communications (SNC) connection

  1. 1. Disable the Catalog Service.
  2. 2. Download the sapjco3.jar file and copy the file to the following location: <Install_directory>/services/CatalogService/access/WEB-INF/lib
    3. Note: The SAP Java Connector version supported is 3.1.4.
  3. 3. Download the libsapjco3.so file, and then copy the file to the following location: <Install_directory>/services/shared/bin
  4. 4. Configure the SNC connection type with X.509 certificate. For more information about the steps to configure SNC connection type, see the SAP documentation.
  5. 5. Create and set the SECUDIR environment variable for the Catalog Service as the location of the libsapcrypto.so file.
  6. 6. Include the following files in the SAPJCO.zip file:
  7. 7. Copy the SAPJCO.zip file to the following location: <Install_directory>/services/CatalogService/ScannerBinaries
  8. 8. Enable the Catalog Service.
  9. 9. In a multi-node cluster, verify that you perform the following tasks:

Basic Information

The General tab includes the following basic information about the resource:
Information
Description
Name
The name of the resource.
Description
The description of the resource.
Resource type
The type of the resource.
Execute On
You can choose to execute on the default catalog server or offline.

Resource Connection Properties

The General tab includes the following properties:
Property
Description
SAP Server Type
The type of SAP server installation:
  • - SAP Central Instance
  • - SAP Load Balancer (Message Server)
Server Host
Host name or IP address of the system that hosts the SAP Business Warehouse.
Login Group
Login group is a group of servers that belong to an SAP system. Login groups distribute user logins to individual instances or groups of SAP instances or application servers. Login groups are maintained in the transaction SAP Logon Groups (SMLG).
The option appears when you select SAP Load Balancer (Message Server) as the SAP Server Type.
Message Server Port
Default port of the Message server.
The option appears when you select SAP Load Balancer (Message Server) as the SAP Server Type.
System Number
System number of the SAP Business Warehouse.
The option appears when you select SAP Central Instance as the SAP Server Type.
SAP SID
The SAP System Identifier of the SAP instance.
Client
The SAP Business Warehouse client to access data from the SAP Business Warehouse.
Language
The language for metadata import from the resource. The selected login language is used to extract the SAP descriptions.
Connection Type
The type of SAP server connection:
  • - Basic
  • - Secure Network Communications (SNC). You can use the connection type to extract metadata from the SAP BW/4HANA data source.
Username
SAP Business Warehouse system user name.
Password
SAP Business Warehouse system password.
SNC Partner Name
The SNC name of the communication partner.
X.509 Certificate File Name
The file name of the X.509 certificate as the log in ticket.
SNC My Name
The SNC name of the user sending the Remote Function Call (RFC) from Enterprise Data Catalog.
SNC QoP
Specifies the level of protection to use for the connection.
Following are the available protection levels:
  • - 1. Authentication only
  • - 2. Integrity protection
  • - 3. Privacy protection
  • - 8. Use the value from the snc/data_protection/use location on the application server
  • - 9. Use the value from the snc/data_protection/max location on the application server
The default protection level is 3.
Auto Assign Connections
Indicates whether the connections must be assigned automatically.
The following table describes the properties that you can configure in the Source Metadata section of the Metadata Load Settings tab:
Property
Description
Enable Source Metadata
Enables metadata extraction
Source Extraction
The type of source metadata extraction:
  • - Full. Extracts the full metadata from the source.
  • - Based on Object Modified Date. Extracts metadata that is modified or created after the specified date. You must perform at least one full extraction before extracting metadata based on object modified date.
  • - Based on Query Execution Date. Extracts metadata based on the query execution date. The corresponding dependant metadata objects are also extracted.
Memory
The memory value required to run a scanner job.
Specify one of the following memory values:
  • - Low
  • - Medium
  • - High
Note: For more information about the memory values, see the Tuning Enterprise Data Catalog Performance article on How To-Library Articles tab in the Informatica Doc Portal
Custom Options
JVM parameters that you can set to configure scanner container. Use the following arguments to configure the parameters:
  • - -Dscannerloglevel=<DEBUG/INFO/ERROR>. Changes the log level of scanner to values, such as DEBUG, INFO, or ERROR. Default value is INFO.
  • - -Dscanner.container.core=<No. of core>. Increases the core for the scanner container. The value must be a number.
  • - -Dscanner.yarn.app.environment=<key=value>. Key pair value that you need to set in the Yarn environment. Use a comma to separate the multiple key value pairs.
  • - -Dscanner.pmem.enabled.container.memory.jvm.memory.ratio=<1.0/2.0>. Increases the scanner container memory when pmem is enabled. The default value is 1.
Track Data Source Changes
View metadata source change notifications in Enterprise Data Catalog.