KM510 Course Guide PDF

Preface
November, 2015
NOTICES
This information was developed for products and services offered in the USA.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to
state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any
non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
United States of America
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of
those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information
concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the
examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and
addresses used by an actual business enterprise is entirely coincidental.
TRADEMARKS
IBM, the IBM logo, ibm.com and InfoSphere® are trademarks or registered trademarks of International Business Machines Corp., registered in
many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is
available on the web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.
Adobe, and the Adobe logo, are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other
countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
© Copyright International Business Machines Corporation 2015.
This document may not be reproduced in whole or in part without the prior written permission of IBM.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
© Copyright IBM Corp. 2007, 2015 P-2

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Preface
Contents
Preface .................................................................................................................. P-1
Contents .............................................................................................................. P-3
Course overview .................................................................................................. P-8
Document conventions ........................................................................................ P-9
Additional training resources ............................................................................. P-10
IBM product help................................................................................................ P-11
Information Server technical overview ................................................ 1-1
Unit objectives ..................................................................................................... 1-3
Information Server functional categories ............................................................. 1-4
IS products support these functional categories .................................................. 1-5
Role-based tools with integrated metadata ......................................................... 1-6
Topic: Data quality products and components ..................................................... 1-7
Information Analyzer ............................................................................................ 1-8
QualityStage functionality .................................................................................... 1-9
Why data cleansing with QualityStage is needed .............................................. 1-10
Topic: Data governance..................................................................................... 1-12
Information Governance Catalog ....................................................................... 1-13
The Information Governance Catalog (IGC) ...................................................... 1-14
Stewardship Center ........................................................................................... 1-15
Topic: Transformation ........................................................................................ 1-16
Using Information Server to transform data ....................................................... 1-17
DataStage .......................................................................................................... 1-18
FastTrack ........................................................................................................... 1-19
Topic: Delivery ................................................................................................... 1-20
Information Services Director ............................................................................ 1-21
Topic: Information Server Architecture .............................................................. 1-22
Information Server architecture ......................................................................... 1-23
Information Server backbone............................................................................. 1-24
Parallel processing engine................................................................................. 1-25
Information Server architectural tiers ................................................................. 1-26
Architecture diagram.......................................................................................... 1-27
Platform topologies ............................................................................................ 1-29
Client tier............................................................................................................ 1-30

Preface
Services tier ....................................................................................................... 1-31

Engine tier.......................................................................................................... 1-32
Repository tier.................................................................................................... 1-33
Tier interaction ................................................................................................... 1-34
Apply your knowledge........................................................................................ 1-35
Unit summary..................................................................................................... 1-39
Working with Information Server clients ............................................. 2-1
Unit objectives ..................................................................................................... 2-3
Information Server Client-Server architecture ..................................................... 2-4
Information Server client icons ............................................................................ 2-5
Topic: Thin clients ................................................................................................ 2-6
Information Server launch pad............................................................................. 2-7
Logging into thin clients ....................................................................................... 2-8
Administration Console ........................................................................................ 2-9
Console administrative tasks ............................................................................. 2-10
Metadata Asset Manager................................................................................... 2-11
Repository Management tab.............................................................................. 2-12
Information Governance Catalog ....................................................................... 2-13
Example Category hierarchy ............................................................................. 2-14
Topic: Engine clients.......................................................................................... 2-15
Engine clients .................................................................................................... 2-16
DataStage administrative tasks ......................................................................... 2-17
Logging into DataStage Administrator ............................................................... 2-18
DataStage Administrator Projects tab ................................................................ 2-19
DataStage designer tasks.................................................................................. 2-20
Logging into Designer ........................................................................................ 2-21
Designer work area............................................................................................ 2-22
DataStage Operations Console ......................................................................... 2-23
Operations Console ........................................................................................... 2-24
FastTrack ........................................................................................................... 2-25
FastTrack data source configuration ................................................................. 2-26
Multi-Client Manager.......................................................................................... 2-27
Topic: Information Server console clients .......................................................... 2-28
Information Server console ................................................................................ 2-29
Analysis Engine settings .................................................................................... 2-30
Analysis database settings ................................................................................ 2-31
Demonstration 1: Working with Information Server clients ................................ 2-32
Unit summary..................................................................................................... 2-45

Preface
Authentication and Suite Security ........................................................ 3-1

Unit objectives ..................................................................................................... 3-3
Topic: Information Server user configuration ....................................................... 3-4
Assigning roles for access control ....................................................................... 3-5
Suite roles ............................................................................................................ 3-6
Suite Component roles ........................................................................................ 3-7
Creating IS users and groups .............................................................................. 3-8
Creating a new group .......................................................................................... 3-9
Selecting group attributes and roles .................................................................. 3-10
Creating a new user........................................................................................... 3-11
Specifying user attributes .................................................................................. 3-12
Topic: Credential mappings ............................................................................... 3-13
Credential mappings .......................................................................................... 3-14
Default credential mapping ................................................................................ 3-15
Specify the default credential mapping .............................................................. 3-16
User credential mappings .................................................................................. 3-17
Individual credential mappings .......................................................................... 3-18
Demonstration 1: Authentication and Suite Security ......................................... 3-19
Unit summary..................................................................................................... 3-26
Session management ............................................................................ 4-1
Unit objectives ..................................................................................................... 4-3
Client session management ................................................................................ 4-4
Viewing active client sessions ............................................................................. 4-5
Global session properties .................................................................................... 4-6
Session details..................................................................................................... 4-7
Disconnecting sessions ....................................................................................... 4-8
Demonstration 1: Session management .............................................................. 4-9
Unit summary..................................................................................................... 4-13
Managing reports ................................................................................... 5-1
Unit objectives ..................................................................................................... 5-3
Reporting administration ...................................................................................... 5-4
Creating a new report folder ................................................................................ 5-5
Creating a report .................................................................................................. 5-6
Selecting the report template ............................................................................... 5-7
Editing the report ................................................................................................. 5-8
Viewing a list of your reports................................................................................ 5-9
Report results .................................................................................................... 5-10
Report access control ........................................................................................ 5-11
Demonstration 1: Managing reports .................................................................. 5-12
Unit summary..................................................................................................... 5-19

Preface
Administrative tools ............................................................................... 6-1

Unit objectives ..................................................................................................... 6-3
Topic: Session management using SessionAdmin .............................................. 6-4
SessionAdmin tool ............................................................................................... 6-5
Running the SessionAdmin command ................................................................. 6-6
Listing active sessions ......................................................................................... 6-7
Killing active sessions .......................................................................................... 6-8
Topic: User management using DirectoryCommand ........................................... 6-9
Directory Command tool .................................................................................... 6-10
Running the DirectoryCommand command ....................................................... 6-11
Listing users and groups.................................................................................... 6-12
Creating users ................................................................................................... 6-13
Topic: Encrypt passwords using the Encrypt command .................................... 6-14
Encrypt command .............................................................................................. 6-15
Encrypt command example ............................................................................... 6-16
Creating a credentials file .................................................................................. 6-17
Example using command with credentials file ................................................... 6-18
Demonstration 1: Administrative tools ............................................................... 6-19
Unit summary..................................................................................................... 6-27
Managing Information Server repository assets ................................. 7-1
Unit objectives ..................................................................................................... 7-3
What is asset interchange? ................................................................................. 7-4
istool commands .................................................................................................. 7-5
Invoking istool ...................................................................................................... 7-6
Asset interchange archive ................................................................................... 7-7
Topic: Exporting common repository metadata ................................................... 7-8
Exporting common metadata assets ................................................................... 7-9
Identity strings for database assets ................................................................... 7-10
Common metadata export example ................................................................... 7-11
The query command .......................................................................................... 7-12
The query command output file ......................................................................... 7-13
Topic: Exporting security assets ........................................................................ 7-14
Exporting security assets ................................................................................... 7-15
Security export example .................................................................................... 7-16
The -preview parameter..................................................................................... 7-17
Topic: Exporting reporting assets ...................................................................... 7-18
Exporting reporting assets ................................................................................. 7-19
Exporting reporting assets example .................................................................. 7-20
Topic: Exporting individual product assets ........................................................ 7-21
Exporting individual product assets ................................................................... 7-22

Preface
Example: Export Information Analyzer assets .................................................. 7-23

Specifying DataStage assets in istool ................................................................ 7-24
Example: Export parallel jobs in a project folder ................................................ 7-25
Exporting Information Governance Catalog assets ........................................... 7-26
Topic: Importing information assets ................................................................... 7-27
Importing information assets.............................................................................. 7-28
Import example .................................................................................................. 7-29
Import example for DataStage assets ............................................................... 7-30
Demonstration 1: Managing Information Server repository assets .................... 7-31
Unit summary..................................................................................................... 7-38

Preface
Course overview
Preface overview
This course gets those charged with administering Information Server v11.5 and its
suite of many products and components started with the basic administrative tasks
necessary to support Information Server users and developers. The course begins with
a functional overview of Information Server and the products and components that
support these functions. Then it focuses on the basic administrative tasks an
Information Server administration will need to perform including user management,
session management, and reporting management tasks. The course covers both the
use of Information Server administrative clients such as the Administration Console and
Metadata Asset Manager and the use of command line tools such as istool and
encrypt.
Intended audience
Those who will be administering Information Server and/or its product components.
Topics covered
Topics covered in this course include:
• Information Server Technical Overview
• Working with Information Server Clients
• Authentication and Suite Security
• Session Management
• Managing Reports
• Administrative Tools
• Managing Information Server Repository Assets
Course prerequisites
Participants should have:
• No prerequisites

Preface
Document conventions
Conventions used in this guide follow Microsoft Windows application standards, where
applicable. As well, the following conventions are observed:
• Bold: Bold style is used in demonstration and exercise step-by-step solutions to
indicate a user interface element that is actively selected or text that must be
typed by the participant.
• Italic: Used to reference book titles.
• CAPITALIZATION: All file names, table names, column names, and folder names
appear in this guide exactly as they appear in the application.
To keep capitalization consistent with this guide, type text exactly as shown.

Preface
Additional training resources

• Visit IBM Analytics Product Training and Certification on the IBM website for
details on:
• Instructor-led training in a classroom or online
• Self-paced training that fits your needs and schedule
• Comprehensive curricula and training paths that help you identify the courses
that are right for you
• IBM Analytics Certification program
• Other resources that will enhance your success with IBM Analytics Software
• For the URL relevant to your training requirements outlined above, bookmark:
• Information Management portfolio:
http://www-01.ibm.com/software/data/education/

Preface
IBM product help

Help type When to use Location
Task- You are working in the product and IBM Product - Help link
oriented you need specific task-oriented help.
Books for You want to use search engines to Start/Programs/IBM

Printing find information. You can then print Product/Documentation
(.pdf) out selected pages, a section, or the
whole book.
Use Step-by-Step online books
(.pdf) if you want to know how to
complete a task but prefer to read
about it in a book.
The Step-by-Step online books
contain the same information as the
online help, but the method of
presentation is different.
IBM on the You want to access any of the

Web following:
• IBM - Training and Certification • http://www-01.ibm.com/

software/analytics/training-
and-certification/
• Online support • http://www-947.ibm.com/
support/entry/portal/
Overview/Software
• IBM Web site • http://www.ibm.com

Preface

Information Server technical overview
Information Server technical

overview
Information Server v11.5
© Copyright IBM Corporation 2015

Course materials may not be reproduced in whole or in part without the written permission of IBM.
U n i t 1 I n f o r m a t i o n S e r v e r t e c h n i c a l o ve r vi e w
© Copyright IBM Corp. 2007, 2015 1-2

Unit objectives
• List the Information Server functional categories
• List the Information Server products and components that support the
Information Server functional categories
• List the Information Server software, architectural tiers
Information Server technical overview © Copyright IBM Corporation 2015
Unit objectives

IBM InfoSphere Information Server
Unified Deployment
Data cleansing, Common information Data migration and Deliver information

profiling, monitoring vocabulary, transformation and functionality to
information information consumers
accountability
Integrated Metadata Management

Information Server (IS) provides four basic categories of functionality: data quality, data
governance, data transformation, and data delivery. Data quality functions include
checking whether the data meets standards of quality (profiling), monitoring the quality
of data on an ongoing basis, and fixing data that fails to meet standards of quality. Data
governance functions include the development of a common information vocabulary to
facilitate collaboration and information sharing, support for information accountability
and responsibility, and the development of policies and rules to enable precise
communication of information governance requirements.
Information Server hosts various products and components that provide this
functionality. These are discussed on the following pages.

IS products support these functional categories
IBM InfoSphere Information Server
Unified Deployment
Information Analyzer, Information FastTrack, Information Services

QualityStage, Governance Catalog, DataStage, Director
Stewardship Center Stewardship Center QualityStage
IS products support these functional categories

Information Server hosts various products and components that provide this
functionality. These are discussed on the following pages.
There is some overlap in the products that implement this functionality. For example,
QualityStage is a tool for transforming data to meet data quality standards. So it
provides both data quality functionality and data transformation functionality. The
Stewardship Center manages business processes related to both data quality and data
governance, so it provides both data quality and data governance functionality.

Role-based tools with integrated metadata
Business Subject Matter Architect Data Developers DBA

Analyst Expert Analyst
 Simplify Integration  Increase trust and confidence

in information
 Facilitate change  Increase compliance to
Design Operational management and reuse standards
Role-based tools with integrated metadata

Different roles are involved in the typical enterprise data integration project, each role
producing and consuming different types of information assets, also referred to as
metadata. With Information Server, information assets are managed across these
different roles and functions. Different products and different uses of the same product
are geared towards different user roles. For example, FastTrack is geared towards
business analysts. DataStage is geared towards developers. The Information
Governance Catalog supports multiple user roles, including business analysts, subject
matter experts, data analysts, and developers.
As each product creates new information assets, those information assets are
immediately available to others working on the project and within Information Server.
This enables different user roles to communicate with one another and to work together
and share information.
Integrated metadata management has many benefits including simplified data
integration, change management, reliable information, and increased data governance.

Topic:
Data quality products and
components
Topic: Data quality products and components

Information Analyzer
• In-depth analysis of existing data
systems
 Analysis of application, database, and
file-based source data for content,
Subject Matter Data
quality, and structure Experts Analysts
 Profiling of fields, and relationship Other Business

analysis across fields and across Product Modules Glossary
Analyze source data structures, and
monitor adherence to integration and
sources quality rules
• Ongoing measurement and baseline

reporting of information quality
• Creates metadata that describes
where information is managed across
systems
 Provides an understanding of the fitness Physical View
of specific sources and highlights data
that may need downstream attention
Information Analyzer
In order to ensure data quality you need to measure the quality of data in data resource
systems. This is accomplished using Information Analyzer through data-centric profiling
and analysis of source systems, including column analysis, table analysis, and cross-
table analysis, which provide detailed profiling of the data in each column (cardinality,
nullability, range, scale, length, precision). This activity is typically conducted by data
analysts and subject matter experts.
Information Analyzer provides insight into the quality and usage characteristics of the
information. It can also help uncover data relationships across systems, through foreign
key affinity mapping. Profiling is designed to become an ongoing process, comparing
ongoing quality against a baseline, to understand how data quality changes over time
and to ensure that the understanding assumptions are still holding true.

