ZS805 Unit03 Script
ZS805 Unit03 Script
Unit objectives
After completing this unit, you should be able to:
• Identify the key components of web UI layout and explain their purpose
• Explain how to use the web UI to manage various types of service
metadata
• Manage configuration profiles through the configuration perspective
• Configure Business Space widgets to work with service metadata
After completing this unit, you should be able to identify the key components of a Web UI layout
and explain their purpose. Explain how to use the web UI to manage various types of service
metadata. Manage configuration profiles through the configuration perspective. Configure
Business Space widgets to work with service metadata.
Topics
• Web user interface
• Business Space
The web user interface, or Web UI, provides administration features from a web application.
In your web browser, open http://<hostname:port>/ServiceRegistry/
If application security is enabled, clients must log in with a user in the WebSphere Service
Registry and Repository user or administrator role.
1 2
5
3 4
© Copyright IBM Corporation 2012
The web UI home page provides quick access to entities according to type, applied classification,
or a previously saved search.
List all business objects (concepts) by type.
Start a previously saved search by name.
Retrieve a list of all physical documents by type.
Retrieve a list of all logical objects by type.
Search all entities with a specific classification.
The bottom half of the home page includes a widget for loading service documents.
6
© Copyright IBM Corporation 2012
The load documents widget and help links are on the bottom half of the home page.
The load documents widget uploads one service document and specifies the mandatory
description and version fields. The name and namespace fields are taken from the document.
The Help and Web Resources panes link to the product page, information center, and support
pages on IBM.com.
The About pane displays the version and build of Service Registry and Repository.
Loading documents
• All document dependencies must be resolved before Service Registry
accepts the new document
– For example, if a WSDL document imports an XML schema document, the
referenced file must exist in Service Registry as well
• Documents already in the registry are proposed as dependency
resolution candidates
– Users have the option of removing or replacing the suggested files
All document dependencies must be resolved before Service Registry accepts the new
document. For example, if a WSDL document imports an XML schema document, the referenced
file must exist in Service Registry as well.
Documents already in the registry are proposed as dependency resolution candidates. Users
have the option of removing or replacing the suggested files.
Remember to select Finish to create the three new service document entities: account business
object, account creation schema, and account creation service interface.
Auto-suggest results
Candidates that match
your search text are
listed in the menu, with
the number of results
for the string
In the upper right corner, the search field finds every entity with the string in its name. The auto-
suggest feature lists search hits as you type. This feature is available by default, and can be
disabled through preferences.
The auto-suggest results returns candidates that match your search text are listed in the menu,
with the number of results for the string.
10
11
1. Enter in the
1
query
parameters
2. Include child
classifications
in the search
3
3. Manage the
classification
list
12
Select Add from the classification field in the query wizard to open the classifications selector. It
has three main parts.
In the classification tree, select one or more classifications to apply.
Click Add to include the selected classifications with the query. For more information
about each classification, select the class to view the classification system, name, and
OWL URI.
Click OK to return to the query wizard.
13
The last page of the query wizard reviews your property. Click Finish to start the query.
14
The query wizard displays the property search results in a collections view. In this example, there
are three WSDL Service logical objects with the name that starts with "Account".
Filter the results by governance lifecycle states, relationships, and properties.
Provide a name for the query to save the search for future use.
15
Collections view
2 3
© Copyright IBM Corporation 2012
Another way to examine service metadata entities is by browsing through a collection by type. In
this example, the WSDL Documents collection lists all physical documents that represent WSDL
files.
The collections toolbar contains actions that can be applied to an entity, such as deleting, adding
metadata, exporting as files, subscribing, and adding to favorites. Load document starts the load
documents wizard.
To view more information about the entity, click its name to examine it in the details view.
The Graph icon examines the relationships between the selected entity and other entities in
Service Registry.
16
Details view
The details view lists all the metadata that is associated with a service description entity. The
layout differs depending on the entity type.
General Properties lists fields common to all entities, including name, namespace, description,
and owner. These fields are set at entity creation and cannot be modified.
User-defined properties and other type-specific fields are listed in Additional Properties. In this
example, the XML namespaces that are defined in the WSDL document are listed in this section.
Edit Properties, Edit Relationships, and Edit Classifications are links for adding and
modifying properties, relationships, and classifications.
The Service Metadata section lists links to logical objects linked to the document.
Relationships list relationships to related entities. Select the name to open the document in the
outbound relationship.
17
To retrieve a copy of the original document from the repository, select the Content tab.
Select Download Document to retrieve a copy of the document in its entirety.
18
10
9
Impact analysis graphs the dependencies between entities. You can use these graphs to
examine possible side effects from modifying the current entity. For example, deleting an XML
schema document affects all WSDL documents that depend on it.
Three options are available: show all outbound relationships, all inbound relationships, and all
relationships. The Dependency depth setting limits the maximum level of traversals in case of
circular relationships between entities.
Select any number of relationship types to include in the impact analysis graph.
Choose a custom relationship according to the name, as defined in the business object OWL
definition.
19
The impact analysis graph uses vector graphics to dynamically draw entities and relationships.
The graph lists the Name and Type of each service entity. Hover your mouse cursor over an
entity to view common entity properties, including its bsrURI.
For large graphs, move the viewing window to move around the graph.
Apply an Action over the selected entity. Quickly add a property, a relationship, or a classification
on the object. Use the Refocus Graph action to redraw the graph around another entity.
Use the List to quickly view and jump to an entity in the graph. Change the dependency depth of
the graph in Options. History lists the previous actions.
20
Business Space
Business Space.
21
Business Space is a user interface framework for aggregating content in a web browser.
Within the framework, a business space is a collection of web content for a particular business
task or role.
The Business Space web application contains multiple spaces, each with one or more pages.
Each page consists of a collection of widgets. Widgets can interact with each other using events.
Business Space is not a stand-alone product; it is a feature available in IBM software products as
a standardized graphical user interface.
22
23
The Business Space interface provides a cleaner, more task-oriented interface that is designed
for users. While the web UI provides a full breadth of functions, the Service Registry Business
Space widgets provide more task-oriented features.
The list of objects depends on the widget settings. In this example, the SOA governance role has
a quick way to see all approved business capabilities.
Watch List provides a list of entities in a governance state that needs approval from the current
role. Your role depends on the user ID that you used to log on to Business Space.
Service Registry Actions lists the actions specific to the role. The actions that are listed are
configurable through the widget settings.
The Service Reuse widget lists the amount of reuse in business objects. In this case, there are
no registered consumers for the current service. Although reuse level is not part of the
governance process, architects can use this high-level view for a better understanding of the
health of services in the entire organization.
24
The Load Documents action in Business Space provides the same features as the Load
Documents wizard in the web UI.
Load a service description document from the local file system or on a remote web server.
The location of the document is a required field.
When you select automatically detect document type, the action determines the file type
according to the file extension.
Provide a description and version number for the document.
25
Before the wizard loads the service description document into Service Registry and Repository,
you must resolve any dependencies to other documents. If a matching document exists in
Service Registry and Repository, the wizard resolves the dependency for you. If it does not exist,
you must load the matching document by selecting Add.
To change the description or version number on any of the documents, select Describe.
To add another document to Service Registry and Repository, select Add Another Document.
26
• Lock collection
views to restrict
any changes to
the items that are
listed
The Service Registry collection widget displays a table of service metadata entities.
You can configure collections on a per-type basis. You can also configure custom views by
selecting specific properties and relationships in the collection.
To restrict changes to the collection settings, lock the collections view. For example, a watch list
is a locked collection view of items that need your attention.
27
4
© Copyright IBM Corporation 2012
Business Space administrators can edit and customize widget settings. Select the View Menu to
define a custom collection of entities.
Through the view menu display settings, customize the entity metadata that are listed in the
columns.
Select the View Menu to edit the list of custom collection views.
The collection widget also supports a list of built-in entity types. Certain items are not specific to
Service Registry: Application Server, Application Server Cluster, and Computer System.
Select one of the custom menu items by name to edit its settings.
To create a custom collection view, select Add menu item.
28
2 3
In this example, the Watch List custom collection view shows business model objects in lifecycle
states that require approval from a user in the SOA governance role.
Provide a name and description for the collection view type.
Define queries that populate the collection view with entries. In the first item, this collection view
lists Business Capabilities marked with the lifecycle state classifications of Identified,
Deprecated, Rejected, Retired, and Charter Review.
Apply other classifications and properties to further refine the search results.
Select Add Query to search for entities, by either the entity type or a custom XPath expression.
29
Users can view details from a list of Service Registry entities in the Browse page.
Select an object from the Service Registry Collection widget.
View the relationship between service metadata entities by using the Service Registry Navigator
widget.
Manage properties, classifications, and relationships on entities by using the Service Registry
Detail widget.
View all previous changes by using the Service Registry Activity widget.
30
• Manage properties,
classifications, and
relationships by using
Edit
The Service Registry Detail widget is highly customizable, designed to list the most essential
information that the user role uses to accomplish a task.
In this example, the SOA governance role receives an approved account creation service.
Architects can deprecate a service capability by using Action. To create a service version that is
based on the capability, select Edit.
31
You can manage entity properties, relationships, and classifications with the Edit view. You can
also create other entities that are related to the current entity.
For example, you can create a capability version that is related to the current service capability.
32
Administrators can select which properties to show in the Display widget, on an entity-to-entity
basis:
Configure visibility of service metadata
Configure which operations to show in the Actions menu
Edit metadata
Show custom properties and relationships
Add custom queries as relationships to show reverse relationships
33
The Graphical Explorer widget maps the relationships between entities in Service Registry. Its
icons reveal the entity type at a glance, along with the entity name and type below the icon. Use
the slider on the upper right corner to zoom in and out of the diagram. Move the rectangle within
the mini-map to explore the rest of the relationships in the graph.
34
With Service Registry widgets, you can view, modify, and manage service metadata in
WebSphere Service Registry and Repository.
The approved business capabilities collection lists business capabilities that a developer can
implement as a service. The watch list displays entities that require the attention of a particular
role: a business analyst, an architect, a service developer, or a system administrator. The
actions widget lists the WebSphere Service Registry and Repository operations that you can
issue. The details view displays properties, relationships, and classifications specific to a role.
The search, navigator, and graph widgets allow you to quickly search through a list of entities.
For the service governance role, the governance policy enforcement and effectiveness details
list how many policies are attached to deployed service.
To determine the percentage of services that comply with the WS-I Basic Profile, use the WS-I
Basic Profile compliance graph.
To view the list of all available widgets for Service Registry, log on to Business Space as an
administrator and select Edit Page.
35
Unit summary
Having completed this unit, you should be able to:
• Identify the key components of web UI layout and explain their purpose
• Explain how to use the web UI to manage various types of service
metadata
• Manage configuration profiles through the configuration perspective
• Configure Business Space widgets to work with service metadata
36