SAP BO - Servers Management (Services)

1 - About

This article talk about general information about the several servers that contain BO XI.

On Windows, only two services are installed in the default installation :

• The Tomcat service : BOBJ - Web application servers
• The server intelligent agent which manage all servers installed on the machine

You can manage the various servers that comprise a BO XI installation by :

• selecting the Servers option from the main menu of the SAP BOBJ - Central Management Console (CMC).
• with the SAP BO - Central Configuration Manager (CCM)

3 - Stopping and disabling a server

3.1 - with CMC

Selecting the Servers option from the main menu of the SAP BOBJ - Central Management Console (CMC), you can control the servers and manage their individual settings. You can also start and stop as well as enable and disable servers. There is a difference between :

• stopping
• and disabling a server.

Stopping a server terminates the server’s process completely and results in a complete shutdown. Disabling a server prevents it from receiving any further requests but doesn’t actually shut down the process. In production environments, it’s a good practice to disable certain servers like the Job Server and Program Job Server prior to stopping them so that they can complete the processing of any pending jobs.

If you have memory problem, you can also disable the server to start automatically in its property :

You can not seen all servers in the server list node. For instance, the PMServers that are present in the performance management are not listed in the server list node. Use SAP BO - Central Configuration Manager (CCM) to have a global view of all server instead.

3.2 - with CMM

see SAP BO - Central Configuration Manager (CCM)

4 - SERVER COMMAND-LINE PARAMETERS

If you open the SAP BO - Central Configuration Manager (CCM), right-click a server, and select the Properties option from the pop-up menu, you’ll see a dialog that looks like the figure below

The text boxes are all disabled because the server is running. You need to stop the server to make any edits. All servers are Windows Services, and the Command setting is the path and EXE name of that service. The command property of the Program Server, for example, looks like this:

-boot "C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\_boe_NGERARD.bootstrap"
 -cmspath "C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\cms.exe" -cmsdir 
"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86" -port "6410" -dbinfo 
"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\_boe_NGERARD.dbinfo" -loggingPath
"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\Logging" -name "NGERARD" -piddir 
"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\serverpids"

The switches that appear after the EXE reference are placed there by default when BO XI is installed and should not be modified except on the instructions of technical support. These switches are not listed in any published documentation for this reason. The only switch setting that technical support may instruct you to add is the -trace option. Adding this to the command line will cause the server to write files to the \Program Files\Business Objects\BusinessObjects Enterprise 11.5\Logging directory. Should you wish to send the log files elsewhere, use the -loggingPath switch like this: -loggingPath c:\temp

5 - Programmatic Access

Server information is stored in the CI_SYSTEMOBJECTS category of the InfoStore. Here, server entries have an SI_KIND value of Server. The basic information about servers can be extracted with a SQL statement that requests the main server properties.

6 - Server processes

Server processes can be :

• vertically scaled to reduce cost

where one computer runs several, or all, server-side processes) ,

• or horizontally scaled to improve performance.

where server processes are distributed between two or more networked machines

It is also possible to run duplicate instances of a server process on the same machine, or across several networked machines.

Server processes run as services on Windows machines, and as daemons on UNIX machines. While it is possible to deploy a mixture of Windows and UNIX platforms at the tier level (such as a UNIX web application server with a Windows CMS), it is recommended that you do not mix operating systems for server processes (such as a cluster of two CMS systems where one runs Windows and the other runs UNIX).