Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Content Management Service
  4. Data Integration Service
  5. Data Integration Service Architecture
  6. Data Integration Service Management
  7. Data Integration Service Grid
  8. Data Integration Service Applications
  9. Mass Ingestion Service
  10. Metadata Access Service
  11. Metadata Manager Service
  12. Model Repository Service
  13. PowerCenter Integration Service
  14. PowerCenter Integration Service Architecture
  15. High Availability for the PowerCenter Integration Service
  16. PowerCenter Repository Service
  17. PowerCenter Repository Management
  18. PowerExchange Listener Service
  19. PowerExchange Logger Service
  20. SAP BW Service
  21. Search Service
  22. System Services
  23. Test Data Manager Service
  24. Test Data Warehouse Service
  25. Web Services Hub
  26. Application Service Upgrade
  27. Application Service Databases
  28. Connecting to Databases from Windows
  29. Connecting to Databases from UNIX
  30. Updating the DynamicSections Parameter of a DB2 Database

DBMOVER Statements for the Listener Service

DBMOVER Statements for the Listener Service

Before you create a Listener Service, define LISTENER and SVCNODE statements in the DBMOVER file on each node in the Informatica domain where a PowerExchange Listener runs. Also, define a NODE statement in the DBMOVER file on each node where an Informatica client tool or integration service that connects to the Listener runs.
A client tool is the Developer tool or PowerCenter Client. An integration service is the PowerCenter Integration Service or Data Integration Service.
Define the following DBMOVER statements on all nodes where a PowerExchange Listener runs:
LISTENER
Required. Defines the
TCP/IP
port on which a named PowerExchange Listener process listens for work requests.
The node name in the LISTENER statement must match the name that you provide in the Start Parameters configuration property when you define the Listener Service.
SVCNODE
Optional. On Linux, UNIX, and Windows, use the SVCNODE statement to specify the
TCP/IP
port on which a PowerExchange Listener listens for infacmd pwx or pwxcmd commands.
This name must match the node name specified in the LISTENER statement in the DBMOVER configuration file.
Also, to issue infacmd pwx commands to connect to the Listener through the Listener application service, this name must match one of the following values:
  • If you created the application service through Informatica Administrator, the node name value that you specified in the
    Start Parameters
    property.
  • If you created the application service through the infacmd pwx CreateListenerService command, the node name value that you specified for the -StartParameters option on the command.
Use the same port number that you specify for the SVCNODE Port Number configuration property for the service.
Define the following DBMOVER statement on each node where an Informatica client tool or integration service that connects to the Listener runs:
NODE
Configures the Informatica client tool or integration service to connect to the PowerExchange Listener at the specified IP address or host name or to locate the Listener Service in the domain.
To configure the client tool or integration service to locate the Listener Service in the domain, include the optional
service_name
parameter in the NODE statement. The
service_name
parameter identifies the node, and the
port
parameter in the NODE statement identifies the port number.
If the NODE statement does not include the
service_name
parameter, the Informatica client tool or integration service connects directly to the Listener at the specified IP address or host name. It does not locate the Listener Service in the domain.
For more information about customizing the DBMOVER configuration file for bulk data movement or CDC sessions, see the following guides:
  • PowerExchange Bulk Data Movement Guide
  • PowerExchange CDC Guide for Linux, UNIX, and Windows