QualityStage functionality
• Provides specialized data quality
processing
 Ensures clean, standardized, de-
duplicated information
 Enables a single version of the truth Subject Matter Data
Experts Analysts
 Supports global postal verification
Standardize and correct source data
• Provides visual tools for designing fields, and match records together
across sources to create a single view
quality rules and matching logic
 Seamlessly integrated into
DataStage
 Precisely calibrates matching rules
• Allows quality logic to be deployed
seamlessly within DataStage
Extraction, Transformation, Load Visual Match Rule Design
(ETL) jobs
QualityStage functionality
QualityStage is a product that helps to identify and resolve the data cleansing issues
previously discussed. It provides data quality functions on an easy-to-use, design-as-
you-think flow diagram. This allows data quality to be embedded in any information
integration process.
QualityStage data quality functions include:
• Free-form text investigation: Enables you to recognize and parse out individual
fields of data from free-form text
• Standardization: Enables individual fields to be made uniform according to your
standards
• Address verification and correction: Uses postal information to standardize,
validate, and enrich address data
• Matching: Enables duplicates to be removed from individual sources, and
common records across sources to be identified and linked
• Survivorship: Enables the best data from across different systems to be merged
into a consolidated record

Why data cleansing with QualityStage is needed

• Lack of information standards
 Different formats and structures across different systems
• Data surprises in individual fields
 Data misplaced in the database
• Information buried in free-form fields
• Data myopia
 Lack of consistent identifiers inhibits a single view
• The redundancy nightmare
 Duplicate records with a lack of standards
Why data cleansing with QualityStage is needed

There are several types of problems within enterprise data stores that QualityStage is
designed to handle:
• The first is a lack of information standards. Names, addresses, part numbers, and
other data are entered in inconsistent ways, particularly across different systems.
• Another common issue involves data surprises in individual fields. Data in the
database is often misplaced, or fields are used for multiple purposes – as where
a name field contains company and address information, a tax ID field contains
telephone numbers, and the telephone field has a variety of mistakes.
• A third common problem is information buried in free-form fields. In this case
valuable information is hidden away in text fields. Since these fields are difficult to
query using SQL, this information is often not leveraged, although it likely has
value to the business. This type of problem is common in product information and
Customer Support case records.
• The fourth problem is data myopia – a term for the lack of consistent identifiers
across different systems. Without adequate foreign-key relationships, it is
impossible to get a complete view of information across systems. This example
shows three products that look very different, but are actually the same.
• The final problem is redundancy within individual tables. This is extremely
common, where data is re-entered into systems because the data entry
mechanism is not aware that the original record is already there.

Topic:
Data governance
Topic: Data governance

Information Governance Catalog

• What is information governance?
• Policies and rules enable precise communication of governance
requirements
 Facilitates use and reuse of trusted information
• Common information vocabulary
 Streamlines the development of business requirements
 Enables collaboration
 Greater understanding of the context and use of information assets
• Support for information accountability and responsibility
 Stewards of information as a single point of contact
 Links between business metadata and technical metadata to ensure
compliance

There are three pillars of information governance: A common information vocabulary,
support for information accountability and responsibility, and policies implemented by
rules that enable the precise communication of governance requirements.
All three of these pillars are supported within the Information Governance Catalog
(IGC). Using IGC you can develop a glossary hierarchy of categories and terms. You
can create policies and implement them as a set of rules. These rules can also be
further implemented by data rules that validate that the data meets relevant conditions
that ensure trusted results.

The Information Governance Catalog (IGC)

• IGC supports information governance
• Governance policies and governance rules
 Governance policies communicate the company’s governance requirements
 Governance rules implement policies by communicating and enforcing data
quality requirements
− Linked to Information Server data rules that specify data quality conditions that can
be run against data in DataStage and Information Analyzer
• Governance categories and terms
 Terms describe specific information assets
− Information assets can be linked to the terms that describe them
 Terms are classified within an hierarchical structure of categories
• Stewards can be assigned to terms and information assets to provide a
single point of contact
The Information Governance Catalog (IGC)

This slide outlines the ways in which the IGC supports information governance. In
addition to the common vocabulary provided by glossary hierarchies of categories and
terms and policies and rules that facilitate the use and reuse of trusted information,
stewards can be assigned to information assets to provide a single point of contact for
information about the assets.

Stewardship Center
• Business process workflow application to resolve data quality issues
 Data quality exceptions can be generated in Information Analyzer,
DataStage, and QualityStage
• Business process workflow application to support the development of a
governance catalog
 Governance events can be generated in the information governance catalog
− E.g., a catalog term has been submitted for approval
• Stewardship Center application sends an email to notify the reviewers
Stewardship Center
Using the Stewardship Center you can implement business process workflows that
facility data quality and governance applications.
Data quality exceptions can be generated in several Information Server products and
components including DataStage, QualityStage, and Information Analyzer. With the
Stewardship Center you can specify workflows to handle these exceptions. These
workflows include email notifications and signoffs.
The Stewardship Center also supports the development of a governance catalog in the
Information Governance Catalog. For example, the Stewardship Center can send
notifications to Catalog term reviewers for their approvals.

Topic:
Transformation
Topic: Transformation

Using Information Server to transform data

• Transformation is key to
enabling information to be used
in new business contexts
• Designed for use by Data
Data DBAs Subject Matter
information experts using the Analysts
Architects Experts
understanding provided by the
metadata
Logic
• Transformation and delivery Reuse
can be reused across multiple
mechanisms
Request Response
 Large volume batch movement
 Real-time event-driven response
 Service-oriented architecture
Using Information Server to transform data

Information Server transforms information from the application-centric context in which
it is currently locked, into an entirely new business contexts that are appropriate to new
business opportunities or challenges. This type of transformation is not simply about
format-to-format translation, but is more focused on merging data together. Since
transformation is really focused on the context of information, it requires an
understanding of the information sources, business meaning, and relationships, so it
needs to be created by information experts (data analysts, database administrators,
subject matter experts), using the understanding provided by the metadata.
The primary Information Server product used to transform data is DataStage, which is
discussed on the following pages.

DataStage
• Create codeless, visual designs of ETL
data flows using built-in transformation
components (stages) and links
 Use stages to extract data from and load
data to data resources, including Developers Architects
database tables, sequential files,
Transform and aggregate any volume
enterprise resources of information in batch or real time
through visually designed logic
 Links specify the flow of data from one
stage to another
 Can create reusable sets of components
(shared containers) that can be shared
across jobs, projects, and developers
• Complete ETL functionality with
metadata-driven productivity
• Supports team-based development and
collaboration
DataStage
DataStage is the main Information Server product that is focused on transformation and
movement of information. DataStage enables codeless visual design of data flows, and
includes built-in transformation components (stages) and connectors.
DataStage is built around team collaboration and reuse. Everything from individual
stages, to connections, to entire data flows can be reused across different jobs and
projects. In addition, DataStage leverages the shared platform services for parallel
processing, administration, deployment, and connectivity.

FastTrack
Business
• Used in conjunction Users
with DataStage
• Build mapping
specifications that
describe and
document
DataStage ETL jobs Generated
DataStage job
• Generate DataStage FastTrack mapping
jobs from the specification
mapping
specifications
• Reverse-engineer
DataStage jobs into
mapping
specifications
FastTrack
Mapping specifications specify how data is mapped and transformed from source fields
to target fields. Business analysts create mapping specifications, leveraging source
analysis, target models, and metadata to facilitate the mapping process. Prototype
DataStage ETL jobs can be generated from these FastTrack mapping specifications.
These mapping specifications guide the DataStage developer’s work, and provide
DataStage them with a head-start in designing and building their DataStage jobs.
DataStage jobs can also be "reverse-engineered" back into mapping specifications that
document their mappings and transformations.

Topic:
Delivery
Topic: Delivery

Information Services Director

• Rapid SOA Deployment
• Package information integration logic
(DataStage jobs) as services
• These services to be invoked as
Enterprise Java Beans or Web Developers Architects
services Flexibly deploy and manage reusable
• Provides load balancing and fault information services without hand

coding
tolerance for requests across multiple
servers
Rapid SOA Deployment
Information Services Director

Information Services Director is used to deliver functional and component logic as
Enterprise Java Beans or Web Services. Within the Information Server context, this
logic includes database functionality as well as DataStage and QualityStage ETL
functionality.
DataStage and QualityStage jobs can include ISD input stages and/or ISD output
stages. The ISD input stages are used in a service to pass values to the job. ISD output
stages are used to return data to the service that can then be passed to the service
consumers.
All functions are deployed as shared services within a Service Oriented Architecture
(SOA). This is done consistently, whether you are using DataStage, QualityStage, or
DB2.

Topic:
Information Server
Architecture
Topic: Information Server Architecture

Information Server architecture

• Provides a unified architecture
 Common services for Information Server products and components
 Parallel processing engine
 Repository
• Service-oriented architecture
• Efficiently uses hardware resources
• Reduces the amount of development and administrative effort that are
required to deploy an integrated solution
Information Server architecture

Information Server provides a unified architecture that works with all types of
information integration. Common services, unified parallel processing, and unified
metadata are at the core of the IS architecture.
The architecture is service-oriented, enabling Information Server to work within an
organization's evolving enterprise service-oriented architectures. A service-oriented
architecture also connects the individual products of Information Server.

Information Server backbone
Information Information Information DataStage QualityStage MetaBrokers

Stewardship
Services Governance Analyzer Center
Director Catalog
Metadata Metadata
Access Services Analysis Services
Services Domain
Information Server backbone

This graphic shows the Information Server backbone. The hosted applications are at
the top. They all share the same services displayed in the middle. They all share the
same repository displayed at the bottom. The Information Server parallel processing
engine is used by several Information Server applications to run their jobs, including
DataStage ETL jobs, QualityStage data cleansing jobs, and Information Analyzer data
analysis jobs.

Parallel processing engine

• Supports all hardware
configurations (single
processor, SMP, MPP,
GRID, Cluster)
• Scale up by adding
processors or nodes
with no design change
or re-compilation
• External configuration
file specifies hardware
configuration and
resources Single
processor
SMP System MPP, GRID, and
Clustered
Systems
Parallel processing engine

Information Server uses a parallel processing layer (Engine) that is used by DataStage,
QualityStage, Information Analyzer, and other IS products and components. This
architecture enables those products to scale up their processing speeds by adding
additional processors, in several different hardware configurations.

Information Server architectural tiers

• Four tiers (or domains)
 Client tier (Information Server clients and hosted products clients)
 Services tier
 Repository tier
 Engine tier
• Tiers may be installed on multiple computers
 For example:
− Client tier on one or more different computers
− Services and Repository tiers on an additional computer
− Engine tier on one or more additional computers
Information Server architectural tiers

Information Server functionality, products, and components are separated into four
different layers or tiers. During Information Server installation you specify which tier or
tiers you want to install on a particular computer system. Different tiers can be installed
on the same or different computers that are network connected.
This distributes the Information Server workload for high performance job development
and data processing.

Architecture diagram
Information Server
Information Server Platform
Services 1 Repository 1
Client 1 .. N
Platform Services
Common Services Product-specific

Suite Clients Services
Information Assets
Desktop and Web Repository
WebSphere Application Server

(WAS)
Product Clients
Desktop and Web
Working Areas
Engine 1 .. N
DataStage/QualityStage
Scratch and Dataset
Information Server Engine
Information Analyzer data
QualityStage Match data Connectors, Packs, Service

QualityStage Modules Agents
ISD Resource Providers

Communication Agents
Architecture diagram
Information Server clients include:
• Information Server Web Console (IS administration/reporting)
• DataStage/QualityStage clients (Administrator, Designer and Director)
• FastTrack client
• Metadata Workbench client
• Information Server Console: hosts Information Analyzer and Information Services
Director
• WebSphere Application Server (WAS) client
• Information Server Manager
• Multi-Client Manager
• Information Server Command Line Interface (istools)

Services:
• Uses IBM WebSphere Application Server (WAS) to implement the J2EE services
functionality
Repository:
• DB2, Oracle, SQL Server, etc.
Parallel engine:
• A C++ compiler is required to compile DataStage, QualityStage, and Information
Analyzer jobs into an executable form capable of being run by the parallel engine.

Platform topologies
Two-systems Three-systems
deployment deployment
Services
Services
Platform topologies
The diagram shows DB2 as the Repository database server, but Oracle and SQL
Server are also supported, as previously noted. Although only one Engine is shown for
each topology, Information Server supports multiple parallel engines on the same or
separate systems.
All tiers should be installed in the same physical LAN, connected by high-speed
network connections.
The Services and Engine platform types must match. The Repository database need
not match platform type of the Services and Engine.

Client tier
• Provides access to both Suite clients and Suite product and component clients
• Administrative clients include Information Server clients as well as clients specific
to Information Server hosted products:
 Information Server Administration Console
− Security
− Session maintenance
− Logging and reporting management
 DataStage Administrator client
− DataStage global and project configuration and defaults
 Other Information Server products have a single client used for both administration and
user tasks
− Administrative tasks require product administrator authorization
• Clients for specific Information Server products and functional components:
 Appropriate interfaces for the type of user (business or technical)
 Facilitate the Information Server data quality, governance, integration, and delivery
functions
Client tier
Information Server products and components can be accessed through client
components. The client tier contains both administrative clients and user clients.
Some products and functionality are accessed through a web browser. These are
called "thin clients", because the functional components exist on the server but are
delivered to the web browser.
Other clients are called "thick clients", because functional components are installed and
exist on the client computer system as well as the server computer system.

Services tier
• Set of shared services that centralize core tasks across the platform
 Administrative tasks such as security, user administration, logging, and
reporting
 Repository services
 Shared services allow these tasks to be managed and controlled in one
place, regardless of which product is using the service
• Various product components add additional product-specific services
to those that are deployed
• Deployed by IBM WebSphere Application Server (WAS)
Services tier
The Services tier consists of a set of shared services that centralize core tasks across
the platform.
Some services address functionality that is unique to a specific Information Server
product or component. Other services, such as security services, are used across
multiple products and components.
The services tier is deployed within an IBM WebSphere Application Server (WAS)
instance. The computer system running the WAS instance is referred to as the domain
or services host system.

Engine tier
• Components
 Engine: The high-performance, parallel engine that performs analysis,
cleansing, and transformation
 Connectors: Provide common connectivity to external resources such as
DB2, Teradata, Oracle, Sybase, InfoSphere MQ, and others
 Packs: provide high-speed connectivity to packaged enterprise applications
 QualityStage modules: a set of integrated modules for accomplishing data
cleansing and re-engineering tasks such as Investigating, Standardizing,
Matching and Survivorship
 Service Agents: manages bi-directional communication between the engine
