E-mail Password Forgot Password? Sign Up

Top Vendor Included


Testimonials

CertKingdom.com is No1
CertKingdom.com is No1 in sites coz in 50$ I cant believe this but when i purchased the 50$ package it was amazing I passed 5 Exams using Certkingdom guides in one month, " Now I am MCITP Certified" many thanks to Certkingdom Team , Thanks. Samantha R

Exam: 000-011

Certkingdom's preparation material includes the most excellent features, prepared by the same dedicated experts who have come together to offer an integrated solution. We provide the most excellent and simple method to pass your certification exams on the first attempt “GUARANTEED”

Whether you want to improve your skills, expertise or career growth, with Certkingdom's training and certification resources help you achieve your goals. Our exams files feature hands-on tasks and real-world scenarios; in just a matter of days, you'll be more productive and embracing new technology standards. Our online resources and events enable you to focus on learning just what you want on your timeframe. You get access to every exams files and there continuously update our study materials; these exam updates are supplied free of charge to our valued customers. Get the best 000-011 exam Training; as you study from our exam-files "Best Materials Great Results"


000-011 Exam and 4000+ Exam $70 - $50
(you save $20)
Buy Now

Vendor IBM
Certification IBM Certifications
Exam Code 000-011
Exam Title IBM Tivoli Application Dependency and Discovery Manager V7.1 Implementation
No. of Questions 100
Last Updated 09/14/2014
Product Type Q & A with Explanation
Question & Answers Download
Prep. Lab Download
Study Guide Download
Audio Download
Video Download
Test Engine Download
Price $50 - Unlimited life time access Immediate access to 000-011 & 4000+ more exam training tools included in this package
Buy Now
Exams Description

000-011
IBM Tivoli Application Dependency and Discovery Manager V7.1 Implementation

Related certifications:
* IBM Certified Deployment Professional - Tivoli Application Dependency and Discovery Manager V7.1
* IBM Certified Advanced Deployment Professional - IBM Service Management Data Center Management and Transformation 2009
* IBM Certified Advanced Deployment Professional - IBM Service Management Service Delivery and Process Automation 2009
* IBM Certified Advanced Deployment Professional - IBM Service Management Service Delivery and Process Automation V2
* IBM Certified Advanced Deployment Professional - IBM Service Management Data Center Management and Transformation V2

This training will cover

Section 1: Planning
1. Given the IT environment of a customer, review the customers environment, so that that the TADDM pre-requisites have been verified.

With emphasis on performing the following tasks:
1. Acquire customer Hardware and OS hosting preference.
2. Review that the TADDM Hardware is supported.
1. Each TADDM server requires a system with the following requirements:

- 100 GB of available disk space
- 2 - 4 processors with a minimum processor speed of 2 GHz
- 4 - 8 GB of memory
- 4 - 8 GB of swap space on the disk used by the operating systemReview that the OS is supported under the TADDM install document.
3. 4. Review Database OS requirement used with TADDM is supported.
1. IBM DB2 Version 9.1 and Fix Pack 2 for AIX (64 bit), Solaris SPARC (64 bit), Linux on System z (64 bit), Linux x86 (32 bit and 64 bit), and Windows (32 bit and 64 bit) operating systems
2. IBM DB2 Version 8.2 and Fix Pack 10 for AIX (32 bit and 64 bit), Solaris SPARC (32 bit and 64 bit), Linux on System z (32 bit and 64 bit), Linux x86 (32 bit and 64 bit), and Windows (32 bit and 64 bit) operating systems
3. Oracle 9i and 10g
5. Review that the browser is supported for both Product Console UI and Domain Manager UI.
6. Review that the Anchor Server OS and Hardware is supported.
7. Review that the Windows Gateway OS and Hardware is supported.
8. Review the ability to leverage NMAP third party software.
9. On AIX, verify that Unzip has been installed so that the install image can be unzipped.

2. Given a customer representative(s) that is capable and authorized to represent the TADDM project, discuss with them the intended use and reporting needs for the TADDM product, document and address any mismatches appropriately, so that the customers needs have been reviewed.


With emphasis on performing the following tasks:
1. Interview customer representative(s) on their intended use of TADDM.
1. Areas of potential use to investigate include:

- Determine the environments (e.g., test, product) where discoveries will be run.
- Number of server to be discovered, frequency that discoveries will be run, discovery of workstations.
- Integration with existing ITIL processes/tools.
2. - Integration with other data sources, federation. Compare intended use of TADDM with capabilities/function of TADDM, document and address any mismatches appropriately.
2. Interview customer representative(s) on their reporting needs.
1. Compare reporting needs with reporting capabilities of the TADDM product, and if discrepancies are found, document and address any mismatches appropriately.

3. Given SME(s) and/or documentation, determine and document the customer's existing environments that will be discovered and managed with TADDM, so that the customers existing environment has been documented.


With emphasis on performing the following tasks:
1. If System Administrator(s) are available:
1. Determine and document the different operating system types (OS) that are in the customer's environment.
2. Determine and document the number of servers for each OS type that will be discovered in each environment (e.g., test, production) where discoveries will be run.
3. Discuss how TADDM works, what the credential requirements for computer systems are, and begin the process to manage and obtain credentials.
4. Discuss requirement for List Open Files (LSOF).
5. Discuss WMI requirements for Windows discovery.
2. If Network SME(s) are available:
1. Determine and document the types of network equipment that are in the customer's environment.
2. Determine and document the number of each type of network equipment that will be discovered in each environment (e.g., test, production) where discoveries will be run.
3. Determine and document firewalls in the customer's environment.
4. Discuss how TADDM works, what the credential requirements for network equipment are, and begin the process to manage and obtain credentials.
3. If Business Application SME(s) are available:
1. For each business application to be managed via TADDM, determine the various servers/components/applications that compose the business application.
2. Discuss how TADDM works, what the credential requirements for components/applications are, and begin the process to manage and obtain credentials.
3. If system diagrams, network diagrams, and/or application architectural documents/diagrams are available:
4. Review the available documents and determine and document: OS types and number of each OS type in the environments to be discovered, types of network equipment and number of each type in the environments to be discovered, business applications and servers/components/applications that compose each business application.
4. Note: The creation of credentials should be started as soon as possible, so they are available prior to discoveries being run.

4. Giiven a customer's environment, determine the best estimate of the number of TADDM components required, so that the initial architecture plan for the deployment has been created..


With emphasis on performing the following tasks:
1. Determine which authentication and security protocols are in use.
2. Determine if machines exist behind firewalls to determine need for anchor servers and windows gateways.
3. Determine the number of assets to be managed.
4. Estimate the number of configuration items to be created.
5. Estimate the number of computer systems to be discovered.
6. Determine the number of domains and enterprise server that are required for each environment monitored by TADDM.

5. Given that Customers would like to connect to an LDAP, options for the use of ITDS and AD must be explained, so that the customer understands their option with the use of LDAP.


With emphasis on performing the following tasks:
1. Find out if customer is looking into having TADDM authenticate to an LDAP.
2. Explain that TADDM supports ITDS directly.
3. Explain that TADDM supports Active Directory using vmm configuration (WebSphere federated repository).
4. Explain that ITDS is configured with Users and User Groups.
5. Configure Users and User Groups TADDM access in the TADDM Domain Manager.
6. Configure several security-related properties in the $COLLATION_HOME/etc/collations.properties file.
7. Secure Socket Layer (SSL) not supported.

6. Given the customer's data source requirements, analyze the requirements to determine if Discovery Library Adapters (DLA) are necessary and a method to import and export data to/from TADDM, so that the customer's environment has been evaluated for DLA requirements.



With emphasis on performing the following tasks:
1. Review TADDM functionality with Environment Owner.
2. Determine which data sources having data to be exchanged with TADDM.
3. Determine which database types are being used.
4. Determine which data sources already have DLA written.
5. Determine requirements for frequency of data loads via the DLA.
6. Determine methodology for developing a new DLA if one does not exist.

7. Given a list of computer systems/components/applications that will be discovered, create a list of TADDM sensors that will be run, so that a list of sensors and any required credentials has been created.


With emphasis on performing the following tasks:
1. Review the list of computer systems/components/applications to be discovered and document which ones TADDM uses sensors to discover.
2. Of the sensors in the list, document which ones require credentials to run.
3. Work with the customer to get the process to manage and obtain credentials started.

