Cloud & Smarter Infrastructure Professional Certification...

This information is IBM Copyrighted and may not be distributed without the approval of IBM.

Cloud & Smarter Infrastructure Professional Certification Program

Study Guide Series

Exam C2010-657 - IBM Tivoli Netcool/OMNIBUS V7.4 Implementation


Purpose of Exam Objectives .................................................................. 3

High-level Exam Objectives .................................................................... 4

Detailed Exam Objectives ........................................................................ 8

Detailed Exam Objectives ........................................................................ 8

Section 1 - Planning ................................................................................................ 8

Section 2 - Installation ......................................................................................... 12

Section 3 - Configuration .................................................................................... 16

Section 4 - Administration .................................................................................. 23

Section 5 - Performance Tuning and Problem Determination .................. 25

Next Steps .................................................................................................. 28


Purpose of Exam Objectives

When an exam is being developed, the Subject Matter Experts work together to define the role the certified individual will fill. They define all of the tasks and knowledge that an individual would need to have in order to successfully implement the product. This creates the foundation for the objectives and measurement criteria, which are the basis for the certification exam. The Tivoli Certification item writers use these objectives to develop the questions that they write and which will appear on the exam. It is recommended that you review these objectives. Do you know how to complete the task in the objective? Do you know why that task needs to be done? Do you know what will happen if you do it incorrectly? If you are not familiar with a task, then go through the objective and perform that task in your own environment. Read more information on the task. If there is an objective on a task there is about a 95% chance that you WILL see a question about it on the actual exam. After you have reviewed the objectives and completed your own research, then take the assessment exam. While the assessment exam will not tell you which question you answered incorrectly, it will tell you how you did by section. This will give you a good indication as to whether you are ready to take the actual exam or if you need to further review the materials. Note: This is the high-level list of objectives. As you review these objectives, click for a more detailed level of how to perform the task.


High-level Exam Objectives

Section 1 - Planning

1.1

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

1.2 Given the number of devices, device types, and system/application monitoring, calculate the number of events so that the number of events expected is available.

1.3

Given the customer organization, users, groups, and tools, identify which user groups require access to what functions, and the type of authentication required so that the number of user access requirements is identified.

1.4

Given the IBM Tivoli Netcool architecture, event volume, and hardware and software supported, calculate event volume and perform sizing calculation so that the required amount of hardware, memory and disk space per hardware is identified or defined.

1.5 Given the implementation requirements ,design the IBM Tivoli Netcool/OMNIbus (Netcool/OMNIbus) architecture document so that Netcool/OMNIbus architecture satisfies the customer requirements.

1.6

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

1.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.

1.8 Given the availability of prerequisite scanner utility, verify the prerequisites on target installation servers so that the prerequisites have been identified.

Section 2 - Installation

2.1 Given the disk space requirements, privileged ID and operating system dependencies, install ObjectServer so that the ObjectServer is installed and running.

2.2 Given the customer environment and solution architecture, install/upgrade the required probes so that the probes and gateways are available.

2.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.

2.4 Given the IBM Tivoli Integrated Portal 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.


2.5 Given that the ObjectServer is installed, determine and configure the appropriate settings for properties files so that the properties file for ObjectServer is configured.

2.6 Given the disk space, privileged ID, operating system dependencies and type of Display ObjectServer, install display ObjectServer so that the display ObjectServer is up and running.

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

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

Section 3 - Configuration

3.1. Given the privileged ID with ObjectServers and gateway installed, configure ObjectServer gateways so that the gateways are configured between two ObjectServers.

3.2.

Given that IBM Tivoli Netcool/OMNIbus (Netcool/OMNIbus) is installed, Netcool architecture document, modify and verify the configuration of locale, environment variable, gateway, and ObjectServer so the Process agent is managing the ObjectServer and gateway as per the Netcool architecture document.

3.3.

Given the Installed and configured ObjectServer, Netcool architecture document and hardware, Identify and configure the probes requested so that the requested probes are configured as per the Netcool architecture documentation.

3.4. Given the Installed ObjectServer , installed Web GUI and Netcool architecture document , configure the required tools so that the requested tools are available for users.

3.5.

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

3.6. Given the Netcool Architecture, configure the Proxy server and probes so that the Proxy server is running with probes connected.

3.7. Given the Netcool architecture and installed ObjectServers and gateways, configure the multi-tiered architecture so that the multi-tiered ObjectServers and gateways are running.

3.8.

Given the Netcool 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.

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


3.10. Given Netcool/OMNIbus has been installed and configured, configure pages and views so that pages and views are customized per the customer’s requirements.

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

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

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

3.14. Given installed and configured Netcool/OMNIbus, configure the HTTP/OSLC interface so that the HTTP/OSLC interface is configured.

3.15. Given Netcool/OMNIbus has been installed and configured, configure HTTP and OSLC so that you can communicate with the probes using HTTP and OSLC.

3.16.

