Skip to main content

 spacer
Professional certification
spacer
  >  		spacer
Certifications
spacer
  >  		spacer
Test information
spacer

Test 933: IBM Tivoli Netcool/OMNIbus V7.2 Implementation


spacer
spacer Overview spacerObjectives spacer Test Preparationspacer
spacer
spacer

Section 1 - Planning

  1. Given the customer requirements in the Statement of Work, review the solution details in order to confirm the architecture. With emphasis on performing the following steps:
    1. Review proposed architecture.
    2. Determine high level architecture.
    3. Determine unique requirements
    4. Determine hardware and OS.
    5. Evaluate port availability (firewall and Access Control Lists)
    6. Determine contacts at the customer.
    7. Gather Users, Roles, and Physical location.
    8. Evaluate security requirements.
    9. Determine integrations to existing customer applications.

  2. Given the design details develop an architecture document. With emphasis on performing the following steps:
    1. Verify all software needed.
    2. Determine product integration probes and gateways.
    3. Define components, locations, and network connectivity.
    4. Determine naming conventions.
    5. Determine directory for install.
    6. Review customer compliance requirements. (Acceptance testing.)
    7. Determine configuration of messages on the end nodes

  3. Given a design document obtain the required components so that you are ready to install Netcool/OMNIbus.

    4. With emphasis on performing the following steps:
    1. Determine appropriate installer (console vs. GUI).
    2. Obtain network availability.
    3. Obtain access to systems and servers.
    4. Obtain authorization for network.
    5. Obtain install media.

Section 2 - Installation

  1. Given that environment variables have been set and sourced on a supported UNIX/Linux server, install Netcool/OMNIbus V7.2 using the console, so that the selected Netcool/OMNIbus V7.2 components are installed. With emphasis on performing the following steps:
    1. Download the required omnibus binaries from IBM support site.
    2. Locate the binaries on the UNIX/Linux server in an appropriate temporary location.
    3. Un-tar the package and run the install script ./INSTALL -console.
    4. Accept the license agreement
    5. Select the required features:

      6. Desktop
      Gateways
      Process Control
      Servers
      ConfPack
      Administrator
      AEN Client
      Local Help System
      Install selected features

  2. Given OMNIbus is installed, download the probes patch from the IBM support site and install the patches using $NCHOME/omnibus/install/nco_patch so the probe is installed. With emphasis on performing the following steps:
    1. Download probe patch from the IBM support site.
    2. Untar the patch to a tmp directory.
    3. Run $NCHOME/omnibus/install/nco_patch –install
    4. Type 'yes' and hit enter to install the probe.

  3. Given OMNIbus V7.2 is installed on a UNIX host and a FixPack is downloaded from the IBM support site, install the FixPack , so that the selected FixPack has been installed. With emphasis on performing the following steps:
    1. Run the FixPack install command: $NCHOME/install/ncisetup –install

      2. Individual should receive a notice that the patch has successfully been installed.

  4. Given OMNIbus V7.2 has been installed and configured on UNIX/Linux, export configuration of the ObjectServer and import it into another ObjectServer using nco_confpack, so that the ObjectServer configuration can be exported and imported. With emphasis on performing the following steps:
    1. Create a list of exportable configuration items using $NCHOME/omnibus/bin/nco_confpack -list -server NCOMSI -file /tmp/NCOMSI_list
    2. Edit package list /tmp/NCOMSI_list to contain only the items to export
    3. Export NCOMSI configuration using: $NCHOME/omnibus/bin/nco_confpack -export -file /tmp/NCOMSI_list - package /tmp/NCOMSI_package.
    4. Import NCOMSI configuration in to NCOMS2 using: $NCHOME/omnibus/bin/nco_confpack -import –package /tmp/NCOMSI_package -server NCOMS2.

