Test 000-007: IBM Tivoli Netcool/OMNIbus V7.3 Implementation

Section 1 - Planning

1. Given the customer environment, tools, and network architecture, identify event sources, probes, and gateways so that a list of event sources, probes, and gateways is available.


With emphasis on performing the following tasks:

1. Review the customer's environment and tools.
2. Review the network architecture.
3. Determine the network device type.
4. Determine the applications.
5. Determine the security requirements.
6. Determine the types of probes required.
7. Determine the types and gateway required.
8. Determine the number of licenses required.


2. Given the number of devices and device types, calculate the number of events so that the number of expected events is available.


With emphasis on performing the following tasks:

1. Find the number of devices in the network.
2. Find the type of devices in the network.
3. Determine the existing event load per hour.
4. Determine the existing event load for integrations.
5. Determine the types of integrations (if any are required).
6. Calculate the number of events based on the number and type of devices.


3. Given the customer organization, groups, and tools, identify which groups require access so that the number of users is identified.


With emphasis on performing the following tasks:

1. Review customer organization and groups.
2. Identify operators.
3. Identify administrators.
4. Identify super users.
5. Verify access is required with groups.
6. Determine integrations to customer's existing LDAP applications.
7. Determine the security requirements (firewall, ACL).


4. Given the IBM Tivoli Netcool/OMNIbus (Tivoli Netcool/OMNIbus) architecture, event volume, and supported hardware and software, calculate event volume and calculate sizing so that the required number of hardware, memory, and disk space per hardware is defined.


With emphasis on performing the following tasks:

1. Review the preferred hardware requirements with respect to space and memory.
2. Review the hardware requirements with respect to probes.
3. Determine the number of events that will occur per hour.
4. Determine the number of events that will occur on each probe type per hour.
5. Determine if network bandwidth will support event throughput.
6. Determine OS patch requirements based on chosen platform and product release notes.
7. Determine integrated products version to ensure compatibility.
8. Determine security requirements.
9. Produce a detailed list of hardware, software, and network requirements.
10. Review the event source.
11. Review the number and type of probes proposed.
12. Review the number and type of gateways proposed.
13. Determine if any proxy server proposed.
14. Determine if any display or desktop ObjectServer proposed.
15. Determine failover requirements.


5. Given the implementation requirements, design the Tivoli Netcool/OMNIbus architecture document so that Tivoli Netcool/OMNIbus architecture satisfies the customer requirements.


With emphasis on performing the following tasks:

1. Verify all software needed.
2. Verify hardware components.
3. Determine which software will run on each hardware component.
4. Determine product integration probes and gateways.
5. Determine network infrastructure requirements.
6. Determine user access and authentication requirements.
7. Determine the type of failover.
8. Define components, locations, and network connectivity.
9. Determine naming conventions.
10. Determine directory for installation.
11. Review customer compliance requirements.


6. Given Tivoli Netcool/OMNIbus architecture document, network requirements, communication protocols, and customer security requirements, review and document the information so that the security requirements are documented.


With emphasis on performing the following tasks:

1. Review network requirements and determine compatible security types.
2. Review customer security requirements and determine suitable security type.
3. Document the security requirements.


7. Given the software requirements, architecture, and user ID access requirements, determine the installation requirements for disk, user account, and platform so that the system is prepared for the product installation.


With emphasis on performing the following tasks:

1. Review the product documentation.
2. Determine space available on customer's hardware.
3. Identify disk requirements for components to be installed.
4. Ensure disk space is adequate on the system.
5. Determine default location of installation.
6. Determine authentication methods.
7. Determine user account required for installation/upgrade.
8. Determine access or privileges required for installation/upgrade.
9. Determine directories that need write access permissions.
10. Verify whether the platform is supported.
11. Obtain the installation package.

Section 2 - Installation

1. Given the disk space, privileged ID, and OS dependencies install ObjectServer so that the ObjectServer is installed and running.


With emphasis on performing the following tasks:

