JaxView is a
scalable service policy enforcement and SOA management solution for organizations
transitioning to Web services and for mature service-oriented architectures.
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. The JaxView agent will be a generic handler on the J2EE application servers and a .Net extension on the .Net servers.
Both deployment options include the following capabilities:
Security Proxy and XML Firewall Functions
Use JaxView as a service proxy or network intermediary component to enable centralized security for Web services to save implementation time and ease security management. In this mode allows you to use JaxView to:
- Authenticate users against LDAP and Identity Management Services
- Token Mapping using Secure Token Service (STS) using WS-Trust
- Handle incoming and outgoing SSL/TLS handshakes
- Support connections using X.509 certificates or Kerberos
- Encrypt or decrypt XML message content
- Validate XML digital signatures and WS-Security headers
- Block non-compliant service requests based on message content
- Support for WS-Security headers
Runtime Service Mediation and Brokering Functions
Use JaxView as a network intermediary enable runtime service mediation and message brokering. JaxView enables you to:
- Modify service messages in runtime to mediate between different systems
- Reroute service requests in runtime based on content checking rules such as service version
- Protocol conversion. Convert SOAP service requests to the JMS protocol and forward them to an ESB. Open api for creating new protocol conversion mechanisms.
- Exception based routing. Automate runtime exception handling to route messages to available services and provide exception response messages
- Throttling of messages to allow only a specific number of messages to reach the service in a specific period of time
- 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
- Throttling of messages
- Protocol conversion Ex: JMS to HTTP or vice versa. 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. Use JaxView's bi-directional registry synchronization capability to:
- 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
Be able to create a set of Policy profiles and assing them to a group of services as they are discovered.
- Create policy profiles once and assign to a group of Web Services
- Assing mulitple policy profiles to a Web Service. As an example you can have a set of policies for internal consumers of the service and another set for external consumers of the service.