processes and the Repository
• To deploy the Engine tier to multiple machines, the Information Server
engine installation software is copied or NFS mounted to each engine
server
Engine tier
The engine tier consists of the following pieces:
• Information Server Parallel Engine: The high-performance, parallel engine that
performs analysis, cleansing and transformation processing
• Connectors: Provide common connectivity to external resources such as DB2,
Teradata, Oracle, Sybase, InfoSphere MQ, and others
• Packs: provide high-speed connectivity to packaged enterprise applications
• QualityStage Modules: a set of integrated modules for accomplishing data
cleansing and re-engineering tasks such as Investigating, Standardizing,
Matching and Survivorship
• Service Agents: manages bidirectional communication between the engine
processes and the Metadata Repository
To deploy the engine tier to multiple computer, the Information Server engine software
is copied or NFS mounted to each server.

Repository tier
• Stores objects and metadata for Information Server and each of its
hosted products
• Enables Information Server products to share metadata with each
other throughout the data integration lifecycle
• For the Repository database (named XMETA by default), the
Information Server installation package comes with DB2
 An existing DB2 instance can also be configured
 If another DBMS is used (for example, Oracle), scripts must be run before
the installation to configure the Repository
Repository tier
The Information Server Repository stores the objects and metadata produced and
consumed by Information Server hosted products and components. The Repository is
implemented as a database, named XMETA by default. Since all the products hosted
by Information Server use the same XMETA database, metadata produced by one
product can be shared with other Information Server products.
For the XMETA database, DB2 is supported. DB2 can be installed as part of the
Information Server installation or an existing DB2 instance can be used. Other
database systems, such as Oracle, are also supported.

Tier interaction
2. Authentication Service
retrieves credential
information
Client
Client Services Repository
1. Client Logs in to IS Server .

using the IS Authentication Common
Service (using host and port) Services
Metadata
3. List of DSEngines and Repository
mapped credentials for
logged user
5. List of DS projects, jobs,

and design information.
Engine 8. Access services and

4. Logs in to Engine data on primary IS Server
Server (TCP/IP) using
Credential Mappings
and server short name Information
Server 7. Logs in to IS Server using the IS
Engine Authentication Service (using host and
port provided by user)
6. DS Job compile and

run information.
Tier interaction
DataStage clients log into the IS Server and retrieve the DataStage credentials the
users are mapped to. The DataStage client, using the IS Authentication Service, logs
into the IS Server as follows:
• The host name and port number provided in the DataStage login window are
used to do an HTTP request with the IS server.
• The HTTP request is going to return the JNDI properties needed to establish a
remote EJB session between the client and the IS server. One of these JNDI
properties is the Provider URL which include the hostname and port number
(from the InfoSphere serverindex.xml file). The client uses JNDI lookups to call
and work with IS Services using the retrieved JNDI properties.
• The IS Server returns to the client the mapped credentials for the user. Even if
credential mapping is turned off (shared user registry mode), the credentials
needed to log in to the DataStage Server are returned from the IS Server (in this
case, the credentials will be the same as the ones used to login to the IS server).
These will allow the client to log onto the various DataStage Servers installed.

Apply your knowledge

Identify Information Server functions and associated components

Purpose:
Check your understanding of the different products, components, and
functions of the Information Server product suite. As you take this test feel
free to review the unit content.
Question 1: Which Information Server product performs data cleansing? Choose one.
A. Information Analyzer
B. QualityStage
C. DataStage
D. FastTrack
E. Information Governance Catalog
Question 2: Which Information Server product performs data transformation? Choose
one.
A. Information Analyzer
B. QualityStage
C. DataStage
D. FastTrack
E. Information Governance Catalog
Question 3: Information Governance Catalog profiles source data.
A. True
B. False
Question 4: Which Information Server layer is comprised of design and operational
databases? Choose one.
A. Services (Domain)
B. XMETA Repository
C. Server
D. Client

Question 5: Which function does Information Server FastTrack perform? Choose two.
A. Creates business terms
B. Generates DataStage jobs
C. Runs metadata analysis reports
D. Creates data models
E. Creates mapping specifications for ETL jobs
Question 6: Which functions does Information Governance Catalog perform? Choose
two.
A. Browse Information Server information assets
B. Data cleansing
C. Cross-tool reporting
D. Data transformation
E. Data governance
Question 7: The DataStage Multi-Client manager allows you to do which of the
following? Choose one.
A. Connect to multiple repositories
B. Connect to multiple servers
C. Install multiple DataStage client versions on a workstation
D. Install multiple repositories
Question 8: QualityStage cleanses data by using logic provided by which object?
Choose one.
A. Rule Sets
B. Services
C. Connectors
D. Packs

Apply your knowledge - solutions

Answer 1: B
Answer 2: C
Answer 3: B (False)
Answer 4: B
Answer 5: B, E
Answer 6: A, E
Answer 7: C
Answer 8: A

Unit summary
• List the Information Server functional categories
• List the Information Server products and components that support the
• List the Information Server software, architectural tiers
Unit summary


Working with Information Server clients
Working with Information

Server clients

U n i t 2 W o r k i n g wi t h I n f o r m a t i o n S e r v e r c l i e n t s

Unit objectives
• Using the Information Server Launch Pad to access Information Server
thin clients
 Administrative Console
 Information Governance Catalog
 Metadata Asset Manager
• Accessing Engine clients
 DataStage / QualityStage clients
 FastTrack
 Information Server Manager
• Information Server Console clients
 Accessing Information Analyzer
 Accessing Information Services Director
Working with Information Server clients © Copyright IBM Corporation 2015
Unit objectives

Information Server Client-Server architecture
Client system, with “fat clients” and “thin clients”,

interacting with server systems
Services
Information Server Client-Server architecture

The Information Server clients run on Windows only. Unless the server systems are
also running on Windows, the clients will be accessing the server systems from
separate computers. Typically, this is the case. Information Server includes both "fat
clients" and "thin clients". "Fat clients" are those that require functionality to be installed
on each Client system. "Thin clients" do not require this. They provide a client interface
to functionality that is fully installed on the Server system. In most cases thin clients are
accessed by means of an Internet browser.
In this diagram, the Repository, Services, and Engine tiers are all placed on one
computer. As mentioned earlier, this is just one possible deployment. For example,
commonly, the Engine tier is separated from the Repository and Services tiers.

Information Server client icons
Thin Clients are accessed using a web browser,

Internet Explorer or Mozilla
Information Server Client icons Command Line

Manager Interface (istool)
Multi-
Information
Server Console Client
Manager
DataStage
FastTrack
clients
Information Server client icons

Thin clients include the Information Server Administrative Console, Information
Governance Catalog, and Metadata Asset Manager. These are clients such that no
client components are installed on the client system. Any systems with a supported web
browser can access these clients. Most thin clients can be accessed from the
Information Server Launch Pad.
Fat clients include the Information Server Console (which provides access to
Information Services Director and Information Analyzer), Multi-Client Manager,
FastTrack, and the DataStage clients.
The Command Line Interface (istool) is a metadata interchange tool discussed in a later
unit.
Information Server Manager client is Engine tier client not discussed in this course.

Topic:
Thin clients
Topic: Thin clients

Information Server launch pad

• Easy access to many Information Server thin clients
• No log in required to the Launch Pad
 Log in occurs when specific clients are accessed
Click on the link to

the client
Information Server launch pad

The Information Server Launch Pad provides easy access to most of the Information
Server thin clients including the Administration Console, the Information Governance
Catalog, the Operations Console, and Metadata Asset Manager. Click on a link to get to
the component client.
No log in is required to access the Launch Pad. Log in occurs when specific clients are
accessed.
You can also log in to any of these clients separately using the client URL.

Logging into thin clients

• Process is the same for all thin clients
 From the Launch Pad click the link to open the client
 Log in using a user ID and password with authorization to work in the client
Logging into thin clients

The process to log into think clients is the same for all thin clients. Open up the Launch
Pad and then click the client link. Then log in with a user ID and password with
appropriate authorization. Authorizations are discussed in a later unit.

Administration Console
• Log in using Information Server administrator user ID
 By default, isadmin
• Perform general Information Server administrative tasks, including:
 Session management
 User management
 Reporting management
Here is the log in window for the Administration Console. The log in windows for other
think clients are similar. Enter your user ID and password, with appropriate
authorization, in the User name and Password boxes. Then click the Login button.
To log in to the Administration Console you require the Suite Administration
authorization role. When Information Server is installed a user ID named isadmin is
created by default with this authorization.
The Administration Console is specifically designed for Information Server
administration tasks including session management, user management, and reporting
management.

Console administrative tasks

• Specify user IDs and authorizations
• Session management
• Reporting management
• Specify Engine credentials
 Required when the DataStage user registry is different from the Information
Server user registry
Manage reports
Manage sessions
Manage users
Console administrative tasks

There are two tabs in the Administration Console. The Reporting tab is used for report
management. The Administration tab is used primarily for managing users and groups
and for session management.
DataStage users also require Engine credentials. This is discussed in a later unit. This
is done in the Domain Management folder.

Metadata Asset Manager

• Primarily for users to import metadata for use with specific IS products
and components
• IS Administrators can use it to:
 Set up connections to data sources
 Clean up the Repository (XMETA)
− Delete assets
− Manage orphaned assets
− Manage duplicate assets
 Specify metadata interchange servers
− Server systems from which information assets can be imported
Metadata Asset Manager

Information Server products and components not only product information assets
(metadata), they also consume information assets. For example, a DataStage job might
process data in a database table. In order to process this data DataStage needs to
know its format, including its columns and their types and nullability. This information is
provided through the metadata import process. Metadata Asset Manager (also known
as IMAM) is one of the primary Information Server components used to import
metadata. Within IMAM you can define connectors to various types of data resources
and use these connectors to import metadata for them.
IMAM also contains functionality for managing the Information Server Repository which
by default is a database named XMETA. Within IMAM you can browse metadata
assets stored in the Repository and you can clean up corrupted metadata assets.
Metadata can be imported from any computer systems defined within IMAM as a
metadata interchange server.

Repository Management tab
Clean up Repository
assets
Create connections
and import
information assets
Repository Management tab

Here you see the Import tab of Metadata Asset Manager. The metadata assets are
imported to a staging area before being shared with the Repository.
IMAM contains a large number of Connector or Bridge types that can be used import
the metadata. There is a subtle difference between Bridges and Connectors.
Connectors are used to access a data source. Bridges are used to access the data
source and to perform additional conversions to the information assets to enable them
to be integrated into the Repository.


• Used to build and manage the enterprise governance catalog
• Also browse Information Server information assets
• Administrative tasks include:
 Managing the governance catalog development workflow
 Manage the display and accessibility to information assets and Catalog
assets

The Information Governance Catalog (IGC) provides two primary functions. Like
Metadata Asset Manager, you can use it to browse information assets stored in the
Repository. But Metadata Asset Manager can only be used to browse the types of
information assets it can import. There are other types of information assets, in
particular those produced by Information Server products and components, which
cannot be browsed in Metadata Asset Manager. In the IGC you can browse all the
types of information assets stored in the Repository.
The other main function of IGC is the development of governance assets including a
governance catalog of categories and terms and a set of governance policies and rules.
Among an IGC administrator's primary responsibilities are managing the governance
catalog development workflow and managing accessibility to what information assets
users can view.

Example Category hierarchy
Category name
Category description
Category terms
Category hierarchy
Example Category hierarchy

Here you see an example governance catalog of categories and terms. Catalog
categories are organized in a hierarchy. Categories can contain terms that describe
information assets within the domain of the category. For example, the category
Physical Address contains terms such as Postal Code and State.

Topic:
Engine clients
Topic: Engine clients

Engine clients
• The DataStage parallel engine is used not only by DataStage but also by several
other Information Server products and components, in particular Information
Analyzer
 QualityStage is embedded within DataStage and also uses the DataStage parallel engine
• DataStage clients
 Administrator client: Used for DataStage, QualityStage development and runtime
administration
 Designer client: Build and run DataStage jobs
 Director client: Primarily used by DataStage operators to run DataStage jobs
− A DataStage operator is a user who can run job but cannot build or administer them
• Operations Console
 Monitor DataStage jobs as they run
 Monitor Engine resource usage
• FastTrack
 Create mapping specifications for DataStage jobs
• Multi-Client Manager
 Switch between different DataStage client versions
Engine clients
The Information Server Engine system refers to a computer system where DataStage is
installed. For this reason it is also called the DataStage Engine. It is called the Engine
because this is the system where jobs are run that perform various Information Server
tasks. Within an Information Server domain there can be multiple engine systems.
DataStage actually has two engines: the parallel engine and the server engine. These
refer to two types of DataStage jobs that can be run: parallel jobs and server jobs.
When the word engine is used without qualification, it refers to the parallel engine.
Engine clients refers to the DataStage product clients (Designer, Administrator,
Director) as well as the clients for other products and components associated with
DataStage. The Operations Console is a client used to monitor running DataStage jobs.
This client is discussed in a later unit. The Multi-Client Manager is a client used to
switch between different versions of DataStage.

DataStage administrative tasks

• DataStage configuration is done at the DataStage project level
• DataStage project administrative tasks include:
 Adding and deleting DataStage projects
 Specify user project permissions
− Who can log into a DataStage project
− What they can do in the project
 Environment variable settings
− Environment variables specify the development and runtime environment for jobs
stored within the project
 Backing up and restoring DataStage project objects
DataStage administrative tasks

DataStage developers work with projects. A project stores the objects, such as
DataStage jobs, that the developers build. Multiple DataStage developers can work
within the same project. In order to work within a particular project a user must be
authorized. As will be discussed later, authorization is provided partially within the
Information Server Administration Console and partially within the DataStage
Administrator client.
The development and runtime environments for a particular DataStage project are
specified within the DataStage Administrator client. In addition, there is a set of
environment variables, configured within the Administrator client, which set the project
environment. These include variables that specify database libraries that DataStage
jobs will access ($LD_LIBRARY_PATH) and variables that determine how much
information is logged during a DataStage job run (for example, $APT_DUMP_SCORE).

Logging into DataStage Administrator
Host name of the

services system
DataStage
administrator
user ID
DataStage
server system
Logging into DataStage Administrator

This graphic shows the log in window for DataStage/QualityStage Administrator client.
In the Host name of the services tier type the name of the system that hosts the
services. This is the system where the WAS instance is installed.
In the User name and Password boxes type the user name and password with
DataStage Administrator or developer role authorization and with DataStage
credentials.
Multiple DataStage servers can exist either on the same or on different systems. In the
Host name of the Information Server engine box, you select the server system that
has the DataStage projects you want to work with.

DataStage Administrator Projects tab
DataStage Add/Delete
projects projects
Specify project
properties
DataStage Administrator Projects tab

This graphic shows the Projects tab in the Administrator client. It lists all DataStage
projects. Click the Properties button to configure the properties and environment for
the project.
You can also add and delete DataStage projects from this window.

DataStage Designer tasks

