Professional Documents
Culture Documents
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.
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
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.
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.
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.
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.
10. Explore some of the terms in the Physical Address category, for example,
StreetAddress.
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.
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.
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.
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.
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.
Demonstration 1
Authentication and Suite Security
Demonstration 1:
Authentication and Suite Security
Purpose:
In this unit, you learn how to create users and groups in the Information
Server Administration Console.
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.
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.
Session management
Demonstration 1
Session management
Demonstration 1:
Session management
Purpose:
You will learn how to manage sessions using the Information Server
Administrative 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".
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.
Results:
You learned how to manage sessions using the Information Server
Administrative Console.
Managing reports
Demonstration 1
Managing reports
Demonstration 1:
Managing reports
Purpose:
You will learn how to manage reports.
6. Click OK.
The new report folders are displayed.
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.
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.
Administrative tools
Demonstration 1
Administrative tools
Demonstration 1:
Administrative tools
Purpose:
You will use command line tools to perform administrative tasks.
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.
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.
• 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.
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.
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.)
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.
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.
Demonstration 1
Managing Information Server repository assets
Demonstration 1:
Managing Information Server repository assets
Purpose:
You will learn how to import and export information assets using istool.
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.
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.)
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.
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.
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.
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.