Chat now with support
Chat mit Support

Identity Manager Data Governance Edition 8.1.1 - Technical Insight Guide

Introduction Data Governance Edition Network Communications Data Governance service Data Governance agents Resource activity collection in Data Governance Edition Cloud managed hosts permission level to role mapping QAM module tables Configurable configuration file settings
Data Governance service configuration file settings Data Governance agent configuration file settings
Configurable registry settings PowerShell commands
Adding the PowerShell snap-ins Finding component IDs Data Governance Edition deployment Service account management Managed domain deployment Agent deployment Managed host deployment Account access management Resource access management Governed data management Classification management

WCF timeouts (wcfTimeoutInMinutes)

Create the following registry key on the client computer where the Manager is installed to specify the maximum amount of time it should take a WCF command to complete before it times out. The Data Governance service will disconnect from the Manager client if the server does not receive any contact or messages within the allotted time.

Table 98: Registry setting: wcfTimeoutInMinutes
Location Registry
Path HKEY_CURRENT_USER\SOFTWARE\One Identity\Broadway\Client
Value name wcfTimeoutInMinutes
Value type DWORD
Value

Maximum amount of time, in minutes, for WCF commands to complete before timing out.

Default: 5 minutes

Reporting timeout (WcfTimeoutReportingInMinutes)

Create the following registry key on the client computer where the Manager is installed to specify the maximum amount of time it should take to generate a report before it times out.

Table 99: Registry setting: WcfTimeoutReportingInMinutes
Location Registry
Path HKEY_CURRENT_USER\SOFTWARE\One Identity\Broadway\Client
Value name wcfTimeoutReportingInMinutes
Value type DWORD
Value

Maximum amount of time, in minutes, for a report to generate before timing out.

Default: 15 minutes

PowerShell commands

This chapter provides a list of the Windows PowerShell commands available to deploy and configure Data Governance Edition components and administer Data Governance Edition to manage the unstructured data in your organization.

For full parameter details and examples, see the command help. For a list and full parameter details and examples of the PowerShell commands available for creating and maintaining managed resources (such as, file shares created through the IT Shop self-service request functionality), see the One Identity Manager Data Governance Edition IT Shop Resource Access Requests User Guide.

Adding the PowerShell snap-ins

Data Governance Edition comes with a Windows PowerShell snap-in for you to use to manage your environment.

If you installed Windows PowerShell on your computer after you installed the Data Governance server, you must register the cmdlets before you can start using them in Windows PowerShell.

To import the Data Governance Edition PowerShell module

  1. Open a Windows PowerShell window and type the following at the Windows PowerShell command prompt:

    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 is "C:\Program Files\One Identity\One Identity Manager\QAM.Client.PowerShell.dll".

  2. To verify that the module was added, type the following at the Windows PowerShell command prompt:

    Get-Module -All

    The registered PowerShell modules are listed.

Note: Run the Set-QServiceConnection command before you can use any of the Data Governance Edition commands.

Adding the module automatically to new sessions

If you do not want to manually add the Data Governance Edition PowerShell module each time you start a new Windows PowerShell session, you can modify the Windows PowerShell profile file so that it is added automatically for you.

To add the Data Governance Edition PowerShell module automatically when you start a new Windows PowerShell session

  • Add the following line to the Windows PowerShell profile file (profile.ps1) file:

    Import-Module "<path>"

    The location of the Windows PowerShell profile file is as follows: WINDOWS\system32\windowspowershell\v1.0

Note: If you get the error message "...profile.ps1 cannot be loaded because the execution of scripts is disabled" the next time you start a new Windows PowerShell session, type the following at the Windows PowerShell command prompt:

Set-ExecutionPolicy RemoteSigned

Then, type the following at the Windows PowerShell command prompt to confirm that the execution policy has been changed:

Get-ExecutionPolicy RemoteSigned

Verwandte Dokumente