• DataStage developers use the Designer client to build, run, and
monitor their DataStage jobs
• Within the DataStage Designer client, developers can:
 Build and compile DataStage Extraction, Transformation, Load (ETL) jobs
 Import metadata for use within jobs
 Run DataStage jobs
 Monitor the job log messages, written to the log while the job runs
 Back up and restore DataStage objects
DataStage Designer tasks

In addition to the administrative tasks performed in the DataStage Administrator client,
there are also administrative tasks that can only be performed in the DataStage
Designer client. But primarily DataStage Designer is used by DataStage job
developers.
Notice that Metadata Asset Manager which was discussed earlier is not the only
Information Server product or component that can import metadata. Within DataStage
Designer, metadata for data sources that can be processed by DataStage jobs can be
imported, including sequential files, mainframe files, database tables, and many other
types. But DataStage imports are stored in a separate repository local to DataStage.
They cannot be directly used by other products and components in Information Server.
DataStage Designer does contain a tool that can be used to convert locally stored
metadata to shared Repository metadata.

Logging into Designer
DataStage
project
Logging into Designer

Logging into Designer is like logging into Administrator, except that in Designer you are
logging into a specific DataStage project. You select this project in the Project list.
Multiple DataStage servers can exist either on the same or on different systems. The
name of the project is preceded by the name of the DataStage server that hosts it.
The user ID entered here requires a DataStage Administrator or DataStage Developer
role. The former is specified in the IS Administration Console. The latter is specified
within DataStage Administrator.

Designer work area
Repository
DataStage
parallel job
DataStage
components
palette
Designer work area

The appearance of the Designer work space is configurable. The graphic shown here is
only one example of how the GUI components might be arranged.
In the right center is the Designer canvas, where DataStage jobs are built. On the top
left is the DataStage local Repository window. Items in the Repository, such as jobs
and table definitions can be dragged to the canvas area. On the bottom left is the
Palette, which contains the components (stages) that can be added to the canvas to
build the DataStage jobs.
Shown on the canvas is an example of a DataStage ETL (Extraction Transformation
Load) job. The stages are functional components of the job. The links are like "pipes"
through which data flows. This job reads a sequential file, transforms the data, and then
writes it to DB2 tables using the DB2 Connector stage.

DataStage Operations Console

• Accessible from the Information Server Launch Pad
• Thin client
 Log in using Operations Console user ID
• Monitor jobs running on any server in any project in the domain
• View job runtime information, including:
 Job run times
 Performance information
 Log information
• View system resources (CPU, memory) as the jobs are running
• Manage the Engine workload
 Job runtime prioritization
 Number of jobs that can run at the same time
DataStage Operations Console

The DataStage Operations Console is a thin client used to monitor the DataStage
parallel Engine and Engine system resources. It also contains a workload manager
which can prioritize the running of DataStage jobs. The total number of jobs running at
the same time can be limited and jobs can be put into different queues providing
different levels of priority.
System resources that can be monitored include CPU usage and available memory.

Operations Console
Job activity
Engine
status
System
resources
Operations Console
In this graphic, you see the Dashboard tab of the Operations Console. The Operations
Console opens to the Dashboard tab, which contains three sections of information.
The Job Activity section shows which jobs are currently running and their statuses
within a time range, for example, last 3 days. In this example, no jobs are currently
running or have been running for the last few days.
The Operating System Resources section displays the CPU usage and free memory
that is currently available within a time range for DataStage jobs running on the
selected Engine.
The Engine Status section displays the current status of engine services, including the
Operational Console services and WLM (Workload Management).

FastTrack
• Fat client
• Logon procedure same as for other fat clients
• Used to create mapping specifications
 Defines mappings, filters, and transformations between source and target
columns
 DataStage jobs can be generated from mapping specifications
• Administrative tasks
 Can define data source connections within FastTrack that are available
throughout Information Server
− Connections defined in Metadata Asset Manager are also available within
FastTrack
 Import metadata of mapping specification sources and targets
 FastTrack projects configuration
FastTrack
Logging into FastTrack is similar to logging into other fat clients. You specify the
services system and the port used to communicate with it, and you specify a user ID
and password with FastTrack credentials.
FastTrack is a product designed to work with DataStage. With FastTrack you can
create mapping specifications that document the mappings and transformations of a
DataStage job. This mapping specification can be used to document a DataStage job,
as well as to provide a DataStage developer with specifications for building it.
From mapping specifications, prototype DataStage jobs can be generated, which
implement the mappings and transformations specified in the mapping specification.

FastTrack data source configuration

Data source
connection
New
connection
FastTrack data source configuration

One administrative task you may be called on to perform with respect to FastTrack is to
define data resource connections to database tables. These database table definitions
are stored in the Information Server Repository, to be used by FastTrack as well as
other Information Server products, such as Information Analyzer.
Data source connections defined in Metadata Asset Manager are also visible and can
be used within FastTrack.
After a connection has been defined, developers can import metadata for selected
schemas and tables, to be used in their mapping specifications.

Multi-Client Manager
• DataStage clients for different versions of DataStage can be installed
on a single computer system
 But only one version can be active at a time
• Use the DataStage Multi-Client Manager to switch between different
versions of DataStage clients
Multi-Client Manager
From a single client system you can connect to multiple DataStage server systems, but
the DataStage clients work with only one version of DataStage. In order to connect to
DataStage servers running different versions of DataStage you need to install clients for
both versions and use Multi-Client Manager to switch between them.

Topic:
Information Server console
clients
Topic: Information Server console clients


• Provides access to Information Analyzer and Information Services
Director (ISD)
• Administrative tasks
 Configure Analysis Settings
− Configure and validate Engine settings
• Specify DataStage credentials
− Configure the analysis database (IADB)
• Select IADB connection in the Information Server Console
• The connection to IADB must already have been created in Metadata
Asset Manager
 Configure Information Services Director connections to information
components such as DataStage that will implement services defined in ISD
 Configure projects
− Projects can be either Information Services Director projects or Information
Analyzer projects

The Information Server Console provides access to two different Information Server
products: Information Analyzer (IA) and Information Services Director (ISD).
(Information Services Director is also known as WISD, because it used to be a
WebSphere product.)
Information Analyzer is used to analyze data in order to determine its quality and
formats. It might be used to analyze the data sourced by DataStage jobs or it might be
used to analyze the data loaded into a data warehouse by DataStage jobs.
Information Services Director is used to wrap DataStage and QualityStage ISD jobs
and other functional components into services that can be delivered to consumers.

Analysis Engine settings
Engine
credentials
Analysis Engine settings

Configuration for Information Analyzer occurs on three tabs. On the Analysis Engine
tab you specify DataStage credentials for the DataStage Engine that will be used to run
the analysis jobs. You also specify the host name of the DataStage Engine system.
When Information Server is installed, a special DataStage project named by default
ANALYZERPROJECT is created for use by Information Analyzer. You also specify the
name of the DataStage project used by Information Analyzer.
When DataStage is installed, as part of the Information Server installation, a user ID
named by default dsadm is created and/or configured. In this example, dsadm is used
to run the DataStage jobs used by Information Analyzer.

Analysis database settings
ODBC
connection
to IADB
Validate database
settings
Analysis database settings

On the Analysis Database tab you specify a connection to the IADB database. This is
a special database used by Information Analyzer created during Information Server
installation.
The JDBC data source connection to IADB is also automatically created during
Information Server installation. However, a non-JDBC connection (ODBC or native) is
also required and this is not automatically created during Information Server installation.
You need to create this data connection within Metadata Asset Manager by running a
dummy import of the IADB database. In this example, a native DB2 connection named
IADBConn was created during a dummy import and selected in this panel. In this
example, and in the course image, IADB and the XMETA Repository are DB2
databases created during Information Server installation.

Demonstration 1
Working with Information Server Clients
In this demonstration, you will:

• Log into and explore the Information Server Administration Console
• Log into and explore the Metadata Asset Manager thin client
• Log into and explore the Information Governance Catalog
• Log into and explore the Information Server Console
• Log into and explore DataStage client functionality
• Log into and explore the DataStage and QualityStage Operations Console
• Log into and explore the FastTrack client
Demonstration 1: Working with Information Server Clients

Demonstration 1:
Working with Information Server clients
Purpose:
This exercise helps familiarize you with the Information Server clients used
for administration. Information Server hosts a complex array of products.
Although you do not need to acquire in-depth knowledge of all of these
products, you need to have some understanding of what they do and how
they are used.
Task 1. Log into and explore the Information Server

Administration Console.
1. Log into the course image using student/student (that is, user ID student,
password student).
2. Open Mozilla Firefox which defaults to the Information Server Launch Pad.
3. Click the Administration Console link.

4. Enter an Information Server (IS) Administrator user ID and password:

isadmin/isadmin.
5. Click the Administration tab.

6. Open and explore the available folders in the Navigation panel.
7. When you are done exploring the Administration tab, click and explore the
Reporting tab. In particular, expand the Report Templates folder to view the
templates for the different types of reports that can be created and run.

Task 2. Log into and explore the Metadata Asset Manager

thin client.
1. From the Information Server Launch Pad click the Metadata Asset Manager
link.
Notice that you did not have to separately log into Metadata Asset Manager.
Unless you close the browser or explicitly log out of a thin client, Information
Server automatically logs you in using the current user ID and password.
2. Explore the Repository Management, Import, and Administration tabs.
Notice that there are three types of functionality available within Metadata Asset
Manager: Importing metadata assets into the Repository, searching and
browsing metadata assets in the Repository from the Repository Management
folder, and managing assets within the Repository from the Repository
Management folder.
3. When you are finished exploring, click Logout at the top right to log out of
Metadata Asset Manager.
Task 3. Log into and explore the Information Governance
Catalog.
The Information Governance Catalog can be used to browse information assets
in the repository and to develop and maintain a governance catalog of
categories, terms, policies and rules. A sample governance catalog has been
imported into the Repository on the course lab image for you to explore.
1. From the Information Server Launch Pad, click the Information Governance
Catalog link.
2. If necessary, log in as student/student.

3. From the Catalog tab, click Information Assets>Browse All.

Here you see folders of all the types of information assets that the Information
Server Repository contains. Explore, for example, the database assets.
4. Click the Hosts icon.

The EDSERVER host is listed.
5. Click the EDSERVER link and then open the Contains Assets folder.
Notice that a host computer system can host several different types of assets
including databases, transformation (DataStage) projects, and data
connections.

6. Explore, for instance, the database asset named SAMPLE. Click on the
SAMPLE link.
7. Click on the STUDENT schema in the Database Schemas folder.
Notice the database table metadata that is stored in the Information Server
Repository.
8. Click on, for example, the EMPLOYEE table link to display the columns of this
database table.

9. Click Glossary>Category Hierarchy. Then click the Business

Information>Location Information>Physical Address category. Then
expand the Terms folder.
10. Explore some of the terms in the Physical Address category, for example,
StreetAddress.

Task 4. Log into and explore the Information Server Console.

The Information Server Console provides access to two Information Server
products: Information Services Director and Information Analyzer.
In this task you will explore how and where the Console is configured.
1. Click the Information Server Console icon on your desktop and log in to as
student/student. The host name of the services tier is https://edserver:9443,
as shown below.
2. Click the Home pillar icon (blue sphere in the upper left portion of the window)
and then click Configuration>Analysis Settings.
There are three tabs for configuration.

The Information Server (DataStage) Engine is used by Information Analyzer to

run data profile jobs.
3. On the Analysis Engine tab the credentials used to access the Engine are
specified. If none are specified as shown here, then the Engine credentials are
taken from the default setting in the Administrator Console.
4. Click the Analysis Database tab.
5. When Information Server is installed a database named IADB is created for use
by Information Analyzer to store profiling information. On the Analysis
Database tab, the connections used to access this database are specified.
In this example the non-JDBC connection is named IADB. This connection was
created in Metadata Asset Manager.
In this example the JDBC connection is named jdbc/IADB. This connection
was created during Information Server installation.

6. Click the Analysis Settings tab.
7. When a data profiling job is run, data in columns in a table are profiled. On the
Analysis Settings tab profiling defaults are specified. Shown are the default
settings configured when Information Analyzer was installed.

Task 5. Log into and explore DataStage client functionality.

The DataStage Administrator client is used to configure and administer
DataStage projects.
1. Click the DataStage Administrator Client icon on your desktop. Enter a
DataStage user ID and password (here, student/student). Select the host
name of the services tier, here edserver:9443. Also select the host name of the
Information Server (DataStage) Engine, here EDSERVER.
2. Click Login and then select the Projects tab.

3. Select the DSProject DataStage project. Then click Properties to open the
Administrator Project Properties window. Explore each of the tabs.
4. The Environment button is used specify environment variables that control the
DataStage development and runtime environments.
5. The Permissions tab is used by a DataStage Administrator to specify
DataStage project user roles.
6. Close DataStage Administrator.
7. Optionally, use the same procedure to log into and explore DataStage
Designer. When you log into Designer you log into a specific project. Here, log
into the project named DSProject.

DataStage Designer is used by DataStage developers to build DataStage ETL

(Extraction, Transformation, Load) jobs. It is beyond the scope of this course to
discuss in more detail how this is done.
Task 6. Log into and explore the DataStage and QualityStage
Operations Console.
The Operations Console is used to monitor the Engine system and status and
to monitor DataStage job activities.
1. From the Information Server Launch Pad click the Operations Console link.
2. In the Login window, enter your user ID and password (student/student), and
then click Login.
The top left panel displays jobs that have run and are currently running on the
Engine. In this example, no DataStage jobs are running or have been running
over the last several days.
The top right panel displays the status of the Engine services. In this example,
all Engine services are running OK.
The bottom two panels display the CPU and memory resources on the system
running the Engine.

Optional Task. Log into and explore the FastTrack client.

FastTrack is used to build mapping specifications for DataStage jobs.
1. Double-click on the FastTrack icon on the desktop, and log into the FastTrack
client as student/student.
2. Explore FastTrack. Without knowing anything about FastTrack, there is not

much of interest that can be explored. It is beyond the scope of this course to
discuss how FastTrack works in more detail.
Close FastTrack when you are done exploring.
Results:
You have logged into and explored Information Server clients.

Unit summary
• Using the Information Server Launch Pad to access Information Server
thin clients
 Administrative Console
 Information Governance Catalog
 Metadata Asset Manager
• Accessing Engine clients
 DataStage / QualityStage clients
 FastTrack
 Information Server Manager
• Information Server Console clients
 Accessing Information Analyzer
 Accessing Information Services Director
Unit summary

Authentication and Suite Security
Authentication and Suite

Security

Unit 3 Authentication and Suite Security

Unit objectives
• Configure Suite Users and Groups
• Configure DataStage credentials for DataStage Engine users
Authentication and Suite Security © Copyright IBM Corporation 2015
Unit objectives

Topic:
Information Server user
configuration
Topic: Information Server user configuration

Assigning roles for access control

• Three types of roles
 Suite roles: Provide access to Suite-level clients, for example, IS
