|
|
Communications between the Cisco Info Server and other components, such as Admin Desktops running on separate hosts, is controlled by entries in the interfaces file in the /opt/Omnibus/etc directory.
This file can be edited directly. However, to assist you in maintaining the interfaces file, Cisco Info Center includes the nco_xigen utility.
This chapter describes the interfaces file and the use of the nco_xigen utility. In addition, this chapter describes a number of additional utilities that you can use to implement your Cisco Info Center installation.
For communications to be established between the components of Cisco Info Center, you must create an interfaces file.
The interfaces file contains information about:
 |
Note The interfaces file is created automatically when you run the nco_config configuration utility to configure the Info Server component and other components. After running nco_config during the initial installation procedure, you can modify the interfaces as needed by running the nco_xigen utility. |
When Cisco Info Center components are started, they search for the $OMNIHOME/etc/interfaces.solaris2 file.
You can also use the nco_igen command's -java parameter to generate the interfaces file used specifically for Java support.
Without an appropriate interfaces file, the software looks for a file named $OMNIHOME/etc/interfaces and uses that as the interfaces file.
If that file does not exist, the programs are unable to contact any Cisco Info Servers and they fail to run.
Complete these steps to run the nco_xigen utility.
The Server Editor window may display an empty list or display the list of Cisco Info Servers, Info Gateways, or Process Control that may have been configured, along with the host name and the TCP port to which they are allocated. The list of servers is stored in the $OMNIHOME/etc/omni.dat file and any changes you make in the Server Editor window are saved in this file.
Note, although it is possible to edit the $OMNIHOME/etc/omni.dat file directly, it is recommended you use the Server Editor window to edit the list of servers. However, there may be occasions when you want to edit the connections data file. For more information about how to edit this file, see Section, "Editing the Connections Data File" in Appendix B, in the Cisco Info Center Administrator Reference guide.
Step 2 To change the host name, complete these steps:
a. Click on the server name to select it.
b. Specify the name of the host machine in the Host field.
c. Click on the Update button.
d. Click on the Apply button.
Cisco Info Center allows you to specify backup hosts for each server defined. This ensures that when a server, for example, NCOMS, fails on the first host, Cisco Info Center attempts to connect to NCOMS on the backup host.
For example, to specify a backup host for NCOMS:
1. Click on the CISCO server in the main list.
2. Specify a different host name in the Host field.
3. Click on the Add button.
In Figure 6-2, the NCOMS server shows two backup hosts: muppet and darkstar.
To change the priority of the server in the list:
1. Click on the server name to select it.
2. Click on either the Raise or Lower buttons to move the server up or down the list, respectively.
To add a new server to the interfaces file:
1. Specify the name of the server into the Name field.
2. Specify the name of the host machine in the Host field.
3. Specify the port number into the Port field.
4. Click on the Add button to add the new server.
5. Click on the Apply button to apply the changes.
1. Click on the server name to select it, or specify the server name in the Name field.
2. Edit the Name, Host, or Port fields, as required.
3. Click on the Update button.
4. Click on the Apply button to apply the changes.
1. Click on the server name to select it.
2. Click on the Remove button.
3. Click on the Apply button to apply the changes.
By default, the Server Editor window generates the $OMNIHOME/etc/interfaces.solaris2 interfaces file for use on Solaris 2.
You can then copy this file to the $OMNIHOME/etc directory on each of the participating Cisco Info Center machines.
This section describes how to install the start-up scripts and configure the login procedure. The multi- and single-system installation processes automatically add the automatic start-up procedures to the /etc/init.d/nco file.
To manually start the installed Cisco Info Center components, execute the following command:
To manually shut down the running Cisco Info Center components, execute the following command:
Each Cisco Info Center user must have the OMNIHOME environment variable set and the $OMNIHOME/bin directory added to the PATH environment variable.
When you start the Event List, the default Event List configuration is displayed. The Event List displays one Monitor box.
You can, however, create a new Event List configuration and save it as default.elc. You should then copy this file to the /opt/Omnibus/desktop directory. (You must be logged in as user root to write to this directory.)
The Login window is displayed when you start the Desktop tools. To modify the Server button on the Login window, use a skip filter file. This filter is an external file that comprises regular expression statements to define the servers that will not appear in the Login window.
To use this skip file, create the $OMNIHOME/etc/skip-filter file.
Posted: Tue Jun 13 16:30:27 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.