Skip to Main Content
Integration


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.


Status Submitted
Created by Guest
Created on Oct 21, 2025

Allow webMethods Deployer (WDY) skip reloading dependent packages while deploying a package X

So, let’s say I have a package X with three other packages depending on it:

Package A depends on X
Package B depends on X
Package C depends on X

In a scenario where we’re deploying a new version of X — for example, a minor fix or a library upgrade with no functional impact on A, B, or C — it seems there is currently no way to deploy only X without triggering automatic reloads of its dependent packages.

As soon as package X is installed, all dependent packages (A, B, C in this case) are automatically reloaded.

While this is manageable with just a few packages, in our real-world environment we often have 20–30 packages depending on a common core package. This means each dependent package goes through its shutdown and startup services, causing significant delays and in some cases even timeouts, depending on server load.

Would it be possible to consider introducing a flag or setting in Deployer that allows us to skip the reload of dependent packages when desired?

This would greatly reduce deployment time for non-breaking changes. Also the biggest aim is to use this on CI/CD pipelines for non-prod environments.

Our current workaround for critical packages that are part of our common framework (and which have more than 30 packages depending on) we opt for doing a full server shutdown and install the package offline.

Idea priority Urgent