Configuring a database server
BMC Server Automation works in conjunction with an Oracle or SQL Server database server. The installation program can configure the Application Server to communicate with this database. However, you can manually configure the Application Server to communicate with the database, as described in this procedure.
In a Multiple Application Server (MAS) environment, you can perform this task only once on each host machine. The database server settings that you configure are applied to all servers hosted on the single host machine. For more information about a Multiple Application Server environment, see Managing multiple Application Servers on the same host.
- Start the Application Server Administration console, as described in Starting the Application Server Administration console.
- To specify a connection string for the database, enter the following:
set database connectionstring
where string is a string that specifies the database type, the server running the database, the port the database listens on, and SQL Server database name or Oracle SID. The connection string can use one of the following formats:
When using one of the formats shown above, do the following:
DBSERVERwith the name or IP address of the server running the database.
DBNAMEwith the name of the database or replace
<SID>with the Oracle SID.
PORTwith the port number the database is listening on. By default, a BMC Server Automation installation uses the following database ports:
- To specify the driver class for the database, enter the following:
set database driverclass <class>
<class>is the Java class used to communicate with the database. Depending on the type of database you are using, you can define the class with one of the following strings:
To specify the user ID and password for the database, enter the following two commands:
set database userid <id> set database password ******
<id>is the user name that the database requires to authenticate your connection and ******** is the password assigned to that user ID.
If you modify the BMC Server Automation database details (for example: server name, SID, or password), you must change the BMC BladeLogic Decision Support for Server Automation site context to use the modified details. For instructions on the changing the site context, see To manage the BMC Decision Support for Server Automation sites in the BMC BladeLogic Decision Support for Server Automation documentation.
To specify a commit size for an Oracle database, enter the following:
set database commitsize <size>
<size>is the maximum number of rows that can be updated in an Oracle database before you either have to commit your updates or roll them back. Commit size is primarily used when taking snapshots or performing audits in BMC Server Automation. A larger commit size means database processes execute more quickly, but at the same time you run the risk of losing more data if a database process fails.
Because Oracle databases can be highly tuned, consult your Oracle DBA to achieve best results when defining a commit size.
- Restart the Application Server.