mediator architecture question

, ,
1

I would like to verify the following architecture for Mediator.

We have 2 clustered Integration Servers in two different hosts. We are proposing to install a clustered two node mediator in these two hosts. These mediators will NOT be installed in the existing Integration Servers. I have following quesitons

  1. Should the mediatorevents db component be installed where the existing ISCoreAudit db schema is installed, which is being shared by the clustered Integration Servers? or Should the mediators have it’s own separate schemas where we will install ISCoreAudit and mediatorevents components.

  2. Load balancers in front of the mediator will pass in the webservices requests to one of the two mediators in the environment. Should we route the requests from the mediator to the Integration Server back to the loadbalancer to be forwarded to one of the Integration Servers? or use mediator to choose one of the Integration Servers?

–
Tanveer

2

  1. This db connection is only needed if you have the LogInvocation policy (configured with Audit Log destination) with your virtual service. You have to configure the IS hosting Mediator Audit Logging to write to database also. If your IS/Mediator is writing Audit Log to file, this db connection is not needed either. Therefore, all the configuration/connection should be done on the Mediator/IS, not the IS hosting your native service.

  2. Note that when you have a Mediator cluster, a virtual service deployed to Mediator cluster members has exactly the same contents (and the same routing address). Therefore, if you want it to forward requests to the exactly the IS running on the same host, then you have to use “localhost” in straight through routing. In that case, the LB routes a request to Mediator instance, which in turn forwards the request to the IS on the same host. You would not need to configure VS to route the request to the LB. However, the short coming of this is you need to make sure the IS instance on the same host is always running and you lose the benefit of the load balance among these two IS when some of the requests overwhelm one specific IS instance. Therefore, it is suggested that you configure VS to foward to LB (not necessary to be the same LB in front of Mediator), when your native service provider is clustered. Another alternative is that you configure VS to use load balance routing (to utilize both ISs hosting the native service) without a LB between Mediator and nattive service hosting IS.