Enabling packages

Enabling a package activates its services and assets, making them available for execution. This option applies to both main packages and custom packages.

Before you begin

Make sure that all dependent packages are properly loaded and enabled before the main package is enabled to avoid disruptions. If not, the main package is automatically disabled. For more information, see Reloading packages.

About this task

When you enable a package, the runtime replica runs any startup services that are defined in the package. Services become available for clients, triggers, or other packages. Listeners and connectors (for example, JDBC, JMS) are initialized.

Disabling a package stops its services from being run, but it might still be loaded. If a package is disabled, then you cannot view the assets, and the project does not work as expected. A package can be disabled under several conditions, such as,
  • When an administrator manually disables it for purposes such as maintenance or updates.
  • When dependency issues arise, for instance, required packages are missing or the package relies on another package that is not currently loaded or enabled.
  • When deployment conflicts occur during package version updates. These conflicts might occur when an update introduces changes that affect dependent packages.
These conflicts can prevent successful deployment and might result in the package being disabled until the issues are resolved.

Procedure

  1. Go to Projects > Packages.
  2. To know more about the issues, click the package name.
    The package details are displayed.
  3. Resolve the issues and save the package. The issues related to custom packages can be resolved in the on-premises environment before the package is exported and uploaded to the cloud.
    For example, your custom package OrderProcessingPkg fails to enable in cloud due to a missing dependency OrderValidator. If a dependency is missing, you can add the required package to your cloud project. If any logic needs to be updated, open the package in IBM webMethods Designer, make the necessary changes, rebuild the service, and test it locally. After verification, you can upload the updated package. These packages can be saved to an external repository and pulled into your cloud project as needed. After the pull, the packages are loaded into the Cloud Designtime environment.
  4. Click Enable.
    The package is enabled and ready for use in integrations.
    Note: Enabling a package does not cause its associated custom packages to be reloaded.