Skip navigation
Share:|

BMC TrueSight Capacity Optimization 10.3 is now released and many customers are planning or already in process to upgrade their environment from BCO 9.5.X or BMC TrueSight CO 10.0.X to 10.3. Due to environmental constraints it is not always possible to perform the installation with a user interface and hence as an alternative you can use silent installation option. The silent installer is useful if you want to add the installation of product to your own install script or push out the installation on multiple machines. The silent install feature allows you to enter installation parameters into a file that is read in by the installation program instead of typing them in response to each installation prompt.

 

In this blog, I will share sample silent installer configuration file for Typical install on the First Server: Install the Application Server + ETL Engine – All component for Postgres database. Before you begin with upgrade please go through our documentation page, Preparing to upgrade the Application server and Upgrading Application server and components

 

  1. Login to your Application Server with already existing BMC TrueSight Capacity Optimization user (for example, cpit)
  2. Create a temporary folder to store TrueSight CO 10.3 installation files (for example, /opt/cpitinstall)
  3. Download package TSCO_AppServer_ver10.3.00_[OSversion]_[arch].tar.gz from EPD site into this temporary folder -  /opt/cpitinstall
  4. Use tar –xvf to extract .gz file.

                tar -xvf TSCO_AppServer_ver10.3.00_[OSversion]_[arch].tar.gz

After extracting installation files change working directory as [Installation_file_path]/BCO/Disk1/silentInstallTemplates

cd /opt/cpitinstall /BCO/Disk1/silentInstallTemplates

    6.     Take backup of BCO_FIRST_SERVER_TYPICAL.txt

                cp BCO_FIRST_SERVER_TYPICAL.txt BCO_FIRST_SERVER_TYPICAL_backup.txt

    7.     Open BCO_FIRST_SERVER_TYPICAL_backup.txt in a text editor, enter your environment specific values against default installation parameters and options that you would like to customize, and save the file.

    8.     In case of product upgrade -J BCO_DB_CREATE_SCHEMA option is ‘false’ by default but if there are any database changes then you need to specify encrypted password in BCO_DB_PASSWORD and must uncomment and update the following parameters as per your current BMC TrueSight Capacity Optimization installation: #Tablespaces, #Console Schema, #Views Schema, and #Reporting User.

1.png

2.png

 

3.png

 

9.     To generate encrypted database password execute [Installation_file_path]/BCO/Disk1/BCOEncoder.sh which is shipped with Installer

4.png

 

10.   Sample BCO_FIRST_SERVER_TYPICAL_backup.txt is attached with this article. Parameters of all configuration files are explained on our documentation page.

11.   Change the working directory back to [Installation_file_path]/BCO/Disk1 and type the following command to launch the silent upgrade using a config file and upgrade the product on your machine:

./setup.sh -i silent -DOPTIONS_FILE=<file path>/<config file name>.txt

./setup.sh -i silent -DOPTIONS_FILE=/opt/cpitinstall/BCO/Disk1/silentInstallTemplates/BCO_FIRST_SERVER_TYPICAL_backup.txt

12.   If the silent upgrade completes successfully, the upgrade will exit with no notifications, and the shell prompt will display the blinking cursor.

13.   Check /tmp/bco_install_log.txt to verify if upgrade is successful. For successful installation you will see this message,

 

(Aug 26 2015 05:24:03.297 AM -0500),INFO,com.bmc.install.utility.logging.Log,

--------------------------------------------------------

  BMC TrueSight Capacity Optimization 10.3.00 install succeeded.

--------------------------------------------------------

 

Missed previous blog posting? Find them here: BMC TrueSight Support Blogs

The blogs share the experience of BMC Customer Support on how to understand and best use particular product features. You can read more about the goals of Pulse Blogs in About the Customer Support Community. These blogs are posted in the individual product community, but as many community members have multiple BMC ProactiveNet products, this document provides a summary and links to these posts to make them easier to find.

I hope this blog was helpful. Share your experiences by rating this post or adding a comment, you can also suggest topics which you like us to cover in future.

Share:|

With the release of TrueSight Capacity Optimization 10.0 we have simplified Lookup Table management for OOTB ETLs with 'Entity Catalog'. In this article, I will explain some concepts of Entity Catalog which was known as shared Lookup table in previous BCO versions.

 

Earlier BCO versions used a "master" ETL or fake ETL to import the systems in the workspace and it was in charge to create the Master lookup that could be shared among the others ETL so that we can avoid the creation of duplicate systems. In TrueSight CO 10.X, with entity catalog, we provide a clearer user interface to use the Master lookup feature. Now we have entity catalog, which are "group" of lookup tables so there is no more reason to speak about multiple lookups. So now when an ETL import systems, the list of imported items is stored in an object called entity catalog.  It is a list of imported systems by an ETL and all those ETLs that use the same systems can share the same entity catalog. In this way, Entity Catalogs provide an easier way of sharing entities imported by multiple connectors with respect to Lookup Tables.

 

Share Entity Catalog with other ETLs collecting performance/capacity data

1.png

2.jpg

 

If you already had Master Lookup in place in BCO 9.X then in TrueSight CO 10.X you need not make any changes in Entity Catalog (unless there are specific problems in your environment), everything will be taken care by TrueSight CO when you upgraded. There is an out of the box entity catalog called "default entity catalog" where all systems are imported unless a user decides differently.

 

Entity Catalog allows the user to distinguish between which ETL created an entity and which ETL added additional metrics to it afterward.

 

