Building a SAP BI 4 Demo System

This article provides a summary of the high level steps involved with building a SAP BI 4 Demo System and provides guidance on hardware and software requirements and links to where software can be downloaded from. The Demo System will host SAP Business Objects 4.0 and SAP Data Services 4.0

Overview

The demo server consists of virtual machine running a Linux operating system on which is installed SAP Business Objects 4.0, SAP Data Services 4.0, Apache Tomcat web application server and Oracle database server. The desktop tools for SAP Business Objects and SAP Data Services are deployed directly to the desktop of the host system which is running Windows 7.

Requirements

Hardware

The host operating system which will be running the virtual machine (VM) needs to have enough system resources to run the virtual machine, the host operating system and any other applications running on the host system. The table below summarises the hardware requirements of the host desktop.

Software

The table below lists the required software and provides links to download web sites. Note, for most of these you will need to sign up to the web site and for the SAP products you need to be either a customer of SAP or a partner with rights to download the software and be able to download trial license keys. Right click to open the download sites in a new page or window.

Building the SAP BI 4 Demo System

The following are the high level steps required to build the demo system. It is recommended that you make a note of the detailed steps as you go through the deployment and it is highly recommended that you write down all the user accounts and passwords that you create.

Once the required software above has been downloaded, build a demo system,

1. Install VM Player.
2. Create a new virtual machine using the iso files that were downloaded.
   1. Creating the VM with 6GB of RAM (or higher) and 60GB disk
   2. Make a note of the root password you define
3. Configure the Linux operating system. Refer to the SUSE Online Documentation for further assistance
   1. Oracle Express requires that you have a swap partition of 2GB in size. This can be done using the YaST application and select Partitioner.
   2. Also using YaST create a new user account “boeadm” that BusinessObjects and Data Services will be installed with and run under
   3. And again using YaST enable the FTP server on the system
   4. Create a folder /opt/sapboe where BOE and SDS will be installed – make sure boeadm is owner and has full permission to this folder.
4. Install and configure Oracle Express
   1. Follow the Oracle Express installation guide. Note use a different port for Oracle Application Express e.g. 9090 so that it won’t conflict with 8080 for Tomcat. Make note of the admin password you define.
   2. Create schemas required by SAP products as listed in the table below

   User	Purpose	Notes
   BOE_CMS	User for the Business Objects CMS Repository	This database holds the Business Objects security model and pointers to all the objects in the FRS. The size of this schema will initially be approximately 24MB
   BOE_AUDIT	User for the Business Objects Audit database	If enabled the audit database logs all events and activity on the Business Objects system as such it can grow large – about a million new audit events per month in a production system. The size of this schema will initially be approximately 11MB
   SDS_LOCAL	User for the Data Services local repository.	A local repository is created for each developer and holds all the ETL code written by the developer. Its size depends on how much code is written but this is typically small. The size of this schema will initially be approximately 40MB
   SDS_CENTRAL	User for the Data Services central repository.	The central repository is shared by all developers as version control for Data Services code. The size of this schema will initially be approximately 36MB

   3. Configure the Linux boeadm account to use Oracle by setting the oracle environment variables in boeadm’s profile.
5. Install SAP Business Objects
   1. Use the boeadm account create above to do the installation – do not use root.
   2. When installing select to install the Web Tier components so that Apache Tomcat will be installed and configured for you.
   3. Do not install the Integrated Database as we’re using Oracle.
   4. The SMD Agent and Introscope Enterprise Manage are not required and can be skipped
   5. After installation, test that you can logon to the Central Management Console
6. Configure Business Objects
   1. Create additional administrator accounts
   2. Optional: move File Repository Server (FRS) to a separate partition. This is recommended on production systems so that the FRS can be backed up and restored separately to the operating system and BusinessObjects deployment.
   3. Optional: move log folder. SAP BusinessObjects can produce a large amount of log data and it is recommended that this is also held on a separate partition.
   4. Split Adaptive Processing Server and Adaptive Job Server
   5. Install Desktop applications
7. Install and configure SAP Data Services
   1. Install the desktop applications first and create required local and central repositories
   2. Install SAP Data Services on the Linux server
   3. Using SAP Business Objects CMC create one or more developer accounts and grant each account access to their local repository and to the central repository

Creating demo servers is a great way to learn how to deploy SAP Business Objects and SAP Data Services and I hope you find the above informative.

If you are new to Linux then I recommend obtaining a good Linux reference manual such as Linux Pocket Guide by Daniel J. Barrett.

http://rcm-uk.amazon.co.uk/e/cm?lt1=_blank&bc1=000000&IS2=1&nou=1&bg1=FFFFFF&fc1=000000&lc1=0000FF&t=gullandcom-21&o=2&p=8&l=as1&m=amazon&f=ifr&ref=qf_sp_asin_til&asins=1449316697

Share this:

• Click to share on Twitter (Opens in new window)
• Click to share on Facebook (Opens in new window)

Like this:

Like Loading...