|
|
 |
|
Welcome to my Blog!
|
|
Test information:
Number of questions: 52
Time allowed in minutes: 75
Required passing score: 59% or 56%
Test languages: English The test consists of six sections containing a total of approximately 52 multiple-choice questions. The percentages after each section reflect the approximate distribution of the total question set across the sections. Section 1 - Planning (13%) Identify the features and benefits of IBM WebSphere MQ
Identify the migration considerations (e.g., 64 bit, SSL migration, IPv6 support)
Identify the functionalities of IBM WebSphere MQ across platforms
Describe the necessary pre-requisites for implementing an IBM WebSphere MQ configuration
Select appropriate logging options for a recovery strategy
Section 2 - Installation and Configuration (24%) Create a working queue manager
Create the necessary IBM WebSphere MQ objects to support an application
Identify differences between persistent and non-persistent messages, including features that are new for IBM WebSphere MQ V6.0
Identify features of Eclipse MQ Explorer, MQSC scripting, PCF commands, ISPF panels (Interactive Systems Productivity Facility), and Command Language (CL)
Create/modify IBM WebSphere MQ objects necessary for a triggered application
Configure IBM WebSphere MQ objects for Web Services
Configure IBM WebSphere MQ objects for JMS
Section 3 - Distributed Queuing and Clustered Queue Management (24%) Select the appropriate IBM WebSphere MQ configuration. (e.g., hub and spoke, star, clustering)
Create the appropriate IBM WebSphere MQ objects to satisfy a WebSphere MQ network design
Install a IBM WebSphere MQ client and connect the client to a queue manager server
Choose the appropriate methods of starting and stopping channels
Create and manage the objects required to enable clustering
Identify IBM WebSphere MQ clustering workload management capabilities
Describe different message channel compression options for IBM WebSphere V6.0
Predict the final destination of a message given a scenario containing alias or remote definitions
Section 4 - Operations (13%) Start and stop queue managers and appropriate queue manager services
Design procedures to recover messages and queues in the event of failure
Optimize IBM WebSphere MQ performance for application throughput
Monitor and change IBM WebSphere MQ objects using the administrative facilities
Section 5 - Problem Determination (13%) Locate sources of information (e.g., IBM WebSphere MQ error logs, operating system logs, FFST files) to help identify problem
Determine cause of problem
Recover from problem
Follow the message path
Section 6 - Security (13%) Determine the need for and install various channel exits
Control access to IBM WebSphere MQ objects
Determine when and why to use the REFRESH SECURITY command
Identify the SSL functions provided in IBM WebSphere MQ
Configure IBM WebSphere MQ channels with SSL
To assess your current skill level and readiness for Test 992 - IBM WebSphere MQ V6 System Administration, you can take a Web-based assessment test. Passing this assessment test does not result in achieving a credential. It is designed to provide diagnostic feedback on the Examination Score Report, correlating back to the test objectives, showing how you scored on each section of the test. For this assessment test, the passing score is 56% and the time provided to take the test is 90 minutes. A $10 USD test fee applies worldwide to each time a test is taken, even if the same test is retaken. VISA, Master Card and American Express credit cards are accepted. To take the assessment test: Access the Web-based test delivery tool Prime.
If you already have an account on Prime, select Secure Sign-In and continue to Take Test. Otherwise select First Time Registration and follow the 2 steps below: Step 1: If you already have a Prometric ID number enter it into Step 1. If you do not have one, proceed to Step 2.
Step 2: Select the WebSphere Assessment/Sample Tests section. Enter your demographic data and 'Submit'.
Note: Choose your username and password that you will use every time you take a test via Prime. Record them for future reference, along with your ID number that Prime generates. Select Take Test (first option).
Under Public Test (first rectangle), select the WebSphere Assessment/Sample Tests section, and 'Submit'.
Select Assessment: Test 992, IBM WebSphere MQ V6.0 System Administration, and proceed with on screen instructions.
Pass4side IBM WebSphere MQ V6 System Administration 000-992 demo download More Certification exam visit: www.pass4side.com
|
|
Test information: - Number of questions: 62
- Time allowed in minutes: 90
- Required passing score: 74%
- Test languages: English
Section 1 - Planning - Given the customer requirements in the Statement of Work, review the solution details in order to confirm the architecture. With emphasis on performing the following steps:
- Review proposed architecture.
- Determine high level architecture.
- Determine unique requirements
- Determine hardware and OS.
- Evaluate port availability (firewall and Access Control Lists)
- Determine contacts at the customer.
- Gather Users, Roles, and Physical location.
- Evaluate security requirements.
- Determine integrations to existing customer applications.
- Given the design details develop an architecture document. With emphasis on performing the following steps:
- Verify all software needed.
- Determine product integration probes and gateways.
- Define components, locations, and network connectivity.
- Determine naming conventions.
- Determine directory for install.
- Review customer compliance requirements. (Acceptance testing.)
- Determine configuration of messages on the end nodes
- Given a design document obtain the required components so that you are ready to install Netcool/OMNIbus.
With emphasis on performing the following steps: - Determine appropriate installer (console vs. GUI).
- Obtain network availability.
- Obtain access to systems and servers.
- Obtain authorization for network.
- Obtain install media.
Section 2 - Installation - Given that environment variables have been set and sourced on a supported UNIX/Linux server, install Netcool/OMNIbus V7.2 using the console, so that the selected Netcool/OMNIbus V7.2 components are installed. With emphasis on performing the following steps:
- Download the required omnibus binaries from IBM support site.
- Locate the binaries on the UNIX/Linux server in an appropriate temporary location.
- Un-tar the package and run the install script ./INSTALL -console.
- Accept the license agreement
- Select the required features:
Desktop
Gateways
Process Control
Servers
ConfPack
Administrator
AEN Client
Local Help System
Install selected features
- Given OMNIbus is installed, download the probes patch from the IBM support site and install the patches using $NCHOME/omnibus/install/nco_patch so the probe is installed. With emphasis on performing the following steps:
- Download probe patch from the IBM support site.
- Untar the patch to a tmp directory.
- Run $NCHOME/omnibus/install/nco_patch –install <path_to_patch_folder>
- Type 'yes' and hit enter to install the probe.
- Given OMNIbus V7.2 is installed on a UNIX host and a FixPack is downloaded from the IBM support site, install the FixPack , so that the selected FixPack has been installed. With emphasis on performing the following steps:
- Run the FixPack install command: $NCHOME/install/ncisetup –install <path_to_FixPack>
Individual should receive a notice that the patch has successfully been installed.
- Given OMNIbus V7.2 has been installed and configured on UNIX/Linux, export configuration of the ObjectServer and import it into another ObjectServer using nco_confpack, so that the ObjectServer configuration can be exported and imported. With emphasis on performing the following steps:
- Create a list of exportable configuration items using $NCHOME/omnibus/bin/nco_confpack -list -server NCOMSI -file /tmp/NCOMSI_list
- Edit package list /tmp/NCOMSI_list to contain only the items to export
- Export NCOMSI configuration using: $NCHOME/omnibus/bin/nco_confpack -export -file /tmp/NCOMSI_list - package /tmp/NCOMSI_package.
- Import NCOMSI configuration in to NCOMS2 using: $NCHOME/omnibus/bin/nco_confpack -import –package /tmp/NCOMSI_package -server NCOMS2.
Section 3 - Configuration - Given a supported UNIX/Linux operating system and Netcool OMNIbus V7.2 and a user with proper permissions, configure and verify environmental variables, so that the environmental variables have been configured. With emphasis on performing the following steps:
- Start the UNIX text editor.
- Edit system home profile /etc/profile
- Define Netcool Environment Variables: $NCHOME; $LD_LIBRARY_PATH (opt); $PATH (opt.); $LANG (if required).
- Netcool users must source this file when they login.
- Given a UNIX/Linux OS, and the ObjectServer was installed by the root user, the root user owns the $NCHOME directory. Configure the system so that a non root user (netcool) is a member of the netcool group.
With emphasis on performing the following steps: - Find an unused group number for example 550 by doing a more /etc/group
- Add a new group netcool: groupadd -g 550 netcool
- Add root user to the netcool group within /etc/group.
- Given OMNIbus V7.2 is installed on a IPv4 or IPv6 UNIX/Linux server, configure OMNIbus communications, so that communications are configured. The hostname may or may not be resolvable to the IP address (IPv4 or IPv6). With emphasis on performing the following steps:
- If the hostname is resolvable to an IP address, edit: $NCHOME/etc/omni.dat and replace "omnihost" with local servers hostname. If the hostname is not resolvable to an IP address, replace "omnihost" with the appropriate IPv4 or IPv6 address.
- Run $NCHOME/bin/nco_igen.
- Given OMNIbus V7.2 has been installed and configured, environmental variables have been set on a supported Windows server, verify OMNIbus communications, so that OMNIbus communications are available.
With emphasis on performing the following steps: - Run the Netcool Server Editor. Run ->All Programs->Netcool OMNIBUS-> System Utilities -> Server Editor.
- Highlight appropriate ObjectServer and select 'test" check for "servers available" window.
- Given an OMNIbus install on UNIX/Linux, create a working object server instance using available Netcool commands and files , so that an ObjectServer has been created and an instance configured.
With emphasis on performing the following steps: - Open a command line and run $NCHOME/omnibus/bin/nco_dbinit -server <name>.
- Edit $NCHOME/etc/omni.dat file and set the ObjectServer name and port.
- Run $NCHOME/bin/nco_igen.
- Given that OMNIbus is installed on UNIX/Linux, start the ObjectServer and run nco_ping to verify the ObjectServer is running, so that the ObjectServer is available. With emphasis on performing the following steps:
- Run $NCHOME/omnibus/bin/nco_objserv -name <ObjectServer name>
- Verify the ObjectServer is running by using the $NCHOME/omnibus/bin/nco_ping <ObjectServer name>
- Given an ObjectServer is installed and running on a supported Unix/Linux OS, start and verify a local event list, so that local event lists can connect to the local ObjectServer. With emphasis on performing the following steps:
- Launch event list ($NCHOME/omnibus/bin/nco_event).
- Enter username and password.
- Verify event list connects to the ObjectServer.
- Given OMNIbus V7.2 has been installed and configured, environmental variables have been set, install the remote desktop, so that the remote desktop on a supported Windows desktop, so that the remote desktop can connect to the ObjectServer. With emphasis on performing the following steps:
- Locate and un-zip Omnibus binaries on remote desktop machine.
- Run the OMNIbus install package, setup.exe.
- Accept the license agreement.
- Choose the install directory.
- Deselect every program feature except the desktop component:
- Click the Installation button.
- Reboot the desktop on completion of installation.
- Create an entry for the objectserver in the Servers Editor on the remote desktop
- Launch the event list by selecting Start>All Programs>Netcool Suite> Event List and log into the ObjectServer.
- Given an OMNIbus V7.2 install, edit the probe properties file, set the SERVER property to the name of the ObjectServer and configure a probe to connect to an ObjectServer, so that the Probe is configured. With emphasis on performing the following steps:
- Open the Probe properties file.
- Set the server property to the name of the ObjectServer.
Given OMNIbus V7.2 has been installed and configured, environmental variables have been set and sourced on a supported UNIX/Linux server, the simnet probe package is installed, start and verify the probes, so that the probes are running and tested. With emphasis on performing the following steps: - Modify the simnet.props file and verify the ObjectServer target in $NCHOME/omnibus/probes/<arch>.
- Modify rules file (simnet.rules) to include the host system name in the manager field.
- Start the probe using the command line (nco_p_simnet).
- Check process list to verify probe is running.
- Launch the event list and verify probe events in the ObjectServer and verify events parsed correctly.
- Check for errors in log file.
- Given OMNIbus 7.2 is installed, configure an unidirectional gateway, so that the unidirectional gateway has been configured. With emphasis on performing the following steps:
- Create a directory for gateway files eg: $NCHOME/omnibus/gates/UNI_GATE.
- Copy all files from $NCHOME/omnibus/gates/objserv_uni to $NCHOME/omnibus/gates/UNI_GATE:
objserv_uni.props
objserv_uni.map
objserv_uni.reader.tblrep.def
objserv_uni.startup.cmd - Rename all files copied to match unique name of the uni-directional gateway, eg UNI_GATE.*
- Edit UNI_GATE.props file and modify the following properties:
Name
PropsFile
Gate.MapFile
Gate.StartupCmdFile
Gate.Reader.Server
Gate.Reader.TblReplicateDefFile
Gate.Writer.Server - Edit UNI_GATE.map file and UNI_GATE.reader.tblrep.def file, modify the entries to define which objectserver tables and fields are accessed by the gateway.
- Given OMNIbus is installed, configure a Oracle gateway Remedy Gateway, or ODBC gateway so that the unidirectional gateway has been configured.
- Given OMNIbus is installed, both ObjectServers (that will be connected via the gateway) are running, start an ObjectServer gateway. Update an event in an ObjectServer (source ObjectServer if a uni-gateway is used), confirm that the same event in the other objectserver has similarly changed, so that the gateway has been configured correctly and initialized. With emphasis on performing the following steps:
- Start a ObjectServer gateway using $NCHOME/omnibus/bin/nco_g_objserv_uni- name uni or $NCHOME/omnibus/bin/nco_g_objserv_bi - name BIGATE.
- Verify that the gateway is working by deleting and or modifying an event on the one ObjectServer and checking to see that the modification is made on the other ObjectServer.
- Given OMNIbus is installed add a server entry for nco_pa in omni.dat, run nco_igen, edit nco_pa.conf, set the hostname and name of ObjectServer in nco_pa.conf and configure process control, so that process control is configured. With emphasis on performing the following steps:
- Open $NCHOME/omnibus/etc/nco_pa.conf file.
- Change the name of the ObjectServer from NCOMS (if different).
- Set the omnihost value to the hostname of the local machine under nco_routing entry.
- Set user and password values under nco_routing if using secure mode, else delete the user and password values.
- Add an entry to $NCHOME/etc/omni.dat for nco_pa and run $NCHOME/bin/nco_igen.
- Given OMNIbus is installed on a UNIX/Linux system, process control is configured, run nco_pad, verify PA status using nco_pa_status to start process control and verify that process control is available and running.
With emphasis on performing the following steps: - Run $NCHOME/omnibus/bin/nco_pad.
- Run $NCHOME/omnibus/bin/nco_pa_status -server NCO_PA.
- Manually kill one of the running processes using ‘kill pid’ where pid is the process id of the process that was killed.
- Run $NCHOME/omnibus/bin/nco_pa_status -server NCO_PA to verify that the killed process is running with a different process ID.
- Given OMNIbus is installed on UNIX/Linux and root level access has been granted, configure, run and verify the startup scripts, so that start-up scripts have been configured and verified. With emphasis on performing the following steps:
- Execute the start-up script, $NCHOME/omnibus/install/startup/<arch>install.
- Verify the creation of symbolic links.
- Input/verify the process control name.
- Select secure mode or not.
- Enter a value for the netcool_license_file variable. Save the file.
- Start nco script via the command line nco start.
- Verify that the process control has started.
- Run nco stop. Verify nco_pad has stopped.
- Given an OMNIbus install on UNIX/Linux, copy all gateway files from $NCHOME/omnibus/gates/objserv_bi to a new directory, configure gateway properties file, configure a server entry for the bi-directional gateway and create a bi-directional gateway between two ObjectServers, so that bi-directional gateway is configured.
With emphasis on performing the following steps: - Create a directory for gateway files. Example: $NCHOME/omnibus/gates/BI_GATE.
- Copy all files from $NCHOME/omnibus/gates/objserv_bi to $NCHOME/omnibus/gates/BI_GATE.
- Edit $NCHOME/omnibus/gates/BI_GATE/objserv_bi.props and set the following properties: Gate.MapFile; Gate.StartupCmdFile; Gate.ObjectServerA.Server; Gate.ObjectServerA.TblReplicateDefFile; Gate.ObjectServerB.Server; Gate.ObjectServerB.TblReplicateDefFile.
- Copy $NCHOME/omnibus/gates/BI_GATE/objserv_bi.props to $NCHOME/omnibus/etc/BI_GATE.props
- Edit $NCHOME/etc/omni.dat and add an entry for BI_GATE.
- Run $NCHOME/bin/nco_igen.
- Given OMNIbus V7.2 has been installed and configured, add a user so that users are created in OMNIbus.
With emphasis on performing the following steps: - From the main OMNIbus Administrator window, select the "user" tab and then select "user".
- Click the "Add User" icon in the toolbar.
- Enter a Name and Select an unused User ID.
- Enter a Full Name.
- Put a check in the "Create Conversion" checkbox
- From the "Groups" tab, double-click Administrator to assign the administrator role. Click "OK".
- Given OMNIbus V7.2 has been installed and configured, environmental variables have been set, create a view based on the statement of work, so that an event view has been created. With emphasis on performing the following steps:
- Launch View Builder from the Event List.
- Select Filet --> New.
- Enter View Name.
- From Available Field pane select Node, Severity, and Summary.
- From Available Sort Fields pane select Severity.
- In the Sorted by pane, double-click the Severity icon to set sort order to descending order.
- Click Apply
- Click Close.
- Click File --> Save from Main Event List window.
- Given OMNIbus V7.2 has been installed and configured, utilize the Event List GUI (nco_event) to create a Filter using the Desktop client, so that an event filter has been set. With emphasis on performing the following steps:
- Click Filter Builder button on Sub-Event List.
- Click File --> New.
- Provide Filter Name.
- Select Severity from the Column drop down menu.
- Select Greater than or Equal to from Operator drop down.
- Select Minor (#) from Value drop down menu.
- Click Apply.
- Click File --> Save from the Main Event List window.
- Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) to add a restriction filter, so that a restriction filter has been added. With emphasis on performing the following steps:
- From the main OMNIbus Administrator window, select the "Users" tab and then select Restriction Filters.
- Select Add Restriction Filter from the toolbar.
- Assign a Name to the filter.
- Enter the filter criteria.
- Click OK.
- Given OMNIbus V7.2 has been installed and configured, create a new menu, so that a menu is created.
With emphasis on performing the following steps: - From the Menu tab select Add New Item within the Configuration Manager GUI.
- Select Menu Item Type, Tool, and Title, then click OK.
- Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) create a new database field, so that a new database field has been created. With emphasis on performing the following steps:
- Select the System tab from the Administrator GUI.
- Select Databases.
- Select Databases Alerts and Table Status.
- Select Add Column icon from the menu.
- Enter Column Name, Data Type.
- Click OK.
- Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) add a tool, so that a tool has been added. With emphasis on performing the following steps:
- Within the Tools menu, click Add Tool.
- Enter a Name.
- Select Enter Relevant Tool Instructions.
- Click OK.
- Given OMNIbus V7.2 has been installed and configured, use the Administrator GUI (nco_config) create a trigger, so that a trigger has been created. With emphasis on performing the following steps:
- Select DB Trigger.
- Select Trigger Group.
- Enter Trigger Name.
- Set Trigger Priority.
- Set Action on Delete.
- Set Apply To pane to Statement.
- Enter SQL code for action. Begin Write into dellogs1 values ('The following row was deleted at; getdate (), old.Node, old.Summary); End
- Enable Trigger.
- Click OK.
- Given OMNIbus V7.2 has been installed and configured, the ObjectServer is running, customize the Rules file, so that a customized probe rules file is available. With emphasis on performing the following steps:
- Open probe rules file with text editor.
- Create a temporary element to hold a value extracted from @Summary.
- Assign a probe property to the @Summary field.
- Add a "switch" statement to execute a rule based on node name.
- Use an "include" statement to include a new rule file segment.
- Make a change so that @AlertGroup is updated on deduplication.
- Discard events with the word "test" in the @Summary field.
2Create a lookup table to look up department name based on node name. - Turn on probe details if @Summary=unknown.
- Test the syntax of the new rules file and debug.
- Update the probe rules file without stopping the probe.
- Given an OMNIbus install running on UNIX/Linux, configure primary ObjectServer (NCOMS_P), create a backup ObjectServer (NCOMS_B), set the BackupObjectServer property to TRUE, configure bi-directional gateway, configure triggers & procedures and create a high availability architecture, so that automated failover and failback architecture is configured. With emphasis on performing the following steps:
- On the primary ObjectServer host, create the primary ObjectServer.
- On the backup ObjectServer host, create the backup ObjectServer.
- Edit $NCHOME/omnibus/etc/NCOMS_B.props and set the Backup ObjectServer property to 'True'.
- Configure a bi-directional gateway between the primary and backup ObjectServer.
- On primary ObjectServer host, configure $NCHOME/etc/omni.dat for the primary and backup ObjectServer entries.
- On primary ObjectServer host run $NCHOME/bin/nco_igen. Copy $NCHOME/etc/interfaces.<arch> file to the backup ObjectServer host.
- On backup ObjectServer, enable 'backup_startup, backup_counterpart_down, backup_counterpart_up' triggers for automation failover & failback.
- On backup ObjectServer, disable 'primary_only' trigger group for automation failover & failback.
- Given OMNIbus V7.2 has been installed and configured, add entries to omni.dat for primary and desktop ObjectServer run the command $NCHOME/bin/nco-igen, copy the $NCHOME/etc/interfaces.<arch> file from the primary ObjectServer host to the desktop ObjectServer host, configure the desktop ObjectServer, configure a unidirectional gateway between the primary and desktop ObjectServer to set up desktop architecture, so that the desktop architecture is configured. With emphasis on performing the following steps:
- On the primary ObjectServer host edit $NCHOME/etc/omni.dat and add entries for the primary and desktop ObjectServers.
- Run $NCHOME/bin/nco_igen copy $NCHOME/etc/interfaces.<arch> file from the primary ObjectServerhost to the desktop ObjectServer host.
- Create and configure the primary ObjectServer.
- Create the desktop ObjectServer using $NCHOME/omnibus/bin/nco_dbinit -desktopserver -server DESKOS.
- Start the desktop ObjectServer.
- Using $OMNIHOME/bin/nco_sql insert the following row in to the master national table or the DESKOS. (O, MASTEROS, 1).
- Configure a uni-directional gateway between the primary ObjectServer and the desktop ObjectServer.
- Given OMNIbus V7.2 has been installed and configured on UNIX/Linux, export configuration of the ObjectServer and import it into another ObjectServer using nco_confpack, so that the ObjectServer configuration can be exported and imported. With emphasis on performing the following steps:
- Create a list of exportable configuration items using $NCHOME/omnibus/bin/nco_confpack -list -server NCOMSI -file /tmp/NCOMSI_list
- Edit package list /tmp/NCOMSI_list to contain only the items to export
- Export NCOMSI configuration using: $NCHOME/omnibus/bin/nco_confpack -export -file /tmp/NCOMSI_list - package /tmp/NCOMSI_package.
- Import NCOMSI configuration in to NCOMS2 using: $NCHOME/omnibus/bin/nco_confpack -import –package /tmp/NCOMSI_package -server NCOMS2.
- Given OMNIbus V7.2 has been installed and configured, environmental variables have been set, add a group, so that a group is added. With emphasis on performing the following steps:
- From the main OMNIbus Administrator window, select the Users tab and then select Groups.
- Click the Add Group icon.
- Assign a name to the group.
- Assign an unused Group ID.
- Assign a Role.
- Assign a Restriction Filter.
- Click OK.
- Given OMNIbus V7.2 has been installed and configured, create a class, so that a class has been created.
With emphasis on performing the following steps: - Using the Configuration Manager, select Add Class from the Visual menu.
- Assign an identifier.
- Name the class.
- Click OK.
- Given OMNIbus V7.2 has been installed and configured, create a role, so that a role is available.
With emphasis on performing the following steps: - Within the Configuration Manager select the Users tab.
- Select Roles and Add New Role menu item.
- Add Role name.
- Assign Role Permissions.
- Click Save.
- Given an OMNIbus installed and running, configure omnibus probes rules to flag some events for acclerated event notification, create channels and configure triggers to send event details using these channels so that accelerated event notification is configured for some events. With emphasis on performing the following steps:
- Modify probe rules file using text editor and flag the events which has Summary like 'Port failure'.
- Configure channels to broadcast event data for the flagged events.
- Using IDUC EVTFT and IDUC SNDMSG, create and configure post-insert or post-update or post-reinsert triggers to send event notification to AEN client.
- Given OMNIbus V7.2 has been installed and configured on a UNIX/Linux system, configure the Accelerated Event Notification (AEN) Client so that the AEN Client is configured. With emphasis on the following steps
- Start the AEN Client using the command $NCHOME/omnibus/bin/nco_aen
- If starting the AEN for the first time, right-click the AEN icon and select ‘Properties’
- On the Application tab make the following selections:
- Notification settings:
Server (from drop-down list – Note if unpopulated, or required server is not available, add details to the interfaces file))
View in either Netcool Event List or Netcool Webtop
Launch in Control Settings
For either Netcool Event List or Netcool Webtop, specify the required Server and View
iBrowser Settings - Specify the Browser to use.
- Configure Message and Channels tabs, as required
- Select ‘Ok’
- Given that the AEN Client has previously been configured, log on to AEN Client by right-clicking icon and select ‘Sign In’
- Input a valid ObjectServer user details and select ‘Log In’
- Observe that the Icon changes from x to y..
- Given OMNIbus V7.2 has been installed on a UNIX/Linux system, configure the ObjectServer system so that it is Accelerated Event Notification messages can be sent so that the ObjectServer AEN feature is configured.
With emphasis on the following steps: - Determine whether AEN events are to be generated at a probe or by a trigger.
- If AEN events are to be generated by a probe:
- Create a dedicated ObjectServer Flag field.
- Modify the probe rules file to set the Flag field for AEN events
- Create a database trigger to respond to either the Flag field or the appropriate database action/database condition, using SQL commands IDUC EVTFT or IDUC SNDMSG to generate the AEN.
- Configure a Channel to broadcast AEN event data by doing the following:
- From with Netcool/OMNIbus Administrator, select Channels from System menu
- Right-click within the GUI to select ‘Add a new Channel’
- Within the Channel Details screen, add a name for the Channel
- On the ‘Channels’ tab, select ‘Channel Columns Detail’ button to be able to define the ObjectServer Table and Fields to use for the notification, then select ‘Ok’
- On the ‘Recipients’ tab, select ‘Add new Channel Recipient’ button to be able to define recipients for the notification, then select ‘Ok’
- When complete, click the ‘Ok’ button on the Channel Details screen
- Test the Channel notification by right-clicking the Channel and selecting ‘Send Message’
- Given that ObjectServer V7.2 is running on a UNIX/Linux platform and the Tivoli Health Monitoring Agent for ObjectServer V7.2 is installed. Configure the agent so that the agent will monitor the ObjectServer. With emphasis on the following steps:
@cd <tivoli installdir>/<arch>/no/bin
@Import the schema and automations to the ObjectServer as follows:
$NCHOME/bin/nco_sql -user root -S<server_name> < itm_os.sql
Section 4 - Performance Tuning and Problem Determination - Given OMNIbus V7.2 has been installed and configured, add devices to simnet.def file and run the simnet probe to generate test events using the simnet probe, so that test events are generated. With emphasis on performing the following steps:
- Edit $NCHOME/omnibus/probes/ARCH/simnet.def file and add line device1 0 50 & device2 3 100.
- Set the property in $NCHOME/omnibus/probes/ARCH/simnet.props to $NCHOME/omnibus/probes/ARCH/simnet.def.
- Set the server property in $NCHOME/omnibus/probes/ARCH/simnet.props to the name of the ObjectServer. Server:
- Start the simnet probe using $NCHOME/omnibus/probes/nco_p_simnet
- Given a failover architecture, verify that the failover architecture is working, so that failover functionality has been confirmed. With emphasis on performing the following steps:
- Shut down the Master ObjectServer
- Connect desktop client to the backup ObjectServer using $NCHOME/omnibus/bin/nco_event and check that the events are coming into the backup ObjectServer.
- Restart the Master ObjectServer.
- Connect the desktop client to the Master ObjectServer using $NCHOME/omnibus/bin/nco_event and check that the client indicates it is connected to the Master ObjectServer.
- Given on a UNIX/Linux OS that ObjectServer V7.2 is installed but unable to start, determine why the ObjectServer does not start. With emphasis on performing the following steps:
- Check the environment variables $NCHOME.
- Check to make sure that the ObjectServer has been created using $NCHOME/omnibus/bin/nco_dbinit.
- Check to make sure that the entry for the ObjectServer exists in $NCHOME/etc/omni.dat and in the interfaces file.
- Ensure that the port for the ObjectServer is not already in use.
- Ensure that the proper user is starting the object server process.
- Given an OMNIbus installed and the license server and configured, determine why probes do not connect, so that the probes are running. With emphasis on performing the following steps:
- Check probes log file.
- Verify that the probe’s designated objectserver is running.
- Check whether the interfaces file on the probe server is correctly defined
- Verify that the probe server has network connectivity to the objectserver host.
- Check whether any firewall settings are affecting communications
+#Given an OMNIbus installed and the license server is configured, determine why the desktop does not start, so that the desktop is running and connected to the ObjectServer. With emphasis on performing the following steps: - Ensure that X server settings are set correctly.
- Ensure that the ObjectServer to which the desktop is connected is running.
- Given OMNIbus V7.2 has been installed and configured, users are complaining of slow response time, determine the reason for slow event list response, so that the problem can be resolved. With emphasis on performing the following steps:
- Check # of events.
- Check OS profiles.
- Check event rates.
- Check # of desktops.
- Check process on OS server.
- Check resource usage of OS server, memory, CPU, & disk.
- Check network response times.
- Check log files.
- Check automations.
- Check the number of journals and details.
- Determine what other components are connected.
- Given OMNIbus V7.2 has been installed and configured, optimize system performance so that the ObjectServer performance is optimized. With emphasis on performing the following steps:
- Check frequency of triggers.
- Check execution scope of triggers: once only, for each row.
- Check number of details. details($*).
- Check SQL used in trigger for performance.
- Check whether 'update via' is being used.
- Check desktop filters.
Section 5 - Administering - Given a running and verified system, complete post implementation process including system backup, documentation, acceptance testing, so that customer acceptance can be obtained. With emphasis on performing the following steps:
- Backup the installed system.
- Create system environment documentation.
- Verify compliance with customer requirements.
- Knowledge transfer to staff.
- Demonstrate system to client.
- Complete acceptance testing.
- Customer sign-off.
Section 6 - Training - Given new users, provide training, so that users are educated on the new system.
With emphasis on performing the following steps: - Train users and administrators.
This sample test is designed to give the candidate an idea of the content and format of the questions that will be on the certification exam. Performance on the sample test is NOT an indicator of performance on the certification exam and this should not be considered an assessment tool. IBM Tivoli Netcool/OMNIbus V7.2 Implementation Exam #933
Sample Test
Assessment Test:
An assessment test is available for this exam (for a cost of $10 USD) and is designed to
be a predictor of success on the actual exam. To take the assessment test:
1. Visit the IBM Prometric testing Web site (http://ibmtesting.prime.prometric.com/).
2. Select "Secure Sign-in" if you have a Prometric user ID and password. If you do
not, then select "First Time Registration".
3. Enter your Prometric ID and password and click "sign-in".
4. Select "Take Test".
5. From the Step 1 page, look at the "Public Test" area and select "Tivoli
Assessment/Mastery Exams" from the pull-down menu.
6. Select the Assessment/Mastery exam that you would like to take.
Sample Test:
This sample test is designed to give the candidate an idea of the content and format of
the questions that will be on the certification exam. Performance on the sample test is
NOT an indicator of performance on the certification exam and this should not be
considered an assessment tool.
(Answer Key at end)
1. A customer wants to minimize system administration, including ObjectServer
maintenance. The customer is running a high-availability pair of Object Servers.
The customer wants the system configured so that any new users that are added to
the primary ObjectServer will also be added to the failover with the least amount of
manual intervention and in a timely manner.
What is the best technique that can be used to satisfy the customer’s requirements?
A. add entries to the gateway tblrep.def files and map file to enable replication of the
user tables
B. use nco_confpack to extract the user tables from the primary and import them into the
failover
C. create a script to use nco_sql to connect to the gateway and issue REPLICATE
commands to copy the user tables
D. configure TRANSFER commands in the gateway startup.cmd file to copy the user
tables from the primary to the failover
2. What are the default authorization roles available to normal user created in
OMNIbus?
A. AlertsUser, Normal, Public
B. AlertsUser, CatalogUser, ISQLWrite
C. AlertsUser, CatalogUser, ChannelUser.
D. AlertsUser, ChannelUser, DesktopAdmin
E. Every user is assigned ‘Normal’ role by default. 3. To set up OMNIbus 7.2 authorization, security objects should be configured in a
certain order. In which order should security objects be configured?
A. First Users, second Groups and third Roles
B. First Roles, second Groups and third Users
C. First Groups, second Users and third Roles
D. First Groups, second Roles and third Users
4. Omnibus 7.2 provides several default groups. Which default groups are required
by the ObjectServer and cannot be deleted or renamed?
A. Administrator, Public and ISQL
B. ISQL, ISQLWrite and Public
C. Normal, Administrator and System
D. Public, AlertsUser and System
5. During an event storm, 50 events per second were logged in the system log file.
The syslog probe sent 30 events per second to the ObjectServer. What should be
changed to improve probe performance?
A. The syslog probe property StoreAndForward should be set to 1
B. The syslog probe should be configured to read from a named pipe
C. The syslog probe property Buffering should be enabled and adjust BufferSize
property
D. The syslog probe property Mode should be set to Master, and a new syslog probe
should be configured with Mode set to slave.
6. The monitor you are using has to connect to an EMS to retrieve events. The
hostname of the EMS is 'emsserver'. The device listens for connections on port 23.
The monitor is not receiving any events, and the logfile tells you that it cannot log in
on the EMS. How can you manually check this?
A. ssh emsserver
B. telnet emsserver
C. nco_ping emsserver
D. nco_sql -u root -server emsserver
7. Users connected with native desktops to an ObjectServer running on a UNIX
server are complaining about slow response times. You suspect that a misconfigured
automation has generated too many Journal records.
What is the best technique for quickly verifying the total number of Journal records
in the ObjectServer?
A. enable Object Server profiling and check the ObjectServer log file for the total B. start a desktop client, highlight an event record and use the right-click option to select
Journal
C. start a desktop client, and modify the Metric setting on the All Events monitor box to
show total Journal records
D. use the nco_sql utility to connect to the ObjectServer and issue the following
command: select count(*) from alerts.journal; go
8. Which configuration has the greatest effect on ObjectServer response time?
A. Reaper frequency
B. Granularity frequency
C. Deduplication frequency
D. Temporal Trigger frequency
9. What are two properties that need to be set to ensure failover functionality is
enabled for the Netcool OMNIbus Syslog probe? (Choose two.)
A. PeerPort
B. PeerHost
C. SlavePort
D. SlaveHost
E. MasterHost
10. Which rules file code segments shows the proper implementation of a multicolumn
lookup table within a rules file?
A. table upsWellKnownAlarms =
{
{"33.1.6.3.1","UPS Battery Status","4","100041"},
{"33.1.6.3.5","UPS Temperature Status","4","100059"},
{"33.1.6.3.6","UPS Input Status","4","4001"}
}
default = {"UPS Status","4","4001"}
B. lookup upsWellKnownAlarms =
{
{"33.1.6.3.1","UPS Battery Status","4","100041"},
{"33.1.6.3.5","UPS Temperature Status","4","100059"},
{"33.1.6.3.6","UPS Input Status","4","4001"}
}
default = {"UPS Status","4","4001"}
C. 33.1.6.3.1<tab>UPS Battery Status<tab>4<tab>100041
33.1.6.3.5<tab>UPS Temperature Status<tab>4<tab>100059
33.1.6.3.6<tab>UPS Input Status<tab>4<tab>4001
D. 33.1.6.3.1,UPS Battery Status,4,100041 33.1.6.3.5,UPS Temperature Status,4,100059
33.1.6.3.6,UPS Input Status,4,4001
Answer Key:
1. A
2. C
3. B
4. C
5. C
6. B
7. D
8. D
9. AB
10. A Pass4side IBM Tivoli Netcool/OMNIbus V7.2 Implementation 000-933 demo download More Certification exam visit: www.pass4side.com
|
|
The test contains eight sections totalling approximately 60 multiple-choice questions. The percentages after each section title reflect the approximate distribution of the total question set across the sections. Section 1 - Installation / Upgrade (11.5%) - Describe how to install UniVerse v10.2
- Describe how to upgrade UniVerse v10.2
- Describe UniVerse v10.2 account flavors and content
Section 2 - Configuration (13%) - Demonstrate knowledge of Set User Environment & VOC Commands
- Describe how to maintain peripheral devices
- Describe how to manage Shared Memory Structures
Section 3 - File Maintenance (25%) - Identify the file type structures and their uses
- Describe monitoring of files
- Describe the use of file indexing
Section 4 - Performance (18%) - Demonstrate knowledge of how to Start, Stop, and Pause UniVerse
- Demonstrate how to optimize and maintain UniVerse Performance
- Describe various UniVerse System Recovery methods
- Demonstrate knowledge of DB replication
Section 5 - Client Access (8%) - Describe how to install and configure client products
- Describe how to prepare Account for Access
- Describe the process for Establishing Connections
Section 6 - Security (11.5%) - Describe how to control Account and File Access
- Describe how to implement encryption
- Describe the use of user controls
Section 7 - Troubleshooting (13%) - Analyze log files and interpret error messages
- Demonstrate knowledge of troubleshooting commands
- Demonstrate knowledge of process tracking
Test information: - Number of questions: 60
- Time allowed in minutes: 90
- Required passing score: 67%
Assessment Test  | To assess your current skill level and readiness for Test 718 - IBM U2 UniVerse V10.2 Administration, you can take a Web-based assessment test.
Passing this assessment test does not result in achieving a credential. It is designed to provide diagnostic feedback on the Examination Score Report, correlating back to the test objectives, showing how you scored on each section of the test.
For this assessment test, the passing score is 65% and the time provided to take the test is 90 minutes. A $10.00 test fee applies worldwide to each time a test is taken, even if the same test is retaken. VISA, Master Card and American Express credit cards are accepted. To take the assessment test: - Access the Web-based test delivery tool
 Prime. - If you already have an account on Prime, select Secure Sign-In and continue to Take Test. Otherwise select First Time Registration and follow the 2 steps below:
| | Step 1: | If you already have a Prometric ID number enter it into Step 1. If you do not have one, proceed to Step 2. | | | Step 2: | Select the DB2 Information Management Assessment Tests section. Enter your demographic data and 'Submit'. | | | Note: | Choose your username and password that you will use every time you take a test via Prime. Record them for future reference, along with your ID number that Prime generates. |
|
Pass4side IBM U2 UniVerse V10.2 Administration 000-718 demo download More Certification exam visit: www.pass4side.com
|
|
Test information: - Number of questions: 51
- Time allowed in minutes: 90
- Required passing score: 65%
- Test languages: English
Section 1 - Planning - Given vendor documentation, customer documentation, and requirements, validate customer environment, so that customer requirements are fulfilled and TBSM is ready to install.
- Verify Operating Systems
- Verify OS patches
- Verify DNS
- Identify non root login
- Determine disk space
- Determine memory
- Determine failover configuration
- Determine authentication types
- Given business service information, determine which services to monitor, service dependencies, service-affecting events and data, and create a diagram so that all service dependencies are shown.
With emphasis on performing the following tasks:
- Determine the highest-level services to monitor
- Determine what applications, devices, etc. that support the high-level services
- Determine how the lower-level services affect the higher-level services
- Determine what events and/or data affects each service type
- Given TBSM prerequisites, server information, and expected product load information, verify the prerequisites are met, create a deployment plan, so that business objectives are met.
With emphasis on performing the following tasks:
- Ensure the prerequisites for TBSM product are met
- Determine TBSM installation plan (simple or advanced; 1 host, 2 hosts, or 4 hosts)
Section 2 - Installation - Given the installation media and prerequisites for TBSM, install TBSM using the installation program so that all TBSM components are installed.
With emphasis on the following steps:
- Create TBSM user. (Unix: local non root user id with shell capabilities, Windows: user that is a member of the local administrator group, not a user that is a member of the domain administrator group)
- Obtain installation media
- Ensure prerequisites for TBSM product are met
- Run installation program using launchpad.sh (Windows: launchpad.exe)
- Given a running ObjectServer and TBSM server, discover the ObjectServer schema so that TBSM events appear in the ObjectServer.
With emphasis on the following steps:
- Run $NCHOME/bin/rad_discover_schema ObjectServer
- Run $NCHOME/bin/rad_discover_schema OutputObjectServer
- Verify that TBSM events are appearing in ObjectServer
Section 3 - Configuration - Given the customer requirements, service model requirements, product manuals, maintenance schedules, edit log levels and maintenance schedules, verify OMNIbus connection, and configure properties, so that a TBSM server settings are configured.
With emphasis on the following steps:
- Edit log detail levels (RAD_server.props, RAD_policylogger.props, and log4j.properties)
- Edit maintenance schedules using the GUI
- Edit scheduleTime.xml file to delete a maintenance schedule
- Configure properties (Servicetree refresh interval, service model timeout, discriminator field, default
service viewer type) in RAD_sla.props and RAD_av.props.
- Given a Data Source type and the correct Data Source connectivity information, and assuming they exist and work, create a Data Source mapping within TBSM so that external information can affect the status of services in a service model.
With emphasis on the following steps:
- Login to TBSM
- Switch to Service Administration Page
- Click the Data tab
- Click the New button
- Enter the Data Source Settings and connectivity information
- Click Test Data Source
- Save
- Given the query data, a timing interval, and an existing data source name, create a Data Fetcher so that results are returned to TBSM.
With emphasis on the following steps:
- Login to TBSM
- Switch to Service Administration Page
- Click the Data Fetcher tab
- Click the New button
- Enter unique name for data fetcher
- Select the Data Source
- Enter the SQL Query
- Enter the expression for the SQL query
- Set up interval
- Click the View button
- Given access to TBSM, service template and service instance information, configure a service template and service instance so that a service model is displayed.
With emphasis on the following steps:
- Login to TBSM
- Switch to Service Administration Page
- Select Templates tab
- Click New button
- Enter the template settings
- Create template rules
- Save service template
- Switch to Service Administration Page
- Select Services tab
- Click New button
- Enter the service instance settings
- Select service template
- Click on Identification field tab
- Enter field value
- Save service instance
- Given the SSL certificate was created or purchased, TBSM installed, server login information, create SSL Secured Access to the TBSM server so that customer data is protected.
With emphasis on the following steps:
- Security Manager SSL Authentication:
- Login to the SecurityManager server
- Create SecurityManager Server Certificate
- Add the certificate properties to SM_servletservice.props
- Encrypt the keypass password
- Configure SM_server.props
- TBSM SSL Authentication
- Login to the TBSM server
- Create SecurityManager Server Certificate (if different from NCSM)
- Add the certificate properties to server.props
- Configure server.xml
- Given access to TBSM and an existing and configured Data Source, Data Fetcher, and service template, create AutoPopulation rules in a template so that a Service is created automatically.
With emphasis on the following steps:
- Login in to TBSM
- Switch to Service Administration Page
- Click on Templates tab
- Edit the template
- Click Create Auto-Population Rules button
- Enter unique rule name
- Select incoming status rule
- Enter Auto-Population information
- Repeat step 8 for any parent configuration
- Save service template
- Given an existing template and access to TBSM, create rules so that an enriched event can be displayed on the service model.
With emphasis on the following steps:
- Edit template
- Create dependency rule by clicking on Rule tab
- Select outage information
- Save
- Edit template
- Create incoming status rule by clicking on Rule tab
- Determine whether to create good/marginal/bad rule or numerical rule
- Enter the rule settings
- Save
- Edit template
- Given an existing service template, data sources, and product documentation, create a service using ESDA so that the ESDA rule is configured.
With emphasis on the following steps: - Edit template
- Create ESDA rule by clicking on Rule tab
- Determine whether the ESDA is a child or parent rule
- Select Data Source
- Enter SQL query
- Enter expressions field information
- Verify selected template
- Click Enabled
- Given an existing service instance and existing user or group, add security permissions to service instance so that access to view or edit the server instance is restricted.
With emphasis on the following steps:
- Edit service instance
- Click the Security tab
- Select users or groups
- Select privilege
- Save service instance
Section 4 - Customization - Given the customer page template was verified, product documentation, TBSM installed, and admin user defined, create a custom page using customer specified layouts and viewpoints so that a custom page is properly displayed.
With emphasis on the following steps:
- Login to the TBSM GUI with admin user
- Switch to the Adminstration page
- Switch to the layout tab
- Click the add button
- Type in the page name and page title
- Select correct category name and value
- Click add
- Edit the page from the designated view
- Select layout (menu pane, one column, tab pane, three columns, two columns, state-maintained tab pane)
- Select Security ID ( user only, default, admin view only, admins only, user view only)
- Add designated viewpoint (active event list, chartview, iframe example, lightweight event list, mapview, service details, service tree, service viewer, table view, urgent service, version information, end of viewpoints), pane, or view
- Organize viewpoints as specified by the template
- Select decoration as specified by the template
- Save the page
- Given a TBSM install, Admin user defined, service model, product documentation, and canvas template, create a custom canvas in the appropriate way, add and organize indicator icons and decorations, select the background color, and save the canvas so that the custom canvas can be displayed.
With emphasis on the following steps:
- Login to TBSM install with admin user
- Switch to the Service administration page
If the canvas should be tied to an instance: - Display the instance in the service viewer
- Click the create canvas button from the service viewer
If the canvas shouldn’t be tied to an instance: - Click the Custom canvases selector
- Click the Create custom canvas button
- Add the indicator icons as specified by the predefined canvas template
- When adding indicator icons, specify correct rules for each value
- Organize icons on the canvas
- Add and organize decorations
- Select background color
- Save canvas
If canvas is not tied to a service instance, supply name as defined by client
- Given a TBSM install, admin user defined, existing custom page, templates, metric rules, data sources, data fetchers, and product documentation, create a new tree template which defines the templates to be used and data to be displayed so that a custom scorecard is created to display external data.
With emphasis on the following steps:
- Login to the TBSM GUI with the admin user
- Switch to the Service administration page
- From the services selector, click the tree template editor button
- Create a new tree template
- Select the new tree template
- Change sizing for columns to be displayed
- Create the columns to be displayed on the custom scorecard
- Select templates to be used
- For each template, select the user defined metric/incoming status rule or system defined rule
- Relate each rule that is selected to a column on the tree
- Edit the policy to customize what is displayed in the column, such as value being received, or custom icon
- Save the Tree template
- Switch to the custom page where the custom service tree should be located
- Edit the service tree viewpoint
- Select the new tree template and the starting service instance
- Given the client’s custom images, customize the TBSM page header and viewpoint header, as well as the custom service tree icons, so that TBSM displays the customer’s header images. and custom service tree icons.
With emphasis on the following steps:
- Place all custom background header images in the appropriate directory
- Edit the background-image for the file: $NCHOME/guifoundation/webapps/desktop/css/ngf/ngf.css to point TBSM to display new header images in the following sections:
Table.netcool-topheader
Td.netcool-topheader-left
Td.netcool-topheader-right - Edit the background-image for the file:
- $NCHOME/guifoundation/webapps/desktop/css/viewpoint.css to point TBSM to display new viewpoint header images in the following sections:
table.vp_header td.vp_header_left
table.vp_header vp_header_title
table.vp_header td.vp_header_right
- Given the custom icons and defined service model, customize TBSM, so that the client service tree displays custom icons.
With emphasis on the following steps:
- Place all custom icon images in the following directory: $NCHOME/guifoundaiton/webapps/sla/images
- Edit the following policy to change the icon based on the current column by using the tree template
editor in the TBSM GUI.
@Change the VALUE variable for each icon that should display if the column name is customized,
based on the icon that would normally be displayed - Save policy
Section 5 - Operations - Given the dependencies between all four TBSM components, perform correct starting order (1.License Server 2.Omnibus 3.Security Manager 4.TBSM) and stopping order (1.TBSM 2.Security Manager 3.Omnibus 4.License Server) of all four components so that all four components will function properly and will allow for a login to the tbsm console.
With emphasis on the following steps:
- The order of starting TBSM components are:
- Start IBM Tivoli Netcool Common License Server
Unix - $NCHOME/license/bin/nc_start_license
Windows net start NCO Flex License Manager or can start from services panel - Start IBM Tivoli Netcool OMNIBus
Unix - $OMNIHOME/bin/nco_objserv &
Windows net start Netcool/OMNIbus Object Server - Start IBM Tivoli Netcool Security Manager
Unix - $NCHOME/security/bin/ncsm_server &
Windows net start Netcool Security Manager Server - Start TBSM
Unix - $NCHOME/bin/rad_server
Windows - net start Netcool Postgres Database
net start Netcool GUI Foundation Server
- The order of stopping TBSM components are:
- Stop TBSM
Unix - $NCHOME/bin/rad_shutdown
Windows - net stop Netcool GUI Foundation Server,
net stop Netcool Postgres Database - Stop IBM Tivoli Netcool Security Manager
Unix - $NCHOME/security/bin/ncsm_shutdown
Windows net stop Netcool Security Manager Server - Stop IBM Tivoli Netcool OMNIBus
Unix - $OMNIHOME/bin/nco_sql -S NCOMS -U root -P “”
alter system shutdown
go
Exit
Windows - net stop Netcool/OMNIbus Object Server - Stop IBM Tivoli Netcool Common License Server
Unix - $NCHOME/license/bin/nc_stop_license
Windows - net stop NCO Flex License Manager or can stop from services panel
- Given that you have configured a service model, use the rad_sendevent utility to send test events to the TBSM ObjectServer so that one can confirm that the services in the model respond to service-affecting ObjectServer events properly.
With emphasis on the following steps:
- Issue the rad_sendevent command using the following syntax:
rad_sendevent <ObjectServer host> <ObjectServer port> <ObjectServer userid>
<ObjectServer Password or "">
where:
ObjectServer host - Name of host machine running the ObjectServer monitored by TBSM
ObjectServer port - Port number for the ObjectServer monitored by TBSM
ObjectServer userid - The user name needed to access the ObjectServer
ObjectServer Password - Password for the Userid. Enter "" for no password - After issuing the rad_sendevent command, a READY prompt will appear and then type the field name
- Press the enter key
- Type the field value pair on the next line
- Press the enter key again
- When finished typing the field name and value pairs for an event, press the enter key twice.
- Then either send another event, or press the Ctrl-C keys to exit rad_sendevent.
- Given TBSM 4.1.1 is installed and object server is running, modify the OMNIbus schema using the tbsm_db_update.sql file so that the additional fields are now imported to the alerts.status table and an additional table called alerts.service_deps is also added into the schema of the object server.
With emphasis on the following steps:
- Verify the tbsm_db_update.sql file is located in the appropriate directory.
- Modify the OMNIbus Object server schema by issuing the following command:
cat $NCHOME/guifoundation/webapps/sla/install/tbsm_db_update.sql
| $OMNIHOME/bin/nco_sql -server <servername> -user <username>
-password <password>
where:
servername is the name of the ObjectServer you want to create for Netcool/RAD.
username is the Objectserver user name.
password is the Objectserver password.
- Given that a file is manually edited in the $NCHOME/guifoundation/webapps/sla/av/xmlconfig and $NCHOME/guifoundation/webapps/sla/av/css directories, issue the rad_reinitcanvas script so that you see the changes from the tbsm gui without having to restart the RAD server.
With emphaiss on the following steps:
- Edit any file manually within the following directories: $NCHOME/guifoundation/webapps/sla/av/css and $NCHOME/guifoundation/webapps/sla/av/xmlconfig
- Execute $NCHOME/bin/rad_reinitcanvas (Windows: %NCHOME%/bin/rad_reinitcanvas.bat)
- View the service tree to see changes
- Given the desired services, templates, data fetchers, data sources are configured on another TBSM server, perform the exporting and importing of service configuration using radshell function so that services are configured successfully without having to manually create them again.
With emphasis on the following steps:
- On the TBSM server with existing services configured, use the radshell export function
@execute $NCHOME/bin/rad_radshell
@When the prompt changes to radshell>, type export ();
@Press enter
@When finished exporting, then type exit ();
@Press enter (All of the service templates, services, data fetchers, and data sources are now written to a file named export.radsh in the $NCHOME/guifoundation/webapps/sla directory.) - Copy the export.radsh file into the $NCHOME/guifoundation/webapps/sla directory of the
TBSM server you want to import the services to - Import the file into that TBSM server, enter the command: cat export.radsh | $NCHOME/bin/rad_radshell
Section 6 - Troubleshooting - Given Statement: Given a TBSM 4.1.1 install failure on Windows platform with MSIEXEC error 1603 in install logs and a console error ‘Insufficient space in Javaheap to satisfy allocation request’, first uninstall TBSM including removing the %NCHOME% directory and when reinstalling TBSM make sure the pgservice user is created using the correct guidelines so that the TBSM install will not fail due to the rights of the pgservice user.
With emphasis on the following steps:
- Make sure failed install is cleaned up.
- Stop all Netcool Services (must have rebooted since original installation).
- Start > Control Panel > Add or remove programs; select IBM® Tivoli® Business Service Manager (TBSM) and the Change/Remove button.
- Read the information on the Welcome panel and click Next.
- On this panel, all the features that have been installed are selected by default. Select the
features to uninstall and click Next. - Read the listing of features that will be removed. Click Uninstall.
- Read the post-uninstallation summary information and click Finish.
- Reboot the computer after the uninstallation process finishes.
- If all components have been uninstalled, remove the %NCHOME% directory
- Given a TBSM 4.1.1 install failure on Unix platform, and subsequent installation attempts also fail with 'Import of the schema failed', uninstall TBSM using the ‘uninstaller.bin’, delete the file /var/tmp/locknetcool , login as a non-root user and reinstall TBSM so that a successful install is achieved.
With emphasis on the following steps:
- cd $NCHOME/_uninst and run ./uninstaller.bin
- Delete the file: /var/tmp/locknetcool (/var/tmp/locknetcool file remains from a previous installation attempt. License server fails to start and as a result, the OMNIbus Object Server installation also fails (failure to import
schema into the Object Server). - Installation must be done by someone with a non-root userid. The TBSM 4.1.1 installation
program does not support logging in as root and then switching from root to a different userid. If you are logged in as root, logout and then login using a non-root userid. - Re-install TBSM 4.1.1.
- Given an upgrade from TBSM 4.1 to TBSM 4.1.1 on Windows with the TBSM Reports component, out of memory errors occur after you view a few reports and TBSM server stops running, set the registry entries for JVM options for the NCGFServer service executable so that the server should continue running when reviewing reports.
With emphaiss on the following steps:
- Set the registry entries for JVM options for the NCGFServer service executable as follows:
- If it is running, stop the Netcool GUI Foundation Server service.
- To open the Registry Editor, select: Start->Run-> and enter regedit in the window that opens.
- From the Registry Editor, select:
HKEY_LOCAL_MACHINE
-> SOFTWARE
-> Apache Software Foundation
-> Procrun2.0
-> NCGFServer
-> Parameters
-> Java - To see the JVM options, double click on Options in the right-hand column.
- In the Edit Multi-String window, add these parameters:
-XX:MaxPermSize=128m
-XX:+DisableExplicitGC - Start the Netcool GUI Foundation Server service.
Courses and publications are offered to help you prepare for the certification tests. The courses are recommended, but not required, before taking a certification test. If you wish to purchase Web-based training courses or are unable to locate a Web-based course or classroom course at the time and location you desire, please feel free to contact one of our delivery management teams at:
- Americas - tivamedu@us.ibm.com
- EMEA - tived@uk.ibm.com
- AP - tivtrainingap@au1.ibm.com
Please note that course offerings are continuously being added and updated. If you do not see the course(s) below listed in your geography please contact the delivery management team. Classroom Course |
Course title: IBM Tivoli Business Services Manager 4.1 for Implementers
Course duration: 2 days
Course number: TM302
Abstract: IBM Tivoli Business Services Manager (TBSM) helps visualize the health of critical business services and associated SLAs. TBSM enables IT to target resources and actions toward the most critical and costly IT resources and issues, ultimately delivering the greatest impact to the business. In this course you learn how to install and integrate TBSM 4.1 with a variety of service event sources. Additionally, you learn how to build custom dashboards to visualize business service health. | Course title: IBM Tivoli Business Services Manager 4.1 for Administrators
Course duration: 3 days
Course number: TM332
Abstract: IBM Tivoli Business Services Manager (TBSM) helps visualize the health of critical business services and associated Service Level Agreements (SLAs). TBSM 4.1 enables IT to target resources and actions toward the most critical and costly IT resources and issues, ultimately delivering the greatest impact to the business. In this course, you will learn how to develop and build service models and configure service views. Through hands-on exercises, you will use, configure, and administer TBSM 4.1. |
Redbook |
 | Redpaper - IBM Tivoli Business Service Manager V4.1
This IBM® Redpaper leads you through the new Tivoli Business Service Manager V4.1 that is based on Netcool/Realtime Active Dashboard (RAD), instead of the previous Tivoli Business Systems Manager V3.1. This book will describe Tivoli Business Service Manager V4.1 components and architecture. We also discuss function comparison of functions for Tivoli Business Systems Manager V3.1 and Netcool/RAD to Tivoli Business Service Manager V4.1. We documents the installation and migration of Tivoli Business Service Manager V4.1 in our environment. Migration is currently only available for Netcool/RAD 3.0 users. This book also contains integration with IBM Tivoli® Service Management framework that allows Tivoli Business Service Manager to integrates with Tivoli Change and Configuration Management database (CCMDB) using Discovery Library toolkit. This functions is also available for z/OS® configuration. Finally, Tivoli Business Service Manager operational consideration is discussed, includes backup and recovery process; maintenance schedule and some performance tips.
|
IBM Tivoli Business Service Manager V4.1.1 Implementation Exam #436
Sample Test
Assessment Test:
An assessment test is available for this exam (for a cost of $10 USD) and is designed to
be a predictor of success on the actual exam. To take the assessment test:
1. Visit the IBM Prometric testing Web site (http://ibmtesting.prime.prometric.com/).
2. Select "Secure Sign-in" if you have a Prometric user ID and password. If you do
not, then select "First Time Registration".
3. Enter your Prometric ID and password and click "sign-in".
4. Select "Take Test".
5. From the Step 1 page, look at the "Public Test" area and select "Tivoli
Assessment/Mastery Exams" from the pull-down menu.
6. Select the Assessment/Mastery exam that you would like to take.
Sample Test:
This sample test is designed to give the candidate an idea of the content and format of
the questions that will be on the certification exam. Performance on the sample test is
NOT an indicator of performance on the certification exam and this should not be
considered an assessment tool.
(Answer Key at end)
1. On a typical TBSM server running TBSM and Security Manager, what is the
minimum amount of RAM that should be installed ?
A. 1 GB
B. 2 GB
C. 4 GB
D. 6 GB
2. In order to send events from TBSM to an ObjectServer, the applications need
matching schemas. On a Windows server, which holds the default TBSM schemas
that can be used to compare against a schema of an OMNIbus ObjectServer?
A. C:IBMNetcooletc
B. C:IBMNetcoolslainstall
C. C:IBMNetcoolguifoundationetc
D. C:IBMNetcoolguifoundationwebappsslainstall 3. If a rule that uses a Data Fetcher named "xyz" does not seem to be working
correctly, what log files should be checked. Select all that apply. (Choose Two.)
A. ngf.out
B. XYZ.log
C. torque.log
D. RAD_xyz.log
E. RAD_server.log
4. Company XYZ requires SSL to be implemented, when possible, to protect data
transmissions. A SSL certificate has been generated and the credentials have
been given to a user. Which file should the user modify on the TBSM server to
configure the TBSM SSL client credentials?
A. $NCHOME/etc
B. $NCHOME/etc/server.props
C. $NCHOME/etc/rad/server.props
D. $NCHOME/etc/rad/RAD_server.props
5. What does the __serviceinstancename__ refer to when creating an ESDA rule?
A. The value of the service instance name for the seed service instance
B. The value of the service instance name for the child service instance
C. The value of the service instance name for the parent service instance
D. The name of the Service Template for which the ESDA is being created
6. Where are the tree template configurations stored for TBSM 4.1.1?
A. $NCHOME/XMLtoolkit/xml
B. $NCHOME/guifoundation/webapps/sla/xml
C. $NCHOME/guifoundation/webapps/sla/av/xmlconfig
D. $NCHOME/guifoundation/webapps/webtop/tep/templates/
7. In order to export one service named "Payroll" with a serviceID of 365, its service
tempates, and all of its child services and service templates to a file, which
rad_radshell syntax below would be used?
A. export(365);
B. exportStartFromParent("Payroll");
C. exportFromStartingInstance("365);
D. exportFromStartingInstance("Payroll"); Answer Key:
1. C
2. D
3. DE
4. D
5. A
6. C
7. D Pass4side IBM Tivoli Business Service Manager V4.1.1 Implementation 000-436 demo download More Certification exam visit: www.pass4side.com |
|
|
I LIKE
NICE BLOG
|
|
