SAPEX Installation for Remote Scenarios – Kiuwan

Configure remote scripts

1. Install RFC-enabled function modules

To run the SAPEX scripts from a remote host (where KLA is deployed), the ZKW_SAPEX_*_RPC function modules should be created using Function Builder (transaction SE37).

To create the ZKW_SAPEX_FG function group, you can use transaction SE80 as follows:
Before creating the function modules, it is recommended to create the ZKW_SAPEX_FG function group.

After creating the ZKW_SAPEX_FG function group, create a Function Module for every ZKW_SAPEX_*_RPC function modules included in $(AGENT_HOME)/resources/abap/.../ZKW_SAPEX_FG/functions

Use Function Builder (transaction SE37) as follows:

After creating it, go to the Source Code tab and paste the content of the associated file.

Make sure that all functions are terminated _RPC are marked as RFC-enabled, as they will be called remotely from the SAPEX scripts.

Click Save.

2. Install SAP JCo Connector library

Remote scripts use SAP JCo Connector to remotely connect to the SAP server.

SAP JCO Connector must be installed in the remote containing the SAPEX remote scripts that will execute the Kiuwan Local Analyzer.

Full details for installing SAP JCo library

Download SAP JCo from SAP Service Marketplace Connectors - you need service-marketplace access for it.

Once you have downloaded the corresponding package for your operating system, install it.

Windows: There are different distribution packages for various JRE versions and hardware processors available:

File	Platform
sapjco3-ntintel-3.0.8.zip	for a 32-bit JRE running on a 32- or 64-bit AMD or INTEL x86 or a 64-bit INTEL Itanium processor
sapjco3-ntia64-3.0.8.zip	for a 64-bit JRE running on a 64-bit INTEL Itanium processor
sapjco3-ntamd64-3.0.8.zip	for a 64-bit JRE running on a 64-bit AMD or INTEL x86 processor

Before installing JCo, please install the latest Microsoft Visual Studio 2005 C/C++ runtime libraries, as described in note 684106.

To install JCo for Windows, unzip the appropriate distribution package into an arbitrary directory sapjco3-install-path.

Do not copy the sapjco3.dll in the WINDIR\system32 nor into the WINDIR\SysWOW64 directory. This will break the operability of other JCo versions that are already installed on the same system. Furthermore, you would risk that the current installation also would not work anymore if the sapjco3.dll gets replaced in the respective Windows system directory in the future.

Linux: There are different distribution packages for various JRE versions and hardware processors available:

File	Platform
sapjco3-linuxintel-3.0.8.tgz	for a 32-bit JRE running on a 32- or 64-bit AMD or INTEL x86 processor
sapjco3-linuxia64-3.0.8.tgz	for a 64-bit JRE running on a 64-bit INTEL Itanium processor
sapjco3-linuxx86_64-3.0.8.tgz	for a 64-bit JRE running on a 64-bit AMD or INTEL x86 processor
sapjco3-linuxppc64-3.0.8.tgz	for a 64-bit JRE running on a 64-bit PowerPC processor
sapjco3-linuxs390x-3.0.8.tgz	for a 64-bit JRE running on a 64-bit IBM eServer zSeries processor

To install JCo for Linux, copy the appropriate distribution package into an arbitrary directory sapjco3-install-path. Next, change to the installation directory:

  cd sapjco3-install-path

and extract the archive:

  tar zxvf sapjco3-linux*3.0.8.tgz

3. Configure SAPEX scripts in Kiuwan Local Analyzer

The last step is to configure the scripts used for the scripts in KLA for remote extraction.

Note: Scripts for extracting source code (sapexCode.xml ) and metadata (sapexMetadata.xml) use following configuration files:
- sapex.properties
- sapexCode.properties
- sapexMetadata.propertiesYou can find configuration files at $(AGENT_HOME)/conf/sapex directory of your Kiuwan Local Analyzer installation directory.

As an alternative, you may use the extractor programs provided in the SAP system, and then either transfer the results to the system where the KLA is deployed, or directly run the KLA in the target SAP system (in particular, when an automated audit should be performed before releasing a transport request/task).

Please note that the extraction programs for code/metadata allow you to specify a local directory (on the user host) where exported contents will be saved.

If the extract operations will be performed manually, remote extraction scripts are not needed.

Further reading: Please visit SAP Extractor- Remote use - Appendix Configuration Files for further information.

Test SAPEX installation

Once completed, you may test the installation:

You may run the run the extraction programs in SAP to check if programs and their dependencies are active.
If the remote sapex was configured, run command line scripts to ensure that the connection properties and extraction filters work.

Related to