Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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
Created by Guest
Created on May 11, 2023

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 Medium
  • Guest
    Dec 14, 2023

    The feature that you requested has been delivered and is available in release DevOps Automation 2023.12 (version 11).
    Additional information can be found here >

  • Guest
    Sep 20, 2023

    The feature that is described in this request is currently under development and should be included in a subsequent release.

  • Admin
    Willetta Ar-Rahmaan
    Aug 10, 2023

    The feature that is described in this request is a candidate for a future release

  • Admin
    Willetta Ar-Rahmaan
    May 15, 2023

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.