000-938 Exam

IBM Tivoli Netcool Impact V4.0 Implementation

科目編號 : 000-938

科目名稱 : IBM Tivoli Netcool Impact V4.0 Implementation

題目數量：65

考試時間以分鐘為單位：75

所需的及格分數：68％

相關：IBM certifications I

Examsoon考古題價格：: $ 102.00 $ 28.50

000-938 考試是 IBM 公司的 IBM Tivoli Netcool Impact V4.0 Implementation 認證考試官方代號，IBM Tivoli Netcool Impact V4.0 Implementation 認證作為全球IT領域專家 IBM 熱門認證之一，是許多大中IT企業選擇人才標準的必備條件。

IBM 000-938 考試知識點：

Section 1: Planning

Given the stakeholder requirements, document the functional steps so that an IBM Tivoli Netcool Impact solution is designed. With emphasis on the following steps:

Analyze stakeholder high-level requirements.

Determine methods of achieving customer requirements.

Identify local and remote data to process.

Determine components necessary to achieve requirements.

Architect solution with necessary components design policies to fulfill functional requirements.

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. With emphasis on the following steps:

Determine hardware and operating system restrictions (what is available or desired).

Gather current Netcool component deployment architecture (ObjectServers, Security Manager, unique deployment features).

Gather and determine Event Source Requirements (Event readers and Event listeners).

Determine sources of data.

Determine Availability Requirements - clustering and failover requirements.

Determine Release Management infrastructure/requirements (dev, test, production or other).

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

Determine connectivity requirements (firewall paths, network access, security restrictions and requirements).

Create technical architecture documentation.

Present and obtain architecture signoff from relevant stakeholders.

Given IBM Tivoli Netcool Impact functional and architectual requirements, determine IBM Tivoli Netcool Impact policy flow so that an IBM Tivoli Netcool Impact Policy Design standard is created. With emphasis on the following steps:

Determine Policy Naming Convention.

Determine Data Models: Data Sources, Data Types, Data Items, Links, Event Sources.

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

Determine Services: Event Readers/Listeners, Email sender/Readers, Policy Activators.

Determine External Requirements: Data Sources, ObjectServer fields, rules files, scripts.

Determine Pre-Conditions: suppression states, triggering events, timing.

Determine Post-Conditions: suppression states, synthetic/meta events creation, event fields, notifications.

Determine Logging Standards: Required, Info, Debug.

Given the stakeholders for IBM Tivoli Netcool Impact, communicate and coordinate their involvement such that IBM Tivoli Netcool Impact functionality can be exploited. With emphasis on the following steps:

Identify from data users which OMNIbus events are incomplete.

Identify which external data owners have information that can be used to enhance OMNIbus events.

Request external data owners to advise on data structures (for example, database names, tables, fields).

Request external data owners create user accounts to permit IBM Tivoli Netcool Impact to access the data.

Determine external data access details to enable creation of data sources.

Determine which events need enriching and develop and implement appropriate policies.

Confirm with data users that events now contain additional information.

Given that functional requirements for IBM Tivoli Netcool Impact have been identified and external resources have been established, determine the users, administrators and authentication specifics so that users can be configured within IBM Tivoli Netcool Impact. With emphasis on the following steps:

Determine administrators of the Netcool users.

Determine users of the IBM Tivoli Netcool Impact system.

Determine native or external authentication.

Determine SSL requirements.

Given detailed functional requirements, assess existing application infrastructure such that application dependencies are documented. With emphasis on the following steps:

Review detailed functional requirements.

Assess application infrastructure.

Determine Netcool application dependencies: Precision, TBSM, ObjectServers, fields in ObjectServer, database accesses, data sources, data types.

Determine other application dependencies, for example: Oracle, Web Services, DB2, Jabber, XML, e-mail, data source adapters.

Document application dependencies.

Section 2: Installation

Given the prerequisite components, verify their setup so that the IBM Tivoli Netcool Impact Server is ready for installation. With emphasis on the following steps:

Verify installation of Netcool Security Manager.

Verify installation of a Netcool OMNIbus ObjectServer instance.

Verify IBM Tivoli Netcool Impact Server system requirements.

Verify file permissions for source and destination directories where IBM Tivoli Netcool Impact will be installed.

Verify all necessary operating system patches and packages are installed on IBM Tivoli Netcool Impact Server

