Details
-
Enhancement
-
Resolution: Done
-
Major
-
7.3.0.GA
-
None
-
2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17)
Description
Today, when an unmanaged, immutable kieserver is connected to the Business Central, it successfully appears in the "Servers" page, under "Deploy".
But if one needs to start a new process instance from BC (or wish to perform any other task in the container), will need to create a new Deployment Unit manually.
This could be automatic since this information can be queried by BC using this endpoint:
/services/rest/server/containers
Here's a response example:
<response type="SUCCESS" msg="List of created containers"> <kie-containers> <kie-container container-id="rhpam-rewards" status="STARTED"> <messages> <content>Container rhpam-rewards successfully created with module com.redhat.demo.hr:rewards:1.0.0.</content> <severity>INFO</severity> <timestamp>2019-05-03T14:04:43.347Z</timestamp> </messages> <release-id> <artifact-id>rewards</artifact-id> <group-id>com.redhat.demo.hr</group-id> <version>1.0.0</version> </release-id> <resolved-release-id> <artifact-id>rewards</artifact-id> <group-id>com.redhat.demo.hr</group-id> <version>1.0.0</version> </resolved-release-id> <scanner status="DISPOSED" /> </kie-container> </kie-containers> </response>
The container-id can be mapped to the Deployment Unit name and the resolved-release-id element to the GAV parameters.
Please see this doc for more reference.
Attachments
Issue Links
- relates to
-
KIECLOUD-172 Monitoring console problems in rhpam-production-immutable environment
-
- Closed
-
