Setting up a SQL Server database

This topic provides instructions for setting up a fresh installation of the BladeLogic Portal database using a Microsoft SQL Server database. 

The procedure describes how to create two users (also known as logins). One user creates the portal database while the other user functions as an operational user. For security reasons, the operational user is granted only limited access to data.

This procedure uses SQL scripts that are provided in installation files.

Warning

These tasks should be performed by a database administrator (DBA). Perform the steps in these tasks in the order in which they are described. If you are not using the scripts mentioned in this procedure, refer to them to determine the privileges required.

Recommendation

Use only Latin alphabet letters, numbers, and underscores (_) in database names. Do not begin database names with a number.

Before you begin

  • Use SQL Server 2008 R2 or later.
  • Obtain the installation file called windows.zip and extract its contents.  The windows.zip file is included in the installation file used to install BladeLogic Portal on Windows. See Downloading-the-installation-files.

To set up a SQL Server database

  1. Log into the SQL Server database using administrator credentials.
  2. Create a new login.
    1. Assign any name consistent with your naming standards. For example, create a login named blportal_owner. 
    2. If you select SQL Server authentication, provide a password.
    3. When defining the login, on the Server Roles page, select Public. 
    4. On the Status page, ensure that Permission to connect to database engine is set to Grant and Login is set to Enabled.
  3. Create a new database object.
    1. Assign any name consistent with your naming standards. For example, assign a name called blportal. 
    2. Set Owner to the login name you created in step 1, such as blportal_owner.
  1. Open the Properties page for the login created in step 2 and change Default database to the database created in step 3.
    This step limits user access to only the portal database for security reasons.
  2. Create another login that functions as the operational user. 
    1. Assign any name consistent with your naming standards. For example create a login named blportal_oper. 
    2. If you select SQL Server authentication, provide a password.
    3. Set Default database to the database created in step 3. 
    4. On the User Mapping page, select the database created in step 3, and on the same page select the db_datawriter role membership.
      The public role is automatically selected on the User Mapping page. Leave it as is. 
    5. On the Status page, ensure that Permission to connect to database engine is set to Grant and Login is set to Enabled

  3. Create the database tables by executing the sqlserver_master.bat script. 

    1. In the installation files, cd to this directory: installation_file_location\windows\BMCAutomationPortal\Disk1\utility\sqlserver. 

    2. Run the following command:

      sqlserver_master.bat sqlserv db user pwd
       

      sqlserv is the name of the host where SQL Server is running, such as localhost. 
      db is the name of the database created in step 2, such as blportal.
      user is the name of the SQL Server user that has the db_owner role. This is the login created in step 1. For example, blportal_owner.
      pwd is the password of the SQL Server user.

    SQL Server creates the schema, core data, indexes, and constraints.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*