− Assigned using the IS Administration Console
 Suite Component roles: Provide access to specific IS products
− Assigned using the IS Administration Console
 Project-level roles: Roles defined within a specific IS product
− Example: For a specific DataStage project, a user can be assigned the role of
"Developer" or alternatively of "Operator"
− Assigned using administrative functionality within the specific project
• Suite and Suite Component roles can be assigned to users or groups
 Users added to a group inherit the roles of the group
Assigning roles for access control

There are three types of roles used to control access to Information Server products
and components. Suite roles control access to suite-level clients such as the
Information Server Administration Console. Suite Component roles control access to
specific Information Server products. In addition, some products have additional roles,
defined within the product, for controlling access to its objects and functions.
Roles can be assigned to individual users are to groups of users. Roles assigned to a
group are inherited by all users who are members of the group.

Suite roles
• Suite Administrator: Maximum privileges
• Suite User: Minimum requirement to access any IS suite component
or product
• Common Metadata Administrator
 Full functionality within Metadata Asset Manager to browse and manage
metadata assets
• Common Metadata Importer
 Required to import metadata assets into the Repository in Metadata Asset
Manager
• Common Metadata User
 Required to browse metadata assets in Metadata Asset Manager
Suite roles
There are four different types of Suite roles. The bottom three roles apply to Metadata
Asset Manager product and related tasks using istool.
There are two standard Suite roles: Suite Administrator, Suite User. A Suite
Administrator can log into the Information Server Administration Console and perform
any task, including creating user IDs. A Suite User has limited authority within the
Information Server Administration Console and other IS products. A Suite User can, for
instance, log into the Administration Console and view reports, but cannot create user
IDs.
The Suite User role is the minimum role required to do anything (requiring
authorization) within Information Server.

Suite Component roles

• Product Administrators: Information Analyzer Project Administrator,
Information Governance Catalog Glossary Administrator, DataStage
Administrator, etc.
 Create, configure, and manage projects and users
 Perform other administrative tasks depending on product
• Product component user: DataStage User, etc.)
 Use product component user functions, depending on authorizations assigned by
the product administrator
• Other specialized roles
 Information Governance Catalog Glossary Author: Create and edit catalog terms
and categories
 Information Governance Catalog Glossary Basic User: More limited than User
• Roles related to rule sets used by QualityStage, including:
 Rule Administrator: Administer who can access and run rules and rule sets
Suite Component roles

For each product there is a Suite Component Administrator role and a Suite
Component User role. Some products have additional specialized roles. The nature of
these roles differs depending on the product.
For example, with respect to DataStage, a user can be an Administrator or a User. An
Administrator has full authorization, including the ability to specify user project roles. A
User’s project authorizations are limited to those assigned by a DataStage
Administrator.

Creating IS users and groups

• Performed on the IS Administration Console Administration > Users
and Groups tab
 Requires Suite Administrator privileges
• Creating a Group
 Specify user ID (for example, DEV)
 Specify Name (IS Developers)
 Specify other attributes: email, organization, and so on
 Specify Suite and Suite Component roles
 Add users
− Users must already exist
• Creating a User
 Specify ID
 Name and other attributes
 Specify Suite and Suite Component roles
Creating IS users and groups

Security roles can be applied to users or groups. Users in the group inherit the roles
defined for the group.
When creating a user or group, the primary tasks are to specify the name of the user or
group and other attributes, and to specify the Suite and Suite Component roles that
apply to the user or group. Users are also given a password.

Creating a new group

• Click Administration > Users and Groups > Groups
• Click New Group
Groups New Group
Creating a new group

This graphic shows how to create a new group in the IS Administration Console
Administration tab. First click on Users and Groups > Groups on the
Administration tab. Then click New Group. This opens the window where you specify
the group attributes, shown on the next page.

Selecting group attributes and roles
Suite roles
Suite
Component
Group ID and other roles
attributes
Selecting group attributes and roles

This graphic shows the page where you specify the attributes of a group. Required
attributes include the group Principal ID and Name. In the Roles panel, select the
Suite roles for the group in the top panel, and select the Suite Component roles for the
group in the bottom panel.
In this example, the group ID is DEV. Two Suite roles have been chosen for the group
(Suite User, Common Metadata Administrator) and one Component role has been
chosen for the group (DataStage and QualityStage User).
Click the Browse button to add users to the group. These users must already be
defined.

Creating a new user

• Click Administration > Users and Groups > Users
• Click New User
Users New user
Creating a new user

This graphic shows how to create a new user in the IS Web Console Administration
tab. First click on Users and Groups > Users on the Administration tab. Then click
New User. This opens the window where you specify the group attributes, shown on
the next page.

Specifying user attributes

Groups user is a
member of
Suite roles
Suite
Component
roles
User ID and other

attributes
Specifying user attributes

This graphic shows the page where you specify the attributes of a user. Required
attributes include the User Name and Password. In the Roles panel, select the Suite
roles for the user in the top panel, and select the Suite Component roles for the user in
the bottom panel.
In this example, the user name is dev1. One Suite role has been chosen for the user
(Suite User).
Click the Browse button to add the user to one or more groups. These groups must
already been defined. Additional Suite and Suite Component roles will be acquired by
the user’s membership in these groups.
In this example, the user acquires the roles owned by the DEV group.

Topic:
Credential mappings
Topic: Credential mappings

Credential mappings
• By default the Information Server (DataStage) Engine uses a different
user registry, namely the Engine operating system, than Information
Server
• To use and access the Engine, a user ID must be mapped to an
Engine operating system user ID
• A default can be specified so that all (non-mapped) Information Server
user IDs get mapped to the same, default operating system user
• Credential mappings are specified in the Information Server
 Click Domain Management > Engine Credentials
Credential mappings
If Information Server and DataStage do not share the same user registry, which is the
default installation, then mappings must be created between Information Server user
IDs, having DataStage Administration or DataStage User roles, and user IDs that exist
locally in the operating system registry where DataStage is installed.
Assume that DataStage is using the operating system user registry, which is what it
uses by default. A credential mapping consists of mapping an Information Server user
ID (and password), who has a DataStage User or Administrator role attached to it, to an
operating system user ID (and password).
Alternatively, a single operating system user ID and password can be specified as the
default operating system user ID that all Information Server user IDs are mapped to.

Default credential mapping

• Click Administration > Domain Management > Engine Credentials
• Select the engine
 A single IS domain can contain multiple engines
• Click Open Configuration
Engine Open configuration
Engine credentials
Default credential mapping

Credential mappings are specified in the Information Server Administration Console in
the Domain Management > Engine Credentials folder on the Administration tab.
Begin by selecting the engine. In this example, there is only one engine to select, but
multiple engines are possible in a domain. Then click Open Configuration to open the
Engine Credentials window, shown on the next page.

Specify the default credential mapping

• Specify a user ID in the Engine user registry
 dsadm is a valid OS user
− Created as part of the IS Engine installation
• "Share User Registry…" must be unchecked
Engine operating
system user ID
Specify the default credential mapping

A default credential mapping can be specified in the Default Credentials panel,
highlighted in the graphic. Here you specify an operating system user name and
password on the Engine system.
This mapping will be applied to DataStage users that have not been given any explicit,
specific mapping. If you leave this blank, then every DataStage user must be explicitly
mapped to an engine system user.

User credential mappings

• Click Administration > Domain Management > Engine Credentials
• Select the engine
 A single IS domain can contain multiple engines
• Click Open User Credentials
Engine Open user credentials

Engine credentials
User credential mappings

This graphic shows how to map an individual DataStage user to an engine operating
system user ID. After selecting the engine, click Open User Credentials. This opens
the Map User Credential window, shown on the next page.

Individual credential mappings
Engine credentials
IS user ID
Engine OS user ID
Individual credential mappings

First click Browse to retrieve the Information Server user ID. Then specify the engine
system user ID and password it is to be mapped to. You must include both the engine
user ID and its associated password. Note that if the engine system ID password
changes, the mapping will no longer work and will have to be updated.
After you specify the engine system user, click Apply to complete the mapping.
In this example, dev1 has been mapped to dev1. Here, dev1 is a user with DataStage
authorization. Dev1 is also a user on the engine operating system. Notice also that
isadmin has been mapped to an Engine user. In this case the Engine user is dsadm,
which is, by default, a DataStage user created and/or configured during installation.

Demonstration 1

• Create an Information Server group
• Create an Information Server user
• Provide Engine credentials to a user
Demonstration 1: Authentication and Suite Security

Demonstration 1:
Purpose:
In this unit, you learn how to create users and groups in the Information
Server Administration Console.
Task 1. Create an Information Server group.

1. From the Information Server Launch Pad click the Administration Console
link.
2. Log into the Information Server Administration Console as isadmin/isadmin,
and then click the Administration tab.
3. Expand Users and Groups, and then click Groups.

4. Click New Group.

• Type DEV in the Principal ID box.
• Type IS Developer in the Name box.
• In the Roles panel expand the Suite folder and then select Common
Metadata Administrator and Suite User
• Expand the Suite Component folder and then select DataStage and
QualityStage User.
5. Click Save and Close.

Task 2. Create an Information Server user.
1. Expand Users and Groups, and then click Users.
Notice that there are several users already created including student, which
you have been using to log into clients: isadmin, the default Information Server
administrator ID created during Information Server installation, which you have
been using to log into the Administration Console, and wasadmin which is the
default WebSphere Application Server (WAS) user ID.

2. Select isadmin and then click Open User.

Notice this user ID’s Suite roles:
• Common Metadata Administrator, which enables isadmin to import and
manage information assets.
• Suite Administrator, which gives isadmin maximum privileges in the Suite.
3. Notice isadmin’s Suite Component roles.

Essentially isadmin has administration roles in all Information Server products
and components.
4. Click Cancel, and then open user student and examine its Suite and Suite
Component roles.
Notice it has all roles!

5. Define a new user named dev1. For simplicity here, type dev1 in all required
fields (the fields with the asterisks).
6. Expand the Suite folder, and then select the Suite User role (which by default
is selected).
This role is required by every Information Server user.
7. Expand the Suite Component folder, and then select the Information
Governance Catalog User role.
This will allow dev1 to use browse information assets in the Information
Governance Catalog.

8. Click Browse in the Groups panel, select the DEV group, and then click OK.
This gives dev1 the developer roles the DEV group possesses.
9. Click Save and Close, and then verify in the Users list that the new user, dev1,
has been created.
Task 3. Provide Engine credentials to a user.
1. Click Domain Management > Engine Credentials.
2. Select the Engine (edserver), and then click Open user Credentials.
3. Browse for user dev1 and add dev1 to the Map User Credentials list.

4. With dev1 selected, type in credentials for this user in the Assign User
Credentials area. Map dev1 to dsadm / dsadm, which is a valid OS user on
the DataStage Engine system.
5. Click Apply.
You should see dev1 mapped to dsadm.
You may be wondering whether you can now log into DataStage using the dev1
ID, since you have both created the user ID and given it DataStage credentials.
The answer is that you cannot, because dev1 still needs to be given
authorization to log into a DataStage project from a DataStage administrator.
This is done in the DataStage Administrator client on the Permissions tab.
Results:
You learned how to create Information Server users and groups.

Unit summary
• Configure Suite Users and Groups
• Configure DataStage credentials for DataStage Engine users
Unit summary

Session management
Session management

Unit 4 Session management

Unit objectives
• View a list of active sessions
• View session properties
• Disconnect sessions
• Configure global session properties
Session management © Copyright IBM Corporation 2015
Unit objectives

Client session management

• Each user connection to Information Server results in the creation of a
client session
 Two connections with the same user ID result in the creation of two
sessions
• A session has a timeout and expires if not "touched"
• While a client is active, it "touches" the services tier on a regular basis
to avoid expiration
 If a client crashes, the session will expire
• A session can be disconnected by an Information Server administrator
 From the Information Server Administration Console
 No warning sent to the client
• Repository services are listening to the session and are notified when a
session disappears
 The services then can remove cached objects, locks, and so on
Client session management

Each user connection using an Information Server client results in the creation of a
session. A user can log into multiple clients as the same time. Each established
connection creates another session.
A session will timeout and expire if nothing happens in it for an extended period of time.
Alternatively, a session will cease if the user closes the client or if an Information Server
administrator stops it. The latter can be done in the Information Server Administration
Console.

Viewing active client sessions

• Log into Administration Console using a Suite administrator ID (isadmin)
• On the Administration tab, click Session Management > Active Sessions
 The active client sessions are listed
 The address or hostname of the client is provided
• Select a client session and then click Open to get more details about the session
 User information: user attributes, user security roles
 Session duration
• Click Global Session Properties to specify general session properties
List of active sessions Client type
Viewing active client sessions

User sessions can be managed by an Information Server administrator in the
Information Server Administration Console. On the Administration tab, click Session
Management > Active Sessions. The current active sessions are listed.
In this example, there are three active sessions. The Type column identifies the type of
session. The first session was established when the administrator isadmin logged into
the Administration Console. The third session was established when a user logged into
DataStage Designer. The second session was established when a user logged into
Information Analyzer.
The Session ID column identifies the unique identifier of the session.
To open or disconnect a specific session, select the session and then click the
appropriate link in the right panel (not visible in the screenshot).
Click Global Session Properties (not visible) to specify general session attributes.

Global session properties
Session
properties
Global session properties

This graphic shows the Global Session Properties window.
Each session consumes WAS and engine resources. At some point as more and more
sessions are established performance will begin to deteriorate. You can limit this
deterioration by reducing the maximum number of sessions.
The maximum number of sessions determines how many users can log into
Information Server applications at one time. A user, other than an Information Server
administrator logging into the Web Console, will be unable to log into an Information
Server client after the maximum has been reached. Users will receive a message that
they are unable to log in because the maximum has been reached.
If too many users are "bumping into" the maximum, you can try reducing the inactive
session timeout period. This will free additional sessions.

Session details
Session
properties
User
attributes
Session details
Select a session and then click Open to view details about it and the user logged into
the session. In this example, a user named student is logged into the session.
Information about that user, including the authorization roles the user possesses is
displayed.
Some information about the session is also displayed, including its duration and the
number cached objects, which indicates how many resources the session is
consuming.

Disconnecting sessions
• To disconnect specific sessions:
• From the Active Sessions tab, select the connections you want to
disconnect
 Click Disconnect
• To disconnect all sessions (including your own session)
 Select Disconnect All
Disconnect all users
Disconnect selected
users
Disconnecting sessions
You can disconnect active sessions by selecting the sessions and then clicking
Disconnect. You can also disconnect all sessions by clicking Disconnect All. Note
that this will also disconnect your session in the Administration Console as well as all
others.

Demonstration 1
Session management

• Manage active sessions
Demonstration 1: Session management

Demonstration 1:
Session management
Purpose:
You will learn how to manage sessions using the Information Server
Administrative Console.
Task 1. Manage active sessions.

