Integration
Hide about this portal


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 Future consideration
Workspace App Connect
Created by Guest
Created on Nov 7, 2013

RELATED IDEAS

CDOutput node should have the ability to invoke a predfined C:D process

See this idea on ideas.ibm.com

There is quite a bit of power and flexibility built-in to Connect:Direct, which allows various options while completing a managed file transfer. This functionality is associated the process definition within Connect:Direct. Using the broker CD nodes this flexibility cannot be utilised as the broker generates its own process based on the few options specified within the CD node properties and the Local Environment.

While this functionality is useful performing a basic managed file transfer, it would be more useful if the broker could use or invoke a process that has been defined within C:D itself. This would expose all of the ability within C:D to the broker integration. The default behaviour could remain as is, but with an option on the nodes or the environment or both, to call a process directly.

Idea priority Medium
RFE ID 41322
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Reply
    |     Aug 2, 2021

    Idea / RFE Review. Apologies for the length of time this idea has been in the status of Uncommitted Candidate / Future Consideration. A potential workaround for the interim could perhaps take advantage of the job execution node(https://github.com/ot4i/job-execution-node) although obviously you would ideally prefer a built-in product solution. Whilst we have not yet managed to prioritize a business case for this feature we will maintain its status as Future Consideration for now.

  • Guest
    Reply
    |     May 12, 2017

    Apologies this RFE has been in status of Under consideration for so long.
    Status of the RFE is updated to Uncommitted Candidate.

  • Guest
    Reply
    |     Jun 24, 2016

    The lack of this feature prevents us from using this node completely. All our output C:D connections have such a follow-up job like:

    submit D1234567 process snode=CDMVS_DWPT
    st02 run task snode (pgm=XYZCND)
    sysopts="'ADD COND W-CD1234/D1234567 2201'"

    pend;

    There's also some logic in our scripts for these jobs, so we need the following features:

    - static configuration (overwritable in the bar file)
    - policy based configuration
    - dynamic configuration (using pre-set variables in the Environment)

  • Guest
    Reply
    |     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

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.