Setting up and configuring BCO EE (BPA) Linux Console How I Learned to Stop Worrying and Love BCO EE Dima Seliverstov 3/3/2014

Setting up and configuring BCO EE (BPA) Linux Console

How I Learned to Stop Worrying and Love BCO EE

Dima Seliverstov3/3/2014

Steps

• Installing and configuring the database• Installing the console• Configuring the console• Using the console• Monitoring the console

Installing and configuring the database

• Pick the latest database you can use – https://docs.bmc.com/docs/display/public/bcmco95/Oracle+Populate+support

• Install the database– Same machine as console or another machine

• Configure tablespaces– Command

• sqlplus / as sysdba• CREATE TABLESPACE visdb DATAFILE '/<location>/<instance>/visdb01.dbf' SIZE 8G;

• (ALTER TABLESPACE visdb ADD DATAFILE /<location>/<instance>/visdb01.dbf’ SIZE 8G;) to increase

• Configure the users to use tablespace– Command

• sqlplus / as sysdba• CREATE USER<user> IDENTIFIED BY <password> DEFAULT TABLESPACE visdb;• GRANT CONNECT <user>; GRANT RESOURCE <user>;

• Check to see if your database is up and running via Oracle Developer– http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html

https://docs.bmc.com/docs/display/public/bcmco95/Oracle+Populate+support

Installing the console

• Pick the latest hardware and software NOT the minimum versions– https://docs.bmc.com/docs/display/public/bcmco95/Minimum+system+requirements+by+component

• Use Silent Install* (Use Silent Install because X Windows GUI is slow and error messages are few)

– See silent directory for file contents and instructions• Run as root, but configure the product user to be someone other then root• Double check everything you enter, the script or the GUI have limited error

messages

• Make sure best1_9.5.00 or 9.0.00 links are created in /usr/adm• Make sure you have cron configured and running

– Run $BEST1_HOME/bgs/scripts/checkCron.pl• If cron is not running start cron on Linux via “/etc/init.d/crond start” as root

https://docs.bmc.com/docs/display/public/bcmco95/Minimum+system+requirements+by+component

Configuring the console

• Use AutoNodeDiscovery for agents and proxy (Windows, Vmware)

• Use Web Based console General Manager

Configuring the console: Why use AutoNodeDiscovery?

• AutoNodeDiscovery– Automatic manager run creation• Scalability based on BMC best practices• Nightly update and discovery• Reasonable defaults provided• Separation by functionality or platform

Configuring the console: What is AutoNodeDiscovery?

– Command line only tool– Proxy Configuration• Supports

– VMware,– Windows

• User Specifies– Proxy Host– Domain

– Agent Configuration• Control node lists using a simple csv file

Configuring the console: How to use Proxy AutoNodeDiscovery?

• Command – AutoNodeDiscovery –C –v <ProxyHostName> -d <Domain Name> -u <UDR Data Repository> -

s <Manager Script Name> • Accepting all other defaults not specified on the command line is an excellent

starting point• Manager Script Name

– Should contain the platform and domain description and function– Should not contain any spaces– Should not be very (long 20 characters max)– Example:

• VCenterBCMDev

• UDR Data Repository should contain the name of the manager run– Easy to identify nodes in a run– Easy to transfer nodes in a run to another console for workload or modeling– Increased performance

• each run is not looking at nodes from another run

– Example: $BEST1_HOME/local/collect/<manager Script Name>

Configuring the console: How to use Agent AutoNodeDiscovery?

• Command – AutoNodeDiscovery –C –a <Agent List Location> -u <UDR Data Repository> -s <Manager Script Name>

• Accepting all other defaults not specified on the command line is an excellent starting point• Manager Script Name

– Should contain the platform and domain description and function– Should not contain any spaces– Should not be very (long 20 characters max)– Example:

• AIX_Dev,Windows_Dev,Solaris_LDOM_Dev

• Agent List Location– Should correspond to the manager script name– Should be placed outside of the BEST1_HOME, so we can migrate the runs to another release

• Example :/data1/AIX_Dev.csv

– Information can be easily imported and updated as needed into the Agent List Location• UDR Data Repository should contain the name of the manager run

– Easy to identify nodes in a run– Easy to transfer nodes in a run to another console for workload or modeling– Increased performance

• each run is not looking at nodes from another run

– Example: $BEST1_HOME/local/collect/<manager Script Name>

Configuring the console: Why use Web Based General Manager?

• Native X Window console lacks functionality of the web console– No recovery– No health dashboard– No ability to start or stop multiple runs

