Show Table of Contents
10.5. Managing Containers
Containers within the Realtime Decision Server can be started, stopped, updated from within Business Central.
Starting a Container
Once registered, a Container is in the 'Stopped' mode. Click
to select the Container, then click . You can select multiple Containers and start them all at the same time.
to select the Container, then click . You can select multiple Containers and start them all at the same time.
Once the Container is in the 'Running' mode,
appears next to it.
appears next to it.
In case of errors,
appears next to Container(s) and the Realtime Decision Server that they are deployed on. For troubleshooting, check the logs of both the Realtime Decision Server and the Business Central before redeploying the Containers.
appears next to Container(s) and the Realtime Decision Server that they are deployed on. For troubleshooting, check the logs of both the Realtime Decision Server and the Business Central before redeploying the Containers.
Stopping and Deleting a Container
Click
to select the running Container(s) and or .
to select the running Container(s) and or .
Updating Container Deployments
You can update deployed Containers without needing to restart the Realtime Decision Server. This is useful in cases where the Business rule changes cause new versions of packages to be provisioned.
You can have multiple versions of the same package provisioned and deployed.
To update deployments in a Container dynamically, click
next to the Container. This opens up the Container Info screen:
next to the Container. This opens up the Container Info screen:
The Container Info screen allows you to see the endpoint for the Container (for example, http://localhost:8080/kie-server/services/rest/server). You can also either manually or automatically refresh the Container if an update is available.
- Manual Update: To manually update a provision, enter the new Version number in the Version box and click . You can update the Group Id or the Artifact Id, if these have changed as well.
- Automatic Update: If you want a deployed Container to always have the latest version of your deployment without manually editing it, you need to set the Version property to the value of
LATESTand start a Scanner. This will ensure that the deployed provision always contains the latest version. The Scanner can be started on demand by clicking or you can start it in the background with scans happening at a specified interval (in seconds).You can also set this value toLATESTwhen you are first creating this deployment.The Resolved Release Id will show you the actual, latest version number. Note that if the Resolved Release Id is empty, this is an issue not influencing the functionality of the upgrade feature.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.