JaxView: Service Mediation and SOA Message Brokering
An important part of SOA governance is to be able to appropriately route requests.
- Are requests being sent to the right Web service version?
- How is load managed and distributed across Web services?
-
Are exceptions handled gracefully?
Manage the Message Flow
JaxView acts as a network intermediary to enable runtime message mediation and content-based brokering for Web services. With JaxView you can:
- Easily integrate different systems
- Automate message routing rules by consumer type
- Manage throttling, load balancing, and failover
- Simplify and streamline exception handling
- Dynamically modify message schemas
Dynamic Message Modification and Protocol Conversion
Because services can be easily reused within a SOA environment, there may be instances when the consumer of the service doesn't necessarily send requests in a schema that is recognized by the provider. To prevent failures and deliver a robust SOA application, there must to be a way to dynamically modify a schema or a protocol so it can be immediately recognized by the provider. With JaxView you can:
- Dynamically modify the schema of the request or the response by using xsl transformation
- Dynamically modify the schema by writing a proprietary algorithm to perform the modification
- Convert from http -> jms -> http or jms -> http -> jms protocols depending on your provider's protocol of choice
- Create adapters for other protocols to perform the conversion
JaxView Features for SOA Message Brokering
When deployed as a service proxy, JaxView can be used as a policy enforcement point for centralized runtime governance of service-oriented environments. JaxView can also deploy small agents on the application server to enforce policies. Both deployment options include the following capabilities:
Runtime Service Mediation and Brokering Functions
Use JaxView as a network intermediary to enable runtime service mediation and message brokering. With JaxView you can:
- Modify service messages in runtime to mediate between different systems
- Reroute service requests in runtime based on content checking rules such as service version
- Convert SOAP service requests to the JMS protocol and forward them to an ESB
- Create new protocol conversion mechanisms with the Open API
- Set exception based routing and automate runtime exception handling to route messages to available services and provide exception response messages
- Throttle messages to allow only a specific number of messages to reach the service in a specific period of time
- Provide load balancing and failover support
Runtime Policy Enforcement Functions
Use the JaxView service proxy deployment option to combine enforcement of automated policies on service access and usage with visibility into policy compliance. JaxView enables you to:
- Block access to individual service operations based on time of day or date
- Create and manage WS-Policy assertions using JaxView's internal repository and WS-Policy tools
- Automatically update service and policy information from a UDDI-compliant registry
- Monitor for policy compliance and compliance failures
- Set daily or hourly limits on the number of service requests that are forwarded
- Block service messages that exceed a certain size
- Throttle messages
- Apply protocol conversion (i.e.: JMS ->HTTP or vice versa) with an open API for all protocol customization
Closed-loop Service and Policy Management Functions
Increase efficiency in managing services and runtime policies by integrating JaxView with a UDDI service registry. JaxView's bi-directional registry synchronization capability lets you:
- Automatically query the service registry and update service information
- Automatically configure new service monitoring configurations in JaxView by querying a service registry
- Automatically query the service registry and update JaxView policy implementations
- Create, update and manage policies through the JaxView interface
- Export JaxView policy implementations as WS-Policy-complaint assertions to a UDDI registry
- Automatically update the service registry with service information and policy changes made using the JaxView interface
Web Service Policy Profiles
Create a set of Policy profiles and assign them to a group of services as they are discovered. You can:
- Create policy profiles once and assign to a group of Web Services
- Assign multiple policy profiles to a Web Service. As an example you can have one set of policies for internal consumers of the service and another set for external consumers of the service.