Given the Installed and configured ObjectServer, Netcool architecture document, and hardware, Identify and configure the probes for remote communication so that remote configuration of probes is complete.(this is what the online docs states).

Section 4 - Administration

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

4.2. Given the customer environment, solution architecture and detailed requirements, administer/configure the Web GUI so that the Web GUI is successfully administered.

4.3. Given the customer environment, solution architecture and detailed requirements, create Backups of Web GUI so that Web GUI has successful backups.

4.4. Given the customer environment, solution architecture, and detailed requirements, deploy startup scripts so that startup scripts are successfully deployed.

4.5. Given the customer environment, Solution architecture and detailed requirements, create filters, views and maps in Web GUI as per the user’s requirement so that filters, views and maps are successfully created.

Section 5 - Performance Tuning and Problem Determination

5.1 Given that there are multiple Log Files Management commands, manage log filse so that log files for the ObjectServer, Probes, and Gateways are configured properly.

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


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

5.4 Given that a Probe has been installed, check the properties file so that the properties files are configured properly.

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

5.6 Given Netcool/OMNIbus has been installed and configured, customize Netcool/OMNIbus ObjectServer configuration such that the ObjectServer performance is optimal.

5.7 Given Netcool/OMNIbus Web GUI has been installed and configured, log in to Web GUI so that the HTTP access to Netcool/OMNIbus Web GUI verified.


Detailed Exam Objectives

Section 1 - Planning

1.1. Given the customer environment, tools, and network architecture, identify event sources, probes and gateways for the event management solution deployment so that a list of event sources, probes and gateways is available.

SUBTASK(S): 1.1.1. Review the customer’s environment and tools. 1.1.2. Review the network architecture. 1.1.3. Determine the network device types. 1.1.4. Determine the servers and applications. 1.1.5. Determine the security requirements. 1.1.6. Determine the types of probe required. 1.1.7. Determine the types and gateway required. 1.1.8. Determine the number of licenses required. 1.1.9. Determine the mobile, remote, cloud, and virtual environment operations

requirements. 1.1.10. Determine the requirements for operational support via bidirectional

(ObjectServer and probes) integration API. 1.1.11. Determine the types of reports required. 1.1.12. Determine the legacy event management integration. 1.2. Given the number of devices, device types, and system/application

monitoring, calculate the number of events so that the number of events expected is available.

SUBTASK(S): 1.2.1. Find the number of devices in the network. 1.2.2. Find the type of devices in the network. 1.2.3. Determine the existing event load per hour. 1.2.4. Determine the existing event load for integrations. 1.2.5. Determine the types of integration if any required. 1.2.6. Calculate the number of events based on the environment. 1.2.7. Determine the need for potential ObjectServer table indexes. 1.2.8. Determine the need for event flood control thresholds for performance

considerations. 1.3. Given the customer organization, users, groups, and tools, identify

which user groups require access to what functions, and the type of authentication required so that the number of user access requirements is identified.

SUBTASK(S): 1.3.1. Review customer organization and groups.


1.3.2. Identify operators. 1.3.3. Identify administrators. 1.3.4. Identify super users. 1.3.5. Verify access is required with groups 1.3.6. Determine integrations to customer’s existing LDAP applications. 1.3.7. Determine the security requirements (firewall, communication ports, ACL). 1.4. Given the IBM Tivoli Netcool architecture, event volume, and hardware

and software supported, calculate event volume and perform sizing calculation so that the required amount of hardware, memory and disk space per hardware is identified or defined.

SUBTASK(S): 1.4.1. Review the preferred hardware requirements with respect to space and

memory. 1.4.2. Review the hardware requirements with respect to probes. 1.4.3. Determine the number of events that will occur on each probe type per

hour. 1.4.4. Determine the total number of events that will be stored on the

ObjectServer per hour. 1.4.5. Determine if network bandwidth will support event throughput. 1.4.6. Determine and verify OS patch requirements based on chosen platform. 1.4.7. Determine integrated products version to ensure compatibility 1.4.8. Determine security and access requirements. 1.4.9. Produce a detailed list of hardware, software, and network requirements. 1.4.10. Review the event source and integration strategy. 1.4.11. Review the number and type of probes proposed. 1.4.12. Review the number and type of gateway proposed. 1.4.13. Determine if a proxy server is required or proposed. 1.4.14. Determine if any Display or Desktop ObjectServer proposed. 1.4.15. Determine failover or High Availability requirements for all components of

the implementation (ObjectServer, gateways, probes, Web GUI. ). 1.4.16. Determine the MIBs required for SNMP related event management, and

probe rules generation and distribution method. 1.4.17. Determine the rules update process and the need for rules file caching). 1.5. Given the implementation requirements ,design the IBM Tivoli

Netcool/OMNIbus (Netcool/OMNIbus) architecture document so that Netcool/OMNIbus architecture satisfies the customer requirements.

