App Connect

App Connect

Join this online user group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#Applicationintegration
#App Connect
#AppConnect
#Integration
#Automation
 View Only
Back to discussions
Expand all | Collapse all

Message flow to handle new API version requests

  • 1.  Message flow to handle new API version requests

    Posted 01/12/21 08:16 AM
    Hello All,

    Scenario is :

    Message Flow - TEST.msgflow has HTTP Input node with url (/test/v1/sample/) and we need to accommodate new API request which will be exposed by either new flow or same flow with new url(/test/v2/sample/).

    Note: we need to keep untouched to existing url(keeping that url and flow functionality) as it is since it is still be used by clients.

    So, creating new message flow say. TEST.2.0.0.msgflow with new url and copying most of functionalities from existing and implement new feature on it ?.

    This way, we are not disturbing existing (/test/v1/sample/) request and adding new Message flow for (/test/v2/sample/) and it will he good for maintenance and trouble shoot.

    If required, its easy to retire older version message flow with out disturbing new version.

    Also Could you recommend adding version number like 1.0.0 or 2.0.0 in the end of the new Flow names as we progress with new api urls/versions ?

    Example - TEST.1.0.0.msgflow, TEST.2.0.0.msgflow

    Thanks.

    ------------------------------
    Hassan
    ------------------------------


Related Content