6 SOA Solutions Using IBM Information Server
IBM Information Server. By eliminating duplication of functions, the architecture
efficiently uses resources and reduces the amount of development and
administrative effort that are required to deploy an integration solution.
In the following sections we briefly describe each of these components:
򐂰 Unified user interface
򐂰 Common services
򐂰 Key integration functions (understand, cleanse, transform and move, deliver)
򐂰 Unified parallel processing
򐂰 Unified metadata
򐂰 Common connectivity
1.2.1 Unified user interface
The unified user interface enables an organization’s entire user community of
business users, subject matter experts, architects, data analysts, developers,
and database administrators (DBAs) to collaborate, administer, and query
information within the enterprise. A security infrastructure ensures that users are
permitted to access information and perform tasks for which they are authorized.
The face of IBM Information Server is a common graphical interface and tool
framework. Shared interfaces such as the IBM Information Server console and
Web console provide a common look and feel, visual controls, and user
experience across products. Common functions such as catalog browsing,
metadata import, query, and data browsing all expose underlying common
services in a uniform way. IBM Information Center provides rich client interfaces
for highly detailed development work and thin clients that run in Web browsers for
administration. Application programming interfaces (APIs) support a variety of
interface styles that include standard request-reply, service-oriented,
event-driven, and scheduled task invocation.
The three broad user interface categories are the analysis interface,
development interface, and Web Admin interface as shown in Figure 1-1 on
page 5.
1.2.2 Common services
IBM Information Server is built entirely on a set of shared services that centralize
core tasks across the platform. These include administrative tasks such as
unified service deployment, security, user administration, logging, and reporting.
The common services provides flexible, configurable interconnections among the
many parts of the architecture.
Chapter 1. IBM Information Server architecture 7
Shared services allow these tasks to be managed and controlled in one place,
regardless of which product module is being used. The common services also
include the metadata services, which provide standard service-oriented access
and analysis of metadata across the platform. In addition, the common services
layer manages how services are deployed from any of the product functions,
allowing cleansing and transformation rules or federated queries to be published
as shared services within an SOA, using a consistent and easy-to-use
The common services layer is deployed on J2EE-compliant application servers
such as IBM WebSphere Application Server.
IBM Information Server products can access four general categories of service:
design, execution, metadata, and unified service deployment, which we discuss
in the following sections.
Design services
Design services help developers create function-specific services that can also
be shared. For example, WebSphere Information Analyzer calls a column
analyzer service that was created for enterprise data analysis but can be
integrated with other parts of IBM Information Server because it exhibits common
SOA characteristics.
Execution services
Execution services include logging, scheduling, monitoring, reporting, security,
and Web framework:
򐂰 Logging services help you manage logs across all of the IBM Information
Server suite components. The Web console shown in Figure 1-2 provides a
central place to view logs and resolve problems. Logs are stored in the
common repository, and each IBM Information Server suite component
defines relevant logging categories.
You can configure which categories of logging messages are saved in the
repository. Log views are saved queries that an administrator can create to
help with common tasks. For example, you might want to display all of the
errors in DataStage jobs that ran in the past 24 hours. Logging is organized
by server components. The Web console displays default and active
configurations for each component.
Attention: Today, common services are consumed exclusively by the various
components of IBM Information Server. These common services are currently
not exposed as public SOA services, and therefore cannot be invoked by
applications or tools.
8 SOA Solutions Using IBM Information Server
Figure 1-2 Web console for setting up logs
򐂰 Scheduling services help plan and track activities such as logging and
reporting, and suite component tasks such data monitoring and trending.
Schedules are maintained using the IBM Information Server console shown in
Figure 1-3, which helps you define schedules, view their status, history, and
forecast, and purge them from the system.

Get SOA Solutions Using IBM Information Server now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.