SUBTASK(S): 1.5.1. Verify all software needed. 1.5.2. Verify hardware components. 1.5.3. Determine which software will run on each hardware component. 1.5.4. Determine product integration probes and gateways. 1.5.5. Determine network infrastructure requirements.


1.5.6. Determine network connectivity between affected servers. 1.5.7. Determine user access and authentication requirements for servers given

the existing security policies. 1.5.8. Determine the type of failover and high-availability of each component. 1.5.9. Define components, locations, and network connectivity. 1.5.10. Determine naming conventions. 1.5.11. Determine directory for install, and install mode. 1.5.12. Review customer compliance requirements. 1.5.13. Determine event group, event relationship, group filter, and mobile event

dashboard requirements. 1.5.14. Determine upgrade strategy, and coexistence of existing implementation

(pre V7.4 ObjectServers, probes, and Web GUI servers) 1.5.15. OUTPUTS: OMNIbus architecture that satisfies the customer

requirements 1.6. Given Netcool/OMNIbus architecture document, network requirements,

communication protocols, and customer security requirements, review and document the information so that the security requirements are documented.

SUBTASK(S): 1.6.1. Review network requirements and determine compatible security types. 1.6.2. Review customer security requirements and determine suitable security

type. 1.6.3. Determine the Netcool/OMNIbus java meets the customer's security

requirement. 1.6.4. Document the security requirements. 1.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.

SUBTASK(S): 1.7.1. Review the product documentation. 1.7.2. Determine space available on customer hardware. 1.7.3. Identify disk requirements for components to be installed. 1.7.4. Ensure disk space is adequate on the systems. 1.7.5. Determine default location of installation and install type. 1.7.6. Determine authentication methods. 1.7.7. Determine user account required to install/upgrade. 1.7.8. Determine access or privileges required to install/upgrade. 1.7.9. Determine directories that need write and execute access permissions. 1.7.10. Verify the platform is supported using product documentation, and

prerequisite checking tool when appropriate. 1.7.11. Obtain the installation package appropriate for the hardware platform.


1.8. Given the availability of prerequisite scanner utility, verify the

prerequisites on target installation servers so that the prerequisites have been identified.

1.8.1. Download the prerequisite Scanner from Fix Central for Unix or Windows. 1.8.2. Determine the product codes for the software components. 1.8.3. Determine the access permission to system. 1.8.4. Run the prerequisite scanner. 1.8.5. Review the prerequisite scanner report to verify all prerequisites are met.


Section 2 - Installation

2.1. Given the disk space requirements, privileged ID and operating system dependencies, install ObjectServer so that the ObjectServer is installed and running.

SUBTASK(S): 2.1.1. Determine Root or Non-Root User ID installation. 2.1.2. Determine installation location (destination folder) 2.1.3. Verify User ID has write privilege to installation location and temp directory. 2.1.4. Verify Disk space requirements (1 GB Disk / 250 Temp / 300 Memory). 2.1.5. Verify operating system dependencies / libraries. 2.1.6. Verify Existing Deployment Engine associated to Installation User ID. 2.1.7. Determine mode of installation. 2.1.8. Run installation script. 2.1.9. Input installation location / destination folder. 2.1.10. Choose install set (typical or customize). 2.1.11. Select installation product features or components. 2.1.12. Upgrade / migrate from older version. 2.1.13. Verify Pre-installation summary. 2.1.14. Verify installation message and log file. 2.1.15. Determine what type of ObjectServer (Display, desktop, dual-write,

primary) and use appropriate command line option to start ObjectServer. 2.1.16. Create ObjectServer. 2.1.17. Configure omni.dat/sql.inifile. 2.1.18. Generate interfaces file. 2.1.19. Verify by connecting to the ObjectServer by using SQL command. 2.2. Given the customer environment and solution architecture,

install/upgrade the required probes so that the probes and gateways are available.

SUBTASK(S): Review the customer’s environment, Solution architecture and detailed requirements. 2.2.1. Determine the event source for probe. 2.2.2. Determine the configuration required on the network device for probes and

gateway. 2.2.3. Determine the existence of relevant old probe’s and gateway’s files in

case of an upgrade. 2.2.4. Determine the changes required in ObjectServer’s DB schema to enable

the successful working of probe or gateway. 2.2.5. Determine any third party dependency for the working of probes and

gateway (ex . for odbc gateway there is a need of a DB in operational state ).

2.2.6. Determine hardware and OS systems.


2.2.7. Determine the security/network requirements for communication of probes and Gateways.

2.2.8. Verify User ID has write privilege to installation location. 2.2.9. If there is an existing Deployment Engine, verify User ID is the same user

who installed Deployment Engine. 2.2.10. Back up Deployment Engine database. 2.2.11. Run the installation. 2.2.12. Verify probes and gateways are installed. 2.2.13. Configure omni.dat/sql.inifile. 2.2.14. Choose the appropriate port for gateway. 2.2.15. Generate interfaces file. 2.2.16. Verify connectivity to ObjectServer. 2.2.17. Configure probe or gateway properties file. 2.2.18. Use appropriate command line option to start probe or gateway. 2.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.