Section 3 - Configuration

  1. Given a supported UNIX/Linux operating system and Netcool OMNIbus V7.2 and a user with proper permissions, configure and verify environmental variables, so that the environmental variables have been configured. With emphasis on performing the following steps:
    1. Start the UNIX text editor.
    2. Edit system home profile /etc/profile
    3. Define Netcool Environment Variables: $NCHOME; $LD_LIBRARY_PATH (opt); $PATH (opt.); $LANG (if required).
    4. Netcool users must source this file when they login.

  2. Given a UNIX/Linux OS, and the ObjectServer was installed by the root user, the root user owns the $NCHOME directory. Configure the system so that a non root user (netcool) is a member of the netcool group.

    3. With emphasis on performing the following steps:
    1. Find an unused group number for example 550 by doing a more /etc/group
    2. Add a new group netcool: groupadd -g 550 netcool
    3. Add root user to the netcool group within /etc/group.

  3. Given OMNIbus V7.2 is installed on a IPv4 or IPv6 UNIX/Linux server, configure OMNIbus communications, so that communications are configured. The hostname may or may not be resolvable to the IP address (IPv4 or IPv6). With emphasis on performing the following steps:
    1. If the hostname is resolvable to an IP address, edit: $NCHOME/etc/omni.dat and replace "omnihost" with local servers hostname. If the hostname is not resolvable to an IP address, replace "omnihost" with the appropriate IPv4 or IPv6 address.
    2. Run $NCHOME/bin/nco_igen.

  4. Given OMNIbus V7.2 has been installed and configured, environmental variables have been set on a supported Windows server, verify OMNIbus communications, so that OMNIbus communications are available.

    5. With emphasis on performing the following steps:
    1. Run the Netcool Server Editor. Run ->All Programs->Netcool OMNIBUS-> System Utilities -> Server Editor.
    2. Highlight appropriate ObjectServer and select 'test" check for "servers available" window.

  5. Given an OMNIbus install on UNIX/Linux, create a working object server instance using available Netcool commands and files , so that an ObjectServer has been created and an instance configured.

    6. With emphasis on performing the following steps:
    1. Open a command line and run $NCHOME/omnibus/bin/nco_dbinit -server .
    2. Edit $NCHOME/etc/omni.dat file and set the ObjectServer name and port.
    3. Run $NCHOME/bin/nco_igen.

  6. Given that OMNIbus is installed on UNIX/Linux, start the ObjectServer and run nco_ping to verify the ObjectServer is running, so that the ObjectServer is available. With emphasis on performing the following steps:
    1. Run $NCHOME/omnibus/bin/nco_objserv -name
    2. Verify the ObjectServer is running by using the $NCHOME/omnibus/bin/nco_ping

  7. Given an ObjectServer is installed and running on a supported Unix/Linux OS, start and verify a local event list, so that local event lists can connect to the local ObjectServer. With emphasis on performing the following steps:
    1. Launch event list ($NCHOME/omnibus/bin/nco_event).
    2. Enter username and password.
    3. Verify event list connects to the ObjectServer.

  8. Given OMNIbus V7.2 has been installed and configured, environmental variables have been set, install the remote desktop, so that the remote desktop on a supported Windows desktop, so that the remote desktop can connect to the ObjectServer. With emphasis on performing the following steps:
    1. Locate and un-zip Omnibus binaries on remote desktop machine.
    2. Run the OMNIbus install package, setup.exe.
    3. Accept the license agreement.
    4. Choose the install directory.
    5. Deselect every program feature except the desktop component:
    6. Click the Installation button.
    7. Reboot the desktop on completion of installation.
    8. Create an entry for the objectserver in the Servers Editor on the remote desktop
    9. Launch the event list by selecting Start>All Programs>Netcool Suite> Event List and log into the ObjectServer.

  9. Given an OMNIbus V7.2 install, edit the probe properties file, set the SERVER property to the name of the ObjectServer and configure a probe to connect to an ObjectServer, so that the Probe is configured. With emphasis on performing the following steps:
    1. Open the Probe properties file.
    2. Set the server property to the name of the ObjectServer.

      3. Given OMNIbus V7.2 has been installed and configured, environmental variables have been set and sourced on a supported UNIX/Linux server, the simnet probe package is installed, start and verify the probes, so that the probes are running and tested. With emphasis on performing the following steps:
    3. Modify the simnet.props file and verify the ObjectServer target in $NCHOME/omnibus/probes/.
    4. Modify rules file (simnet.rules) to include the host system name in the manager field.
    5. Start the probe using the command line (nco_p_simnet).
    6. Check process list to verify probe is running.
    7. Launch the event list and verify probe events in the ObjectServer and verify events parsed correctly.
    8. Check for errors in log file.

  10. Given OMNIbus 7.2 is installed, configure an unidirectional gateway, so that the unidirectional gateway has been configured. With emphasis on performing the following steps:
    1. Create a directory for gateway files eg: $NCHOME/omnibus/gates/UNI_GATE.
    2. Copy all files from $NCHOME/omnibus/gates/objserv_uni to $NCHOME/omnibus/gates/UNI_GATE:

      3. objserv_uni.props
      objserv_uni.map
      objserv_uni.reader.tblrep.def
      objserv_uni.startup.cmd
    3. Rename all files copied to match unique name of the uni-directional gateway, eg UNI_GATE.*
    4. Edit UNI_GATE.props file and modify the following properties:

      5. Name
      PropsFile
      Gate.MapFile
      Gate.StartupCmdFile
      Gate.Reader.Server
      Gate.Reader.TblReplicateDefFile
      Gate.Writer.Server
    5. Edit UNI_GATE.map file and UNI_GATE.reader.tblrep.def file, modify the entries to define which objectserver tables and fields are accessed by the gateway.

  11. Given OMNIbus is installed, configure a Oracle gateway Remedy Gateway, or ODBC gateway so that the unidirectional gateway has been configured.
  12. Given OMNIbus is installed, both ObjectServers (that will be connected via the gateway) are running, start an ObjectServer gateway. Update an event in an ObjectServer (source ObjectServer if a uni-gateway is used), confirm that the same event in the other objectserver has similarly changed, so that the gateway has been configured correctly and initialized. With emphasis on performing the following steps:
    1. Start a ObjectServer gateway using $NCHOME/omnibus/bin/nco_g_objserv_uni- name uni or $NCHOME/omnibus/bin/nco_g_objserv_bi - name BIGATE.
    2. Verify that the gateway is working by deleting and or modifying an event on the one ObjectServer and checking to see that the modification is made on the other ObjectServer.

  13. Given OMNIbus is installed add a server entry for nco_pa in omni.dat, run nco_igen, edit nco_pa.conf, set the hostname and name of ObjectServer in nco_pa.conf and configure process control, so that process control is configured. With emphasis on performing the following steps:
    1. Open $NCHOME/omnibus/etc/nco_pa.conf file.
    2. Change the name of the ObjectServer from NCOMS (if different).
    3. Set the omnihost value to the hostname of the local machine under nco_routing entry.
    4. Set user and password values under nco_routing if using secure mode, else delete the user and password values.
    5. Add an entry to $NCHOME/etc/omni.dat for nco_pa and run $NCHOME/bin/nco_igen.

  14. Given OMNIbus is installed on a UNIX/Linux system, process control is configured, run nco_pad, verify PA status using nco_pa_status to start process control and verify that process control is available and running.

    15. With emphasis on performing the following steps:
    1. Run $NCHOME/omnibus/bin/nco_pad.
    2. Run $NCHOME/omnibus/bin/nco_pa_status -server NCO_PA.
    3. Manually kill one of the running processes using ‘kill pid’ where pid is the process id of the process that was killed.
    4. Run $NCHOME/omnibus/bin/nco_pa_status -server NCO_PA to verify that the killed process is running with a different process ID.

  15. Given OMNIbus is installed on UNIX/Linux and root level access has been granted, configure, run and verify the startup scripts, so that start-up scripts have been configured and verified. With emphasis on performing the following steps:
    1. Execute the start-up script, $NCHOME/omnibus/install/startup/install.
    2. Verify the creation of symbolic links.
    3. Input/verify the process control name.
    4. Select secure mode or not.
    5. Enter a value for the netcool_license_file variable. Save the file.
    6. Start nco script via the command line nco start.
    7. Verify that the process control has started.
    8. Run nco stop. Verify nco_pad has stopped.

  16. Given an OMNIbus install on UNIX/Linux, copy all gateway files from $NCHOME/omnibus/gates/objserv_bi to a new directory, configure gateway properties file, configure a server entry for the bi-directional gateway and create a bi-directional gateway between two ObjectServers, so that bi-directional gateway is configured.

    17. With emphasis on performing the following steps:
    1. Create a directory for gateway files. Example: $NCHOME/omnibus/gates/BI_GATE.
    2. Copy all files from $NCHOME/omnibus/gates/objserv_bi to $NCHOME/omnibus/gates/BI_GATE.
    3. Edit $NCHOME/omnibus/gates/BI_GATE/objserv_bi.props and set the following properties: Gate.MapFile; Gate.StartupCmdFile; Gate.ObjectServerA.Server; Gate.ObjectServerA.TblReplicateDefFile; Gate.ObjectServerB.Server; Gate.ObjectServerB.TblReplicateDefFile.
    4. Copy $NCHOME/omnibus/gates/BI_GATE/objserv_bi.props to $NCHOME/omnibus/etc/BI_GATE.props
    5. Edit $NCHOME/etc/omni.dat and add an entry for BI_GATE.
    6. Run $NCHOME/bin/nco_igen.

  17. Given OMNIbus V7.2 has been installed and configured, add a user so that users are created in OMNIbus.

    18. With emphasis on performing the following steps:
    1. From the main OMNIbus Administrator window, select the "user" tab and then select "user".
    2. Click the "Add User" icon in the toolbar.
    3. Enter a Name and Select an unused User ID.
    4. Enter a Full Name.
    5. Put a check in the "Create Conversion" checkbox
    6. From the "Groups" tab, double-click Administrator to assign the administrator role. Click "OK".

  18. Given OMNIbus V7.2 has been installed and configured, environmental variables have been set, create a view based on the statement of work, so that an event view has been created. With emphasis on performing the following steps:
    1. Launch View Builder from the Event List.
    2. Select Filet --> New.
    3. Enter View Name.
    4. From Available Field pane select Node, Severity, and Summary.
    5. From Available Sort Fields pane select Severity.
    6. In the Sorted by pane, double-click the Severity icon to set sort order to descending order.
    7. Click Apply
    8. Click Close.
    9. Click File --> Save from Main Event List window.

  19. Given OMNIbus V7.2 has been installed and configured, utilize the Event List GUI (nco_event) to create a Filter using the Desktop client, so that an event filter has been set. With emphasis on performing the following steps:
    1. Click Filter Builder button on Sub-Event List.
    2. Click File --> New.
    3. Provide Filter Name.
    4. Select Severity from the Column drop down menu.
    5. Select Greater than or Equal to from Operator drop down.
    6. Select Minor (#) from Value drop down menu.
    7. Click Apply.
    8. Click File --> Save from the Main Event List window.

  20. Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) to add a restriction filter, so that a restriction filter has been added. With emphasis on performing the following steps:
    1. From the main OMNIbus Administrator window, select the "Users" tab and then select Restriction Filters.
    2. Select Add Restriction Filter from the toolbar.
    3. Assign a Name to the filter.
    4. Enter the filter criteria.
    5. Click OK.

  21. Given OMNIbus V7.2 has been installed and configured, create a new menu, so that a menu is created.

    22. With emphasis on performing the following steps:
    1. From the Menu tab select Add New Item within the Configuration Manager GUI.
    2. Select Menu Item Type, Tool, and Title, then click OK.

  22. Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) create a new database field, so that a new database field has been created. With emphasis on performing the following steps:
    1. Select the System tab from the Administrator GUI.
    2. Select Databases.
    3. Select Databases Alerts and Table Status.
    4. Select Add Column icon from the menu.
    5. Enter Column Name, Data Type.
    6. Click OK.

  23. Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) add a tool, so that a tool has been added. With emphasis on performing the following steps:
    1. Within the Tools menu, click Add Tool.
    2. Enter a Name.
    3. Select Enter Relevant Tool Instructions.
    4. Click OK.

  24. Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) create a trigger, so that a trigger has been created. With emphasis on performing the following steps:
    1. Select DB Trigger.
    2. Select Trigger Group.
    3. Enter Trigger Name.
    4. Set Trigger Priority.
    5. Set Action on Delete.
    6. Set Apply To pane to Statement.
    7. Enter SQL code for action. Begin Write into dellogs1 values ('The following row was deleted at; getdate (), old.Node, old.Summary); End
    8. Enable Trigger.
    9. Click OK.

  25. Given OMNIbus V7.2 has been installed and configured, the ObjectServer is running, customize the Rules file, so that a customized probe rules file is available. With emphasis on performing the following steps:
    1. Open probe rules file with text editor.
    2. Create a temporary element to hold a value extracted from @Summary.
    3. Assign a probe property to the @Summary field.
    4. Add a "switch" statement to execute a rule based on node name.
    5. Use an "include" statement to include a new rule file segment.
    6. Make a change so that @AlertGroup is updated on deduplication.
    7. Discard events with the word "test" in the @Summary field.

      8. 2Create a lookup table to look up department name based on node name.
    8. Turn on probe details if @Summary=unknown.
    9. Test the syntax of the new rules file and debug.
    10. Update the probe rules file without stopping the probe.

  26. Given an OMNIbus install running on UNIX/Linux, configure primary ObjectServer (NCOMS_P), create a backup ObjectServer (NCOMS_B), set the BackupObjectServer property to TRUE, configure bi-directional gateway, configure triggers & procedures and create a high availability architecture, so that automated failover and failback architecture is configured. With emphasis on performing the following steps:
    1. On the primary ObjectServer host, create the primary ObjectServer.
    2. On the backup ObjectServer host, create the backup ObjectServer.
    3. Edit $NCHOME/omnibus/etc/NCOMS_B.props and set the Backup ObjectServer property to 'True'.
    4. Configure a bi-directional gateway between the primary and backup ObjectServer.
    5. On primary ObjectServer host, configure $NCHOME/etc/omni.dat for the primary and backup ObjectServer entries.
    6. On primary ObjectServer host run $NCHOME/bin/nco_igen. Copy $NCHOME/etc/interfaces. file to the backup ObjectServer host.
    7. On backup ObjectServer, enable 'backup_startup, backup_counterpart_down, backup_counterpart_up' triggers for automation failover & failback.
    8. On backup ObjectServer, disable 'primary_only' trigger group for automation failover & failback.

  27. Given OMNIbus V7.2 has been installed and configured, add entries to omni.dat for primary and desktop ObjectServer run the command $NCHOME/bin/nco-igen, copy the $NCHOME/etc/interfaces. file from the primary ObjectServer host to the desktop ObjectServer host, configure the desktop ObjectServer, configure a unidirectional gateway between the primary and desktop ObjectServer to set up desktop architecture, so that the desktop architecture is configured. With emphasis on performing the following steps:
    1. On the primary ObjectServer host edit $NCHOME/etc/omni.dat and add entries for the primary and desktop ObjectServers.
    2. Run $NCHOME/bin/nco_igen copy $NCHOME/etc/interfaces. file from the primary ObjectServerhost to the desktop ObjectServer host.
    3. Create and configure the primary ObjectServer.
    4. Create the desktop ObjectServer using $NCHOME/omnibus/bin/nco_dbinit -desktopserver -server DESKOS.
    5. Start the desktop ObjectServer.
    6. Using $OMNIHOME/bin/nco_sql insert the following row in to the master national table or the DESKOS. (O, MASTEROS, 1).
    7. Configure a uni-directional gateway between the primary ObjectServer and the desktop ObjectServer.

  28. Given OMNIbus V7.2 has been installed and configured on UNIX/Linux, export configuration of the ObjectServer and import it into another ObjectServer using nco_confpack, so that the ObjectServer configuration can be exported and imported. With emphasis on performing the following steps:
    1. Create a list of exportable configuration items using $NCHOME/omnibus/bin/nco_confpack -list -server NCOMSI -file /tmp/NCOMSI_list
    2. Edit package list /tmp/NCOMSI_list to contain only the items to export
    3. Export NCOMSI configuration using: $NCHOME/omnibus/bin/nco_confpack -export -file /tmp/NCOMSI_list - package /tmp/NCOMSI_package.
    4. Import NCOMSI configuration in to NCOMS2 using: $NCHOME/omnibus/bin/nco_confpack -import –package /tmp/NCOMSI_package -server NCOMS2.

  29. Given OMNIbus V7.2 has been installed and configured, environmental variables have been set, add a group, so that a group is added. With emphasis on performing the following steps:
    1. From the main OMNIbus Administrator window, select the Users tab and then select Groups.
    2. Click the Add Group icon.
    3. Assign a name to the group.
    4. Assign an unused Group ID.
    5. Assign a Role.
    6. Assign a Restriction Filter.
    7. Click OK.

  30. Given OMNIbus V7.2 has been installed and configured, create a class, so that a class has been created.

    31. With emphasis on performing the following steps:
    1. Using the Configuration Manager, select Add Class from the Visual menu.
    2. Assign an identifier.
    3. Name the class.
    4. Click OK.

  31. Given OMNIbus V7.2 has been installed and configured, create a role, so that a role is available.

    32. With emphasis on performing the following steps:
    1. Within the Configuration Manager select the Users tab.
    2. Select Roles and Add New Role menu item.
    3. Add Role name.
    4. Assign Role Permissions.
    5. Click Save.

  32. Given an OMNIbus installed and running, configure omnibus probes rules to flag some events for acclerated event notification, create channels and configure triggers to send event details using these channels so that accelerated event notification is configured for some events. With emphasis on performing the following steps:
    1. Modify probe rules file using text editor and flag the events which has Summary like 'Port failure'.
    2. Configure channels to broadcast event data for the flagged events.
    3. Using IDUC EVTFT and IDUC SNDMSG, create and configure post-insert or post-update or post-reinsert triggers to send event notification to AEN client.

  33. Given OMNIbus V7.2 has been installed and configured on a UNIX/Linux system, configure the Accelerated Event Notification (AEN) Client so that the AEN Client is configured. With emphasis on the following steps
    1. Start the AEN Client using the command $NCHOME/omnibus/bin/nco_aen
    2. If starting the AEN for the first time, right-click the AEN icon and select ‘Properties’
    3. On the Application tab make the following selections:
    4. Notification settings:

      5. Server (from drop-down list – Note if unpopulated, or required server is not available, add details to the interfaces file))
      View in either Netcool Event List or Netcool Webtop
      Launch in Control Settings
      For either Netcool Event List or Netcool Webtop, specify the required Server and View
      iBrowser Settings
    5. Specify the Browser to use.
    6. Configure Message and Channels tabs, as required
    7. Select ‘Ok’
    8. Given that the AEN Client has previously been configured, log on to AEN Client by right-clicking icon and select ‘Sign In’
    9. Input a valid ObjectServer user details and select ‘Log In’
    10. Observe that the Icon changes from x to y..

  34. Given OMNIbus V7.2 has been installed on a UNIX/Linux system, configure the ObjectServer system so that it is Accelerated Event Notification messages can be sent so that the ObjectServer AEN feature is configured.

    35. With emphasis on the following steps:
    1. Determine whether AEN events are to be generated at a probe or by a trigger.
    2. If AEN events are to be generated by a probe:
    3. Create a dedicated ObjectServer Flag field.
    4. Modify the probe rules file to set the Flag field for AEN events
    5. Create a database trigger to respond to either the Flag field or the appropriate database action/database condition, using SQL commands IDUC EVTFT or IDUC SNDMSG to generate the AEN.
    6. Configure a Channel to broadcast AEN event data by doing the following:
    7. From with Netcool/OMNIbus Administrator, select Channels from System menu
    8. Right-click within the GUI to select ‘Add a new Channel’
    9. Within the Channel Details screen, add a name for the Channel
    10. On the ‘Channels’ tab, select ‘Channel Columns Detail’ button to be able to define the ObjectServer Table and Fields to use for the notification, then select ‘Ok’
    11. On the ‘Recipients’ tab, select ‘Add new Channel Recipient’ button to be able to define recipients for the notification, then select ‘Ok’
    12. When complete, click the ‘Ok’ button on the Channel Details screen
    13. Test the Channel notification by right-clicking the Channel and selecting ‘Send Message’

  35. Given that ObjectServer V7.2 is running on a UNIX/Linux platform and the Tivoli Health Monitoring Agent for ObjectServer V7.2 is installed. Configure the agent so that the agent will monitor the ObjectServer. With emphasis on the following steps:

    36. @cd //no/bin
    @Import the schema and automations to the ObjectServer as follows:
    $NCHOME/bin/nco_sql -user root -S < itm_os.sql

