Posts Tagged ‘Services’

Manually Starting Services

September 19th, 2008 4 comments

Even though the SIA has been setup to automatically start services, another alternative is to control the starting of these services through scripts. One colleague of mine setup his BusinessObjects Enterprise SIA so that only the CMS and the FRS Input and Output services started up automatically.  All other services were setup to start manually.

In his experience, this made the starting of the SIA require less resources making startup (even) less error-prone that it already is.

Batch File for Starting Services

Below I have included all the contents of the batch file which you can download here.  Enjoy…

«Good BI»

:: Cleaning up
del /f /q "C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0Logging*.log

:: Starting up dependencies
net start "SQL Server (MSSQLSERVER)" 

:: CMS configured to startup automatically with SIA
:: See Control Panel Services for startup configuration (automatic)
net start "Server Intelligence Agent (cdi6BOE)"
net start "Apache Tomcat 5.5.20"

:: add timeout to allow CMS to initialize
:: sleep 90

cd "C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0win32_x86"
:: CMS and FRS configured to startup automatically with SIA
:: (CMC > Servers > Properties)
:: ccm.exe -managedstart cdi6BOE.CentralManagementServer
:: ccm.exe -managedstart cdi6BOE.InputFileRepository
:: ccm.exe -managedstart cdi6BOE.OutputFileRepository
ccm.exe -managedstart cdi6BOE.AdaptiveProcessingServer
ccm.exe -managedstart cdi6BOE.DestinationJobServer
ccm.exe -managedstart cdi6BOE.EventServer
ccm.exe -managedstart cdi6BOE.ProgramJobServer
ccm.exe -managedstart cdi6BOE.PublicationJobServer

:: Crystal Reports
ccm.exe -managedstart cdi6BOE.CrystalReportsCacheServer
ccm.exe -managedstart cdi6BOE.CrystalReportsJobServer
ccm.exe -managedstart cdi6BOE.CrystalReportsProcessingServer
ccm.exe -managedstart cdi6BOE.ListOfValuesJobServer
ccm.exe -managedstart cdi6BOE.ReportApplicationServer

:: Desktop Intelligence
:: ccm.exe -managedstart cdi6BOE.ConnectionServer
:: ccm.exe -managedstart cdi6BOE.DesktopIntelligenceCacheServer
:: ccm.exe -managedstart cdi6BOE.DesktopIntelligenceJobServer
:: ccm.exe -managedstart cdi6BOE.DesktopIntelligenceProcessingServer

:: Performance Management
ccm.exe -managedstart cdi6BOE.DashboardAnalyticsServer
ccm.exe -managedstart cdi6BOE.DashboardServer
ccm.exe -managedstart cdi6BOE.PMMetricsServer
ccm.exe -managedstart cdi6BOE.PMRepositoryServer
ccm.exe -managedstart cdi6BOE.PMRulesServer
:: ccm.exe -managedstart cdi6BOE.PredictiveAnalysisServer
:: ccm.exe -managedstart cdi6BOE.ProcessAnalysisServer
:: ccm.exe -managedstart cdi6BOE.SetsProfileServer
:: ccm.exe -managedstart cdi6BOE.SetsQueryServer

:: Voyager
:: ccm.exe -managedstart cdi6BOE.MultiDimensionalAnalysisServicesServer

:: Web Intelligence
ccm.exe -managedstart cdi6BOE.AdaptiveJobServer
ccm.exe -managedstart cdi6BOE.WebIntelligenceProcessingServer
Categories: Administrators Tags: , , , , ,

How does your SIA start?

September 18th, 2008 3 comments

If you are running a development environment in which you have the BusinessObjects XI 3.0 server running on the same physical box as your BusinessObjectcs repository, you have run into a common problem.  In XI 3.0, the SIA is dependent on the repository and if the repository database is unavailable the SIA will failed to start and not retry.

Service Dependencies in Windows

In my case, I am using Microsoft SQL Server as my BusinessObjects repository database.  Therefore I need to make sure that Microsoft SQL Server is up and running before the SIA attempts to start.  Microsoft Windows accommodates this by allowing you to create service dependencies.  In our case, it will guarantee that  Microsoft SQL Server service is running before the SIA service attempts to start.

Changing the Configuration

Let’s walk through the process of setting up a dependency to the SIA will start automatically.

  1. Start the CCM and select the SIA Service. The SIA service must be stopped before you make your changes.

  2. Next, Choose Properties and Dependency

  3. Lastly choose Add and select SQL Server (MSSQLSERVER) from the list of available services.

  4. After you add the dependency you will see:

Now each time the SIA attempts to start, it will first check and verify that in addition to the Event Log servcie and the RPC service are running, the SQL Server service must also running before it attempts to start.

Do you have Multiple SIAs?

If you have multiple SIA’s, you should add this dependency to each one so that anytime the server reboots, the SIA will start correctly.

One Last Thing You’ll Want to Know

You may also which to modify the “Recovery” properties of your SIA Service so that in case it fails to start, it will attempt to restart.  To change these properties you will need to go into to Windows Services.

  1. Start > Run and type in services.msc

  2. Go to the Recover Tab and change the Restart service after value to 1.

Getting It Right Every Time

Adding these few dependencies will help to make sure that you never have any problems getting your CMS to start during the normal system restart.  If you have made any modifications to the start-up process of your BusinessObjects server, I would love to hear what you’ve done!

«Good BI»

Categories: Administrators Tags: , ,