Verify hard disk space requirements on IBM Tivoli Netcool Impact Server.

Verify availability of console emulation availability when remotely installing IBM Tivoli Netcool Impact on a Windows Server.

Given available ports, additional components, resiliency requirements and Nameserver location, identify all of the installation parameters so that installation parameters are identified in preparation for installation of IBM Tivoli Netcool Impact. With emphasis on the following steps:

Identify whether default installation directory ($NCHOME - unix, %NCHOME% - Windows) has been defined. If so, assess whether there may be any conflicts with existing applications. Identify configuration settings for additional components (such as, License Manager (if applicable), Security Manager, GUI Server (if applicable), default ObjectServer).

Determine naming conventions for IBM Tivoli Netcool Impact servers and clusters.

Determine if the IBM Tivoli Netcool Impact Database Server is to be installed. If so (UNIX only), ensure that the minimum specified shared memory is available.

Determine if there are any potential conflicts with default ports to be used (using netstat, and with reference to IBM Tivoli Netcool Impact Administration guide).

Identify setting for e-mail sender service, if required.

Determine which version of CVS is to be used.

Given the determined technical architecture and installation prerequisites and parameters, obtain, install, test and document the IBM Tivoli Netcool Impact solution so that a functioning IBM Tivoli Netcool Impact solution is available and deployment is documented. With emphasis on the following steps:

Download IBM Tivoli Netcool Impact Server Binaries.

Uncompress IBM Tivoli Netcool Impact Server Binaries.

Review Installation Parameters.

Execute IBM Tivoli Netcool Impact Installer.

Review installation and installation logs for issues.

Start IBM Tivoli Netcool Impact Server.

Test availability and proper installation.

Document installation procedure.

Given the architecture resiliency requirements, install two IBM Tivoli Netcool Impact server cluster members, configure the necessary failover points, and set up self-monitoring of IBM Tivoli Netcool Impact so that all components meet the requirements. With emphasis on the following steps:

Review the requirements and determine appropriate resilient architecture.

Install the primary IBM Tivoli Netcool Impact server in the cluster.

Install the secondary IBM Tivoli Netcool Impact server cluster member.

Set the server clustering properties.

Configure an Object Server data source with failover.

Configure other data sources with failover.

Set up IBM Tivoli Netcool Impact self-monitoring.

Recommend actions to be taken on self-monitoring events.

Given the various IBM Tivoli Netcool Impact component scripts, configure application startup so that all necessary components are running and will start up automatically upon physical server restart. With emphasis on the following steps:

Select the IBM Tivoli Netcool Impact Services to automatically start up (such as event readers, policy activators, email readers).

Start GUI server (if deployed remotely).

Start WASCE Server (includes auto-startup of GUI Server and IBM Tivoli Netcool Impact Server, unless deployed remotely).

Start IBM Tivoli Netcool Impact's Postgres database.

Start IBM Tivoli Netcool Impact server separately (if deployed remotely).

Start secondary IBM Tivoli Netcool Impact Server (if clustering is deployed).

Start JRExec process on all IBM Tivoli Netcool Impact Servers.

Deploy script to auto-start all processes upon physical server startup (UNIX Installation).

Set up Windows Services for automatic startup (Windows Installation).

Section 3: Configuration

Given appropriate data access and the documented system architecture, configure and test IBM Tivoli Netcool Impact data sources such that defined data sources are operational. With emphasis on the following steps:

Obtain access information from identified personnel (hostname/IP, database name/instance, schema, login, ports).

Obtain Web Services definition library files and XML schema definitions, if applicable.

Configure IBM Tivoli Netcool Impact data sources per the documented system architecture through IBM Tivoli Netcool Impact GUI.

Test connection to and from IBM Tivoli Netcool Impact data source (where applicable).

Given a properly configured and accessible data source and access to the IBM Tivoli Netcool Impact GUI, create a data type based on that data source such that a configured data type with access to data items within the data type is available. With emphasis on the following steps:

Select the Data Types tab.

Select the data source required for the data type from the drop-down list, and then select Add.

In the DataType window, provide a unique name for the Data Type.

Select a different display icon, if required.

Input details of the base table of the database and then select Refresh.

Select at least one field of the returned table as the key field.

Remove fields from the table if not required in the Data Type.

