Cloud & Smarter Infrastructure Professional Certification Program

Study Guide Series

Exam C9560- 524 - IBM Tivoli Netcool/Impact V7.1 Implementation

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

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

Detailed Exam Objectives ................................................................................... 7

Section 1 - Planning ............................................................................................................ 7

Section 2 - Installation ..................................................................................................... 10

Section 3 - Configuration ................................................................................................ 12

Section 4 - Development ................................................................................................. 16

Section 5 - Administration .............................................................................................. 19

Section 6 - Performance Tuning and Problem Determination .............................. 21

Next Steps .............................................................................................................23

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 stakeholder requirements, document the functional steps so that an IBMNetcool/Impact solution is designed.

1.2

Given the functional requirements determined by the stakeholders and the current state system architecture (if one exists), gather technical deployment requirements from the stakeholders so that a full technical architecture is documented and approved.

1.3 Given Netcool/Impact functional requirements, and architectual requirements, determine Netcool/Impact policy design standards so that the policies can be written.

1.4 Given the stakeholders for Impact, communicate and coordinate their involvement such that Impact functionality can be best utilized.

1.5 Given that functional requirements have been identified, and external resources have been established, determine the users, administrators and authentication specifics so that users can be configured within Netcool/Impact.

1.6 Given the functional requirements access the application dependencies to fulfill functional requirements and document them so that applications can be integrated.

Section 2 - Installation

2.1 Given the prerequisite components, verify their setup so that the Impact Server is ready for installation.

2.2

Given available ports, additional components, password for impactadmin user, installation user, resiliency requirements and Objectserver location, identify all of the installation parameters so that installation parameters are identified in preparation for installation of Impact.

2.3 Given the approved technical architecture and verified installation prerequisites; install, test and document the Impact solution so that it is ready for use.

2.4

Given the architecture resiliency requirements, install two Impact server cluster members, configure the necessary failover points, and set up self monitoring of Impact so that all components meet the requirements for resiliency.

2.5 Given the various Impact component scripts, configure application startup so that all necessary components are running and will startup automatically upon physical server restart.

Section 3 - Configuration

3.1 Given appropriate data access and the documented system architecture, configure and test Impact Data Sources such that defined data sources are operational.

3.2 Given a properly configured and accessible data source and access to the Impact GUI create data type and data source relationships so that a data model can be built.

3.3

Given that Netcool Impact has been properly installed, the name of the Netcool Impact Server is known, a valid username and password is known (optionally encrypted), a policy to execute is known, and optionally a @Identifier and @Serial if policy contains a call to the Returnevent function, configure command-line activiation of policies requirements so that policies may be executed from the command-line.

3.4 Given the anticipated event volumes and multi-policy processing, set up event processor so that processing of events is optimized with minimal conflicts.

3.5

Given that Access to Data Sources has been configured, Data Types have been created and Policies written, identify Netcool Impact Service configuration requirements so that Event Readers can be created within Netcool Impact.

3.6 Given that Services are available, configure Services such that Impact services are ready to record log messages to file.

3.7

Given a working installation of JazzSM/DASH (Jazz for Service Management/Dashboard Application Service Hub) and a working installation of Netcool/Impact V7.1 add connections to Impact from DASH so that DASH is allowed to access Impact to gain information from policies.

3.8 Given a user registry is required, configure the user registry so that all roles, groups and users are defined.

3.9 Given data from various sources and the stakeholder's functional requirements, define data providers so that an interface is created that allows DASH to consume the required data.

3.10 Given the Impact Documentation, describe the DASH concept so that the DASH concept is understood.

3.11

Given that DASH will be used, JazzSM with DASH has been installed, the data sources and data type relationships have been established, policies are written, and that the connection between Netcool/Impact and DASH have been established, add widgets to the DASH environment so that DASH widgets are connected to and populated by Netcool/Impact UI Data Providers.

Section 4 - Development

4.1 Given functional requirements, an architectural design, and policy objectives, draft a pseudo-code so that a document fully describes the critical elements of a policy defined in the functional requirements is created.

4.2

