Navigator User Guide

10.5.5
- 10.5.6
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Adding a Personal Metadata Profile

Add a personal metadata profile that you can use to connect to a source or target.

You can include filters to limit the tables that the profile contains.

On the

Resources

tab in the

Resource Explorer

, click

Add > Personal Metadata

In the

Personal Metadata - Name

dialog box, enter the following information:

Name: A user-defined name for the personal metadata profile.
Location: The location of the source or target for which you want to view metadata. Select
local
if the source or target is on the PowerExchange Navigator system.

This field lists locations that are defined in NODE statements in the dbmover.cfg configuration file on the PowerExchange Navigator system.

Default is
local
.
Type: The data source or target type. Select one of the following types and then complete the fields for that type:

DB2
. DB2 for i5/OS or DB2 for z/OS sources or targets.

For DB2 for i5/OS, optionally enter the database name in the
SSID or DBName
field. Default is the default database.

For DB2 for z/OS, enter the SSID in the
SSID or DBName
field.

DB2400C
. DB2 Call Level Interface (CLI) for i5/OS sources.

Enter the database name in the
SSID or DBName
field.

DB2UDB
. DB2 for Linux, UNIX, and Windows sources or targets.

Optionally enter a database name in the
DBName
field.

MSSQL
. Microsoft SQL Server sources or targets.

Enter the SQL Server instance name in the
DSN
field. Optionally, enter a database name to override the database for the connection in the
Database
field.

MYSQL
. MySQL sources.

Enter the MySQL database server name in the
Server
field.

NRDB
or
NRDB2
. PowerExchange data maps for nonrelational sources such as Adabas, CA Datacom/DB, CA IDMS/DB, IMS, VSAM, and flat files.

Optionally enter an override file name in the
Override File Name
field.

The
NRDB2
data source type uses a two-tier naming convention for generated SQL in a database row test while
NRDB
uses a three-tier naming convention. You can use
NRDB
or
NRDB2
for PowerExchange data maps.

ORACLE
. Oracle sources or targets.

Optionally, enter a TNS name for the Oracle instance in the
SQL*Net Name
field.

PGSQL
. PostgreSQL sources.

Do not select any of the following deprecated source or target types:

AS4_META

CAPX

CAPXRT

ODBC

TASK_CNTL
UserID: Enter a user ID that allows access to the source. The type of user ID depends on the source type and PowerExchange security settings:

If the source is on an i5/OS or z/OS system and PowerExchange security is enabled, enter an operating system user ID. PowerExchange security is enabled when the PowerExchange SECURITY statement in the DBMOVER member is set to (1,x) or 2.x).

For a DB2 for Linux, UNIX, and Windows, Microsoft SQL Server, MySQL, Oracle, or PostgreSQL source, enter a valid database user ID, if required. For more information, see the SECURITY Statement in the
PowerExchange Reference Manual
.

For a source on a supported Linux, UNIX, or Windows system, if you have enabled PowerExchange LDAP user authentication and, if applicable, disabled relational pass-through authentication, the user ID is the enterprise user name. For more information, see the
PowerExchange Reference Manual
.
Password: A password for the specified user ID.

If the source is on an i5/OS or z/OS system, you can enter a valid PowerExchange passphrase instead of a password. An i5/OS passphrase can be from 9 to 31 characters in length. A z/OS passphrase can be from 9 to 128 characters in length. A passphrase can contain the following characters:

Uppercase and lowercase letters

The numbers 0 to 9

Spaces

The following special characters:

’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ?

The first character is an apostrophe.

Passphrases cannot include single quotation marks (‘), double quotation marks (“), or currency symbols.

On z/OS, the allowable characters in the IBM IRRPHREX exit do not affect the allowable characters in PowerExchange passphrases.

On z/OS, a valid RACF passphrase can be up to 100 characters in length. PowerExchange truncates passphrases longer than 100 characters when passing them to RACF for validation.

To use passphrases, ensure that the PowerExchange Listener runs with a security setting of SECURITY=(1,N) or higher in the DBMOVER member. For more information, see "SECURITY Statement" in the
PowerExchange Reference Manual
.

If you specify a user ID and omit the password or passphrase, when you open the personal metadata profile, the PowerExchange Navigator prompts you for the password in the
Missing Password
dialog box.
Type-specific fields: Type
Fields

DB2, DB2400C, or DB2UDB

SSID or DBNAME
. For a DB2 for z/OS, enter a DB2 subsystem ID. For DB2400C or DB2UDB, enter a DB2 database name.

MSSQL

Server
. The SQL Server publication server name.

Database
. The SQL Server database name.

MYSQL

Server
. The MySQL database server name.

ORACLE

SQL*Net Name
. The TNS name for the Oracle instance.

PGSQL

Server
. The PostgreSQL database server name.

Database
. The PostgreSQL database name.
Description: A user-defined description for the personal metadata profile.

Type	Fields
DB2, DB2400C, or DB2UDB	SSID or DBNAME . For a DB2 for z/OS, enter a DB2 subsystem ID. For DB2400C or DB2UDB, enter a DB2 database name.
MSSQL	Server . The SQL Server publication server name. Database . The SQL Server database name.
MYSQL	Server . The MySQL database server name.
ORACLE	SQL*Net Name . The TNS name for the Oracle instance.
PGSQL	Server . The PostgreSQL database server name. Database . The PostgreSQL database name.

Click

In the

Personal Metadata - Filters

dialog box, enter the following information to limit the tables that the profile contains:

Filter Data: Enter optional filter criteria in the following filter fields, depending on the source or target type:

For the DB2, DB2400C, or DB2UDB type, enter filters in the
Creator/Schema
,
DBName/Definer
, and
Table
boxes.

For the MYSQL, ORACLE, or PGSQL type, enter filters in the
Schema
and
Table
boxes.

For the MSSQL type, enter filters in the
Owner
and
Table
boxes.

For the NRDB or NRDB2 type, enter filters in the
Schema
,
Mapname
, and
Table
boxes.

In any filter field, you can use the following wildcard characters:

An asterisk (*) to represent one or more matching characters.

A question mark (?) to represent a single matching character.
Respect Case: By default, text entered in any of the filter boxes is converted to the standard case for the data source. For example, on Oracle, uppercase is the standard and so a value of
scott
or
SCOTT
produces the same result:
SCOTT
.

Select the
Respect Case
check box for those filters for which you do not want PowerExchange to switch to the standard case for the data source.
Escape Character: Enter the escape character to use for delimiting an asterisk (*) or question mark (?) that is used as a literal value rather than as a wildcard in the filter fields.

For example, if you specify an escape character of
~
, a filter value of
tab*
returns all tables beginning with
tab
. A filter value of
tab~*
returns the table named
tab*
.

Do not use an escape character with data sources that are multibyte-enabled.

Click

Finish

The

Personal Metadata

tab in the

Resource Explorer

displays the personal metadata profile and all tables that match the specified filters.

To verify that the personal metadata profile can preview data, run a database row test on a table in the profile.

Rename Saved Search

Table of Contents

Navigator User Guide

Navigator User Guide

Adding a Personal Metadata Profile

Adding a Personal Metadata Profile