SUBTASK(S): 2.3.1. Determine the appropriate method for migration (upgrade.sh or

nco_osreports). 2.3.2. Determine location and verify access permission to source ObjectServer. 2.3.3. Obtain access to systems and servers. 2.3.4. Log in to IBM Tivoli Netcool/OMNIbus (Netcool/OMNIbus) environment. 2.3.5. Execute migration commands. 2.3.6. Verify ObjectServer data. 2.4. Given the IBM Tivoli Integrated Portal 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.

SUBTASK(S): 2.4.1. Determine the version of previous Webtop or Web GUI. 2.4.2. Determine the appropriate method of migration depending on version of

previous Webtop or Web GUI. 2.4.3. Verify Filter, tool and other data. 2.5. Given that the ObjectServer is installed, determine and configure the

appropriate settings for properties files so that the properties file for ObjectServer is configured.

SUBTASK(S): 2.5.1. Review the user access. 2.5.2. Determine which software component is installed on the given system.


2.5.3. Gather the required information about the software component installed from the documentation .

2.5.4. Verify if the required properties file is available. 2.5.5. Determine encryption requirements and make the appropriate changes to

the properties files. 2.5.6. Determine if it is the primary or backup ObjectServer and set the

properties file. 2.5.7. Determine other requirements and set properties file appropriately. 2.5.8. Restart ObjectServer. 2.6. Given the disk space, privileged ID, operating system dependencies

and type of Display ObjectServer, install display ObjectServer so that the display ObjectServer is up and running.

SUBTASK(S): 2.6.1. Verify ID has privileges to install application. 2.6.2. Verify ID has write permissions to NCHOME directory 2.6.3. Verify Disk space requirements 2.6.4. Verify Operating System Dependencies. 2.6.5. Verify compatibility with previous versions. 2.6.6. Ensure omni.dat/sql.inior sql.ini file is configured 2.6.7. Generate interfaces file 2.6.8. Determine what type of Display ObjectServer (desktop, dual-write, primary)

and use appropriate command line option and SQL customization to create ObjectServer

2.6.9. Run the initialize command 2.6.10. Start the ObjectServer 2.6.11. Verify by connecting to the ObjectServer using SQL command 2.7. Given the supported Java versions and compatibility with previous

Netcool/OMNIbus versions, initiate installation of Admin client so that the Admin client is installed and running.

SUBTASK(S): 2.7.1. Verify if Admin GUI can be upgraded from the current version. 2.7.2. Verify ID has appropriate privileges to install Admin client. 2.7.3. Determine the network/port communication with the ObjectServer(s) and

Process agent(s). 2.7.4. Start the installation. 2.7.5. Select/Unselect components to install the Admin client. 2.7.6. Set up omni.dat/sql.ini with ObjectServer(s) and Process agent(s) host

names and listening ports. 2.7.7. Verify Installation by starting Admin client and connecting to

ObjectServer(s) and Process agent(s).


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

SUBTASK(S): 2.8.1. For upgrade from older versions, verify compatibility with previous

versions. 2.8.2. Determine appropriate steps based on previous version of Webtop/Web

GUI. 2.8.3. Verify ID has privileges to install application. 2.8.4. Verify ID has write permissions to NCHOME directory 2.8.5. Verify Disk space requirements 2.8.6. Verify operating system dependencies. 2.8.7. Determine mode of installation. 2.8.8. Perform export/import procedure for older versions. 2.8.9. Install the TIP feature pack to upgrade TIP to 2.2 if previous version is 2.1

and in place upgrade path is chosen. 2.8.10. Run installation command. 2.8.11. Enter ObjectServer Data source name. 2.8.12. Verify installation logs. 2.8.13. For upgrades, perform import procedure of exported files after installation.


Section 3 - Configuration

3.1. Given the privileged ID with ObjectServers and gateway installed, configure ObjectServer gateways so that the gateways are configured between two ObjectServers.

SUBTASK(S) for configuring gateway: 3.1.1. Identify type of gateway to be configured (uni-directional or bi-directional). 3.1.2. View the properties file. 3.1.3. Edit gateway properties file. 3.1.4. Specify name of ObjectServer which the gateway will read from. 3.1.5. Specify name of ObjectServer which the gateway will write to. 3.1.6. Specify location of map definition file. 3.1.7. Set values in mapping file. 3.1.8. Specify gateway reader properties. 3.1.9. Specify table replication definition file. 3.1.10. Perform performance tuning parameters. 3.1.11. Filter out events that will NOT be forwarded to the other ObjectServer. 3.1.12. Configure appropriate settings based on requirements. 3.1.13. Set secure connections to the ObjectServer. 3.1.14. Stop/Start gateway. 3.1.15. Verify synchronized events. 3.2. Given that IBM Tivoli Netcool/OMNIbus (Netcool/OMNIbus) is installed,

