Skip to end of metadata
Go to start of metadata


  • Windows server 2003 or Higher version
  • Processor: 32 or 64 bit (x86) AMD
  • BOXI 3.1 System server:
    •  Central Management  Server
    • Input/ Output File Repository Server
    • Adaptive Processing Server
    • Web application Server ( Tomcat)


  • Bo client Tools
  • BO SAP integration Kit
  • JCO files Java Connectors
  • SAP BO Transports.


Step 1:

Install BO Server ( on SAP BW / SAP R/3)

Click on set up line , Select Language , Next , I Accept Agreement (select radio button) , Next ,  Give your Product key code(C801F2XXXXXXXXXX)  ,  Next ,  select the Language package (EN) ,  Next  ,  Select install MY SQL Data base or using existing database server , Next , CMS port 64XX, Admin a/c: ……….., Password: …, Confirm Password:…), Select the Configure the business,  Select Next  select radio button *SYSTEM REPOSITORY (*My SQL ROOT User …….., USER……………, Password………,) *AUDIT PURPOSE (*My SQL ROOT User …….., USER……………, Password………,), Select Apache Tomcat 5.5, Select its extra Application Java stack and Click on Next


I f Select Other Than My SQL for Repository Creation then you Want to manually create  two Database which are dedicated to System and Audit Repository.

Once Installation is done you can change the Portal.

Step 2:

Install in BO Client tools (Install with Crystal Reports):

Select your Crystal report (Cr), Click on Set Up-iri Files, Choose English, Click Ok, Select Language and Provide Key Code, select custom installation Type, Click on Next, Crystal is Successfully Installed, Finish.

Step 3:

Copy JCO Files:

JCO Files are called as Java connectors they are two java connectors which have to be configured.

a)      JCO.JAR

b)      JCO.DLL

JCO.JAR is responsible to bring securities to SAP Systems to BO systems and which as to be placed in BO application directory path as below

Copy the JAR Files,  C: Programs/BO /Tomcat 5.5/Convert /Lib/Paste

  After Pasting the JAR Files go to the Start, Programs, Tomcat, tomcat configuration, go to Java, JAVA Class Path and Paste the Jar Path, click on Apply

Go to General Tab, Click on Stop, click on Again Start.

JCO.DLL will in creating single sign on connectivity between BO and SAP environment it has to kept has Below Path.

C: folder/Windows/System 32 bi

After apache Tomcat is restarted it should also ensure the BO services are running mode to understand the BO server Behavior. Go to central Configuration Manager, go to SIA and Click on Manage Server and enable the server which are disabled.

(I.e. Programs, BO, Bo enterprise, Central configuration manager, save it, User Name, Select disable nodes and it select enable).

Step 4:

 Install SAP BO Integration Kit Configuration

a)      Host

b)      CMC

c)       Publisher ID

d)      Gate Way Host

e)      Gate Way Services

 Select your kit, set up, Select English Click on Next, Select I Agree, Next, Full name: SS…., Organization: ……., Program ID: (Copy Program ID), Next, Select English,  Select Custom, Next, Select all, Next, CMS Name Equal to CCM name , Port: 64xx.., Address: .. , Click Next.

Note: Program Id is any string less than 256 characteristics (i.e. BW Publisher).

  • Gate Way Host :  Equal to  CCM name
  • Gate Way Services: 33###

33     is the  Unique Identification for SAP Kit and ### is Sap System Number.

 Next, Select Check Box Yes Automate, Next, Kit connects SAP, JD, Oracle, Etc, Click on Finish.

After Kit is Successfully Installed then we can see that BO info view has added with SAP authentication and BO CCM is added with a new Services Called BW publisher Services.

After Kit is successfully installed go to Transports.

Step 5:


To integrated BO With Sap Integration Kit Has Provide CO- Files and Data Files ( K- Indexes’, R- Actual Data Driver).

We have to these files in to your Landscape SAP Installed Directory. Ex: In my system is installed this Directory, D: user/SAP/Trans/CO- Files,   D: user/SAP/Trans/ Data Files.

After Copying these files , Log on to the BW System--> Go to Transaction Code STMS ( Transport Management System),  Click on Import Over View, Click on Queue( Import is Empty), Go to Extra Tab, Other request,  add

After adding request and select the request, click on Import request, Target Clint is ( 800, 200,100), yes, up load them, Repeat the Steps for remaining request, Refresh. After Uploading the transport successfully Go to CMC.

Step 6:  

CMC (Central Management Console):

Go to CMC, select Authentication, SAP, Entitlement System ( Provide SAP System No, System ID, Client ID, Application Server, User Name ,Password  and Language Details), click on Up date ( then BO System is Logically attached to BW System),  Go to Options select automatic Import user, Click on Update, Select SNC Setting, Select Quality Protection As Authentication, update, Select Role Import ,Bring BW roles in to BO environment, Click on update ,SAP BO integration Bo is Successfully Completed.

Note: Now you access only SAP BEx queries I f you want to access to InfoCube and MultiProvider you want work on custom BAPI Configuration.

  • No labels