Skip to Content

Changes for page Container management

Last modified by Danniar Firdausy on 2024/09/18 13:01
From version 9.10
edited by Danniar Firdausy
on 2024/09/04 16:18
Change comment: There is no comment for this version
To version 9.9
edited by Danniar Firdausy
on 2024/09/04 16:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,8 +16,8 @@
16 16  * Default behavior of new onramps and offramps is that these will be spread over all process containers. In some cases this desirable (2 containers - failover setup), but in some case one has to be specific and ensure the flows are put on the right process container
17 17  * In case a certain flow is made part of a release, but has not been assigned to any container than that release can't be set to active
18 18  * Entry and Exit flow are always put on the system specific container
19 -* Exit gate flows are always put on the gateway container
20 -* Event processors are always put on the streaming container
19 +* Exit gate flows are always put on the Gateway Container
20 +* Event processors are always put on the Event Container
21 21  
22 22  Please make sure that the maximum number of flows on any container is approx. 60 flows
23 23