Thursday, January 19, 2012

Install sapjco-ntintel-2.1.9

Install sapjco-ntintel-2.1.9 (install 32bit version even if u have 64bit OS)

SAP Java Connector

The SAP Java Connector is being leveraged from BusinessObjects Edge and the SAP Integration Kit as part of the SAP Authentication plug-in in the Central Management Console.

You can download the SAP Java Connector from the service marketplace (http://service.sap.com/connectors).

I am downloading the version 2.1.9

After unzipping the Java Connector download, I and the file sapjcorfc.dll to %windir%\system32.

(see page 51 in the installation guide for the Integration Kit for SAP Solutions for details)

Unzip sapjco on C:



copy the file sapjco.jar to the shared library folder of the application server (in my example : \Program Files (x86)\Business Objects\Tomcat55\common\lib)





Copy the file sapjcorfc.dll to %windir%\system32.














Copy Unicode or ANSI files to sap system:

There are two different sets of the transports: Unicode compatible transports

and ANSI transports. If you are running a BASIS system of 6.20 or later, use

the Unicode compatible transports. If you are running a BASIS system earlier

than 6.20, use the ANSI transports. The transports_EN.txt file located in

the transports directory on the installation cd lists the Unicode compatible

and ANSI transport files.

Read the transports_EN.txt file located in the transports directory on

the installation CD. This text file lists the exact names of the files that make

up each transport. (The cofiles and data directories below the transports

directory correspond to the .../trans/cofiles and .../trans/data directories

on your SAP server.)

You must import the Open SQL Connectivity transport before importing the

Row-level Security Definition or the Cluster Definition transports. You may

import the other transports in any order.

Note:

After copying files from CD to server, ensure that all files are writable

before you import the transports. Imports fail if the import files are

read-only.

Because the transports are binary files, on UNIX installations you must

add the files by FTP in Binary mode (to avoid file corruption). In addition,

you must have write permissions for the UNIX server.



Previous Page First Page Next Page



0 comments:

Post a Comment