Declaring database keys on a Job server
Perform the following steps to deploy the database key for the One Identity Manager On Demand Service.
Prerequisite
The key for the database encryption is available in the One Identity Starling portal. For more information, see Information provided for accessing One Identity Manager On Demand.
To declare the database key on a Job server
-
Create a private.key file.
-
Add the key for the database encryption in the private.key file and save the file.
-
Copy the file with the private key in the service's install directory.
-
Open the service management and restart the One Identity Manager On Demand Service.
Configuring connection data for the application server
Perform these steps to configure the Job server to connect via the application server.
Prerequisites
For the One Identity Manager On Demand Service connection you need the application server's URL as well as the user name and password of the system user. This information is provided in the One Identity Starling Portal. For more information, see Information provided for accessing One Identity Manager On Demand.
To declare the connection data on the Job server
-
Start the Designer.
-
In the Designer, select the Base Data > Installation > Job server category.
-
In the Job Server Editor, select the Job server to edit in the Job servers overview.
-
On the Properties tab, enable the No direct database connection option.
-
On the Properties tab, click the 
icon next to the Connection data menu and enter the following connection data for the application server.
-
Display name: Enter a display name for the connection.
-
Provider: Select Application server.
-
Connection parameter: Enter the address (URL) for the application server.
-
Authentication data: Enter the authentication data.
-
Click the ... button.
-
In the Authentication method dialog, select the System user authentication method and enter the user name and password of the system user.
-
Click OK.
-
To save the connection data, click OK.
-
Select the Database > Commit to database and click Save.
How to transfer script modifications from the test instance to the production instance
With a paid subscription, you get a test instance and a production instance. Test your script in the test instance first before adding the changes to the production instance.
To transfer changes the between test and product instances, use the Database Transporter. With this you can create transport packages from the test instance and then use the Database Transporter again to import the transport packages into the production instance.
For detailed information about working with the Database Transporter, see Transporting custom changes in the online documentation on the Support Portal.
One Identity Manager On Demand configuration, customization and product limitations
A configuration is where you use the provided original tools in the system to change its behavior or features without adding additional code or customization.
A customization is a feature or extension or modification of available feature(s) that requires custom coding and or some form of implementation.
To ensure our One Identity operations team can manage, monitor, and perform upgrades to the One Identity Manager On Demand cloud components, all customizations to the offering are strictly prohibited.
Ignoring these limitations may cause the One Identity Manager On Demand cloud components to become in an unupgradable state. If this happens, additional professional services may be required at the customers expenses to revert the One Identity Manager On Demand cloud components to the original state or to install upgrades to the One Identity Manager On Demand cloud components.