1. Set the NCHOME variable to the IBM Tivoli Netcool/OMNIbus (Tivoli Netcool/OMNIbus) home directory.
2. Verify ID has privileges to install application.
3. Verify ID has write permissions to NCHOME directory.
4. Verify disk space requirements.
5. Verify OS dependencies.
6. For upgrade from older versions, verify compatibility with previous versions.
7. For upgrade from older versions, if DES encryption is being used, change encryption from DES to AES before upgrade.
8. Determine mode of installation.
9. Run upgrade or installation command.
10. Select components to be installed.
11. Choose the appropriate ports.
12. Enter an ObjectServer name following ObjectServer naming standards.
13. Verify installation logs.
14. Configure omni.dat file.
15. Generate interfaces file.
16. Create the ObjectServer.
17. Determine what type of ObjectServer (display, desktop, dual-write, and primary) and use appropriate command line option to start ObjectServer.
18. Verify connection to the ObjectServer by using SQL command.
19. For upgrades, run SQLs to upgrade schemas to 7.3.


2. Given the customer's environment, solution architecture, and details required, install/upgrade the required probes, so that the probes and gateways are successfully installed.


With emphasis on performing the following tasks:

1. Review the customer's environment, solution architecture, and detailed requirements.
2. Determine the network device type.
3. Determine the event source for probe.
4. Determine the configuration required on the network device for probes and gateways.
5. Determine the existence of relevant old probe's and gateway's files (in case of an upgrade).
6. Determine the changes required in ObjectServer's database schema to enable the successful working of probe or gateway.
7. Determine any third party dependency for the working of probes and gateways (ex. for ODBC gateway a database in operational state is needed).
8. Determine hardware and OS systems.
9. Determine the security/network requirements for communication of probes and gateways.
10. Install the required probe based on the event source.
11. Install the required gateway.


3. Given that ObjectServer has been installed and configured, and environmental variables have been set, migrate existing ObjectServer data so that the existing ObjectServer data has been migrated.


With emphasis on performing the following tasks:

1. Determine the appropriate method for migration (console vs. GUI).
2. Obtain access to systems and servers.
3. Log in to the Tivoli Netcool/OMNIbus environment.
4. Execute migration commands.


4. Given the TIP Admin ID password, with Webtop and Web GUI installed, follow export/import steps so that data is migrated from Webtop 2.x into Web GUI.


With emphasis on performing the following tasks:

1. Copy migration_tool_export.zip to Webtop server.
2. Extract migration_tool_export.zip on Web GUI server.
3. Run the command to export user data.
4. Export NGF data.
5. Run migration_export command.
6. Copy output files to Web GUI host.
7. Verify if Web GUI is running.
8. Update migration tool setting.
9. Run the migration import command.
10. Import generatedUsersandGroups.ldif into LDAP.
11. Import users and groups.
12. Restart TIP server.
13. Delete settings.properties on the Webtop & Web GUI server.
14. Merge the default filters with global filters.
15. Run migration import -rollback command to roll back imports.


5. Given the installed product and the Tivoli Netcool/OMNIbus architecture documentation, determine and configure the appropriate settings for properties files so that the properties file for ObjectServer is configured.


With emphasis on performing the following tasks:

1. Review the user access.
2. Determine which software component is installed on the given system.
3. Gather the required information about the software component installed from the documentation.
4. Verify if the required properties file is available.
5. Determine encryption requirements and make the appropriate changes to the properties file.
6. Determine if it is the primary or backup ObjectServer and set the properties file.
7. Set ObjectServer name based on ObjectServer naming standards.
8. Determine other requirements and set properties file appropriately.
9. Restart ObjectServer.


6. Given the disk space, privileged ID, OS dependencies, and type of display ObjectServer, install the display ObjectServer so that the display ObjectServer is up and running.


With emphasis on performing the following tasks:

1. Verify ID has privileges to install application.
2. Verify ID has write permissions to NCHOME directory.
3. Verify disk space requirements.
4. Verify OS dependencies.
5. Verify compatibility with previous versions.
6. Determine mode of installation.
7. Determine the command for installation.
8. Run the installation command.
9. Select components to be installed.
10. Verify installation logs.
11. Generate interfaces file.
12. Ensure omni.dat and sql.ini file are configured.
13. Determine what type of display ObjectServer (desktop, dual-write, primary) and use appropriate command line option to create the ObjectServer.
14. Start the ObjectServer.
15. Verify connection to the ObjectServer by using SQL command.
16. Apply SQL customization to the ObjectServer.


