Recommendations and tips for transporting IT Shop components with the Database Transporter
For detailed about working with change labels and about transporting changes with the Database Transporter, see the One Identity Manager Operational Guide.
To transport IT Shop components with the Database Transporter, take the following into account:
-
In one transport package, only include a maximum of one shop with shelves and customer nodes including the dynamic roles and, if necessary, associated approval policies.
-
You should not transport products that reference target system entitlements. Target system entitlements are loaded into the database by synchronization and obtain different UIDs in different databases. This means that references to these entitlements do not match up in the products.
-
Approval policies, approval workflows, approval steps, and approval procedures should be transported together. If necessary, mail templates and mail definitions must be transported as well.
-
If IT Shop components reference application or business roles, they must also be transported along with their child roles.
-
Transport translations if required.
-
If you want to group several objects and dependencies and other changes into a transport package, work with change labels where possible. In the Database Transporter, you can export change labels to a transport package. You can import the transport package with the Database Transporter.
-
Alternatively, you can transport a single object with its dependencies by creating an export in transport format. Then you can import the export with the Database Transporter.
Troubleshooting errors in the IT Shop
Timeout on saving requests
If new requests are saved in bulk in the database a timeout may occur, after importing data, for example.
Probable reason
By default, the approvers responsible are determined during saving. This delays the saving process. No more actions can take place in One Identity Manager until all requests are saved and, therefore, all approvers have been found. Depending on the system configuration, this may cause a timeout to occur when large amounts of data are being processed.
Solution
Effect
-
The requests are saved and a calculation task for determining approvers is queued in the DBQueue. Approvers responsible are determined outside the save process.
-
If the requester is also the approver, the approval step is not automatically granted approval. Approvers must explicitly approve their own requests. For more information, see Automatically approving requests.
-
Automatic approval decisions are also met if necessary, but are delayed. This affects requests with self-service, for example.
Bulk delegation errors
You have the option to delegate all your responsibilities to an identity in the Web Portal. If you have a lot of responsibilities, it is possible that not all the delegations are carried out. A delegator can send a notification to themselves if an error occurs.
Probable reason
An error occurred processing delegations. VI_ITShop_Person Mass Delegate was stopped, although only a fraction of the delegations has been applied.
Solution
-
Configure the notification procedure.
-
Run all remaining delegations again in the Web Portal.
Related topics