Article ID: 2299893 - View products that this article applies to.
This article outlines the connectivity requirements for the various Opalis Integration Server components to interact with each other. If firewalls exist between the various components, rules may need to be introduced in your environment in order to allow the components to communicate.
The core components of an Opalis Integration Server implementation are:
Microsoft SQL Server
The configured TCP port for the desired Microsoft SQL Server instance must be accessible to the following Opalis Integration Server components:
By default, Microsoft SQL Server's default instance listens on TCP port 1433 however this can be changed by following the instructions in the Knowledge Base article below:
Opalis Integration Server Management Server
The Opalis Integration Server Management Server is a DCOM server which is exposed through the normal Windows Remote Procedure Call (RPC) interface. This will require that TCP port 135 and dynamic ephemeral ports are accessible by the following Opalis Integration Server components:
Remote Procedure Call (RPC) can be configured to limit the number of ephemeral ports that are exposed for the purposes of working with firewalls by leveraging the following Knowledge Base article:
Opalis Integration Server Operator Console
The Opalis Integration Server Operator Console is a web server that by default listens on TCP port 5314 which must be accessible by the following Opalis Integration Server components:
Deploying Opalis Integration Server Components
Using the Opalis Integration Server Deployment Manager that is installed with the Opalis Integration Server Management Server requires the ability to access the computer where the Opalis Integration Server component(s) are to be installed via SMB/CIFS. As a result, TCP ports 135, 139 and 445 must be accessible on the target computer from the Opalis Integration Server Management Server.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2299893 - Last Review: February 7, 2011 - Revision: 8.0
Contact us for more help