Category Archives: Jedox SAP Connectivity

Jedox to SAP Connectivity Part 3 – Importing Transport Requests

1 Reply

Continuing on from my prior post on SAP Connectivity Part 2, the next step is to import the transport requests into SAP. This is where you need the assistance of the SAP Basis Administrator, so make sure you have one on hand to assist through this process!

The SAP Add on consists of three transport packages. These are delivered during the Jedox installation with SAP connectivity which can be found in the following directory: \Jedox\Jedox Suite\tomcat\webapps\etlserver\config\sap\sap-trreq of your Jedox installation path. The below screenshot shows these transport requests:

Since these transport packages contain RFC function modules etc, these need to be copied into the SAP Application server. What you need to copy to the SAP Application server is largely dependent on what you need to extract from SAP into Jedox.

If you need to extract ERP data from SAP ERP (R/3) such as Cost Centres, Profit Centres etc. you will need to have eltsap_erp_trreq.zip and etlsap_rfc_trreq.zip copied to the SAP Application server.

If you need to extract SAP BW components such as Infoobjects, Infocubes, then you will need to have eltsap_bw_trreq.zip and etlsap_rfc_trreq.zip copied to SAP Application server.

In either case, you will need to unzip the relevant files, and copy the files to the SAP Application Server. Typically this would be done by the SAP Basis Administrator.

After you unzip the zip files, you will see prefixed with K9 and R9. You will need to do the following:

– Files starting with K9*, copy to directory <drive>:\usr\sap\trans\cofiles

– Files starting with R9*, to directory <drive>:\usr\sap\trans\data

The transport files need to be imported into SAP system using Transport Manager (transaction code: STMS) , this is something SAP Basis Administrator typically performs.

Once the transport requests have been imported into SAP, you can then establish connectivity in Jedox through to the SAP system. In Jedox ETL, create a Connection step using “SAP” Connection type, and enter the relevant details as shown in the screen shot below:

Click the ‘test’ icon to test connection. The following screen should come up if connection is successful.

If you get to this point, you are now connected to SAP from Jedox . Congratulations!!

In my next post, we will cover off some of the SAP extract types that you can use in Jedox ETL.

Jedox to SAP Connectivity Part 2 – Setting up the Jedox SAP Connector

2 Replies

Continuing on from my prior post on SAP Connectivity Part 1, the next step is configuring the SAP Connector in Jedox ETL.

After you have successfully installed SAP JCo Connector, you need to select the SAP Connector component during the Jedox all-in-one install process. This will install the Jedox ETL SAP Connector where it establishes the connection to SAP and supports several extract types.

At the time of the Jedox installation, you need to tick the check box for SAP Connectivity:

The following screen comes up where you would need to specify the directory path where the SAP JCO connector files are stored. Select the location:

During the installation of the SAP Java Connector, the files sapjco3.jar and sapjco3.dll are installed on the server. When you install Jedox with the SAP Connector, the installer copies these files to the folder {Jedox-Suite-install-path}\tomcat\webapps\etlserver\WEB-INF\lib_external.

For Jedox to be able to connect to SAP, you need to confirm that your Jedox Suite licence key has SAP Connectivity enabled. Go to System Manager , then click on Licences:

If you do not see SAP Connector listed, you cannot connect to SAP via the Jedox SAP Connector. If it is not listed, please contact your Jedox representative for further information.

Ok, we are nearly there! In Part 3, I will step you through how to establish connectivity directly to the SAP system and confirm your connection in Jedox ETL. At ths point, We will need assistance from the SAP team (the BASIS Administrator) to import transport requests.

Jedox to SAP Connectivity Part 1 – The SAP Java Connector

2 Replies

Amongst other available connection types to other source systems, Jedox also provides connection to SAP R3 system.

The first step of configuring the Jedox SAP Connector is to setup the SAP Java Connector.

At the time of Jedox All-in-one suite installation, you can select the Jedox SAP Connectivity option. This consists technically of two components: A Jedox ETL Add-On which defines the SAP connection and extract types, such as SAP ERP content and SAP BW and SAP Add-On which has to be transported to the SAP System.

You need to have the SAP Java Connector Adapter Version 3 or higher downloaded on the machine where Jedox is installed. You will need to have a valid account to download it from SAP Service Marketplace. You need to download the relevant file based on your operating system.
Extract the relevant zip folder to a directory where Jedox is to be installed.
You will need to set the Environment Variables. Go to “Environment Variables” in the System Properties:

Create a new System Variable called: “CLASSPATH” which should specify the sapjco.3jar file in the SAP JCO install path, the below screenshot shows this:

In the existing System Variable called: “Path”, you need to add the entire SAP JCO install path in the variable value. The below screenshot shows that folder: sapjco3-NTAMD64-3.0.9 contains the SAPJCO3 dll, jar files etc:

To verify that the installation of SAP JCO has been done correctly, you can enter the following using command prompt: java -jar {sapjco-install-path}/sapjco3.jar.
Then the following screen of SAP Java Connector comes up. This indicates that the SAP JCO installation has been done successfully. If there was any error, you can see the errors in the window:

Note: For more information on SAP JCO Connector, you can open the Intro document in your SAPJCO install-path in a web browser: file:///c:/sapjco3-install-path/javadoc/intro.html

To follow on to the next steps in Part 2 of this post, please click here

%d bloggers like this: