Cloud Management and AIOps

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

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.

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Control Desk

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Not under consideration
Created by Guest
Created on Feb 18, 2013

Servergroups

In a SERVER application group any number of components can be
specified that must be available before the group is considered
to be available. With SERVER application groups you can specify
what should happen if their components fail to start.

The automation programmer can set the numbers of members that
should be available for a SERVER application group by specifying
the Availability Target when defining the group.

Idea Priority Urgent
Use Case
same use case like in SA z/OS. I. e. load distribution
RFE ID 31391
RFE URL
RFE Product Tivoli System Automation Application Manager (SA AM)
  • Guest
    Apr 12, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Workload Automation and Control Desk
    Product - Tivoli System Automation Application Manager (SA AM)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli System Automation Application Manager (SA AM)

  • Guest
    Oct 10, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli System Automation Application Manager (SA AM)

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Automation
    Product - Tivoli System Automation Application Manager (SA AM)

  • Guest
    Apr 10, 2013

    Additionally to the basic function of a server group, there is an additional feature "Rolling Recycle", that should be implemented with the server group:

    In most cases a server group is used to realize application clusters, where n members run in parallel, but only mIn case of maintance, you often restart one member after the other to ensure the service. This function should be provided by a button "rolling recycle" which stops and restarts one member after the other. Addtionally, you could think of providing a selection panel, where the operator can specify only those members that should be recycled.

    Furthermore, you should a possibility for nested server groups. E.g. for configuration where 4 members on 2 sites are providing service. In this case you would first create 1 server group for each site and then add these 2 server groups to one top-level server group.