7. Given the supported Java versions and compatibility with previous Tivoli Netcool/OMNIbus versions, initiate installation of an Admin client so that the Admin client is installed and running.


With emphasis on performing the following tasks:

1. Verify if Admin GUI can be upgraded from the current version.
2. Verify ID has administrator privileges to install Admin client.
3. Verify supported Java version.
4. Determine the network/port communication with the ObjectServer.
5. Start the installation.
6. Select/Unselect components to install.
7. Configure performance tuning parameters.
8. Verify installation by starting Admin client.


8. Given the disk space, privileged ID, and OS dependencies install or upgrade Web GUI so that the Web GUI server is installed or upgraded and ready for configuration.


With emphasis on performing the following tasks:

1. For upgrade from older versions, verify compatibility with previous versions.
2. If older version is 1.3, 2.0, or 2.1, follow steps for new installation, with installation directory in a different location from where Webtop is installed. If older version is 2.2, backup the following files:
1. Backup all files under install_dir
2. Backup DE files
3. Verify ID has privileges to install application.
4. Verify ID has write permissions to NCHOME directory.
5. Verify disk space requirements.
6. Verify OS dependencies.
7. Determine mode of installation.
8. Identify command for upgrade or installation.
9. Run upgrade or installation command.
10. Enter ObjectServer datasource name.
11. Verify installation logs.
12. For upgrades from version 2.2, merge the default global filters with the default.
13. For upgrades from version 2.2, start and stop TIP server.

Section 3 - Configuration

1. Given the privileged ID with ObjectServer and gateway installed, configure ObjectServer gateways so that the gateways are configured.


With emphasis on performing the following tasks:

1. Identify the type of gateway to be configured (uni-directional or bi-directional).
2. View the properties file.
3. Edit the gateway properties file.
4. Specify name of ObjectServer, which the gateway will read from.
5. Specify the location of map definition file.
6. Edit Mapping file.
7. Set mapping values.
8. Specify gateway reader properties.
9. Specify table replication definition file.
10. Perform performance tuning parameters.
11. Configure appropriate settings based on requirements.
12. Set secure connections to the ObjectServer.
13. Enable/Disable failback.
14. Stop/Start gateway.
15. Verify configuration.


2. Given the installed product, IBM Tivoli Netcool/OMNIbus (Tivoli Netcool/OMNIbus) architecture document, modify and verify the configuration of locale, environment variable, gateway, ObjectServer and process control so that ObjectServer, gateway, and process control properties are modified as per the Tivoli Netcool/OMNIbus architecture document.


With emphasis on performing the following tasks:

1. Review the Tivoli Netcool/OMNIbus architecture document.
2. Determine the environment variables to be set.
3. Verify if the super user access is available.
4. Verify if the user has permission to write into the user profile file.
5. Verify if the SSL or FIPS needs to be implemented from the Tivoli Netcool/OMNIbus architecture document.
6. Verify if any third party software needs to be configured to listen to Omnibus events.
7. Check if the automation needs to be configured for the third party software.
8. Verify the required properties file for the ObjectServer is available.
9. Verify the required properties file process control is available.
10. Set the required properties in the ObjectServer properties file, Omni.dat file, and interface file with respect to Tivoli Netcool/OMNIbus architecture.
11. Set the required properties, maps, and definition files in the gateway with respect to Tivoli Netcool/OMNIbus architecture.
12. Determine and configure appropriate settings on the properties file.
13. Execute the proper command or modify the properties in proxy ObjectServer to work in secure mode.
14. Modify the required properties in the gateway in accordance with the type of integration in respect to ObjectServer or third party.
15. Modify the omni.dat file and interface file to set the SSL communication with ObjectSever.
16. Modify the required properties file to enable the FIPS security for SSL Connection.
17. Modify the required properties file to integrate Tivoli Netcool/OMNIbus with third party authentication tool.
18. Add or Modify the required automation to enable the required changes to be made as per the gateway probes or ObjectServer or per the Tivoli Netcool/OMNIbus architecture documentation.
19. Execute the proper command-line command to export and import the ObjectServer settings.
20. Modify the process control properties file as required.
21. Execute the proper command to enable the PAM authentication while starting the process control.


3. Given the installed and configured ObjectServer, Tivoli Netcool/OMNIbus architecture document and hardware, identify and configure the probes requested so that the requested probes are configured as per the Tivoli Netcool/OMNIbus architecture documentation.


