Hello,
We are planning to use ServiceMix as a mediation framework between various
System and a Manager of Manager.
Our question concerns the packaging and deployment.
For integrating a System with the Manager of Manager we should have this
typical deployment of components:
System A -> a-in-BC -> a-in-SE ---------> MoM-in-SE -----> MoM-in-BC
--------> Manager Of Manager
System A <- a-inout-BC <- a-inout-SE <--- MoM-inout-SE <----MoM-inout-BC
<----- Manager Of Manager
So we plan to deliver a First common Service Assembly composed of:
MoM-in-BC + MoM-inout-BC + MoM-inout-SE + MoM-in-SE
For each type of System we plan to deliver a Service Assembly composed of:
xxx-in-BC + xxx-in-SE + xxx-inout-BC + xxx-inout-SE
For each BC we plan to define a configuration file for configuring the
endpoints according to the customer context (port number, system ip address,
....)
For integrating this Service Assembly on a production platform, the
integrator just need to fill the configuration file and deploy the Service
Assembly.
But how managing the case where we have multiple Systems of the same type to
integrate to the same Manager of Manager?
Indeed we cannot deploy another instance of the same Service Assembly. It
implies to make a new service assembly with a different name. This is not
possible during the integration phase.
There're some threads about dynamic endpoints, but I dont think it can help
in our context.
Do you have an idea?
Thank
Christophe
--
View this message in context:
http://www.nabble.com/Packaging-and-deployment-question-tf4561543s12049.html#a13018002
Sent from the ServiceMix - User mailing list archive at Nabble.com.
