Skip to Main Content
Cloud Platform

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 a notification 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.

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 Submitted
Workspace Rational Other
Categories Change
Created by Guest
Created on Mar 11, 2022

For Physical Web Server definitions split Host and Port configuration for test and passthrough behaviour

Currently in RIT Client configuring the physical definition the Host and Port configuration on the settings tab is used for both initiating test (bound to the operation and logical transport) and also for the default passthrough endpoint for stubs.

If the stub port is hardcoded using Port field on Server Socket Overrides section of the server tab and the RTCP proxy is not used and published to RTCP and started on RTVS it's not possible to use test configured for the same environment as they will be sent to the configured passthrough endpoint for stubs, instead of the hardcoded port and endpoint of the RTVS server.

Also when deploying multiple stubs with the same passthrough address (on settings tab) the proxy will fail to correctly configuring rules and/or will round robin between the started stubs if connecting through the proxy with this address as a RIT tests.

To test the stub directly we now always have to define another physical definition and/or environment to be able connect to/test the stub by configuring the rtvs server and configured port for the stub on the Settings tab.

Could an option be made to separately specify the passthrough hostname and port in the physical definition so we don't have to create to physical definitions/env to test the stub.

Idea priority High