After completing this lesson, you will be able to:
• Explain SAP HANA Direct Extractor Connection Setup & Configuration
All relevant information about setup and configuration is provided by Note 1665602 and Note 1583403.
You must go through following sap notes before you start the installation-
1583403 Direct extractor connection to SAP HANA
1670518 SAP HANA Direct Extractor Connection: Monitoring
1688750 DataSource: Reading a property in the source system
1701750 DataSource: Secondary Index on the PSA
1677278 DataSource: Changing the Key Definition (A version)
1710236 SAP HANA DXC: DataSource Restrictions
1714852 Troubleshooting SAP HANA DXC issues
You can get updated versions of these notes from the SAP Service Marketplace.
Ensure that the necessary technology components in SAP HANA are running, that is:
• The XSEngine
• The ICM service
Enabling XS Engine
Go to administration console configuration tab.
Expand daemon.ini section and then expand the sapwebdisp section.
For the instances parameter, a green light showing the number 1 on the Host column should be displayed.
If the value 1 is not displayed, double-click the instances parameter and change the configuration value from 0 to 1 and click Save.
In the same daemon.ini section, expand the xsengine section.
A green light showing value 1 under Host column should be displayed, if not then change it to 1 and save.
Check if the XSEngine is running by accessing the following URL:
Importing Delivery Unit
Download the delivery unit archive from SAP service marketplace and save in local computer.
Open SAP HANA studio and go to Modeler perspective.
In the Quick Launch window, choose Import.
Expand HANA content node and choose Delivery Unit, click Next.
Select client and browse to the folder on your local computer where you have stored your delivery unit archive.
Select the delivery unit archive and click OK.
The status in the Object import simulation should display green lights.
Keep the existing defaults and click Finish.
In the job log tab, you can see the status of the import.
Enable DXC Engine
In the administration console of your HANA instance, go to configuration tab.
Expand the xsengine.ini section and then expand the application_container section.
Right click the application_list parameter and select Change from the context menu.
In the new value field, enter libxsdxc
If another value is already present, put a comma and enter value libxsdxc
Save your entry.
In order to make the new configuration active, you need to restart the XSEngine.
In the administration console, go to Landscape tab.
Right click the xsengine service and select Reconfigure service.
Choose Yes to confirm.
To check the setup of DXC, a python script is provided.
Unzip the file DXCConnectionTest.zip attached to Note 1665602.
Use ftp or a similar utility to place the connection test file from the ZIP file on the Linux file system, in location such as /usr/sap/<SID>/HDC<sysnum>/backup.
Run the python script with the following command (provide password for SYSTEM user):
python connectionTest.py –httpport=80<instance number> –dbpwd
=<password for SAP HANA database>
If the connection test was successful, you will see the following results: Testing connectivity of url: http://localhost:80<instance number>/ DXC/DXC.xscfunc Using database user 'SYSTEM' and password '<password>' Sending first request (unauthorized)... done. Response status is 401 Unauthorized (as expected) Sending second request (authorized)... done. Response status is 200 OK (as expected) CONNECTION TEST SUCCESSFUL
Check if DXC is operational. The DXC application should be accessible
now by using the following URL:
If the check is successful, you will be prompted to save a file with the name dxc.xscfunc to your computer. The contents of this file are not important; the test is successful if calling this URL produces this file.
Creating a DXC user and schema in SAP HANA
Create a user who has the privileges to execute the DXC extraction and load.
In the HANA studio, go to Catalog -> Authorization -> Users
Right click user and select New user.
In the user name field, enter an appropriate name for example DXCUSER
Select internal authentication, enter password and confirm password.
On the Granted Roles tab, add the roles PUBLIC and MONITORING
Click the green Deploy icon.
Now create a schema.
Create a schema for use with DXC connection which is owned by DXC user.
Note: As recommended by SAP, you should create a separate schema for each specific SAP system that you will connect to HANA using DXC.
In HANA studio, execute the following SQL command:
CREATE SCHEMA <schema name> OWNED BY <dxcusername>
CREATE SCHEMA r3source OWNED BY dxcuser.
Click deploy or press F8 to create the schema.
Create HTTP connection to the SAP HANA system
Go to your source SAP Business suite system.
Create HTTP destination of type G using transaction SM59.
On the Configuration of RFC connections screen, select the node HTTP connections to External server and click Create icon.
Provide a name for the HTTP destination for example DXC_HANA_CONNECT_<SID>
In the Technical Settings tab, enter the target host name and port number of your remote SAP HANA system in the Target host and Service No. fields.
Note: The port number is 80<instance number> of your SAP HANA database.
In the Path Prefix field, enter “/sap/hana/dxc/dxc.xscfunc ” (depends of HANA version)
On the Logon & Security tab, choose Basic Authentication and provide the user name and password of your DXC user.
Configure DXC HTTP Interface Destination
Create an entry in the table RSADMIN, which is the primary BW configuration table. In this table, the HTTP destination to the SAP HANA system created earlier is designated as the connection used for DXC.
Use transaction SE38 to execute the program SAP_RSADMIN_MAINTAIN
• In the OBJECT field, enter the value PSA_TO_HDB_DESTINATION.
• In the VALUE field, enter the name of the HTTP destination you created, for example DXC_HANA_CONNECTION_<SID>.
Note: Make sure that you use upper and lower case letters for the name of the HTTP destination correctly.
Click Update, and then click Execute (F8) to create the table entry.
Choose the system wide setting for Datasources
Use transaction SE38 to execute the program SAP_RSADMIN_MAINTAIN.
Create an additional entry object PSA_TO_HDB. In the VALUE field, enter either the value GLOBAL, SYSTEM or DATASOURCE, depending on the option which is best in your scenario:
All DataSources are available for use with DXC. When you choose this value, it is no longer possible to execute any BW processes or reports in the source system.
Keep in mind that this refers to the BW system used with DXC (which is typically the embedded BW inside an SAP Business Suite system, which is very often not used). If you have a separate SAP BW system connected to this SAP Business Suite system, this setting has no impact (except in the “sidecar” scenario, where it does).
Only the specified clients are used with DXC. The remaining clients are available for DataSources to be extracted, transformed and loaded into the PSA of the SAP BW system (embedded BW system).
Only the specified DataSources are used with DXC. Any DataSources not specified can be extracted, transformed and loaded into the PSA of the SAP BW system. If this SAP BW system (embedded BW or sidecar BW) is used for other purposes besides DXC, then choose this option. However, keep in mind that any DataSources you choose to be used by DXC cannot be used in this (embedded or sidecar) SAP BW system.
Once you have decided on the appropriate configuration setting, enter the text for that choice (for example DATASOURCE), and click Insert.
Click Execute (F8) to create the table entry.
Designate the Schema in SAP HANA to Store IMDSOs
Within the SAP HANA database, an In-Memory DataStore Object (IMDSO) is generated for each DataSource.
Use transaction SE38 to execute the program SAP_RSADMIN_MAINTAIN.
Create the entry object PSA_TO_HDB_SCHEMA. In the VALUE filed, enter the name of the SAP HANA database schema to use, for example r3source.
The remaining steps are similar to what we do in usual BW system-
- Activate Business content datasources or create new datasources
- Replicate datasources
- Create Infopackage
- Monitor data load
- Go to HANA schema and check the data loaded
- Create process chain
- Monitor activation process of IMDSO
Below are the tables created after datasource activation-
/BIC/A<datasource name>00 – active table of records, used in HANA modeling
/BIC/A<datasource name>40 – activation queue table, data comes here before activation to maintain the sequence
/BIC/A<datasource name>70, 80, AO etc. are technical tables used to create the activation process.