Professional Documents
Culture Documents
SAP Business Objects Data Services Setup Guide
SAP Business Objects Data Services Setup Guide
Follow the instructions below on how to setup SAP Business Objects Data Services
After having the licensed version of SAP BODS XI, Click the installation icon "setup.exe" to
launch installer.
Click Next
Check the option "I accept the License Agreement" and Click the Next button.
Click on the Next button and provide the license information as provided by SAP.
Services\ You can install in any local directory of your choice and also on SAN drive.
By default the server, client and web components are selected. Real time services i.e. Message
Provide the pre configured database connection information. (MSSQL Server in this case)
Password:
Click on the button Get Version to check whether the service can connect to database.
Next check the Create option and click the Next button to continue.
Next click on the Advanced button, to change Cache Directory for this job server.
Click the Next button to continue with the Service Login Information.
Check the option Use system account and click the Next button to continue.
Three BODS services namely BOE120Tomcat, Business Objects Address Server and
DI_JOBSERVICE will be created under this system account. Click Next to Continue.
Next check the option Skip Access Server Configuration and click the Next button to continue.
Since we are not using Real Time Data Services we skip this configuration step.
Click Next to install the web application server.
Check the option Install Tomcat application server and click the Next button to continue.
Leave the ports as default and click the Next button to continue installation.
This tomcat web application server will host the Data Services web based management console.
Click Next to finalize the installation. The list of programs and services to be installed are
displayed.
After successful installation of SAP Business Objects Data Services reboot to reflect
configuration changes.
Click Yes.
After machine restart do the initial validation to check the SAP BODS Services and Programs
installed. Click Start then All Programs, next check the SAP BODS Installed programs.
In this part of the article, we will see how to change the default Log file directory of SAP BODS,
Create Local, Central (Secured version control for multi-user environment) and Profiler (Data
license information and Configuring SAP BODS Metadata Integrator with SAP BOXI.
BODS automatically creates an environment variable, called LINK_DIR which points to the root folder
For the sake of future conveniences and logical grouping, we may also create the following directory
Separating the directories in the above fashion, makes it easy for us to quickly access them later.
We need to create the folders in windows and use them for the purpose defined above. For example to
point the source or target file to proper directory either enter the directory path in the Root directory
option of the File Format or you can also use Substitution Parameters for each environment.
But you may change the default log directory location to some other folder, eg. the below folder for
quicker access:
D:\Business Objects\LogDir
AL_JobServerLogDirectory1=
As below
AL_JobServerLogDirectory1=log
AL_JobServerLogReDir1=D:\Business Objects\LogDir
Next Restart the BODS Job Server or BODS Services and you are done.
Businessobjects Data Services(SAP BODS) solutions are built over 2 different types of meta-data
repositories called central and local repository. While the local repositories can be used by the individual
ETL developers to store the metadata pertaining to their ETL codes, the central repository is used to
"check in" the individual work and maintain a single version of truth for the configuration items (e.g.
ETL code). Without the necessity of installation of the additional modules, it supports the team work in
the ETL projects. The central repository allows adding tested scripts and then import them to local
repositories or check them out and open them in exclusion mode. Versioning is also fully supported.
In the next section we will see how can we create and configure a local repository. Go to SAP BODS
Repository Manager and enter the following information to configure the Local Repository:
Click on Get Version button, first to check it is able to connect to database. Next Click on Create button
Next we will see how to create SAP BODS SECURED CENTRAL REPOSITORY.
Page 4 of 9
As discussed in the previous page, Businessobjects Data Services (SAP BODS) solutions are built based
on a central repository which is independent from the local repositories of the ETL developers. The
central repository, among other things, supports the team work in the ETL projects. Versioning is also
Go to SAP BODS Repository Manager and enter the following information to configure the metadata of
Click on Get Version button, first to check it is able to connect to database. Next Click on Create button
The above message shows that the Central Repository is successfully created.
Central repository is used for the sole purpose of version control check-in and check-out functionality
ideal for multi-user development environment. You cannot run the jobs or you cannot configure a job
A profiler repository is a special repository that contains the profiling information for the objects. Among
other things, this repository stores the column level details including cardinality/ max, min and Null
values etc. A job server needs to be associated with the profiler repository. Next we will see how to
configure a profiler repository. Go to SAP BODS Repository Manager and enter the following information
Click on Get Version button, first to check it is able to connect to database. Next Click on Create button
Note:- Profile repository is used for the sole purpose of performing column level profiling of the DW
tables. You must configure or associate a Job Server with the Profiler Repository.
Next we will learn how to CONFIGURE JOB SERVER USING DS SERVER MANAGER for the Profiler
repository.
You need to configure a Job server before you are able to execute data services ETL jobs. Job server
needs to be configured on some local repository that you have already created. Here we will see how
Click Add and enter the Name of the Job Server and associate it with the local repository.
Next click the Add button to associate the repository to the Job Server.
Click Apply.
You will be greeted with the below screen once you login.
Next Click on Administrator to Register the Repositories. Following screen will appear. You may click on
On the left hand pane Click on Management list item and then Click on Repositories.
Next Click the Add button to register a repository in management console. Enter the repository
credentials.
Click Test.
Click Apply.
Next we will learn how to ADD CENTRAL REPOSITORY USERS AND GROUP in BODS
<< Prev
Next >>
< Prev
Next >
Click Add.
Click Apply.
Now you will be able to connect to the Profiler Repository using this User.
BODS DESIGNER
Look at the bottom right hand corner for job server symbol. On pointing the mouse it will show Job
Look at the bottom right hand corner for Profiler Server symbol. On pointing the mouse it will show
Profiler Server is not running. Double click the Profiler server, or go to Tools and click Profiler Server
Host: localhost
Port: 28080
User name: DEVETLREPO_PROFILER
Password:
Click on Test button.
Now On pointing the mouse to the Profiler Server will show the server running and the user connected.
Select the default key in the location, which was generated during Central
Repository Creation.
User name: DEVETLREPO_CENTRAL
Password:
Note: You can create separate Logins to central repository for individual developers from Management
Console and provide the same to the developers who will connect to Check-In and Check-Out Objects.
Click the Activate button and enter the password again to activate central repository with this current
local repository.
Pointing the mouse over the secure central repository will show the details.
Click on the Data Services Management Console icon shown above to connect from the designer GUI.
Next use SAP BODS LICENSE MANAGER to Add new license information using the Add button or to
Regarding installation and configuration of SAP BODS METADATA INTEGRATOR we will discuss in
another topic as this particular component need to be installed in BOXI server machine. So both BOXI
and BODS can reside in the same machine or in different machine. But the metadata integrator
component should be installed and configured at the BOXI server or precisely where the BOXI CMS
resides so that we can take the full advantage of lineage and impact analysis of the target report fields