In the screenshot below you can see a snapshot of the functionalities of the entity catalog:

 

  • Reconcile Entities: when you have imported the systems twice without sharing entity catalog, the systems will be duplicated. With this functionality, you can remove duplicated entities specifying the criteria of the reconciliation
  • Merge Entity Catalog: it’s used when you decide to merge two different entity catalog in one
  • Filter “Show only entities used by:” this picker contains all ETLs sharing the same entity catalog and only systems used by the selected ETL will be showed in the table

 

3.jpg

For more detailed information, you can also refer to our documentation.

 

Missed previous blog posting? Find them here: BMC TrueSight Support Blogs

These blogs share the experience of BMC Customer Support on how to understand and best use particular product features.  You can read more about the goals of Pulse Blogs in About the Customer Support Community. These blogs are posted in the individual product community, but as many community members have multiple BMC ProactiveNet products, this document provides a summary and links to these posts to make them easier to find.

I hope this blog was helpful. Share your experiences by rating this post or adding a comment, you can also suggest topics which you like us to cover in future.

Share:|

In this blog I will explain some concepts of vis file parser connector in BCO 9.X Vs TrueSight CO 10.0, what is new in TrueSight CO 10.0 in terms of Visualizer file processing.

 

Vis parser connector in BCO 9.X

 

In 9.X there are two different BPA vis parser ETLs:

  • BMC - BPA 7.5.x/9.x vis files parser
  • BMC - BPA 7.5.x/9.x Virtual Nodes vis files parser

 

The "BMC - BPA 7.5.x/9.x vis files parser" imports data for the following system types from the BPA vis file:

 

  • Standalone (any OS)
  • VMware (data collected via BPA vCenter proxy collection)
  • AIX Power VM/WPAR
  • Solaris LDOM/Zone/DSD
  • HP IVM/nPar/vPar
  • Xen
  • MS HyperV
  • KVM


The 'BMC - BPA 7.5.x/9.x Virtual Nodes vis files parser' ETL imports data for computers in the Visualizer file whose type is VIRTUAL (i.e. nodetype = VIRTUAL and associated SYSTEMD/CAXNODED tables).  This is generally data collected within a VMware guest OS instance by a locally installed collector (or for Windows via proxy collection as well).  The key point is that if the NODE_MODE of the machine is VIRTUAL in CAXNODE table then it will only be imported into BCO via the 'BMC - BPA 7.5.x/9.x Virtual Nodes vis files parser' ETL. Usually if you check the vis file in the T;SYSTEMS section you will see that these systems are the "VIRTUAL" kind. So, you should use BPA VIRTUAL Nodes vis file parser ETL to load systems data from VMWare guests that was collected by a collector running within VMWare guest machine, which only reports virtual resource consumption.

Use the BPA vis file parser to load data that are not of "VIRTUAL" kind. For that, choose the appropriated options (run configuration tab), which could be Standalone, AIX Power VM/WPAR, VMWare, Solaris LDOM/Zone/DSD, XEN, HP IVM/nPar vPar, MS HyperV, KVM. See the online documentation to learn more about Virtual Node vis file parser and vis file parser.

Note that when you import those new computers into BCO they will create new entities in BCO separate from the existing vCenter collected entities.  The Entity Type for the VIRTUAL in-guest collected data will be "VMware - Virtual Node' as opposed to 'VMware - Virtual Machine' which is the entity type for vCenter collected data about the guest.

 

Vis parser connector in TrueSight CO 10


TrueSight Capacity Optimization 10.0 now has the ability to process Virtual nodes along with other platform types in a single connector instance so you only need to parse the Visualizer files through one ETL called BMC - TrueSight Capacity Optimization Gateway VIS files parser even if it contains both VIRTUAL nodes and the other system types. It supports TrueSight Capacity Optimization VIS files versions greater or equal to 7.5.00. Files can be retrieved using the Gateway Manager Web Service or can be read locally to TSCO Application Server (after file transfer from Gateway Server to TSCO AS). This feature is now available for both VIS connector and CDB connector types. There is a built-in task called
Virtual Node Linker in the hierarchy rule to create relationships among systems and virtual nodes. The Virtual Node Linker task connects a VM (an entity that is collected from the Hypervisor) to the corresponding virtual node (an entity that is collected from inside the VM) in Capacity Optimization. Data for these entities is imported from different ETLs, however, the execution sequence of these ETLs does not matter. The name of this relationship between the VM and virtual node entities is identified as GM_ASSOCIATED_TO_VN.

The "BMC - TrueSight Capacity Optimization Gateway VIS files parser" imports data for the following system types:

  • Standalone (any OS)
  • VMware (data collected via BPA vCenter proxy collection)
  • AIX Power VM/WPAR
  • Solaris LDOM/Zone/DSD
  • HP IVM/nPar/vPar
  • Xen
  • MS HyperV
  • KVM
  • Virtual

For additional information, please refer to online documentation.

 

Missed previous blog posting? Find them here: BMC TrueSight Support Blogs

These blogs share the experience of BMC Customer Support on how to understand and best use particular product features.  You can read more about the goals of Pulse Blogs in About the Customer Support Community. These blogs are posted in the individual product community, but as many community members have multiple BMC ProactiveNet products, this document provides a summary and links to these posts to make them easier to find.

I hope this blog was helpful. Share your experiences by rating this post or adding a comment, you can also suggest topics which you like us to cover in future.

Filter Blog

By date:
By tag: