NOTE: Oracle Database support was deprecated beginning with One Identity Manager 8.1. Do not use.
This key defines the database system, SQL Server or Oracle Database, being used for the One Identity Manager database. This setting is used by the ManagementServer internal service that manages the core Data Governance service dependencies.
NOTE: If you are using an Oracle database for the One Identity Manager database, create this registry key on the computer where the Data Governance service is to be installed. Once this key and the QDGDBPlatformOracle key are created and set to 1, use the Data Governance Configuration wizard to deploy the Data Governance service and create the Resource Activity database.
Table 98: Registry setting: Q1IMDBPlatformOracle
| Location |
Registry |
| Path |
HKEY_LOCAL_MACHINE\SOFTWARE\One Identity\Broadway\Server |
| Value name |
Q1IMDBPlatformOracle |
| Value type |
REG_DWORD |
| Value |
Valid values:
- 0: Use SQL server database (default)
- 1: Use Oracle database
|
| Note |
If using an Oracle deployment, create the key and set the value to 1. |
This key indicates whether the default managed resource data defined in Data Governance Edition is written to the One Identity Manager database This includes the following default data about a managed resource:
- Managed group templates
- Name pattern resolvers
- Server selection scripts
- Managed resource type (that is, Simple Share)
- Type group permissions
- Managed resource functions
For more information on the managed resources, see the One Identity Manager Data Governance Edition IT Shop Resource Access Requests User Guide.
NOTE: This registry value is checked on Data Governance service startup and if not present or if its value is set to 0, Data Governance Edition writes the default managed resource data into the One Identity Manager database and sets the registry value. When this value is set to 1, this indicates that the default managed resource data is already stored in One Identity Manager database and should not be overwritten on service startup.
Table 99: Registry setting: ResourceTemplateDefaultData
| Location |
Registry |
| Path |
HKEY_LOCAL_MACHINE\SOFTWARE\One Identity\Broadway\Server |
| Value name |
ResourceTemplateDefaultData |
| Value type |
REG_DWORD |
| Value |
Valid values:
- 0: Write the default managed resource data into the One Identity Manager database.
- 1: Default template data is already stored in the One Identity Manager database: do not overwrite on Data Governance service startup.
|
| Notes |
If you delete the default managed resource data in your Data Governance Edition deployment and replace it with a new managed resources, you must move or set this registry key if you move the Data Governance service to another machine. When you move the Data Governance service to another machine, before starting the Data Governance service ensure that this registry key is set (value is set to 1); otherwise, the Data Governance service will reload any previously deleted template data that was inserted when the Data Governance service was initially started (on the first machine).
If you modify the default managed resource data in your Data Governance Edition deployment, the data is retained if you move the Data Governance service to another machine. |
Create this registry key on the Data Governance server to specify the amount of time (in seconds) to wait for an agent service to start or stop before timing out.
Table 100: Registry setting: StartStopServiceTimeout
| Location |
Registry |
| Path |
HKEY_LOCAL_MACHINE\SOFTWARE\One Identity\Broadway\Server\AgentDeployment
NOTE: The AgentDeployment subkey does not exist by default and will need to be created. |
| Value name |
StartStopServiceTimeout |
| Value type |
REG_DWORD |
| Value |
Maximum amount of time, in seconds, before an agent start/stop times out.
The default is 300 seconds. |
| Note |
During an agent uninstall, the Data Governance server sends a command to stop the agent service and then waits for the service to stop. If the agent service takes a long time to shut down, the unistall fails. To solve this, the timeout value for the agent service stop can be increased using this registry key setting.
In addition, if you modify the timeout value here, you should also update the RemoteExecutor.WaitResultTimeout configuration setting to the same value. For more information, see RemoteExecutor.WaitResultTimeout. |
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 101: 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 |
