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
- Install BODS
- Upgrade/configure all the repositories after taking sufficient backups.
- Modify the datastore connections (applicable only if new database server has been installed).
- Add job servers.
- Add repositories to the Management Console.
- Add Users
- Create ODBC connections (applicable only if new OS has been installed).
- Create folder structure (applicable only if new OS has been installed).
- Sybase Client installation and configuration (applicable only if new OS has been installed).
- 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
- Go to Start–> All Programs — >SAP BusinessObjects XI 3.2–>SAP BusinessObjects Data Services–> Data Services Server Management
- Specify Cache as existing path i.e. D:\Log\Cache
- Select “Edit Job server config -> Add”. Check default repository option for all.
- 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
- Go to Start–> All Programs — >SAP BusinessObjects XI 3.2–>SAP BusinessObjects Data Services–> Data Services Management Console
- Use default login credentials.
User Id – admin
Password – admin
- Go to Management-> Repositories -> Add.
(Note: Keep a screen shot of existing repositories from console.)
Step 6: Add Users
- Go to Start–> All Programs — >SAP BusinessObjects XI 3.2–>SAP BusinessObjects Data Services–> Data Services Management Console
- 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.
- Go to Start-> All Programs -> Sybase ->Connectivity->Open Client Directory Service Editor.
- 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.
It is very helpful for this topic.
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.
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
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..
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.
PLease use try-catch logic. Inside the catch, write a script to insert the error_message() to the oracle target table .
Can you let me know steps if it is a migration?Lets say from DS XI 3 to DS 4.