Configuration Prerequisites
Before you configure the Analyst Service, you can complete the prerequisite tasks for the service. You can also choose to complete these tasks after you create an Analyst Service.
Perform the following tasks before you configure the Analyst Service:
- •Create and enable the associated Data Integration Services, Model Repository Service, and Metadata Manager Service.
- •Identify a directory for the flat file cache to upload flat files.
- •Identify a directory to export a business glossary.
- •Identify a keystore file to configure the Transport Layer Security protocol for the Analyst Service.
Services Associated with the Analyst Service
The Analyst Service connects to associated services that you create and enable before you configure the Analyst Service.
The Analyst Service connects to the following associated services:
- •Data Integration Services. You can associate up to two Data Integration Services with the Analyst Service. Associate a Data Integration Service to run mapping specifications, profiles, and scorecards. Associate a Data Integration Service to run workflows. You can associate the same Data Integration Service to run mapping specifications, profiles, scorecards, and workflows.
- •Model Repository Service. When you create an Analyst Service, you assign a Model Repository Service to the Analyst Service. You cannot assign the same Model Repository Service to another Analyst Service.
- •Metadata Manager Service. You can associate a Metadata Manager Service with the Analyst Service to perform data lineage analysis on scorecards.
- •Search Service. The Analyst Service determines the associated Search Service based on the Model Repository Service associated with the Analyst Service. If you modify the Analyst Service, you must recycle the Search Service.
Flat File Cache Directory
Create a directory for the flat file cache where the Analyst tool stores uploaded flat files. The Data Integration Service must also be able to access this directory.
If the Analyst Service and the Data Integration Service run on different nodes, configure the flat file directory to use a shared directory. If the Data Integration Service runs on primary and back-up nodes or on a grid, each Data Integration Service process must be able to access the files in the shared directory.
For example, you can create a directory named "flatfilecache" in the following mapped drive that all Analyst Service and Data Integration Service processes can access:
F:\shared\<InformaticaInstallationDir>\server
If the Analyst Service connects to a Data Integration Service that uses operating system profiles, the operating system user specified in the operating system profile must have access to the flat file cache directory.
When you import a reference table or flat file source, the Analyst tool uses the files from this directory to create a reference table or flat file data object.
Export File Directory
Create a directory to store the temporary business glossary files that the business glossary export process creates.
For example, you can create a directory named "exportfiledirectory" in the following location:
<InformaticaInstallationDir>\server
Attachments Directory
Create a directory to store attachments that the Business Glossary data steward adds to Glossary assets.
For example, you can create a directory named "BGattachmentsdirectory" in the following location:
<InformaticaInstallationDir>\server
Keystore File
A keystore file contains the keys and certificates required if you enable secure communication and use the HTTPS protocol for the Analyst Service.
You can create the keystore file when you install the Informatica services or you can create a keystore file with keytool. keytool is a utility that generates and stores private or public key pairs and associated certificates in a file called a “keystore.” When you generate a public or private key pair, keytool wraps the public key into a self-signed certificate. You can use the self-signed certificate or use a certificate signed by a certificate authority.
Note: You must use a certified keystore file. If you do not use a certified keystore file, security warnings and error messages for the browser appear when you access the Analyst tool.