PrathibaJee
commented
1 year ago (Including the points we discussed over email) Pre-configuring the application-name of the http-server will make all instances of MIM work perfectly in the current design of ApplicationPattern. For example ,
- MIM application source code will have a http-server-capability/application-name(example: XXXMediatorInstanceManager)
- Before deploying the MIM application , we shall modify the http-server-capability/application-name either manually or by using a script(example: XXXMediatorInstanceManagerInstance1)
- This will make each instance of MIM application unique in the environment and solve the problem.
Another proposal : Introducing an optional configurable attribute in http-server-configuration/instance-name to differentiate different instances of a same application. So that the application-name shall remain as designed and a TypeApprover(Human) can identify an application easily.
openBackhaul
MediatorInstanceManager(MIM) is the REST layer(NBI) of the mediator VM. For example , if a vendor has 3 mediator VM in the environment , then in all the 3 VMs, same application with same version of MIM will be up and running.
As per the current application pattern , we cannot hold difference instance of a same application(with same version) in the CONFIGfile. Since MIM is the REST layer of a mediator vm, in the application layer can we manage the MediatorInstanceOrchestrator(MIO) and not the MIM.