Netcool architecture document, modify and verify the configuration of locale, environment variable, gateway, and ObjectServer so the Process agent is managing the ObjectServer and gateway as per the Netcool architecture document.

SUBTASK(S): 3.2.1. Determine the environment variables to be set. 3.2.2. Verify the super user access is available. 3.2.3. Verify if user has permission to write into user profile file. 3.2.4. Verify if the SSL or FIPS needs to be implemented from the Netcool

Architecture document. 3.2.5. Set the required properties in ObjectServer properties file, omni.dat/sql.ini

file and interface file with respect to Netcool architecture. 3.2.6. Set the required properties, map and definition files need to be modified in

gateway with respect to Netcool architecture. 3.2.7. Determine and configure appropriate settings on the properties file. 3.2.8. Modify the required properties in the gateway in accordance with the type

of integration respect to ObjectServer or third party. 3.2.9. Modify the omni.dat/sql.ini file and interface file to set the SSL

communication with object sever (if SSL is a requirement). 3.2.10. Modify the required the properties file to enable the FIPS security for SSL

connection (if FIPS/SSL is requirement).


3.2.11. Modify the Process agent config file as required to start ObjectServer and gateway.

3.2.12. Execute the proper command for Process agent to use PAM authentication if using UNIX.

3.2.13. Query Process agent for status of managed components. 3.2.14. Command Process agent to stop and start managed components. 3.3. Given the Installed and configured ObjectServer, Netcool architecture

document and hardware, Identify and configure the probes requested so that the requested probes are configured as per the Netcool architecture documentation.

SUBTASK(S): 3.3.1. Download the appropriate probe software. 3.3.2. Check if the required ports/logs/api for the probes are available. 3.3.3. Check connectivity between probes to both the ObjectServer and what is

being monitored. 3.3.4. Check the prerequisites for the probe. Make sure all the requirements are

installed (dependant patches, fixpacks, third party libs, etc). 3.3.5. Make sure all the available accounts (eg. email account) and permissions

(eg. ping, mttrapd and syslog) are available for the probe to run. 3.3.6. Determine if the architecture would benefit on a dedicated probe server or

within the core Netcool/OMNIbus installation. 3.3.7. Install the requested probe(s). 3.3.8. Check if the SSL or FIPS is implemented in the ObjectServer. 3.3.9. Check the required properties to modify is in the probes. 3.3.10. Configure performance tuning parameters including flood control. 3.3.11. Modify the required properties in the probes as per the Netcool

Architecture document. 3.3.12. Modify the rules file and caching options as per the client requirements. 3.3.13. Syntax check the rules before implementing the new rules. 3.3.14. Include or modify the lookup files as required. 3.3.15. Modify the probes properties file to enable the probe to run in failover

mode. 3.3.16. Modify the properties file or the command line options to start the probe

in secure mode. 3.3.17. Configure probe to failover, peer to peer and failback. 3.3.18. Configure Store and forward. 3.3.19. Confirm the probes are sending alarms to the ObjectServer. 3.4. Given the Installed ObjectServer , installed Web GUI and Netcool

architecture document , configure the required tools so that the requested tools are available for users.

SUBTASK(S):


3.4.1. Determine what tools are required on Netcool/OMNIbus desktop and Web GUI.

3.4.2. Determine type of tools – SQL, CGI, HTTP or external command. 3.4.3. Check requirements for the tools are met (eg. java version, PERL, browser

version, fixpack, etc). 3.4.4. Identify commands with syntax required for each of the above tools. 3.4.5. Create the tools. 3.4.6. Check the availability of binaries/scripts of tools that execute them. 3.4.7. Assign appropriate privileges based on requirements. 3.4.8. Assign AllClasses OR specific classes based on requirements. 3.4.9. Assign tools to menu. 3.4.10. Refresh Native Desktop client or refresh AEL client on Web GUI. 3.4.11. Verify tools appear on the menu. 3.4.12. Verify compatibility of tools with the operating system on which the tool is

to be executed. 3.5. Given the installed and configured ObjectServer, and installed

process agent, modify and verify the required properties file and configure the Process Agent and required user for the Process Agent so that the Process Agent is configured with the required process.

SUBTASK(S): 3.5.1. Determine the environment variables to be set . 3.5.2. Verify the user access is available. 3.5.3. Verify if the SSL or encryption needs to be implemented from the Netcool

Architecture document 3.5.4. Modify the required ObjectServer properties file to assign the Process

agent user and password 3.5.5. Modify the Process Agent properties file as required based on the Netcool

Architecture document. 3.5.6. Deploy the startup script to start the process agent when the system starts. 3.5.7. Execute the Proper command to enable the PAM authentication while

starting the Process Agent if using UNIX. 3.5.8. Test the Process Agent and nco script by rebooting the system. 3.6. Given the Netcool Architecture, configure the Proxy server and probes

so that the Proxy server is running with probes connected. SUBTASK(S): 3.6.1. Ensure the Proxy server is configured in the interfaces. 3.6.2. Modify Proxy server properties as required. 3.6.3. Configure the Proxy server in secure mode if required. 3.6.4. Start the Proxy server . 3.6.5. Confirm connectivity between proxy server, probes and ObjectServer. 3.6.6. Configure probes to connect in secure mode if required, 3.6.7. Start probes,


3.6.8. Verify events are flowing from probes to Proxy server to ObjectServer. 3.7. Given the Netcool architecture and installed ObjectServers and

gateways, configure the multi-tiered architecture so that the multi-tiered ObjectServers and gateways are running.

SUBTASK(S): 3.7.1. Determine how to handle Severity on deduplication. 3.7.2. Configure omni.dat/sql.ini. 3.7.3. Create Primary and Backup Aggregation ObjectServers . 3.7.4. Configure bi-directional Aggregation failover ObjectServer gateway. 3.7.5. Create Collection ObjectServers if required. 3.7.6. Configure uni-directional Collection to Aggregation routing ObjectServer

gateways 3.7.7. Create Display ObjectServers if required. 3.7.8. Configure uni-directional Aggregation to Collection routing ObjectServer

gateways if required. 3.7.9. Configure Display ObjectServers for load balancing of event list clients. 3.7.10. Customize triggers if required. 3.7.11. Set up components to run under Process agents. 3.7.12. Start gateways and ObjectServers using Process agents. 3.7.13. Review performance data to ensure events are receive.d 3.8. Given the Netcool 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.

SUBTASK(S): 3.8.1. Review customer requirements for automation. 3.8.2. Review customer processes. 3.8.3. Add ObjectServer columns/tables to store required event data. 3.8.4. Identify processes which can be automated. 3.8.5. Use process steps to write automation pseudo-code. 3.8.6. Write pseudo-code into ObjectServer triggers and procedures. 3.9. Given the Netcool architecture, authentication requirements ,and Web

GUI user processes, configure Web GUI so that the Web GUI is customized to meet requirements.

SUBTASK(S): 3.9.1. Configure SSL Connection to the ObjectServer if required. 3.9.2. Configure LDAP integration if required. 3.9.3. Configure and initialize data source files for Web GUI. 3.9.4. Configure Single Sign-On if required. 3.9.5. Configure users, user groups, user roles and group roles.


3.9.6. Configure DB2 for high availability or load-balancing of the Web GUI multiple server instances.

3.9.7. Review Web GUI user processes. 3.9.8. Identify tools required for Web GUI user processes. 3.9.9. Configure WAAPI. 3.9.10. Configure SSL for WAAPI if required. 3.10. Given Netcool/OMNIbus has been installed and configured, configure

pages and views so that pages and views are customized per the customer’s requirements.

SUBTASKS 3.10.1. Configure user permission. 3.10.2. Configure client requirements for page and view. 3.10.3. Configure the portlets to use for pages. 3.10.4. Configure the type of page. 3.10.5. Configure if wires will be utilized with the portlets. 3.10.6. Configure automatic load or startup options for page. 3.11. Given Netcool/OMNIbus has been installed and configured, use the

Administrator GUI to add an external tool so that an external tool has been configured.

SUBTASK(S): 3.11.1. Verify ID has privileges to create a tool. 3.11.2. Determine the external command to execute in the tool. 3.11.3. Determine OS compatibility with the external command. 3.11.4. Determine ID privileges to run the external tools. 3.11.5. Configure the tool.Within the Tools menu, click Add Tool.

3.11.5.1. Enter the tool name. 3.11.5.2. From the Executable tab enter the external command/script 3.11.5.3. Configure access permissions. 3.11.5.4. Specify the platform.

3.11.6. Enable the tool. 3.12. Given that the Web GUI is installed and running and administrator

permission is available, configure the user permissions so that user permissions are configured.

SUBTASK(S): 3.12.1. Verify that the user has appropriate privileges to configure users

permissions. 3.12.2. Select the Users and Groups menu. 3.12.3. Select the User Roles menu. 3.12.4. Search and select the user you want to configure its permissions. 3.12.5. Add the permissions.


3.12.6. Save. 3.13. Given ID requirements and installed and configured Netcool/OMNIbus,

configure the Accelerated Event Notification (AEN) client so that the AEN client is configured.

SUBTASK(S): 3.13.1. Verify ID has privileges to start the AEN client. 3.13.2. Start the AEN client. 3.13.3. If starting the AEN for the first time, right-click the AEN icon and select

Properties. 3.13.4. Configure the Notification settings:. 3.13.5. Configure the Launch in Context Settings. 3.13.6. Configure the Browser settings. 3.13.7. Configure Message and Channels tabs, as required. 3.13.8. Select OK. 3.13.9. Given that the AEN Client has previously been configured, log on to AEN

client by right-clicking icon and select Sign In. 3.13.10. Input a valid ObjectServer user details and select Log In . 3.14. Given installed and configured Netcool/OMNIbus, configure the

HTTP/OSLC interface so that the HTTP/OSLC interface is configured. SUBTASK(S): 3.14.1. Determine what interface is to be used. 3.14.2. Edit the ObjectServer properties file. 3.14.3. Enable the interface. 3.14.4. Configure the port. 3.14.5. Configure SSL if required. 3.14.6. Configure filesharing if required. 3.14.7. Restart ObjectServer. 3.14.8. Verify that the interface is working. 3.15. Given Netcool/OMNIbus has been installed and configured, configure

HTTP and OSLC so that you can communicate with the probes using HTTP and OSLC.

SUBTASK(S): 3.15.1. Determine if HTTP or HTTPS will be used. 3.15.2. Determine the property settings for NHTTPD. 3.15.3. Configure authentication. 3.15.4. Configure SSL connections if required. 3.15.5. Determine nco_http commands required. 3.15.6. Determine nco_probe reload rules options to use. 3.15.7. Determine nco_set probe prop options to use. 3.15.8. Determine nco_probe event factory commands to use for testing.


3.15.9. Determine possible URI’s to use to communicate with remote probes. 3.16. Given the Installed and configured ObjectServer, Netcool architecture

document, and hardware, Identify and configure the probes for remote communication so that remote configuration of probes is complete.(this is what the online docs states).

SUBTASK(S): 3.16.1. Determine probes to install. 3.16.2. Determine if HTTP or HTTPS protocol to be used for probe

communication. 3.16.3. Identify the communication ports used for bi-directional probe

communication and enable the ports to communicate thru the firewalls (if any).

3.16.4. Set up the omni.dat/sql.ini file for communications with ObjectServer . 3.16.5. Add additional HTTP properties to the probe props file. 3.16.6. Enabled the basic HTTP properties for the probe to receive HTTP

commands. 3.16.7. Start the probe with the correct props file. 3.16.8. Run HTTP utility to query the probe. 3.16.9. Run HTTP utility to change properties. 3.16.10. Run HTTP utilty to reload rules file. 3.16.11. Run HTTP utilty to send test event to ObjectServer. 3.16.12. Verify via the probe debug log, probe outputs and ObjectServer that the

above HTTP commands work.


Section 4 - Administration

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

SUBTASK(S): 4.1.1. Connect to an ObjectServer . 4.1.2. Connect to a Process Agent. 4.1.3. Create and restore backups. (nco.confpack and nco.osreport enable the

autobackup trigger). 4.1.4. Create a new ObjectServers. 4.1.5. Generate the interfaces file. 4.1.6. Create/delete triggers. 4.1.7. Create/delete signals. 4.1.8. Create/delete procedures. 4.1.9. Create indexes. 4.1.10. Monitor probe connections. 4.1.11. Create user and assign roles. 4.1.12. Modify ObjectServer properties. 4.2. Given the customer environment, solution architecture and detailed

requirements, administer/configure the Web GUI so that the Web GUI is successfully administered.

SUBTASK(S): 4.2.1. Review the customer’s environment, Solution architecture and detailed

requirements. 4.2.2. Determine the security/Network requirements for communication of Web

GUI with ObjectServer and LDAP’s (if any ). 4.2.3. Add and remove users, groups and roles. 4.2.4. Determine the users and user’s privilege level in Web GUI for different

pages , Views, Portlets , event filters, events menu and events tools. 4.2.5. Determine the requirement of custom pages/portlets to suffice the

customer requirement. 4.2.6. Determine the failover architecture of the Web GUI to ensure the changes

are. propagated to each server in the failover cluster. 4.3. Given the customer environment, solution architecture and detailed

requirements, create Backups of Web GUI so that Web GUI has successful backups.

SUBTASK(S): 4.3.1. Review the customer’s environment, solution architecture and detailed

requirements. 4.3.2. Determine the failover Architecture of the Web GUI to ensure the backup

should be done for Active servers.


4.3.3. Back up Web GUI. 4.3.4. Back up IBM Tivoli Integrated Portal. 4.3.5. Back up deployment engine. 4.4. Given the customer environment, solution architecture, and detailed

requirements, deploy startup scripts so that startup scripts are successfully deployed.


requirements. 4.4.2. Determine the variable that needs to used while creating startup scripts. 4.4.3. Determine the init level at which scripts need to be deployed. 4.4.4. Deploy the startup scripts. 4.5. Given the customer environment, Solution architecture and detailed

requirements, create filters, views and maps in Web GUI as per the user’s requirement so that filters, views and maps are successfully created.


requirements. 4.5.2. Determine requirements for filters, views and maps. 4.5.3. Determine the user permission and access to filters, views and maps. 4.5.4. Create filters, views, and maps based on requirements.


Section 5 - Performance Tuning and Problem Determination

5.1. Given that there are multiple Log Files Management commands, manage log filse so that log files for the ObjectServer, Probes, and Gateways are configured properly.

SUBTASK(S): 5.1.1. Identify the location of the ObjectServer, Probe and Gateway log files. 5.1.2. Review and configure the settings required to increase the log level to

Debug for the ObjectServer, probes ,and gateways. 5.1.3. Review and set log rotation requirements. 5.1.4. Review and set the properties files for probes and gateways related to

logging. 5.1.5. Review the ObjectServer for checkpointing. 5.1.6. Review and configure audit files for the ObjectServer. 5.1.7. Review and configure debugging.for triggers 5.1.8. Review and set the appropriate Message Level for the ObjectServer,

Probes and Gateways. 5.2. Given that a set of probe rules has been created, check the syntax so

that the probe syntax is verified. SUBTASK(S): 5.2.1. Create or Modify a Rules file for a probe. 5.2.2. Run the nco_p_syntax against the rules file. 5.2.3. Check the output of the nco_p_syntax command. 5.2.4. Review and correct probe rules syntax errors. 5.2.5. Rename the probe rules file to the code that will be run from the probe

properties file. 5.2.6. Verify the probe rules file syntax. 5.2.7. Determine the correct rules file is being read by the probe. 5.3. Given that the ObjectServer is configured and running, verify the

communications settings for the ObjectServer so that communication between the components is identified and verified.

SUBTASK(S): 5.3.1. Review secure host settings for the ObjectServer. 5.3.2. Review the server interfaces on ObjectServer. 5.3.3. Review the server interfaces on probes. 5.3.4. Review the server interfaces on gateways. 5.3.5. Review data source settings on the Web GUI. 5.3.6. Modify the communications settings. 5.3.7. Distribute the modified omni.dat/sql.ini interfaces.<platform> file. 5.3.8. Restart the ObjectServer and ancillary components to ensure

communications settings are set properly.


5.3.9. Test the communication between the components with nco_ping or nco_xigen in UNIX.

5.3.10. Test the communication between the components with Server Editor in Windows.

5.3.11. Verify log files to ensure correct communication between the components.

5.4. Given that a Probe has been installed, check the properties file so that

the properties files are configured properly. SUBTASK(S): 5.4.1. Review and set appropriate settings for the Probe properties file. 5.4.2. Stop and start the probe. 5.4.3. Ensure that the probe is running. 5.4.4. Run the Configuration Analyzer. 5.4.5. Verify the output of Configuration Analyzer. 5.4.6. Verify log file to ensure correct operation of probe. 5.5. Given Tivoli Netcool OMNIbus (Netcool/OMNIbus) has been installed,

configure and verify the Netcool/OMNIbus environment variables so that the environment variables have been configured.

SUBTASK(S): 5.5.1. Edit system user profile. 5.5.2. Define Netcool environment variables. 5.5.3. Source the profile in UNIX. 5.5.4. Run the “env” command in UNIX or check the System Properties in

Windows. 5.5.5. Verify Netcool environment variables. 5.6. Given Netcool/OMNIbus has been installed and configured, customize

Netcool/OMNIbus ObjectServer configuration such that the ObjectServer performance is optimal.

SUBTASK(S): 5.6.1. Check frequency of triggers. 5.6.2. Check execution scope of triggers: once only, for each row. 5.6.3. Check SQL used in trigger for performance. 5.6.4. Check whether 'update via' is being used. 5.6.5. Check desktop filters. 5.6.6. Check other appropriate settings (e.g. Granularity). 5.6.7. Check profile and trigger statistics logs. 5.6.8. Check number of connections allowed. 5.6.9. Define table indexes for better performance. 5.6.10. Check the number of events in the ObjectServer. 5.6.11. Check ObjectServer footprint in ObjectServer debug log.


5.6.12. Check system resources used by ObjectServer. 5.7. Given Netcool/OMNIbus Web GUI has been installed and configured,

log in to Web GUI so that the HTTP access to Netcool/OMNIbus Web GUI verified.

SUBTASK(S): 5.7.1. Verify host name and port. 5.7.2. Log in to Web GUI (TIP).


Next Steps

1. Take the IBM Tivoli Netcool/OMNIBUS V7.4 Implementation assessment test using the promotion code csistudy for $10 ($20 USD savings).

2. If you pass the assessment exam, visit pearsonvue.com/ibm to schedule

your testing sessions. Use the promotion code tivguide to receive 20% off.

3. If you failed the assessment exam, review how you did by section. Focus attention on the sections where you need improvement. Keep in mind that you can take the assessment exam as many times as you would like ($10 per exam), however, you will still receive the same questions only in a different order.

http://www-03.ibm.com/certify/tests/samC2010-657.shtml

Cloud & Smarter Infrastructure Professional Certification...

Documents

Transcript of Cloud & Smarter Infrastructure Professional Certification...