Administrator Guide > Understanding Domains > Application Services
  

Application Services

Application services represent server-based functionality.
Application services include services that you create and system services that are created for you when you create the domain. A system service can have a single instance in the domain.
Application services include the following services:
When you configure an application service, you designate a node to run the service process. When a service process runs, the Service Manager assigns a port number from the range of port numbers assigned to the node.
The service process is the runtime representation of a service running on a node. The service type determines how many service processes can run at a time. For example, the PowerCenter Integration Service can run multiple service processes at a time when you run it on a grid.
If you have the high availability option, you can run a service on multiple nodes. Designate the primary node to run the service. All other nodes are back-up nodes for the service. If the primary node is not available, the service runs on a back-up node. You can subscribe to alerts to receive notification in the event of a service process failover.
If you do not have the high availability option, configure a service to run on one node. If you assign the service to multiple nodes, then the service will not start.

Analyst Service

The Analyst Service is an application service that runs the Informatica Analyst application in the Informatica domain. The Analyst Service manages the connections between service components and the users that log in to Informatica Analyst. The Analyst Service connects to a Data Integration Service, a Model Repository Service, a Metadata Manager Service, and a Search Service. The Analyst Service also specifies a flat file cache directory and a directory for business glossary export files.
When you configure the Analyst Service, connect it to a Data Integration Service to run profiles, scorecards, and mapping specifications. You can also connect the Analyst Service to a Data Integration Service that runs Human tasks. Connect the Analyst Service to a Model Repository Service to identify a Model repository.
Connect the Analyst Service to a Metadata Manager Service to perform data lineage operations on scorecards in the Analyst tool. Connect the Analyst Service to a Search Service to manage search operations in the Analyst tool.
Specify a flat file cache directory to store temporary data from flat files that you upload. Specify a business glossary directory to stores temporary files that you export from the Business Glossary.

Content Management Service

The Content Management Service is an application service that manages reference data. It provides reference data information to the Data Integration Service and to the Developer tool.
The Content Management Service provides reference data properties to the Data Integration Service. The Data Integration Service uses these properties when it runs mappings that require address reference data.
The Content Management Service also provides Developer tool transformations with information about the address reference data and identity populations installed in the file system. The Developer tool displays the installed address reference datasets in the Content Status view within application preferences. The Developer tool displays the installed identity populations in the Match transformation and Comparison transformation.

Data Integration Service

The Data Integration Service is an application service that performs data integration tasks for Informatica Analyst, Informatica Developer, and external clients. Data integration tasks include previewing data and running profiles, SQL data services, web services, and mappings.
When you start a command from the command line or an external client to run SQL data services and mappings in an application, the command sends the request to the Data Integration Service.
You can configure the Data Integration Service to run on the following domain objects:
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.

Email Service

The Email Service is a system service that manages email notifications for business glossaries, scorecards, and workflows.
Enable the Email Service to allow users to configure email notifications.
The Email Service sends emails for the following notifications:
You can configure the service to run on multiple nodes. Designate the primary node to run the service. All other nodes are backup nodes for the service. If the primary node is not available, the service runs on a backup node.

Metadata Manager Service

The Metadata Manager Service is an application service that runs the Metadata Manager application and manages connections between the Metadata Manager components.
Use Metadata Manager to browse and analyze metadata from disparate source repositories. You can load, browse, and analyze metadata from application, business intelligence, data integration, data modelling, and relational metadata sources.
You can configure the Metadata Manager Service to run on only one node. The Metadata Manager Service is not a highly available service. However, you can run multiple Metadata Manager Services on the same node.

Model Repository Service

The Model Repository Service is an application service that manages the Model repository. The Model repository is a relational database that stores the metadata for projects created in Informatica Analyst and Informatica Developer. The Model repository also stores run-time and configuration information for applications that are deployed to a Data Integration Service.
You can configure the Model Repository Service to run on one node. The Model Repository Service is not a highly available service. However, you can run multiple Model Repository Services on the same node. If the Model Repository Service fails, it automatically restarts on the same node.

PowerCenter Integration Service

The PowerCenter Integration Service runs PowerCenter sessions and workflows. When you configure the PowerCenter Integration Service, you can specify where you want it to run:

PowerCenter Repository Service

The PowerCenter Repository Service manages the PowerCenter repository. It retrieves, inserts, and updates metadata in the repository database tables. If the service process fails or the node becomes unavailable, then the service becomes unavailable.
If you have the high availability option, you can configure the service to run on primary and backup nodes. By default, the service process runs on the primary node. If the service process fails, a new process starts on the same node. If the node becomes unavailable, a service process starts on one of the backup nodes.

PowerExchange Listener Service