With emphasis on performing the following tasks:

1. Review the Tivoli Netcool/OMNIbus architecture document.
2. Determine what type of probes have been requested and purchased.
3. Check if the required ports for the probes are available.
4. Install the requested probe.
5. Check if the SSL or FIPS is implemented in the ObjectServer.
6. Check the required properties to modify are in the probes.
7. Check if the required changes are made to the host file.
8. Configure performance tuning parameters.
9. Modify the required properties in the probes as per the Tivoli Netcool/OMNIbus architecture document.
10. Modify the rules file in accordance with events and requests by the client.
11. Include or modify the lookup files as requested.
12. Verify if the environment variable for the Tivoli Netcool/OMNIbus knowledge library is set.
13. Modify the probe's properties file to enable the probe to run in failover mode.
14. Modify the properties file or the command line options to start the probe in secure mode.


4. Given the installed ObjectServer, installed Web GUI and Tivoli Netcool/OMNIbus architecture document, configure the required tools so that the requested tools are available for users.


With emphasis on performing the following tasks:

1. Review the Tivoli Netcool/OMNIbus architecture document.
2. Determine if tools are required on Tivoli Netcool/OMNIbus desktop or Web GUI or both.
3. Determine the type of tools - SQL, CGI, HTTP, or external command.
4. Identify commands with syntax required for each of the above tools.
5. Identify if the tools to be created fall under either the menu alerts or the tools menu.
6. Create the tools.
7. Assign appropriate privileges based on requirements.
8. Assign all classes or specific classes based on requirements.
9. Assign tools to menu.
10. Restart native desktop client or restart AEL client on Web GUI.
11. Verify tools appearing on the menu.
12. Verify compatibility of tools with the OS on which the tool is to be executed.


5. Given the installed and configured ObjectServer, and installed process agent, modify and verify the required properties file and configure the process control and required user for the process control so that the process control is configured with the required process.


With emphasis on performing the following tasks:

1. Review the Tivoli Netcool/OMNIbus architecture document.
2. Determine the environment variables to be set.
3. Verify if the user access is available.
4. Verify if the SSL or encryption needs to be implemented from the Tivoli Netcool/OMNIbus architecture document.
5. Modify the required ObjectServer properties file to assign the process agent user and password.
6. Modify the process control properties file as required based on the Tivoli Netcool/OMNIbus architecture document.
7. Deploy the startup script to start the process agent when the system starts.
8. Execute the proper command to enable the PAM authentication while starting the process control.


6. Given the Tivoli Netcool/OMNIbus architecture, configure the proxy server and probes so that the proxy server is running with probes connected.


With emphasis on performing the following tasks:

1. Review the Tivoli Netcool/OMNIbus architecture.
2. Ensure the proxy server is configured in the interfaces.
3. Modify proxy server properties as required.
4. Configure the proxy server in secure mode (if required).
5. Start the proxy server.
6. Configure the proxy server to connect to the probes.
7. Configure the probes to connect in secure mode (if required).
8. Start the probes.
9. Verify that the probes are connected to the proxy.


7. Given the Tivoli Netcool/OMNIbus architecture and installed ObjectServers and gateways, configure the multi-tiered architecture so that the multi-tiered ObjectServers and gateways are running.


With emphasis on performing the following tasks:

1. Review the Tivoli Netcool/OMNIbus architecture.
2. Determine how to handle severity on reduplication.
3. Configure server interfaces.
4. Create a primary aggregation ObjectServer.
5. Create a backup aggregation ObjectServer.
6. Configure a bilateral-directional aggregation failover ObjectServer gateway.
7. Create a collection ObjectServer (if required).
8. Configure a unilateral-directional collection to aggregation routing ObjectServer gateways (if required).
9. Create a display ObjectServer (if required).
10. Configure a unilateral-directional aggregation to collection routing ObjectServer gateways (if required).
11. Configure a display ObjectServer for load-balancing of event list clients.
12. Create custom triggers.
13. Setup components to run under process control.
14. Start ObjectServer and gateways.
15. Review performance data to ensure events are received.


8. Given the Tivoli Netcool/OMNIbus architecture, customer requirements on event data, and customer processes, modify the ObjectServer schema and create ObjectServer automations, so that the ObjectServer is customized to meet requirements.


With emphasis on performing the following tasks:

1. Review the Tivoli Netcool/OMNIbus architecture.
2. Review customer requirements on event data to collect.
3. Add ObjectServer columns to store required event data.
4. Review customer processes.
5. Identify processes that can be automated.
6. Use process steps to write automation pseudo-code.
7. Write pseudo-code into ObjectServer triggers and procedures.


9. Given the Tivoli Netcool/OMNIbus architecture, authentication requirements, and Web GUI user processes, configure Web GUI so that the Web GUI is customized to meet requirements.


With emphasis on performing the following tasks:

1. Review Tivoli Netcool/OMNIbus architecture.
2. Configure Web GUI for HTTPS.
3. Configure SSL connection to the ObjectServer.
4. Configure LDAP integration.
5. Configure and initialize data source files for Web GUI.
6. Configure single Sign-On.
7. Configure users, user groups, user roles, and group roles.
8. Configure DB2 for high availability of Web GUI multiple server instances.
9. Configure load-balancing of the Web GUI.
10. Review Web GUI user processes.
11. Identify tools required for Web GUI user processes.
12. Create tools for Web GUI.
13. Configure launch in context integrations.
14. Configure WAAPI.
15. Configure SSL for WAAPI.


10. Given that Tivoli Netcool/OMNIbus has been installed and configured, use the administrator GUI to add an external tool, so that an external tool has been configured.


With emphasis on performing the following tasks:

1. Verify ID has privileges to create a tool.
2. Determine the external command to execute in the tool.
3. Determine OS compatibility with the external command.
4. Determine ID privileges to run the external tools.
5. Within the tools menu, click 'Add Tool'.
6. Enter the tool name.
7. Enter the external command from the executable tab.
8. Configure access permissions.
9. Specify the platform.
10. Enable the tool.


11. Given that the Web GUI is installed and running and administrator permission is available, configure the user permissions and Portlet configurations so that user permissions and Porlets are configured.


With emphasis on performing the following tasks:

1. Verify if ID has privileges to configure the portlet configurations and user permissions.
2. Select the security menu.
3. Select the user's roles menu.
4. Select the user for whom you want to configure permissions.
5. Add the permissions.
6. Determine a Portlet to copy. .
7. Select Settings -> Portlet in the navigation panel.
8. Copy one of the Portlets.
9. Enter the new Portlet name.
10. Select the roles with access to the Portlet.
11. Save the configuration.


12. Given ID requirements and installed and configured Tivoli Netcool/OMNIbus, configure the Accelerated Event Notification (AEN) client so that the AEN client is configured.


With emphasis on performing the following tasks:

1. Verify ID has privileges to start the AEN client.
2. Start the AEN client.
3. If starting the AEN for the first time, right-click the AEN icon and select Properties.
4. Configure the notification settings.
5. Configure the browser settings.
6. Configure Message and Channels tabs, as required.
7. Select Ok.
8. Given that the AEN client has previously been configured, log on to the AEN client by right-clicking the icon and selecting 'Sign In'.
9. Input valid ObjectServer user details and select 'Log In'.

Section 4 - Administration

1. Given that the ObjectServer has been installed and configured and ID privileges are available, perform administration tasks on the ObjectServer so that the ObjectServer is administrated.


With emphasis on performing the following tasks:

1. Start and stop the ObjectServer.
2. Start and stop the IBM Tivoli Netcool/OMNIbus (Tivoli Netcool/OMNIbus) administrator.
3. Connect to an ObjectServer.
4. Connect to a process agent.
5. Create and restore backups.
6. Add new ObjectServers.
7. Generate the interfaces file.
8. Create/delete triggers.
9. Create/delete signals.
10. Create/delete procedures.
11. Set up log rotations.


2. Given the customer environment, solution architecture, and requirement details, administer/configure the Web GUI so that the Web GUI is successfully administered.


With emphasis on performing the following tasks:

1. Review the customer's environment, solution architecture, and requirement details.
2. Determine the security/network requirements for communication of Web GUI with ObjectServer and LDAP's (if any).
3. Determine the users and users' privilege levels in Web GUI for different pages, views, Portlets, event filters, event menus, and event tools.
4. Determine the requirement of custom pages/Portlets to suffice the customer requirement.
5. Determine the failover architecture of the Web GUI to ensure the changes are propagated to each server in the failover cluster.


3. Given the customer environment, solution architecture, and requirement details, create backups of Tivoli Netcool/OMNIbus/Web GUI so that Tivoli Netcool/OMNIbus/Web GUI has successful backups.


With emphasis on performing the following tasks:

1. Review the customer's environment, Solution architecture and requirement details.
2. Determine the failover architecture of the Tivoli Netcool/OMNIbus/Web GUI to ensure the backup is complete for active servers.
3. Determine the backup location and frequency.
4. Determine the rotation/archival policy for backups.
5. Backup Tivoli Netcool/OMNIbus/Web GUI.


4. Given the customer environment, solution architecture, and requirement details, deploy startup scripts so that startup scripts are successfully deployed.


With emphasis on performing the following tasks:

1. Review the customer's environment, solution architecture, and requirement details.
2. Determine the OS.
3. Determine the variable that needs to be used while creating startup scripts.
4. Determine the unit level at which scripts need to be deployed.
5. Deploy the startup scripts.


5. Given the customer environment, solution architecture, and requirement details, create filters and views as per the user's requirement so that filters and views are successfully created.


With emphasis on performing the following tasks:

1. Review the customer's environment, solution architecture, and requirement.
2. Determine requirements for filers and views.
3. Determine user access to filters and views.
4. Set filters and views based on requirements.

Section 5 - Performance Tuning and Problem Determination

1. Given that there are multiple log file management commands, manage log files so that log files for the ObjectServer and probes are configured properly.


With emphasis on performing the following tasks:

1. Identify the location of the ObjectServer, probe, and gateway log files.
2. Review and configure the settings required to increase the log level for the ObjectServer, probes, and gateways.
3. Review and set log rotation requirements.
4. Review and set the properties files for probes and gateways related to logging.
5. Review the ObjectServer for checkpointing.
6. Review and configure audit files for the ObjectServer.
7. Review and set the message level for the ObjectServer, probes and gateways.


2. Given that a set of probe rules has been created, check the syntax so that the probe syntax is verified.


With emphasis on performing the following tasks:

1. Create or modify a rules file for a probe.
2. Run the nco_p_syntax against the rules file.
3. Check the output of the nco_p_syntax command.
4. Review and correct probe rules syntax errors.
5. Rename the probe rules file to the code that will be run from the probe properties file.
6. Verify the probe rules file syntax.


3. Given that the ObjectServer is configured and running, verify the communication settings for the ObjectServer so that communication between the components is identified and verified.


With emphasis on performing the following tasks:

1. Review secure host settings for the ObjectServer.
2. Review the server interfaces on ObjectServer.
3. Review the server interfaces on probes.
4. Review the server interfaces on gateways.
5. Review Datasource settings on the GUI.
6. Modify the communications settings.
7. On UNIX, distribute the modified omni.dat or interfaces file.
8. Restart the ObjectServer and ancillary components to ensure communication settings are set properly.
9. Verify log files to ensure communication between the components.


4. Given that a probe has been installed, check the properties file so that the properties file is configured properly.


With emphasis on performing the following tasks:

1. Review and set appropriate settings for the probe properties file.
2. Stop and start the probe.
3. Ensure that the probe is running.
4. Run the Configuration Analyzer.
5. Verify the output.
6. Review the log file.


5. Given that IBM Tivoli Netcool/OMNIbus has been installed, configure and verify the Tivoli Netcool/OMNIbus environment variables, so that the environment variables have been configured.


With emphasis on performing the following tasks:

1. Edit the system user profile.
2. Define Tivoli Netcool/OMNIbus environment variables.
3. Verify environment variables.


6. Given that Tivoli Netcool/OMNIbus has been installed and configured, customize Tivoli Netcool/OMNIbus ObjectServer configuration so that the ObjectServer performance is optimal.


With emphasis on performing the following tasks:

1. Check frequency of triggers.
2. Check execution scope of triggers: once only, for each row.
3. Check SQL used in trigger for performance.
4. Check whether 'update via' is being used.
5. Check desktop filters.
6. Check other appropriate settings.
7. Check profile and trigger statistics logs.