Given that Netcool Impact planning requirements have been met, proper Installation and Configuration of the Netcool Impact server has occured, and a Netcool ObjectServer is running and accessable with administrative access, determine and create Netcool ObjectServer fields to meet functional requirements so that addtional ObjectServer fields are created.

4.3 Given pseudo-code or policy flow statements with properly configured data sources and data types, develop and unit test Impact policies such that functional requirements are met.

4.4 Given policies, type of service details, and filter conditions, configure Netcool/Impact services so that policies are automatically executed.

4.5 Given that an Operator View is required, create and configure an Operator View so that data can be visualized in Netcool/Impact.

4.6 Given the system requirements and a functioning Impact system with deployed policies and services, test with relevant stakeholders so that policy output is verified.

4.7

Given the complete project requirements, identify the appropriate parties and available mechanisms to formulate and document a policy exception plan so that a document that defines the project specific policy exception plan is created.

Section 5 - Administration

5.1

Given that Netcool Impact planning requirements have been met, proper Installation and Configuration of the Netcool Impact server has occurred, is running and accessible, and Project Members have been determined, configure Netcool Impact Projects so that a subset of elements stored in the global repository is grouped together into a project.

5.2 Given detailed functional requirements related to user access and roles, configure users and roles so that users have appropriate access to Impact.

5.3 Given that Impact Server A has been configured, export data from Impact Server A such that the data can be Imported into Impact Server B.

Section 6 - Performance Tuning and Problem Determination

6.1 Given an installed Impact system based on technical architecture specifications, review the deployment documentation and check various outputs of systems so that a properly installed Impact system is verified.

6.2

Given an operating Impact server and performance requirements, analyze reports, identify potential data source and policy performance issues, and create recommendations for those issues so that a document describing data source and policy performance issues is created recommending appropriate actions to mitigate the issues.

6.3 Given that a functional Netcool Impact Installation is running, Logging Standards and Netcool Impact Services are configured, utilize Netcool/Impact and system tools so that performance issues may be assessed.

6.4 Given incorrect output of a policy but syntax shows no errors, test system and review logs so that problems and issues are isolated within the system.

6.5

Given that Impact Subversion is generating error messages in the log files, and the user has permissions to troubleshoot using the nci_version_control script identify and troubleshoot Impact Subversion so that SVN no longer generates error messages.

Detailed Exam Objectives

Section 1 - Planning

1.1. Given the stakeholder requirements, document the functional steps so that an IBMNetcool/Impact solution is designed.

SUBTASK(S): 1.1.1. Analyze stakeholder high level requirements. 1.1.2. Determine method(s) of achieving customer requirements. 1.1.3. Identify local and remote data to process. 1.1.4. Determine components necessary to achieve requirements. 1.1.5. Architect solution with necessary components. 1.1.6. Design policies to fulfill functional requirements. 1.2. Given the functional requirements determined by the stakeholders and the

current state system architecture (if one exists), gather technical deployment requirements from the stakeholders so that a full technical architecture is documented and approved.

SUBTASK(S): 1.2.1. Determine Hardware and Operating System Restrictions (what‟s available or

desired). 1.2.2. Gather current Netcool component deployment architecture (ObjectServers,

Name Server, unique deployment features). 1.2.3. Gather and determine Event “Source” Requirements (Event readers and

listeners). 1.2.4. Determine if the data source is a UI data provider if DASH is used. 1.2.5. Determine if DASH will be used. 1.2.6. Determine sources of data. 1.2.7. Determine Availability Requirements - clustering and failover requirements. 1.2.8. Determine Release Management infrastructure/requirements (dev, test,

production or other). 1.2.9. Determine other external integration points (APIs, notification, external systems,

etc.). 1.2.10. Determine Connectivity requirements (firewall paths, network access, security

restrictions and requirements, etc.). 1.2.11. Create Technical Architecture Documentation. 1.2.12. Present and obtain architecture signoff from relevant stakeholders. 1.3. Given Netcool/Impact functional requirements, and architectual

requirements, determine Netcool/Impact policy design standards so that the policies can be written.

