A simple trick to improve the reliability of your Business Objects server during startup is to use service dependencies. If you have your database and Business Objects both running on the same server, you can often run into problems during startup where the CMS service attempts to start before the database is started. Without access to its repository database, the CMS will fail to start and the entire Business Objects platform will be inaccessible. All those services would have to be manually started once the database is online.
To fix this, you can very easily add a service dependency via the Central Configuration Manager. In Business Objects 3.0/3.1, fire up the CCM and click on your Server Intelligence Agent. To add the dependency, you will have to first stop the SIA. Once stopped, right-click on the SIA and go to Properties. Click the Dependency tab, then click Add. Locate your database service in the list — SQL Server, Oracle, etc. — and click Add. Restart your SIA and you’re good to go. Next time you restart the server, the SIA (and the CMS) will wait to start until the database is online.
Adding a Service Dependency in BOBJ Enterprise 3.1
Wednesday, April 8, 2009
System Administration, Tutorials