Defining the Admin Database Settings for an MS SQL Database Server

The steps in this section describe how to define the settings for the Decision Admin database when the source database is an MS SQL database. For an Oracle database, see "Defining Admin Database Settings for an Oracle Database Server".

There are two approaches that you can use for creating databases for PCO/PDA when you are using MS SQL databases. You can already have defined a database in MS SQL and then just connect it during the installation process, or you can create and connect it during the installation process with the steps that follow. (This option is not available for Oracle databases.)

Before you begin

Make sure to have completed the setup tasks described in "Preparing MS SQL Databases." For example, when you define the Admin database, you need to specify a system userA user is an instance of a User object in the Automation Engine, and generally the user is a specific person who works with Automic products. The user object is assigned a user ID and then a set of access rights to various parts of the system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and Release Manager object rights. You can manage all these centrally in the AWI user management functions. See also, Unified user management. for it. This user needs to be defined in your MS SQL Server database and must have at least the following rolesRoles in the user management functions in the AWI refer to user roles in Decision. User roles indicate what actions the user is allowed to perform, for example, a user with the role "super administrator" is allowed to work with all functions related to Decision. assigned to it:

Steps...

1. In the Settings section, click the Admin DB tabTabs allow you to structure the Main Pane in several overlapping sections that are all open at the same time but are viewed one at time..

2. In the DB Type box under DB Connection Type, select "Microsoft SQL Server".

   The Connection Type is automatically set to "SQL Native Client," which is the only option here.

   

3. Define the DB Connection Settings

   Setting	Description
   Server Name	The host name of the server where the Admin database is installed.
   DB-Name	The name of the Admin database.
   Authentication	The kind of authenticationAuthentication is the process through which Automic systems verify whether a user is allowed to enter the system. This is done by verifying the user ID and the related password. that is used to access the Admin database. Options are: SQL Server Authentication Windows Authentication. If you select this option, the remaining fields are disabled.
   User Name	The database user name with which Policy Orchestrator can log into the Admin Node database.
   Password	The database user password.

   As you enter the settings for the DB Connection, the Configuration Manager constructs a connection string statement in the DB Connection String box. This is greyed out because it is locked.

4. Optionally, modify the DB Connection String manually, if you want to add other configuration settings.

   1. Click the padlock icon to unlock the field.

   2. Type your modifications.

      

5. Click the Create DB button to automatically create the Admin database.

   Note: You can also manually create the database and assign the user to the database. In this case the database user needs to have only the DBOWNER role.

6. Test the connection to make sure that the Configuration Manager can find the database.

   1. Click the Test Connection button.

      A progress bar appears at the bottom of the tab page. If the test process finds errors, a window appears with a description of the errors.

   2. Correct any errors and retest the configuration until the Status at the bottom on the tab page reads "Connection has been tested successfully."

7. Continue with "Defining Services Settings".