8. Given that TADDM defines the different levels of discovery, it is critical to understand their data needs and then explain the customers the different levels and the options that are available, so that the customer understands the three levels of discovery available within TADDM.


With emphasis on performing the following tasks:
1. Understand what the customer needs for discovery and explain what each discovery levels are available and how it can be matched by creating different discovery profiles.
2. Level 1 Profile/Discovery:
1. Level 1 profile is designed to perform credential-free discoveries.
2. The default purpose is to discover and create Computer Systems inventory from a defined set of host, range, and/or subnet of IP addresses scope.
3. The main senor that is run is the StackScanSensor. This will gather very basic information from the discovered Computer Systems.

4. - UNIX: For StackScanSensor to execute, must include the user id into the sudoers file, example for the TADDM Domain/Anchor Server owner id of taddm: taddm ALL= (ALL) NOPASSWD: ALLWhen used with Nmap (must be installed separately on the TADDM and Anchor Servers), much more detailed information will be retrieved with a higher discovered OS confidence level.
3. Level 2 Discovery:
1. This Level 2 profile is only used to discover host with credentials.
2. This Level 2 profile includes the Level 1 profile with the OS credentials which are entered in the Access List for all the targeted machines (Solaris, Linux, Windows, etc) along with a number of additional Computer System Sensors that will run. This is still a more of an inventory discovery with minimum discovered dependencies (TCP only connections).
4. Level 2 Discovery with shallow application discovery :
1. This is an enhanced Level 2 discovery scan that will also capture shallow application objects without application credentials. With this variable set to true, a CustomAppServer object representing the application running on the target machine will be recieved. This will also build limited application dependencies as they are discovered.
2. Set this variable: com.collation.internalITemplatesEnabled to true in the collation.propreties file.
5. Level 3 Discovery:
1. This Level 3 profile is used for deep-dive discovery (includes all of Level 2)
2. This profile can be used to discover the entire application infrastructure, deployed software components, physical servers, network devices, virtual LAN, and host data used in a runtime environment. This discovery requires credentials for all deep dive discoveries sensors that are delivered with TADDM product. This level will also discover applications that do not require credentials for custom templates that are also delivered with TADDM product. This will build dependencies of all applications as they are discovered and have sensors for.
6. Other Discovery Profiles:
1. Any of these profiles (Level 1-3) can be cloned and modified according to your needs. New profiles can be created
2. These new profiles can clone sensors with the ability of modifying parameters and/or remove sensors for discoveries via the Product Console.

9. Given the need to exchange data between TADDM and other application(s), describe the purpose and use of the Common Data Model by TADDM, so that the customer understands the purpose and use of the Common Data Model in modeling customer data.


With emphasis on performing the following tasks:
1. Describe the purpose of the Common Data Model.
1. To facilitate sharing of data among multiple applications
2. To provide a common means of describing objects and relationships in IT environments
3. To provide a common format (IDML) for sharing the data through files
2. Describe the use of the Common Data Model.
1. Use the CDM website contained in the SDK of TADDM (installed with product)
2. Leverage the schema definitions in writing the code to create IDML files
3. Define relationship in the context of the Common Data Model.
1. Relationships consist of a target and source in an IDML file
2. Target and source must be defined in the file prior to defining the relationship


Section 2: Installation

1. Given the proper access administrator authority for a designated anchor server, log into the anchor server and create a service ID and on Windows, configure WINSSHD that will be used for discovery behind firewalls, so that a service account has been created that will be used by the anchor server for discovery behind the firewall.


With emphasis on performing the following tasks:

1. For UNIX/Linux - log into the designated anchor server with root user authority.
2. Use the following commands to create the service account: (Example User Id is coll)

- mkdir -p /export/home/coll
- useradd -G sys -d /export/home/coll -s /bin/sh -c "Service Account" -m coll
3. - chown -R coll /export/home/coll For Windows - log into the designated anchor server with administrator user authority and use the following procedure to create the local service account:
1. Create a user who is a member of the local administrator's group.
4. Use the following procedure to create the local service account if a domain ID is used: (Example User Id is itaddm in domain LAB2)
1. Create a virtual group named itaddm.
2. From the WinSSHD control panel, click Settings  Edit  View  Settings.
3. Select Access Control in the navigation tree pane.
4. Select Virtual Groups.
5. Click Add.
6. Complete the following fields:

- In the Group field, type ittaddm.
- In the Windows account domain field, type LAB2.
- In the Windows account name field, type ittaddm.
- Click Login allowed.
7. - Keep the default values for the remaining fields.c. Create a virtual account called itaddm.

- Type itaddm as your virtual account name.
- Click Virtual account password and set the password.
- Click Use default Windows account.
- Keep the default values for the remaining fields.
2. Given the proper access administrator authority for a designated TADDM database server, and access to the make_ora_user binary for Oracle, log into the server and create the database IDs, so that the necessary User ID for the TADDM database have been created.


With emphasis on performing the following tasks:

1. For UNIX/Linux using Oracle - log into the designated database server with root user authority.
1. From the product DVD, copy the following file to system where Oracle is installed: support/bin/make_ora_user.sh
2. Log in as the Oracle user or, if known, use the user ID that was used to install the Oracle database.
3. Run the file with the following command: make_ora_user.sh
2. For Windows operating systems, complete these steps:
1. Log in as a user who is a member of the ORA_DB group. User IDs in the ORA_DB group have the authority to access the Oracle database.
2. From the product DVD, copy the following file to the remote Oracle database: supportinmake_ora_user.bat
3. Run the file with the following command: make_ora_user.bat
3. Using the Oracle Admin GUI on Windows, Linux, Solaris, AIX, and Linux on System z operating systems grant both the primary and secondary user IDs the following roles:
1. CONNECT
2. RESOURCE
3. SELECT_CATALOG_ROLE
4. CREATE ANY VIEW
5. SELECT ANY TABLE
6. CREATE MATERIALIZED VIEW
4. When using a remote DB2 database, complete the following steps on the system where the DB2 server is installed:
1. Create the secondary DB2 system user ID, the archive user. (There is no need to create the primary DB2 system user ID because this ID is created during the installation process.)
2. Add the archive user to the DB2 group of the DB2 instance owner. (By being in the same DB2 group with the DB2 instance owner, the archive user has permission to access the database.)

3. Given a supported computing environment (hardware, operating system, and installed database), install TADDM using either the installation wizard or in silent mode so that a running TADDM server is available.


With emphasis on performing the following tasks:
1. Install TADDM (GUI)
2. Log in to the server on which TADDM is to be installed
1. For Windows operating systems, use a Windows logon ID with Administrator authority.
2. For Linux, Solaris, AIX, and Linux for System z operating systems, use either a root or non-root user ID.
3. Insert the product DVD or transfer the image files to the server for TADDM installation
4. Open a command prompt window, navigate to the CD drive, and enter one of the following commands:
1. AIX: setupAix.bin
2. Linux: setupLinux.bin
3. Linux on System z: setupLinux390.bin
4. Solaris: setupSolarisSparc.bin
5. Windows: setupWin32.exe
5. A Welcome page is displayed. Click Next.
6. The Software License Agreement page is displayed. Select the "I accept both the IBM and the non-IBM terms." radio button and click Next.
7. Verify the location for the server. Click Next.
8. Type the user name that you want to use to run the server.
1. Windows only - The user must belong to the Administrators group. If the user does not exist or is not part of the Administrators group, there is a check box that you can select to create the user or add the user to the Administrators group.
2. Linux, Solaris, AIX, and Linux on System z only - The user ID must be non-root.
3. Windows only - Type the password associated with the user name typed in the previous step. Click Next.
9. Select Advanced. Click Next.
10. A page requesting the type of server that you want to install is displayed. Select TADDM server if you want only one server. Click Next.
11. A page requesting information about ports for the server is displayed. Verify the Web server port number, Web server SSL port number, GUI server communication port number, GUI server communication SSL port number, JNDI port number, RMI port number, topology manager communication port number, topology builder port number, RMID port number. Click Next.
12. Verify the security manager port number, topology manager port number, API server port number, change manager port number, report server port number. Click Next. The ports are validated.
13. Type the name for the RMI server host name. The default for this field is default.
14. Select the platform binaries you want to install.
15. Select local as the mode for the Discovery Manager Server.
16. To start the server when the system starts, select the Start the server at system boot radio button.
17. To start the server after the installation process is complete, select the Start the server after install radio button.
18. Click Next. A page requesting optional information is displayed. Click Next.
19. The database type page is displayed.
1. DB2

