Installation and Configuration Guide

10.2.2 HotFix 1
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0
- 10.2.2 Service Pack 1
- 10.2.2
- 10.2.1
- 10.2 HotFix 2
- 10.2 HotFix 1
- 10.2

Back Next

Creating a Catalog Service

Create a Catalog Service to run the Enterprise Data Catalog application and manage the connections between the Enterprise Data Catalog components. You can configure the general, application service, and security properties of the Catalog Service.

If you plan to deploy Enterprise Data Catalog on multiple nodes, ensure that you configure Informatica Cluster Service and Catalog Service on separate nodes.

The Catalog Service has the same privileges as the user account that creates it. Ensure that the user account does not have privileges to read or modify sensitive files on the system.

In the Administrator tool, select a domain, and click the

Services and Nodes

tab.

On the Actions menu, click

New

Catalog Service

The

New Catalog Service Step 1 of 4

dialog box appears.

Configure the general properties in the dialog box.

The following table describes the properties:

Property	Description
Name	Name of the service. The name is not case-sensitive and must be unique within the domain. The name cannot exceed 128 characters or begin with @. The name cannot contain character spaces. The characters in the name must be compatible with the code page of the Model repository that you associate with the Catalog Service. The name cannot contain the following special characters: ` ~ % ^ * + = { } \ ; : ' " / ? . , < > \| ! ( ) ] [
Description	Description of the service. The description cannot exceed 765 characters.
Location	Domain in which the service runs.
License	License to assign to the Catalog Service. Select the license that you installed with Informatica.
Node	Node in the Informatica domain on which the Catalog Service runs. If you change the node, you must recycle the Catalog Service.
Backup Nodes	If your license includes high availability, nodes on which the service can run if the primary node is unavailable.

Click

The

New Catalog Service - Step 2 of 4

dialog box appears.

Configure the application service properties in the dialog box.

The following table describes the properties:

Property	Description
Model Repository Service	Model Repository Service to associate with the Catalog Service. The Model Repository Service manages the Model repository that Enterprise Data Catalog uses. If you update the property to specify a different Model Repository Service, recycle the Catalog Service.
User name	The database user name for the Model repository.
Password	An encrypted version of the database password for the Model repository.
Security Domain	Name of the security domain that includes the User name .

Click

The

New Catalog Service - Step 3 of 4

dialog box appears.

Configure the security properties in the dialog box.

The following table describes the properties:

Property	Description
HTTP Port	A unique HTTP port number used for each Data Integration Service process. The defaults is 8085.
Enable Transport Layer Security	Indicates that the Catalog Service must use HTTPS. If you did not configure the Data Integration Service to use HTTPS, the Catalog Service does not start.
HTTPS Port	Port number for the HTTPS connection.
Keystore File	Path and file name of the keystore file. The keystore file contains the keys and certificates required if you use the SSL security protocol with Catalog Administrator. Required if you select Enable Transport layer Security. When Enterprise Data Catalog creates the Catalog Service, Enterprise Data Catalog exports the keystore to a certificate and stores the certificate in the keystore directory. Ensure that you configure the read and write permissions on the directory for Enterprise Data Catalog to successfully store the certificate.
Keystore Password	Password for the keystore file. Required if you select Enable Transport layer Security.
SSL Protocol	Secure Sockets Layer protocol to use.

Click

The

New Catalog Service - Step 4 of 4

dialog box appears.

Configure the Hadoop cluster properties in the dialog box.

The following table describes the properties:

Property	Description
Cluster Type	Select one of the following options to indicate the deployment type for Enterprise Data Catalog: External Cluster. Deploy Enterprise Data Catalog in an existing Hadoop cluster on Hortonworks, ClouderaManager, or Azure HDInsight. Internal Cluster. Deploy Enterprise Data Catalog in the embedded Hadoop cluster on Hortonworks.
Hadoop Distribution	Applicable if you select the External Cluster option for Cluster Type . Select one of the following options to specify the Hadoop distribution: ClouderaManager. Use this option if you want to use a ClouderaManager Hadoop distribution. Hortonworks. Use this option if you want to use a Hortonworks Hadoop distribution. If you select ClouderaManager or Hortonworks as the Hadoop distribution, Enterprise Data Catalog automatically identifies the following properties for the Hadoop-distribution type: ZooKeeper Cluster URI HDFS Namenode URI Yarn resource manager URI Yarn resource manager HTTPS or HTTP URI History Server HTTP URI HDFS Service Name for High Availability Yarn resource manager scheduler URI HDInsight. Use this option if you want to use an Azure HDInsight Hadoop distribution. Others. Use this option if you want to manually specify all the properties for a ClouderaManager, Hortonworks, or an Azure HDInsight Hadoop distribution. Make sure that you configure the following custom options for the Catalog Service: LdmCustomOptions.yarn-site.yarn.application.classpath LdmCustomOptions.yarn-site.yarn.nodemanager.webapp.address LdmCustomOptions.yarn-site.yarn.nodemanager.webapp.https.address If you select ClouderaManager or Hortonworks, configure the following properties with the other required properties : Cluster URL. The cluster URL to access the selected Hadoop distribution. Cluster URL username. The username to access the cluster URL. Cluster URL password. The password associated with the cluster URL username.
ZooKeeper Cluster URI	Applies to existing cluster. Multiple ZooKeeper addresses in a comma-separated list.
HDFS Namenode URI	Applies to existing cluster. The URI to access HDFS. Use the following format to specify the NameNode URI in the Cloudera distribution: <Hostname>:<Port> Where <host name> is the host name or IP address of the NameNode <port number> is the port number that the NameNode listens for Remote Procedure Calls (RPC).
Yarn resource manager URI	Applies to existing cluster. The service within Hadoop that submits the MapReduce tasks to specific nodes in the cluster. Use the following format: <Hostname>:<Port> Where <host name> is the name or IP address of the Yarn resource manager. <port number> is the port number on which Yarn resource manager listens for Remote Procedure Calls (RPC).
Yarn resource manager HTTPS or HTTP URI	Applies to existing cluster. https or http URI value for the Yarn resource manager.
History Server HTTP URI	Applies to existing cluster. Specify a value to generate YARN allocation log files for scanners. Catalog Administrator displays the log URL as part of task monitoring.
HDFS Service Name for High Availability	Applies to highly available existing cluster. Specify the HDFS service name.
Yarn resource manager scheduler URI	Applies to existing cluster. Scheduler URI value for the Yarn resource manager.
Service Cluster Name	Applies to both embedded and existing clusters. Name of the service cluster. Ensure that you have a directory /Informatica/LDM/<ServiceClusterName> in HDFS. If you do not specify a service cluster name, Enterprise Data Catalog considers DomainName_CatalogServiceName as the default value. You must then have the /Informatica/LDM/<DomainName>_<CatalogServiceName> directory in HDFS. Otherwise, Catalog Service might fail.
Load Type	Select any of the following options to specify the data size that you plan to load in the catalog: demo low medium high See the Tuning Enterprise Data Catalog Performance How-to-article for more information about data size, load types, and the performance tuning parameter values that Enterprise Data Catalog configures for each load type.
Enable Kerberos Authentication	Select to enable Kerberos authentication for the existing cluster.
HDFS Service Principal Name	Applies to Kerberos authentication. Principal name for the HDFS Service.
YARN Service Principal Name	Applies to Kerberos authentication. Principal name for the YARN Service.
Service Keytab Location	Applies to Kerberos authentication. Path to the keytab file.
Kerberos Domain Name	Applies to Kerberos authentication. Name of the Kerberos domain.
Enable Cluster SSL	Select to enable SSL authentication for secure communication in the existing cluster.
Solr Keystore	Applies to SSL authentication. Path to the Solr keystore file.
Solr Keystore Password	Applies to SSL authentication. Password for the Solr keystore file.
Receive Alerts through Email	Applies to both embedded and existing clusters. Choose to receive email notifications on the Catalog Service status. If you select this option, you must enable the Email Service. For more information about enabling Email Service, see the Administrator Reference for Enterprise Data Catalog guide.
Enable Catalog Service	Applies to both embedded and existing clusters. Select the option to enable the Catalog Service.
Informatica Cluster Service	Applies to embedded cluster. Name of the Informatica Cluster Service, which is an application service that Enterprise Data Catalog uses in embedded cluster deployment.