The NvORB wraps the IBM Tivoli NetView network management system with a CORBA object interface to enable Operations Center software to access many of NetView’s core functions and data over a network. The Tivoli NetView adapter in Operations Center software connects to NvORB over the network (or locally, if NetView and Operations Center software are installed on the same machine) to provide real-time access to managed objects on NetView from any Web browser through the Operations Center console. Use Operations Center software to automate and contain NetView elements in a centralized location.
For instructions on creating and configuring IBM Tivoli NetView adapters after the NvORB is installed, see Section 2.17, IBM Tivoli NetView.
NvORB is installed as an extension to Tivoli NetView. When the first NetView user interface application starts on the NetView server, the NvORB process also starts and is ready for contact by the server. However, stopping the NetView user interface application also stops the NvORB process. This is a limitation of the NetView APIs. Operations Center software automatically reconnects when the NetView console is relaunched.
Table 10-13 outlines the system requirements for installing the NvORB:
Table 10-13 System Requirements
|
OS |
Description |
|---|---|
|
Windows |
|
|
AIX |
|
|
Solaris |
|
The default port for NvORB is 1572. Prior to installing NvORB, determine if port 1572 is already in use on the NetView server.
To configure ports for NvORB:
To verify port 1572 is available, enter one of the following at a command prompt:
|
Windows: |
netstat ‑an | find "LISTEN" | find "1572" |
|
UNIX: |
netstat ‑an | grep "LISTEN" | grep "1572" If this command results in a line ending with LISTENING, then select a different port. |
To select a port other than 1572, using any text editor, replace the port number in the /usr/bin/registration/C/NvORB.arf file.
Use a port number above 1000 if running the NetView client as a user other than root.
The command to install NvORB depends on the operating system. In all cases, load the installation file from the ORBS directory on the Operations Center CD.
To install NvORB:
Verify NetView is not running.
Do one of the following:
On Windows NT, launch \ORBS\NetView\NT\NetView‑7.09.exe
On AIX, issue the following command:
restore -qvxf /ORBS/NetView/AIX/nvorb_7.09.bff
On Solaris, issue the following command:
pkgadd -d /ORBS/NetView/SolSparc/nvorb_7.09
Typically no configuration is required after installing NvORB. However, if the TCP/IP port number 1572 is already in use on the NetView server, then change a configuration file.
On UNIX systems, set the DISPLAY environment variable to an available X server display.
To set the DISPLAY environment variable for bsh or ksh, use the following setting:
DISPLAY=<X server display>:0.0 export DISPLAY
To set the DISPLAY environment variable for csh, use the following setting:
setenv DISPLAY <X server display>:0.0
By default, any host can connect to the ORB. However, it is possible to specify the hosts that can connect to the ORB and thereby deny access to all other hosts.
To restrict access to NvORB:
Open the /registration/C/NvORB.arf file.
Locate the line that starts the NvORB, as shown:
Command ‑Initial ‑Shared "directory_path_name ‑OAport 1572";
where directory_path_name is the NvORB installation directory.
Append the following option to the code that initiates the ORB:
‑CORBA.Allow IP_addresses
where IP_addresses are those that are permitted to access the NvORB.
For example:
Command ‑Initial ‑Shared "directory_path_name ‑OAport 1572 ‑CORBA.allow 206.55.26.20,206.55.26.21,206.55.26.23
When NetView starts, it loads a default map named default. The NvORB is set to run automatically when NetView starts, regardless of the map loaded at startup. However, it is possible to modify the registration file, NvORB.arf, to specify which map to load on startup.
IMPORTANT:If the map name specified in the .arf file and the map name given to NetView in the command line do not match, NvORB does not start.
To start NvORB only when it loads a specific map, add the following option to the NvORB.arf file:
‑map map_name
where map_name is the name of the map to load at NetView startup.
You can abbreviate the ‑map command to ‑m. For example:
Command ‑Initial ‑Shared directory_path_name NvORB ‑m Test ‑OAport 1572
where directory_path_name is the NvORB installation directory.
By default, NetView invokes NvORB at run time after selection of the appropriate menu item or executable symbol. Each selection loads and executes another instance of NvORB.
To change the behavior when NvORB starts:
Select and add one of three special flags to the command entry in the NvORB.arf file.
Enter the following at a command prompt in the NvORB.arf file:
Command –Initial ‑Shared ‑Restart directory_path_name NvORB ‑m mapname ‑OAport 1572
where directory_path_name is the NvORB installation directory.
The following explains the three switches:
–Initial: Instructs NetView to start NvORB when the NetView NNM starts.
–Shared: Instructs NetView to run only a single instance of the NvORB command at any time. In addition, this NvORB instance is shared, servicing multiple action requests. If another instance of NV starts, it attempts to start another instance of the ORB. This usually results in an ORB error because of a port conflict.
–Restart: Instructs NetView to restart NvORB automatically if the application stops while the NetView NNM is still running.
For more information concerning NetView process flags and commands, see the documentation provided by NetView.
To append to the log file every time the ORB starts, add the command line argument ‑LogAppend to the NvORB.arf file. For example:
Command ‑Initial ‑Shared "/usr/OV/bin/NvORB ‑OAport 1572 ‑LogAppend"
To start the NvORB:
Start the IBM/Tivoli TME 10 NetView Console by performing one of the following steps:
Enter netview at a command prompt.
Click the NetView Console icon in the NetView program folder.
Define an adapter in the Operations Center software to integrate with this NetView server.
Specify the NetView server’s hostname and port number (1572 or the one chosen earlier).
To stop the NvORB, stop the NetView user interface, which also stops the NvORB.