1. Log into DataStage Designer DSProject as student / student.
This will create one session.
2. Log into the Information Server Console as student / student.
This will create another session.
3. Log into the Information Server Administration Console as isadmin / isadmin.
This will create a third session.
4. On the Administration tab, click the Session Management > Active
Sessions folder.
You should see the three sessions that were created when you logged into
DataStage Designer, Information Server Console, and the Administration
Console.
Notice that type displayed for each session. The Administration Console type is
listed as "Web Console". The Information Server Console type is listed as
"Console".

5. Select the session that is labeled as a Console type.

This should be your Information Server Console session.
6. Click Open to view details about the session.
Notice session details such as the session duration as well as details about the
user, including the user’s authentication roles and user attributes.
7. Click Close to close and return to the Active Sessions list.
8. With the same session selected, click Disconnect and complete the process of
disconnecting the session.
Outside of the Administration Console, notice that the Information Server
Console session has been terminated (stopped working).
9. Back in the Administration Console, click Global Session Properties, increase
the inactive session timeout period to 180000 seconds, and then click Save and
Close.

10. On the Active Sessions tab, click Disconnect All.

Notice this kills the Administration Console session as well as the other
sessions.
However you will notice some interesting behavior when you open up
DataStage Designer. DataStage Designer will attempt to establish a session
that has been disconnected. So after a couple of minutes DataStage Designer
will start working again.
Results:
You learned how to manage sessions using the Information Server
Administrative Console.

Unit summary
• View a list of active sessions
• View session properties
• Disconnect sessions
• Configure global session properties
Unit summary


Managing reports
Managing reports

Unit 5 Managing reports

Unit objectives
• Create and manage report folders
• Create a report
• Run a report
• View report results
• Control report access
Managing reports © Copyright IBM Corporation 2015
Unit objectives

Reporting administration
• Managed on the Information Server Administration Console Reporting
tab
• Reports can be created about Suite component activities and
administrative functions
• Report formats include: HTML, PDF, RTF, TXT, XML
• Access to reports, report templates, and report results can be
restricted
• Reports are organized into folders
 Root folder is named Reports
 Additional folders can be created
− Folders can only be created by Information Server administrators
Reporting administration
Information Server reporting is managed through the Information Server Administration
Console Reporting tab. The Reporting tab, contains a folder of templates to build your
reports, and a set of folders you can use to store your reports. Access to reports, report
templates, and report results can be restricted.
Reports are stored and organized in folders. Folders can only be created by Information
Server administrators.

Creating a new report folder

• Select the folder in which the new folder or folders are to be created
 Multiple folders can be created
 Separate folder names by forward slashes to create folder paths
• Click New
Selected base folder
New folder New report

path
Creating a new report folder

To create a new report folder, first select a base folder. Then click New. The new folder
will be created under the base folder. You can create multiple folder paths at a time. A
folder path consists of the names of folders separated by forward slashes. Each folder
in the path will be created. The folder named after the forward slash will be created as a
sub-folder of the folder named before the slash.
Use separate lines to create multiple folder paths in a single operation.

Creating a report
• Select a report template
 Report templates are organized by Suite product or component
 Example for Administration: "List of users"
• Click New Report
• Browse for report folder
• Report settings
 Name
 Parameters
− Vary depending on report type
− Example: DataStage projectname
 Format: HTML, PDF
 Settings include: Expiration, History policy
Creating a report
There are a number of pre-build reports that can be run from within Information Server
products.
New reports can also be created on the Reporting tab. You begin by selecting a report
template. Information Server administrators have access to all of the report templates,
but not all templates are available to all users. Then you specify the report settings in
the new report.
When you create a report you specify the folder to store the report in. The folder must
already exist at the time you create the report.
Several output formats are supported, including HTML and PDF.

Selecting the report template
Selected template New report
Selecting the report template

In this example, the selected report template is List of users from the
Administration > Security folder of report templates. After you select the template
click New Report.
Notice that there are administration report templates as well as report templates for
specific Information Server products.

Editing the report
Report folder
Add report to
Report name favorites folder
Report parameters
Report format (html)

and settings (hidden)
Editing the report

In this List of users example, the Reports/Security/Users folder has been selected
for its storage.
Select the Add to Favorites box to have this report listed in your Favorites view list.
Report parameters are specific to the type of report being created. In this example,
users with product roles are being selected. The specific product is DataStage.
The output report format is a mandatory parameter. This parameter is not visible in the
graphic, but has been set to HTML.

Viewing a list of your reports

• Click My Reporting to view the reports you have created
 Select a View in the left panel to choose how the reports are listed
− In this example the Favorites view has been selected
• Select one or more reports to perform an action upon:
 Click Run Now to run the report
− Optionally specify additional parameter values that were left undefined
 Click View Report Result to view the results of report runs
View results
Selected report
Run report
Viewing a list of your reports

You have a few options for viewing the reports you have created. Click Recent
Reports to view a list of reports. Click Favorites to view the reports you designated as
favorites when you created them.
Keep in mind that creating a report is not the same as running a report. You create the
report once, but you can run it many times. Each time you run the report a new report
result occurs. These report results are saved and can be viewed multiple times.
To run a report and thereby create a report result, first select the report and then click
Run Now.

Report results
Report results
The graphic shows an example of a List of Users report results. This is available after
the report is run. In this example, the users and their user attributes are listed.
The criteria by which this list of users was chosen is described in the bottom half of the
upper panel. In this case, this report selects users who have one or more DataStage
product roles.
When you create a report you optionally specify report parameters. When you run the
report you are given the opportunity to specify additional report parameters that apply to
just this report run.

Report access control

• Click Open Access Control to specify access permissions
• Browse for users to give access to the report
• Specify user's access permissions: Update, Delete, Run,
Administration
 Users with Information Server administration credentials can specify
access rights for other users
User permissions
Report access control

This window is displayed if you click Open Access Control on the Reports panel. In
this example, isadmin (the user who created the report) and other Suite administrators
automatically have access to the report. There are several layers of access that can be
allowed or restricted, including the ability to read, update, delete, run, and administer
the report. In this example, only isadmin can administer the report, that is, specify
access control for it. Other Suite administrators can view, delete, and run it, but not
administer it.
You can browse for users, groups, and roles to add to the access control list. Then you
can specify what authorizations they have. In this example user dev1 has been added.
Added users are automatically given read access to the report. dev1 has been given
the additional permission to run the report and view the run results.

Demonstration 1
Managing reports

• Create a report folder
• Run a report
• Specify report access control
Demonstration 1: Managing reports

Demonstration 1:
Managing reports
Purpose:
You will learn how to manage reports.
Task 1. Create a report folder.

1. Log into the Administration Console as isadmin/isadmin.
2. Click the Reporting tab.
3. Click Reports > Folder Management.
4. Select the existing Reports folder, and then click New.

5. In the New Folders window, type Security/Users.
This creates two folders, the second embedded in the first.

6. Click OK.
The new report folders are displayed.
Task 2. Create a report.

1. Expand the Report Templates > Administration > Security folder, click View
Report Templates, and then select the List of users template.
2. Click New Report to open a new report form.

3. In the new report template, browse to the /Reports/Security/Users folder.
4. Select the Add to Favorites box.
5. Change the name of the report to IS Users.

6. In the Role Type box, select Suite.

7. In the Components box, select Information Server.
8. Output Format is the only required option. Select HTML.
9. In the Settings folder, select Expire After 4 Days.
10. Click Finish > Save and Close from the Finish menu in lower right portion of
the window.
You will be returned to the Report Template to Work With window.

Task 3. Run a report.

1. Click My Reporting > Favorites.
Your report is displayed.
2. Select the IS Users report, and then click Run Now.

The Set Run Parameter Values panel is displayed where you can optionally
specify values for undefined fields in the Report Settings folder.
3. Click Run Now.

4. Click Report Result Status, which displays a list of the latest report executions.
5. Select your report execution, and then click View Report Result.
6. Close the report execution browser tab to return to the report execution list.
Task 4. Specify report access control.
1. Select Favorites.

2. Select your IS Users report and then click Open Access Control.
3. Click Browse, and then add student to the access control list. Afterwards click
OK.
When a user is added, the user automatically has read access to the report.
4. In addition, give student access to run the report.
5. Click Save and Close.

Results:
You have learned how to manage reports.

Unit summary
• Create and manage report folders
• Create a report
• Run a report
• View report results
• Control report access
Unit summary


Administrative tools

Unit 6 Administrative tools

Unit objectives
• Run the SessionAdmin tool
• Run the DirectoryCommand tool
• Run the Encrypt tool
Administrative tools © Copyright IBM Corporation 2015
Unit objectives

Topic:
Session management
using SessionAdmin
Topic: Session management using SessionAdmin

SessionAdmin tool
• Used to manage and monitor active Information Server sessions
• Command line tool
 Duplicates session management functionality performed in the
• To run the tool:
 Open a command window
 Change to the \InformationServer\ASBServer\bin directory
 Run the command with necessary parameters
− Most parameters require a value following the parameter keyword
• Parameter keywords are preceded by a dash
SessionAdmin tool
The SessionAdmin tool is the command line equivalent of the session management
functionality available in the Administration Console. This command line tool is available
in the \InformationServer\ASBServer\bin directory. To run the command first open an
operating system command window.

Running the SessionAdmin command

• Use the –url parameters to connect to the IS server system:
 Example: DirectoryCommand –url https://edserver:9443
− Here "edserver" is the host name of the server
• Optionally use the –user and –password parameters to specify an
Information Server administrator user ID and password
 If omitted you will be prompted
• Specify one or more additional parameters
• Example: SessionAdmin –url https://edserver:9443 –user isadmin
–password isadmin –lus
 -lus is an abbreviation –list-user-sessions
Running the SessionAdmin command

You use the -url parameter to specify the connection to the IS server system. The URL
contains the host name of the server followed by the port number used to connect to it.
The -user and -password parameters are used to specify the user connecting to the
server. In this case, since this is an administrative command, you should provide an
Information Server administrator IS such as isadmin. If you do not specify these
parameters in the command you will be prompted for a user ID and password when the
command is run.
Following these parameters you will specify one or more additional parameters
depending on the administrative task you are performing. For example, you might add
the -lus parameter to list all user sessions.

Listing active sessions

• Each session lists the session owner followed by the session ID
followed by additional information including:
 Session type
 Session date
• You can kill specific sessions using the session ID
Session ID
Listing active sessions

In this example the -list-user-sessions parameter has been used to list all active user
sessions.
The information displayed is similar to what you would see if you listed all user sessions
in the Administrative Console, although there are a couple of minor differences. One
difference is that the session of running the SessionAdmin command is listed when
your run the command, but this session does not show up in the Administration
Console. And the terms used to express the session types are a little different in some
cases.
One reason you might want to list the sessions is to determine the session IDs. These
session IDs can be used in other SessionAdmin commands to kill a session. Since
these session IDs are somewhat long, you may want to write the output of this
command to a file from which you can copy the IDs.

Killing active sessions

• List all sessions to determine the session ID
• Use one or more occurrences of the –ks (-kill-session) parameter
followed by the session IDs
-ks parameter
Killing active sessions

In this example, the -ks parameter is used to kill a particular session. The list all
sessions parameter was previously used to determine the session ID of the session to
be killed.
The -ks parameter can be used multiple times in a single command in order to kill
multiple sessions at one time.

Topic:
User management using
DirectoryCommand
Topic: User management using DirectoryCommand

Topic:
User management using
DirectoryCommand
Topic: User management using DirectoryCommand

The DirectoryCommand tool is the command line equivalent of the user management
functionality available in the Administration Console. This command line tool is available
in the \InformationServer\ASBServer\bin directory. To run the command first open an
operating system command window.
Running the DirectoryCommand tool is similar to running the SessionAdmin tool.

Directory Command tool

• Used to manage user authorizations
 Create/remove users and user groups
− Assign roles
 Map DataStage credentials
 Assign/remove DataStage project roles
 Duplicates user management functionality performed in the Administration
Console
 Contains additional functionality not available in the Administration Console
 Run the command with necessary parameters
− Most parameters require a value following the parameter keyword
• Parameter keywords are preceded by a dash
Directory Command tool

The DirectoryCommand tool uses the -url and -user and -password parameters in
the same way as the SessionAdmin tool.
Additional parameters include the -list parameter which can be used to list objects. The
tilde (~) is used to separate more than one type of object to be listed. In this example
-list USERS~GROUPS lists all Information Server users and groups.

Listing users and groups

• Use the –list parameter followed by one or more of the following
values separated by the tilde (~): USERS, GROUPS, ROLES,
DSPROJECTS (DataStage project roles), ALL
• Example: -list USERS~GROUPS~DSPROJECTS
 Lists users, groups, DataStage projects
Listing users and groups

In this example the -list parameter has been used to list DataStage projects as well as
users and groups.

Creating users
• Use one or more instances of the –add_user parameter followed by a
user information string with values separated by the tilde (~):
userID~password~firstName~lastName…
 Example: -add_user dev2~dev2~Nelsen~Rock
• To add a user to a group use the –add_users_group parameter
 Example: -add_users_group dev1~dev2$DEV
− Here users dev1 and dev2 are added to the DEV group
− Here the dollar sign ($) is used to separate the users list from the name of the
list of groups
Creating users
In the top graphic, the -add_user parameter has been used to create a new user. The
user information is separated by occurs of the tilde. In this example the user information
includes the user ID, password, first name, and last name. Additional information can
be added.
In the bottom graphic, the -add_users_group parameter has been used to add the
users just create (dev1 and dev2) to a group named DEV. The dollar sign ($) is used to
separate the string of user names from the group name. The user names are separated
with the tilde.

Topic:
Encrypt passwords using
the Encrypt command
Topic: Encrypt passwords using the Encrypt command

Encrypt command
• Provides a method to encrypt user credentials
 Run the command with or without the text to be encrypted
 Copy the encrypted string as a value to the password parameter of any
commands that support it
Encrypt command
The encrypt command provides a method for encrypting a string. Generally it is used
to encrypt passwords. Like the other tools we have discussed the encrypt command is
found in the \InformationServer\ASBServer\bin directory.

Encrypt command example

• Encrypt the password for user dev3, the password is "dev3"
 In this example, the encrypt command writes the encrypted password to a file where it can be
easily copied
• Run the DirectoryCommand command with the encrypted password to add user
dev3
• The newly added user dev3 can now log into IS products using "dev3" as
the password
• Notice that encrypted passwords are prefixed by the name of the encryption
provider in curly brackets: {iisenc} Encrypted password
written to a file
Encrypted password
Encrypt command example

In the graphic the string "dev3" is encrypted. This is a password for user dev3. Since
the encrypted password can be very long, it might be helpful to send the output to a file,
as shown in the second example in the graphic.
The encrypted password can now be used to replace the password in supported
Information Server commands. In the third example in the graphic, the encrypted
password is used in the -add_user parameter instead of the unencrypted password.
Notice that encrypted passwords are prefixed y the name of their encryption provider.
Encrypted passwords generated by the encrypt command are preceded by the string
"{iisenc}".

