IBM Sterling Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Configuration management should have an approval process for changes

There should be an approval process built into SCC for making changes with the Configure Servers functions. Adding an optional hook to make a call to a change management system for validation would be even better. The change process should include configurable fields like change record and configuration items effected.
  • Guest
  • Jan 8 2018
  • Future consideration
DeveloperWorks ID DW_ID46866
Link to original RFE
  • Guest commented
    14 Mar, 2019 05:20pm

    A variation on this is the ability (via LDAP groups) to limit user's functionality.

    We use this within C:D Windows already so that a user typically only has 'select stats' type access and cannot change anything by default. With the correct LDAP (ie. Active Directory) group membership, they can have admin rights. Users can be added/remove from AD roles to limit what they can do. This is enabled within C:D Windows using group functional authorities which relate to AD groups.

    To complete this, the groups that users are added to have 'timed access' where they are added to an AD group for a set amount of time then removed again. This access has to be independently approved and ties in with our Change Management solution.

    For C:D z/OS, we have similar functionality; users are members of RACF groups which are checked by the security exit. Again, the groups are centrally administered.

    It's not perfect; once a user has admin rights, they can do anything but it's huge improvement on what's available natively in ICC.

  • Guest commented
    14 Mar, 2018 07:19pm

    Change management procedures can vary greatly from one company to another.  I believe change management standards regarding the use of Control Center to change items needs to developed/managed "in house".

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.