HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations - نسخه متنی

Tammy Zitello

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید


13.14 CONFIGURE A NEW OVO OPERATOR


The administrator is responsible for defining the customized environment for each operator. The operator configuration is controlled through the Motif graphical user interface by logging on as the OVO Administrator. At this time, there are no administrator functions (such as customization, configuration distribution, and so on) available through the Java console. You can also log on as opc_adm in the JAVA GUI, but you will have operational capabilities only. The administrator can define operator responsibilities based on specific skills or roles via a profile. The profile contains all the tools, applications, node groups, and message groups required by the operator. When the operator account is configured with a name, password, preferences, node hierarchy, the profile is added. Use this method to quickly configure many operators based on the roles they have within the enterprise. Every operator will not see all messages; only those that originate from the nodes which are members of the assigned Node Groups and have a Message Group assigned to the user. By limiting the scope of the messages the operator sees, we maintain focus on the important events that cause messages in the browser. This enables the operations, development, support, and other experts with the knowledge of the applications, servers, and network and services experience to own the problem until it is resolved.

The operator relies upon the tools assigned in their profile to get the job done. In some instances, operators require tools that are not included in the profile. After the application is defined in the administrators' application bank window, assign the application to the operator. Assign the operator's application desktop.

For example, if you want to assign the OV Services to one operator and not a profile, open the application bank in the operators' configuration. Open the application bank window and drag and drop the OV Service application group into the operator's application window. The next time the operator logs into the system he will see new menu items and network tools in the root window. She will also see the Internet icon in the root window.

13.14.1 Summary of the Process to Create a New Operator


The following example is meant to give a high-level overview of the major steps required to configure a new operator account.


Step 1. Start opc and login as opc_adm.

Step 2. In the Node Bank, select

WindowUser Bank . This opens the the User Bank.

Step 3. Select

ActionUserAdd . This opens another screen for you to customize the new operator account.

Step 4. Alternately, to modify an existing operator account, select the icon for the account in the User Bank, right-click, and select modify from the pop-up menu.

Step 5. The Add/Modify User window contains the configuration components for a typical OpenView Operator. Define the user account name, password, Preferences, Node Hierarchy, Responsibilities, Applications, and Profile(s).

Step 6. If you have configured a Profile or installed SPIs that contain the components for this operator's role, assign the Profile. The steps to assign a profile were described in Section 13.11, "Profiles and User Banks."

Step 7. If this is the only customization you require at this time, click

OK .

Step 8. Add the Managed Nodes that will be managed by the operator (covered in Section 13.9.1).

Step 9. Assign the Managed Nodes to appropriate Node Groups (covered in Section 13.9.2).

Note

Steps 8 and 9 are not part of the operator configuration. They are listed here as reminders of additional tasks to complete.

13.14.2 Functional Tests for the Operator Account


When a new operator account is configured (or an existing account modified), perform a few functional tests before you turn the account over to the production operator. Several recommended tests along with suggestions on how to perform them are shown here:

  • Test the login account
    Login as the operator; use the account name/password.

  • Test the message environment
    Use the

    opcmsg command after it is installed.

  • Test the integrated OVO Applications
    From the operator UI, open the application desktop. Select a node and drag and drop the node onto an application.

  • Test the integrated OV Services
    Open the Root window, check to see whether the Internet Icon appears, and drill down (double-click) on the icon to see additional network topology (if applicable, not all operators have this service assigned).

  • Test the integrated tools
    Select items in the Root Menu, for example Tools, SNMP MIB Browser.

  • Test the Message Browser Layout
    Open the message browser; ensure that the messages are arriving from the nodes. Perform this test this after the managed nodes are configured and assigned to the operator.

  • Test the Java Client Console
    Start the Java console and use the operator account to login.



    / 276