You need the following to manually deploy the Data Governance service:
- Data Governance Server installation msi
- Local Administrator rights on the server where the Data Governance service is to be installed.
- Installation of the One Identity Manager client applications (including the Data Governance Edition PowerShell snap-in)
- Ability to change One Identity Manager configuration options in the Designer application
- Connection information to the One Identity Manager database
- Database creation permissions (if creating the Data Governance Resource Activity database)
To manually deploy the Data Governance service
- Log on to the system with the One Identity Manager client installation.
- Open the Designer and log on as a system user with administrative privileges (for example, viadmin)
- Edit the Data Governance service configuration parameters:
- In the navigation view, select Base Data | General | Configuration parameters.
- In the far right column, click Edit configuration parameters.
- Expand TargetSystem | ADS | QAM | QAMServer.
- Change the ServerName value to the fully qualified DNS name of the server where the Data Governance service is to be installed.
- Set the Port value to the net.tcp port your server will listen on. The HTTP port will automatically be configured to use the net.tcp port value -1.
Set the Deployment value to the name of your Data Governance Edition deployment.
Note: This defaults to "DEFAULT". If you are going to or already have multiple Data Governance Edition deployments in your Active Directory forest, you must ensure this name is unique. The Deployment value is restricted to a maximum of 30 characters and can contain alphanumeric characters and underscores (no spaces).
Use the LocalSystem account to log on to the Data Governance server specified above and run the Data Governance Server installation msi.
Note: When you run the MSIEXEC from a command prompt, you must be running as local system. This ensures that the service connection point can be updated no matter what your Data Governance service runs as.
Example: ->msiexec /i "DataGovernance_ServerComponentsInstaller_x64.msi" /lv C:\DgeMsintallLog QAMDEPLOYMENT="testNew" QAMPORT=8722
Note: Refer to the Microsoft documentation for command line syntax of MSIEXEC.EXE. For more information on using the Windows Installer (MSIEXEC.exe) refer to Microsoft's MSDN library: https://msdn.microsoft.com/en-us/library/aa367988(VS.85).aspx
See Data Governance service options for a description of the Data Governance deployment options available.
- Open a Windows PowerShell console on the machine with the One Identity Manager client installation.
Run the following cmdlet to import the Data Governance Edition PowerShell module:
Import Module "<path>"
Where <path> is the file path for the QAM.Client.PowerShell.dll assembly. By default, the <path> for the Data Governance server machine would be "C\:Program Files\One Identity\One Identity Manager\QAM.Client.PowerShell.dll"
Run the following PowerShell cmdlet to set the server name, deployment name and port information used by the Data Governance Edition commands to connect to the Data Governance server:
Set-QServiceConnection -ServerName "<DGE server machine name>" -Port <Value> - Deployment "<Deployment name>"
Note: The <DGE server machine name>, Port <Value> and <Deployment name> must be the same values as specified in step 3.
Close the PowerShell console and restart the Data Governance service.
Run the following PowerShell cmdlet to establish the database connection between One Identity Manager and Data Governance Edition:
Initialize-QDataGovernanceServer -DatabaseConnectionString "<Connection string for Identity Manager database>" [-DefaultEmployeeSid "<SID of user account>"
Note: Only specify the "-DefaultEmployeeSid" parameter if you want to take advantage of the automatic forest topology harvest. Adding this parameter adds the user associated with the specified SID to the One Identity Manager Employees with the appropriate Data Governance application roles. This provides the same functionality as selecting the Add the current user to the One Identity Manager Employees with Data Governance application roles option when using the Data Governance Configuration wizard.
Note: If Windows Integrated Authentication is used to connect to the database, the Data Governance server must be configured to run as an identity other than LocalSystem (See step 4).
Connection string examples:
An example of a connection string for Windows authentication may look like this:
An example of a connection string for SQL authentication may look like this:
"Data Source=myServerAddress;Intitial Catalog=myDatabase;User Id=myUser;Password=myPassword"
For more information on connection strings, see The Connection String Reference.
- Using your preferred database management tool, browse on the Data Governance server to the %ProgramFiles%\One Identity\One Identity Manager Data Governance Edition\Server\Activity Database Scripts folder and locate a file named "DGAuditDatabaseCreationScript.sql".
For SQL Server hosted databases, open the DCAuditDatabaseCreationScript.sql file and update the database name specified in the CREATE DATABASE and USE statements.
Note: If you are running multiple Data Governance Edition deployments, it is highly recommended that you append the deployment name to the database name (for example, DGE_DEFAULT). This database name has a maximum length of 30 characters and can contain alphanumeric characters and underscores (no spaces).
- Run the appropriate script for your database management system to create the Data Governance Resource Activity database.
Run the following PowerShell cmdlet to initialize the database to store data generated when a managed host has resource activity collection enabled:
Initialize-QDataGovernanceActivity -ConnectionString "<Connection string to activity database>"
Note: Ensure the connection string's Initial Catalog value (Database value if using Windows authentication) matches the name you specifies in the sql script when creating the Data Governance Resource Activity database.
Restart the Data Governance service.
Note: It might take a few minutes before the Data Governance topology harvest task begins.