The Operations Center server cannot know in advance the location of other Operations Center component such as the Operations Center console. For this reason, Operations Center consoles and other Operations Center components issue a standard request to a target server when they want to communicate with it. This request travels over either the unsecured or secured Web port, and takes the form of a special URL. The originating Operations Center component parses the data returned by this request to determine which port number to use for further communication with the target.
If the Operations Center console contacts the target server using secure HTTP, the port value returned is the bidirectional IIOP port for secure data. If the Operations Center console contacts the target server using unsecured HTTP, then the port value returned is the bidirectional IIOP port for standard HTTP.
The server bidirectional port number is stored in the /OperationsCenter_install_path/html/classes/CORBA.properties file.
The InterConnection adapter (ICA) connection mechanism is similar to that of the Operations Center client to server. When specifying adapter properties, specify the hostname and HTTP port of the other Operations Center server to which you are connecting. It is possible to use the ICA over the HTTPS port. The ICA follows the same process of determining the other required ports. If the default of CORBA.bidir=true has not changed in the /OperationsCenter_install_path/html/classes/CORBA.properties file, the server uses one port for bidirectional IIOP communications.
The following sections describe how to configure ports:
In Table 4-1, an “X” in the first 3 columns identifies the different settings that are possible for Client/Server Communications Mode:
Table 4-1 Ports Defined in the Server Properties
|
Unsecured |
Secured |
Both |
Name |
Explanation |
|---|---|---|---|---|
|
X |
X |
X |
ooc.iiop.port |
Unidirectional IIOP port |
|
X |
X |
X |
ooc.iiop.acceptor.iiop.port |
Unidirectional IIOP port |
|
X |
X |
ooc.fssl.acceptor.RootPOAManager.port |
Bidirectional IIOP for SSL |
|
|
X |
|
|
ooc.iiop.acceptor.RootPOAManager.port |
Bidirectional IIOP for standard HTTP |
|
|
|
X |
ooc.iiop.acceptor.bidirManager.port |
Bidirectional IIOP for standard HTTP |
These values only display in the Operations Center console; they are not reported in formula.trc.
To identify the ports currently in use on the server and the specific usage of each port:
In the Explorer pane in the Operations Center console, expand the root Administration element.
Right-click Server, then select Properties.
Click the System Information tab.
Page down to view the port values.
To change the selected ports and their associated names, do one of the following:
Select a new value for the Client/Server Communication Mode.
Modify the port range in /OperationsCenter_install_path/config/mosdaemon.properties.
Review the following to determine whether you need to change server port ranges:
The Operations Center server uses a range of consecutive ports for its internal and external communications. The exact number depends upon the number of Java Virtual Machine (JVM) processes configured to start.
The default values for the range are specified in /OperationsCenter_install_path/config/mosdaemon.properties under the headings of:
Table 4-2 Default Server Port Specifications
|
Name |
Value |
|---|---|
|
MOSDaemon.ServerPortStart |
2000 |
|
MOSDaemon.ServerPortEnd |
3000 |
During every initialization, the server starts at the lower number specified in ServerPortStart and looks for a consecutive range of unused port equal to the number it needs. The selected values in this range remain fixed as long as the server remains active.
The default values described above are fine for everyday usage in most environments. However, the potential exists for the server to use a different range of ports each time the server starts. If the configuration of the physical server changes to allow another application to start before the server, the other application might acquire one or more of the ports at the beginning of the range that Operations Center software tries to use, thus forcing Operations Center software to use a different set of values. In situations with firewalls where the port values must be fixed and known, this is a problem.
It is possible to open specific ports. However, do not change the default values before carefully studying the current values and considering the potential effects of changes. Also note that making changes means accepting the responsibility of ensuring that the changes remain in effect through the application of patches, upgrades, and general maintenance of the server.
IMPORTANT:Do not change the default server port specification without carefully considering the potential impact.
If there is a requirement for the server’s external port usage to remain fixed, such as the existence of closed and secure firewalls, it is necessary to change the server configuration:
On the server, open the /OperationsCenter_install_path/config/daemon.ini file for editing.
Replace the Port=nnnn line, where nnnn is the numeric value, for the first port in the consecutive range of ports that Operations Center software should acquire.
On the server, this port is the ooc.iiop.port and ooc.iiop.acceptor.iiop.port.
To start correctly, the server must find the correct number of consecutive, available ports beginning with the specified port number.
Save the file.
Continue with Section 4.2.3, Configuring the Operations Center Port Assignments.
Specific port assignments are made for some of the Operations Center components. Review the following sections for information on making the port assignments:
The Web server ports on the Operations Center server allow access to the Operations Center server from the integrated Web server used for the Web servers used for access from the Operations Center console and dashboard. There are three possible ports to set on the Operations Center server:
Web server port (HTTP): Unsecured TCP/IP port number. The default is 80 for Windows and 8080 for UNIX.
Web server port (HTTPS): Secured TCP/IP port number. The default is 443 for both Windows and UNIX.
Web server shutdown port: Opens a socket connection to listen to shutdown commands for the Web server. The default is 8005 for both Windows and UNIX.
The settings for these ports are set in Configuration Manager on the Networking pane under the Tasks tab. For instructions, see Updating Server Settings Using the Configuration Manager.
For more information about Web server ports and communications security, see Communications Security
in the Operations Center Security Management Guide
The Experience Manager also uses a Web server port. The default is 8080, which might conflict with the default Web server port for the Manager Objects server for UNIX.
This is the only port definition that might conflict with Operations Center software.
You should use different ports for the individual Web servers.
For more information on Experience Manager, see the Operations Center Experience Manager Guide.
An Image Server is required by Operations Center to allow Web clients (including the Operations Center console and dashboard) to render dynamic and 3‑D charts. There are four ports to configure for the Image server:
Server port: The port to handle external communications between a Web client and the Image server. Because of firewall restrictions, the Web server’s name is actually used to access the Image server and then all Image server traffic is then redirected to the Image server. The default is 3001 for both Windows and UNIX.
Communications port: The port to handle internal communications between the Operations Center server and Image server. The default is 3002 for both Windows and UNIX.
Agent port: The port used by the Image server agent.
Admin port: The port used to access the administration application for the Web server.
The settings for these ports are set in Configuration Manager on the Networking pane under the Tasks tab. For instructions, see Updating Server Settings Using the Configuration Manager.
For more information about the Image Server port and communications security, see Communications Security
in the Operations Center Security Management Guide
In order for the dashboard to communicate with Operations Center, there need to be two ports opened. The first is for the Remote Invocation Method (RMI) directory which is the contact point for the dashboard to communicate with Operations Center. The second is randomly assigned by this contact point for the actual communications to occur. Because the second port is not set to a specific port, it makes it nearly impossible to use a firewall between the dashboard and Operations Center.
The Remote Services (RMI) port is configured in the Operations Center Configurations Manager and defaults to 1099 for both Windows and UNIX. The second port for actual communications can be set adding the following line to the config/Formula.custom.properties file:
mymo.rmi.port=port_number_1:port_number_2
where, port_number_1 is the first available port in a range of ports ending with port_number_2.
For more information about using the Formula.custom.properties file to customize configuration options, see Section 2.4, Making Custom Changes.
For more information about the dashboard, see the Operations Center Dashboard Guide.
For more information about the RMI ports and communications security, see Communications Security
in the Operations Center Security Management Guide
Third-party applications can use the Operations Center Web Services Application Programmer Interface (WASPI) for access to the Operations Center server. The Web services port must be configured and is 8084 by default for both Windows and UNIX.
For more information, see the Operations Center Web Services Guide.
SQL Views provides functionality in Operations Center that allows for third-party applications to have read access to Operations Center data. To allow access to the Operations Center server, you must designate a SQL Views port. The default is 1560 for both Windows and UNIX. The port is set in the Updating Server Settings Using the Configuration Manager on the Networking pane under the Tasks tab.
For more information, see the Operations Center SQL Views Guide.
For the Event Manager product, create sources that are access points for the Event Manager agents to receive data from hosts. As part of the source creation, specify a port for the following types of sources: server sockets and client sockets. Make sure that these port selections do not conflict with the ports already in use for Operations Center software.
For more information about the Event Manager, see the Operations Center Event Manager Guide.