Section 4 - Performance Tuning and Problem Determination

  1. Given OMNIbus V7.2 has been installed and configured, add devices to simnet.def file and run the simnet probe to generate test events using the simnet probe, so that test events are generated. With emphasis on performing the following steps:
    1. Edit $NCHOME/omnibus/probes/ARCH/simnet.def file and add line device1 0 50 & device2 3 100.
    2. Set the property in $NCHOME/omnibus/probes/ARCH/simnet.props to $NCHOME/omnibus/probes/ARCH/simnet.def.
    3. Set the server property in $NCHOME/omnibus/probes/ARCH/simnet.props to the name of the ObjectServer. Server:
    4. Start the simnet probe using $NCHOME/omnibus/probes/nco_p_simnet

  2. Given a failover architecture, verify that the failover architecture is working, so that failover functionality has been confirmed. With emphasis on performing the following steps:
    1. Shut down the Master ObjectServer
    2. Connect desktop client to the backup ObjectServer using $NCHOME/omnibus/bin/nco_event and check that the events are coming into the backup ObjectServer.
    3. Restart the Master ObjectServer.
    4. Connect the desktop client to the Master ObjectServer using $NCHOME/omnibus/bin/nco_event and check that the client indicates it is connected to the Master ObjectServer.

  3. Given on a UNIX/Linux OS that ObjectServer V7.2 is installed but unable to start, determine why the ObjectServer does not start. With emphasis on performing the following steps:
    1. Check the environment variables $NCHOME.
    2. Check to make sure that the ObjectServer has been created using $NCHOME/omnibus/bin/nco_dbinit.
    3. Check to make sure that the entry for the ObjectServer exists in $NCHOME/etc/omni.dat and in the interfaces file.
    4. Ensure that the port for the ObjectServer is not already in use.
    5. Ensure that the proper user is starting the object server process.

  4. Given an OMNIbus installed and the license server and configured, determine why probes do not connect, so that the probes are running. With emphasis on performing the following steps:
    1. Check probes log file.
    2. Verify that the probe’s designated objectserver is running.
    3. Check whether the interfaces file on the probe server is correctly defined
    4. Verify that the probe server has network connectivity to the objectserver host.
    5. Check whether any firewall settings are affecting communications

      6. +#Given an OMNIbus installed and the license server is configured, determine why the desktop does not start, so that the desktop is running and connected to the ObjectServer. With emphasis on performing the following steps:
    6. Ensure that X server settings are set correctly.
    7. Ensure that the ObjectServer to which the desktop is connected is running.

  5. Given OMNIbus V7.2 has been installed and configured, users are complaining of slow response time, determine the reason for slow event list response, so that the problem can be resolved. With emphasis on performing the following steps:
    1. Check # of events.
    2. Check OS profiles.
    3. Check event rates.
    4. Check # of desktops.
    5. Check process on OS server.
    6. Check resource usage of OS server, memory, CPU, & disk.
    7. Check network response times.
    8. Check log files.
    9. Check automations.
    10. Check the number of journals and details.
    11. Determine what other components are connected.

  6. Given OMNIbus V7.2 has been installed and configured, optimize system performance so that the ObjectServer performance is optimized. With emphasis on performing the following steps:
    1. Check frequency of triggers.
    2. Check execution scope of triggers: once only, for each row.
    3. Check number of details. details($*).
    4. Check SQL used in trigger for performance.
    5. Check whether 'update via' is being used.
    6. Check desktop filters.

Section 5 - Administering

  1. Given a running and verified system, complete post implementation process including system backup, documentation, acceptance testing, so that customer acceptance can be obtained. With emphasis on performing the following steps:
    1. Backup the installed system.
    2. Create system environment documentation.
    3. Verify compliance with customer requirements.
    4. Knowledge transfer to staff.
    5. Demonstrate system to client.
    6. Complete acceptance testing.
    7. Customer sign-off.

Section 6 - Training

  1. Given new users, provide training, so that users are educated on the new system.

    2. With emphasis on performing the following steps:
    1. Train users and administrators.

spacer
Test registration

Authorized Prometric test centers (worldwide testing)