|
|
|||||||||||||||||||||||||||||
|
Экзамен Tivoli 905 - IBM Tivoli Composite Application Manager for WebSphere v6.1Информация об экзамене:
Программы сертификаций, в треки которых входит данный экзамен:
Разделы экзамена:Раздел 1 - Planning 1. Given customer input and ITCAM for WebSphere architecture, identify what should be monitored, location and configuration of the Managing Server and Data Collectors and the location of the database so that a deployment plan is created. a. Identify the servers to be monitored. b. Identify location for Managing Servers. c. Decide how the Managing Server components will be distributed given customer needs and design requirements. d. Identify if embedded installation of WebSphere Application Server will be performed, or an existing installation will be used. e. Identify if embedded installation of the database will be performed, or an existing installation will be used. 2. Given the installation guide and design requirements, create a Managing Server deployment plan, so that Managing Server installation values can be identified. a. Identify hardware and software requirements b. Identify required ports c. Gather database information - users and home for embedded d. Select file system location e. Take necessary firewall action 3. Given the installation guide and design requirements, create a Data Collector deployment plan, so that Data Collector installation values can be identified. a. Determine silent or interactive installation b. Determine SOAP port c. Determine specific cell/node/server d. Determine installation location 4. Given the architectural differences between WebSphere Application Server on z/OS and distributed platforms, describe how server instances are grouped so that the deployment plan allows for correct Data Collector configurations. a. Describe the differences between WebSphere Application Server (WAS) on z/OS and that on distributed @platform for data collectors b. Describe the differences between z/OS and distributed platforms for server groups. 5. Given a design requirement to use CICS, CICS Transaction Gateway and WebSphere MQ, describe how CICS Transaction Gateway or WebSphere MQ will be used, so that requirements for monitoring composite requests can be written. a. Describe how CICS Transaction Gateway or WebSphere MQ Connect to WebSphere Application Server to CICS. b. Describe how to configure z/OS and Distributed WebSphere Application Server(s) for composite requests. c. Describe how to configure ITCAM for WebSphere for composite requests. 6. Given a design requirement to use IMS, IMS Connect and WebSphere MQ, describe how IMS Connect or WebSphere MQ will be used, so that requirements for monitoring composite requests can be written. a. Describe at a high level how IMS Connect is used for composite requests. b. Describe how to configure z/OS and Distributed WebSphere Application Server(s) for composite requests. c. Describe how to configure ITCAM for WebSphere for composite requests. 7. Given the ITCAM for WebSphere architecture and with the customer's input, create a test plan, so that the installation and configuration of the critical components can be validated. a. Identify the critical components to be tested. b. Identify the base functions to be tested. Раздел 2 - Preconfiguration 1. Given the customer’s design requirements, identify necessary configuration information related to the application server so that ITCAM for WebSphere can be installed as specified in the deployment plan. a. Identify the application server that will be running the monitored applications. b. Identify a WebSphere Application Server for running the Visualization Engine of the Managing Server. c. Identify communication requirements between the Managing Server and the Data Collectors. 2. Given the customer’s design requirements, identify configuration information related to the database so that ITCAM for WebSphere can be installed as specified in the deployment plan. a. Identify the database configuration information. b. Identify database user information. 3. Given a Windows target platform for installing the Managing Server, prepare the system so that the Managing Server can be successfully installed. a. Download Microsoft Windows Services for UNIX (SFU). b. Install SFU. 4. Given the requirements for installing the Managing Server, create the users and configure their environment so that the Managing Server is prepared for installation. a. Configure environment variables b. Configure PATH c. Create and authorize users Раздел 3 - Installation 1. Given a requirement to do an embedded installation, identify the necessary configuration information so that you can install ITCAM for WebSphere Managing Server successfully. a. Identify WebSphere Application Server parameters b. Identify database parameters c. Identify Managing Server parameters 2. Given a requirement to do a non-embedded installation, identify the necessary configuration information so that you can install ITCAM for WebSphere Managing Server successfully. a. Identify WebSphere Application Server parameters b. Identify database parameters c. Identify Managing Server parameters 3. Given the requirements for Managing Server install and values for Data Collector install using either the GUI or silent install, input values so that Data Collector software is installed. a. Identify Managing Server parameters b. Identify WebSphere Application Server parameters c. Identify Data Collector parameters 4. Given the Data Collector was installed with TEMA support, install and configure the ITCAM for WebSphere TEMA so that data can be collected for ITM. a. Install ITCAM for WebSphere application support on the Tivoli Enterprise Monitoring Server. b. Install ITCAM for WebSphere TEMA on monitored system. c. Configure ITCAM for WebSphere TEMA. Раздел 4 - Configuration 1. Given that you want to enable the trap and alert feature, configure ITCAM for WebSphere so that support for SNMP and email (SMTP) alerts is enabled. a. Change appropriate configuration files to enable SMTP email alerts. b. Stop and start appropriate components. c. Modify Managing Server system properties to configure SNMP settings. 2. Given that PDF support for reports is required, configure ITCAM for WebSphere and install the iText package so that PDF support is enabled for reports. a. Obtain and install the iText package. b. Change appropriate configuration files to enable PDF support. c. Restart appropriate components. 3. Given that a web server requires monitoring, configure ITCAM for WebSphere and the Web server so that ITCAM for WebSphere monitors the web server. a. Modify appropriate files to allow ITCAM for WebSphere to monitor the Web server. b. Add the Web server to the list of Web servers that ITCAM for WebSphere monitors. 4. Given the installed Data Collector software, run the Data Collector Configuration Tool so that monitoring can be enabled on the Data Collector. a. Verify that appropriate WebSphere components are started. b. Launch the appropriate program to start the Data Collector Configuration Tool. c. Enter appropriate configuration values. d. Restart appropriate WebSphere components. e. Verify that the Data Collector started correctly. 5. Given the configuration files for the bytecode instrumentation (BCI) on the Data Collector, modify them so that classes can be instrumented for heap, lock, and method analysis. a. Identify the appropriate configuration files that must be modified to instrument classes. b. Modify configuration files to enable specific classes to be instrumented for heap, lock or method analysis. c. Remove appropriate generated configuration files. d. Restart appropriate WebSphere components on monitored system. e. Verify that bytecode instrumentation was enabled for specific classes on Data Collector. Раздел 5 - Administration 1. Given an unconfigured Data Collector, select and apply an existing configuration (or create a custom one) so that the collector is configured. a. Select unconfigured Data Collector. b. Apply the appropriate configuration (J2EE, CICS, custom, etc). c. Create custom data collector configuration to monitor Java classes and packages. 2. Given a Managing Server configuration, create user profiles and server groups so that users have appropriate access to the server groups. a. Create Server Group. b. Associate members and user access. 3. Given design requirements, set up roles and create user profiles so that roles are associated with created users. a. Create users. b. Create roles. c. Assign privileges from list shown. 4. Given proper database authority, maintain the ITCAM for WebSphere database so that obsolete data is purged and the database is reorganized. a. Edit the XML and properties files as needed. b. Execute the datatrim.sh job. c. Reorganize the database. d. Update database statistics. 5. Given a configured Managing Server and server groups, set the Monitoring On Demand level to L1, L2 or L3 or change the schedule associated with the server group to set the monitoring level. a. Set Monitoring On Demand level for specific servers to L1, L2 or L3. b. Create a schedule and assign specific servers to that schedule. 6. Given an installed Managing Server, stop and start components so that components can be managed. a. Use the appropriate shell scripts to start and stop all components b. Use the appropriate shell scripts to start and stop a specific component instance. 7. Given an installed Managing Server, add and remove instances of components so that performance can be optimized. a. Modify the environment to add new instances of specific components. b. Modify the environment to remove instances of specific components. Раздел 6 - Troubleshooting 1. Given an installed and configured Managing Server and Data Collector, work with the log files so that diagnostic information can be found. a. Locate managing server logs. b. Locate data collector logs. c. Locate Visualization Engine logs. d. Locate installation logs. e. Execute gather scripts. f. Locate First Failure Data Capture (FFDC) trace files. g. Use the Log Viewer tool. 2. Given that method level tracing is not showing up as expected, determine the cause and perform basic tuning of ITCAM for WebSphere so that method level information is presented properly. a. Verify (and change if necessary) that bytecode instrumentation is enabled. b. Verify (and change if necessary) that application classes are not being filtered out in the Data Collector configuration. c. Verify the correct level of monitoring and change if necessary. 3. Given an installed Data Collector, determine the changes to the JVM custom properties, custom services, environment entries, change PMI settings and generic JVM arguments so that you can identify the changes made to the Data Collector. a. Find the added generic JVM arguments. b. Find the added custom services. c. Find the added custom (JVM) properties. d. Identify the environment variables. e. Note changes to WebSphere PMI. f. Note changes to the Java Security Policy. 4. Given that the Managing Server is installed, test connection and determine the cause of failures so that the Managing Server connects to the database. a. Select the data source in the WAS Administration Console. b. Test connection from Administration Console. c. Test Kernel database connection. d. Determine cause of failures. 5. Given that the monitored application server does not start, make corrections so that the server starts. a. Confirm generic JVM arguments are correct. b. Correct JVM arguments. c. Restart the application server. 6. Given that the Data Collectors do not show up in the configured or unconfigured list of ITCAM for WebSphere UI, determine cause of failures so that the Data Collectors are listed in the ITCAM for WebSphere UI. a. Confirm and correct the Data Collector properties files. b. Verify and correct if necessary TCP/IP connectivity. c. Restart the application server. Подготовка к экзамену:
|
|