HTTP Proxy for runtime monitoring discovery
In EasySOA Registry 2.0, the HTTP Proxy is now part of the release. But did you know its management web interface prevents users from stepping on each other’s feet by forbidding to use it at the same time to discover services in different projects ?
This web page displays all configuration properties of the service discovery probe within the EasySOA Proxy. For instance, it says on which port on which host service exchanges are listened to. But it especially displays properties defining where discovered services are registered : in which context (SOA Project and Phase, here respectively Intégration DPS – DCV and Deploiement) and in which environment (here, Production).
These properties are filled when the user (here, Administrator) clicks on “Service Discovery by Runtime monitoring” buttons in EasySOA Registry. For instance, when the user clicks on it in the Service Browsing UI of a service deployment (endpoint), it is filled by this service deployment’s Project and Phase, and from now the Proxy can only be asked to discover services from the same User, Project and Phase, at least until the Proxy configuration is explicitly reset.
At the end, what’s actually interesting to users is obviously that all those Probe configuration properties make it in the registry (save User which is soon upcoming) and appear there on discovered service deployments and service consumptions that the Proxy registers when it sees a message exchange corresponding to a service call from a consumption host to a deployment url, along service- and exchange- specific information extracted from this monitored flow.
Note that there is a single instance of the Proxy, though allowing to create new ones on demand is in the works. Technically, this is being done by making out of the Proxy an OW2 FraSCAti Studio generated template application.