The PowerExchange Listener Service is an application service that manages the PowerExchange Listener. The PowerExchange Listener manages communication between a PowerCenter or PowerExchange client and a data source for bulk data movement and change data capture. The PowerCenter Integration Service connects to the PowerExchange Listener through the Listener Service. Use the Administrator tool to manage the service and view service logs.
If you have the PowerCenter high availability option, you can run the Listener Service on multiple nodes. If the Listener Service process fails on the primary node, it fails over to a backup node.

PowerExchange Logger Service

The Logger Service is an application service that manages the PowerExchange Logger for Linux, UNIX, and Windows. The PowerExchange Logger captures change data from a data source and writes the data to PowerExchange Logger log files. Use the Admnistrator tool to manage the service and view service logs.
If you have the PowerCenter high availability option, you can run the Logger Service on multiple nodes. If the Logger Service process fails on the primary node, it fails over to a backup node.

Reporting Service (Deprecated)

The Reporting Service is an application service that runs the Data Analyzer application in an Informatica domain. You log in to Data Analyzer to create and run reports on data in a relational database or to run the following PowerCenter reports: PowerCenter Repository Reports or Metadata Manager Reports. You can also run other reports within your organization.
The Reporting Service is not a highly available service. However, you can run multiple Reporting Services on the same node.
Configure a Reporting Service for each data source you want to run reports against. If you want a Reporting Service to point to different data sources, create the data sources in Data Analyzer.

Deprecated Behavior

Effective in version 10.1, Informatica deprecated the Reporting Service. Informatica will drop support for the Reporting Service in a future release.
If you upgrade to version 10.1, you can continue to use the Reporting Service. Informatica recommends that you begin using a third-party reporting tool before Informatica drops support. You can use the recommended SQL queries for building all the reports shipped with earlier versions of PowerCenter.
If you install version 10.1, you cannot create a Reporting Service. You must use a third-party reporting tool to run PowerCenter and Metadata Manager reports.
For information about the PowerCenter Reports, see the Informatica PowerCenter Using PowerCenter Reports Guide. For information about the PowerCenter repository views, see the Informatica PowerCenter Repository Guide. For information about the Metadata Manager repository views, see the Informatica Metadata Manager View Reference.

Reporting and Dashboards Service (Deprecated)

You can create the Reporting and Dashboards Service from Informatica Administrator. You can use the service to create and run reports from the JasperReports application.
JasperReports is an open source reporting library that users can embed into any Java application. JasperReports Server builds on JasperReports and forms a part of the Jaspersoft Business Intelligence suite of products.

Deprecated Behavior

Effective in version 10.1, Informatica deprecated the Reporting and Dashboards Service. Informatica will drop support for the Reporting and Dashboards Service and JasperReports Server in a future release.
If you upgrade to version 10.1, you can continue to use the Reporting and Dashboards Service. Informatica recommends that you begin using a third-party reporting tool before Informatica drops support. You can use the recommended SQL queries for building all the reports shipped with earlier versions of PowerCenter.
If you install version 10.1, you cannot create a Reporting and Dashboards Service. You must use a third-party reporting tool to run PowerCenter and Metadata Manager reports.
For information about the PowerCenter Reports, see the Informatica PowerCenter Using PowerCenter Reports Guide. For information about the PowerCenter repository views, see the Informatica PowerCenter Repository Guide. For more information about the Metadata Manager repository views, see the Informatica Metadata Manager View Reference.

Resource Manager Service

The Resource Manager Service is a system service that manages computing resources in the domain and dispatches jobs to achieve optimal performance and scalability. The Resource Manager Service collects information about nodes with the compute role. The service matches job requirements with resource availability to identify the best compute node to run the job.
The Resource Manager Service communicates with compute nodes in a Data Integration Service grid. Enable the Resource Manager Service when you configure a Data Integration Service grid to run jobs in separate remote processes.
You can configure the service to run on multiple nodes. Designate the primary node to run the service. All other nodes are back-up nodes for the service. If the primary node is not available, the service runs on a back-up node.

SAP BW Service

The SAP BW Service listens for RFC requests from SAP NetWeaver BI and initiates workflows to extract from or load to SAP NetWeaver BI. The SAP BW Service is not highly available. You can configure it to run on one node.

Scheduler Service

The Scheduler Service is a system service that manages schedules for profiles, scorecards, deployed mappings, and deployed workflows.
Enable the Scheduler Service to create, manage, and run schedules.
You can configure the service to run on multiple nodes. Designate the primary node to run the service. All other nodes are back-up nodes for the service. If the primary node is not available, the service runs on a back-up node.

Web Services Hub

The Web Services Hub receives requests from web service clients and exposes PowerCenter workflows as services. The Web Services Hub does not run an associated service process. It runs within the Service Manager.