Application Services

• •Analyst Service
• •Catalog Service
• •Cluster Service
• •Data Integration Service
• •Model Repository Service

Analyst Service

Cluster Service

Catalog Service

Connect the MetaDex Server to the Catalog Service

1. Log in to the MetaDex tool.
2. On the header of the MetaDex tool, click Administration > EDC Instance.
The EDC Instance page appears with the predefined connection variables and the information on the variable origin, as shown in the following image:

3. Click the Edit icon to the right of each variable.
The Edit global variable dialog box appears.
4. Enter the values for the following variables:

Name	Description
EDC_URL	The host name and port number of the Catalog Service in the following format: <host>:<port>
EDC_USER	The user name configured for the catalog administrator user.
EDC_PASSWORD	The password configured for the catalog administrator user. When you add the password, click the Hide password icon.

5. Click Save.
The Edit global variable dialog box closes.
6. Test and reload the license.

Enable Data Preview, Provisioning and Preparation

Data Asset Analytics Repository Database Requirements

• •Oracle
• •Microsoft SQL Server
• •PostgreSQL

Oracle Database Requirements

1. 1. Create a user name and password to access the Oracle database using the following command: CREATE USER <Database schema>
2. 2. Run the following commands to provide the required user privileges:
GRANT CONNECT TO <Database schema>;
GRANT RESOURCE TO <Database schema>;
GRANT CREATE VIEW TO <Database schema>;
GRANT CREATE MATERIALIZED VIEW TO <Database schema>;
GRANT UNLIMITED TABLESPACE TO <Database schema>;

Alternatively, if you do not want to grant the unlimited tablespace privilege, run the command ALTER USER <Database schema> QUOTA <Size> ON <Tablespace name>;

Microsoft SQL Server Database Requirements

1. 1. Use the dbo schema for SQL Server.
2. 2. Run the following commands to create the database, the user name, password and assign the required privileges for the user:
USE master
GO
CREATE DATABASE <New database name>;
GO
use <New database name>
CREATE LOGIN <New login name> WITH PASSWORD = '<Password>';
CREATE USER <New user name> FOR LOGIN <New login name> WITH DEFAULT_SCHEMA = [dbo];
GRANT CREATE TABLE TO <New user name>;
GRANT CREATE VIEW TO <New user name>;
GRANT SELECT, ALTER, INSERT, DELETE, UPDATE on schema::dbo to <New user name> ;
GRANT REFERENCES to <New user name>;

PostgreSQL Database Requirements

1. 1. Use the public schema for PostgreSQL.
2. 2. Create the credentials to access the database using the following command: CREATE USER <New user name> WITH PASSWORD '<Password>';
Note: Make sure that you choose a user name that is different from the name of the database schema.
3. 3. Create the database and assign the ownership to the user name that you created. Use the following command to complete this step: CREATE DATABASE <NEW db NAME> owner=<New user name>;
4. 4. After you connect to the database, run the command SHOW search_path. The command must return the value <User>, public.

Data Flow Analytics Repository Database Requirements

Oracle Database Requirements

1. 1. Create a user name and password to access the database using the CREATE USER <Database schema> IDENTIFIED BY <database schema> command.
2. 2. Run the following commands to provide the required privileges to the database user:
GRANT CONNECT TO <Database schema>;
GRANT SELECT ON <PowerCenter repository schema>.OPB_WFLOW_RUN TO <Database schema>;
GRANT SELECT ON <PowerCenter repository schema>.OPB_SUBJECT TO <Database schema>;

3. 3. Run the following commands to create synonyms for the tables to query the workflow execution details:
CREATE synonym <Database schema>.OPB_WFLOW_RUN FOR <PCRS schema>.OPB_WFLOW_RUN;
CREATE synonym <Database schema>.OPB_SUBJECT FOR <PCRS schema>.OPB_SUBJECT;

Microsoft SQL Server Database Requirements

1. 1. Run the following commands to create a user name and password to access the database:
USE <PowerCenter repository name>
CREATE LOGIN <New login name> WITH PASSWORD='<Password>';
CREATE USER <New user name> FOR LOGIN <New login name>;
2. 2. Run the following commands to provide the required privileges to the database user:
GRANT SELECT ON OPB_SUBJECT TO <New user name>;
GRANT SELECT ON OPB_WFLOW_RUN TO <New user name>

IBM DB2 Database Requirements

1. 1. Log in to the machine that hosts the IBM DB2 database as a root user and create a new user account on the machine.
2. 2. Run the following commands to provide the required privileges to the database user:
GRANT CONNECT ON <PowerCenter repository name> TO USER <Database user name>;
GRANT SELECT ON TABLE <PowerCenter repository name>."OPB_WFLOW_RUN" TO USER <Database user name>;
GRANT SELECT ON TABLE <PowerCenter repository name>."OPB_SUBJECT" TO USER <Database user name>;

3. 3. Run the following commands to create aliases for the tables to query the workflow execution details:
CREATE ALIAS <Database user name>.OPB_WFLOW_RUN FOR <PowerCenter repository name>.OPB_WFLOW_RUN;
CREATE ALIAS <Database user name>.OPB_SUBJECT FOR <PowerCenter repository name>.OPB_SUBJECT;

Sybase

1. 1. Log in to a Sybase client as an administrator and run the following commands to create a user name and password to access the database:
sp_addlogin <New login name>, <Password>
use <PowerCenter repository name>
sp_adduser <New login name>, <New user name>
2. 2. Run the following commands to provide the required privileges to the database user:
GRANT SELECT TO <New user name>
GRANT CREATE VIEW TO <New user name>
3. 3. Run the following commands to create views for the tables to query the workflow execution details:
CREATE VIEW <Database user name>.OPB_WFLOW_RUN as select * from <PowerCenter repository schema>.OPB_WFLOW_RUN
CREATE VIEW <Database user name>.OPB_SUBJECT as select * from <PowerCenter repository schema>.OPB_SUBJECT

PostgreSQL

1. 1. Create a user name and password to access the database using the following command: CREATE USER <Database user name> WITH PASSWORD '<Database user name>'
2. 2. Create a role using the CREATE ROLE <Role name> command.
3. 3. Run the following commands to provide the required privileges to the user:
GRANT <role name> TO <Database user name>;
GRANT CONNECT ON DATABASE "<PowerCenter repository name>" to <Role name>;
GRANT USAGE ON SCHEMA <PowerCenter repository schema> TO <Role name>;
GRANT SELECT ON OPB_WFLOW_RUN TO <Role name>;
GRANT SELECT ON OPB_SUBJECT TO <Role name>;

Content Management Service

Data Integration Service

On nodes

If your license includes high availability, you can configure the service to run on multiple nodes. By default, the service runs on the primary node. If the primary node is not available, the service runs on a back-up node. If the service process fails or the node becomes unavailable, the service fails over to another node. If your license does not include high availability, you can configure the service to run on one node.

On a grid

If your license includes grid, you can configure the service to run on a grid. A grid is an alias assigned to a group of nodes. The Data Integration Service dispatches jobs to available nodes assigned to the grid. When the Data Integration Service runs on a grid, the service remains available if a service process fails or a node becomes unavailable.

Model Repository Service