Creating a credentials file

• The credentials file contains user credentials that can be used by IS
commands that support the –authfile parameter
• Must contain user name and password parameter value pairs on
separate lines:
 The password can optionally be encrypted
 Example: user=isadmin
 Example: password={iisenc}EH/z9tfjAQ/9E+fg/x8rFw==
 Optionally can contain additional parameter name value pairs depending
on the command it is used with
Example credentials
file with encrypted
password
Creating a credentials file

A credentials file contains user credentials that can be used by Information Server
commands and tools that support the -authfile parameter. This avoids having to display
the credentials when executing the command. The password inside the credentials file
can be encrypted to provide additional security.
A credentials file requires a specific format. The name of the parameter specified inside
the file is followed by an equal sign (=) and then the value, without spaces. Each
parameter must be specified on a separate line. In the example shown, the credentials
file contains a parameter named user and a parameter named password followed by
their values.
The -authfile parameter is used to specify the name and location of the credentials file.

Example using command with credentials file

• The –authfile parameter is used to specify the path to the credentials
file
Credentials file
Example using command with credentials file

The -authfile parameter is used to specify the name and location of the credentials file.
The path to the file is specified (without surrounding quotes) after the parameter name
as shown in the example.
In the example, the DirectoryCommand tool is run to list users and groups. The -
authfile parameter has been used in place of the -user and -password parameters.

Demonstration 1

• Use the SessionAdmin tool to manage and monitor sessions
• Use the DirectoryCommand tool to list users and groups
• Use the DirectoryCommand tool to create a user and add the user to a group
• Create a credentials file with an encrypted password
Demonstration 1: Administrative tools

Demonstration 1:
Purpose:
You will use command line tools to perform administrative tasks.
Task 1. Use the SessionAdmin tool to manage and monitor

sessions.
In this task you will create some sessions and view them in the Administration Console
just as you did in an earlier demonstration. Then you will manage these sessions from
the command line using the SessionAdmin tool.
1. Log into DataStage Designer DSProject as student / student.
This will create one session.
2. Log into the Information Server Console as student / student.
This will create another session.
3. Log into the Information Server Administration Console as isadmin / isadmin.
This will create a third session.
4. On the Administration tab, click the Session Management > Active
Sessions folder.
You should see the three sessions that were created when you logged into
DataStage Designer, Information Server Console, and the Administration
Console.
Notice the type displayed for each session. The Administration Console type is
listed as "Web Console". The Information Server Console type is listed as
"Console."
5. Open up a Windows command window. To do this click Start > Run and then
open with cmd.

6. Change to the c:\IBM\InformationServer\ASBServer\bin directory.
7. Each time you run the SessionAdmin command you should use the following
parameters:
• –url https://edserver:9443 to connect to Information Server
• –user isadmin –password isadmin to authenticate with Information Server
8. Enter the command to list the user sessions. This uses the –lus (-list-user-
sessions) parameter.
Note: This command and others are contained in the Commands.txt file in
your ISAdmin1_Files folder.
Compare the session information displayed by the command to the information

displayed in the Administration Console.
• Notice that there are some differences in how the session types are
designated. The biggest difference is that the Information Server Console is
classified as "Console" in the Administration Console but as "Mozart" in the
command display.
• Notice that the command lists one additional session of type "Command". The
command appears to list itself as an active session, but the Administration
Console does not list it.
9. Enter the command to kill the Information Server Console session.
• Use the –ks (-kill-session) command to accomplish this.
• The easiest way to do this is to retrieve the previous command, using the Up-
Arrow and then modifying it.

• The most difficult part of doing this is typing the session ID. One way to make
this a little easier is to first run the –lus command to a temporary file. Then you
can copy and paste the session ID into the command to kill the session.
Task 2. Use the DirectoryCommand tool to list users and

groups.
1. Log into the Administration Console, and then click Users and Groups > Users
and Users and Groups > Groups to review the list of users and groups
displayed in the Administration Console.
Here are the users.

Here are the groups.
2. In a command window change to the

c:\IBM\InformationServer\ASBServer\bin directory.
3. Each time you run the DirectoryCommand command you should use the
following three parameters:
• –url https://edserver:9443 to connect to Information Server
• –user isadmin –password isadmin to authenticate with Information Server
4. Enter the command to list users and groups.
• Use the –list parameter followed by the types of objects to list. The USERS
value indicates user IDs. The GROUPS value indicates groups. Use ALL to
list everything. Separate multiple objects names using the tilde (~).
5. Compare the list you get from the command with the list displayed in the
Administration Console. My lists were the same.

6. Run the same command using the –list ALL parameter.
Notice that in addition to the users and groups, you get a list of all the user roles
and a list of all the DataStage projects.
Task 3. Use the DirectoryCommand tool to create a user and
add the user to a group.
1. Run the DirectoryCommand command to create a user ID named dev2,
password pass2, first name Nelsen, last name Rock.
2. Use the –add_user parameter followed by a user information string with values
separated by the tilde (~):
• userID~password~firstName~lastName
3. Verify in the Administration Console that the user was created. (You may need
to refresh the Administration Console to see the new user.)

4. Add user dev2 to group DEV.

• Use the –add_users_group parameter followed by a value string of the form
userID$groupID.
5. Verify in the Administration Console that the user has been added to the group.
Here group DEV has been opened in the Administration Console. Notice that
dev2 is listed as a user in the group in the right panel.
Task 4. Create a credentials file with an encrypted password.
In this task you will create a credentials file for user isadmin whose password is also
isadmin.
1. In a command window change to the
c:\IBM\InformationServer\ASBServer\bin directory.

2. Run the encrypt command to encrypt the password isadmin. Write the result
to a temporary file named ISCredentials.txt in the c:\Temp directory.
3. Open up the ISCredentials.txt file. Alter it so that it conforms to the format of a

credentials file: user=username, password=passwordValue placed on
separate lines.
4. Run the DirectoryCommand command to list users and groups using the
–authfile parameter to invoke the credentials file your created in the previous
step.
Results:
You have used command line tools to perform administrative tasks.

Unit summary
• Run the SessionAdmin tool
• Run the DirectoryCommand tool
• Run the Encrypt tool
Unit summary


Managing Information Server repository assets
Managing Information Server

repository assets

Unit 7 Managing Information Server repository assets

Unit objectives
• Use istool to export common metadata assets
• Use istool to query information assets
• Use istool to export security assets
• Use istool to export reporting assets
• Use istool to export individual product assets
Managing Information Server repository assets © Copyright IBM Corporation 2015
Unit objectives

What is asset interchange?

• Export of metadata from an Information Server repository followed by the
import of this exported metadata into the same or another repository
• You specify a set of related assets in the source repository
 Then export them to the file system and create an archive
 This archive is used to import the group of related assets into the target repository
− Relationships to other assets in the source can be optionally carried over to the
target repository
• istool can be used for asset interchange on both Client and Engine tiers
 On Client, invoke IS Command Line Interface client
 On Server, istool is located in /InformationServer/Clients/istools/cli directory
• istool commands are available to export metadata assets produced by
all IS products
• istool commands are also available for administrative and management
metadata
 Security user / group roles
 Reports
What is asset interchange?

Asset interchange consists of the export of metadata from an Information Server
repository followed by the import of this exported metadata into the same or another
repository. You specify a set of related assets in the source repository to export to an
archive file. For the import you specify a set of related assets to import from an archive
file.
The istool command can be used to perform the interchange.

istool commands
• Engine management:
 Build and deploy DataStage packages
− Packages contains DataStage jobs and supporting assets
 Purge DataStage operational metadata
• IS Repository asset management
 Delete common metadata assets
 Export and import information assets to and from a file
− Individual product assets, e.g.:
• DataStage jobs
• Governance catalog assets
− Common Repository information assets, e.g.:
• Database assets
− Reporting assets
− Security assets
istool commands
Our focus in this unit is on using istool for asset management. This includes deleting
information assets from the Information Server repository as well as the import and
export of information assets.
The Information Server Repository contains a number of different types of information
assets including common repository assets such as database assets, reporting assets,
security assets, and individual products assets such as DataStage jobs and Information
Governance Catalog governance assets. Different parameters are used to handle
these different types of assets.

Invoking istool
• Command-line interface
 Syntax of the istool command is:
− istool <command> <authentication_parameters> <archive> [ archive
parameters ]
−[ generic_params ][ command specific_parameters ]
 Generic parameters: -help, -verbose, -silent
 Authentication parameters: -domain, -username, -password
− Alternatively you can use the -authfile parameter to specify a credentials file
− If -domain is not specified, the primary domain server is assumed
Invoking istool
The istool utility is very powerful. It supports four basic commands: export, import,
build package, and deploy package. The build package and deploy package
functionality has been captured into the Information Server Manager tool. It is part of
DataStage administration and is not covered in this course.
There are two common parameters in the istool command. You will always need to
specify authentication, that is, the services domain you are logging into and the user ID
and password you are using to do so. The istool command supports the -authfile
parameter so that a credentials file can be used for authentication.
Secondly, you will always be specifying a path to the archive file. The archive file is
where the exported assets are or will be stored on the file system, during an import or
export.

Asset interchange archive

• Uses an archive format called ISX
 Java archive that can be viewed with the jar utility provided with the Java
SDK, WinZip, and other archiving tools
 Archive contains a manifest file and a set of files containing the serialized
assets
Asset interchange archive

The istool command uses an archive format called ISX. The archive contains a
manifest file and a set of files containing the serialized assets.
The archive file is a compressed, non-proprietary file. Its contents can be viewed by
standard tools such as WinZip and the Java SDK.
An archive consists of a manifest file, which describes the contents, and a set of files
that contain the assets.

Topic:
Exporting common
repository metadata
Topic: Exporting common repository metadata

Exporting common metadata assets

• Use the export command with the -commonmetadata (-cm)
parameter
 The -cm parameter is followed by one or more identity strings and options
enclosed in single quotes
− The identify strings identify the assets to be exported
• Use the -archive parameter to specify the *.isx file the assets are
exported to
 The path must be surrounded by quotes
• Common metadata assets include:
 Database assets
 Data model assets
 Data connections
Exporting common metadata assets

Common metadata assets include database assets, data model assets, and data
connections. The -cm parameter is used.
You follow the -cm parameter by one or more strings that identify the assets and
additional options. These values must all be surrounded by single quotes.
The -archive parameter is used to specify the archive file, which has an .isx extension.
The name and path of the archive file must be surrounded by double quotes.

Identity strings for database assets

• Identify strings identity the assets to be exported
 Extensions identify the type of asset
 An asterisk (*) can be used a wild card character
 The full identity string contains a hierarchy of assets separated by forward slashes
(/)
• Database assets include:
 Host: /host_name.hst
 Database: /host_name/database_name.db
 Database schema: /host_name/database_name/schema_name.sch
 Database table: /host_name/database_name/schema_name/table_name.tbl
• Example: '/EDSERVER/SAMPLE/STUDENT/CUSTOMER.tbl'
 Identifies the CUSTOMER table in the STUDENT schema of the SAMPLE
database of the EDSERVER host
• Example: '/EDSERVER/SAMPLE/STUDENT/*.tbl'
 Identifies all tables in the STUDENT schema of the SAMPLE database of the
EDSERVER host
Identity strings for database assets

Identity strings are used to identify the assets to be exported. Predefined extensions
identify the type of assets. For database assets use the .hst extension to identify the
hosts, the .db extension to identify the databases, the .sch extension to identify the
database schemas, and the .tbl extension to identify the database tables. You need to
provide the full path to assets you are exporting. For a database table this consists of
the host name followed by the database name followed by the schema name followed
by table name. Use forward slashes to separate asset types.
Use the asterisk (*) as a wild card character. For example
'/EDSERVER/SAMPLE/*/*.tbl' identifies all table assets in all schemas of the database
named SAMPLE.

Common metadata export example

• Export all database tables in the SAMPLE database STUDENT
schema starting with "E"
• Use the -authfile parameter to reference a credentials file
Archive path
-cm parameter with

identity string
Common metadata export example

The istool command is executed from the Information Server command line. When this
command window is opened the istool> prompt is displayed. Since istool is in the
prompt you do not type it as part of the command.
In this example, the -authfile parameter has been used to specify a credentials file. The
-archive (-ar) parameter has been used to specify the parameter file. Notice that the
path to the parameter file is surrounded by double quotes and that the file extension is
.isx.
An identity string follows the parameter (-cm) for common metadata. Notice that the
identity string is surrounded by single quotes.

The query command

• Retrieve a list of one or more common metadata asset types
• Use one or more identity strings with wildcards to identify the asset
types
 Separate multiple identity strings with spaces
• Example: Retrieve a list of schemas of all databases on all hosts:
query … -cm '/*/*/*.sch'
• Optionally specify an output file using the -outputfile (-of) "filepath"
parameter
 If not specified, results are written to a default output file
Output file
The query command

In this example, the query command is used to list common metadata assets in the
Information Server Repository. Again identity strings are used to identify the assets
following the -cm parameter. In this example the command requests a list of all
schemas in all databases on all hosts.
The output of the query command is written to a file. The -outputfile parameter is used
to specify this file. If you do not specify an output file explicitly the output will still be
written to an output file at a default location.

The query command output file

• The identify strings of the specific assets are listed
Identify strings
The query command output file

This shows the output from the query command. It lists all the schema assets. Notice
that identity strings are used to identify the assets found.

Topic:
Exporting security assets
Topic: Exporting security assets


• Use the -security parameter followed by security specific parameters:
 Use '-securityUser …' to export user assets
 Use '-securityGroup …' to export user assets
 Surround with single quotes
 Use the -userident or -groupident sub-parameter to identify users and
groups
− Users and groups are identified by name with optional wildcard characters
 Additional sub-parameters can be included
• Use to export Information Server users and groups
 Users and groups must be exported using separate commands
 Users and groups are exported by name
 Can include related metadata such as credential mappings

The istool command can also be used to export security assets, including users and
groups and their authorization roles. The -security keyword is used in the istool
command to specify users and groups to import or export as part of the archive.
Related metadata such as credential mappings can also be included.
Like with the -cm parameter, what follows the -security parameter must be surrounded
by single quotes. This includes options (or sub-parameters) that are used to specify the
types of assets to be exported.

Security export example

• Export all users to an archive file
• Include user group relationships
• Include user Suite and Component roles
Identify users (all) to

export Archive path
-security parameter
Security export example

The -preview parameter

• Previews a list of the assets that will be exported when the export runs
Preview parameter
The -preview parameter

You can use the -preview option in both exports and imports. Here it is illustrated for
use in the export command. It allows you to preview what will be done when the
command runs without running the command. This can provide a good check on
whether you have specified the command correctly before actually running the
command.

Topic:
Exporting reporting assets
Topic: Exporting reporting assets


• Use the -report parameter followed by one or more of the two
following parameters enclosed in single quotes:
 Use '-reportName…' to export reports by name
− Example: '-reportName "MyRep*"'
 Use '-ownedByProduct…' (-prod) to export reports associated with