Select an appropriate field for the Display Name.

Apply a filter condition to apply to the Data Source's Data Items, as required.

Apply a sort order to apply to the Data Source's Data Items, as required.

Save the configuration by selecting the Floppy Disk icon

Confirm the Data Type's configuration by selecting the View Data Items icon adjacent to the Data Type entry.

Given that IBM Tivoli Netcool Impact has been properly installed, the name of the IBM Tivoli 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. With emphasis on the following steps:

Determine Name of IBM Tivoli Netcool Impact Server.

Determine Valid Username/Password combination.

Determine Policy Name.

Optionally determine "@" Identifier and "@" Serial fields.

Optionally determine encrypted password.

Given the anticipated event volumes and multi-policy processing, set up event processor so that processing of events is optimized with minimal conflicts. With emphasis on the following steps:

Determine if event volumes warrant additional multi-threading of policy processing.

Select the Event Processor Service from the Service Status Pane.

Enter the desired number of simultaneous threads.

Enter the desired maximum number of events per query.

Enter the desired event fetch rate.

Select whether to enable logging.

Save configuration; stop and restart event processor.

Determine whether to enable event locking within the Event Readers, and update Event Readers accordingly.

Given that access to data sources has been configured, data types have been created and policies written, identify IBM Tivoli Netcool Impact Service configuration requirements so that Event Readers can be created within IBM Tivoli Netcool Impact. With emphasis on the following steps:

Determine Service Name.

Determine Data Source.

Determine Polling Interval.

Determine Restrict Fields.

Determine IBM Tivoli Netcool Impact Server startup requirements.

Determine logging and reporting requirements.

Determine Event Mapping requirements.

Given that Services are available, configure Services such that logging is available. With emphasis on the following steps:

For any Service where logging is an option, select the Service to access the configuration window.

Review Service Log: write to file option and select or de-select as required and then select Ok.

For the Policy Logger service, select or de-select the following Log options, as required:

Highest Log Level (0-3)

All SQL statements

Pre-execution Action Module Parameters

Post-execution Action Module Parameters

All Action Module Parameters

Service Log: Write to file; Append Thread Name to Log File Name; Append Policy Name to Log File Name

For any Service where logging has been selected, check the log files at $NCHOME/impact/log/.log.

Section 4: Development

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

Review the requirements.

Formulate a development plan for accessing appropriate data.

Formulate a development plan for testing the policy during development.

Verify access to test systems and data.

Define the event or trigger that will execute the policy.

Identify any relationships or interactions with other events or policies.

Create pseudo-code or flow chart.

Given that IBM Tivoli Netcool Impact planning requirements have been met, proper Installation and Configuration of the IBM Tivoli 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. With emphasis on the following steps:

Determine Policy Interaction requirements.

Determine Event Suppression Flow requirements.

Determine Communication States between ObjectServer and IBM Tivoli Netcool Impact requirements.

Determine Column Name and Data Type.

Log in to Netcool ObjectServer with Administration application.

Use Administration tool to create ObjectServer Columns.

Optionally Use SQL Interactive to create ObjectServer Columns.

Given pseudo-code or policy flow statements with properly configured data sources and data types, develop and unit test IBM Tivoli Netcool Impact policies such that functional requirements are met. With emphasis on the following steps:

Determine the functional category.

Event Enrichment policy

X in Y Policy

Event Notification

Event Gateway or Third-party integration

Event Correlation

Event Consolidation or Service Event

Message (e-mail reader or IM reader) policy

Scheduling policy

Develop IBM Tivoli Netcool Impact policies.

Data types: user defined variables, arrays, context

Control structures: if statements, while statements

Functions: action, parser, user defined

Logging: policy context and checkpoints

Unit test functions or functional blocks.

Given the tasks required, configure IBM Tivoli Netcool Impact services so that policies are automatically executed. With emphasis on the following steps:

Determine which services and methods are necessary to automate policy execution.

Determine triggers and filters to automate policy execution within service with consideration +#Given to avoid conflicts between policies.

Obtain required data to enable IBM Tivoli Netcool Impact Service.

Email Server information (if an Email Reader Service is necessary)

Event Listener Service Information (if an Event Listener Service is necessary)

ObjectServer Connectivity Information (if an Event Reader Service is necessary)

Instant Messaging Jabber Server Information (If a Jabber Reader Service is necessary)

Java Messaging Bus information (if JMS Message Listener Service is necessary)

Determine frequency to execute policies.

Configure new or existing services.

For Event Reader Service, create event mapping filters with special attention given to avoid conflicts between policies, and to achieve efficient processing.

Given that an Operator View is required, create and configure an Operator View so that an Operator View is available. With emphasis on the following steps:

Select New Operator View from the Operator View tab.

In the Operator View configuration panel, define the Operator View, as necessary, using the following tabs:

Name & Layout

Action Panel

Information Groups

Save the Operator View by selecting the Floppy Disk icon.

If a custom Operator View is required modify the Operator View files as follows:

Edit the Operator View definition policy

Edit the Operator View html file

Review the Operator View, from a Web browser.

Given the system requirements and a functioning IBM Tivoli Netcool Impact system with deployed policies and services, plan, set up, implement and review IBM Tivoli Netcool Impact systems test with relevant stakeholders so that properly configured test systems and data are verified. With emphasis on the following steps:

Review technical architecture and requirements.

Map requirements into system test cases.

Create system test plan.

Get stakeholder approval for system test plan.

Set up test systems required.

Set up test data as required.

Execute system test.

Document test results.

Review test results with all stakeholders and developers.

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. With emphasis on the following steps:

Review the requirements.

Identify the available exception notification capabilities.

Identify the parties who must be notified.

Formulate and publish a plan for policy exceptions.

Define a standard, programmatic mechanism for handling policy exceptions.

Produce a document that defines how to handle exceptions within policies.

Section 5: Administration

Given that IBM Tivoli Netcool Impact planning requirements have been met, proper installation and configuration of the IBM Tivoli Netcool Impact Server has occured, an IBM Tivoli Netcool Impact Server is running and accessable, and project members have been determined, configure IBM Tivoli Netcool Impact projects so that functional requirements are met. With emphasis on the following steps:

Determine project members from Global Repository based on functional requirements.

Log in to IBM Tivoli Netcool Impact.

Select Project Tab.

Enter name of Project and select New button.

Select Members from the Global Repository for Data Sources, Data Types, Policies, Services and Operator Views.

Select OK and save Project.

Given detailed functional requirements related to user access and roles, configure users and roles in Security Manager so that users have appropriate access to IBM Tivoli Netcool Impact. With emphasis on the following steps:

Interview stakeholders on desired user roles.

Determine users requiring access to IBM Tivoli Netcool Impact.

Set up Security Manager with appropriate role(s).

Create IBM Tivoli Netcool Impact users in Security Manager.

Assign roles to users in Security Manager to match requirements.

Given the technical architecture and requirements for a functioning IBM Tivoli Netcool Impact deployment, deploy IBM Tivoli Netcool Impact objects so that deployment policy usage is documented and objects are deployed to other servers and clusters as needed. With emphasis on the following steps:

Determine method for moving object.

command-line utility nci import/export

deployment function

Review technical requirements.

Create deployment policies needed based on architecture.

Test deployment policies.

Document deployment policy usage.

Deploy objects as needed.

Given that IBM Tivoli Netcool Impact Server A has been configured, export data from IBM Tivoli Netcool Impact Server A such that the data can be Imported into IBM Tivoli Netcool Impact Server B. With emphasis on the following steps:

Ensure that IBM Tivoli Netcool Impact Server A is running.

From IBM Tivoli Netcool Impact Server A's user interface, Global tab, select Clear all Source Control File Locking: button.

Export the data from IBM Tivoli Netcool Impact Server A using nci_export and specifying a location for the export directory.

Copy the export directory to a temporary location within IBM Tivoli Netcool Impact Server B's host server.

Ensure IBM Tivoli Netcool Impact Server B is running.

From IBM Tivoli Netcool Impact Server B's user interface, Global tab, select Clear all Source Control File Locking: button.

Import data into IBM Tivoli Netcool Impact Server B using nci_import and specifying the location of IBM Tivoli Netcool Impact Server A's exported data

Check the IBM Tivoli Netcool Impact Server B's log file for errors.

Shut down and re-start IBM Tivoli Netcool Impact Server B in order to view the imported data within the user interface.

Given a running IBM Tivoli Netcool Impact server and any EAR file modification requirements, modify the IBM Tivoli Netcool Impact ear file and redeploy it so that the WASCE server is running the newly modified version. With emphasis on the following steps:

Determine if this is to be a HOT or COLD redeploy.

Execute the nci_ear_editor utility.

Redeploy the EAR.

For a HOT redeployment, verify that ear was redeployed in wasce.log file.

For a COLD redeployment: stop WASCE; remove the previous deployment files; restart WASCE; review the wasce.log file.

Given that the IBM Tivoli Netcool Impact EAR file has been modified, deploy a new EAR file such that IBM Tivoli Netcool Impact has the new functionality. With emphasis on the following steps:

Access and log in to the WASCE management console from a Web browser.

Select Application EARs from Console Navigation pane.

Uninstall the IBM Tivoli Netcool Impact component.

Select Deploy New from Console Navigation pane.

Navigate to the location of the modified EAR file, and then select the file.

Select Start application after installation, as required, and then select the Install button.

Confirm application has started within WASCE.

Log out of the WASCE console.

Check log files for errors and resolve as appropriate.

Log in to IBM Tivoli Netcool Impact and confirm that the new functionality is available.

Section 6: Troubleshooting and Performance Tuning

Given an installed IBM Tivoli Netcool Impact system based on technical architecture specifications, review the deployment documentation and check various outputs of systems so that a properly installed IBM Tivoli Netcool Impact system is verified. With emphasis on the following steps:

Review technical architecture and requirements.

Review installation logs for errors.

Review external systems logs for errors.

Review IBM Tivoli Netcool Impact server logs for errors.

Given an operating IBM Tivoli Netcool Impact server and performance requirements, analyze reports, identify potential bottlenecks, and create recommendations for those bottlenecks so that a document describing performance bottlenecks is created recommending appropriate actions to mitigate the issues. With emphasis on the following steps:

Enable the appropriate monitoring reports.

Review the monitoring reports and identify problem areas.

Map problem performance areas to specific policies or services.

Review the policy code or service configuration.

Identify external system bottlenecks.

Document the potential bottlenecks and provide to policy developers or system administrators for review and recommendations.

Consolidate and publish the recommendations.

Given that a functional IBM Tivoli Netcool Impact Installation is running, logging standards and IBM Tivoli Netcool Impact Services are configured, utilize IBM Tivoli Netcool Impact and system tools so that performance issues may be assessed. With emphasis on the following steps:

Utilize Server Logs: netcool.log, (Server)_(Service).log, (Server)_Policylogger.log, (Server)_Policylogger_PolicyName.log.

Utilize Operating System Tools: netstat, uptime, iostat, sar, vmstat, top.

Utilize self-monitoring service.

Determine when to utilize.

Enable using GUI ( IBM Tivoli Netcool Impact Self-Monitoring Service), or CLI ( IBM Tivoli Netcool Impact Clustered mode), ( IBM Tivoli Netcool Impact Service)_selfmonitoring.props.

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

Utilize Reporting Tools.

Determine when to utilize.

Enable using IBM Tivoli Netcool Impact Policy Logger Service.

Analyze Network and Network Operators Reports: Node Efficiency Report, Operator Efficiency Report.

Analyze IBM Tivoli Netcool Impact Configuration Reports: Action Efficiency Report, Action Error Report., Impact Profile Report, Impact Return on Investment Report, Policy Efficiency Report, Policy Error Report.

Given known bugs or issues, test system and review logs so that bugs and issues are isolated within the system. With emphasis on the following steps:

Review bug tracking list or known issues.

Increase logging level in the Policy Logger service.

Replicate the bug..

Review Policy logs, Event Reader logs and Server logs to determine where bug(s) exist in policy.

Review Event Reader configuration if applicable.

Given that IBM Tivoli Netcool Impact CVS is generating error messages in the log files, troubleshoot IBM Tivoli Netcool Impact CVS using nci_version_control such that error messages are not generated. With emphasis on the following steps:

If CVS is preventing a policy or other object (data source, data type) from being configured, use the IBM Tivoli Netcool Impact cvs script, nci_version_control, to modify the status of the file. The script can be used for the following actions:

Check in a file.

Check out a file.

Add a file.

Remove a file.

Uncheck out a file.

Rename a file.

Download 000-938 Exam Testing Engine