- Select the DB2 radio button. Click Next.
2. - A page with DB2 database configuration information is displayed. Verify the host name, port, database node name, database name, user ID and password, secondary user ID and password for the database. Click Next.Oracle

- Select the Oracle radio button. Click Next.
- A page with Oracle database configuration information is displayed. Verify the host name, database port, Oracle SID, Oracle user ID and password, additional database user ID and password for the database. Click Next.
- A page requesting more information for the Oracle database configuration is displayed. Complete the following steps:
- Verify the name for the Oracle SYS user. The SYS user is the owner of the database and the owner of the data dictionary.
- Type the password for the Oracle SYS user.
- Verify the Oracle connect as role.
- Type the directory for the Oracle home.
- Windows:
- Open a command prompt window.
- Type regedit.
- Go to HKEY_LOCAL_MACHINESOFTWAREORACLE.
- Search for ORACLE_HOME under the subnodes (below this node). The value of the variable is the Oracle home directory. Click Next.A page with the user registry options is displayed. Select the corresponding radio button to use a file-based registry.
20. 21. Click Next. A summary page is displayed.
22. Review the summary information and click Install.
23. After the installation completes successfully, a page, indicating a successful installation, is displayed. Click Finish to close the installation program.
24. Silent install.
25. Copy the response file to the system on which TADDM is to be installed into the temp directory.
26. Log in to the server on which TADDM is to be installed
1. For Windows operating systems, use a Windows logon ID with Administrator authority.
2. For Linux, Solaris, AIX, and Linux for System z operating systems, use either a root or non-root user ID.
27. Insert the product DVD or transfer the image files to the server for TADDM installation
28. Open a command prompt window, navigate to the CD drive, and enter one of the following commands:
1. Linux: setupLinux.bin -options /tmp/install.rsp -silent -is:log /tmp/install.log
2. Solaris: setupSolarisSparc.bin -options /tmp/install.rsp -silent -is:log /tmp/install.log
3. AIX: setupAix.bin -options /tmp/install.rsp -silent -is:log /tmp/install.log
4. Linux on System z: setupLinux390.bin -options /tmp/install.rsp -silent -is:log /tmp/install.log
5. Windows: setupWin32.exe -options c: emp install.rsp -silent -is:log c: empinstall.log

4. Given a potential Windows gateway, verify that the WinSSHD or Cygwin is installed and configured correctly, so that the Windows server can receive SSH requests.


With emphasis on performing the following tasks:
1. Log into the Product Console.
1. Add Windows Gateway ssh user and password under Computer System
2. Add a Windows target service user id under the Computer System (Windows)
2. Log into TADDM Server as the TADDM owner.
3. Change into the following directory: ${COLLATION_HOME}/support/bin.
4. Execute a test command on the gateway host using SSH.
1. UNIX: testssh.py
2. Windows: testssh.bat
5. Execute a test command to verify that WMI is installed on the gateway system.
1. UNIX: testwmi.jy
2. Windows: testwmi.bat
6. Execute a test command on a target Windows-based system.
1. UNIX: wmiexec.jy
2. Windows: wmiexec.bat


Section 3: Configuration

1. Given the host name(s) or TCP/IP address(s) of a server(s), a working TADDM server and access to the product console, using either the UI or command line add a Scope Set with the machine(s) configured so that the machine(s) can be discovered.


With emphasis on performing the following tasks:
1. Navigate to the product console user interface.
2. Open the Discovery tab.
3. Select the "Scope" ICON.
4. Select the "Add Set" button at the bottom left.
5. Input the Name of your Scope Set and select "OK".
6. Select the Newly added Scope Set and select the "Add" button
7. In the Add Scope pop-up, select "Host" in the pull down.
1. The Options are to add Address Ranges, or Subnets
8. Input the TCP/IP address, or the Hostname in proper fields and select "OK"
1. For Ranges add TCP/IP ranges and select "OK"
2. For Subnets, add the subnet range and select subnet mask, and select "OK"
9. Login to the TADDM server and change the directory to $COLLATION_HOME/bin.
10. Using an editor, create a scope file with the proper information - < scope, [exclude_scope:exclude_scope...],[description] >
1. A scope file can contain any number of scopes, using any combination of the following scope types:
2. Subnet scopes (for example, 1.2.3.4/255.255.255.0)
3. Address scopes (for example, 1.2.3.4)
4. Range scopes (for example, 1.2.3.4-5.6.7.8)
5. Note: The following details about the scope file format:

