Services on a node in an Informatica domain use TCP/IP to connect to services on other nodes. Because services can run on multiple nodes in the domain, services rely on the Service Manager to route requests. The Service Manager on the master gateway node handles requests for services and responds with the address of the requested service.
Nodes communicate through TCP/IP on the port you select for a node when you install Informatica Services. When you create a node, you select a port number for the node. The Service Manager listens for incoming TCP/IP connections on that port.
The platform uses connection objects to define connectivity information for source and target databases. The connection objects can use native or ODBC connectivity. The Data Integration Service uses connection objects to connect to sources and targets.
The services and clients connect in the following ways:
Model Repository Service
The Model Repository Service uses JDBC to read or write data and metadata in the Model repository. It uses TCP/IP to communicate with the Data Integration Service and the clients.
Data Integration Service
The Data Integration Service uses ODBC or native drivers to connect and read data from a source database and write data to a target database. It uses TCP/IP to communicate with the Model Repository Service, Content Management Service, and client applications.
Informatica Developer
The Developer tool uses TCP/IP to send data transformation requests to the Data Integration Service. It uses TCP/IP to communicate with the Content Management Service to manage reference tables, probabilistic model files, and to retrieve configuration and status information for identity population files and address validation reference data files. When you preview mappings or data objects in the Developer tool, it uses JDBC or ODBC drivers to connect to the source or target database to fetch the metadata required for preview.
ASK INFAPreview