• Native X Window console is slow over the network

Configuring the console: What is Web Based General Manager ?

• General Manager is part of BCO Console or BCO EE Perceiver

• Web Based tool to manage multiple BPA consoles from a single web page

• Health Dashboard• Recovery• Log Viewer

Configuring the console: How to use Web Based General Manager?

1. Run AutoNodeDiscovery for a single run.– This will create a manager run– *An alternative is to create a new run and change the parameters to

make them default.

2. Modify the parameters of the manager run to be the future default of all your runs– All the future created scripts will have the desired default parameters.– Use the best practices specified in

– https://docs.bmc.com/docs/display/public/bcmco90/Best%20practices%20when%20using%20Manager

– https://kb.bmc.com/render/KCSRenderController?type=cssolutionint&id=SLN000000214439&searchid=1393861895031

3. Run AutoNodeDiscoveryfor all the other runs4. Schedule the runs

https://docs.bmc.com/docs/display/public/bcmco90/Best%20practices%20when%20using%20Manager



https://kb.bmc.com/render/KCSRenderController?type=cssolutionint&id=SLN000000214439&searchid=1393861895031




• Add Console

Configuring the console: How to use Web Based General Manager? Configuring

Default Values

DoubleClick


Default Values


Default Values

Set desired Begin Time


Default Values

Enable Cut Disk Options


Default Values

Enable Oracle Population


Default Values

Visualizer Interval and Analyze Reports


Default Values

Enable Scheduling

Options


Default Values

Disable OSR


Default Values

Save the Manager Run


Default Values

Save Desired Setting as Default


Scheduling the runs

Multiple Runs can be

Selected and Scheduled

Using the console

• General Manager Recovery• Perceiver• Building Workloads using the Windows

Console using Analyze

Using the console: General Manager Recovery

• For additional details see KA329791 https://kb.bmc.com/infocenter/index?page=content&id=KA329791&actp=search&viewlocale=en_US&searchid=1393887760642

Using the console: Perceiver

• You can view the data populated to the database using Perceiver– Configure a Data Source– Configure a Group– View the data

Using the console : Perceiver Configure a Data Source

Using the console : Perceiver Configure a Group

Using the console : Perceiver View the data

Using the console: Building Workloads using the Windows Console using Analyze

• UNIX Console can be used for building workloads.• Windows Console is a newer and more user

friendly– UDR data should be transferred from UNIX to

Windows– Workloads can be generated and downloaded from

UNIX to Windows console– Workloads are platform independent

• It does not matter which console (UNIX or Windows) builds them


– UDR data transfer from UNIX to Windows


– Workloads can be generated and downloaded from UNIX to Windows console.

– Workloads are platform independent• A free graphical tool WinScp(winscp.net) is very useful

for data transfer

Monitoring the console

• Use GeneralManagerLite scripts• Create an e-mail action script (outside the

product) to monitor daily console operation and differences

Monitoring the console: GeneralManagerLite scripts

• Command: – $BEST1_HOME/bgs/scripts/BCO_BPAStatusAndRecoveryManager.pl

• For the pure BCO EE use case the only input required is the console name

• For a BCO EE /BCO integration the database information is required

• Both text and plots are generated

Monitoring the console: GeneralManagerLite Output

Monitoring the console: e-mail action script

• Quick daily assessment tool (10 second)• E-mail client based (mutt)• Daily e-mail message – differences between today and yesterday– File system utilization

• When problems occur root cause can be obtained via e-mail contents

• Script attached to the notes• If a script is found to be useful, a better integration

with BCO EE will be provided

Monitoring the console: e-mail action script output

Configuration and change since yesterday Date = 2014/03/03 : 2014/03/02 Number of Configured BPA Nodes = 74 : 74 : change 0 Number of Collected BPA Nodes = 65 : 57 : change 8 Number of Transfered BPA Nodes = 62 : 55 : change 7 Number of Processed BPA Nodes = 58 : 52 : change 6 Number of BCO ETLid BPA Nodes = 0 : 0 : change 0 ----------------------Details-------------------------------------- File system disk space usage for location of status file = /usr/adm/best1_9.5.00/local/manager/status/GeneralManagerLite/BCO_BPAWebReport/BCO_BPAStatusCount.csv Filesystem 1K-blocks Used Available Use% Mounted on/dev/mapper/vg00-datalv 82569904 29847852 48527748 39% /data1

Questions?

Documents

Setting up and configuring BCO EE (BPA) Linux Console How I Learned to Stop Worrying and Love BCO EE Dima Seliverstov 3/3/2014