How To
Summary
Locking down a Rational Change instance to be read-only requires updating the lifecycle process. The ability to make changes should be allowed for admin users who have a particular privileged role, like ccm_admin. This role should be given to only a small number of users.
The approach described here will allow you to make one, some, or all databases accessible yet read-only to users by limiting them to one specific privilege.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYQQ2","label":"Rational Change"},"ARM Category":[{"code":"a8m0z000000bonMAAQ","label":"Change-\u003EAdministration"},{"code":"a8m0z000000bonRAAQ","label":"Change-\u003ELifecycle"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
24 July 2024
UID
ibm17160629