Skip to Content

First step is to check if installed OS and your DB  are compatible with BODS.

(Refer to BODS 3.2 Supported Platforms. PDF)

If using old OS, then uninstall BODI and install BODS.

If new OS has been installed, then directly install BODS.

Steps to setup BODS on existing server

  1. Install BODS
  2. Upgrade/configure all the repositories after taking sufficient backups.
  3. Modify  the datastore connections (applicable only if new database server has been installed).
  4. Add job servers.
  5. Add repositories to the Management Console.
  6. Add Users
  7. Create ODBC connections (applicable only if new OS has been installed).
  8. Create folder structure (applicable only if new OS has been installed).
  9. Sybase Client installation and configuration (applicable only if new OS has been installed).
  10. Oracle Client installation and configuration (applicable only if new OS has been installed).

     

Step 1: Installation of BODS

Refer to Installation Guide Data Services 3.2.pdf

Use Skip Configuration setting for following options:

Directory Selection

Local Repository Selection

Configure Job Server

Configure Access Sever

Configure Metadata Integrator

Use Tomcat server with default settings as Web Application Server.

Step 2: Upgrade/configure Repository

Go to Start–> All Programs — >SAP BusinessObjects XI 3.2–>SAP BusinessObjects Data Services–>Data Services Repository Manager

Follow below steps:

i)                    Select Local Repository.

ii)                  Database server name

iii)                Give Repository name.

iv)                Give credentials

v)                  Get Version

vi)                Upgrade Repository.

NOTE:  Take repository DB backup first and for worst case take backup of JOBs also in atl file.

Step 3: Modify the Datastores settings.

Step 4: Add Job servers

  1. Go to Start–> All Programs — >SAP BusinessObjects XI 3.2–>SAP BusinessObjects Data Services–> Data Services Server Management
  2. Specify Cache as existing path i.e. D:\Log\Cache
  3. Select “Edit Job server config -> Add”. Check default repository option for all.
  4. Restart after adding all the job servers.

     

(Note: Keep the screen shot of details of existing job servers)

Step 5: Add Repositories to Management Console

  1. Go to Start–> All Programs — >SAP BusinessObjects XI 3.2–>SAP BusinessObjects Data Services–> Data Services Management Console

   

  1. Use default login credentials.

User Id – admin

Password – admin

  1. Go to Management-> Repositories -> Add.

(Note: Keep a screen shot of existing repositories from console.)

Step 6: Add Users

  1. Go to Start–> All Programs — >SAP BusinessObjects XI 3.2–>SAP BusinessObjects Data Services–> Data Services Management Console
  1. Go to Management-> Users-> Add.

(Note: Keep the screen shot of details of existing users)

Step 7: Create ODBC connections

This step is applicable only if new OS has been installed.

Go to C:\Windows\SysWOW64\odbcad32.exe.

(Note: Keep the screen shot of details of existing ODBC connections)

Step 8: Create folder structure for input files

This step is applicable only if new OS has been installed.

Step 9: Sybase Client installation and configuration

This step is applicable only if new OS has been installed.

Install Sybase Client. After installation check if it configured. If not, then follow below steps.

  1. Go to Start-> All Programs -> Sybase ->Connectivity->Open Client Directory Service Editor.
  2. Server Objects -> Add.

Step 10: Oracle Client installation and configuration

This step is applicable only if new OS has been installed.

Install Oracle Client.

And configure it.

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. sapkrisboedge mac

    It is good. can you please tell me the how to call oracle stored procedure in SAP BODS. please let me know the steps are using oracle stored procedure. please help me suraj.

    (0) 
    1. Suraj Garg Post author

      Hi

      there are two ways

      1. import your stored procedure from the datastore and you will see it in function wizard. you can call this function like any other BODS function

      2. you can use it it script also

      Datastorename.ownername.procedurename(parameters);

      Its good to use print command before and after executing procedure to keep track

      (0) 
  2. sapkrisboedge mac

    Hi Suraj,

    Thanks for help..I need one help Suraj.

    The oracle exception Errors Automatically loaded to the Oracle Target table?

    My Source is Oracle  and My target is Oracle. Please let me know the Answer..

    It is Very Urgent Suraj..

    (0) 
  3. sapkrisboedge mac

    Hi,

    Our DI job is throwing some oracle exceptions like unique integrity contraint error & not null constraints error.  We would like to log those errors into an another Oracle Target table with the oracle error details and the source record details.

    Can anyone please help in this.

    (0) 

Leave a Reply