Reloading packages
Package loading refers to the process by which the runtime replica loads a package's contents (like services, configurations, and metadata) during startup. A loaded package is not necessarily enabled.
Before you begin
About this task
When you load a package, the runtime replica reads the package directory and loads metadata, services, and configuration files into the memory. Loaded packages are not yet active for execution. Make sure that the dependencies are resolved before the package is added.
A package can be reloaded under several conditions, such as,
- If you updated any services or configuration files in the on-premises environment and reexported the package, reloading the package makes sure that the recent changes are applied.
- If the startup services failed, then reloading restarts any defined startup services and reinitializes resources if any.
- If a dependent package is reloaded, all packages that depend on it are also reloaded automatically to maintain consistency.
- If memory refresh issues occur, then reloading clears the current package from memory and loads a fresh copy.
Note: Reloading system packages such as wm* in a production environment is not recommended as it
might disrupt running services.
Note:
Procedure
Results
You can enable the disabled packages. For more information, see Enabling packages.
Verify Package Status
- Go to . The Package information page is displayed.
- Confirm that the package is loaded and enabled.
- Check for any error messages or warnings.
Validate dependencies
- From the Package information page, verify that all dependent packages are also loaded and enabled.
- Check for missing services or shared resources.
Inspect connector connections
- From the Connections page, recheck JDBC, JMS, or other connector connections.
- Make sure that they are active and properly configured.
Review Logs
- View logs to identify runtime errors or warnings.
- Focus on package-specific logs and system logs.