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 (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.

Add a new idea Subscribe
Status Functionality already exists
Workspace Sterling Transformation Extender
Categories Launcher
Created by Guest
Created on Dec 14, 2020

RELATED IDEAS

Add Ability To Configure Where Launcher Logs Are Written

We are starting to use the Launcher image to deploy and run Launcher in containers. The Launcher Logs are written to <itx_install_dir>/logs by default, and there is no way to change where these logs are written. So, when the pod/container is destroyed, the Launcher Logs are not persisted and we lose this history.

What would help is a setting within the "dtx.ini" file where we could choose to write these logs to a Persistent Volume Claim so we can retain them.

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

Please see my previous short description.
  • Guest
    Reply
    |     Jan 7, 2021

    I already had a support case for this (TS004626050). What is in the PDF would work if we were starting our container using a CLI, but we use a web console. Rex Chan and I came up with a workaround involving creating a mount point. However, a more straightforward approach would be to configure this in the "dtx.ini" file, as we do with other ITX-related paths.

  • Guest
    Reply
    |     Jan 7, 2021

    Refer to the PDF document included with the container for the archive file on how to configure this capability. If additional infomration is needed, please log a support incident

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.