- Only IP addresses are valid in the scope file. Host names can not be used.
- Each scope element resides on a separate line.
- Address scopes should not include exclusions.
- Comment lines can be inserted prefixed with the number sign (#).
6. - Entries are ignored if they are not valid.The following sample text is a sample scope file:

- 10.10.10.10,,
- 10.10.10.20,,
- 10.10.10.30,,
- 10.10.10.0/255.255.255.0,10.10.10.2:10.10.10.3,
- 10.10.10.2-10.10.10.9,10.10.10.4:10.10.10.5,
- 10.10.10.88,,
- 10.10.10.999,, xecute loadscope.jy -u -p -s ScopeName load .
11.

2. Given that TADDM and DB2 have been installed, perform the initial tuning of the DB2 database, so that DB2 performance has been optimized.


With emphasis on performing the following tasks:
1. Bufferpool: The default bufferpool size must be increased as the data volume grows.

ALTER BUFFERPOOL IBMDEFAULTBP SIZE 90000;
ALTER BUFFERPOOL BUF8K SIZE 10000;
ALTER BUFFERPOOL BUF32K SIZE 3000;
Update the database configuration for TADDM using the following settings:
UTIL_HEAP_SZ 5000
LOGBUFSZ 1024
SORTHEAP 2048
2. PCKCACHESZ AUTOMATIC;UPDATE DBM CFG USING HEALTH_MON OFF:

3. This parameter was on and causes the DB2 database to perform database maintenance activities, for example, REORG and RUNSTATS, automatically. It looks like the RUNSTATS utility was run when many of the tables were empty and the catalog statistics showed they had 0 rows. During the sync, many of the SQL statements were doing table scans because of this, and many of them had thousands of rows in them.The RUNSTATS utility should be run after a bulkload or small sync. The utility should also be run on all tables after the first sync with each domain.

-Xmx2048M;-Xdisableexplicitgc;-Xk15000
1. Disabling explicit garbage collection is recommended for the IBM JVM. -Xk is the kCluster setting and is helpful to reduce fragmentation in the heap. This can lead to out of memory conditions.

3. Given the username and password for access to machines, a working TADDM server, and access to the product console, navigate to the product console user interface and add an access credential so that Configuration Items can be discovered.


With emphasis on performing the following tasks:
1. Navigate to the product console user interface.
2. Open the "Discovery" tab.
3. Select the "Access List" ICON.
4. Select the "Add" button at the bottom
5. Select the "Computer System" option in the Component Type pull down.
1. Other options include: Windows Servers, Application Servers, Database Servers, LDAP, SNMP, SAP, etc.
6. Input the Name of your Access List, Username, Password and Confirm Password in Access Details Dialog Box.
7. Select the Scope Limitation folder and select your scope options if necessary.
8. Select the "OK" button at the bottom to complete.

4. Given the host name or IP address of a configured gateway, a running TADDM server and access to the product console, navigate to the product console user interface and define a gateway or anchor server, so that the gateway or anchor server can be used for discoveries.


With emphasis on performing the following tasks:
1. Navigate to the product console user interface.
2. Open the Discovery tab.
3. Select the Anchors and Gateways.
4. Select the Add button at the bottom left.
5. Select Gateway from the drop down menu. To add a anchor server, select Anchor from the drop down menu.
6. Input the either the hostname or IP address of the gateway to be defined.
7. Select one of the many scopes if one is required.
8. Click OK.

5. Given the information required to add/edit/delete/move a Custom Server Template, a running TADDM, server and access to the product console, navigate to the product console user interface and add/edit/delete/move a Custom Server Template as appropriate, so that the Custom Server Templates have been completed properly.


With emphasis on performing the following tasks:
1. Open the Discovery tab.
2. Select the Custom Servers icon.
3. If adding a new Custom Server Template:
1. Click "Add", the Custom Server Details notebook is displayed.
2. Click on the General Info and Criteria tab and enter General Server Information (Name, Type, Action, check/uncheck Enabled box, and select Icon).
3. Enter the Identifying Criteria.
4. Click on the Config Files tab:

- To add a config file, click on the Add button, and enter the information in the Search Path for Capture File dialog.
- To edit an existing Config File entry, select the config file to be edited, click on the Edit button, and enter the information in the Search Path for Capture File dialog.
- To delete an existing Config File entry, select the config file to be edited, click on the Remove button.
- To save the setting in the Custom Server Template, click "OK". If editing an existing Custom Server Template:
4.
1. Click on/highlight the Custom Server Template being edited and click the Edit button.
2. Click on the General Info and Criteria tab and make the appropriate changes.
3. Click on the Config Files tab:

- To add a config file, click on the Add button, and enter the information in the Search Path for Capture File dialog.
- To edit an existing Config File entry, select the config file to be edited, click on the Edit button, and enter the information in the Search Path for Capture File dialog.
- To delete an existing Config File entry, select the config file to be edited, click on the Remove button.
- To save the setting in the Custom Server Template, click "OK".If deleting an existing Custom Server Template:
5.
1. Click on/highlight the Custom Server Template being deleted and click the Delete button.
2. Click on Yes on the Conform Deletion popup.
6. If creating a copy of an existing Custom Server Template:
1. Click on/highlight the Custom Server Template being copied and click the Copy button.
2. Enter the name of the new Custom Server Template in the Set Name dialog.
3. Click the OK button.
4. Follow the "If editing an existing Custom Server Template" steps to make the required changes to this new Custom Server Template.
7. To change the order an existing Custom Server Template appears in the list:
1. Click on/highlight the Custom Server Template being moved and click on the Move Up or Move Down buttons as appropriate.

6. Given the information required to add/edit/delete a Application Template, a running TADDM, server and access to the product console, navigate to the product console user interface and define Application Templates, so that Application Templates have been added/edited/deleted as appropriate.


With emphasis on performing the following tasks:
1. Navigate to the product console user interface.
2. Open the Discovery tab.
3. Select the Application Templates icon.
4. If adding a new Application Template:
1. Click "Add", the Create Application Template notebook is displayed.
2. Click on the General tab and enter Name and Admin Info.
3. Click on the Criteria tab, and from the Available Server list, select the servers to be included in the Application Template. To include the selected servers, click on the ">>" button.
4. To save the setting in your Application Template, click "OK".
5. If editing an existing Application Template:
1. Click on/highlight the Application Template being edited and click the Edit button.
2. Click on the General tab and edit Admin Info if applicable.
3. Click on the Criteria tab.

- To add servers to the Selected Server list, select the server(s) from the Available Server list and click on the ">>" button.
- To remove servers from the Selected Server list, select the server(s) from the Selected Server list and click on the "<<" button. To save the setting in the Application Template, click "OK".
6. 7. If deleting an existing Application Template:
1. Click on/highlight the Application Template being deleted and click the Delete button.
2. Click on Yes on the Conform Deletion popup.

7. Given admin access to a working TADDM server, and access to the domain user interface, create domain or enterprise User IDs, so that TADDM User IDs have been configured for use.

INPUTS/DEPENDENCIES: TADDM Admin User ID, Working TADDM Environment, Domain UI.

With emphasis on performing the following tasks:
1. Login to the domain user interface with an admin ID.
2. Under the "Administration" tab on left, select "Users".
3. In the Users Dialog box, select "Create User".
4. Input the Username, Email Address, Password, Confirm Password and Session Timeout value in the General Information Dialog Box.
5. Select the proper role assignment under the Role Assignment Dialog Box.
6. Select the proper access collection under the Role Assignment Dialog Box.
7. Select the "Create User" button at the bottom to complete.
8. NOTE: If using Enterprise Domain, a Sync must be run for the Domain that the ID was created for.

8. Given a business application and the list of servers/components/applications that compose the business application, create the appropriate application descriptor files and deploy them to the appropriate directories on the servers where discovery will be done, so that discoveries have been run and it has been verified that the business application has been built correctly.


With emphasis on performing the following tasks:
1. Create the optional base application descriptor for the business application if you need to define general information about the business application:
1. Using an editor, create the base-app-descriptor file using the example in the TADDM 7.1 User's Guide.
2. Store the base application descriptor file in the appropriate directory on one of the servers that is part of the business application.
2. For each component/application that is part of the business application:
1. Using an editor, create the component application descriptor file using the example in the TADDM 7.1 User's Guide.
2. Save the component application descriptor file in the appropriate directory on the server where the component runs (e.g., in the $root_dir/appdescriptors directory on the WebSphere server).
3. Run discovery and view the results to verify that the application descriptors are setup correctly.

9. Given that TADDM requires WMI files on a gateway and target Windows, a few small WMI files are pushed onto the targeted Windows machine and WMI restarts, so that WMI is available on the gateway(s) and target machine(s).


With emphasis on performing the following tasks:
1. During the initial Level 2 discovery, small set of files will be pushed to the Windows target machines.
1. The following files comprise the WMI provider and are located on the TADDM server in the ${COLLATION_HOME}/dist/lib/ms/gateway directory and pushed to the Windows Gateway and targeted Windows machine (%SystemRoot%System32wbem).

- TaddmWmi.dll - This is the actual WMI provider that will be registered. It in turn runs TaddmWmi.exe.
- TaddmWmi.mof - Specifies what new WMI methods are provided by the provider (TaddmWmi.dll)
- TaddmWmi.exe - Called by the TaddmWmi.dll WMI provider to run a command.
- TaddmPortMap.exe - Only copied if the endpoint is Win2000. Provides functionality similar to netstat
- aports.dll Only copied if the endpoint is Win2000. Used by TaddmPortMap After the files are deployed, WMI on all Windows target and gateway will be restarted.
2. 3. WMI will also be restarted after a communication failure. These are configurable in the collation.properties.
1. Restart WMI if a WMI error is encountered during AutoDeploy

- com.collation.RestartWmiOnAutoDeploy=true
2. - com.collation.RestartWmiOnAutoDeploy.1.2.3.4=true Restart WMI if a WMI error is encountered (except during AutoDeploy)

- com.collation.RestartWmiOnFailure=true
- com.collation.RestartWmiOnFailure.1.2.3.4=true


Section 4: Discovery

1. Given a list of initial business applications to be discovered, the list of servers the application runs on, and the approved project plan, assure the work fits into the defined project scope and if it does, define a phased plan to discover the servers and the components on those servers, so that scopes have been defined for discovering the servers that the initial list of business applications runs on and the components on those servers.


With emphasis on performing the following tasks:
1. Compare list of initial business applications to be discovered and the list of servers the applications run on to the scope of work defined in the approved project plan. If everything fits in the scope of work defined in the project plan, proceed. If not, work with the customer to reduce the list of initial business applications to be discovered and the list of servers.
2. Develop phased plan for discovering the servers in the list of servers the applications run on.
3. Develop scopes to implement the phased plan for discovering the servers.

2. Given a list of servers and components/applications to be discovered, determine which sensors are required to discover the servers/components/applications. Document the credentials required for the sensors and submit requests for the credentials using the customer's process for requesting credentials; and track each request escalating any request that is not completed by the specified completion date, so that credentials have been created on the requested servers/components/applications.


With emphasis on performing the following tasks:
1. From the list of servers/components/applications that need to be discovered, determine which sensors need credentials to run successfully.
2. For each sensor that requires credentials, document the credential requirements.
3. Work with customer's process for requesting credentials; document each credential request as the request is submitted. Include in the document when the request is scheduled to be completed.
4. As credential requests are completed, update credential requirements document and enter the credentials in the product.
5. If the documented completion date for any credential request expires, use the customer's process to escalate the request.

3. Given an existing scope and discovery profile to use, run a TADDM discovery using the user interface or the API. Scan the discovery log/messages and handle any errors as appropriate, so that a discovery has been run using the API or User Interface.


With emphasis on performing the following tasks:
1. Determine whether discovery will be done using the UI or API.
2. If discovery is to be done using the UI:
1. Navigate to the product console user interface, or UI.
2. Open the Discovery tab.
3. Select the Overview icon.
4. Click on the "Run Discovery" button.
5. Select the scope to run discovery on.
6. Select the discovery profile to use for this discovery.
7. Click "OK", discovery will begin.
8. Scan discovery log for any errors and handle any errors as appropriate.
3. If discovery is to be done using the API:
1. Logon to the TADDM server, and navigate to the $COLLATION_HOME/sdk/bin directory.
2. Enter the command "api.sh -u -p discover start" with the appropriate command parameters, such as scope element(s) and profile name.
3. Scan discovery message for any error message, handle any errors as appropriate.

4. Given a customer representative capable and authorized to discuss the Unknown Servers report and to advise on definition of customer server templates, a running TADDM server and access to the product console, navigate to the product console user interface, generate the Unknown Servers report, and create Custom Server Templates as appropriate, so that Custom Server Templates have been defined.


With emphasis on performing the following tasks:
1. Navigate to the product console user interface, or UI.
2. Open the Analytics tab.
3. Select the Inventory icon.
4. Check the Unknown Servers check box and click on the "Run Report" button. Report Notification dialog will popup stating that this operation may take a long time and asking if you wish to continue. Click Yes.
5. Discuss the Unknown Servers report with the customer representative and decide which custom servers need to be defined.
6. For each customer server template that needs to be defined from the Unknown Server report:
1. Click on/highlight in the Unknown Server report the unknown server that needs a customer server defined and click on the Create Custom Server button. The Custom Server Details notebook is displayed.
2. Click on the General Info and Criteria tab and enter General Server Information (Name, Type, Action, check/uncheck Enabled box, and select Icon).
3. Enter the Identifying Criteria.
4. Click on the Config Files tab:

- To add a config file, click on the Add button, and enter the information in the Search Path for Capture File dialog.
- To edit an existing Config File entry, select the config file to be edited, click on the Edit button, and enter the information in the Search Path for Capture File dialog.
- To delete an existing Config File entry, select the config file to be edited, click on the Remove button.To save the setting in your Custom Server Template, click "OK".
7.

5. Given a valid IdML file for loading, a running TADDM server and access to the server running TADDM, use the loadidml script to populate the TADDM database, so that the information contained in the IDML file is loaded into the TADDM database.


With emphasis on performing the following tasks:
1. Transfer the file to the TADDM server or make it available through a network share or other means.
2. Log in as the user that starts and stops the TADDM server. Open a terminal window (UNIX) or command prompt (Windows).
3. Navigate to the home directory of the TADDM installation.
4. Issue the command to load the contents of the file where the -h, -u, -p flags specify the hostname, user name, and password to connect to the TADDM server.
1. Windows platform: distinloadidml -f -h -u -p
2. UNIX / Linux platforms: dist/bin/loadidml.sh -f -h -u -p
5. Confirm the load through the TADDM console UI.

6. Given that a few displayed Status are available during discovery and history, explain the status messages, so that the status message displayed during discovery and history have been explained.


With emphasis on performing the following tasks:
1. Log into the Product Console. Run a Discovery and view the Discovery Overview, or after Discovery completion, view History.
2. View the current Status of the sensor. Values that can be displayed are done, in progress, error or warning.
3. Define done as a successful sensor completion.
4. Define in progress as the sensor is still analyzing the target application, computer system or network devices.
5. Define error as an unsuccessful sensor completion, it can also indicate that previous sensors did not run for one reason or another and caused this sensor to run and fail.
6. Define warning as all critical functions in the sensor completed successfully. Warnings would include things like certain configuration files were not located or did not have permission to open files or run commands.
7. Define Description and Information as a light status description of what the sensor is doing and final description result.


Section 5: Problem Determination

1. Given the need to debug Sensors more efficiently and effectively, set the SplitSensor option, so that a clear view of each sensor is available.

SUBTASK(S):
1. In the $COLLATION_HOME/etc/collation.properties file the parameter com.collation.discover.engine.SplitSensorLog=true must be set to true. This will spawn a directory in the $COLLATION_HOME/log/sensors.
1. Restart TADDM if the file is changed.
2. In that directory there will be individual logs with the name of the sensor and the IP Address of the machine.
3. Setting this option will break down the logs by sensor into a separate directory called sensors. Each sensor will spawn a separate log for each type of sensor, as well as IP Address of the machine itself.

2. Given that a problem has occurred within the TADDM environment, debugging mode needs to be set, so that the correct messaging is captured.


With emphasis on performing the following tasks:
1. Debug log level for Apache (digester / common) classes in clientproxy.log

2. com.collation.debuglevel.org.apache=WARN Flag that enables debug sockets on the service JVMs:com.collation.debugsocketsenabled=false
3. For profiling purposes: the place where OptimizeIt is installed on the system

4. com.collation.debug.optimizeitdir=/opt/optit/OptimizeitSuite Extra template debugging: com.collation.discover.engine.Template.ExtraDebugging=false
5. Log file prefix for mindterm ssh2 debugging: com.collation.mindterm.Ssh2LogFilePrefix=/tmp/ssh2
6. Log level for mindterm ssh2 debugging (0=none, 7=all)

7. com.collation.mindterm.Ssh2LogLevel=0 Extra debugging
1. com.collation.platform.session.ExtraDebugging=false
2. com.collation.platform.ip.ExtraDebugging=false
3. com.collation.platform.logger.ExtraDebugging=false
8. Overall log level
1. It can take the values:
2. FATAL - Messages that indicate that processing was halted because of some serious errors.
3. ERROR - Something bad happened. Gets logged in the error.log file
4. WARN - Not sure whether its bad but its definitely not good
5. INFO - Informational message about the inner workings of a service
6. DEBUG - Message that helps developers debug. Should not be used for tracing
7. TRACE - Debug message used for tracing. Will generate alot of log output. Should be enabled only on a per class level com.collation.log.level=DEBUG

3. Given TADDM is installed and user IDs are created, problems occur with Discover, Topology, Discovery Admin, Proxy or Gigaspace, review the jvmarg settings in the collation.properites file and determine if more memory is required, so that the issue has been addressed and potentially resolved.


With emphasis on performing the following tasks:
1. These do NOT override the settings in cmdb-context.xml
1. com.collation.Proxy.jvmargs.sun=-XX:MaxPermSize=128M
2. com.collation.Topology.jvmargs.sun=-XX:MaxPermSize=128M
3. com.collation.EventsCore.jvmargs.sun=-XX:MaxPermSize=128M
4. com.collation.EcmdbCore.jvmargs.sun=-XX:MaxPermSize=128M
2. java.nio calls System.gc heavily. This negatively impacts Discover Manager, particularly on Solaris.
1. com.collation.Discover.jvmargs.sun=-XX:+DisableExplicitGC
3. It may also benefit other platforms
1. com.collation.Discover.jvmargs.ibm=-Xdisableexplicitgc this deprecates the com.collation.javaspace.mem option
2. com.collation.GigaSpaces.jvmargs=-Xms8M -Xmx256M
3. com.collation.Discover.jvmargs=-Xms128M -Xmx2048M -Xminf0.1 -Xmaxf0.3
4. The above are examples of what can be changed. Contact support if you are unsure what the values should be changed to.

4. Given an installed TADDM host, determine the DNS resolution configuration on the host and use this information to correctly update the collation.properties for proper TADDM operation, so that TADDM is correctly configured for the DNS configuration of the TADDM host.


With emphasis on performing the following tasks:
1. Log in as the user that starts and stops the TADDM server.
2. Open a command window.
3. Issue the command: nslookup where is the hostname of a potential TADDM discovery target
4. Confirm DNS operation using the command: ping -a where is the IP address of the potential target.
5. If the nslookup command fails, or the ping -a command fails to resolve to a hostname, then DNS is not enabled for the TADDM server. If these succeed, DNS is enabled.
6. Navigate to the home directory of the TADDM installation.
7. Change to the dist/etc (Windows: distetc) directory within the TADDM installation directory.

8. Open the collation.properties file in the text editor of your choice. Locate the two parameters: com.collation.platform.os.disableDNSLookups and com.collation.platform.os.disableRemoteHostDNSLookups.
9. Set both parameters to false if DNS is not enabled. There is the option of setting these to true if DNS is enabled.
10. Save the changes and exit the text editor.
11. Restart the TADDM server to pick up the changes to the collation.properties file.

5. Given TADDM is installed and user IDs are created, define the different logs levels and what they mean and where to locate the logs, so that the logs have been explained.


With emphasis on performing the following tasks:
1. FATAL
2. ERROR
3. WARN
4. INFO (the default and provide the least amount of debugging information)
5. DEBUG (most commonly use for debugging problems)
6. TRACE
7. NOTE: File size of a rollover log file (located in the collation.properties)
1. com.collation.log.filesize=20MB
2. Number of logfiles before rollover: com.collation.log.filecount=5

3. # File size of a rollover log file: com.collation.log.filesize=20MB Number of logfiles before rollover: com.collation.log.filecount=5
8. Log Location $COLLATION_HOME/log/
1. log direcotory
2. services directory
3. sensors directory

6. Given a running TADDM server and access to the host running TADDM, determine if the database password configured for TADDM has expired or is invalid.


With emphasis on performing the following tasks:
1. Log in as the user that starts and stops the TADDM server.
2. Open a command window.
3. Navigate to the directory $COLLATION_HOME/bin (Windows: %COLLATION_HOME%in)
4. Check connection to the DB using the command: ./dbquery.sh 'select count(*) from compsys' (Windows: dbquery.bat 'select count(*) from compsys' )
5. If this succeeds, navigate to the directory $COLLATION_HOME/support/bin (Windows: %COLLATION_HOME%supportin)
6. Check JDBC connectivity with the command using the username and password defined in collation.properties for the JDBC connection:
1. DB2

2. - testjdbc.jy d (Windows: testjdbc.bat)Oracle

- testjdbc.jy o d (Windows: testjdbc.bat)If this command fails, then the password is either incorrect or expired.
7.

7. Given the need to diagnose a problem within the TADDM environment, utilize the support bin tools, so that problem can be debugged.


With emphasis on performing the following tasks:
1. authconv.sh - Will convert the access lists from the old format into the new format. Backups will be made of the existing access lists before being converted for UNIX
2. drop_db2_reporting_views.bat - Will disconnect from the database for Windows
3. drop_db2_reporting_views.sh - Will disconnect from the database for UNIX
4. sshexec.sh - Executes an ssh to check it is successful for UNIX
5. sshexec.bat - Executes an ssh to check it is successful for Windows
6. taddmsec.py - Test taddm security
7. testenv.bat - Test environment to ensure that authentication of functions are working for Windows
8. testenv.jy - Test environment to ensure that authentication of functions are working for UNIX
9. encryptprops.bat - To re-encrypt the password in the collation.properties file if they are changed for Windows
10. encryptprops.sh - To re-encrypt the password in the collation.properties file if they are changed for UNIX
11. TestGetRoutes.bat - Note: this test calls a private method in WindowsOs. For it to work, you need to set python.security.respectJavaAccessibility = false in the jython registry file (e.g. /usr/local/canopus/dist/external/jython-2.1/registry) for Windows
12. TestGetRoutes.jy - - Note: this test calls a private method in UNIXOs. For it to work, you need to set python.security.respectJavaAccessibility = false in the jython registry file (e.g. /usr/local/canopus/dist/external/jython-2.1/registry) for UNIX
13. testping.jy - Pings to see if there is network connectivity for UNIX
14. testprops.bat - Checks the settings in collation.properties to ensure they are set correctly for Windows
15. make_db2_db.bat - Makes and sets db2 parameters for Windows
16. testprops.jy the settings in collation.properties to ensure they are set correctly for UNIX
17. make_db2_db.sh - Makes and sets db2 parameters for UNIX
18. testquotes.jy - Tests WMI on the host for UNIX
19. make_db2_reporting_views.bat
20. testsnmp.bat - Test SNMP for Windows
21. make_db2_reporting_views.sh - Make Reports for db2 views for UNIX
22. testsnmp.jy - Test SNMP for UNIX
23. testssh.bat - Test ssh for Windows
24. testsshport.jy - Text ssh port for UNIX
25. make_ora_user.bat - Make oracle user for Windows
26. testssh.py - Test ssh for UNIX
27. make_ora_user.sh - Make oracle user for UNIX
28. testwasconnection.bat - Test Websphere for Windows
29. testwasconnection.sh - Test Websphere for UNIX
30. testwmi.bat - Test WMI for Windows
31. testwmi.js - Test WMI for UNIX
32. testwmi.jy - Test WMI for UNIX
33. wmiexec.bat - Test WMI for Windows
34. wmiexec.jy Test WMI for UNIX

8. Given the need to define common parameters in the collation.properties files, define the most common parameters that are located in the collation.properties file, so that the common parameters have been defined.


With emphasis on performing the following tasks:
1. com.collation.log.level=INFO Overall log level, forces all modules to log at this level if it is higher than the level they are set to
2. com.collation.view.cache.optimization.enabled=true View cache optimization helps improve the user experience when loading views in the UI. This setting should be set to true in production environments.

com.collation.view.cache.disk=true Caches the topology to the hard drive.
3. com.collation.view.cache.disk.path=var/viewmgr The directory in the TADDM installation structure where it stores the cache.com.collation.db.user=collation User name used to access the database
4. com.collation.db.password=collation User password used to access the database
5. com.collation.db.url=jdbc:postgresql://localhost:5432/topo JDBC URL of db to use
6. com.collation.db.driver=org.postgresql.Driver JDBC driver. Jar file containing it needs to be present in collation deploy dir
7. com.collation.db.archive.user=carchive Additional database user for archive
8. com.collation.db.archive.password=carchive Additional database user password
9. com.collation.db.archive.url=jdbc:postgresql://localhost:5432/topo JDBC URL of db to use
10. com.collation.db.archive.driver=org.postgresql.Driver JDBC driver. Jar file containing it needs to be present in collation deploy dir
11. com.collation.kodo.topomgr.port=5636 Kodo port for topomgr
12. com.collation.api.port=9530 Port for collation API
13. com.collation.webport=9430 HTTP port to use without SSL
14. com.collation.websslport=9431 HTTPS port to use with SSL
15. com.collation.commport=9435 RMI data port to use without SSL
16. com.collation.commsslport=9434 RMI data port to use with SSL
17. com.collation.rmiport=9433 Naming service RMI registry port
18. com.collation.jndiport=9432 Naming service JNDI lookup port
19. com.collation.sslpassphrase=140423933 SSL passphrase used by Jetty HTTPS server and GUI HTTPS server
20. com.collation.discover.dwcount=16 Max number of discover worker threads
21. com.collation.discover.agent.command.lsof.Linux=lsof How to run lsof on this platform
22. com.collation.discover.agent.command.lsof.SunOS.10.10.10.15=sudo lsof overriding lsof on a specific IP
23. com.collation.clientproxy.rmi.server.hostname=default if set to an IP address or hostname, then the clientproxy will set the java.rmi.server.hostname. If set to "default", then clientproxy will NOT set it. This is required if server forward and reverse DNS are not set or if the name resolves without domain and the client does not have the DNS domain in the search path


Section 6: Administration

1. Given a working TADDM server, access to the TADDM server, and a TADDM User ID/password, login to the TADDM server and execute the API query, so that xml data is outputted with the query from the TADDM database.


With emphasis on performing the following tasks:
1. Login to the TADDM server.
2. cd $COLLATION_HOME/sdk/bin.
3. Execute the api.sh -u -p .
1. Other Options for the api command include:

- discover
- topology
- changes
- version
- delete
- import
- export
2. Given the availability of database space, a running TADDM server and access to the product console, navigate to the product console user interface and create Versions of the current infrastructure, so that the version has been created which can be used for things like Disaster recovery, major IT infrastructure changing, and/or for Audit/Compliance reports.


With emphasis on performing the following tasks:
1. Log into the Product Console user interface.
1. Open the Discovery tab and select Versions or go to Menu Bar ->Discovery->Versions.
2. Select the Create button. This is also the location to remove or view each Version.
3. Give a descriptive Version Name.
4. Click OK; Versions are created under the database archive user.
5. Versions can be deleted
2. TADDM API: log into the TADDM Server under the TADDM owner
1. Change into the following directory: ${COLLATION_HOME}/sdk/bin
2. api.sh/api.bat -u|--u user -p|--p password [-H|--host host] [-P|--port port] [-l logfile_name] version [-c|--create version-name version-description] [-e|--createempty version-name version-description] [-d|--delete version-id-or-name]

3. Given an installed TADDM server, access to the server running TADDM and the new database user password, update the collation.properties file and encrypt the database access passwords, so that the collation.properties file is updated with the new encrypted passwords.


With emphasis on performing the following tasks:
1. Log in as user that starts and stops the TADDM server.
2. Open a terminal window.
3. Navigate to the $COLLATION_HOME/dist/etc (Windows: %COLLATION_HOME%distetc) directory within the TADDM installation.
4. Modify the collation.properties file and update the following parameters: com.collation.db.password and com.collation.db.archive.password. Replace the encrypted password string with the new password in clear text.
5. Save the file.
6. Issue the command to encrypt the passwords:
1. (UNIX) $COLLATION_HOME/dist/support/bin/encryptprops.sh $COLLATION_HOME
2. (WINDOWS) %COLLATION_HOME%distsupportinencryptprops.bat %COLLATION_HOME%
7. Check the collation.properties file the passwords are no longer plain text.
8. Restart the TADDM server.

4. Given an installed TADDM server and terminal access to the server running TADDM, start and stop the TADDM server processes, so that the TADDM server has been stopped or started.


With emphasis on performing the following tasks:
1. Starting TADDM.
2. Log in as the non-administrator that was defined during installation for starting and stopping TADDM.
3. Go to the directory where you installed the TADDM Server and run the start script:
1. UNIX: $COLLATION_HOME/bin/control start
2. Windows: %COLLATION_HOME%instartserver.bat
4. Confirm startup by issuing the command:
1. UNIX: $COLLATION_HOME/bin/control status
2. Windows: %COLLATION_HOME%incontrol.bat status
5. Stopping TADDM
6. Log in as the non-administrator that was defined during installation for starting and stopping TADDM.
7. Go to the directory where you installed the TADDM Server and run the control script:
1. UNIX: $COLLATION_HOME/bin/control stop
2. Windows: %COLLATION_HOME%instopserver.bat
8. Confirm shutdown by issuing the command:
1. UNIX: $COLLATION_HOME/bin/control status
2. Windows: %COLLATION_HOME%incontrol.bat status

5. Given the TADDM server is running, log into the product console user interface and run the appropriate report, so that the necessary information can be analyzed.


With emphasis on performing the following tasks:
1. Logon to the Product Console user interface.
2. Open the Analytics function tab or go to the menu bar and select Analytics and any of the listed report types.
3. Product Console Report Types: Custom Query, Inventory, Change History, Dormant Components, Component Comparison, and Switch Topology.
4. Domain Manager Report Types: Custom Query, Inventory Summary, Application Summary, Service Summary, System Inventory, Software Server Inventory, Interactive Wizard, and Monitoring Coverage report.
5. Major Custom Query distinction between Product Console and Domain Manager is that the Domain Manager has the ability to choose other data sources that TADDM may have federated.
6. During the defining of queries, some selected components could have additional attributes that can be viewed from a drop down list and one must be selected. The drop down box mechanics is done by placing a "." after the selected component type.
7. Results in the Product Console can be printed or saved in one of the following types: csv, xml or pdf files.
8. Must set the following variable to true in the collation.properties file (com.collation.domain.pdfreport.enabled=true) and the TADDM Server must be recycle in order to have the Domain Manager UI the ability to save the analytic reports. Available for English only.
9. Domain Manager can add additional custom reports by creating two views: JSP and External report views.

6. Given that TADDM is installed and Users have been created, using the User Interface define and configure schedules for discovery and sync, so that discoveries and syncs are automated.


With emphasis on performing the following tasks:
1. Log on to the TADDM User Interface.
2. Scheduling Synchronization on Demand:
1. In the Domain Summary window, select the domain that you want to synchronize.
2. Click Schedule. The Synchronize Domain window is displayed.
3. To start the synchronization immediately, click Start or to stop the synchronization, click Stop Discovery.
4. Specifying a Scheduled Synchronization
5. In the Domain Summary window, select the domain you want to synchronize. .
6. Click Schedule. The Synchronize Domain window is displayed.
7. In the Scheduled Synchronization section, click Add. The Schedule Period window is displayed.
8. Enter the name of the domain.
9. Enter the time to start synchronization.
10. From the list in the Repeat field, select the interval at which to perform synchronization. The options are hourly, daily, or weekly. The option you select is displayed next to the input box in the Every field.
11. In the Every field, enter a numerical value to correspond with the Repeat interval.
12. To save the information, click Add. The Synchronize Domain window is displayed with the new information in the table in the Scheduled Synchronization section. To return to the Synchronize Domain window without saving the information, click Cancel.
3. Deleting the scheduled synchronization of a domain.
1. On the Domain Summary window, select the domain you want to synchronize.
2. Click Schedule. The Synchronize Domain window is displayed.
3. From the table in the Scheduled Synchronization section, select the schedule that you want to delete.
4. In the Scheduled Synchronization section, click Delete. The schedule for that domain is removed from the table.
4. Viewing Synchronization Information.
1. On the Domain Summary window, select the domain for which you want to view synchronization information.
2. Click Schedule. The Synchronize Domain window is displayed.
3. In the Last Synchronization Time section, click View Sync Details. Synchronization status is displayed for the specified domain.
5. Adding a discovery schedule:
1. In the Functions pane, click Discovery Schedule. The Schedule pane is displayed in the workspace.
2. In the Schedule pane, click Add. The Discovery Schedule notebook displayed.
3. In the Name field, type the name of the discovery schedule.
4. In the Start Time (server time) field, type the date and time when you want the discovery schedule to start.
5. From the Repeat list, select the frequency that you want the discovery schedule to run.
6. In the Every field, type the numeric value for the time interval.
7. To configure the scope of the discovery schedule, click the Scope tab. The Scope page is displayed.
6. From the Scope list, select one of the following options:
1. To specify include specific scope sets in the discovery schedule, select Selected Scope Elements, and then select the scopes that you want to include.
2. To specify business services, business applications, application infrastructure, or physical infrastructure components, select the Selected Components list, and then select the components that you want to include.
3. From the Profile list, select one of the following options:
4. To discover active computer systems in the runtime environment, select Level 1 Discovery. This profile can be used to perform credential-less discovery.
5. To discover detailed information about the active computer systems in the runtime environment, select Level 2 Discovery.
6. To discover the entire application infrastructure, deployed software components, physical servers, network devices, virtual LAN, and host data, select Level 3 Discovery.
7. To save the discovery schedule, click OK.
7. Delete Discovery Schedule
1. In the Functions pane, click Discovery Schedule. The Schedule pane is displayed in the workspace.
2. In the Schedule pane, select the schedule that you want to delete and click Delete. A message window is displayed. To delete the schedule, click Yes in the message window.
3. To confirm the deletion, ensure that the schedule is not listed in the Schedule pane.
8. Note: Discovery and Sync's can not run simultaneously.

7. Given a working TADDM server, and access to the product console, navigate to the product console user interface and create Configuration Items, and relationships/dependencies, so that a new Configuration Item (CI) or relationship/dependency is created.


With emphasis on performing the following tasks:
1. Navigate to the product console user interface.
2. Open the "Create Component" under the "Edit" pull down at the top.
3. Select the "Component Type" that you would like to create.
1. Options Include: Web Server, App Server, J2EE Server, Database, Legacy System, Service, Cluster, and Computer System.
4. Input the name of your CI in the "Name" field and select "Next >>" at the bottom of the window.
1. If Computer System was selected, Input the required information for "HostName" TCP/IP address, etc and select "Next >>".
2. Input the following "Optional Parameters" if wanted, and select "Finish" at the bottom of the page.
3. A "Changes have occurred. Reload the view" prompt will appear at the bottom of the Console UI.
4. Select the "Changes have occurred. Reload the view" and your console cache will be refreshed with the changes made.
5. Navigate to the "Discovered Components" section in the product console user Interface.
6. Select "List/Search" from the pull down window.
7. Select your CI type from within the "Component" pull down.
8. Right �mouse-click' on the CI that you would like to add a dependency to and select "Component Dependencies" in the dialog box.
9. Within the "Dependencies List" dialog box that opens, select the "Add" button on the right.
10. From within the "Add Dependency" dialog box that opens, select the Type, either Dependent or Provider.
11. Select the CI type that the "CI to add" belongs to, Examples include, Web Servers, Messaging Servers, Custom Servers, Databases, etc.
12. Select the specific CI to add and select "OK".
1. Note: Multiple CIs can be added by repeating the process.
13. Select the "Close" button to complete the transaction.
1. A "Changes have occurred. Reload the view" prompt will appear at the bottom of the Console UI.
2. Select the "Changes have occurred. Reload the view" and your console cache will be refreshed with the changes made.

8. Given the need to categorize application components into business applications and business services, create a business application and business service from the user interface, so that Business Applications and Business Services are created to simplify an infrastructure by combining large collections of individual components into groups.


With emphasis on performing the following tasks:
1. Log into the Product Console to build a Business Application and Business Services.
2. Creating a BA and BS can be executed from the menu bar under Edit or under the Discovered Components function tab.
1. General Information Screen; Name, Description, URL.
2. Create BA or BS Components Screen: Include the available components.

- BA Component is available for BS.
3. - BA has an optional to create a new Functional Group.Application Admin Information Screen.
3. Business Application topologies can be viewed under the Topology functional tag.
4. BA and BS: Edit, Delete, show Details, and display Software and Hardware Topology.
1. Under the Discovered Components function, select either Business Application or Business Services and right click on the mouse to view the selections.
2. For Business Applications under the Topology functional tab, select a displayed application and, then right click on the mouse to view the selections.

9. Given admin access to a working TADDM server, and access to the domain user interface, create roles and groups, so that a new TADDM role is configured for use.


With emphasis on performing the following tasks:
1. Login to the domain user interface with an Admin ID.
2. Under the "Administration" tab on left, select "Roles".
3. In the Users Dialog box, select "Create Role"
4. Input the Role Name, value in the Create Role Dialog Box.
5. Select the proper permission for the new Role under the Create Role Assignment Dialog Box.
1. Options include: Update, Discover, Read and Admin.
6. Select the "Create Role" button at the bottom to complete


Make The Best Choice Chose - Certkingdom

Make yourself more valuable in today's competitive computer industry Certkingdom's preparation material includes the most excellent features, prepared by the same dedicated experts who have come together to offer an integrated solution. We provide the most excellent and simple method to pass your IBM IBM Certifications 000-011 exam on the first attempt "GUARANTEED".

Unlimited Access Package
will prepare you for your exam with guaranteed results, 000-011 Study Guide. Your exam will download as a single 000-011 PDF or complete 000-011 testing engine as well as over +4000 other technical exam PDF and exam engine downloads. Forget buying your prep materials separately at three time the price of our unlimited access plan - skip the 000-011 audio exams and select the one package that gives it all to you at your discretion: 000-011 Study Materials featuring the exam engine.

Certkingdom 000-011 Exam Prepration Tools
Certkingdom IBM IBM Certifications preparation begins and ends with your accomplishing this credential goal. Although you will take each IBM IBM Certifications online test one at a time - each one builds upon the previous. Remember that each IBM IBM Certifications exam paper is built from a common certification foundation.

000-011 Exam Testing Engines
Beyond knowing the answer, and actually understanding the 000-011 test questions puts you one step ahead of the test. Completely understanding a concept and reasoning behind how something works, makes your task second nature. Your 000-011 quiz will melt in your hands if you know the logic behind the concepts. Any legitimate IBM IBM Certifications prep materials should enforce this style of learning - but you will be hard pressed to find more than a IBM IBM Certifications practice test anywhere other than Certkingdom.

000-011 Exam Questions and Answers with Explanation
This is where your IBM IBM Certifications 000-011 exam prep really takes off, in the testing your knowledge and ability to quickly come up with answers in the 000-011 online tests. Using IBM Certifications 000-011 practice exams is an excellent way to increase response time and queue certain answers to common issues.

000-011 Exam Study Guides
All IBM IBM Certifications online tests begin somewhere, and that is what the IBM IBM Certifications training course will do for you: create a foundation to build on. Study guides are essentially a detailed IBM IBM Certifications 000-011 tutorial and are great introductions to new IBM IBM Certifications training courses as you advance. The content is always relevant, and compound again to make you pass your 000-011 exams on the first attempt. You will frequently find these 000-011 PDF files downloadable and can then archive or print them for extra reading or studying on-the-go.

000-011 Exam Video Training
For some, this is the best way to get the latest IBM IBM Certifications 000-011 training. However you decide to learn 000-011 exam topics is up to you and your learning style. The Certkingdom IBM IBM Certifications products and tools are designed to work well with every learning style. Give us a try and sample our work. You'll be glad you did.

000-011 Other Features
* Realistic practice questions just like the ones found on certification exams.
* Each guide is composed from industry leading professionals real IBM IBM Certificationsnotes, certifying 100% brain dump free.
* Study guides and exam papers are guaranteed to help you pass on your first attempt or your money back.
* Designed to help you complete your certificate using only
* Delivered in PDF format for easy reading and printing Certkingdom unique CBT 000-011 will have you dancing the IBM IBM Certifications jig before you know it
* IBM Certifications 000-011 prep files are frequently updated to maintain accuracy. Your courses will always be up to date.

Get IBM Certifications ebooks from Certkingdom which contain real 000-011 exam questions and answers. You WILL pass your IBM Certifications exam on the first attempt using only Certkingdom's IBM Certifications excellent preparation tools and tutorials.
Students Feedback This is what our customers are saying about CertKingdom.com.
These are real testimonials.
Hi friends! CertKingdom.com is No1 in sites coz in $50 I cant believe this but when I purchased the $50 package it was amazing I IBM passed 10 Exams using CertKingdom guides in one Month So many thanks to CertKingdom Team , Please continue this offer for next year also. So many Thanks

Mike CA

Thank You! I would just like to thank CertKingdom.com for the IBM IBM Certifications 000-011 test guide that I bought a couple months ago and I took my test and pass overwhelmingly. I completed the test of 100 questions in about 90 minutes I must say that their Q & A with Explanation are very amazing and easy to learn.

Jay Brunets

After my co-workers found out what I used to pass IBM IBM Certifications 000-011 the test, that many are thinking about purchasing CertKingdom.com for their IBM Certifications exams, I know I will again

John NA

I passed the IBM IBM Certifications 000-011 exam yesterday, and now it's on to security exam. Couldn't have done it with out you. Thanks very much.

Oley R.

Hello Everyone
I Just Passed The IBM IBM Certifications 000-011 Took 80 to 90 Minutes max to understand and easy to learn. Thanks For Everything Now On To 000-011

Robert R.

Hi CertKingdom.com thanks so much for your assistance in IBM IBM Certifications i passed today it was a breeze and i couldn't have done it without you. Thanks again

Seymour G.

I have used your Exam Study Guides for preparation for IBM IBM Certifications 000-011. I also passed all those on the first round. I'm currently preparing for the Microsoft and theIBM Certifications. exams

Ken T.

I just wanted to thank you for helping me get myIBM Certifications $50 package for all guides is awesome you made the journey a lot easier. I passed every test the first time using your Guide

Mario B.

I take this opportunity to express my appreciation to the authors of CertKingdom.com IBM IBM Certifications test guide. I purchased the 000-011 soon after my formal hands on training and honestly, my success in the test came out of nowhere but CertKingdom.com. Once again I say thanks

Kris H.

Dear CertKingdom.com team the test no. 000-011 that i took was very good, I received 880 and could have gain more just by learning your exams

Gil L.

Hi and Thanks I have just passed the IBM Certifications Directory Services Design exam with a score of 928 thanks to you! The guide was excellent

Edward T.

Great stuff so far....I love this site....!! I am also on the IBM IBM Certifications I decided to start from certkingdom and start learning study IBM Certifications from home... It has been really difficult but so far I have managed to get through 4 exams....., now currently studying for the more exams.... Have a good day.................................................. Cheers

Ted Hannam

Thanks for your Help, But I have finally downloaded IBM IBM Certifications 000-011 exam preparation from certkingdom.com they are provided me complete information about the exam, lets hope I get success for the 000-011 exam, I found there exams very very realistic and useful. thanks again

lindsay Paul
<