Skip to Main Content

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 (

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 App Connect
Created by Guest
Created on Apr 19, 2013

Message Broker .NET Compute Node Unit Testability

In the 01821,756,000 PMR, it was recommended that I enter an RFE for unit testability of the .NET compute node in Message Broker 8.0. The PMR was raised for recommendations on how to unit test the NBComputeNode object's Execute method, due to complications with the NBAssembly object that is required to write a unit test. The NBAssembly object's parameterless constructor is private, and the public constructors require another NBMessageAssembly object. This creates a chicken-and-the-egg problem, in which we can't create an NBMessageAssembly object because we don't already have one.

Opening this RFE as recommended by the PMR, so that we can get a workaround or an enhancement to Broker to support unit testing the NBComputeNode object's Execute method.

Idea priority Low
RFE ID 33829
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Mar 16, 2022

    As hinted at in the last update on this idea, having delivered a new unit testing framework in ACE which enables granular testing of a node within a flow without having to execute the entire flow, we now have the capability of isolating the .NETCompute node, and proving using a new unit test that we are correctly instantiating the message assembly object (sourced from a message assembly file with .mxml extension) and the correct feeding of this object into the .NET parts of the product runtime.

  • Guest
    Sep 14, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. It is likely that this use case will be resolved in as part of a future expanded scope for unit testing of the product. Status of this RFE is updated to Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB