Integration


This is an IBM Automation portal for Integration 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.


Add a new idea Subscribe
Status Submitted
Workspace webMethods Integration/Microservices Runtime
Created by Guest
Created on Aug 20, 2026

RELATED IDEAS

Assign instance name to MSR

Currently migrating from IS to MSR, we have some custom management logic that rely on instanceNames.

We understand that with multi instance IS, the instance name is extracted from the path in watt.server.homeDir variable.
In all other cases it is a hardcoded string="Default".

In MSR one workaround is to use extended settings or global variables.
However, the IS Administrator GUI and services like wm.server.query:getServerInstanceName would still inconsistently show "Default" as the instance name

Therefore we are asking to allow MSR to override the returned instanceName through a configuration parameter (for example in set_env or a dedicated extended setting), while retaining "Default" when no value is provided.

That would be consistent with MSR's single-instance architecture while preserving backward compatibility for customers migrating management tooling from multi-instance IS environments.


Idea priority Medium

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.