Integrating JaxView with Service Registries
About Service Registries
The use of service registries is ideally one of the core elements of
service-oriented architectures. Service registries provide a centralized location
from which service clients can discover what services are available in a particular
environment and how they can be accessed.
JaxView can be configured to automatically query a UDDI-compliant registry application
in order to retrieve service and policy information and update monitoring and
management settings. JaxView can then uses this information to automatically configure
settings that will allow JaxView to monitor service message traffic and enforce certain
runtime governance policies (when deployed as a service gateway).
JaxView can also be configured to publish service and governance
policy information to a registry. This allows JaxView to act as
a registry interface where service information can be entered using the JaxView
interface and published to the enterprise or other shared registry. It also
enables closed-loop governance between design time information entered directly to the
registry and runtime information entered or updated in production.
This section describes:
The following describes the property settings and options used to integrate
JaxView with an external service registry.
- Title:
- Enter a unique title for this registry object.
- Disable:
- Check this box to disable automated querying with this registry within JaxView.
- Registry Query URL:
- Enter the URL of the query manager service within the target registry provider.
For example: http://localhost:8080/uddi/inquiry.
- Publishing Service URL
- Enter the URL of the life-cycle manager service within the target registry provider.
This will be the service for registry updates.
For example: http://localhost:8080/uddi/publishing.
- UDDI Version
- Enter the version of UDDI to be used in all of the UDDI soap requests to this
registry. The default is UDDI version 2. Consult the documentation for the registry product for any special syntax
that must be used.
- Registry Check Interval
- Select how often you'd like the registry to be checked for new service and
policy objects. The choices are Every Hour, Every Six Hours, Every Twelve Hours or Every Day.
- Connection Factory Class
- Enter the string that specifies the path to any special connection factory
to be used for this registry. Use this option in case there are propietary connection
API's for the specific service registry to which you are connecting.
- Registry Username:
- Enter the username required for publishing information to the target registry.
- Registry Password:
- Enter the password for the username for publishing information to the target registry.
- Proxy Host
- If JaxView needs to access the registry through a proxy server,
enter the HTTP proxy host to be used for accessing the external registries.
- Proxy Port
- If necessary, enter the HTTP proxy port to be used for accessing external
registries. For example: 8080.
Service Auto Discover Settings
- WSDL TModel Key
- Either the Tmodel Key or TModel name for the WSDL information of the Web service
- Auto Discover Services
- Check this box to enable autodiscovery of new services in the registry
and have JaxView automatically add them to its service catalog.
WS-Policy Settings
- WS-Policy TModel Key
- This the UDDI TModel Key or TModel name for the WS-POLICY.
This may be the Remote Policy Reference. Please see WS-PolicyAttachment documentation
at the W3.org Web site.
- Load WS-Policies
- Check this box to have JaxView query the registry on a scheduled basis
and to create a new WS-Policy object in the JaxView
Admin tab with any new
policies that are found.
Service Performance Settings
- Performance TModel Key
- Either the TModel key or TModel name for the performance policies
in milliseconds. This number will be set as the error threshold for
performance monitors assigned to all of the operations for the service.
- Check Performance
- Check this box to have JaxView check for changes to the Web service
performance thresholds published in the service registry and to update
the service performance monitors
in JaxView with the new threshold values.
Monitors To Assign
Check the monitor instances in this list that you want to associate with
this registry. JaxView will automatically synchronize applicable service and
policy information for these monitors with the selected registry.
You use the action menu associated with the applicable service node in the
Services tab to publish information to a registry. Service information can be published to
more than one registry.
To publish service or policy information to a registry:
- Be sure that JaxView has been configured to connect to and publish to the applicable
registry application. See the Admin tab and the section
Configuring JaxView to Connect to Service Registries
for more information.
- Go to the Service tab in JaxView and click on the node for the service for which
you want to publish information to the registry.
- Use the right-click button to display the action menu for the service node.
- Select the Publish Policies to Reg option. The Publish to Registry page is
displayed in the right side window.
- Select the options in the Publish to Registry page for the information you want
to publish to the registry. Expand the subpanels on the page as needed to select
and configure the options as described in the sections below.
- Select the registry to which the information should be published from the
list of registries near the bottom of the form.
- Click the Publish button to complete the action.
Publish To Registry Options
The following describe the options for what service and policy information
can be published from JaxView to a service registry.
Publish Service To Registry
This subsection contains options for publishing the basic
information about the service to a registry
- Publish Web service to registry
- Check this box to publish service information about this Web service
to the registry associated with this service object.
- User information to use admin
- When publishing a service into a registry there needs to be a person
associated with the service. Use the drop down menu to select a JaxView user account
name to be associated with the service information published to the registry.
See the Users section in the Admin tab for more information on creating JaxView user accounts.
- Service Business Entity
- Enter the Business Entity or provider name in which the Web service should
be created. If this entity does not already exist in the target registry
then it will be created by JaxView.
- Publish service status to registry
- Check this box to publish a status report page for the service to registry
Publishing Endpoint URI
This section is used if you want to publish service endpoint information
for services of which JaxView is already aware. You also use this
option to publish virtualized service addresses when you have deployed
JaxView as a service gateway. If the virtual service address is defined
it will normally be listed as one of the options in the radio list in this subsection.
Click the radio button tothe left of the address
that you want to publish to the registry.
For example:
Publish the following Access URI to the registries checked below:
Monitor Thresholds
Use this section to select which monitor event thresholds you want to publish to
the registry. The table in this subpanel lists all of the monitor types assigned to
the operations for the selected service. Use the check box in the far right column of the
table to select the monitor event thresholds to be published. The following is an
example of the Monitor Threshold selection table:
Policies To Publish
Use this section to select the JaxView service
governance policies you want to publish to the registry.
Expand each subpanel as necessary and click on the checkbox to the right
of the policy title for each policy property you want to publish.
It is important to note that there are not widely adopted standards for
the format and syntax of several policy items. JaxView uses a policy
syntax that is meant to conform with guidelines used for WS-Policy.
You can view JaxView native policy XML by selecting a Web service node object
inthe Services tab and then clicking to view the Policies sub tab. The
Policies sub tab displays tables with the JaxView policy labels as hyperlinks.
Clicking on a hyperlinked label will display the XML policy statement for that
item in a new browser window.
The following lists the policy properties that can be
published to the registry. See the section
Applying Policies to Services in JaxView
for more information about policy definitions.
Request/Response Modification Policies
- Response Modification Expressions
- Modify Response With
- Response Mod Class Name
- Request Modification Expressions
- Modify Requests With
- Request Mod Class Name
Security Policies
Authenticate Clients
- Authenticate Client
- Username XPath/REGEX
- Password XPath/REGEX
Encryption/Decryption
- Decrypt Request
- Encrypt Response
Digital Signature
- Validate XML Digital Signature
Digital Certificates - Server Side Certificate
- KeyStore Path
- Key Password
- KeyStore Password
- SSL Port:
LDAP/AD Authentication
- Authenticate Clients Using LDAP/AD
- Enable LDAP Authentication checked
- LDAP Provider URL
- Security Principal
- Default Password
- Search Filter:
- Root DN
Web Service General Policies
General Policies
- Max Message Size
- JaxView Processing Server
- Service Daily Threshold
- Days to save messages
- Fault Element Name:
JMS Policies
- End Point ESB
- Topic Name
- Queue Name
Routing Policies
- Content Expression
- Block requests
- Response to client
- Routing URL
- Routing Schedule:
WS-Policies