SUBTASK(S): 1.3.1. Determine Policy which type of policy will be created: IPL, javascript, wizard(built-

in), operator view.

1.3.2. Determine Policy Naming Convention. 1.3.3. Determine Data Models: Data Sources, Data Types, Data Items, Links, Event

Sources. 1.3.4. Determine Policy Types: Event Enrichment, X events in Y time, Event Notification,

Event Gateway, Web Service, Operator View, UI Data Provider. 1.3.5. Determine Services: Event Readers/Listeners, Policy Activators. 1.3.6. Determine External Requirements: Data Sources, ObjectServer fields, rules files,

scripts. 1.3.7. Determine Pre-Conditions: suppression states, triggering events, timing. 1.3.8. Determine Post-Conditions: suppression states, synthetic/meta events creation,

event fields, notifications. 1.3.9. Determine Logging Standards: Required, Info, Debug. 1.3.10. Create pseudo code which depicts logical policy flow. 1.4. Given the stakeholders for Impact, communicate and coordinate their

involvement such that Impact functionality can be best utilized. SUBTASK(S): 1.4.1. Identify from data users which OMNIbus events are incomplete. 1.4.2. Identify which external data owners have information that can be used to

enhance OMNIbus events. 1.4.3. Request external data owners to advise on data structures (eg database names,

tables, fields etc). 1.4.4. Request external data owners create user accounts to permit Impact to access

the data. 1.4.5. Determine external data access details to enable creation of data sources (ports,

firewalls, ACLs). 1.4.6. Determine which events need enriching and develop and implement appropriate

policies. 1.4.7. Confirm with data users that there are no ill effects of the integration. 1.5. Given that functional requirements have been identified, and external

resources have been established, determine the users, administrators and authentication specifics so that users can be configured within Netcool/Impact.

SUBTASK(S): 1.5.1. Determine sources of authentication (file-based, omnibus, ldap). 1.5.2. Determine Native or External authentication. 1.5.3. Determine Group Membership (administration, operations, sales, marketing,

management,etc). 1.5.4. Determine Roles (administrator, operator, user,etc). 1.5.5. Determine SSL requirements.

1.6. Given the functional requirements access the application dependencies to fulfill functional requirements and document them so that applications can be integrated.

SUBTASK(S): 1.6.1. Review detailed functional requirements. 1.6.2. Assess application infrastructure. 1.6.3. Determine Netcool application dependencies: ITNM for IP, TBSM, OMNIbus,

OMNIbusObjectServer fields, database access, data sources, data types, data provider if DASH is used.

1.6.4. Determine other application dependencies, for example: SQL database, SNMP, UI Data Provider, LDAP, Java™ Message Service (JMS).

1.6.5. Document dependencies.

Section 2 - Installation

2.1. Given the prerequisite components, verify their setup so that the Impact Server is ready for installation.

SUBTASKS: 2.1.1. Use IBM prerequisite scanner. 2.1.2. Verify installation of Netcool Name Server. 2.1.3. Verify installation of a Netcool Omnibus Object Server instance. 2.1.4. Verify Netcool Impact Server system requirements.

2.1.4.1. Verify file permissions for source and destination directories where Impact will be installed.

2.1.4.2. Verify all necessary operating system patches and packages are installed on Impact Server.

2.1.4.3. Verify hard disk space requirements on Impact Server. 2.1.5. Verify availability of console emulation availability when remotely installing

Impact on a Windows Server. 2.2. Given available ports, additional components, password for impactadmin

user, installation user, resiliency requirements and Objectserver location, identify all of the installation parameters so that installation parameters are identified in preparation for installation of Impact.

SUBTASK(S): 2.2.1. Identify if extensions are required and licensed (NOI IBM Connections, NOI

Seasonality) 2.2.2. Determine what components to install (Impact GUI, Impact Server) 2.2.3. Determine which user registry to use 2.2.4. Determine password for impactadmin user so that it is consistent across all

components. 2.2.5. Identify configuration settings for default ObjectServer 2.2.6. Determine naming conventions for Impact servers and clusters. 2.2.7. Determine if there are any potential conflicts with default ports to be used (using

netstat, and with reference to Impact documentation. 2.2.8. Determine which version control is to be used. 2.3. Given the approved technical architecture and verified installation

prerequisites; install, test and document the Impact solution so that it is ready for use.

SUBTASK(S): 2.3.1. Download Impact Server Binaries. 2.3.2. Uncompress Impact Server Binaries. 2.3.3. Review Installation Parameters. 2.3.4. Determine Gui, console, or silent install. 2.3.5. Execute Impact Installer. 2.3.6. Review installation and installation logs for issues.

2.3.7. Start Impact Server. 2.3.8. Test Availability of impact server. 2.4. Given the architecture resiliency requirements, install two Impact server

cluster members, configure the necessary failover points, and set up self monitoring of Impact so that all components meet the requirements for resiliency.

SUBTASK(S): 2.4.1. Review the requirements and determine appropriate resilient architecture. 2.4.2. Install the primary Impact server in the cluster. 2.4.3. Install the secondary Impact server cluster member. 2.4.4. Set the Server clustering properties. 2.4.5. Configure a data source with failover (Objectserver). 2.4.6. Configure event processor if required. 2.4.7. Set up Impact self-monitoring. 2.4.8. Recommend any actions to be taken on self-monitoring events. 2.5. Given the various Impact component scripts, configure application startup

so that all necessary components are running and will startup automatically upon physical server restart.

SUBTASKS: 2.5.1. Select the Impact Services to automatically start up (i.e. event readers, policy

activators, email readers, etc.). 2.5.2. Start Impact GUI server. 2.5.3. Start Impact server. 2.5.4. Start secondary Impact Server (if clustering is deployed). 2.5.5. Start JRExec process on all Impact Servers. 2.5.6. Deploy initscripts or configure services to auto-start all processes upon physical

server startup.

Section 3 - Configuration

3.1. Given appropriate data access and the documented system architecture, configure and test Impact Data Sources such that defined data sources are operational.

SUBTASK(S): 3.1.1. Obtain access information from identified personnel (hostname/IP, database

name/instance, schema, login, ports,etc.). 3.1.2. Obtain drivers for datasource if appliciable. 3.1.3. Install datasource drivers in dsalib directory. 3.1.4. Obtain Web Services definition library files (WSDL) and XML schema definitions,

if applicable. 3.1.5. Configure Impact Data Sources per the documented system architecture via

Impact GUI. 3.1.6. Test connection to from Impact Data Source (where applicable). 3.1.7. Test connection to DASH (where applicable). 3.2. Given a properly configured and accessible data source and access to the

Impact GUI create data type and data source relationships so that a data model can be built.

SUBTASK(S): 3.2.1. Login to Impact gui. 3.2.2. Select the Data Model Tab. 3.2.3. Right click the Data Source and choose „New Data Type‟. 3.2.4. In the DataType window, provide a unique name for the DataType 3.2.5. Select the UI Data Provider checkbox if required. 3.2.6. Select the Base Table from the dropdown and then select „Refresh‟. 3.2.7. Select at least one field of the returned table as the key field. 3.2.8. Remove fields from the table if not required in the DataType. 3.2.9. Select an appropriate field for the Display Name. 3.2.10. Apply a filter condition to apply to the Data Source‟s Data Items, as required. 3.2.11. Apply a sort order to apply to the Data Source‟s Data Items, as required. 3.2.12. Save the configuration. 3.2.13. Confirm the Data Type‟s configuration by right clicking the data type and

selecting the „View Data Items‟. 3.3. Given that Netcool Impact has been properly installed, the name of the

Netcool Impact Server is known, a valid username and password is known (optionally encrypted), a policy to execute is known, and optionally a @Identifier and @Serial if policy contains a call to the Returnevent function, configure command-line activiation of policies requirements so that policies may be executed from the command-line.

SUBTASK(S): 3.3.1. Determine Name of Netcool Impact Server.

3.3.2. Determine Valid Username/Password combination. 3.3.3. Determine Policy Name. 3.3.4. Optionally Determine @Identifier and @Serial fields. 3.3.5. Optionally Determine encrypted password. 3.4. Given the anticipated event volumes and multi-policy processing, set up

event processor so that processing of events is optimized with minimal conflicts.

SUBTASKS: 3.4.1. Determine if event volumes warrant additional multi-threading of policy

processing. 3.4.2. Select the „Event Processor‟ Service from the „Service Status‟ Pane. 3.4.3. Enter the desired minimum & maximum number of simultaneous threads 3.4.4. Enter the desired maximum number of events per query. 3.4.5. Select whether Tuning configuration is Maintained on Restart . 3.4.6. Select whether to enable logging. 3.4.7. Select Clear Queue (where applicable). 3.4.8. Save configuration; stop and restart event processor. 3.4.9. Duplicate settings on Secondary server (where applicable). 3.5. Given that Access to Data Sources has been configured, Data Types have

been created and Policies written, identify Netcool Impact Service configuration requirements so that Event Readers can be created within Netcool Impact.

SUBTASK(S): On the services tab select the event reader to be configured 3.5.1. Input Service Name. 3.5.2. Input Data Source. 3.5.3. Set Polling Interval. 3.5.4. Select Restrict Fields. 3.5.5. Select Impact Server startup requirements. 3.5.6. Select logging and reporting requirements. 3.5.7. Input Event Mapping requirements. 3.6. Given that Services are available, configure Services such that Impact

services are ready to record log messages to file. SUBTASK(S): 3.6.1. Select the service tab. 3.6.2. For any Service where logging is an option, double-click the Service to access

the configuration window. 3.6.3. Review Service Log: write to file option and select or de-select as required and

then click the save icon.

3.6.4. For the Policy Logger service, select or de-select the following Log options, as required: 3.6.4.1. Error-handling Policy. 3.6.4.2. Highest Log Level (0-3). 3.6.4.3. All SQL statements / policy Query Diagnostics. 3.6.4.4. Parameters for Built-in Functions. 3.6.4.5. Local Variables on Exit of Custom Functions. 3.6.4.6. Full Current Context on Entry and Exit of Custom Functions. 3.6.4.7. Policy Profiling. 3.6.4.8. Service Log: Write to file

3.6.4.8.1. Append Thread Name to Log File Name. 3.6.4.8.2. Append Policy Name to Log File Name.

3.6.4.9. Collect Reports. 3.6.5. For any Service where logging has been selected, check the log files at

$NCHOME/impact/log/<servername>_<service name>.log. 3.7. Given a working installation of JazzSM/DASH (Jazz for Service

Management/Dashboard Application Service Hub) and a working installation of Netcool/Impact V7.1 add connections to Impact from DASH so that DASH is allowed to access Impact to gain information from policies.

SUBTASK(S): 3.7.1. Resolve any network access issues. 3.7.2. Navigate to the connections screen within DASH. 3.7.3. Add the hostname for the Impact server. 3.7.4. Add in username and password. 3.7.5. Confirm by accessing datasets and searching for data items configured in Impact. 3.8. Given a user registry is required, configure the user registry so that all roles,

groups and users are defined. SUBTASKS: 3.8.1. Select the type of user management and authentication. 3.8.2. Choose either the ObjectServer based user registry, or the file-based user

registry (default). 3.8.3. Edit the properties file for the registry. 3.8.4. Review and update the property values within the quotation marks. 3.8.5. Run the configuration scripts.

3.8.5.1. confAuth4LDAP and. 3.8.5.2. confAuth4OMNIbus.

3.9. Given data from various sources and the stakeholder's functional

requirements, define data providers so that an interface is created that allows DASH to consume the required data.

SUBTASK(S):

3.9.1. Check that correct components are installed. 3.9.2. Configure user authorization. 3.9.3. Assign the appropriate roles to users. 3.9.4. Determine data sources. 3.9.5. Determine data type. 3.9.6. Validate data type can send data to data provider. 3.9.7. Determine if policy is needed. 3.9.8. Create the remote connection. 3.9.9. Create the information provider. 3.9.10. Create a page and widget in the console. 3.10. Given the Impact Documentation, describe the DASH concept so that the

DASH concept is understood. SUBTASK(S): 3.10.1. DASH is a single console for administrating IBM Products and related

applications. 3.10.2. DASH is a component of Jazz for Service Management (JazzSM). 3.10.3. JazzSM is a separately installed component. 3.10.4. DASH / JazzSM is not required to run Impact. 3.10.5. DASH is UI data provider for visual display enhancements. 3.10.6. Use the Netcool/Impact UI data provider to visualize data. 3.11. Given that DASH will be used, JazzSM with DASH has been installed, the

data sources and data type relationships have been established, policies are written, and that the connection between Netcool/Impact and DASH have been established, add widgets to the DASH environment so that DASH widgets are connected to and populated by Netcool/Impact UI Data Providers.

SUBTASK(S): 3.11.1. Select widgets. 3.11.2. Drag and drop widgets into the pallet. 3.11.3. Edit the widgets. 3.11.4. Select datasets to populate the widgets. 3.11.5. Assign the appropriate fields for the dataset.

Section 4 - Development

4.1. Given functional requirements, an architectural design, and policy objectives, draft a pseudo-code so that a document fully describes the critical elements of a policy defined in the functional requirements is created.

SUBTASK(S): 4.1.1. Review the requirements. 4.1.2. Formulate a development plan for accessing appropriate data. 4.1.3. Formulate a development plan for testing the policy during development. 4.1.4. Verify access to test systems and data. 4.1.5. Define what will execute the policy. 4.1.6. Identify any relationships or interactions with other events or policies if necessary. 4.1.7. Finalize pseudo-code or flow chart. 4.2. Given that Netcool Impact planning requirements have been met, proper

Installation and Configuration of the Netcool Impact server has occured, and a Netcool ObjectServer is running and accessable with administrative access, determine and create Netcool ObjectServer fields to meet functional requirements so that addtional ObjectServer fields are created.

SUBTASK(S): 4.2.1. Determine Policy Interaction requirements. 4.2.2. Determine Event Suppression Flow requirements. 4.2.3. Determine Communication States between ObjectServer and Impact

requirements. 4.2.4. Determine Column Name and Data Type. 4.2.5. Log in to the NetcoolObjectServer Administration application. 4.2.6. Use Administration tool to create ObjectServer Columns. 4.2.7. Optionally Use SQL Interactive to create Object Server Columns. 4.3. Given pseudo-code or policy flow statements with properly configured data

sources and data types, develop and unit test Impact policies such that functional requirements are met.

SUBTASK(S): 4.3.1. Determine the functional category. 4.3.2. Select down arrow next to New Policy 4.3.3. Select policy type (IPL or JavaScript) 4.3.4. Select wizard type and follow the on-screen instructions

4.3.4.1. Event Enrichment policy 4.3.4.2. X in Y policy 4.3.4.3. Event Notification policy 4.3.4.4. Event Relocation policy 4.3.4.5. Event Correlation policy 4.3.4.6. Event Suppression policy 4.3.4.7. XML policy

4.3.4.8. Web Services policy 4.3.5. Enter Policy Name (if wizard is not used) 4.3.6. Develop Impact policies (if wizard is not used)

4.3.6.1. data types: user defined variables, arrays, context 4.3.6.2. control structures: if statements, while statements 4.3.6.3. functions: action, parser, user defined 4.3.6.4. logging: policy context and checkpoints

4.3.7. Unit test functions or functional blocks 4.4. Given policies, type of service details, and filter conditions, configure

Netcool/Impact services so that policies are automatically executed. SUBTASKS: 4.4.1. Determine which services/methods are necessary to automate policy execution. 4.4.2. Determine triggers/filters to automate policy execution within service with

consideration given to avoid conflicts between policies. 4.4.3. Obtain required data to enable Impact Service

4.4.3.1. Email Server information (if an EmailReader Service is necessary) 4.4.3.2. EventListener Service Information (if an EventListener Service is

necessary) 4.4.3.3. Database connectivity Information (if a DatabaseEventReader is

necessary) 4.4.3.4. Object Server connectivity Information (if an OMNIbusEventReader

Service is necessary) 4.4.3.5. Instant Messaging Jabber Server Information (If a JabberReader Service

is necessary) 4.4.3.6. Java Messaging Bus information (if JMSMessageListener Service is

necessary) 4.4.4. Determine frequency to execute policies 4.4.5. Configure new or existing services. 4.4.6. For Event Reader Service, create event mapping filters with special attention

given to avoid conflicts between policies, and to achieve efficient processing. 4.5. Given that an Operator View is required, create and configure an Operator

View so that data can be visualized in Netcool/Impact. SUBTASK(S): 4.5.1. Click Operator View Tab 4.5.2. Click New Operator View icon 4.5.3. In the Operator View configuration panel, provide the following information

4.5.3.1. Name 4.5.3.2. Layout Options 4.5.3.3. Action Panel 4.5.3.4. Information Groups

4.5.4. Save the Operator View by selecting the save icon.

4.5.5. Edit Operator View by double-click on the Operator View name or click the Edit icon.

4.5.6. To customize the operator view further: 4.5.6.1. Edit the Operator View definition policy 4.5.6.2. Edit the Operator View html file

4.5.7. Review the Operator View, from a web browser. 4.6. Given the system requirements and a functioning Impact system with

deployed policies and services, test with relevant stakeholders so that policy output is verified.

SUBTASK(S): 4.6.1. Review Technical Architecture and Requirements. 4.6.2. Map requirements into system test cases. 4.6.3. Create system test plan. 4.6.4. Get stakeholder approval for system test plan. 4.6.5. Set up test systems required. 4.6.6. Set up test data as required. 4.6.7. Execute system test. 4.6.8. Document test results. 4.6.9. Review test results with all stakeholders and developers for approval. 4.7. Given the complete project requirements, identify the appropriate parties

and available mechanisms to formulate and document a policy exception plan so that a document that defines the project specific policy exception plan is created.

SUBTASK(S): 4.7.1. Review the requirements. 4.7.2. Identify the available exception notification capabilities. 4.7.3. Identify the parties who must be notified. 4.7.4. Formulate and publish a plan for policy exceptions. 4.7.5. Define a standard, programmatic mechanism for handling policy exceptions. 4.7.6. Produce a document that defines how to handle exceptions within policies.

Section 5 - Administration

5.1. Given that Netcool Impact planning requirements have been met, proper Installation and Configuration of the Netcool Impact server has occurred, is running and accessible, and Project Members have been determined, configure Netcool Impact Projects so that a subset of elements stored in the global repository is grouped together into a project.

SUBTASK(S): 5.1.1. Login to Netcool Impact. 5.1.2. Determine Project Members from Global Repository based on functional

requirements. 5.1.3. Select the cluster. 5.1.4. Click the down arrow next to the existing project name to open the Projects

window. 5.1.5. Select New Project. 5.1.6. Enter name of Project and select New button. 5.1.7. Select Members from the Global Repository for Data Sources, Data Types,

Policies, Services and Operator Views associated with the project. 5.1.8. Select OK and save Project. 5.2. Given detailed functional requirements related to user access and roles,

configure users and roles so that users have appropriate access to Impact. SUBTASK(S): 5.2.1. Interview stakeholders on desired user roles. 5.2.2. Determine users requiring access to Impact. 5.2.3. Determine if LDAP or OMNIbus is used. 5.2.4. Use the mapRoles or configUsersGroup scripts in

$IMPACT_HOME/install/security. 5.2.5. Verify changes to server.xml and mapRoles.log. 5.3. Given that Impact Server A has been configured, export data from Impact

Server A such that the data can be Imported into Impact Server B SUBTASK(S): 5.3.1. Ensure that Impact Server A is running. 5.3.2. From Impact Server A‟s user interface, Global tab, select „Clear all Source

Control File Locking:‟ button. 5.3.3. Export the data from Impact Server A using nci_export and specifying a location

for the export directory. 5.3.4. Copy the export directory to a temporary location within Impact Server B‟s host

server. 5.3.5. Ensure Impact Server B is running. 5.3.6. From Impact Server B‟s user interface, Global tab, select „Clear all Source

Control File Locking:‟ button.

5.3.7. Import data into Impact Server B using nci_import and specifying the location of Impact Server A‟s exported data.

5.3.8. Check the Impact Server B‟s log file for errors. 5.3.9. Shutdown and re-start Impact Server B in order to view the imported data within

the user interface.

Section 6 - Performance Tuning and Problem Determination

6.1. Given an installed Impact system based on technical architecture specifications, review the deployment documentation and check various outputs of systems so that a properly installed Impact system is verified.

SUBTASK(S): 6.1.1. Review Technical Architecture and Requirements. 6.1.2. Review PreRequisite scanner logs for errors. 6.1.3. Review Installation Manager Logs for errors. 6.1.4. Review external systems logs for errors. 6.1.5. Review Impact server logs for errors. 6.2. Given an operating Impact server and performance requirements, analyze

reports, identify potential data source and policy performance issues, and create recommendations for those issues so that a document describing data source and policy performance issues is created recommending appropriate actions to mitigate the issues.

SUBTASK(S): 6.2.1. Enable the appropriate monitoring reports. 6.2.2. Review the monitoring reports and identify problem areas. 6.2.3. Map problem performance areas to specific policies or services. 6.2.4. Review the policy code or service configuration. 6.2.5. Identify external system performance issues. 6.2.6. Document the potential performance issues and provide to policy developers or

system administrators for review and recommendations. 6.2.7. Consolidate and publish the recommendations. 6.3. Given that a functional Netcool Impact Installation is running, Logging

Standards and Netcool Impact Services are configured, utilize Netcool/Impact and system tools so that performance issues may be assessed.

SUBTASK(S): 6.3.1. Utilize Server Logs: netcool.log, <Server>_<Service>.log,

<Server>_Policylogger.log, <Server>_Policylogger_<PolicyName>.log. 6.3.2. Utilize Operating System Tools: netstat, uptime, iostat, sar, vmstat, top. 6.3.3. Utilize Self-Monitoring Service .

6.3.3.1. Determine when to utilize. 6.3.3.2. Enable using GUI (Netcool Impact Self-Monitoring Service), or CLI

(Netcool Impact Clustered mode), <Netcool Impact Service>_selfmonitoring.props.

6.3.3.3. Analyze Monitoring Types: Memory Status, Queue Stat, Cluster status, Service Status, Data Source Status.

6.3.4. Utilize Reporting Tools. 6.3.4.1. Determine when to utilize.

6.3.4.2. Enable using Netcool Impact Policy Logger Service. 6.3.4.3. Analyze Operators Reports: Node Efficiency Report, Operator Efficiency

Report. 6.3.4.4. Analyze Netcool Impact Configuration Reports: Action Efficiency Report,

Action Error Report, Impact Profile Report, Impact ROI Report, Policy Efficiency Report, Policy Error Report.

6.4. Given incorrect output of a policy but syntax shows no errors, test system

and review logs so that problems and issues are isolated within the system. SUBTASK(S): 6.4.1. Review problem tracking list or known issues. 6.4.2. Increase logging level in the Policy Logger service. 6.4.3. Add in more logging statements. 6.4.4. Replicate the problem. 6.4.5. Review Policy logs, Event Reader logs and Server logs to determine where the

problem exists in policy. 6.4.6. Review Event Reader configuration if applicable. 6.4.7. Reduce incoming events to isolate the problem. 6.5. Given that Impact Subversion is generating error messages in the log files,

and the user has permissions to troubleshoot using the nci_version_control script identify and troubleshoot Impact Subversion so that SVN no longer generates error messages.

SUBTASK(S): 6.5.1. If Impact Subversion is preventing a policy or other object (Data Source, Data

Type) from being configured, use henci_version_control script to modify the status of the file. The script can be used for the following actions: 6.5.1.1. Check in a file 6.5.1.2. Check out a file 6.5.1.3. Add a file 6.5.1.4. Remove a file 6.5.1.5. Uncheck out a file 6.5.1.6. Rename a file

Next Steps

1. Take the IBM Tivoli Netcool/Impact V7.1 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.