Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Dec 31, 2013

Enhancement ticket for the product future Installations

We request IBM to open an Enhancement ticket for the issue that we are struggling for MDM, BackUp MDM, FTA, Patch, etc. installations.

[1] 'root' / 'sudo-root' access requirement: We aren't allowed to be
'root' or 'sudo-root' on a system and execute the IBM's installation
script of which we again aren't aware of what all changes / setup it
runs. We had multiple discussions and convincing to do to acquire 7-
days temporary 'sudo-root' access for it.

[2] DBA schema or a schema with DBA privileges req: We are strictly prohibited to use DBA schema or assign DBA privileges to any schema for the installation. Moreover, we aren't aware of what all impact it will create on running the priviledged account. Hence, it gets
difficult to convince the DBA. We had to take the sole responsibility
of the impact of using DBA priviledge assigned schema for the activity.

ENHANCEMENT REQUIRED: For both the above cases, we need an independent script for both SA (System Admins) and DBA activities (of which they will assess and run it)- followed by an TWS Admin script to integrate both the setups.

Idea priority High
RFE ID 43241
RFE URL
RFE Product IBM Workload Scheduler (IWS)
  • Guest
    Reply
    |
    Jan 24, 2022

    For 1) for traditional script installation you can do it without root privileges for DWC and dynamic agents, alternatively you can use the containerized installation.

    For 2) the steps requiring DBA authority have been isolated in a separated script.

    Both enhancements are available from V9.5.

  • Guest
    Reply
    |
    Nov 6, 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 - IBM Workload Scheduler (IWS)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - IBM Workload Scheduler (IWS)

  • Guest
    Reply
    |
    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 Workload Scheduler for Distributed (TWSd)

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Automation
    Product - Tivoli Workload Scheduler for Distributed (TWSd)

  • Guest
    Reply
    |
    May 7, 2015

    Comment about the bullet 1 of the RFE.
    It requires for the WAS authentication to be switched to WAS File-Based repository at installation time (for the MDM).
    Note that all the other WAS security configuration (LDAP, localOS security adapter) can be performed as post-installation step after the success of the install.

    In this way the post-install can easily be done by the customer to correctly match the requirement of the target system, and also simplifying the TWS
    installation.