Scenario 1 - IPS(Information Platform Services) and Data Services installed on the same server.
For this example I will be using Oracle as the repository DataBases. The Application server will be the bundled tomcat that comes with IPS. The machine details for this install is
Oracle For all repositories
Application server will be the bundled tomcat that comes with IPS
Please see the Information Platform Services Install guide for detailed information on preparing the system. The Preparation section will have detailed information on
-Account Permissions for both Windows OS and Database scemas
-Choosing a Server Location
-Preparing CMS and Auditing DB scema
-Extra requirements for certain Data Bases.
For our example we have reviewed all documentation mentioned on the main wiki page. Have confirmed everything in the preparation section of the IPS install guide.
We will be Installing IPS first. Before we install IPS we want to make sure that we can access our database schemas we have already verified permissions are correct according to the Preparation section in the IPS Install guide. This step is just to confirm we can access them.
We have created two Oracle schemas one for the CMS and one for the Audit database.
CMS schema is called PRODCMS
ID is PRODCMS
password is PRODCMS
Audit Schema is call PRODAUDIT
ID is PRODAUDIT
password is PRODAUDIT
TNSname for the DB for our scemas is called EIM
to test that we can access both these scemas from the windows prompt you will do the following
launch a command prompt in windows and we will use oracles sqlplus from the command prompt to test we can access.
for our install to test the CMS schema it will be
if it connects you will see the Oracle sql prompt like this
In our example since this is a new scema we do not have any tables in this scema. You can check by doing the command
select * from cat;
as you can see there is no rows returned. During Install of IPS the tables will be created for both CMS and Audit DB.
Now we are ready to kick off the Install of IPS. We must ensure when we are launching IPS install we use the InstallIPS.exe executable not the setup.exe. IPS bundles its own keycode and unless you launch the InstallIPS.exe you will not get the bundled keycode and have to enter one.
kbase 1592136 - Error: The Product keycode is not valid. INS00140 - Information platform services 4.0 and later
To ensure no permission issues arise you will also want to right click on the InstallIPS.exe and then click run as Administrator to ensure you are running the executable as administrator.
The setup will then launch
At this point you will select the setup language for our purposes we have English.
The next screen that comes up is the Prerequisite screen. This screen will tell you if you are missing any optional or critical prerequisites. For our install we have passed all prerequisites and a little more detail on them is below.
SAP Business Objects BI Platform not installed- This is a critical prerequisite. This is just checking that the BI platform is not installed.
SAP Crystal Reports Server not installed - This is also a critical prerequisite and it is just checking to make sure Crystal Reports server is not installed on this system.
Administrative rights- This is a critical one as well and it is checking if you have Administrative rights for the install.
BI Platform server 4.x is not present - This is a critical one and it checks to make sure BI Platform server 4.x is not present.
Microsoft .NET Framework 3.5 or higher - This is an optional prerequisite and it is checking to see if you have .NET framework 3.5 or higher.
Supressed Reboot - This is a critical Prerequisite. It is checking to see if there are any file changes pending or if the system is in need of a reboot before proceeding.
Integrated database requirements - This is optional If you are not going to use your own Database IPS will install a bundled Database at the time of writing this the DB on windows is MS SQL server lite.
Windows Server version - This is a critical prerequisite. It will check if our version of Windows is a supported windows version compatible with IPS.
64 bit Operating system - This is a critical Prerequisiite. It will ensure you are installing IPS to a 64 bit operating system.
The next screen that comes up is the setupscreen. It tells you to ensure you close all other programs before running.
The next screen that comes up is the License Agreement screen
The next screen that comes up is the user information screen. You will also notice that if you have used the InstallIPS.exe as described above the bundled keycode for IPS will be already filled out.
The next screen that comes up is the Language packs screen. here is where you can choose the Language packs you want installed or if you want all of them installed you will check the box that has all languages.
The next screen that comes up is the Choose Install Type screen. This screen you will choose the type of Install you want to do
The options are
Full- This Installs a complete Information Platform Services install.
Custom/Expand - With a Custom install you can choose the components you want to install. An Expanded install is when you want to expand an already existing environment.(add another server to an existing configuration is an example)
WebTier - This is used when you only want to install a webtier.
The next screen that comes up is the Destination Folder screen. This is where you select what directory you would like to install IPS to. In our example we will leave it at the default which is C:\Program Files(X86)\SAP BusinessObjects.
The next screen that comes up is the select the database screen on this screen you will choose if you want to install and use the default bundled database that comes with IPS or use an existing database. For our example we chose use and existing Database. If you choose use an existing database you will want to ensure the database schema is setup properly as per the Supported Platforms guide and the IPS Install guide Preperation section. If the database is on a different server than the server you are installing you will also want to ensure the DB client is also setup correctly.
The next screen that comes up is the Select existing CMS database type. This screen you will select what type of Database you will use for your CMS database. For our example we are using Oracle.
The next screen that comes up is the Select Java Web Application Server screen.
There are three options to this screen
Install Tomcat Application Server and automatically deploy web applications and services- This option you would choose if you want to use the existing bundled tomcat server that IPS provides. The install will install tomcat and also automatically deploy the Web applications needed for IPS.
Manually deploy to a preinstalled web application server- You would use this if you are not going to use the bundled tomcat application server that IPS provides. With this option you will want to make sure you are using a supported application server that is compatible with IPS. After the install you will follow the instructions to manually deploy to this application server.
Install Web Application Container Server and automatically deploy web applications. You will select this option if you want to use WACS
For our example we will use the bundled tomcat that comes with IPS.
The next screen that comes up is the Select existing Auditing Database Type. This is the Database you will be using if you want to have an Auditing Database. An auditing Database is optional. For more detaild Information on Auditing you can read the BI Administration guide in a nutshell it is a database that holds system statistics that you can create reports off of (some examples include users logging in, reports being run,). If you do not want an auditing DB you will select the button that says No auditing Database.
For our example we are going to install an auditing database to a seperate oracle schema from our CMS Called PRODAUDIT.
The next screen that comes up is Configure version Management. Here you will select if you want the install to install subversion or if you want to use an already existing version control system. If you choose configure an already existing there are post install steps you must complete to intergrate your version control system.
For our example we will let the system install and configure subversion.
The files that make up SAP BusinessObjects Business Intelligence platform on a server system are now kept under version control. The installation program will install and configure the Subversion version control system, or you can enter details to use an existing Subversion or ClearCase version control system.
A version control system makes it possible to keep and restore different revisions of configuration and other files, which means it is always possible to revert the system to a known state from any time in the past. This is for IPS/BI.
The next screen that comes up is the configure Server Intelligent Agent(SIA)
This is where you configure the ServerIntelligent agent Node name and port. You will notice the Nodename is by default the servername this can be changed to whatever node name you want. And the default pport for the SIA is 6410 this can also be changed to any open available port but for our example we are going to stay with the defaults.
A node is a collection of IPS/BI platform servers running on the same host and managed by the same Server Intelligence Agent (SIA). One or more nodes can be on a single host.
The next screen that comes up is the Configure Central Management Server. This screen is asking for what port you would like your CMS running on. The default port for the CMS is 6400 although this can be changed to any open port. For our example we will be leaving it as the default port.
The next screen that comes up is the Configure CMS Account screen. This is where you will setup the Enterprise Authentication Administrator account password. This is where you will also setup the clusterkey you would like to have.
A cluster key is This key is used to encrypt all the cryptographic keys in the CMS repository. Without the correct cluster key you cannot access the CMS. You will set the clusterkey on install. Once you have the cluster key you will want to make sure you know what it is in order to add any machines to the cluster going forward you will have to provide this cluster key.
The next screen that comes up is the Configure CMS repository Screen. This screen is where we will fill out the Oracle DB information so when the CMS is installed it will be able to create the tables needed in the schema we want it to install the tables.
For our example we will provide the TNS info we discussed before
Oracle TNSname is EIM
Username is PRODCMS
Password is PRODCMS
this was the schema we created for the CMS.
We will also check the box that has reset existing CMS database because currently in our CMS scema sine it is new we do not have any current tables. This will create the tables in the schema. If our CMS already had tables in it that we did not want to recreate we would have not checked the box that said reset existing CMS database.
The next screen that comes up is the screen for Configure Auditing Database. Since we selected the option to create the Audit Database this is the screen where we will put in our Oracle TNS information so the install will be able to create the Audit tables in the Audit schema we created.
Here we will put the information for the Audit schema
Oracle TNSNAME is EIM
The next screen that comes up is the screen to Configure tomcat. this is where we will put the Port information. These ports can be any open port but we will use the defaults which are the default ports for tomcat.
Connection Port 8080
Shutdown Port 8005
Redirect Port 8443
The next screen that comes up is the Configure Subversion screen. On this screen since we opted for the install to install and configure subversion for versioning control.
You will notice on this screen the Subversion repository information
the repository information is not allowing us to fill it in or change it. This is the default repository that the install will configure
The default port for the repository will be
The port though can be changed if you want it to use a different port. For our example we will be using the default port.
The subversion Repository user information is
Repository User is also greyed out and cannot be changed the default is LCM
The repository Password we will set it here. You can make the password anything you want just make sure you remember what it is.
The next screen that comes up is the Configure Connectivity Solution Manager Diagnostic agent. Solution Manager is a tool provided for diagnostics of systems. if you already have an existing Solution Manager you can provide the details here in order to connect this installation to solution manager SMD agent. For our example we do not have a solution Maganer so we will choose do not configure connectivity to solution manager.
The next screen that comes up is the Introscope Integration screen. This is where you can integrate Wiley Introscope which is also a diagnostic tool. If you already have wiley Introscope installed you will select the option to integrate connectivity then you will provide the details. You can see more information on configuring Wiley in the Installation guide. Since we do not have Wiley Introscope installed we will select Do not integrate connectivity to Introscope Enterprise Manager.
The next screen that comes up is the start installation screen. Once you choose next on this screen the installation will begin for IPS.
Once you select next you will notice the installation starting up
The next screen is the post Installation screen here it will tell you any post install instructions.
For our postinstall instructions it tells us to log onto the Central Management console for any other configuration we need and also tells us how to access the monitoring tool from the CMS. This is standard post Install instructions.
The next screen that comes up is the screen telling us IPS has been successfully installed.
The screen after that is click finish to exit the installation. If there were not errors you can click finish at this point to exit the installation.
The next step we will be doing is installing Data Services. Before you start the Data Services installation though we will want to make sure the CMS for IPS was successfully installed and we can access it. Our Data Services install will need to access the CMS in order to install some pieces of Data Services to the CMS.
To check this there are some quick checks you can do to verify your CMS is installed and you can access as well as you can verify all your IPS services are running.
First you can bring up your CCM from IPS (Central Configuration Manager). From this you will be able to see if the bundled tomcat we installed was installed and is running. We can also see if the SIA is installed and started.
To look at this you can go to start-> and then in the list you will see Central Configuration Manager and can launch it.
Or you can go to start->all Programs-> Information Platform Services->Central Configuration manager
As you can see from the above picture you will see both the Apache Tomcat from the bundled IPS install and the SIA(Server Intelligence Agent). They both should be running.
You can also launch the windows Task manager and make sure you see a CMS.exe running. Even though the SIA is running that does not always mean the CMS is running.
If you see the CMS running then you should be able to bring up the Central Management console and log in as the Enterprise Administrator ID you set up during install. This will also be a test to make sure the CMS is running as well as we will verify the servers are all running and enabled.
To do this go to http://servername:8080/BOE/CMC or go to start->All Programs->Information Platform Services-> Information Platform Services and select Information Platform Services Central Management Console.
You should get the login screen for the Central Management Console. Once the central Management Console is up you can log into it with teh Enterprise Administrator ID and password that was creatied during install.
To login you will put the
System Name - This will be the CMS name by default its the server name but can be changed. In our example it is our server name and the default port for the CMS since we used the default port.
Our system name is ORA112:6400.
User Name - we want to use the Administrator account that was created on install.
In our example it is
Authentication- Authentication is how the CMS is going to authenticate the userID. In our example we want to use Enterprise Authentication becasue we are going to use the Administrator ID.
Once we are logged in we go to the main page of the CMC.
This shows us that our CMS is indeed up and running and we were able to connect to it to log on to the CMC.
One other thing you can do is check if all the servers are running and enabled.
To do this you will go to the dropdown and select servers tab or you can just click on the servers icon on the organize section of the CMC.
Once you go to the servers tab you can then click on the servers list icon on the left hand side. This will show a list of all the servers.
You can see from our IPS installation we have the following servers and they are all running and enabled
Adaptive Job server (AJS)
Adaptive Processing server (APS)
Central Management Server (CMS)
Input File Repository Server (IPS)
Output file repository
At this point we will now be able to install Data Services since our IPS installation appeared to be installed sucessfully.
Installing Data Services
For our example we will be installing Data Services 4.1 SP1 patch 4. You will want to ensure you have already read all the Data Services Documentation and Supported platforms guides mentioned in the main section of the wiki.
You will also want to make sure you read the Data Services Installation guide it has specific information on
-Port assignments and Requirements
-It also discusses what to do to install the cleansing package
For this example we will not be installing the cleansing package.
We have created a Local repository in our Oracle Database called DSPRODLOCAL this will house our Data Services Local repository.
TNSNAME is EIM
Since we are going to use Oracle as our local repository we also want to make sure we know where and have the location of the Oracle JDBC driver handy this typically comes with the oracle client/server install. In our example since we installed the Oracle client the jdbc driver is located in our $ORACLE_HOME/jdbc/lib.
You will want to ensure the version of the JDBC driver is a supported version. You can see this in the DS PAM(Supported Platforms guide)
Data Services now uses JDBC driver to connect to the repositories. You want to ensure though that you have created a DB scema per the Preparation section in the install guide to ensure the proper permissions and setup is done for that schema.
For our example we have verified the schema was setup correctly. As you can see we can access the schema and currently there are no tables created.
As you can see from the above we have connected to the schema we created for the DS Local repository. via sqlplus
Here we will query the tables for this schema and as you can see there is no tables created yet. The DS install will create those tables.
Now that we have verified the schema is created and all the other preparations have been followed from the DS install guide we can begin the DS install.
In the Install Media we will now ensure we kick off the setup as run as Administrator.
The next screen that comes up is the Prerequisite check screen this will show you any optional or Critical Prerequisites that have failed.
As you can see we have passed all Prerequisites with exception of the optional SAP HOST Agent. Since we do not have a SAP HOST Agent that is fine.
Some of the prerequisites it checked for
Optional - Microsoft.NET framework 3.5 or Higher
Critical - Detected Active processes (just checks to make sure there are no active processes)
Optional- SAP HOST Agent
Critical - Detect existing Data Services version
Critical- Platform Memory architecture
Critical- Microsoft Windows version
Optional- SAP Business Objects Enterprise
Critical - SAP Business Objects Version
Critical- Cannot Coexist with 32 bit Installation
The next screen comes up with some preinstallation instructions just telling you to close any running programs and some copyright information.
The next screen that comes up is the License agreement screen. You must read and accept the license agreement to proceed.
The next screen that comes up is the user information screen Here you will put your User information and your Data Services keycode that has been provided to you.
In our example I am using the following
Full Name SAP
For the keycode I have put X's in the screenshot but you will want to ensure you use the Data Services keycode you were provided.
The next screen that comes up is the Specify Destination Folder screen. As you can see it is already pointing to the location we installed IPS.
The next screen that comes up is the choose Language packs screen. Here is where you will choose the language packs you want. Or if you want all languagep Packs You would put a check mark in the All Languages box.
The next screen that comes up is the specify CMS connection Information. Data Services now is integrated with IPS/BI with that there are Data Services InfoObjects that need to be added to the CMS Data Base.
This screen we will add the CMS information from the IPS install we did earlier.
For our example we have added
System - ORA112 (This is the CMS name since we are using the default CMS port we do not have to add the port number. If you are not using the default CMS port you would use the CMSname:port)
Username - Administrator ( This is the userid that was created on Install)
Password - xxxxxxx (This is the password that we set for the Administrator ID on Install)
Authentication Mode- Enterprise
There is also an option to Skip configuration. If you skip configuration it will not install the Data Services components to the CMS.
The next screen That comes up is the warning that it will need to stop the SIA then restart the SIA. It also tells you to ensure the FRS(File Repository Servers) are enabled.
The next screen that comes up is the Select Features screen. For our example we are just going to accept the defaults. We are also not installing the cleansing package in this example.
The next screen that comes up is the Configure APS services screen. This screen you will put the Ports for the APS services.
For our example we will keep the default ports but you can change the ports to any open and available ports.
The defaults that we will keep are
Metadata Service 4010
Metadata JMX Connector 4011
ViewData JMX connector 4013
The next screen that comes up is the Merge Existing Configuration screen. This is where if you have an existing Data Services Configuration you can point to the DSconfig.txt and it will ensure your existing configuration is merged Rather than creating a new configuation. For our example since it is a fresh Install and we do not have any existing Configuarations(Repos, Jobservers, etc) We will choose skip configuration. This will cause the install to create a new configuration file.
The next screen that comes up is the Repository Configuration screen. This screen you have the option to have the install create a repository or you can skip the configuation and create a Repository manually after the install. For our example we will have the Data Services instalation create the local Repository in the schema we created for it in our Oracle Database.
For our example we selected to use existing Database server.
The next screen that comes up is the Specify Local Repository Database type.
For our example we selected Oracle
The next screen that comes up is the select JDBC driver screen. Since we are using Oracle the JDBC driver can be located in the Oracle client/server or can be downloaded from Oracle.
Our location is in $ORACLE_HOME\jdbc\lib
You must ensure you check the Data Services PAM to ensure you have the correct version of the JDBC driver.
Then once you locate your JDBC driver you will get the next screen that lists the driver and you can select next.
The next screen is the Repository Connection screen here you will specify the connection details of your Data Base.
For our example we provide the following
Registration Name for the CMS - DSPRODLOCAL (You can name this anything. It is what your repository will be identified as to the CMS you will see this entry when you go into the Central Management Console under the Data Services tab. I chose to name it the same as the repository name to make it easier for me to identify which repo.)
Database Type - Oracle (Since we selected Oracle for our repodb this is put in for us and is greyed out.)
Database connection name - EIM ( here we enter our TNSName)
Database Server name - ORA112 (here we enter the DB servername)
DataBase Port - 1521 (This is the db port for our example)
SID - EIM (here we put the TNSname)
Use connection String Oracle RAC - no (Since we are not using an Oracle RAC we select no)
UserName - DSPRODLOCAL (we entered our Oracle User name here)
Password - DSPRODLOCAL ( we enter our Oracle Password here)
After you enter the options it will confirm if those options are valid and if not will come back with an error message.
The next screen that comes up is the Specify Job server configuration screen.
Here you have two options to configure the job server or to skip this configuration and configure the job server manually after the install.
For our example we chose to configure the job server and will leave the default Job server name and job server port.
Jobservername - JobServer_1
Jobserverport - 3500
The next screen that comes up if you chose to configure the job server is the Specify Job server defaults screen. Here you will choose to specify the job server defaults.
For our example we left it as is and did not change anything.
The next screen that comes up is the configure access server screen. You can either select to configure the access server or skip configuration and configure an access server manually after the install.
For our example we chose to configure the access server and left the defaults.
The next screen that comes up is the Login information. This is the login account that will be used to run the Data Services service.
There are two options use system account or use this account. The use This account is the recommended. As you can see in our example the Use system account has our local Administrator account we just need to type in the Administrator accounts password.
The next screen is the start installation screen. This screen allow you if you want to go back and change any information you can go back.
Once you select next the install begins
Once the installation is finished if the install went successfully you will receive the screen that says the install was successful.
The next screen you will get will be the Reboot required screen. Once you say yes on the screen the reboot will take place.
When the reboot is finished you can log back in. There are also some manual checks after the reboot you can do to ensure the install went well.
You can pull up your services and verify that the Business Objects Data Services server was installed and is running.
To pull up the windows services you can pull up a cmd prompt and type services.msc.
This will launch the services window.
In the services window you can verify the service Business Objects Data Services was installed and it is running.
Another check you can do is to log into your CMC(Central Management Console)
Once logged in you will see in the main CMC page the Data Services link.
You will notice after the Data Services install there is now an icon in the CMC for Data Services.
If you click on that icon because we chose to install our Local repository during install you should now see our local Repo and you want to verify it is active.
Another check you can do is to verify the EIMAPS service was added and is active. To do this in the CMC in the dropdown you can go to the servers tab.
Once you go to the servers tab and select Enterprise Information Management tab you will see a EIMADAPTIVE Processing server has been added. You will want to make sure it is running and enabled.
You can also go to the serverlist icon on the left and it will show you all the current servers you have. You will notice our Data Services install just added the one EIMADAPTVIE Processing server.
The next thing you can check is to make sure the Data Services Management console can be accessed.
To do this you can get to it by two ways
Go to Start->All programs->SAP Business Objects Data Services 4.1 ->DataServices Management Console
or you can just in a browser go to http://server:port/DataServices (server would be your App server and port would be the application server port)
In our example would be
You will get the login screen for the Data Services Management console.
And you can login with the Enterprise Administrator account as we did for the CMC.
At this point you can move on to all the post install steps creating your users adding access to those users to repositories. All that information is in the Data Services Install guide and Data Services Admin guide. That is out of scope for this wiki.
We will not discuss in detail reading the log files for the install on this scenario. It will be a seperate section of this wiki. The location of the log files for all products being installed is located in the following location.
<InstallLocation>\SAP Businessobjects\InstallData\logs\<Install Date>
in our example it is
C:\Program Files (x86)\SAP BusinessObjects\InstallData\logs
and under that directory there are two directories because on this box we did the IPS install and then the Data Services install.
If you go inside the directory in our example we will go into the last one which was the Data Services install. The install log is the setupengine.log.
We will not go into detail on how to read the logs in this scenario but it will be a seperate child page off this wiki.
Related SAP Notes/KBAs
Error Product keycode is not valid: 1592136
How to access online documentation for SAP BusinessObjects products - Data Services / Data Integrator
Supported platforms guide(PAM)