specific products or components: Administration, Information Analyzer,
QualityStage
− Example: '-prod "QualityStage"'
• -reportName and -prod can contain additional parameter options:
 includeAllReportResults
 includeReportResultName

The -report parameter is used to export reporting assets. You can export reports based
on their names or based on the products they apply to. Use the -reportName
parameter to export by name. Use the -ownedByProduct parameter to export based
on the product. These parameters must be enclosed in single quotes.
The -reportName and -ownedByProduct parameters must be followed by strings in
double quotes. These strings identify either the report name or product name and they
can include wild card characters.

Exporting reporting assets example

• Export all reports by name
• Include report results
-reportName
parameter
Exporting reporting assets example

In this example, the -report parameter is used with the -reportName sub-parameter to
export reports based on their names. In this case the wild card character is used in the -
reportName string to indicate reports by all names.
Notice that the -includeAllReportResults option along with the -reportName
parameter have been included in the single quotes following the -report parameter.

Topic:
Exporting individual
product assets
Topic: Exporting individual product assets

Exporting individual product assets

• Information Analyzer (IA) assets
 Use the -ia '…' parameter
− Use the -projects "project1" parameter to specify the IA assets to export
− Optionally add additional parameters, e.g., -includeProjectRoles to include
related project role assignments
• DataStage / QualityStage assets
 Use the -datastage '…' parameter
 Specify an asset path to identify the assets to export
• Use the glossary export command to export Information Governance
Catalog (IGC) assets: categories, terms, governance policies,
governance rules
 Assets are exported to an XML or XMI file
 Requires IGC Administrator role
Exporting individual product assets

Specific parameters are used to indicate specific products whose assets are to be
exported. For example, the -ia parameter is used to indicate Information Analyzer
assets and the -datastage parameter is used to indicate DataStage assets. The
specific assets are indicated by the parameters following these key words.
Following the -ia parameter you can use the -projects parameter to indicate which
Information Analyzer project assets to export.
Following the -datastage parameter you use an identity string to identify the specific
DataStage assets to export.
For Information Governance Catalog assets, the glossary export command is used.

Example: Export Information Analyzer assets

• Exports all IA projects: -ia '…'
• Includes related project roles: -includeProjectRoles
-ia parameter
-projects sub-parameter
Example: Export Information Analyzer assets

In this example, the assets from all Information Analyzer projects are exported. The
includeProjectRoles option is used to export project user roles as well.

Specifying DataStage assets in istool

• An "asset path" identifies the assets to be exported
• Format: host:portnumber/project/folder/…/folder/asset_type
• Asset types include:
 Parallel job: pjb
 Server job: sjb
 Table definition: tbd
 Parameter Set: pst
• Asset path examples:
 /server/project/folder/*.pjb: All parallel jobs in folder
 /server/project/folder/*seq.pjb: All parallel jobs in folder ending with "seq"
 /server/project/folder/*.*: All objects in project folder
Specifying DataStage assets in istool

In the istool export or import commands, you specify an "asset path" to identify the
assets to be exported.
Different keywords are used to identify different types of assets. For example, the pjb
keyword identifies DataStage parallel jobs. The path can also include the asterisk (*) as
a wildcard character. So, for example, *.pjb would refer to all parallel jobs within the
path folder. The path identifies the DataStage server, the project hosted by the server,
and a folder within the project.

Example: Export parallel jobs in a project folder

• Exports all parallel jobs in project DSProject found in the
_Training_ISAdmin/Jobs folder
• *.pjb designates all parallel jobs
All parallel jobs
Example: Export parallel jobs in a project folder

In this example, the istool command is used to export parallel jobs in a DataStage
project folder named Jobs. The folder is in a project named DSProject, hosted by the
Engine system named edserver. *.pjb identifies all parallel jobs in that project folder.
Here, the command is used to export to a file identified by the -archive (-ar) parameter.

Exporting Information Governance Catalog assets

• Use glossary export command
• Use the -format parameter to specify the format of the export file: XML
or XMI
 By default the format is XML
− XML provides more editing capabilities in the export file
• Specify categories, terms, policies, and rules to export
 Categories:
− Use -allcategories to export all categories
− Use -categories to export a comma-separated list of category paths
• The "::" character is used as a path designator
• Cat1::Cat2 specifies the path from the first category down to the second sub-
category
 Policies and rules: Use -includepoliciesrules to include all policies and rules of
all exported categories
Exporting Information Governance Catalog assets

So far in this unit we have been discussing the export command for exporting
individual product and other types of information assets. With respect to Information
Governance Catalog assets a different command is used, namely the glossary export
command.
In the export command we used the -archive parameter to identify the isx export file.
The glossary export command supports two different types of export file, namely XML
and XMI. They differ in terms of the types of editing that can be performed in the file.
XML offers the most flexibility.
Following the glossary export command you specify the categories to export. You can
either specify all categories or specify a list of categories. The terms contained in the
categories will also be exported. And you can use the -includepoliciesrules to include
the policies and rules contained in the categories.

Topic:
Importing information
assets
Topic: Importing information assets

Importing information assets

• Use the same authentication parameters as for the export
• Use the same -archive parameter to specify the archive file
• Use the -replace parameter to replace existing assets with imported
assets having the same name
• Optionally use the -preview parameter to preview a list of the assets that
will be imported when the import runs
• Use parameters to select the type of assets in the file to import
 Use -ia ' ' to select Information Analyzer assets
 Use -datastage ' ' to select DataStage assets
 Use -cm ' ' to select common metadata assets
 Use -report ' ' to select reports
 Use -security ' ' to select security assets
 The single quotes following the parameters are required
− You can optionally use identify strings to pick out subsets of assets in the
archive
 You can use multiple parameters to select multiple types of assets
Importing information assets

You use many of the same parameters in the import command as you used in the
export command.
The -preview parameter is particularly useful with the import command to check what
you will be importing before you actually run the command.
The Information Server Repository may already contains assets with the same names
as those being imported. By default, the import command will not overwrite these
assets with the new assets. You must use the -replace parameter to overwrite existing
assets.
The archive file may potentially contain many different types of information assets. You
use the same parameters you used to export the assets to import the same types of
assets from the file.

Import example
• Import all the common metadata information assets in the
CommonMeta.isx archive
• First use the -preview option to preview the import
• Afterwards, use the -replace option to overwrite existing assets
-cm parameter Archive file
Import example
In this example the -cm parameter is used to select common metadata assets from the
archive file for import.
The -replace option is used to replace existing assets with the same names.

Import example for DataStage assets

• Imports assets in archive file into the specified DataStage project
• Use istool import command
• -replace option is used to overwrite if the assets already exist
Import project -replace option
Import example for DataStage assets

In this example, the istool command is used to import an archive file into a DataStage
project. Key parts of the command are highlighted in the graphic.
Here, the command is used to import from a file identified by the -archive parameter.
The DataStage project to import into is specified by the string following the -datastage
parameter.
In this example the -datastage parameter specifies the DataStage project in which to
import the DataStage assets from the archive.

Demonstration 1

• Export common metadata assets using istool
• Use the istool query command to retrieve a list of common metadata asset
• Export security assets using istool
• Export reporting assets using istool
• Export DataStage assets using istool
• Import DataStage assets using istool
Demonstration 1: Managing Information Server repository assets

Demonstration 1:
Purpose:
You will learn how to import and export information assets using istool.
Task 1. Export common metadata assets using istool.

Common metadata assets include database assets, data model assets, and data
connections. In this task you will export database assets to an archive (*.isx) file.
You specify the assets to export using the –cm parameter followed by one or more
identity strings enclosed in single quotes.
The table you will export is the CUSTOMER table in the STUDENT schema of the
SAMPLE database. This database exists on the lab image system named
EDSERVER.
1. In this task you will use the credentials file named ISCredentials.txt that you
created in a previous lab and stored in the c:\temp directory. If you do have this
file you can easily create it using Notepad. Create two lines of the form
user=isadmin (first line), password=isadmin (second line). You do not need
to encrypt the isadmin password, which is encrypted in the screenshot below.
2. Open the Information Server Command Line Interface by clicking on its icon on
the desktop.
Note: This is not the same as the Windows Command window which you used
in the previous exercise.
Notice the istool> prompt.

3. At the prompt, type the word export, and then type the –authfile parameter
followed by its value, namely the path to the credentials file:
c:\Temp\ISCredentials.txt.
4. Now add the –ar parameter followed by a path to the archive file in double
quotes. Name the file CommonMeta.isx and store it in the c:\Temp directory.
5. Now add the –cm parameter followed by the identity string to the CUSTOMERS
table in single quotes.
6. Click Enter.
Task 2. Use the istool query command to retrieve a list of

common metadata asset.
1. At the istool prompt, type the query command, the –authfile parameter
followed by its value, and the –outputfile parameter followed by its value. Write
to an output file named Query_CommonMetaOut.txt in the c:\Temp directory.
2. Now add the –cm parameter and its value in single quotes. Retrieve a list of all
schemas in all databases. The *.sch extension indicates the schema type.

3. Click Enter.
Notice that the command appended “commonmetadata” to the name of the
output file.
4. Open the output file to view the list of schemas. (Your results may differ from
what you see here.)
Task 3. Export security assets using istool.

1. At the istool prompt, type the export command, the –authfile parameter
followed by its value, and the –ar file parameter followed by its value. Write to
an archive file named Users.isx in the c:\Temp directory.
2. Now add the –security parameter and its value in single quotes.
• Include the –securityUser parameter to export user security assets.
• Include the –userident parameter followed by an identity string in double
quotes to identify the users. In this case, specify all users.
• Use the –includeRoles and –includeUserGroupMemberships to include
user role and group membership information for the users exported.
3. Add the –preview parameter to preview what will be exported before the export
runs.

4. Click Enter.
5. Remove the –preview parameter, and then click Enter.

This runs the previewed export performed in the previous step.
Task 4. Export reporting assets using istool.

followed by its value, and the –archive file parameter followed by its value.
Write to an archive file named Reports.isx in the c:\Temp directory.
2. Now add the –report parameter and its value in single quotes.
• Include the –reportName parameter followed by an identity string in double
quotes to identify the reports. In this case, specify all reports.
• Use the –includeAllReportResults to include the results of executed reports.
3. Optionally add the –preview parameter to preview what will be exported before
the export runs, and then click Enter.
4. Click Enter.

Task 5. Export DataStage assets using istool.

Write to an archive file named DSJobs.isx in the c:\Temp directory.
2. Now add the –datastage parameter and its value in single quotes.
• Specify in your identity string that you want to export all parallel jobs in the
Jobs folder of the DataStage project named DSProject.
• The *.pjb extension stands for the parallel job type.
• Your identity string should have the following format:
‘hostName/projectName/folderName/*.pjb’
3. Add the –preview parameter to preview what will be exported before the export
runs, and then click Enter.
4. Remove the –preview parameter, and then click Enter.
Task 6. Import DataStage assets using istool.

In this task you will import the DataStage assets you exported to an archive file in the
previous task to another DataStage project named dstage1.
1. At the istool prompt, type the import command, the –authfile parameter
Read the archive file named DSJobs.isx in the c:\Temp directory.

2. Now add the –datastage parameter and its value in single quotes.
• Specify in your identity string where you want the jobs to written. In this case it
is to a project named dstage1 on the edserver host.
3. Add the –preview parameter to preview what will be imported before the import
runs, and then click Enter.
In this case, these assets already exist in the project, but when you run the
command this may not be the case.
4. Remove the –preview parameter, and then add the –replace parameter. This
will overwrite assets if they already exist. Then click Enter.
5. Optionally, if you feel comfortable using DataStage, you can log into the
dstage1 project in DataStage Designer and verify that the jobs were imported
into the Jobs folder.
Results:
You have learned how to import and export information assets using istool.

Unit summary
• Use istool to export common metadata assets
• Use istool to query information assets
• Use istool to export security assets
• Use istool to export reporting assets
• Use istool to export individual product assets
Unit summary


KM510 Course Guide PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

KM510 Course Guide PDF

Caricato da

Copyright:

Formati disponibili

Preface

© Copyright IBM Corp. 2007, 2015 P-2

© Copyright IBM Corp. 2007, 2015 P-3

Services tier ....................................................................................................... 1-31

© Copyright IBM Corp. 2007, 2015 P-4

Authentication and Suite Security ........................................................ 3-1

© Copyright IBM Corp. 2007, 2015 P-5

Administrative tools ............................................................................... 6-1

© Copyright IBM Corp. 2007, 2015 P-6

Example: Export Information Analyzer assets .................................................. 7-23

© Copyright IBM Corp. 2007, 2015 P-7

© Copyright IBM Corp. 2007, 2015 P-8

© Copyright IBM Corp. 2007, 2015 P-9

Additional training resources

© Copyright IBM Corp. 2007, 2015 P-10

IBM product help

Books for You want to use search engines to Start/Programs/IBM

IBM on the You want to access any of the

• IBM - Training and Certification • http://www-01.ibm.com/

© Copyright IBM Corp. 2007, 2015 P-11

© Copyright IBM Corp. 2007, 2015 P-12

Information Server technical

Information Server v11.5

© Copyright IBM Corporation 2015

© Copyright IBM Corp. 2007, 2015 1-2

Information Server technical overview © Copyright IBM Corporation 2015

© Copyright IBM Corp. 2007, 2015 1-3

Information Server functional categories

IBM InfoSphere Information Server

Data cleansing, Common information Data migration and Deliver information

Integrated Metadata Management

Information Server technical overview © Copyright IBM Corporation 2015

Information Server functional categories

© Copyright IBM Corp. 2007, 2015 1-4

IS products support these functional categories

IBM InfoSphere Information Server

Information Analyzer, Information FastTrack, Information Services

Integrated Metadata Management

Information Server technical overview © Copyright IBM Corporation 2015

IS products support these functional categories

© Copyright IBM Corp. 2007, 2015 1-5

Role-based tools with integrated metadata

Business Subject Matter Architect Data Developers DBA

Integrated Metadata Management

 Simplify Integration  Increase trust and confidence

Information Server technical overview © Copyright IBM Corporation 2015

Role-based tools with integrated metadata

© Copyright IBM Corp. 2007, 2015 1-6

Information Server technical overview © Copyright IBM Corporation 2015

Topic: Data quality products and components

© Copyright IBM Corp. 2007, 2015 1-7

 Profiling of fields, and relationship Other Business

• Ongoing measurement and baseline

© Copyright IBM Corp. 2007, 2015 1-8

© Copyright IBM Corp. 2007, 2015 1-9

Why data cleansing with QualityStage is needed

Information Server technical overview © Copyright IBM Corporation 2015

Why data cleansing with QualityStage is needed

© Copyright IBM Corp. 2007, 2015 1-10

© Copyright IBM Corp. 2007, 2015 1-11

Information Server technical overview © Copyright IBM Corporation 2015

Topic: Data governance

© Copyright IBM Corp. 2007, 2015 1-12