App Connect

 View Only

  • 1.  How to change WLM Policy into a MQ Node in runtime

    Posted Thu May 26, 2022 02:13 PM
    Hi community:

    We are moving to ACE v12 on premise and we need the following requirement as we did in IIB v10,

    I have a specific message flow with a MQ Input Node which is necessary to add/remove instances as per workload. Now we have a Policy Project deployed in Integration Server where this message flow is deployed as well, now this message flow is connected to a Policy with 10 instances, but how is the process to scale up to another one? Example 20 instances?

    • We are changing META-INF/broker.xml to chance new WLM Policy but is require to restart Integration Server, is there any process to do this process without restart?
    • Another option is, at Web User interface we change threads from 10 to 20 instances but if message flow restarts, instances come back to 10.

    I appreciate any help.

    Regards

    ------------------------------
    David Bonilla
    ------------------------------


  • 2.  RE: How to change WLM Policy into a MQ Node in runtime

    Posted Mon May 30, 2022 03:15 AM
    Hi David

    I am assuming you want to dynamically control the number of flow instances in ACEv12.

    You can try the following. my test environment uses independent integration servers.

    1) update the WLM policy in the existing policy project and redeploy just the policy project into the integration server.
    this should reload the flow with the new policy without restarting the integration server process.

    2) export the policy project with the policy changes and place that in the overrides directory of the integration server directory as described in the ACE documentation see https://www.ibm.com/docs/en/app-connect/12.0?topic=policies-overriding-deployed-run-time-overrides-directory
    A restart of the integration server is required in this case.  This change will survive a restart.  It will also override any new updates that you plan to deploy in future.

    Unfortunately, I did not find a way to update the WLM policy via the ACE Admin REST APIs. 




    ------------------------------
    Regards
    Colin Lim
    ------------------------------

    Original Message


  • 3.  RE: How to change WLM Policy into a MQ Node in runtime

    IBM TechXchange Speaker
    Posted Mon May 30, 2022 03:46 AM
    Colin correctly documents the method for updating (redeploying) a WLM policy, in order to persist the change to additional instances should the server get restarted... For non-persisted changes, the web UI uses the following method in the ACE Admin REST API:
    http://localhost:7600/apiv2/applications/{application}/messageflows/{messageflow}/update-thread-pool

    ... so you can make a temporary change programatically using the above if the web ui is not convenient for your needs.

    In general, our aims in this area were to preserve the options we had in previous releases, but with the move from IIBv10 to ACEv11, also simplify the process for policies (ie the separate steps of "deploy" and "attach" are no longer needed) ... this enabled us to gain greater consistency in the way that policies work for different purposes (not just work load management).

    Cheers,
    Ben


    ------------------------------
    Ben Thompson
    IBM UK
    ------------------------------

    Original Message


  • 4.  RE: How to change WLM Policy into a MQ Node in runtime

    Posted Wed June 01, 2022 03:51 PM
    Thanks, we are now applying temporary changes with user interface but we are planning how to persist changes. With Colin´s response we are going to set a plan for our purpuse.

    Regards

    ------------------------------
    David Bonilla
    ------------------------------

    Original Message


  • 5.  RE: How to change WLM Policy into a MQ Node in runtime

    Posted Wed June 01, 2022 03:48 PM
    Thank you for all information, we are going to proceed with this recomendation and hope a future fix comes with a fast and easy process as we did in IIB v10.

    Regards

    ------------------------------
    David Bonilla
    ------------------------------

    Original Message