BMC Atrium Discovery and Dependency Mapping

LAB GUIDE
Lab Exercises
~bmc
BMC Atrium Discovery and Dependency Mapping PREP Boot Camp LAB GUIDE
Contents
Pre-Lab Setup 3
Module Z: Dashboards Overview """""" 5
Lab 2.1: Creating Custom Dashboards 5
Lab 2.2: Working with Dashboard Administrator Utility 6
Lab 2.3: Resetting the [10 eked 1 Flag 7
Module 3: User Administration and System Security 8
Lab 3.1: Providing Security Management Access 8
Lab 3.2: Modifying the Login Page and Checking Audit Logs 9
Lab 3.3: Creating a New User from the CLI 12
Lab 3.4: Listing the New User's Details 13
Lab 3.5: Changing a User's Passwo rd 14
Lab 3.6: Locking and Unlocking an Account.. 15
Module 4: Scanning Basics 16
Lab 4.1: Perform a Sweep Scan 16
Lab 4.2: Exciude Management 18
Module 5: Discovery Credentials Z0
Lab 5.1: Configure a Windows Credential in a Windows Proxy Pool 20
Lab 5.2: Configure Host Credentials 24
Lab 5.3: Configure a Full Discovery Scan 29
Lab 5.4: Configuring Additional Database and Application Discovery 30
Module 6: Query Language Overview 34
Lab 6.1: Running Simpl e Searches 34
Lab 6.2: Searching with the WHERE Clause 34
Lab 6.3: Searching Using WHEREand ANDCLAUSES 35
Lab 6.4: Searching With the Regular Expression Syntax 35
Practice Exercise 1: Using the Advanced Query Language 37
Lab 6.5: Using the 0 RDER BYClause 38
Lab 6.6: Using the EXPLODE Clause 38
Lab 6.7: Using Key Expressio ns 39
Lab 6.8: Using the TRAVERSE Clause 39
Lab 6.9: Using the EXPANDClause 40
Lab 6.10: Using the NODECOUNTClause 41
Lab 6.11: Using the PROCESSWITHClause 41
Module 7: Clustering 4Z
Lab 7.1: Create a Cluster 42
Lab 7.2: Change the Cluster Coordinator 46
Lab 7.3: Enable Fault Tolerance in the Cluster 47
Lab 7.4: Run a Full Discovery Scan from the Created Cluster 48
Lab 7.5: Remove a Cluster Member from the Cluster 49
Module 8: Consolidation 51
Lab 8.1: Set Up Consolidation 51
Lab 8.2: Run a Scan from the Scanning Device and Verify It Is Sent to the Consolidator 52
Page 1
Module 10: Using BMCAtrium Discovery CLI 54

Lab 10.1: Starting Discovery from the CLI 54
Lab 10.2: Deleting a User from the CLI.. 54
Module 11: Appliance Support 55
Lab 11.1: Downloading Logs for Customer Support 55
Module 12: Collaborative Application Mapping 56
Module 13: Edit Pattern Templates 57
Lab 13.1: Edit a Simple SI Pattern Template 57
Lab 13.2: Edit an 51 Version Package Template 63
Lab 13.3: Edit a Business Application Instance Search Template 67
Module 14: Application Mapping Using Templates 71
Lab 14.1: Create a Simple Softwarelnstance of the Wibble Database 75
Lab 14.2: Generate a Versioned Softwarelnstance Pattern for the Wibble Database 77
Lab 14.3: Generate the Softwarelnstance for the Wibble Application Server (Version, Build, Patch) 78
Lab 14.4: Update the Softwarelnstance for the Wibble Application Server - Ports 79
Lab 14.5: Update the Softwarelnstance for the Wibble Application Server - Product Version 81
Lab 14.6: Generate a Softwarelnstance for the Wibble Exporter Server 82
Lab 14.7: Generate a BusinessApplicationlnstance for the QuickExpense Business Application 83
Lab 14.8: Update BusinessApplicationlnstance for QuickExpense Business Application - Apache Web
Server 83
Lab 14.9: Update BusinessApplicationlnstance for QuickExpense Business Application - Containment
Relationships 85
Lab 14.10: Add Simple Identities for All Processes 86
Lab 14.11: Update the BusinessApplicationlnstance Versioning for QuickExpense 87
Page 2
Pre-Lab Setup
IDs and Passwords for Use in the Lab Exercises
Credentials to log in to the environment:

• Login: administrator
• Password: password
BMCAtrium Discovery Login Password Notes

Virtual Appliance
http://192.168.0.10/ui system System1234$ The Primary "ADDM10.1 Demo" virtual machine
http://192.168.0.9/ui system System1234$ The Secondary "ADDM10.1 Clean" virtual machine
WinSCP Credentials
1. From the desktop, open the WinSCP icon using the following credentials:
• Host name: 192.168.0.10
• Port number: 22
• User name: tideway
• Password: tidewayuser
....
;:
::..:;.-:::.::....
--- r~=''----
,...
2. Click Login.
·1 ...... ·1
-
PuTTY Credentials
1. From the desktop, open the PuTTY configuration window using the following credentials:
• Host name: 192.168.0.10
• Port number: 22
Page 3
~purTY(onrt(Juration f.3
8- Souion 80de QIlbo(Io. IOf,YOIJI PU 1lY ~~
8
".",.,.
lornmd
5_,,,,,.,,,,,,,,,,,,,,_ to _to~
Host Jlame to. IP a&tett) Port
"-. 122
B,I
- F~btl.l"l!S
8-'vIndow
[ C'omedicln t}1lC;
(" Row r I"", r RIoOn r. $5" r 5'"'" ,
.... M eoee
8ehavioul lO6d. t4VO Of delete e $tOfcd teuion
l'an~¥.ion SaV$dS~
Selection
eow.
-1-
S C""""On lo"
0...
Oelele
RIoOn
<l! 55H
SOIia!
0"",
2. Click Open.
3. At the command prompt that opens, type the user name tideway and password tidewayuser,
and press ENTER.
Page4
Module 2: Dashboards Overview
Lab 2.1: Creating Custom Dashboards
Task 1: Copy the Default Dashboard
1. Click the Home tab and at the upper-right of the page, click Available Dashboards (~.
2. Click the Copy Current Dashboard link.
Task 2: Rename the Dashboard

1. In the dashboard title, click the Edit link.
2. Close the New dashboard created message.
3. In the Dashboard Title field, change the dashboard name to Custom Dashboard. Do not click
Commit Change in this step.
Note: The next task is a continuation of this step.
Task 3: Include Channels in the Dashboard
1. From the options available under the Included Sections, select any seven channels, based on
your requirements.
Tip: The page shows seven preselected channels from that list. When you scroll down the page, you
will see those channels already displaying. Select Application Mapping to include one additional
channel.
Note: BMCAtrium Discovery and Dependency Mapping 10.1 does not allow more than eight
channels to a dashboard.
2. Click the Commit change button.

3. Click the Home tab to verify that your dashboard displays the selected channels and view the
new dashboard name.
Tip: Instead of clicking the Home tab to view the refreshed channels, you may also click the red x
button on the dashboard configuration options.
Page 5
Lab 2.2: Working with Dashboard Administrator Utility
Task 1: list and View the Currently Available Dashboards

1. In the PuTTY Configuration tool, type the following data in the respective fields:
Host name 192.168.0.10

User name tideway
Password tidewayuser
2. Type tw_config_dashboards --Is and press ENTER.
Note: In the command, ensure that there is a space after dashboards:

tw _config_dashboards<space>--ls
3. Type the password as System1234$. The list of current dashboards should be displayed.
Note: The password typed is the password of the system user from the UI.
The list of available dashboards includes information on locked dashboards. The names of modified
dashboards will appear with alphanumeric characters.
Page 6
Lab 2.3: Resetting the [locked] Flag
Task 1: Unlock the Default dashboard from the CLI

1. From the PuTTY Configuration tool, type tw_config_dashboards «unlock Default and press
ENTER.

tw _config_dashboards<space>--unlock
2. Type the password as System1234$.

3. To view the list of dashboards, perform the steps listed in Lab 3.2.
4. Minimize the PuTTY window. In the UI, click Available Dashboards (1lZIj.
5. Navigate to the default dashboard. Note that the title contains [Edit) that indicates the
dashboard is unlocked and can be edited.
Task 2: lock the Default dashboard from the CLI

1. From the PuTTY Configuration tool, type tw_config_dashboards --lock Default and press
ENTER.

tw _config_dashboards<space>--lock
2. Type the password as System1234$.

3. To view the list of dashboards, perform the steps listed in Lab 3.2.
4. Minimize the PuTTY window. In the UI, click Available Dashboards (~.
5. Navigate to the default dashboard. Note that the title does not contain [Edit) that indicates the
dashboard is locked and cannot be edited.
Page 7
BMC Atrium Discovery and Dependency Mapping PREP Boot Camp LABGUIDE
Module 3: User Administration and System

Security
Lab 3.1: Providing Security Management Access
Task 1: Create a New User's Account

1. From the Administration tab, under the Security section, clickUsers.
2. Clickthe Add button (at the lower right of the page).
3. On the Add User window, create a user by populating the following fields:
a. User name: User_Test
b. Full name: <Your Name>
c. Password: User123$ (Type this password in both of the password fields.)
4. ClickApply.
5. To log out of the system user login, click Logout at the upper-right corner of the page.
Task 2: Check the Access Levels of the New User

1. To log in as the newly created user (User_Test), type the credentials for the newly created
account (user name User_Test and password User123$ - user name and password are case
sensitive).
2. From the Administration tab, in the Security section, click Security Policy.
Question for Discussion: What result do you see?
Answer: Since the newly created user User_Test does not have Administrator permission, you
won't be able to access the Security Policy section.
Tip: After completing this task, log out of the User_Test account and log in again using the user
name system and password System1234$.
Page 8
Lab 3.2: Modifying the Login Page and Checking Audit Logs
Task 1: Change the Appearance of the Login Page

1. From the Administration tab, under the Security section, click Security Policy, then click the
Login Page tab.
2. Note the currently selected option for Plain Login Page. It is at the default No.
3. ClickLogout at the upper-right corner of the page. When you log out of the appliance, you will
notice that the BMCSoftware brand information displays on the login screen.
4. To change the appearance of the login page to a plain (non-branded) view, log in to the
appliance (username system and password System1234$).
5. From the Administration tab, in the Security section, click Security Policy, then click the
Login Page tab.
6. Change the Plain Login Page option from No to Yes and clickApply.
7. ClickLogout at the upper-right corner of the page.
Page 9
8. After logging out of the appliance, you will notice that the BMCSoftware brand no longer
displays on the login screen. It is a plain white login page.
login I
You have suc~essfuiV logged out.
9. Log in again using the credentials of system and System1234$.

10. To revert the appearance of the login page back to the BMCbranding, from the Administration
tab, under the Security section, click Security Policy, then click the Login Page tab.
11. Change the Plain Login Page option from Yes to No and click Apply.
Task 2: Check for the Display of the Legal Warning Message on the Login Page
1. From the Administration tab, in the Security section, click Security Policy, then click the
Login Page tab.
2. Type anything in the Legal Notice field.
• Suggested sample text: This is the legal notice text
3. Click Apply.
4. Log out of the appliance.
5. At the login screen, verify that the Legal Notice in the lower-left corner of the window is now
showing what you typed.
Page 10
Task 3: Check the Audit Logs for a User
1. Search the audit logs for the system user's activities.

a. From the Administration tab, under the Security section, clickAudit.
b. Leave all fields at the default value and click Run.
acme ApplicatIons Inf.astruct\.lre DIscovery aeoorts AdminiStration
Ad ministration:> Audit
f Audit
I Audit LOg> l_pul'ge
From 12 .:J Marcil .:J 12()15 at iOO {17

To oay.:J Monlh .:J Iv••, allhh'rm;;'
User 10
Eventstoup All
Events AU
.:J
c. Note in the Audit log the different events listing each user and date/time.
Important: Security Warning
• Keep knowledge of the password to a minimum of people.
• Comply with your organization's policy on root or superuser passwords.
• Change the password when people leave the team.
Page 11
BMC Atrium Discovery and Dependency Mapping PREPBoot Camp LAB GUIDE
lab 3.3: Creating a New User from the Cli
In this exercise, you will perform user management tasks using utilities from a Command Line
Interface (CLI).
Task 1: Create a New User from the CU Using the tw_adduser Utility
1. Access the PuTTYtool from your desktop to use the appliance from the CLI.
Login: Use tideway/tidewayuser and click Open.
2. Type tw _adduser -f 'Student' student
Note: In the command, ensure that there is a space after tw_adduser, and -f and 'StudentOl'
tw _adduser<space>-f<space>- 'StudentO l' <space>student
[t lr::ieTT=c.:IJ lDI_':t_llll::,.=t ] ~ t-T,T :tll,ill'::'::":t: ~tllle!lt -f I ~tl1Iiell+- 1]1'

rreT,T .P~'='=TTI::'rli !:DL .=tllliellt :-1
3. Type a password Gust use password).
4. Retype the password (password).
-
[t ldeTT:cl':.' j Loc-e Lhce- J ~ t IT_=tI!,-i1t2er a t.ucie n t -:t I .::_r'11-~ell1 01'

IJPTT ;_13..:::--::r,r,-,t1t ror ::tll,ip!,t:
Pe t.y pe pa.szs toord rcr .s t.rad e n r.c
[t 1,ieTT:::'IJ 11::11_':11111::I.::t ] ~ I
Notes:
• The tw_adduser utility creates the new user with the user login student.
• The option -f'Student 01' allows the administrator to specify the full name of the new user
(Student 01).
• For syntax help, use the «help flag.
• For more information on the tw_adduser utility, including required syntax for available
arguments, visit http://discovery.bmc.com/ confluence/display /101jtw _adduser.
Page 12
Lab 3.4: Listing the New User's Details
Task 1: View the Details of a Newly Created User

1. Type twJistusers --filter=student to list the user's details.
Note: In the command, ensure that there is a space only after twJistusers and nowhere else.
twJistusers<space>--filter=student
Notes:
• The twJistusers utility displays all users' details.

• The filter --filter=student displays the specific new user's details.
Page 13
Lab 3.5: Changing a User's Password
Task 1: Change the User's Password Using the tw_passwd Utility

1. Type tw_passwd student.
2. Type the new password (Passwordl$).
3. Retype the new password (Passwordl$).
[r~iIJeq,::t?I:jlc,c;~lYlcl~;t '-J $ t.r.r p.;:tS.3T,r.:i 8tl.t(~e!lt

NetT pa38~TO[cl f,)[ S~lld~!)t:
Pety~le paS3T~or,j fc,r stl1dent:
P·;t33\,l':'t",j set f':'l:" ue e i; rrstU.IJ~r.Lt"
[tiIJE:!,.r,~'rjOl':'c.';;;tll.LCI3t --J $ I
Notes:
• The tw_passwd utility displays warnings about the standard rules for formatting passwords.
• For more information on the tw_passwd utility, including required syntax for available
arguments, visit http://discovery.bmc.com/confluence/display / lOl/tw_passwd.
Page 14
Lab 3.6: Locking and Unlocking an Account
Task 1: Lock an Account

Youcan lock an account from the CLI.
1. Type tw_upduser --locked student
2. Press ENTER
[t 11:it:::l1-:1.~'I~ 1,:,c':-tlll021_ ] ~~ t_ l'1__ ltl'l:lll2~!- --l':"-'~:t::·:;, .::t l~,J~llt:.
?er U3er 3~~te U3EF ~TATE LI="=~EII

[t lci,==TT~~'I~ 1,:"c.:-t111cl.=t -] ~ _ -
Task 2: Unlock an Account

When an account is locked, you can unlock it from the CLI.
1. Type tw_upduser --active student
2. Press ENTER
[i 11::ieT,T=t:T!J IDI...:':-tlllo.:::'i ] ~ iTT 111)li1l.::er --:'1.,__:'ll-:e .:=tlu::ielll
:"et TJ2er ,:t ::tte TJ.:"E:t:',:T.u_TE .u.':TI'i/E
[t Id.r:::T'T:t~T[j lo':'":tlllc,.=t -] ~ I-
Additional Information on tw _upduser:

• For more options on this utility, type tw_upduser -help.
• For more information on the tw_upduser utility, including the required syntax for available
arguments, see http://discovery.bmc.com/confluence/display 1101/tw_upduser.
• For more information on command line utilities noted in this lab, refer to the
documentation at
http://discovery.bmc.com/ confluence I display 1101 IUsing+Command +Line+Utilities.
Page 15
Module 4: Scanning Basics
Lab 4.1: Perform a Sweep Scan
Performing a sweep scan in a new environment is a typical use of this feature to get a quick view of
what is there in the environment.
Before performing a sweep scan, ensure that Discovery is running.
Tip: Ensure that there are no credentials configured in your appliance before you perform a sweep scan.
Task 1: Add a New Run
1. From the Discovery tab, click Discovery Status, and click Add a New Run.
2. ClickAdd a New Run to add a new Discovery run.
3. On the Add a New Run screen, specify the following details:
• Type: Snapshot
• Range: 192.168.0.1-25
• Level: Sweep Scan
• Label: First Sweep Scan
4. ClickOK
a If Discovery is currently not running, click START ALL SCANS.
b. From the Currently Processing Runs tab, monitor the progress of this discovery run.
Task 2: View the Results of the Discovery Run
1. From the Recent Runs tab, explore the latest run by clicking the label (First Sweep Scan) for
the scan.
RUNNING '1.,)"I'Ii"'$'
ReC'MtRuns
Shovling 3 completed Discovery Runs
Range Tuning
First Sweep 192.16&.0.1·25 25 201s..03·1306:53~16·

06.'53:52
SCan (D.OOOO:36)
Page 16
2. View the Discovery result and discuss the various statuses under the Status and Summary
sections with your instructor.
StartTime 13103l201508:0e:33
EndTime 13/031201508:09:03
Duration 0.00:00:30
Numb .. of IPs Scanned 25
Numb .. of IPs Dropped ~
Endpoints 11 OISCOVe-NAcc~ss~srelatoo
o summa!),
Hosts 0
NetWol'k oevices 0
SttIrage Devices 0
Storage Syste<ns 0
Printers 0
SNfl1P Managed oevic:es 0
Mf Parts 0
SUCCHS 0
Skipped 2
NOAa:e$S ~
NOResponse 0
Error 0
3. View the Discovery result for Skipped and for No Access and note those IPs.
4. View the Discovery result for Number of IPs Dropped.
BMCAtrturr Discovery & Dependency Mapping
Hom? Application::. Infrastructure txsee-......
<:'!Y fl.~rts Mrruni-str<i'tlon
Droppec Endpoints: 2015-03-16 05:00:21.00

(AtIions::::J (Related.)
Start Time 1610312O'1S(6:OO:21
E,nd Time 1610312015 05:00:2S
Reason IPs cfroppad No I'es.p()r')s.fi"orn~ IP$
IP ~ddl'esses 192..168.0.14,. 192.168.0.15. 192.168A16~ 192..168.0.17. 192..168A11, 192.168.0..12. 192..168.-0..13.192.168..0.18., 192.168.0.19. 192..168..0.24.
192.168.0.21.192.168..0.20, 192.1E6..0.23. 192.168..0.22
Number of IPs dl'opped 14
Discovery Run firs Sl'MQ sgn
Tip: Individual results for the Skipped and No Access may vary in this lab per run. However, note
that this result screen helps reveal IPs that could be excluded from future scans.
Page 17
Lab 4.2: Exclude Management
Task 1: Add an Exclusion Range

1. From the Discovery tab, click Discovery Status, and click the Exclude Ranges tab.
Discovery Reports AdmlOls!ratton
(Integration pOints) ( SN~P Recognition I (OISooVlfVReports) (TOOlS I
(SIA!U.ALt;.SCAtlSJ
~ Discovery is STOPPED
Exclude Ranges
There are no excludo ranges to show OAdd New Exc'ude, ••
2. To add an exclusion range, from the Exclude Ranges tab, click the Add New Exclude Range
link
3. On the Add a New Exclude Range window that appears, specify the following details:
• Type: Permanent
• Range: 192.168.0.10-24
• Label: IP range to exclude from a Discovery run
• Description: The Admin has requested that these IPs be skipped in a Discovery run
Tip: In the previous lab, we saw that 14 IPs were dropped (192.168.0.11-24), two IPs were skipped
(192.168.0.10 is an unsupported device and 192.168.0.25 is a desktop - excluded), and nine IPs
could not be accessed (192.168.0.1-9).
Based on those observations, we have chosen these IPs to exclude from future scans.
4. ClickOK
Task 2: Add a New Discovery Run

1. Click Add a New Run to add a new Discovery run.
• Type: Snapshot
• Range: 192.168.0.1-25
• Level: Sweep Scan
• Label: Sweep Scan with Excluded IP Range
3. ClickOK
• From the Currently Processing Runs tab, monitor the progress of this discovery run.
Page 18
1. From the Recent Runs tab, explore the latest run by clicking the label (Sweep Scan with
Excluded IP Range) for the scan.
BMC Atrium Discovery & Dependency Mappmg
Heme Application, Infn.l!;\n.lctur~ RQPortr. Admln!~rallon
RUNNING
R~tRuns
Showmg 3completed Ofscovery Runs
Label Range Timing
Sweep Scan with 192.168.0.1·25 25 2015-0l·1605:23:4& • Scan

Excluded IP Range C6:24.16(0.~ ccmpteee
2. View the Discovery result by clicking the label.

3. Refer to the Summary section, Skipped status.
4. Clickthe number link of the Skipped status, as highlighted below.
scattTim. 16f03";C()1S0ea3;AS
(1'4 Time 161O'31a01$C~,:24:16
I NI.IId:oer oIIf':sOfC'j:-,:Cid.u I
(~I'!U 'pO!wY;WArre<.'M(f:jl'''''
o Summncy
Hosts 0
~~Q ....;CIS 0
$lor ap OIlVic:cas 0
SNM'
_.
',inlMS 0
t.W!..-I OeoAQ!S
MI'lIrts
$k~"
0
"'-2
No''''f)Ol\JI 0
fnOf 0
5. Verifythat the results for the dropped IPs match the exclusion details.
~ DIOppf>Crrjp')lnt:,: "'10'1~ 03 I o 05:2 :):5'1.00
IACtion! .) IBr" M .)
StaflTime 16t03l201~05a3$1
End Time 1&'03/201S0!Sa3;:S1
Reason IPs dropped &dude ~ prev.,.ed sannlng of these- IPS
IPAddrM$I!:S 192.168.0.10. 192.168.0.11. 192.168.0.12. 192..168.0.13.192.168.0..14, 192.168.0.15,192.168.0..16,1.92..168.0.17.192;168.0..18,192.168.0.19,

192.168ruO, 192.168.1l21. 192.168.D.22, 192.168.D.23.192.168.0.2A
Numbet or IPS dropped 15
Discovery Run SVo!!>f:O $gnw;th fYPK1ed IP Ranift
Page 19
Module 5: Discovery Credentials
Lab 5.1: Configure a Windows Credential in a Windows Proxy

Pool
Task 1: Create a Windows Credential Proxy Pool
1. From the Discovery tab, click the Credentials button.

2. From the Devices tab, click Windows Proxies, then click Add to create a Windows proxy pool.
3. On the Create Windows Proxy Pool form, provide the following details:
• Name: MyWindowsProxyPool
• Matching Criteria: Match All
• Type: Windows Credential Proxies
• Description: Windows Proxy Pool
BMC Atrium Discovery & Dependency Milpplng
Home ApphcatlOf'lSo In1ra~truC\ur(> Re-port!l Adrnlr'llMrJtlcn
10":cov'ery> Device credentl als > creale windows Proxy POol
Create Windows Proxy Pool

Name: IMyWindOwsP(Oxypoot
Matching Criteria: t.1atch All po

setect -'.ffltch AJr to I1W1xh OJ'ItfldpOtIllS. U!l~(!ieCl it to e.i« vt:/V.EStho: ",JI be usrd rod!rflf':'!iflt JI chi:> l'ft!lcI~':. PfO).YPool.JSsuitable
lora parlfnJlarr/?dprxn~ 1heyrrn; brOr.F ormorp o{"hefctUNl,ng. $mur.1ti.'d byr"'mmrt):
Q(( IPv( oodrtss. (e.g. 10. ;0, rO.3)
an IPv~riJflg?ipi'rIfi'~ttoo (e.g. fO 10. 'O.-&.or 10.10 '·S ""C'r 10. fO.H).Q/)'4j
lin 1P11'fjOddr~s (t.,g.{dIJEf:7554:272f!OSb3:-:3J
on 1°11'6fii'!WOrk pr?{f': "~.g.
/dofr.75S4:772t:nB':J?:.I64)
(9'VPaIttfj2cmg@O
Type: Wlndows cr£odenual ProXIe-S .:J

Nor 1P--t6cr.:pcrbf~
OOlllains:
Description: hls,s a Windows Proxy Pool
4. Click Apply. The page refreshes to display content of the current Windows proxy pools.
Page 20
5. Drag the newly created proxy pool to the top of the list using the grey vertical bar on the left.
BMC Atrium Discovery & Dependency Mapping
-
Home ApplicatIons Inf.astructllre Re-ports AdmInistration
.miley, ( lCnowttdgt MolIt,Igemtnl I ( Inlt8f"tiQn I"oinh ) I~MP RtCOWlilion) ( Discovtry RtportJ) ..

Device Credentials
(Ih'6EMJ ICttdtnl~1 Tts1s I
\Vindo\',sproxy Pools will b~ttled ill the order shown, from top to bottom. Windows PrOXie-!.wttlbe-chosen (rom the Pools basoo on loading. change the- IAdd __I
order by dragging Windows Proxy Pools to a new place in the list.
AIlIP Addresses- OE'.40 AatOr\5 ....

~)'~ Cr~dMtla' gewtpbon
PRO"(Y I I ~I.I '.10' 1313 Actions·

Stitb...~ O-·..,tlJedbrute,
Usns~ see WI~doll'ls'o~n (rtdentials
Allie Addrcv>es - f;'Y'h',odowg,lroXV!'ogl

CreClel'llil'tl . Thb IS' e WII\Clows ProX)' POOl
Task 2: Download the Windows Credential Proxy Installer

1. From the Discovery tab, clickthe Tools button.
2. To download the Credential Proxy version 10.1 installer, click the Download installer for
Windows Proxy version 10.1 link
~ Discovery Tools
Windows Proxies
WindovlS dlscoVf!oI'Y
requires a windows proxy. Th~Proxy ISa BMC.Atrlunl Discovery appliC3tiOll that runs on a customef·provided windOM host.
Proxies have three different forms:
• Active Directory Proxy·. proxy Is configured to run as a specific Actl'l't·Directory account
• Workgroup Proxy -Proxy JsCXJnfiguredto run as a Workgroup ececcnt. Since 8.2 this hasbe~ merg.cl into the ActIve-Directory Proxy
• Credential Proxy -uS&Scrooe-ntials supplied by the eMC Atrium OIscovety appliance to perform windoW'S diSCOVery
Btfor9YOu an use a Proxy to d1$(oV'eryourWlndows IT fnfra5tl'uaure. you ITlUst first Jnstallind Nn the Proxy software 'there IS' s.ll'\gte inRlllet(ol' all prOXJ.es,),
Theonyou need to Idd tht Pl'oxy to the- !pptlance usina ,he Add Window) PrQXY eop! p08e.
(. Download ln$taUerfor Wlndow5Proxyversian 10.1 )
3. Clickingthe download link launches the File Download dialog box. ClickSave File.
t1l Olscovet y roots

OplI'fl!no a-ddnlproxy _ms-laller _10.1_ 401211_(JQ.e-Me EJ
You hlwod'loscn to~:
Windows Proxles a addmproMY _Installer _10.1_ .. OI211_ga.eKe
wtkhis: """",..(IMMe)
Windows d'Kovery requires a WindoW'SProxy. The F frOtl'l: http://I92.I68.0.)O
·provlded Windows hOst.
P(oxles have th~ dlffftent forms:
WOl.td 'J'OIJ Ike to S&'YetHstis?
I
-=s.v.=:....=~~I=c:"":~=~IJth.
• Attive Oirlctory proxy·· Proxy is com.
• Wort<croup Proxy - Proxy Is configuroc< Directory proxy
ActIVe
• Crldlntial Proxy - uses credernlals SUJ... iscovery
8e(creyolJ can use a Proxy to discoveryourWindowslT Infrastructure, you mt,lst first install and run the Proxy software (there Is a single installer for aUproxies).
TtI!?n you ne-edto add the P(oxy to the app.UanceuSing the Add W1otfow:; Proxy PQQ!page.
(. Oowntoad install~ (O( Windows P(oxyve(Sion 10.1 I
Page 21
4. Locate the file (addmproxyjnstaller_10.1_ 401211_ga.exe) in the downloaded folder using

the shortcut on the desktop titled Downloads; from that folder, you can run the installer.
• In Google Chrome, clicking the download link will automatically download the installer to
your computer. After it completes the download, click the installer visible at the bottom of
the browser window. ClickRun to install it
Task 3: Run the Windows Credential Proxy Installer

1. On the Setup - BMCAtrium Discovery Proxy welcome wizard window, click Next
2. On the Select Destination Location window, retain the default location and click Next
• Ifyou get a message about installing to an already existing folder, click YES.
3. On the Select Start Menu Folder window, retain the default location and click Next.
4. On the Select Additional Tasks window, ensure that both check boxes are selected and click
Next
5. On the Active Directory Proxy window, clear Create an Active Directory Proxy and click
Next
6. On the Credential Proxy window,select Create a Credential Proxy and Do not enter
credentials. ClickNext. (We will specify the credentials later.)
7. On the Ready to Install window, click Install and monitor the progress.
• Ifyou get a message about overwriting a winproxy.conf file that already exists, clickYES.
8. On the Completing the BMCAtrium Discovery Proxy Setup Wizard window, retain the two
default selections, and click Finish.
Completing the BMC Atrium

Discovery Proxy Setup Wizard
5etup hes fil"ished ins:ta1ng the 6MC Abhsn ~(OV!r'yPr(lQ(y
C)n your computer.
clkkflnis:h toe)(it Setup.
p B!4"i.i:~~~~~Q5Y..~~~~i~~
IV R.t.!n P,'oxy Manager
9. The page briefly displays the Proxy Manager window before launching the Create Windows
Credential Proxy screen.
f?]UMC Alriurtl DJ~t.uv~ryProxy MdlldUt!r 119Ei
Proxy Edk \/lew Help
Accoont POft state

"Credential LocalSystem i323 RLIlning
Page 22
10. On the Create Windows Credential Proxy screen, enter the Proxy Name details
StudentWindowsProxy and click Apply.
• You may opt to retain the prepopulated value - STUDENT-602A98D.
Hom('l Applications In(rl~ruc.Ur(> R("PO~'!o Admtnl ..tratlon
841!!j,l'MI' (ICn~w'fldr~Mrmt'" I 111'1111,6110"'01111\1 (SNMPR.tC!llfItlion) 100ucrv,I)'"'IIO"\) (follh]
IOlscove,·y> Oovlee Credentials> Cl"eateWlndows Cl"edenUol Proxy
Create Windows Creoentlal Proxy

proxy Pool: Mywlndo\'JSproxyPool.:J
Proxy Name: IStude-ntWrndow..prOXy
proxy Address: 1,92.168.0.25
Port ~323
Certificate: EMBg:·AC:04:07;67·1'_·1P..:QO$3·14:1e..'~r;.-e.!?(SA:BrnF$O;e$
tn. bled: P"
Tip: As we have installed the credential proxy on the machine at IP 192.168.0.25, the Proxy address
is prepopulated to 192.168.0.25.
11. Verify the result that the credential proxy is successfully added to the proxy pool.
12. Note that the status of the Windows credential proxy is Active.
~ Device Credentials
OeI/lee, [[)mb.... I I\ItddlQW3r. I MM.semon'Sysl.,n 1
(kosts) 'dM'@$tt! I"''') IvCtnurl ~ I""''') ICrtlltntWtl Tuts I
-
Windows Proxy Pools will b@'tti&d in th~ ord~ shown, (rom top to bottom. WindoW!. ProXier. "Jill b. chosen (rom th@Poolsbasedonloadfng.Change-th@ IAdd_1
order by dragging Windows Proxy Pools to a new place rn the Ur.t.
AIlIP Adc!rp_",,,p.li;-
f.t)!!tiir.dQ\'!s:PrQ~I>QQJ 1 Actions ...
1yp~ CredMtla.I{C.an.not scan IPvSaddr~sS!S) OMcrlptlon This is a W1ndO\~s Proxy Pool
f)StudentWindo\·JsProxy· 192.16&.0.25:4323 IAO:toni ..
II Actiotel
dO'tlS lOgin (:rect(}111~1S
101l.O1'211
(.(11'1 get IPV4:Ide1e but VJIr'I«1MS Ye($i(ll'I60es not Sl,lpport scen.,ing
IPv6ftddJe~$.
Page 23
Task 4: Check that the Windows Credential Proxy Can be Contacted

1. To force a reconnection test, in the Pool contents window under Actions, click the Ping link.
0eYl~$ T Oatabases I ""fddleware r 1I.13na,gemeontSystem ]
IHo~ltI '4i,l+fg;a·ID (IN....) IvCCn1tr) I~.,,) (WSlM) ICttGtnHOI Te:sul
VvlndovlSProxy Poolswill b~ttl€td in the orde<~hown.from top to bottom. Windov6Proxios will be chose«from tht' Pooisbasecton loading.Chang~the (Add .. )
order by dragging Wlndo'Ns ProX)' Pools to a new ptace In the-list
611If &I.r[C~~:i-l!b~ltiilldgi'illeU2~fRQI I Action ••
(6
lvp .. 'r~(ntilll(C4n.not KIlnIM,ddrc:;u:;)
StudentwindowsProxy·
Acliw
see Wi,'ldoWIS!oRil1 cr.:dt'llltl&lS
191..Itl.~O.2S:4323
0 ..' T'rti!)n This iso WindowsPro)lY
to.' 40121'
Pool
{'AaiO'M:
I\.anag~
Can gel IP..-6dt1l&but Wil'ldom\At,'stoll doesl'I<ol'::uppoll SC&l1nillRDisable
IPv6ftcldr~$
Ping
Test
All If: Addrfsses- OELiQ Delete I--
lyp, Cre<lt'otlaJ O~wptlOf\
11 p~ V. I f II.) I I , 1 Actions ..
Status: OI!3t1led by U~M
U~&C', Set'Wlndow5login (rec:lt'(ltiIJJ$
Vt'r~IOI't UOa'JiI Ii!blt'
I
The banner message indicates that the proxy StudentWindowsProxy has been contacted.
•
-

Ilom(' App!lci'luon", In(r2J!otructurf.> Rl'pOrl!l Admu'!s.trlltlon
o Windows Proxy StudentWindowsPnoxy contacted
Device Credentials
Lab 5.2: Configure Host Credentials
In this lab, we will add three host credentials, one host credential for UNIXand two host credentials
for Windows.
Task 1: Create a Host Credential for Windows

1. From the Discovery tab, click the Credentials button, then in the Devices tab, click Hosts.
..
OWI~s [ Datab.ses I MlddteWare- I Management sy..tem :
(WlndO''''''' PrCXIes) i"'MPI (..otrttrJ (~"·I (.....MI (CI!den'ill) 1t'I$,
( ShowMatchins Credenli.'s...) (AcId ...)
2. Click Add.
Page 24
3. On the Create Login Credential page, specify the following details:

• Matching Criteria: Select Match All
• Enabled: Select Enabled
• Username: BuiltInAdmin
• Description: Host credentials for Win1 Win2 and Win3 systems
•
Access Methods: windows (move rlogin, ssh, and telnet to Disabled)
Keep the rest of the settings as default.
4. ClickApply.
DeviCes I Oataba,.,. I Mlddlil\'/are I Management S;tstenl I
lim tWinllOWS Praxles) (lNMP) (-.<entet) (.,..,,,.) (""SEM) ICredential JeS1s)
Total Credentials: 2 (8y C1U:E's.s (TfI!rJloc/ ~ 1FltOG/u, 1 SSH. 1 TUNEr. 2 ~'f).NfXI.NS· c.rcdwr.w!.s (U."I auplytt'ltr1Of! tfoao onE ( Shcw ...ilchng '''"'''''t ..:.... ) (Add ..•)
."!Ieth~a·}
Host credentials willbe tried in the order shown, from top to bottom. Change-the-order by dragging credentials to a new placelnthe-ist.
All iP ".):11 ~e~ Ji:mlol Actions ...

Desc.npbQn Opbons Mett'>Ods-$5h l'I':'bI'f\. :f'11'ttt an" \\I(I!;IO'IIo1"
J.
u~!-
tllN'et u!:<e<l o;uw~':ttItll
.- CJ 1~IUfA='$.CL8.uiltloAdm~ib AdK)ns ~
Host clcdenUlllb fOI Vim 1 Vii" 2 tUld Wi., 3system31 /I,oIetl'lod. wir-dOM
t
I'tf!Vf!( csee SU((t.'.I$1UIfy
Task 2: Create a Host Credential for Windows

1. From the Devices tab under Hosts, clickAdd.
• Enabled: Select Enabled
• Username: Administrator
• Description: Host credentials for BladeLogicand student system
•
Access Methods: windows (move riogin, ssh, and telnet to Disabled)
3. ClickApply.
-uAll IP Addrgsm ..BlIjlllOArlmjn 1Actions ..
Oe<tr1pbon HO$l crtd-tl'lti(lls fOt "/in 1 Win l..and Win J ::)'stems OFtions M~thod: windl1Ws
t U~E.t
NeVHU$ed suC(essfully
,.,...U AIllP Addr..es5eS::,hdluiuistl'..atol 1Actions ..

.10$1cf(ld.entirlb for ","d(llo&ic find .o;tud~nl~~m M(l_thod' windo'f'l':>
t
N~V(lf used 5uccCl.'Tofuity
-
Page 25
Task3: Create a Second Host Credential for UNIX
1. From the Devices tab under Hosts, clickAdd.

• Enabled: Select the Enabled option
• Username: addm_user
• Description: Host credentials for UNIXsystem
• Access Methods: ssh (move telnet, rlogin, and windows to Disabled)
•
SU:Select the Switch User? option, ensure that Username is root and enter Password as
password
3. ClickApply.
..
Devices I Databases I /l.iiddleware I f\.iana.gement Sy~em •
(Wir.dq'IVS Praxies I ( SImp) IvCtr,1trl ('!5ph". ) (wsw) ICrtdtllt"'l Tells I

Total Credentials: 4 , 8y",,~..ltlef}!od ~ 1 P.J.OGlfI, 2 SSH. 1 fElJJtr ~ 3 V1'rNOO~'6 cferiGt1Uab (WI applytontol! tl,:1n 0/11" ISho\v tv1atdling Credentfals._) IAdd _ )
ftt?thodJ
Host credentials will be trted In the order sho\,lIl, from top to bottom. Change the order by draggln.g aedentials to a new plate In the list.
'lil~ , , 1Jll) Anions ..
I
.t. OtoiUlPbol'l cpuO-I'IS MtthOO!.1!h, ,1081""l~lnttanlJ.w,noows
U:::.ge
N'tVer u!ed rucce~ully
C) AIlIP 8d~rf:~~- BJJilllnAs:imin J..alons ..
I
OtWlption Host: eeeeouets tor Win 1Wln 2and Win 3 systems- opuens Mtthod: windows
t U'tO-S~
'~fVl!r esee sUCCMstUlfy
~ e 8111PM~r~Iii!lI-M!Ilini:i!!aIQ' Actloni ...
I
D!!scnptlon Hort<ftdtntlalstof 8f.adtloglc.and studtl'lt system Opbon~ Mtthod: wmdows
U1.4,t
Ntvtr used SUCC-fssfuity
o 6111P6s!!;t[~~~·su1gm y~~r ,
Aaloni ...
t1o:.1
crc(lc"'il'~'Of IJI'tIX~l'Im Mcthod:$'Ih
t
N(I'<I(l, u,xd "Jcco:;:::fully
Page 26
4. On the Device Credentials screen, drag the credentials (using the left edge of the bar,
displaying the vertical rearrangement arrows) to arrange them in an order per your
requirement.
~ oevtce Credenlials
-
Oevlces ( Da1:abaS5 I Middle-Wilre
Total Crldlntials:
mith"d)
(WlftdOWS prQ)Qts)
4
(IN··I
r syaJ;(~JJ'J('thcd
('o'(tnttf
+
[ Manasement
I
1 MOON
IVSpnere)
System
2SSH. t TWi',
1
1""'''1) ICrtdtnh&1 Tesh I
3 VtWoc;l{S -O€:JMhols eM opplyl~ (tren
Host aedenUalsYlIlI be tried In the- orde( shown, from top to bottom. Change the orde...by dragging credentials to a newptace in the fist.
Ina" one I
( Show "'atchlng Cre<l<nt.lals... (Add_1
06,11 Le69s.t[!l;i~~- ~"dU'l M~I Act,ons ..

tlo~ ~r(ldentiett:
for UNI)(~em MetJ\od· s:::" I
l NC!ver I.ClC'!d
~U'i:~ul'"
Actions -
6 611Ie6dd[e~:t·.e.~ll!illiaCASQ(
D~cflp' on Hott Cted(n~t$- for 81edel.0sic lind student ~m-m OrUon~ Melhod: wjndO'....~
~
U1a'~
Neyer u1fll ~uC(M~ully I
6 t\lIlf t:\dd[Ii:~'ics"Blliltlo&dlIlill Actions -
I
D!.'~atp~on Ho~ Cted-t'ntials:torWin 1 Win 2and Win 3 systMlS Op"on! Method: window~
~~Usog.
Nevtr US~ SuCCH$(uUy
'\Illi 1\ Actions·
D-e~"fpt.QtI OIJUon~ t.1~UI()d~nil ,Ioglr,. u'''!.'tanGwlf1dUW1
t U 4~1'
1" 'Itt I.Itt!)IU(Co!S!<fu 11
...
Task 4: Test the Created Credentials

1. For the addm_user credential, from its Actions menu, select Test to test the credential.
~3[abasg I "'lddll!W3r~ 1 Man3jec'nent S~tem I
GIll (Wi"dQW~ Ptaxlt\) ($N"p) I\l(tl'lle1) (,""""I Iwee",) (C'~clenlj~1resrs I
lotol credentials; 4 8y (rt'':fSi mrthoct 11UJ]",(N 2..";1,1 UiN[f.3+'r:N~ rrdmllof .. (a" apply 10 fr'W" In(,,, "n-r ( Show Mouthing Credentlals..y ) (~d-I
mtrhocl'
Host ,redentlals winbetned In the order shown, from top to bottom. Change the order by dr"gglng at'dentlclls to a newptace In theflit.
,_,
'UAlliE: AeJ{!I' e.lJS:f'-l- a~Jdln 1I!!P,l I Mlon. ;
ttOSl c(edfll\lleb (0' U~IX systflln Mfltll.od:ssl'l Edit
.Ii
Oi>obl.
... Nflve, U;gedsuccMSrul1y
DeI",•
Test
I
6 .811Ie l:!dd[e!l:l~'i·6timioili!IfltQC
De!cnpt:.on Host md~ntlals
1J·,IIa~
ter BiaOtlo&k end student system OptJor,~ M~thod: Windows:
Move to bottom J
Nty~r u'~d sucuss:tully
'-
o alii' AdgrC5sGI· lll!ilu[!aSlmiD Actions·
nesctpnen lion cft':dentials: tor Win 1WIn 2 and Wtn 3 !y'sttms: Optlont: Ml'tl'lod: w~ndOWS
'-
UI.II!:t"
N!.'Wt used succ:es:!:1uuy
I
,,1111 l\ Actions ...
Dt!(11ptIGn
" " OptJOI"lt'" Mt"thods: ssn "OlJ'I, teteee eoo wl~dow"
t U\lI!;e
Nt"II~r1J~~d~(.of~H)'
11
Page 27
2. The Test Device Credentials window opens; specify the IP address (192.168.0.5) to test the
credentials and click Test
Test Device Credentials 11
Address AilIP Add.resses
Oesaiption Host credentia;s for ljI'nx system

USCl'name addm_l)scr
Opt:iooS Methods.: ssh and teleet
se tc rcct
IP Address 1 ... 4 m 16&.05)X
I To>l I (C.n •• 1 I
3. View the result of the test
Device Credentials
DeVlce!o t oatabase-s I '~tddlev/are ro1anageme-nt system
[HII1U) IWind4Yls Pr~tS I ($NMP I (\l(tn1f:r I l\lSptttrt I I¥t1IEM J 8UB.9,ii"d
Test Type Submission Time Start 'rime
Mon Mar1607:11:49201S Mon Mar1607:11:492.01S 12se<ond-s ~ I B.W
4. Similarly you can test the other credentials against any of the indicated IP addresses:
• For addm_user: 192.168.0.5,192.168.0.6,192.168.0.7
• For Administrator: 192.168.0.1,192.168.0.25
• For BuiltInAdmin: 192.168.0.2,192.168.0.3,192.168.0.4
Page 28
Lab 5.3: Configure a Full Discovery Scan
Task 1: Start the Discovery Scan
1. From the Discovery tab, verify that Discovery is running.

• If it is not running, from the Discovery tab, click Discovery Status and start Discovery by
clicking the Start All Scans button.
3. On the Add a New Run window, specify the following details:
• Type: Snapshot
• Range: 192.168.0.1-25
• Level: Full Discovery
• Label: First Full Discovery Scan
4. ClickOK
1. From the Recent Runs tab, explore the latest run by clicking the label (First Full Discovery
Scan) for the scan.
2. Browse through the Discovery Run result and discuss the various statuses under the Summary
section with your instructor.
3. In the Summary section of the scan result, click the link next to Hosts.
4. Note the result for hosts.
f' Host List
o CustomJze
Select: @ I Nan. ) Iinven ) II Actions - ) I Reports - ) IV-""alizatlons -) Found 7 items 10.092 seconds), shovling 1 to 7.
r blapp t-dicrosoft® WindovJSSeNer® 1(1(:6 Enterprise VMware.lnc. Yes "/"'r-;e~

VQorsicn 6.0..6002 Build 6002
r red1 Fled Hat Enterprlset.lnux Server release 5.6 VMware,ln" Yes NI"'iSit IV!}" set N-=-rse~
(Tikanga)
r reez Red Hat Enterpriselinux SeIVe< release 5.6 v",1ware.lnc. Yes NfJrset NOiset f1i'Jrsf'f
(Tikanga)
r red3 Red Hat € nt erprise linux Server release S.3 VlI,1ware.lnc. Yes NO(Sff N!>;-sft r/'Ji5C(
(Tikanga)
r wln1 r.4tcxosoft(R) Wlndo'NS(R) Server 2003 standard VMware.lnc. Yes folOi ;£"t ,Votsn AI'J( _,;t'f
x64 EdltionVersion 5.2.3790Bulld 3790
r Wln2 MIO"Osott(R:) Wlndo'M(fl) Server 2003 StDndard V""ware.lnc. Yes ",'Of st: NOlsn Notsrt
x64 EdItion Vtorslon 5.2.3790Build 3790
r wln3 Mlaosoft;(R) WlndoM(1tl Sif'Vtr 2003 Standard V""war •• me. YIS Norfttt NotSH N~r.. t
.64 Edition V.rsJon 5.2.1mBulld 3790
Page 29
Lab 5.4: Configuring Additional Database and Application

Discovery
Task 1: Start the BladeLogic Services

1. To access BladeLogic from your desktop, double-click the bJapp icon.
2. On the BladeLogic server desktop that opens, double-click the Services shortcut.
3. In the Services window that opens, locate and verify that the following services are running:
• BladeLogic Application Server
• SQLServer (MSSQLSERVER)
• BMCServer Automation RSCDAgent
If any service is not running, right-click it and select Start.
Note: Before the BladeLogic Application Service can start, ensure that the BMC Server
Automation RSCD Agent and the SQL Server services are running.
4. Close this window and return to the BMCAtrium Discovery UI.
Task 2: Configure and Verify SQLCredentials

1. From the Discovery tab, click Credentials, then click the Databases tab.
Hom? Appllt:at.on~ Infrastructure DISCOVery Reports AdmInistration OISJCovery_Applis'ru;e- 10.1
( Ch(OVtrySl~111$) •• #.I@i#, ( i(nQ'",ledgt Monbgemcnl) ( IttltSf61ion Polnl$) ( SNMPRtcogni1ion) ,( CiH9VtryRt:porl)) [ToOI$)
~ Database Credentials
Gin.., OR? RORt-iS UNC:f u~O~rt"~IUt Actions ...

')'Pt SQl
Cfcd~tiolS' 0 Queries: S
A ...icrosoft SOL Seiver iO'Su,o:e.~s~!:J~z F!tI..ft!) ActIons ...

ly-;it SQl
Crtdtntia'$.': 1
2. For Microsoft SQL Server, click the Credentials link.
Page 30
3. To create new database credentials, on the Credentials tab, click Create.

Discovery> OZitaba,. Credentials> Microsoft SQl Server
Q) Microsoft SQL Server

DetaIl, I Credential,(') I Queries(25) I ( C(~ate I
.. Credentials
II
Credentials Wilt be tried In the order sho·wn. from top to' bcuem, Changtthto order by driggrngcredenttilti to a newpr.aceln thell.st.
A. ro",al demo '... ",.,. .. " " «c, I Actions·

rrt rHUIl • MSSQLQuerl., OHo1ptlonsqUtf'J'(Oft.c:tp01ntoohon:).! sot 0rfV('f fr not GllftflCly "".I\ttIM
4. On the Create New Credential screen that opens, specify the following details:
• Name: MS_SQL_Credentials
• Enabled: Select this option
• Description: MS SQLCredentials
• Username: sa
• Password: sa
• Database Driver: Microsoft SQLServer aTDS Driver 1.2.7)
• Database IP Address: Select Match All
5. Keep the remaining settings at default value and click Apply.
6. On the Credentials screen, drag the newly created database credential to the top of the list
using the left edge of the bar.
7. To test this credential, select Test from the Actions menu.
Q) Microsoft SQL Server
Oet&ils r Cr«feotials (2) ( Quer j es (2S) ( Create I
I Crpdpntidl..>
(rtdtntlaJs. wlflb. tned In the ordtr1ohov«l. (rum topto bottom. Chinge the order by dr~Uifl£ credentials. to iI new place In Chi !lr.t. _. __
AatOI"l$ ..
"t,tS SQL "CdillllUiils
.j. ,-~II ... M.S$QU)uc:ric.: Oear¥tioN(lue-ryl:crApoirlt"4lo.sC • i't<·jtcl'J~tk:rvcf:l/e"tlpoi'\1 Edit
pon:--·~mflte"., ...e-, "~t~beo$lt;'·V$""kY&kIt·. Ot",bl.
u. _pe .'a m<!:I c ,~. CMfl1 pic WiLle 1.
I "'m'''9 d""o:o,",,,,,,,,.,.
c.d
r.<i ~
1 -.sl Co~y
TPL (Mult; .. MSSQlQuMiM.06aiptiOruQu!Cy(encpoitIC~ I$.l SQl OtlVK Is not currf.ntly <!vallaDII! oelM~
--
Move to bottom
8. On the Test Credential window that opens, type 192.168.0.1 in the Database IP Address field
and click Test
- .w. .0
Ot'"rv.: Mlcro~ SQt. SHYer (jTOS Ortvtf 1,2,.7)
.. Oiitab.ase.IP A:fdtess:
f19i168A'
0 M~ch
" R(lflp:: Q_!). ?(o.'ll~
Pon: I
O"UlbaS6ll\$UrQc~mlli: I
AdditionaIJDBcpara.m£teJs: J
I Tt>t I( Oncti I
Page 31
9. Verify the test results, which should indicate success.

Test Results
I' SUCCtss· (onnlC( to "jdbc:Jtd~sql$!rv!r:'/192.16S.o.1" at coday at 07:25:3'5 r1!"lUISl.d bysyst.f:m Rtmovt! Rettst
Task 3: Perform a Full Discovery Run
1. From the Discovery tab, click Discovery Status and clickAdd a New Run.
• Type: Snapshot
• Range: 192.168.0.1
• Label: Full Discovery Scan for BladeLogic
3. ClickOK
Task 4: View the Results of the Full Discovery Run
1. From the Recent Runs tab, explore the latest run by clicking the label (Full Discovery Scan for
BladeLogic) for the scan.
~ Discovery is RUNNING '](,'1 "iilt in

_I
FuIlOl$COv~sao(or "2.'6&.0.1 1
BI.dl>logtc
2. Navigate to the Summary section and click the link next to Hosts.
o Summary
Hosts 1
Network Devices 0
Storage Devices 0
Star age Systems 0
Printers 0
Page 32
Host' blapp
1ActiOns.' 1R€OOltS .) 1ViSuali!ations., 1_00 ., ( Software Context II Hld.AlII I Show Provenance I
o Geoe@1 Details --
software Context ! •,
Name bJapp
Hard'''Iare Vendor VMVlat'e'iinc..
Virtual 16
Virtualization Oass VMwa~
software Instances a 5gftwar~ Inganrp<. ~attd
Runtime Environments 3; RlIlIjJrntEn«pnme:oI$ retat,ed
Files c!\WQdow?ymdygRtgNwmI
4. From the Visualizations menu, select Running Software.
Host: blapp
1 Action•• ) 1 R""ort.:0 ",,,,aloul,,,,,, - (llolijed ., (softvmecontextll Hid.AlIIi Showprov.... 'nc.1
.t9p1icatlon 00pMd_ ·Appli<3'i<>n V.e",
o General Details Ap~K>n Oepern:Ienoes· SottwareVJew
AutomatIC Groupng Of!(a:d
Name b ~enng
Folo Sy1tern Depend_
Type J"
FlIe Sy1tem Dependences· Detail
Hardware vendor HOlt Cor«atnn"~
Host Coot~ With SOftware
Vinual
Inf.erred So~ Communication
villualluition Oass '" Inferred SOI\w.n Oependoncy
lnfr.Jstrudure
Software Instances !l! l-' a.Ian<Ing
RuntimeF.nvironmeots 1. Netv",rkTopoIogy . Neighbor
J ObsorledC~·l.fostVi""
FiI~ ~ Ob$erved COf'I'Wl'M'NCatIOn· Prot:ess, View
Observed CO''I','I",_tlon· Software View
o Identity RuonIni SOftware
Vittua"'uuon
5. Verifyyour result.
Running Software visualization ~O( blapp

loom & Pan(ooltets
~utConbol.
Ptlnting & &;POrt Controls
l~
Rooc_
-
Page 33
Module 6: Query Language Overview
Lab 6.1: Running Simple Searches
Task 1: Create a Query to Search for Hosts, Runtime Environments, Software Instances, and
Discovered Files
1. On the search bar, click the Search icon.
2. To open the Search Query window, click the Generic Search Query link.
3. In the Search Query window, type each of the following search queries and click the Run
Query button after each query.
a. SEARCH host
b. SEARCH RuntimeEnvironment
c. SEARCH Software Instance
d. SEARCH DiscoveredFile
Note: The first search query will fail because the search query is case sensitive.
Lab 6.2: Searching with the WHERE Clause
Task 1: Run a Search Query using the WHERE Clause

2. Click Generic Search Query.
=
a. SEARCH Host WHERE os "SunOS 5.10"
This search returns all OSvalues that contain SUNOSS.10.
b. SEARCH Host WHERE os <> "Sun OS 5.10"
This search returns all OS values that do not contain SUNOSS.10.
c. SEARCH Host WHERE name has substring "Win"
This search returns all Name values that contain the substring 'Win'.
d. SEARCH Host WHERE name has subword "Win"
This search returns all Name values that contain the word Win.
Page 34
Lab 6.3: Searching Using WHERE and AND CLAUSES
Task 1: Run a Search Query using the WHEREand Clauses

In this task, you will:
• Execute a search query to display hosts with as SunOS 5.10 and vendor Sun
Microsystems.
• Execute a search query to display hosts with as SunOS 5.10 and vendors other than Sun
Microsystems.

a. SEARCHHost WHEREos = "SunOS S.10" ANDvendor = "Sun Microsystems"
b. SEARCHHost WHEREos = "SunOS S.10" ANDvendor NOTmatches "Sun Microsystems"
Lab 6.4: Searching With the Regular Expression Syntax
Task 1: Run a Search Query using the Regular Expression Syntax

• Execute a search query to display hosts whose name have a suffix 01app.
• Execute a search query to display host, which returns all values whose name has a suffix
OZapp.

a. SEARCHHost WHEREname matches 'Olapp$
This search returns values all values whose name has a suffix 01app.
b. SEARCHHost WHEREname matches '02aPP$'
c. This search will not return any results, as the searches are case sensitive and the host names
do not contain aPP.
d. SEARCHHost WHEREname matches '(?ij02aPP$'
This search returns values all values whose name has a suffix 02app. (?i) ignores the case of
the string.
Page 35
Task 2: Run a Search Query Using the Regular Expression Syntax

• Execute a search query to display hosts, whose name contain 0 and app, and vendor
name contains sun at the beginning of the string.
name does not contain sun at the beginning of the string.
- SEARCHHost WHEREname matches '(?ijO*App$' AND vendor matches '(?i)"sun'
Note:
The asterisk symbol (*) in a search string matches zero or more repetitions of the preceding regular
expression. For example, ab* will match a, ab, or a followed by any number ofb's.
The caret symbol (/I.) in a search string matches the start of the string.
The search string '(?i)O*App$' elements can be explained as follows:
- (?i) ignores the case in the search.
- (?i)O*App$ will match a string with App at the end, preceded by a o.
SEARCHHost WHEREname matches '(?ijO*App$' AND vendor NOTmatches '(?i)"sun'
This search will return results where the Name contains the suffix app and Hardware
Vendor does not contain sun.
Note:
- (?i) ignores the casing in the search.
- /I. matches sun at the start of the string.
Task 3: Run a Search Query using the Regular Expression Syntax

name contains sun at the beginning of the string. Also, display the summary and RAM
details for the hosts.
name contains sun at the beginning of the string. Also, display the summary and RAM
details for the hosts. The RAM column should be displayed as Memory.
a. SEARCHHost WHEREname matches '(?ijO*App$' AND vendor matches '(?i)"'sun'SHOW
summary, ram
b. SEARCHHost WHEREname matches '(?ijO*App$' AND vendor matches '(?ijAsun' SHOW
summary, ram AS "Memory".
Page 36
Practice Exercise 1: Using the Advanced Query Language
This is a practice exercise to revise how to use the advanced query language.
Query 1: Write a query to display all hosts with the following attributes:
• Host name
• Host type
• AlIOS attributes
Tips:
• To find all possible OS attributes, check the list (navigate from the Administration tab and click
View Taxonomy) .
• Search the page using <Ctrl + F> 'OS '. (Notice that there is a space after OS.)
Query 2: Write a query to refine the first query with these conditions:
• Limit the results to only Windows hosts.
• Include attributes for operating system, memory (RAM),vendor, model, service pack,
domain, virtual.
Query 3: Refine the preceding query with this condition:
• Limit the results by Windows hosts having any service pack details.
Query 4: Refine the preceding query with this condition:
• Limit the results by Windows hosts not having any service pack details.
Query 5: Refine the preceding query with these conditions:
• Display all hosts except Windows.
• Remove the service pack and Windows-specific attributes.
• Include attributes for operating system, memory (RAM),vendor, and model.
Query 6: Refine the preceding query with these conditions:
• Limit the result by hosts having power supply status details.
• Display the total package count
Suggested Solutions:
• For Query 1: SEARCHHost SHOW hostname, hosttype, os, os_type, os_version, os_edition,
os_build
• For Query 2: SEARCHHost WHERE os_class = 'Windows' SHOW hostname, os, ram, vendor,
model, service_pack, domain, virtual
• For Query 3: SEARCHHost WHERE os_class = 'Windows' AND service_pack is defined
SHOW hostname, os, ram, vendor, model, service_pack, domain, virtual
• For Query 4: SEARCHHost WHERE os_class = 'Windows' AND service_pack is not defined
SHOW hostname, os, ram, vendor, model, service_pack, domain, virtual
Page 37
Tip: Alternately, you can write the query section as os matches Windows, instead of
os.class = 'Windows'.
• For Query 5: SEARCHHost WHERE osclass <> 'Windows' SHOW hostname, os, os_edition,
os.build, ram, vendor, model
• For Query 6: SEARCHHost WHERE os.class <> 'Windows' AND psustatus is defined SHOW
hostname, os, osedition, osbuild, ram, vendor, model, psustatus, packagecount
Lab 6.5: Using the ORDER BY Clause
Task 1: Run a Search Query using the ORDER BY Clause

• Execute a search query to sort the hosts by OS.
• Execute a search query to first sort the hosts by OS and then by host name.
a. SEARCH Host ORDER BY os
b. SEARCH Host ORDER BY es, hostname
Lab 6.6: Using the EXPLODE Clause
Task 1: Run a Search Query using the EXPLODE Clause

In this task, you will execute a search query that will return the tags in a new line.
Query button after the query.
a. SEARCH Pattern SHOW name, EXPLODE tags. This search will return the tags in a new line.
Note: The result of such a query has comma-separated tags, which enables you to see
each tag on a different line.
Page 38
Lab 6.7: Using Key Expressions
Task 1: Run a Search Query using the TRAVERSE Clause

• Execute a search query to return results for host lonlp0350db and a list of its running
software
• Execute a search query to return results for host lonlp0350db and a list of its running
software. The column Name should be displayed as 51.
• Execute a search query to return SI details as summary for host lonlp0350db.

a. SEARCH Host WHERE hostname = '/onlp0350db'
show summary,
#Host:HostedSojtware:RunningSojtware:Sojtwarelnstance.name
b. SEARCH Host WHERE hostname = '/onlp0350db'
show summary,
#Host:HostedSojtware:RunningSojtware:Sojtwarelnstance.name as SI
c. SEARCH Host WHERE hostname = '/onlp0350db'
show summary, explode #Host:HostedSojtware:RunningSojtware:Sojtwarelnstance.name
as SI
Note: Summary is not an attribute. It is a keyword used to display the taxonomy-defined summary
list in the search results.
Lab 6.8: Using the TRAVERSE Clause
Task 1: Run a Search Query using the TRAVERSE Clause

• Execute a search query to display software running on Solaris operating systems using the
specified traversal.
• Execute a search query to display the software running on the host lonlp0350db, using the
specified traversal and displays the summary.
• Execute a search query to return SI details as summary for host lonlp0350db.
• Execute a search query to display the summary for the software running on the host named
lonlp0350db.
Page 39
a. SEARCH Host WHERE os_type:: 'So/aris' TRAVERSE
Host:HostedSo/tWare:RunningSojtware:Sojtwarelnstance
b. SEARCH Host WHERE hostname:: 'lonlp0350db'TRAVERSE
Host:HostedSo/tWare:RunningSojtware:Sojtwarelnstance SHOW summary
c. SEARCH Host WHERE nonname» '/onlp0350db'
SHOW summary, #Host:HostedSojtware:RunningSojtware:Sojtwarelnstance.name
Instruction: Discuss how the second and third queries differ in their result.
Lab 6.9: Using the EXPAND Clause
Task 1: Run a Search Query using the EXPAND Clause

In this task, you will execute a search query to display the node kind and the number of software
instance nodes for the host lonlp0350db.
1. On the search bar, clickthe Search icon.
2. ClickGeneric Search Query.
SEARCH Host WHERE hostname» 'lonlp0350db' EXPAND
Host:HostedSoftware:Runn;ngSoftware:Softwarelnstance SHOW summary
Task 2: Run a Search Query using the TRAVERSE Clause and Compare the Results with that of the
EXPAND Clause
In this task, you will execute a search query to display the software instance list for the host
lonlp0350db.
SEARCH Host WHERE hostname» 'lonlp0350db' TRAVERSE
Host:HostedSoftware:Runn;ngSoftware:Softwarelnstance SHOW summary
Instructions: Discuss how the TRAVERSEclause and EXPANDclause queries differ in their result.
Page 40
Lab 6.10: Using the NODECOUNT Clause
Task 1: Run a Search Query using the NODECOUNT Clause

• Execute a search query to display the names of business applications and the number of
business application instances dependent on them.
• Execute a search query to display the summary information for hosts having more than
10 software instances running on them.
• Execute a search query to display the names of hosts and the number of software
instances running on them.
a. SEARCH BusinessApplicationlnstance SHOW name, NODECOUNT(TRAVERSE
DependedUpan:Dependency:Dependant:BusinessApplicationlnstance)
b. SEARCH Host
WHERE NODECOUNT (TRAVERSE
Host:HostedSoftware:RunningSoftware:Softwarelnstance) > 10
c. SEARCH Host
SHOW name, NODECOUNT (TRAVERSE
Host:HostedSoftware:RunningSoftware:Softwarelnstance)
Lab 6.11: Using the PROCESSWITH Clause
Task 1: Run a Search Query using the PROCESSWITH Clause

In this task, you will execute a search query to display the commands, corresponding arguments
and the Discovered Process count
SEARCH DiscoveredProcess
SHOW cmd, args
PROCESSWITH countUnique(O)
This search displays the commands, corresponding arguments, and the Discovered Process
count.
Page 41
Module 7: Clustering
Lab 7.1: Create a Cluster
Task 1: Create a Cluster

1. From the Administration tab, in the Appliance section, clickCluster Management. This
launches the Cluster Management page.
Administration> OuStr2J' Management
~ Cluster Mana6erient
Create a new duster Join an existing cluster

""" cpn Cl'f'Ote" dust" Itttl' riilS madhl1t 0'; the 1tu~ ffl(tcil/f1t cannot join lin exiron: clust-er{ofthe
c~ foiJr>llIflg rr.7SO:"!~
l'ihi1i ::t !'.\.-s"u-.'$ first (re!JfE'd. S~"i"€m .iC'f\r,ces I't'iii bE
f \-\'i'bC ogrclrlte.gr(Jfron (.re(/€ntl{l! {ctlnd
""""'" 6SQtlnttg(oltOn crct1tf1(I('t!S [f)v(ld
r iI/trIP (Jec/eflfJal/ound
1 mrun/ra.'np crederoilal found
J j.}(t;ff_PooJ r-rfX[enruf,s lO'.Jnd
, i!SOh'illntpgriJtl'Of1 cmltfiriU! found
2ikNe [rtrienti<hl found
Alcgill c(edmti!1B found
1 IICtn:FrlnieyrorlC(? (redell-traf {ot1nd
t (<<hide range {oond
5 Disc¢VfIVR!1I' Ilod~ /O'.Jnu
166 Hostncdes. ft)f;nrJ
4 Nf'rWf>ri:Dwir.f'flOOes {Qund
1t Fnnter nOdes [r>u(lO
SSNMP,\t~eriD£v;(e nodes fovr.d
Usm have OM'! mOdl{teu
(' ...... C10" ... '
YbtJ Ci1f'l fi',;?r rh(' (c.ntl8tJ(atlon ro df{oalr vn!~e:;. but
fi(xflg so ItlJidrs ...." 'pCS' err Jj"f2'to.,<of'
(Reset Conti uratlon
2. To create a new cluster, on the Cluster Management page, click Create Cluster.
Page 42
3. This opens the Create Cluster window.

Crellt. C1u!.1er ..
·aUSlerm~ .-----------------
OlJSterAlUs ,----------------
~~ J,;?_~ ....i'JP ®i:-<)'iQinO!m/ot refemn, to a{lme(J'liJ(bJ/io hi:;jl~

~: ~o-!c.+cetI ....~tr.t1C} ;oi :JfCOC,essrdr/lrc.ulh aload
.. CCOrdinator Address ......
o Sh!a!!(mrhnMdr,..-V5
J;autt Telerano! r ~~ dt.;..~~ ,OO{J>lJ.elOcpemtt

tn(JlJ!es:t I'.'W( 1'.'tUI'<
VYM~ rr .....~bYUl5UMirJ;::rall"!IlO,:5StM'flM
i'Sliavr/rrJr!'d
• ~1!'»Cj;.'I':i$. H::wwa: ."r(Qf FT)((qeC{)poc:.'Ycpd o-.'tI7X!
c~~t' lJn(?dtr:?d cs ;}Ctor.Sf(JIlilY.C!
.. Memter "dmesses
,---------------------
_"!all ... Ihc WI .,
_ClDf"tt. 09/t1f._"
rOSlOfft ditto
,.,U!tt' ~'Ifom ICl!t!.1' a( 11"(11
'Itlmtl'ffllM :nftt,(~.Htr'
'"
4. On the Create Cluster window, type the appropriate details:

• Cluster Name: Student Cluster
• Cluster Alias: Primary
• Coordinator Address: 192.168.0.10 (delete the existing localhost first)
• Fault Tolerance: (Leave cleared)
• Member Addresses: 192.168.0.9
5. ClickCreate. The machine lists pending cluster changes.
6. ClickCommit Changes. The machine displays an additional warning about the pending cluster
changes.
The foOawhg dlonge:s wiD be made:
• The cluster- and mertJ)ers will be reremed.

• The cluster aias d be changed.
• Adcltionel.nembetS wJl be synctvonlzed with the existing members 01 the cluSier.
• Member_ossa wi be chonged.
WA,RIIiII'«): Oeaa.g a CklSter requires th.!lt 81 services ere restarted on this machine.
Are you swe yw wsf'II to conmue?
OK Cancel
7. Click OK The cluster is created.
Note: This takes about 20-25 minutes.
Page43
8. Note that, after cluster creation, the appliance name changes to Student Cluster-Ol and its
login screen appears. Type the credentials systemjSystem1234$.
9. After logging in, the appliance opens to the Cluster Management page, which should now
display the details of the successful cluster creation.
BMC At' um otsccve-v & Dependency Mapp ICg
Home App!!catlons Inft;;;structuF~ Discovery Report$
6
AdminlstrOltion > duster-Management
~ Cluster tVanagement
Name Student Ouster- I

AliiJS primary ,
Summary All OPERATING NORMAllY
COordinator ThiSmachineIsth~ dust('( cocrdlnator
Fault Tolei'ance- Ois.abl~ (EnableFauItTolera-nce- )
Current f"v1en,bers IMion> -)

o Add Mernb!!f}
o Studf!lit Cluster-01 tI91..1t)'tn.10) Th~$l'nOchH'

Type: CoordlNtoJ AdMly:CltHl« MMlbet
V<llOrme:~d: free C8: foll.1 C;8: .... Co1It&ct: Ins lh¥J. nw.nt.IU' "P
lust ~ 9..30 14.18
~tI"h:Ok.
o ~ut1eJ\' dvstef 021192.16&:).9) 19Yimy Mpchine ACtklns ..

T.,.pe:M~btol AdMly: Oust« MH'Ib«
VClhrmc: usee: 'recGO; 1o'~IGe; lM Ccd.ect:kss thin. minw ago
lusr __ !JAi , .. 18
tf,eeltb: Ok
Notes:
• The cluster name and alias are as specified - Student Cluster and primary
• Fault Tolerance is disabled, as specified during cluster creation
• The machine Student Cluster-Ol (on 192.168.0.10) is the Cluster Coordinator and the machine
Student Cluster-02 (on 192.168.0.9) is the Cluster Member
Page 44
Notes (con't)
• The numbering postfix of member machines (-01, -02) is decided by the Cluster Coordinator
• The role of each cluster member is specified in the Type field
• You can view the member machine(s) by clicking the corresponding View Machine links
• The cluster member Student Cluster-02 can be removed be selecting it from its green vertical bar
and selecting Remove from the Actions menu
• You can perform cluster management actions for the cluster from this page
• You can perform actions for individual machines in the cluster from their corresponding Actions
menus
Task 2: View the Two Machines in the Cluster - the Cluster Coordinator and Cluster Member
1. On the Cluster Management page, click the View Machine link for the cluster member
Student Cluster-02. This launches the details of the cluster member in a new web browser.
2. Enter the credentials system/SystemI234$ for Student Cluster-02 and press ENTER
3. On the cluster member Student Cluster-02, from the Discovery tab, navigate to Credentials,
and under the Devices tab, click Windows Proxies.
4. View and note the credentials.
5. On the Cluster Coordinator Student Cluster-Of. navigate similarly to view the credentials.
Question for Discussion: What are the differences between the credentials displayed in these two
cluster machines?
Answer: There should be no difference between the displayed credentials. These credentials
belong to the cluster and are seen as identical from every machine in the cluster.
Page 45
Lab 7.2: Change the Cluster Coordinator
Task 1: Change the Cluster Coordinator
1. Under the Current Members section, for the cluster member Student Cluster-OZ, click the
Actions menu and select Make Coordinator.
Administration:> duster Management
~ ouster Managerlert
(Shutdown Ouster II__ Oust« )( ~n Oust ... SIMco. I[[n.bI ... alnten.nce MOdel
Name sc:udeo\ duster /

Alias primary I
Summary All OPERATING I\ORMALLY
Fault Tolerance Oiublt<l [ Eno1>l. Foutt Toltranc.1
Current Memt)el s
Actions·
Type: Coofl:llnltor AcIMly: ~ Mmbef
VokAme.: usee: '"uCB: lctelGB; I.asI CO~I.C1:IIHSfft1na~.
lyV
He.llh:Ok
_
!J.lO 1."
c:; St"'ot!nt Ou~et'-02 tI92.1b!lo.~ rC.View Madlin!! A(;tlons •
Type' Mrmb .., M1Mty: Ouu:~Mff'Dbef Change Address
YolUme:lliled: 'fuGR: totalGD: last eo"16a:tHs:tMnanil'llM. Ping
::"h:Ok 9.,49 14.18 Remove -;-,.-1
-'-==---------------------------------1 Make-Coordll\itor
RE-srart~r/l(B
Homt I ~(.a:!tGrI! IlIirffMIruttlft I tuceYtty I R!p$nS I ~I~. Reboot
Co~t 0 2OCO- 201" ~fN( SGttf0ft('"rvI (G~ In1om4.lbM) Sl'u..1doMl
Att1umOiUMI'fMII ~pt.~atyMa~'JIIef\lelL: 10.1Iiltltau,40111 1
2. The page refreshes to display a warning for pending changes. ClickCommit Changes.
3. On the second warning displayed, click OK.
4. The Discovery services restart View the details on the refreshed Cluster Management page.
5. After verification, revert the Cluster Coordinator to Student Cluster-Ol.
• Under the Current Members section, for the cluster member Student Cluster-Ol, clickthe
Actions menu and select Make Coordinator.
Important: This step (reverting the Cluster Coordinator to Student Cluster-Ol) is critical to
maintain continuity of the lab exercises.
Warning: Ifyou do not revert the Cluster Coordinator to Student Cluster-Ol, at the conclusion of
Lab 7.5, you will lose all data in Student Cluster-Ol and you will not be able to successfully
perform any subsequent lab.
Page 46
Lab 7.3: Enable Fault Tolerance in the Cluster
Task 1: Enable Fault Tolerance in the Cluster

1. On the Cluster Management page, click Enable Fault Tolerance.
Admlnrs:trZltJon> duster Management
~ ClllStel ManageMent
Name Studeot Ou:.ter '
Alias pr'imary I
summary AllOPfRATING NORMALLY
coordinator This-machine IS the duster CoordlOilto..-
Fault Tolerance Disabled
2. The page refreshes to display a warning for pending changes. Click Commit Changes.
3. On the second warning displayed (to enable Fault Tolerance), click OK When you click OK, the
Summary field displays the rebalancing progress.
4. After rebalancing concludes, verify that fault tolerance is now enabled.
Page 47
Lab 7.4: Run a Full Discovery Scan from the Created Cluster
Task 1: Run a Full Discovery Scan from the Cluster
1. On the cluster member Student Cluster-Ilf, from the Discovery tab, click Discovery Status
and click Add a New Run.
• Type: Snapshot
• Range: 192.168.0.1-25
• Label: Cluster Scan
3. ClickOK
(Ensure that Discovery is running.)
Task 2: View the Results of the Full Discovery Run
1. On the cluster member Student Cluster-Irl, from the Recent Runs tab, explore the latest run
by clicking the label (Cluster Scan) for the scan.
_CUf!~pr~es.SI~~ ~Runs L~~n$LEXd~Ranges ) QAddNewRun o AddNgow£xdud?
Showing 6 comp1-e-ted Discove-IY Runs
Ouster Scan 2$ ~01$-Q3.11

06:~1 -
06GS0C29(~
2. Navigate to the Summary section and view the results.

3. Now, on the cluster member Student Cluster-02, from the Recent Runs tab, explore the latest
run by clicking the label (Cluster Scan) for the scan.
Tip: Use the credentials system/SystemI234$ to log in to Student Cluster-02.
Questions for Discussion:
1. What are the differences between the Cluster Scan results for these two cluster machines
(Student Cluster-OI and Student Cluster-02)?
Answer: The results as viewed from either machine will be identical in every way.
2. What are the differences between the First Full Discovery Scan results and the Cluster Scan
results?
Answer: There will be no difference between these two scans. The scan First Full Discovery Scan
was a full discovery scan for the IPs 192.168.0.1-25. The scan Cluster Scan is also a full discovery
scan for the IPs 192.168.0.1-25 from a cluster configuration. As you increase number of machines in
a cluster, the scanning time decreases significantly.
This step concludes this lab exercise.
Page 48
Lab 7.5: Remove a Cluster Member from the Cluster
Task 1: Remove a Cluster Member from the Cluster

1. From Student Cluster-Ol (on 192.168.0.10), from the Administration tab, under the
Appliance section, clickCluster Management.
2. On the Discovery Management page, under Current Members, select Student Cluster-02.
dministration > duster Management
~ Cluster tv"anager.ent
( Shutdo:wn Cluster I' Reboot (luster II Restart (luster Services II Enable M<lintenanc;e fl.1ode I
Name StudMtOu5tet'1
Alias pnIlliry _,
SUmmory AU.0PfRA11~G ~ORMAU.Y
Coordinator This mad'llnfo tJ tnt Ousttr(OOr4l1'1Dtor
Fl)ull TolQ(onee 0iAbItd ( En.bl. Flul. TOI."neol
CL rrent Members [ActIons .. )

o Add Membe:fTi
Acttons ...
type: CoordlMtof Ac'tNily: Ouner MHnber
Vo1t.lme; IJ:;ed~ tree CI: Tol.' G~ la~ t;onta<t: IC'$$tNn 0 minute 4g0
/u" '.2.9 14.1&
tita.I'I:Ok
(:) StudMt Ousw...o2(192.1DS.o..9') :9yigw "'amine ACtions ..

Type; M~b:Cf ActNily:Oustcr Member ChangeAddress
~ Ve-lUme: used: If"« GIS:: Tel.' Ci.e: last COfltl'l<:t: Ie-sswn a mlnutl!-ago
JU$T _
941 1.411 PIIlg~----1
Hee_ltI:Ok
R.emove-
------ Ma~ Coordinator
Rl'Start $eorv"&,,,
KGI:lt", ~t.oeictl' IIr.funUurlure IOistcr~1'J I Rt"ports I AdmlllhtroliCI1 Reboot
(e~ 02003.1'01'l9BMC Sc:I!twa,t{Rl11 C41¥ff" (nr(ltmali(ln> Shl,JtdD M'l
AlII_ tMlOiltryand Otptl]d~lI_ry MapplngVtcston: 10..1Rtl~ast: «J1211
3. From the Actions menu, select Remove.
Important: Ensure that removal is that of the member machine Student Cluster-02.
4. ClickOK to all verification/warning screens.
Important/Critical: The removal of a member from a cluster can take up to 20-25 minutes (for
rebalancing and recompiling of patterns). Wait for the screen to automatically refresh before
proceeding with any other action in the lab exercises.
5. After successful removal, the cluster should rebalance and revert to two standalone BMC
Atrium Discovery appliances.
6. Confirm the following:
• The name of Student Cluster-02 is reset to Discovery_Appliance.
• The password for Student Cluster-02 is reset to 'system.'
• Alldata in Student Cluster-02 is erased.
• Credentials will need to be added again to Student Cluster-02
• The name and password for Student Cluster-Ol remain the same.
Page 49
• At the bottom of the Cluster Manager page, Student Cluster-02 is displayed in the
Previous Members section. You can select a previous member from that section and from
the Actions menu, click Dismiss.
Tip: The name Student Cluster-O! can be changed from the Appliance Configuration section of the
machine. (On the Administration page, under the Appliance section, click Configuration and
change the name as desired in the Name field, then click Apply at the bottom of the page.)
This step concludes this lab exercise.
Page SO
Module 8: Consolidation
Lab 8.1: Set Up Consolidation
Task 1: Rename the Appliance to Consolidating Appliance
1. On the ADDMDemo VA(192.168.0.10) UI,in the Administration tab, under the Appliance
section, click Configuration.
2. In the Name field, change Student Cluster-O! to Consolidating Appliance.
3. Scroll down the page and clickApply. The appliance name changes.
Home.- ApplicatIons Infrastructure Discovery Re-ports __
Task 2: Set Up an Appliance as a Consolidating Appliance
1. From the Administration tab, under the Discovery section, click Discovery Consolidation.
Logout
Administration:> Discovery Consolidation
~ Discovery Consolidation
,------------------------------.
This system 11asnot been 5tHup for .onscllda~')n ('hoW ',Ipl
I Set as Consolidation Apptfance J (SetasScanlling~ptlance )
2. ClickSet as Consolidation Appliance. This sets the appliance as a consolidation appliance.
Task 3: Set Up an Appliance as a Scanning Appliance
1. On the ADDMClean VA(192.168.0.9) UI,in the Administration tab, under the Appliance
section, click Discovery Consolidation.
2. Note the instruction on the page to change the default appliance name (Discovery_Appliance)
before it can be used for consolidation. Clickthe System Configuration page link.
3. In the Name field, change Discovery_Appliance to Scanning Appliance.
4. Scroll down the page and clickApply. The appliance name changes.
5. From the Administration tab, under the Discovery section, click Discovery Consolidation.
6. ClickSet as Scanning Appliance. This opens the Add New Consolidation Appliance window.
Page 51
7. On the Add New Consolidation Appliance window, enter the following details:
• Name: Leave as default (Scanning_Appliance)
• Consolidation Appliance: 192.168.0.10
• Username: system
• Password: System1234$
8. ClickSubmit. The page redirects to the Consolidation page.
BlltlCAtrium Discovery & Dependency Mapping
Heme Apphc~Uo(l!' In(("~lIlj'llJr(' O!~O'l~"ry R('f)Orl~ •
e
Admrnlstr3tron > Discovery consolidation
~ Consolidation: Scanning System
~ C ThisScanningSystem is sendillgdata to 'I COllsolidationSystetn IAdd new Consolldatlon,Af?pliance ) ~~~~!Ci!~~

Consolidation Syl>teJn last Data Push CA Certificate Flogelprint ActIons
Consotldating AflpJlance SA:69:5O:F2:~9:CC:35:36:D9:E6:eE:17;BF:88:E 3:1S:OC:3C:7E Approved I~ete I

) T~ Connt"Ctlon)
9. ClickTest Connection to verify the consolidation. Under the Test Connection button, the
appliance should display Connection Successful.
Lab 8.2: Run a Scan from the Scanning Device and Verify It Is
Sent to the Consolidator
Task 1: Start the Discovery Scan from the Scanning Device
First, verify that the credentials have been added to the Scanning Appliance and that Discovery is
running on both the Scanning Appliance and the Consolidation Appliance. (If it is not running, on
the Discovery tab of the desired appliance, click Discovery Status and start Discovery by clicking
the Start All Scans button.)
2. On the Add a New Run window, specify the following details:
• Type: Snapshot
• Range: 192.168.0.1-25
• Label: Consolidation Run
3. ClickOK
4. From the Recent Runs tab, explore the latest run by clicking the label Consolidation Run.
5. View the results.
Page 52
Task 2: Verify the Discovery Scan Sent from the Scanning Device to the Consolidation Device
1. On the Demo VA(192.168.0.10) UI, in the Discovery tab, click Discovery Status and then click
the Recent Runs tab.
2. Youshould be able to see a scan labeled Consolidation Run.
3. Clickthe label of this run.
4. Scroll down to the Status section.
Start Time 17/031201512:10:19
End Time 11/031201512.."11:14
Duration OOO:OOCSS
Number' of IPs scanned 10
Number of IPs Dropped ~
fndpoints 10 Disroyery Accesses related
Provider Accesses 1 PrQy!derAqW ((:fated
nbcevery stan ttme 17103I20151W3.,1J6
Discovery End Time 17/03/201512.:07:43
Consolidated From ScanntngAppliance-
Consolidation Data last 171031201512.40:19

Received
Number of IPs COnsolidated 25
The Consolidated From field displays the source of this scan (Scanning_Appliance).
Page 53
BMC Atrium Discovery and Dependency Mapping PREPBoot Camp LAB GUIDE
Module 10: Using BMC Atrium Discovery Cli
lab 10.1: Starting Discovery from the Cli
Notes:
• Use PuTTY to access the CLI.
• Do not perform this on a production appliance without prior approval.
Task 1: Start a Scan from the CLI by using the Utility tw_scan_control
1. Typetw_scan...controI172.17.150.20-25, 172.17.1.130-135, 172.17.1.109,172.17.1.23.
Note: In the command, ensure that there is a space after control, and comma
tw_scan...control<space>172.17.150.20-25,<space>172.17.1.130-
135,<space>172.17.1.109,<space>172.17.1.23
2. Enter the password as System1234$.

3. Navigate to the Discovery tab.
4. In the Discovery Status tab, click Recent Runs. Check if the run was executed. If the run has
not been executed, it will be displayed in the Currently Processing Runs tab.
lab 10.2: Deleting a User from the Cli
For this exercise, we will delete the user student, created in Lab 3.3 (using the tw_adduser utility).
You may also delete any other user that you have created in the lab.
Task 1: Delete an Existing User from the CLI

1. Type tw_deluser student This command will delete the user named student.
Note: If you do not get any result displayed on the CLI,then the user has been successfully deleted.
2. Type tw_listusers --filter= student: This command searches for a user named student.
Note: This step is just to confirm deletion. If you do not get any result displayed on the CLI,the user
has been successfully deleted.
Page 54
Module 11: Appliance Support
Lab 11.1: Downloading Logs for Customer Support
Task 1: Download log File export-creds.log

1. In the browser, access the Demo VAappliance at 192.168.0.10.
2. Navigate to Administration.
3. In the Appliance section, click Logs. The Log Files table will be displayed.
4. In the export-creds.log row, click the Download link To view the download, navigate to the
Downloads folder on the desktop.
Page 55
Module 12: Collaborative Application Mapping
In this exercise, the instructor will demonstrate the basic functionality of how Collaborative
Application Mapping (CAM) is used to map a business application:
• Search, investigate, and create a prototype
• Define functional components
• Map the application
Page 56
Module 13: Edit Pattern Templates
Lab 13.1: Edit a Simple 51 Pattern Template
In this exercise, you willieam how to:

• Download the pattern template
• Edit the sections in the template:
- Module name
- Pattern name
- Metadata section
- Overview section
- Constants
- Trigger
• Upload and activate the created module
• Run the pattern manually
• View results for the pattern run
Task 1: Download the Pattern Template

1. On the Discovery tab, click Knowledge Management.
2. Clickthe Create Pattern link.
3. From the Pattern Templates list, click Download for templatesimplest and save it on
your desktop.
Page 57
Pattern Templates
tldtll!!
----- ~i'IIaln It ,imlll, $Qtt.frtllftInS{iJnt.ba;9(I on lc'tnIq1ng iI prO«$$
M.Wo1.ln 81'1iGell1i6aobieScltt4!tfrl9'lalltt Ili9llereo 0.'1. pt(l~ss .. '" i~flllttin ~ ~cl'nm.!\d Ii~
~i!n \'I !l,ouped Scltwarel'l$l ance lItlo,red on a protes$., wA'llhe SOltNafell\$'IOlnceWlslon toun(Jln Ih~ oath.
1P2"np'gls " nr&ipR RaID lab!g fJ llhinSaln ;) grouped ScttwalDl~3nc.ln9l1C1fed on a prote:ls. vdhlhl Soft~ejr~.n'lI YClr~ionfound in the plllh lind klOklld Up" ;lIable
1*i~1911)Ii QrOU9tO ScllWtlf~$laMe ,",,0"'4 00 • (IfO(eS8, W#llhe S01tlo'atelMunee VErSiOn(ound bit rllnfflnO • tomfl'l&nd
It;a~ltln ;I grOUQ.6 SOltW'lIfekl51"nc"lI1Qg,te" on a PtO~$" WA'lIh' $qft,..",11'II$1ant, """Ion to\lno in Ih" Wln4OW$ ".11)'
lltairda!na "ouped SCM!eJr\SlalKe triglle,elSon II!)rocesl, Wfh IN: SO~'I~nce wrsion (00.1. 1)6In ttI)lM!. die
~l'Ililln • grouped 50ltwillelnSlance II1gllere4 on iI ptot'*$'" W#lltIe SO~'IIl-WlfI(:e ""'ion (oynd in j)i(k:8ge Iflform.'1on
libl'llaln a aoltw.I!IIrIIi!~lKtJ blladon IOentl)1ng Ill1fOC.". '<ttotIidl(oIItdstlltproc",',1Ii10fen into II slnvlll 81
!'aootlleln8 au-'SftIe$'MIlpliteIlO~ll1l\te.ba$edof'llde~~. SOlWtarelnmflee 8nd Se3J(fIIf'lO(Of some OIM.I eomponeill"
4. Rename the template_simple_si file as WinSCP.slmplesi.
Task 2: Edit the Sections in the Template

1. Open the file WinSCP~simple_si.tpl using a text editor.
2. Edit the Module Name.
Change the text from:
tpll.5 module $$module_name$$j
to
tpll.5 module Training.WinSCPj
3. Edit the Pattern Name.
pattern $$pattern_name$$ 1.0
to
pattern WinSCP_Simple 1.0
4. Edit the Metadata Section.
products := $$products$$j
publishers := $$publishers$$j
to
products := "WinSCP"j
publishers := "Open SRC"j
5. Edit the Overview Section.
tags $$tags$$j
to
tags Training, WinSCP, Demo:
Page 58
6. Edit the Constants.

type := "$$type$$"j
to
type := "Open Source WinSCP"j
7. Edit the Trigger.
on process := DiscoveredProcess where cmd matches unix_cmd "$$command$$"j
to
on process := DiscoveredProcess where cmd matches windows_cmd 'WinSCP"j
8. Save and close this file.
Task 3: Upload the Created Module
1. From the Discovery tab, navigate to Knowledge Management

2. In the Knowledge Management area, click the Upload link. This reveals the Upload
Knowledge section.
3. ClickBrowse, select the saved file,and click Upload.
1(01_ ...... 1 ~
t. Knowledge Management
Upload Knowledge
Page 59
The change progress is indicated on the screen. (The other options are disabled until the
upload is completed.)
~ Knowledge Management
Knowledge Upload - Progress ('
<:') L09d lempla~e_$l1ml)le_Si

(' Actwate Pa~em ,",ocMe'S
Londlno new I:ule.s
Note: If there is any error in the pattern file, it will fail to upload successfully. The error will need to
be diagnosed and corrected before uploading the file.
The successful upload (and activation) is indicated on the screen.
Knowledge Upload - Complete
c:'I toad lempl(lte_slmptc_S!

~ ActiVate Panern Modules
6 Pane(n Module fll1(!lino is active. Changes may nOl be shCYWnin the 11$1bI!Iow.
Knowledge Summary
Latest IKU: 11<'V-2014-01-1·AOOJll.10,O* - 7a, !niH11ri'i atlrr41f'3D
Custorn Modules: 32 - ~ ,'t'n?rt'W
CAMro11odulcs: 5 -~. 'in!! trIA
4. To locate the uploaded file, run a search query for the pattern module using the Filter. Type
WinSCP in the Filter field and click Apply.
[14 75lnocll.o Po" •• n Modules currenlly hidden
Display only active ..:.J J;' (TKU (3/3) .) J;' Custom J;' CAM Filter: JWinscp
5. You may also navigate by expanding the Unclassified Modules section until you see
WinSCP.
Select: @ (None II (Acllons:iJ DiSJI
er Unclassified Modules· 2 active

_r lralnlng. I aclille
Lr WinSCP (acliva) training,WinSCP
Page 60
Task 4: Run the Pattern Manually
1. Clickthe WinSCP link. This reveals the pattern module details.
f, Pattern Module: training.WinSCP

lAcfioM.' (Reports ...1 tRelaled ..)
Module 1)Ipe US'e(
ConAgiPedia Page A(lM} Ye$
Source M05 So'n $6d9.1.t4056f)6t{4J15e$5dJ80at3:506 S4il:)mlfl.n.g User $Y$Iem
SUbmission
~e 2IWfJl01410;37 AdNaCklnOate 26J06flOt4 to:37'29
KnOWledlJp.~ trlilning\'ilnSep .._ __ p_,"_._m Itroh'lII'lQ,WlI'IscP.WII'ISCP Simple

-
2. Clickthe link Training.WinSCP.WinSCP_Simple in the Pattern attribute value. The pattern
details display.
3. From the Actions menu, select Run Pattern.
\t. Pattern: training.WinSCP.WinSCP _Simple

IAtHon•• j IReeo~s .) (VisualiZations ... ) IRelated.)
ccmpare fc ...
KOI'I t-'aneln
m. ualnlng.WlnSCP.Winscp _Simple
ion 1.0
Manual Groups •
f9" Search for these Products on Google Ml Yes
00$ Demo, T(alnlng, WinSCP
ThiS I, 91.mplarl panal" tor a almplo Softv/lrorntlanct baled on

i(tentl~no \1 PIOCG.'.
This feQulred descllptlon btoc)< should be teplaC8d \\lith a

descrIPtion onne p3tlefn and lIle ",oduct iirs Idontif)ring. "J"ha
description appears as an attribute on tile Pattam node stored in
the data store.
Page 61
4. In the Run this Pattern dialog box, make the following selections:
• WinSCP
• Only show Working Set
• Expand
• Debug
• Do not get extra data
Run this Pattern iii'
Run against Group:
WlnSCP .:.I r-; Only showWorl<ing Sol

64 Discovered Process nodes 6nc:luding 64 via 1 Host node)
P Expand
Execution logging:
r.Oebug ("Info ,""alning ("ErrOl (Critical
Additional Discovery.
(;'00 not get extra dala rOe' data as needed ("Getatl newdisc:overydat8
( Run Panern) ( Can .. l)
5. Click Run Pattern.

The results for the successful pattern run are displayed.
~ Running Pattern training.WinSCP.WinSCP Simple
<:I Pattern run completed

&5 000.$ submr.:tIJ !'rom group Wln$¢P'
!node mel ee rigger woolllon5 \WIdi!node$ elid" not
Task 5: View Results for the Pattern Run

1. Clickthe link 1 (the node meeting the trigger condition).
2. Clickthe Created Software Instances link, Open Source WinSCP on test-win2k3vmwvc.
Diseov.ry Run> Diseov.ry Aeeus > Proe.ss List> tnscovereoProcess
ta Discovered Process: C:\Program Files\WinSCP\WinSCPexe

(Adions .) (Reports"') (Visuafi~aljons ...) (Related"')
Comrmnd C;\Pfoglam Files\WinSCP\WinSCP.exe
User Name test-vtin2k3mY\WGlAdministrator
Userid ·1
Processid 2032
Parent Process Id 411
Created Software Inst8ttCOS Open Source WjoSCP on jeS.wjn2k3yooltWc
Process list oBlpmtessUs! 001721 13146
Page 62
This screen is the result of a successful Simple WinSCP SI pattern run.
Softvvare Instance: Open Source WinSCP on test-win2k3vrnwvc

(Actions .) (Reports.) (VlStHIUUttlons.. ) (Re~Jed .)
Naime Open Sourte wmsep en t?S-}-wm2I<l'tmYM
Type open Source WinSep

Configlpedi~ Page
In$lance COunt t
HOSt tet1.....n2k2mlwtt
Mail1faini"lJ Patte,n !rAIDing WjoSCPWioS9P Sunglg
"'''"~Iypfoccnl''u. C)f,og'am f!IIM!QS¢MnBPPe-.:t
Lab 13.2: Edit an SI Version Package Template
In this exercise, you will learn how to:

Module name
Pattern name
Metadata section
Overview section
Constants
Trigger
• Run the package manually

2. Click the Create Pattern link.
3. From the Pattern Templates list, click Download for template.st.version.package and
save it on your desktop.
lQ1t:(M!a" 'i "'!MItt' (.J _inlain fin l~nli'6iblt SOIb<A!$lS!3nt@ lriQoere6 on • protess vrrlt'I itS; lefo:'llittlD its ((!mlf'lllnd iiI)&.
.caI
-..
~
&i'tmP'Me 1! ....."191'1 Pith fJ Miinl~lflll cro~ed" SCItWifEoWlSlanc:. lltiJoered on a proU$$, W4'111'le SOlt.. ,welro$l.ilnc.e '<'er&ion (QtJno 1ft me ~Ih. ~
"!r;m;t!jI:!S a nolSp paID tabl. to lbnIain it oroup'lJ SO~""'~blX,IngIlClnld on I Ilrot'SS •..wtI1bt Sott..'.1t.!r$ncCI ..-.[slon tound- in Ifl* plllllllnd toOk,d uP In I till... ~
~tain 11 cro..,ed" S~!8'lSlilnte lItOoeted (11'1 a profeSS, ""1I1he SGltllfatelMUAee WtSIOI'Itound-tJr fUMitlO 11 COMMand ~
It,aVII;lln J grOUP9~ $olttlti'''S!'''''''In9I1,t,1S on II P~(.f$&,. w.th Ih9 SoIM',v,Sn&anc, vtt$lOn round 11'1
ItI4 Vt'lnQolN$ ";i$1r¥- ~
Q:tJrQlllt 1i wrtign lin It 0 NWllaln • Oto~ell SClb¥aretnsl3nte tng~eted on • ptOt.S,- W#I!be SOltN¥elMUnce 'Wtrsion fCund In trI XNl.lIle. ~
IUlfllain 3 GrOuPed $(Ilb¥aret'lslilnte O'O!l"ed 0t'I IIIp~(es$,. W4'1ltIe SO~e!I\$'liln(:e 't'1!tSIOI'lfOUndIItPil(~e irofommoo. I~ I
Q1Rmp!al' 1jI wPRd 'bfdr,n ~ ItlIl'llaln a 8cllYnfltn!illlnc. bllslKl en jC~lnp 11P~("'.which (oaK~ !lIe PIOCHS' (1I.lIlrcminto " SIng!' 81 G:IDtIQ.lA
MaWIl&in
a a~s.""'l)Iicatio,*"lill\ee hsed OAidemfJfl'lOa SO~'eln.$WIee and ~e3rttliAO (Ot some other (:omoOtlellts ~
4. Rename the template.sl.verston.package file to WinSCP _si_version_package.
Page 63

1. Open the file WinSCP_si_version_package.tpl using a text editor.
2. Edit the Module Name.
Edit text from:
tpll.5 module $$module_name$$j
to
tpll.5 module Training_ WinSCP_Verstoned:
Edit text from:
to
pattern WinSCP_Versioned 1.0
4. Edit the Metadata Section.
Edit text from:
products := $$products$$j
publishers := $$publishers$$j$$ 1.0
to
products := "WinSCP"j
publishers := "Open SRC"j
Edit text from:
tags $$tags$$j
to
tags Training, WinSCP, Verstoned,
6. Edit the Constants.
Edit text from:
type := "$$type$$"j
to
type := "Open Source WinSCP"j
7. Edit the Constants (cont.)
Edit text from:
package_regexes := [regex "$$regexl$$",
regex "$$regex2$$" ];
to
package_regexes:= [regex "WinSCP\s+(\d+\.\d+\.\d+)"]j
Edit text from:
on process := DiscoveredProcess where cmd matches unix.cmd "$$command$$"j
to
on process := DiscoveredProcess where cmd matches windows_cmd 'WinSCP"j
9. Save and close this pattern file.
Task3: Upload the Created Module

Knowledge section.
Page 64
3. In the Upload New Package area, click Browse, select the saved file and click Upload.
4. To locate the uploaded file, run a search query for the pattern module using the Filter. Type
WinSCP in the Filter field and click Apply.
5. Expand the Unclassified Modules section until you see Training_ WinSCP _Versioned.
Pattern Modules (2 active)

Select @ (None IIIP£lions .)
e· r Uncla$silied Modulu· 23C:rre
t
r lralning·. attlve
Lr ~(ac ... ) Ira!nlng.lNtnSCP
r TfajDl® WlnSCP ""[Jfgngd (SCM) Tralning_WlnSCP _v.cs'oned
Task 4: Run the Package Manually
1. Click the link Training_ WinSCP _Versioned. This reveals the pattern module details.
2. Click the link Training. WinSCP. WinSCP _Versioned in the Pattern attribute value.
f, Pattern Module: Training_WinSCP _Versloned

(~ljOM .) IRllpOltI •) IRt'a1(1tJ .. )
MOdUli! Tr.IAlIIO_WlnBCP _YtctIOMd Moclule lYIMt User
C.ltlfllJ1lltldi"P."" A~M! Yet
SOUIO.,MOrtSum 13'38".",.0.51 k :'C·O.Sf&,MSt' Of S~,.. 'lit1i"O UIICtf $)'$1_"'"

S4ll1tnilisionO~e 2110&12(1'4,03& Adfv\ltkmO ... 2110&120\41038,21

• WinSCP
• Expand
• Debug
5. Click Run Pattern
1. Click the link 1 (the node meeting the trigger condition) to view the result screen.
~ Running Pattern: Training WinSCP Versioned.WinSCP Versioned
<::I Pattern run completed

6$ node, svbmllled!rOm tlfOUPWJn$CP'
1 node met the tngger condlUons and i.! nodes did not
Page 65
2. Click the Created Software Instance (the link Open Source WinSCP <version> on test-
win2k3vmwvc).
Discovery Run> Discovery Access> Process list> Discovered Proce$$
~ Discovered Process: C:\Program Files\WinSCP\WinSCP.exe

IActions ... ) (Reports .. I IVisualizatroos '" I (Related ...)
Command C:\Pf~am FilestWinSCPWfInSCP.exe
U!Ief Hame test·win2k3wnwtttAdmlnislr.ltol
UserId ·1
Process id 2032
ParentProcessld "12
Created SottwlIre jnstences op'D S1)urtAWjQSCP yf!fljion 4 Q 8 on tAS'.wipZk1yllWtyt
Process list qAlpIOCiI$,iJsj 00 ' 72 ! 1 31,,8
The WinSCP version is displayed in the result This is the result of the SIversion package
pattern run.
Software Instance: Open Source WinSCP version 4.0.6 on test-win2k3vmwvc

(Actions ~) IRepot1s .) (Vlsuallzabons .. ) IRelated .. I
Name Open SourceW!:nSCP version 4.0.6 on test·vAn2k3vmwvc
Type! open SourceWinSCP
(onOgrpedla Page
Instance Coune 1
FUll~ndol1 4.0.8
Product \A}r$IOil 4.0.6
UOSI tesl.w!o2kbmw)'(,:
Mal,-."io.", Pat(UfO I,.IOIGb WlnSCP Wwloo!ul Wit)SCP YelplQOed
PfilllatY processes C'\proO!§!m Flle!!\VlJlnSCMnSCPem
0 ... ., Com,,6eteness Issues
Page 66
Lab 13.3: Edit a Business Application Instance Search Template
In this exercise, you wilileam how to:

Module name
Pattern name
Metadata section
Overview section
Constants
Trigger
SI Containment
• Run the package manually

2. Click the Create Pattern link.
3. From the Pattern Templates list, click Download for templatebaisearch and save it on
your desktop.
Pattern Templates
.:Q.mp1alt tim," t! f'

Ott.Cll ....,""
N'WlI)ln , tI!'I'Ipl' SOItII\I'IWI.IJI'IC' o.oed 01\111,/111'1'1\0

• prot...
•.
~
oaGrW1
Q"Q)!Iljt, " 10,'.,1., !CI Mml.ln '" '.""""111, Softolo"..... I."'.lnQD".Q on • o~c.'t ¥Mh Ib h""'''' InItf commlMlII,... ~
9ltmplQIt • urllAn paV' ~ Irblflll.n • OtOWI'O ,Of!W.~.lill'C.Ir'gIl'''O 01'1 • IlI'OC•••• '\fIoWI t'It IOlt....attlntt.nt. _.,.101'1r~,IAO In lilt ,.,n ~
~Ir!DQ!!'!' H .. "Ion R"!b 'Ab!' P N.MIIlln I II'OIl(l.1t 8.".."..",.0't01I'''0 01'1 • 111'0(•••• ~ '" 1O~.!IK1.n(. ",,.101) tooJnlJ In ,,,. ».~
,1)(110010:.0IMIII • 10111, ~
ntffl<,QIJili,I vtK!An ("MMd Q MJ,.."ain a QrOI$'OSOllWSltMtI3Mf'IIig!)ertO 01'1 a crottS!, Wlf'l1I'If S6~'!MUnt ..... UIOn IOuI'lObIt'IlMin!) • (OMManG. ~
£htmoljl!' ,I "KlAn l!?fM tQ 1rAfl)nlalna gfOl,SI'o Soltwif81$li\I'I(' Dtg!l,red Of! it llI'OC"" WO'I tit 50~.w.lfIo$;in(.. "",Ion to4.IndIn ,"- WlndoWt AQi$1t't ~
:f)>>mpIM, at urtlpn J!!'I liS " ""lnliln 0 9'OUOlOSoltwi~Slancl! ~lIafllt 0tI a Ilrorest_ lWtI ~ S!lItNlf,'''''''nte ¥tn!o,", oond 11'1
an)(Nt.. 61.. ~
...... ,all'l \'I Oto~fd 601!Warm$lal'lCelltgOited 0t'I a prote .... WIJ'I1J'If SO!tH3relMtanee 'f.rtIOI'l to.Jnd 11'1
~(kaQf 1tII'0~on. ~
QaOlQ"" N [9111" 'htm•n o ~1'I!;lIn. $(lItvn,tIrI,111K,bls,(I~n iO,ntl\'l'IQI oro','1. 'WIfIkl'l(QlltclsII" pnxH"tllildftn inloa tII\IIl' 81 ~
91tm$!il "'i $iijrcb Q .alrilaln • OU:tlrlts'SAllPicalionfnslaneli blte-d On illilrM)lng -a SOftlririlln.Wtlrf and ,eattninlt rot some oeM, tOmpOflfnn:. II~ I
4. Rename the template.bal.search file to WinSCP _bai_search.
1. Open the file WinSCP .baisearch.tpl using a suitable text editor. Edit text from:
tpll.5 module $$module_name$$;
to
tpll.5 module Training.CustomBAI;
Page 67

Edit text from:
to
pattern WinSCP_BAl1.0
Edit text from:
tags $$tags$$j
to
tags Training, WinSCP, Businessapp:
4. Edit the Constants Section.
Edit text from:
type := "$$type$$"
to
type:= "Custom WinSCP BAI"j
Edit text from:
on si:= Softwarelnstance created, confirmed where type = "$$si_type$$"j
to
on si:= Softwarelnstance created, confirmed where type = "Open Source WinSCP"j
6. Edit the SI Containment
Edit text from:
contents := search (Softwarelnstance where $$condition$$)j
to
contents := search (Softwarelnstance where instance = "Open Source WinSCP" and
type= "Open Source WinSCP")j
7. Save and close this file.
Task 3: Upload the Created Module

Knowledge section.
3. Under the Upload Knowledge section, click Browse, select the saved file and click Upload.
4. To locate the uploaded file, run a search query for the pattern module using the Filter. In
the Filter field, type Custom and clickApply.
Page 68
5. Expand the Unclassified Modules section until you see CustomBAI.

Pattern Modules (1 active)
Select: @ I None 111_ns ·1
ilr r Unel....... d ""0010$· I actlvft
9- r Training' 1 adve
Lr CySiPmllA! <_> Training.Cus1omSAI
6. Click the link CustomBAI. This reveals the pattern module details.
~ Pattern Module: Training CustomBAI

(A41Ionl .) (R.oOtll ...) (RliMIG ...1
c_.....
Source
....
IiI)5
s.amSQ'lDae
Sum
Tr"'CurotomBAS
tl8f124ao4Sa3831$b534104!df8b2dl
11J0612014 10 $&
ModuleType UUI
Wlmilt~
A(.'(ive
lNef
AdNation Date
Yes
syslem
2710&1201410;~6;4~
PauCfn Tr'llll'lil'lfl CW31!ltnfW Wt!t§CP RA!
Task 4: Run the Package Manually
1. Click the link Training. CustomBAI. WinSCP _BAI in the Pattern attribute val ue.
• WinSCP
• Expand
• Debug
4. Click Run Pattern.
1. After the results for the successful pattern run are displayed, click the link 1 (the node that
meets the trigger condition).
~ Running Pattern: Training.CustomSAI.WinSCP SAl
~ Pattern run completed

15 nodes sul)mit!e(i from oroop WinSCP'
1 nod. trltllhtlliggtr (:onditiOI'l$$ncSII nOd... dia noc
Page 69
2. The node details display. Click the Custom_ WinSCP _BAllink.
Softvvare Instance Open Source WinSCP version 4.0 6 on test-win2k3vmwvc

[ActJons.1 fRe®lts .. 1 (VlfiUaiIUOOftS .. )IRelate:d .. )
Name Open Source ~"linSCPvetslon~ 0 6 on te$ .. wln~
1yPe Open Source Win$CP
lnscance CounI 1
FUllversiOn ".0.&
Part Of AppIicetlOn CUsJomWltr§¢P IW
The application instance screen is displayed as the result of the BAIpattern template run.
'r;::; Application Instance: Custom WinSCP SAl
1-- I Ail)1l~ .) I R~p~; .) 1'VIW.\I!1.;,*",·1 t R~~ • I
HlIIlMI C:"$I(ltnWnS(PtIAI
1'1110 CI,I$1(lf'n !MtI$C' fW
0'15"2"911". Ijtm! 0'''''0,1)1> .. , §mr' " l? Pi!!""""'!! '! nefmwt so"0 «."p'
.~~.GI'~ij,~.i~:-"I~::~"""""""""""""""""'~'.~'~."~1;'.~""~!1J~
,,0 Q!.IUtfl' ~ M M1ClOto"'rM ti:et
... -
liW
This screen confirms the successful creation of a busness application instance for WinSCP.
Page 70
Module 14: Application Mapping Using

Templates
In the Application Mapping labs, you will learn how to do simple application mapping using
templates.
The labs relate to an example application (QuickExpense), which provides a web-based expense
tracking system to the Wibble Software Company.
The Business Application

You need to model a simple business application called QuickExpense that provides web-based
expenses tracking system for the customer. The application needs to be modeled using The Pattern
Language (TPL).
The application components include:
• Application Server
• Database Server
• Web Server
• Exporter Server
• Watchdog Service
The HAl should be created when a matching Application Server and a matching Web Server are
detected.
Additional information about the various components is provided.
Application Server
The Application Server is proprietary software produced by the Wibble Software Company and is
considered "prime" (the primary SI) to recognize the HAl. It can be identified from the process
name "wibbleAppServ."
You need the full version of the server for modeling.
Tips:
• The command jusr jtideway jtrainingjwibblejwibbleAppServ -v provides the full version of

the Application Server.
• For a displayed version number in the format "x.y.z", store "x.y" as the version number and "z"
as the build number.
• Note any information available for applied patches in a separate attribute.
Page 71
Marketing Names
The Wibble Software Company's Marketing department prefers a different product naming scheme
than the version numbers preferred by the Engineering department.
Engineering Name Marketing Name

vO.S Alpha
v2.6 NG
v2.7 NGi
v3.0 Ultima
Tip: Use the marketing version to populate the "productversion" attribute. Use a product version
"Unknown" for any engineering version other than those listed.
Typically, there is more than one application server instance running in the systems (one for load
sharing and another for failover).
Database Server
This is a proprietary database back-end server. One instance runs to support each of the main
application server instances. You can determine the mapping of these instances by the suffix after
the underscore in the process name. The database server process can be identified by the form
"wibbleDBxy," where "xy" is a two-digit version representing the x.y database version number.
Web Server
It is assumed that an instance of Apache Web Server (v2.1 or later) running on the same host as the
application server is also a part of the QuickExpense application. You need not model Apache
yourself; use the matcher provided in the latest TKU.
Exporter Server
There are one or more copies of an exporter process running to feed data to external systems. No
information is available to distinguish these processes.
Watchdog Service
This process handles failover and error notification in the application server; it is not a major
system component The Watchdog Service does not require any versioning capabilities.
Page 72
Visualization of the Application Model
QuickExpense Web
Application 5.7 on
J''-''W'' -.
IMbble Application W,bble Application
Apache Webserver IMbble Exporter
Server 2.7 instance Server 2.7 instance
version 2.2.3 on Server 1.5.5 on
"MASTER" on ''SLAVE'' on
npgs-saturn npgs-saturn
np9s-satu\ i9s-saturn
Wibble Dat ab as e IMbble Det ebase

Server 3.5 instance Server 3.5 instance
"MASTER" on "SLAVE"on
np9s-satur\ -saturn
npgs-saturn
swrt ch=f I
Page 73
Tips for the Labs:
• Search for these application processes on your appliance, either manually (using SSH) or look at
the process list in the datastore after a scan.
• Examine the configuration and log files.
• Check if the process is running, using the command ps -ef I grep wibble.
• If the process is not running, start wibble using the command

/usr /tideway /training/wibble/run.sh.
• The "update-execute-debug" cycle is time consuming; before you upload/activate the pattern,
ensure that the pattern has minimal errors.
• Before using regular expressions in TPL, test them with "Regex Coach."
• Ifyou activate a pattern, all modules will recompile, so develop using only those patterns
required for your project.
• All inferences are repeated every time a pattern is run.
Page 74
Lab 14.1: Create a Simple Softwarelnstance of the Wibble

Database
In this exercise, you will learn how a simple SoftwareInstance pattern for the Wibble database
works.
Note that the pattern file is provided in the Lab Files folder on your desktop. Youneed to upload it
and study the sections in the file to understand how it works.
Task 1: Create a credential for the Appliance, start Wibble services, Locate and Upload the Pattern File
1. Create a credential for the Appliance: User name _ tideway, Password _ tidewayuser
Use it for the IP address 192.168.0.10 and only select ssb.
Using PuTTY,log in to 192.168.0.10 and type: /usr /tideway /training/wibble/run.sb
(The message you receive about it already being installed is expected.)
2. Navigate to Discovery> Knowledge Management.
3. On the Knowledge Management page, click Upload.
4. Under the Upload Knowledge section, click Browse.
5. Onyour desktop, navigate to Creating Patterns Lab Files> ADDMLab Files>
Application Mapping Lab Files> 01_DBSimple > BAM.tpl ClickOpen to open the file.
6. Clickthe Upload button.
Task 2: View the Activated Pattern

1. In the Filter field of the Pattern Modules section, type wibble and clickApply.
2. ClickWibble.
3. On lines 1, 4, and 7, note the module and pattern names in the uploaded module. On lines
20-22, note the overview section, the constants section (on lines 24-26) and the triggers
section (on lines 28-30}.\d+ searches for a number with at least one digit. On lines 32-40,
note the body section. The model.Softwarelnstance section creates or updates the
datastore. The key section includes the instance, so this package generates two unique SIs.
4. At the top of the page, in the Pattern Module: Wibble section, clickthe pattern
Wibble.WibbleDatabase.
5. Note the information on the uploaded package and how the sections in the uploaded
package affect the displayed information.
• Name
• Pattern Version
• Tags
• Description
• Pattern Module
Page 75
Task 3: Scan the Appliance
1. Navigate to Discovery> Discovery Status.

2. Click Add New Run.
3. Enter Range as 192.168.0.10.
4. Enter Label as Application Mapping Lab.
5. Click OK
6. Click Start All Scans.
7. After the scan is complete, select the Recent Runs tab.
a. In the table, click the first result.
b. Under the Summary section, click Hosts.
c. Under the General Details section, click Software Instances. Note the wibble SI
that you created.
Note:
• To find the Softwarelnstances, click through the results for Lab 14.1. Click the link for the
attribute value of the host nodes, which has a link for the Software Instances.
• To find the provenance information, on the page displaying SI information, click the Show
Provenance button.
• The expected result for the scan is shown. The result may vary if the scan is in the record mode.
Important: Before proceeding to the next lab, delete the previous version of the BAM.tpl file from
Discovery> Knowledge Management
Page 76
Lab 14.2: Generate a Versioned Softwarelnstance Pattern for

the Wibble Database
In this exercise,you willlearn how aversioned SoftwareInstancepattern for the Wibble database works.
Note that the pattern file is provided in the Lab Files folder on your desktop. Youneed to upload it,
study the sections in it to understand how it works, and run the pattern file.
Task 1: Locate and Upload the Pattern File

1. In the Knowledge Management page, click Upload.
Application Mapping Lab Files> 02_DBVersioned > BAM.tpl. ClickOpen to open the file.
Note: The appliance will display a warning, if you do not delete the previous BAM.tpl file from the
uploaded packages.

2. ClickWibble.
3. In the uploaded module, note the constants section (on lines 24-26), the triggers section (on
lines 28-30), and the body section (on lines 32-47).
• "cmd" is the attribute of the discovered process node, which contains the process
command line. (".cmd"is also used to extract version information in this pattern.)
• The regex.extract sections extract the software instance and software version.
• The model.Softwarelnstance section creates/updates the datastore. The key section
includes the instance, so this pattern generates two unique SIs.
Task 3: Scanthe Appliance

2. Clickthe Recent Runs tab.
3. ClickRescan Now for the Application Mapping Lab.
4. After the scan is complete, click the Recent Runs tab.
a. In the table, clickthe first result.
c. Under the General Details section, click Software Instances. Note the wibble SI
that you created. Clickthe Show Provenance button for the created SIs.
Notes:
• Navigate to the results using directions provided in the previous lab.

• Use the Regex Coach (provided on your desktop) to practice regular expression strings.
Page 77
Lab 14.3: Generate the Softwarelnstance for the Wibble

Application Server (Version, Build, Patch)
In this exercise, you willieam how the versioned Softwarelnstance pattern for the Wibble
Application Server works. Note that the created pattern file is provided in the Lab Files folder on
your desktop.
1. On the Knowledge Management page, click Upload.

Application Mapping Lab Files> 03_AppservSimple > BAM.tpl. ClickOpen to open the
file.
1. In Filter field of the Pattern Modules section, type wibble and clickApply.
2. ClickWibble.
3. In the uploaded module, note the metadata section (on lines 67-72), constants section (on
lines 78-80), the triggers section, and the body section (on lines 86-100).
• On running the binary with the -v flag, the cmdResult declaration section locates the
full version of the application server
• "discovery.runCommand" is run for each host node (specified in the parenthesis) to
obtain version information of the WibbleAppserver SI by running "-v".The
"run Command" function returns nodes of type "DiscoveredCommandResult."
• If the command result does not return valid information, a warning message is
displayed.
• If the command executes successfully, it extracts version, build, and patch information
using the declarations-under the else section.
• In "cmdResult.result", the "result" attribute contains the result of the command.
• In "process.args", "args" is the attribute of the discovered process node that contains
command line arguments.
• To determine the instance names and operational mode of the application server, the
configuration file must be examined.
• This command extracts the configuration file path from the discovered process
command path using the -c option. This information is added to the node.

Page 78
3. Click Rescan Now for the Application Mapping Lab.

c. Under the General section, click Software Instances. Note the wibble SI that you
created.
Lab 14.4: Update the Softwarelnstance for the Wibble

Application Server - Ports
In this exercise, you will look at how the update of the Softwarelnstance works for the Wibble
Application Server. Note that the created pattern file is provided in the Lab Files folder on your
desktop.
1. On your desktop, navigate to Creating Patterns Lab Files> ADDM Lab Files>
Application Mapping Lab Files> 04_AppServEditionPorts > BAM.tpl. Upload the
BAM.tpJ pattern file.

1. In the Filter field of the Pattern Modules section, type wibbJe and click Apply.
2. Click Wibble.
3. In the uploaded module, note the section to get the configuration file (lines 109-122).
Page 79
1~3 II Get con~ig =ile

lld c:Q=ile : = dd sccve ry . fileGe-c (hC31:, cfg:ilePCi~h>;
111 po=,cstr :. 1 I ;
11'< e-cii1:icn : = 'I;

113 i: not cfq:ile ~hen
11'; log,warn('Con=iq =ile tcfg=ilePath\ not found');
115 el.3E
lle II Extract edition
11- edition := h~th,evaluate(cfgfile,content, raw'/con;ig/engine/@edition');
11~ i: net edition then
119 etii'Cion : = ";
120 else
121 edition := ~ext,lower(edition[Ol);
1,2 end i:;
123
124 II Extract pO~t information and generate a space-string
125 1/ This eXCo'Upleis ccnccrved, as y-ou could (end probably should) just: ac'tacn a 1i'31: cc
126 II the host node, but it shows what can be done with e for loop,
12- porta : = xpe cn. evedue ce (cigfile, concent , raw '/con=ig/li:steners/li3tenerl I@port' ) ;
12: =cr por-t in pores de
129 i: por rsr.r = " then
130 port31;r := pore;
131 else
132 porcst r ,_ '%pOrt3tr% \pon\';
133 end i:;
13~ end !cr;
13<i end it;
• The cfgfile declaration uses the command discovery.fileGet on the host and
configuration file path,
• discovery.fileGet retrieves the specified file,This command identifies "host" as the
discovery target, either a directly discovered data node or a Host node, The" fileGet"
function returns nodes of type "DiscoveredFile,"
• In "cfgfile.content",the content attribute contains the contents of "cfgfile."
• The ports declaration extracts the ports information and populates the attribute "ports"
with a space-separated list
4, The Create or update datastore section (on lines 137-147) updates the datastore,
• The declaration _tw_meta_data_attrs := ['ports'] creates port metadata attributes
during the scan,
1, Navigate to Discovery> Discovery Status,

2, Clickthe Recent Runs tab,
3, ClickRescan Now for the Application Mapping Lab,
4, After the scan is complete, click the Recent Runs tab,
a, In the table, click the first result.
b. Under the Summary section, click Hosts,
c. Under the General section, clickSoftware Instances, Note the wibble SIthat you
created,
Page 80
Lab 14.5: Update the Softwarelnstance for the Wibble

Application Server - Product Version
In this exercise, you will look at how the SoftwareInstance for the Wibble Application Server is
updated. This update relates to the Product Version. Note that the created pattern file is provided in
the Lab Files folder on your desktop.
Application Mapping Lab Files> 05_AppServVerRel > BAM.tpl. Upload the BAM.tpl
pattern file.

1. In Filter field of the Pattern Modules section, type wibble and click Apply.
2. Click Wibble.
3. In the uploaded module, note the table declaration section (on lines 1-10).
a. This section defines the table with the Engineering and Marketing names.
b. The "Unknown" version has also been declared for any other versions detected.
4. Note the constants section (on lines 93-94)' Also, note the Application Server product
version section (on lines 151-171).
a. The declaration product_version:= AppserverProductVersions [version] is a
key-value lookup in the table declarations section.
Notes on Constants:
• Referencing constants between patterns is a feature ofTPL.
• In this module (.tpl file), the constant "dbtype" is defined in the previous pattern
WibbleDatabase 1.0. It is referenced later in the pattern WibbleAppserver 1.0 with
WibbleDatabase.db_type.

2. Click the Recent Runs tab.
c. Under the General section, click Software Instances. Note the wibble SI that you
created.
Page 81
Lab 14.6: Generate a Softwarelnstance for the Wibble Exporter

Server
In this exercise, you willieam how the SoftwareInstance for the Wibble Exporter Server is created.
The created pattern file is provided in the Lab Files folder on your desktop.

Application Mapping Lab Files> 06_Exporter > BAM.tpl. Upload the BAM.tpl pattern
file.

1. In Filter field of the Pattern Modules section, type wibble and clickApply.
2. ClickWibble.
3. In the uploaded module, note the body section (on lines 211-220).
4. The pattern uses model.findPackages to search for packages, version, and revision
declaration in the installed package named "wibble." When the package detects the installed
packages, it stores the version and revision information. The pattern updates the datastore
with package version and product version information. The key is not explicitly set.

a. In the table, clickthe first result.
c. Under the General section, clickSoftware Instances. Note the wibble exporter
server that you created.
Page 82
Lab 14.7: Generate a BusinessApplicationlnstance for the

QuickExpense Business Application
In this exercise, you will learn how the QuickExpense BusinessApplicationlnstance is created. The
created pattern file is provided in the Lab Files folder on your desktop.
Application Mapping Lab Files> 07 _BAlSimple. Upload the BAM.tpl pattern file.
1. In Filter field of the Pattern Modules section, type wibble and click Apply.
2. Click Wibble.
3. Note the section to create an SI for the Wibble Database Server (on lines 13-48), Wibble
Application Server (on lines 66-110), and Wibble Exporter (on lines 175-209). Also, note
the section to create a BAI for QuickExpense (on lines 231-259). In addition, note the
triggers section (on lines 254-256).

4. After the scan is complete, click the Applications tab.
5. In the Application Summary section, click Application Instances.
The result should indicate a successful BusinessApplicationlnstance creation for the
QuickExpense Business Application.
Lab 14.8: Update BusinessApplicationlnstance for QuickExpense

Business Application - Apache Web Server
In this exercise, you will learn how the QuickExpense BusinessApplicationlnstance is updated. We
need the Apache Web server (ApacheBasedWebserver 2.17) from the Technology Knowledge
Update (TKU) to update the BAI.The web server and the app server will be added to the
application.

1. On your desktop, navigate to Creating Patterns Lab Files> ADDM Lab Files> Application
Mapping Lab Files> 08_BAlWithExpWebLinks. Upload the BAM.tpl pattern file.
Page 83
1. In the Filter field of the Pattern Modules section, type wibble and click Apply.
2. Click Wibble.
3. Note the section to create a BAI for QuickExpense (on lines 235-265). Also, note the
overview section (on lines 248-251). This section requires the ApacheBasedWebserver
from the installed TKU. In addition, note the constants (on lines 253-258), the body (on
lines 264-274), and the software containment relationship section (on lines 282-284).

5. In the Application Summary section, click Application Instances.
The result should indicate a successful BusinessApplicationlnstance creation for the
QuickExpense Business Application.
Page 84
Lab 14.9: Update BusinessApplicationlnstance for QuickExpense

Business Application - Containment Relationships
In this exercise, you will learn to update the QuickExpense BusinessApplicationInstance. Youwill
add the Exporter server and the Database server to the application. The pattern file is provided in
the Lab Files folder on your desktop.

Application Mapping Lab Files> 09_DBWithAlILinks. Upload the BAM.tpl pattern file.

2. ClickWibble.
3. Note the section to create a BAIfor QuickExpense. Also,note the overview section. This
section requires the ApacheBasedWebserver from the installed TKU.In addition, note the
constants, the body, and the software containment relationship section.
4. Note the section to update the BAlfor QuickExpense (on lines 283-290).
a. Note the reference to the constant exp_type from the pattern WibbleExporter 1.0.
292 /1 Crea~e ~ele~ion3hip3 &0 eXpcr&er 513
293 exp_3i3 := sea.:ch{in host. t rsvez-se HC3&:~o3tedScft.ware: RunningSoft~a=-e :So-:twarelnst.ance \.;here
29-4 type = %WlbbleExport.er .eA"p_type%);
295 if not eX9_sis then
296 lo~.we=n{'NcexporterSIs :ound~o li~ BAI to');
297 else
298 II i\e =.ay :ind more than one expor-cez
299 mcdel.add:ontei~~ent(bai, exp_sis);
300 end i!;
01
30, end body;
303 end ~atter~;

5. Under the Application Summary section, clickApplication Instances.
6. The result should indicate the successful addition of the Exporter server and the Database
server for the QuickExpense Business Application.
Page 85
Lab 14.10: Add Simple Identities for All Processes
In this exercise, you wilileam how to add simple identities for all processes.

Application Mapping Lab Files> lO_WithSimpleldent. Upload the BAM.tpl pattern file.
2. ClickWibble.
3. In the uploaded module, note the Simple Identifier Matchers section (on lines 308-
319).The simple identities are added for all processes. Also, note the simple identity
matching commands and arguments.
oZ. II Senple ideneicies maeching ~~ and args (wdog is teo generic a name en it3 own)
32;;' idem:i:y Servers_IHbble_i,atchdog 1.0
32: !;ags Training, lVibble;
J~. Di!cov!!'edPrcc!!! Old, arg! -> !imple_id!neiey;
.25
3d; unix_Old 'wdoq', !'egex 'w1.bbleAppServ' -> 'Wibble Applicaeion Server I,aechdoq Service';
32- end identity:
• The cmd and args are declared because simple identity matching using just "wdog" is
not specific. Simple identify contains both the command and the argument
Task 3: Verifying the Result
1. In the Quick Search box, type ssh.

2. In the Multi Kind Results list, click Discovered Process.
3. In the Discovered Process list, note the Simple Identity column that you created.
Page86
Lab 14.11: Update the BusinessApplicationlnstance Versioning

for QuickExpense
In this exercise, you willieam how to update the QuickExpense BusinessApplicationlnstance for
versioning. The pattern file is provided in the Lab Files folder on your desktop.

Application Mapping Lab Files> 11_AppVersioned. Upload the BAM.tpl pattern file.
2. ClickWibble.
3. Note the section to update the BAIfor QuickExpense (on lines 249-280).
4. Note the body section (on lines 278-296) to update the BAIfor QuickExpense.
The %si.qe_version% updates the BAIwith the server version. "qeverslon" is the
QuickExpense application version extracted from startup file - qexpense.log. This extracted
version is put in a custom attribute "qe,version" for use by the BAIpattern.

5. In the Application Summary section, clickApplication Instances.
The result should indicate a successful update of the BusinessApplicationlnstance
versioning for QuickExpense.
END OF LAB EXERCISES
Page 87
AUTO-ADBC-0100 / BMC Atrium Discovery and Dependency PREP Boot Camp
- END OF COURSE -
About BMC Software
BMC Software, Inc. is a leading global provider of enterprise management solutions that
empower companies to automate their IT and align it to the needs of the business. Delivering
Business Service Management, BMC solutions span enterprise systems, applications, databases
and service management.
About BMC Education Services
At BMC Software, we are dedicated to developing and delivering best-in-class education. We

focus on evolving quality "solution-based" classes around Business Service Management (BSM)
processes and technologies that help to enable our customers to optimize their IT infrastructure
and at the same time discover how BMC solutions can solve contemporary business challenges.
To learn more about BMC Education Services, visit www.bmc.com/education.
~bmc

BMC Atrium Discovery and Dependency Mapping

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BMC Atrium Discovery and Dependency Mapping

Caricato da

Copyright:

Formati disponibili

LAB GUIDE

Module 10: Using BMCAtrium Discovery CLI 54

IDs and Passwords for Use in the Lab Exercises

Credentials to log in to the environment:

BMCAtrium Discovery Login Password Notes

http://192.168.0.9/ui system System1234$ The Secondary "ADDM10.1 Clean" virtual machine

8- Souion 80de QIlbo(Io. IOf,YOIJI PU 1lY ~~

Module 2: Dashboards Overview

Lab 2.1: Creating Custom Dashboards

Task 1: Copy the Default Dashboard

Task 2: Rename the Dashboard

Note: The next task is a continuation of this step.

Task 3: Include Channels in the Dashboard

2. Click the Commit change button.

Lab 2.2: Working with Dashboard Administrator Utility

Task 1: list and View the Currently Available Dashboards

Host name 192.168.0.10

Note: In the command, ensure that there is a space after dashboards:

Lab 2.3: Resetting the [locked] Flag

Task 1: Unlock the Default dashboard from the CLI

Note: In the command, ensure that there is a space after dashboards:

2. Type the password as System1234$.

Task 2: lock the Default dashboard from the CLI

Note: In the command, ensure that there is a space after dashboards:

2. Type the password as System1234$.

Module 3: User Administration and System

Lab 3.1: Providing Security Management Access

Task 1: Create a New User's Account

Task 2: Check the Access Levels of the New User

Question for Discussion: What result do you see?

Task 1: Change the Appearance of the Login Page

You have suc~essfuiV logged out.

9. Log in again using the credentials of system and System1234$.

Task 3: Check the Audit Logs for a User

1. Search the audit logs for the system user's activities.

From 12 .:J Marcil .:J 12()15 at iOO {17

lab 3.3: Creating a New User from the Cli

tw _adduser<space>-f<space>- 'StudentO l' <space>student

[t lr::ieTT=c.:IJ lDI_':t_llll::,.=t ] ~ t-T,T :tll,ill'::'::":t: ~tllle!lt -f I ~tl1Iiell+- 1]1'

[t ldeTT:cl':.' j Loc-e Lhce- J ~ t IT_=tI!,-i1t2er a t.ucie n t -:t I .::_r'11-~ell1 01'

Lab 3.4: Listing the New User's Details

Task 1: View the Details of a Newly Created User

• The twJistusers utility displays all users' details.

Lab 3.5: Changing a User's Password

Task 1: Change the User's Password Using the tw_passwd Utility

[r~iIJeq,::t?I:jlc,c;~lYlcl~;t '-J $ t.r.r p.;:tS.3T,r.:i 8tl.t(~e!lt

Lab 3.6: Locking and Unlocking an Account

Task 1: Lock an Account

?er U3er 3~~te U3EF ~TATE LI="=~EII

Task 2: Unlock an Account

Additional Information on tw _upduser:

Module 4: Scanning Basics

Lab 4.1: Perform a Sweep Scan

Task 1: Add a New Run

Task 2: View the Results of the Discovery Run

Shovling 3 completed Discovery Runs

First Sweep 192.16&.0.1·25 25 201s..03·1306:53~16·

Numb .. of IPs Scanned 25

Numb .. of IPs Dropped ~

SNfl1P Managed oevic:es 0

Droppec Endpoints: 2015-03-16 05:00:21.00

Start Time 1610312O'1S(6:OO:21

E,nd Time 1610312015 05:00:2S

Reason IPs cfroppad No I'es.p()r')s.fi"orn~ IP$