Installation
Informatica MDM - Product 360 is a client server application with multiple optional modules. In general, all modules can be installed on the same host. For performance and load balancing reasons we recommend to use multiple host machines. This deployment guide gives an overview on the possible deployment scenarios and provides detailed installation instructions for each of the modules.
Please refer to the Sizing Guide to get an overview on the needed hardware for your individual project.
Pre-Installation Checklist
Before beginning to install, please check that:
Your system meets the requirements of the Product Availability Matrix (PAM)
Note: Please find the Product Availability Matrix in Informatica Network
You must be able to use a command prompt to continue. If not, please contact your system administrator to assist.
If you have not downloaded the binary packages already, please raise a Shipping Request with Informatica.
Logical Service Overview
The following diagram gives a logical overview on the services which are involved in the overall Product 360 application. The deployment strategy should be individually defined based on the sizing requirements of the customer. Examples for a typical and full deployment can be found alter in this chapter.
General Communication Overview
The diagram shows the general communication connections between the modules of the installation. Mandatory modules are marked in red. The complete list of all communication ports can be found below the diagram. This overview shows only a single server and it omits also load balancing servers/modules since they are identical or common technology.
Port Overview
Database
|
Port |
Database |
|
1433 |
MSSQL |
|
1521 |
Oracle |
Server, Web and Desktop
|
Port |
Protocol |
Product 360 Module |
|
1712 |
tcp/tcps |
Desktop connection. This port is used to connect the Desktop Client with it's Server as well as each server with each other server. |
|
1512 |
http/https |
Web Server Port (Jetty) which is used for the Web Client as well as the Service API or file transfer. |
|
1812 |
tcp |
Data Grid communication. Needed for the synchronization heartbeat of the cluster. No data is transferred with this protocol, only synchronisation tokens. |
|
55555 |
tcp |
Default Java Management Extensions Port which is needed to attach troubleshooting and tuning tools. |
|
61616 |
tcp/tcps |
The port for the message queue connection. |
|
25 |
smtp |
Product 360 - Server is capable to send e-mails in various functional areas, for this it needs access to an smtp e-mail server |
|
445 and 139 |
smb and tcp |
Windows file share ports for the media asset file communication when used with the Product 360 - Media Manager module |
Elasticsearch
|
Port |
Protocol |
Product 360 Module |
Description |
|
9200 |
http/https |
Audit trail and Fulltext search |
This port is used by Product 360 - Server to communicate with Elasticsearch for Audit trail and Fulltext search |
Media Manager
|
Port |
Protocol |
Product 360 Module |
|
11100 |
tcp |
Funcd |
|
11101 |
tcp |
Pipe Funcd |
|
11102 |
tcp |
Internet Funcd |
|
81 |
tcp |
Product 360 Core and Product 360 - Media Manager Web - XOB Connection |
|
8089 |
http |
Session Manager, Web Status Page |
|
8080 |
http |
Product 360 - Media Manager Web, Product 360 - Media Manager REST |
|
82 |
tcp |
Product 360 - Media Manager Web XOB Connection (Administration) (optional for Product 360 8 only for upgrade) |
|
83 |
tcp |
Product 360 - Media Manager Web XOB Connection (Data) (optional for Product 360 8 only for upgrade) |
|
84 |
tcp |
Product 360 - Media Manager Web XOB Connection (Data) (optional for Product 360 8 only for upgrade) |
|
8161 |
tcp |
MessageQueue |
|
61616 |
tcp |
MessageQueue |
|
8009 |
tcp |
Product 360 - Media Manager Web, ajp13/mod_jk connector |
|
59170 - 60678 |
tcp |
Product 360 - Media Manager desktop modules (Workflowmanager) (see port range calculation below) |
|
445 ,139 |
smb, tcp |
Windows file share ports for the Product 360 Core and Product 360 - Media Manager file communication |
Port range
Formula to calculate the port number of a module: Portnumber = modulo(StationId,100) * 15 + 59169 + ModuleId
==> New possible port range: 59170 - 60678
|
Module |
Module Id |
Port for Station 100 |
Port for Station 199 |
|
Process Watcher |
1 |
59170 |
60655 |
|
Pipeline |
2 |
59171 |
60656 |
|
Xob Adminconsole |
3 |
59172 |
60657 |
|
Mediapublisher |
4 |
59173 |
60658 |
|
Workflowmanager |
5 |
59174 |
60659 |
|
XML Connector |
6 |
59175 |
60670 |
|
Hotfolder |
7 |
59176 |
60671 |
|
Archive |
8 |
59177 |
60672 |
|
Interface |
9 |
59178 |
60673 |
|
Medias |
11 |
59180 |
60675 |
|
Production |
12 |
59181 |
60676 |
|
Administration |
14 |
59183 |
60678 |
Supplier Portal
|
Port |
Protocol |
Product 360 Module |
|
9090 |
http |
Product 360 - Supplier Portal (Tomcat Application Server) |
|
25 |
smtp |
Mail Server |
|
8080 |
http |
Product 360 - Media Manager REST |
|
1512 |
http |
Product 360 - Server Service API |