Metadata Access Service Process Properties
A service process is the physical representation of a service running on a node. When the Metadata Access Service runs on multiple nodes, the service process can run on each node with the service role. You can configure the service process properties differently for each node.
To configure properties for the Metadata Access Service processes, click the Processes view. Select a node to configure properties specific to that node.
The number of running service processes depends on the following ways that you can configure the Metadata Access Service:
- Single node
- A single service process runs on the node.
- Primary and back-up nodes
- A service process is enabled on each node. However, only a single process runs at any given time, and the other processes maintain standby status.
When you edit the service process properties, changes take effect when you recycle the Metadata Access Service.
Metadata Access Service Security Properties
When you set the HTTP protocol type for the Metadata Access Service to HTTPS or both, you enable the Transport Layer Security (TLS) protocol for the service. Depending on the HTTP protocol type of the service, you define the HTTP port, the HTTPS port, or both ports for the service process.
The following table describes the Metadata Access Service Security properties:
Property | Description |
|---|
HTTP Port | Unique HTTP port number for the Metadata Access Service process when the service uses the HTTP protocol. Default is 7080. The Metadata Access Service uses consecutive port numbers to connect to multiple Hadoop distributions. |
HTTPS Port | Unique HTTPS port number for the Metadata Access Service process when the service uses the HTTPS protocol. When you set an HTTPS port number, you must also define the keystore file that contains the required keys and certificates. The Metadata Access Service uses consecutive port numbers to connect to multiple Hadoop distributions. |
HTTP Configuration Properties
The HTTP configuration properties for a Metadata Access Service process specify the maximum number of HTTP or HTTPS connections that can be made to the process. The properties also specify the keystore and truststore file to use when the Metadata Access Service uses the HTTPS protocol.
The following table describes the HTTP configuration properties for a Metadata Access Service process:
Property | Description |
|---|
Maximum Concurrent Requests | Maximum number of HTTP or HTTPS connections that can be made to this Metadata Access Service process. Minimum is 4. Default is 200. |
Maximum Backlog Requests | Maximum number of HTTP or HTTPS connections that can wait in a queue for this Metadata Access Service process. Default is 100. |
Keystore File | Path and file name of the keystore file that contains the keys and certificates required if you use HTTPS connections for the Metadata Access Service. You can create a keystore file with a keytool. keytool is a utility that generates and stores private or public key pairs and associated certificates in a keystore file. You can use the self-signed certificate or use a certificate signed by a certificate authority. |
Keystore Password | Password for the keystore file. |
Truststore File | Path and file name of the truststore file that contains authentication certificates trusted by the Metadata Access Service. |
Truststore Password | Password for the truststore file. |
SSL Protocol | Secure Sockets Layer protocol to use. Default is TLS. |
Configuring Developer Tool for HTTPS-enabled Metadata Access Service
When the Metadata Access Service is configured to use HTTPS, the Developer tool clients that connect to the Metadata Access Service require security certificates to be present in the client machine truststore.
To connect to the Metadata Access Service to import and preview metadata, the Developer tool requires security certificate aliases on the machine that hosts the Developer tool.
You might need to set the following environment variables on each client host:
- INFA_TRUSTSTORE
- Set this variable to the directory that contains the infa_truststore.jks and infa_truststore.pem truststore files.
- INFA_TRUSTSTORE_PASSWORD
- Set this variable to the password for the truststore. The password must be encrypted. Use the command line program pmpasswd to encrypt the password.
If you use the default Informatica SSL certificate, and the infa_truststore.jks and infa_truststore.pem files are in the default directory, you do not need to set the INFA_TRUSTSTORE or INFA_TRUSTSTORE_PASSWORD environment variables.
If you use a custom SSL certificate, you must set the INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD environment variables on each client host.
Advanced Properties
The following table describes the Advanced properties:
Property | Description |
|---|
Maximum Heap Size | Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the Metadata Access Service. Use this property to increase the performance. The default heap size is 1024 MB. |
JVM Command Line Options | Java Virtual Machine (JVM) command line options to run Java-based programs. When you configure the JVM options, you must set the Java SDK classpath, Java SDK minimum memory, and Java SDK maximum memory properties. You can also set the idle timeout for a process. The default idle timeout is 120 minutes. |
Custom Properties
Configure custom properties that are unique to specific environments.
You might need to apply custom properties in special cases. When you define a custom property, enter the property name and an initial value. Define custom properties only at the request of Informatica Global Customer Support.
Environment Variables
You can configure environment variables for the Metadata Access Service process.
The following table describes the environment variables:
Property | Description |
|---|
Environment Variable | Stores configuration information. Enter a name and a value for the environment variable. |