Tuesday, January 29, 2013

SAP BO and DS with Oracle Database Part 6 Installing DS Client

SAP BO and DS with Oracle Database Part 6 Installing DS Client

I downloaded the "SBOP DATA SERVICES DESIGNER 4.0 WITH SP03 WINDOWS (64B)" and used the generic trial licenses for the installation.


 
























Using the installed tool access the designer and it would prompt to enter the administrator password.




now we have the console ready for deploying jobs. Wait the jobserver is still not connected to the repository and it had a red cross over the icon which is at the lower right corner. 

The fix took may be a week for me to figure out in the SAP world. It is unlike Oracle world where most of the bug fixes are open and available on the internet. SAP world is still not open based on my 10 years of experience but this is only my view. But still I solved it and I will blog about it later.

SAP BO and DS with Oracle Database Part 5 Verifying CMC and DS

SAP BO and DS with Oracle Database Part 5 Verifying CMC and DS

Now that we are done with the installation , we have to verify CMC and DS information.

Access CMC and make sure you are able to login via the administrative user

URL : http://bodsserver001:8080/BOE/CMC


Access Data Services option to see if the repository is active


Edit the repository and confirm if you can connect using the Test Connection button.


Access the Data Services console to see if you can see the repository and the rest of the components.

URL : http://bodsserver001:8080/DataServices


SAP BO and DS with Oracle Database Part 4 Installing DS on SUSE Linux

SAP BO and DS with Oracle Database Part 4 Installing DS on SUSE Linux

Now that we are doing with installing BO , I wanted to create the DS environment so that we have a complete setup before we go into the rest of the experiments.

I downloaded "SBOP DATA SERVICES 4.0 WITH SP03 LINUX (64B)" and used the generic trial licenses for implementation.

After downloading unzip the files in Windows and then ftp into the linux server.

Set environment variables relevant for the installation
$ export LANG=en_US.utf8
$ export LC_ALL=en_US.utf8
$ export ORACLE_HOME=..../client/
$ PATH=$PATH:$ORACLE_HOME/bin

Now create a directory to store the installation files.

$ mkdir -p /oraapp/bo/bo4
$ sh setup.sh InstallDir=/oraapp/bo/bo4

Now Choose the Installation language


Make sure that you select the BO installation folder. Initially I created another directory /bo/ds4 and installed  the complete package and nothing happened. So the recommendation is to install DS into BO folder.


 Check the prerequisite , which is fine


accept the trial license





input the trial license key , this will expire in 30 days


Choose option to install data services with cms server , so that it can be controlled via the cms console.


Update the administrative password


select the product which has to be installed , you can custom install after expanding and selecting components which is required.


if there is already running data services configuration than that can be reused here but I have skipped it because of the new install


I am selecting the option to use the existing installed database. remember I created the user in the BO installation procedure.


select Oracle , pay attention if you have Oracle RAC (soon we will see HANA here )


give the details of the oracle environment


create the repository


now configure a new job server to process your jobs , this can be done later with the client tool.


I choose to configure the job server and now I gave new name and a port for the job server to listen


Configure access server here


ports and other inputs has to mentioned


start the installation


it starts


it started


it runs


it finished soon ( no i did not know how long it took , I started the installation in the evening and the next day I saw it got finished )


Now we have BO and DS running. Lets play a bit more with the other options.


SAP BO and DS with Oracle Database Part 3 Installing BO on SUSE Linux

SAP BO and DS with Oracle Database Part 3 Installing BO on SUSE Linux

I downloaded "SBOP BI PLATFORM 4.0 SP04 (incl. FP03) SERVER LNX" and used the generic trial licenses for the implementation.

After downloading unzip the files in Windows and then ftp into the linux server.

Set environment variables relevant for the installation
$ export LANG=en_US.utf8
$ export LC_ALL=en_US.utf8
$ export ORACLE_HOME=..../client/
$ PATH=$PATH:$ORACLE_HOME/bin

Now create a directory to store the installation files.

$ mkdir -p /oraapp/bo/bo4
$ sh setup.sh InstallDir=/oraapp/bo/bo4

Now Choose the Installation language


Select the destination folder


Now the prerequisite check  will be done , seems all is fine.


Accept the license agreement


Input the trial key (in my case)


Choose the application language , pay attention if you are deploying BO in the European world as you may have to select mostly all the languages.


Choose the install option


then the install type (here custom installation can be done with option 2) , I choose Full (:-


Choosing the database , here we already have running Oracle Database so option 2


Select Oracle for the CMS repository


Select Oracle for the Audit repository


I used Tomcat application server and there is a possibility to use a wide range of application server. One such is Weblogic which I will try out in a separate installation.


I opt to use the default version management system.


Configure the Server Intelligence Agent which is very helpful when it comes to managing BO components.


Configure the CMS port for the administrative console


Supply the password for the administrator accounts.


Here we have to give the Oracle TNS Name (this should be the name service name that we have mentioned in the tnsnames.ora of the Oracle Client Installation , to create the file source Oracle Home and run netca )

Login into the repository Oracle database and create the below two users.

SQL > grant connect,resource to boecms identified by boecms; (CMS Database User Name)
SQL > grant connect,resource to boeaud identified by boeaud; (Audit Database User Name)




Supply the port number for Tomcat application server


Configure the HTTP listening port


Configure the version management port and administrative password


I do not want to configure SDM agent at this moment so I skip it


I do not want to configure IEM at this moment so I skip it.


Give the confirmation for the installation to start


here we go


go it went to 8% and I can have coffee


now I am going to have lunch will be back and check the status


lunch break is over but still ??? my server is less powerful *may be*


common ....


tea break


good


very good


 Now SAP BO 4.0 SP4 is installed and there is something for me to play this evening.

Next

SAP BO and DS with Oracle Database Part 4 Installing DS on SUSE Linux

Popular Posts