Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace Self Service Tool
Created by Guest
Created on May 24, 2019

Provide method to script the OMoC/Cloud build and deploy process

The following are the 7 basic steps for building and deploying a package to the OMoC/Cloud OMS environment. In an on-prem instance of OMS, all of these steps are easily scripted so that the admin can run one command and execute everything, that makes it much easier and more efficient to do deployments. That capability simply doesn't exist for steps 5, 6, and 7 on OMoC, the request is to change that and make it possible to ssh or whatever method into a jump host to accomplish this.


1) Check-out code and configuration from repository.
2) Build the extensions.jar from the check-out code.
3) Zip up the configuration XMLs.
4) Upload the extensions.jar and CDT zip file to the drop server.
5) Import the deployable package.
6) Import the config from the CDT upload.
7) Execute the cloud deploy to the development environment.

What is your industry? Retail
How will this idea be used?

To make the life of the admin easier and much easier to document the steps.