Skip navigation
1 2 3 Previous Next

TrueSight Orchestration

75 posts
Share This:

The Script is designed to Monitor RSSO, Repository, Grid Manager and Peers for critical attributes likes Available Memory, Used Memory, Total Heap Memory, JVM Uptime, Active Threads, Management Grid Status, Main Grid Status, CDP Grid Components Status (Health, Library Manager, Configuration, Context, Scheduler, Metrics, Job Manager, Adapter Manager, Activity Processor) and all active adapter status active on all peers in the Grid. It also tracks Running, Compensated and Completed Jobs Status of all peers, In case of script find any issue in the grid it will trigger a notification based on the notification method enabled in the Config.xml

 

Enhancements in v3.0

  • Create an Incident ticket in the ITSM tool (Remedy or ServiceNow) to report the issue.
  • Create Event in True Sight Operations Management (TSOM) to report the issue.
  • Monitor Running, Compensated and Completed Job Count in Grid and all peers and notifications will be a trigger for the threshold limit of running jobs.
  • Monitor Embedded and External RSSO Status.

Fix

  • Deprecated library message comes while reading values from Config.xml has been fixed.
  • The use of python minidom library to read XML has been removed as its support in a future version of Python is coming to end.
  • InsecureRequestWarning message issue has been fixed.
  • Logging improved in the console and in logs.

 

Note: Script leverages BAO/TSO REST API and Python web scraping techniques to collect data from RSSO, REPO, Grid Manager and Peers.

 

Which version of BAO/TSO does the script support?

The new version of Script is designed to support TSO 8.x and above including recently release TSO 20.02.00.

 

Which Notification methods does the script support?

The new version of Script is designed to support the below methods to report issues.

  • Email Notifications
  • Remedy Incident Creation
  • SNOW Incident Creation
  • Event Creation in TSOM

 

System Requirements

  • Python 3.6.6 or above.
  • Python Requests Module (Command to install: - pip install requests)
  • For Windows executable file is also available which doesn’t require installation of Python
  • For Linux installation of Python 3.6.6 or above is mandatory along with the installation of request modules.
  • All configurable parameters of the script/tool is controlled by "Config.xml" which should be kept in the same folder as the script.
  • For Remedy Incident creation, script use REST API which needs to be enabled in ARS.
  • For TSOM Event creation and Service Now Incident creation script use REST API.

 

 

Steps to Configure the Script

Getting the Grid ID from your Grid Manager, log in to the Grid Manager and go to Manage>Grids>Select your Grid Name and click on pencil sign for edit. copy the ID and Grid Name as shown below and past it in "Config.xml"

Provide your CDP server IP/FQDN and port details along with BAO/TSO admin account in the "Config.xml", also in "schedule-interval" provide the time interval in secs for the script to check Grid Status, default is set to 270 sec i.e. 4 mins 30 sec if you are using “report Compensated Job” please keep the "schedule-interval" to 4 mins 30 sec only as the Jobs concluded status in kept in the grid only for 5 mins.

 

 

XML TagDescription and excepted value
server
CDP Server Name or FQDN
portCDP Port
schedule-intervalThe interval at which script run (Suggested value is 270 sec i.e. 4 mins 30 sec)
enable-encryptionIf you want to use password encryption set the value as "True" otherwise default value needs to be set as "False"
userAO Admin Username
passwordAO admin password in plain text.
encrypted-passwordEncrypted password string from the encryption tool
GridIDGrid ID which can be collected from Grid Manager console as shown in the above screenshot
GridNameGrid Name of your BAO Environment
AllowInsecureRequestIf you are using self-signed or insecure certificate set this as "True" otherwise set it as "False"
print-onscreenIf you want the script out to be printed on the command prompt or console set this as "True" however if you are running the script in background set it as "False". although in both, the case output will be collected available in logs for reference.
console-loggingIf it is set as "True", INFO, DEBUG or ERROR logging will be also displayed on the console.
monitor-peers

If you want to monitor other peers in the Grid like HACDP, AP's and LAP set this to "True" otherwise set it as "False"

Also if monitor-peer is True you will have to provide peer information as shown below make sure to include protocol like HTTP or HTTPS in value along with the port which peer is utilizing.

 

<peers peerType="HACDP">

        <peer>https://baohacdp.bmc.com:38080</peer>

    </peers>

<peers peerType="AP">

        <peer>https://baoap1.bmc.com:48080</peer>

        <peer>https://baoap2.bmc.com:48080</peer>

</peers>

<peers peerType="LAP">

        <peer>https://baolap1.bmc.com:48080</peer>

</peers>

Threshold-limit

If the threshold limit is hit the script will sending a notification to inform about the same using the notification method enabled.

example:

 

<Threshold-limit>
   <memory>
200</memory>
   <threads>500</threads>
   <runningJob>256</runningJob>
</Threshold-limit>

 

In the above example

if free memory drops below 200 MB a notification will be triggered.

if threads in the BAO cross 500 threads limit a notification will be triggered.

if runningJob are above 256 job limit a notification will be triggered.

repoUrl

URL of the repository

example

<repoUrl>https://baorepo.bmc.com:28080/baorepo</repoUrl>

rsso

URL of RSSO, depending upon whether it was embedded RSSO or External.

example:

<rsso type="embedded">
   <url>https://baorepo.bmc.com:28080/rsso</url>
   <url>https://baocdp.bmc.com:38080/rsso</url>
</rsso>

Or

<rsso type="external">
   <url>https://rsso1.bmc.com:28080/rsso</url>
   <url>https://rsso2.bmc.com:38080/rsso
</url>
</rsso>

report-compensatedJobTo report compensated Job set it as "True"
logging-levelTo Set the Logging level for script default is INFO and other excepted value is DEBUG
Notification

Under the notification tag, different methods of notification are available as

  • Email Notifications
  • Remedy Incident Creation
  • SNOW Incident Creation
  • Event Creation in TSOM

 

Print on Screen and Loggings.

If Print on screens is enabled in Config.xml the script will print status as shown below for all TSO/BAO components. An authentication token will be acquired only once till the time it expires.

The below screenshot shows the status of the RSSO, REPO, GRID along Jobs status in the Grid.

Below screenshot shows the Activity Peer Status along with its respective components and adapters status

Below screenshot show status of CDP components and adapter along with Incident Number which was created to notify one adapter which is in fault state.

If print on screen is turned off, then the details logging are collected in the TSOMonitoring.log depending upon logging level set on Config.xml. In this case, the script can be run in the background.

 

·        Notification Method – Email Setting

 

To turn on email notification set the Tag “enable-email-notification” to “True” and configure the parameter of the EmailSetting as below.

 

Note: For encrypting password uses the encryption tool.

 

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

<EmailSetting>
    <SMTPServer>
{SMTP Server Name or FQDN}</SMTPServer>
    <SMTPPort>
{Port- default is 587} </SMTPPort>
    <secure>
{True or False}</secure>

    <starttls>{True or False}</starttls>  

    <EmailUsername>{ Sender Email like - sender@test.local }</EmailUsername>
    <encrypted-password>
{Encrypted Password - V1ZkU2RHRlhOSGhOYWswOQ== }</encrypted-password>
    <NotificationEmailAddress>
receiver@test.local</NotificationEmailAddress>
    <Subject>
BAO/TSO Monitoring tool reported error for monitored Grid</Subject>
    <Message>
Error details are mentioned below</Message>
    <enable-email-notification>
{True or False}</enable-email-notification>
</EmailSetting>

 

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

Screenshot on left show notification of Adapter in fault state whereas screenshot on the right show notification compensated job.

 

Notification Method – Remedy Incident Creation

 

To enable remedy incident creation set “enable-remedy-incident-creation” to “True” and configure the parameter of the ARS-Config as below.

 

Note:

For encrypting password uses the encryption tool.

Since the script utilizes Remedy REST API it is compatible with ARS 9.1 and above which has Rest API enabled.

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

<ARS-Config>
           <ARServer>
{AR Server FQDN or HOSTNAME}</ARServer>
           <ARSAPIPort>
{Port- 8008}</ARSAPIPort>
           <ARUsername>
{ AR Username }</ARUsername>
           <password>
{ Password in Plain Text }</password>
           <encrypted-password>
{ Encrypted Password using encryption tool} </encrypted-password>
           <secure>
{True or False}</secure>
           <first-name>
{First Name of the user from which Incident will be created}</first-name>
           <last-name>
(Last Name of the user from which Incident will be created} </last-name>
           <impact>
1-Extensive/Widespread</impact>
           <urgency>
1-Critical</urgency>
           <default-incident-status>
New</default-incident-status>
           <short-description>
BAO/TSO Monitoring tool reported error for monitored Grid</short-description>
           <description>
Error details are mentioned below</description>
           <enable-remedy-incident-creation>
{True or False}</enable-remedy-incident-creation>
</ARS-Config>

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

Below screenshot show notification of Adapter in a fault state and a screen of incident created for compensated job

 

·        Notification Method – SNOW Incident Creation

 

To enable SNOW Incident creation set the “enable-snow-incident-creation” to “True”  and configure the parameter of the SNOW-Config as below.

 

Note: For encrypting password uses the encryption tool.

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

<SNOW-Config>
     <snow-host>
{Service Now FQDN like test.service-now.com}</snow-host>
     <snow-port>
{Port -443}</snow-port>
     <snow-username>
{Username of SNOW a/c}</snow-username>
     <password>
{plain text password}</password>
     <encrypted-password>
{Encrypted password}</encrypted-password>
     <secure>
{True or False}</secure>
     <impact>
1</impact>
     <urgency>
1</urgency>
     <category>
Software</category>
     <subcategory></subcategory>
     <caller-id>
486e3a122fd74010d72657ab2799b635</caller-id>
     <default-incident-status>
1</default-incident-status>
     <snow-short-description>
BAO/TSO Monitoring script reported error for monitored Grid</snow-short-description>
     <snow-description>
Error details are mentioned below</snow-description>
     <enable-snow-incident-creation>
{True or False}</enable-snow-incident-creation>
</SNOW-Config>

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

To get the caller-id of the user, open user profile in SNOW portal, under additional actions, click copy sys_id, and past in Config.xml as value for <called_id> tag.

The below screenshot shows a sample incident created to report the Adapter in Fault state.

 

Notification Method – TSOM Event Creation

 

To enable TSOM Event creation set the “enable-event-creation” to “True” and configure the parameter of the TSOM-Config as below.

 

Note:

For encrypting password uses the encryption tool.

If Routing is required you can set the CELLNAME else leave it blank and Event will be routed to default Cell.

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

<TSOM-Config>
     <tsps-host>
{TrueSight Presentation Server Hostname}</tsps-host>
     <tsim-host>
{TrueSight Infrastructure Manager hostname}</tsim-host>
     <cell-name>
{CELLNAME}</cell-name>
     <userid>
{username}</userid>
     <password>
{password}</password>
     <encrypted-password>
{ Encrypted Password using encryption tool}</encrypted-password>
     <secure>
{True or False}</secure>
     <event-title>
BAO/TSO Monitoring tool reported error for monitored Grid</event-title>
     <message>
Error details are mentioned below</message>
     <enable-event-creation>
{True or False}</enable-event-creation>
</TSOM-Config>

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

Below the screenshot shows a sample event for adapter in a fault state.

 

The below screenshot shows a sample event for compensated Job

 

 

Steps to Encrypt or Decrypt passwords

 

To encrypt the password in Windows run the “passwordtool.exe” and For Linux use “passwordtool.py” provide the password string as shown below along with operation as "encrypt" and copy the encrypted output to the Config.xml file for respective encrypted password tag.

Example for Windows: passwordtool.exe -p P@ssw0rd -o encrypt

Example for Linux: passwordtool.py -p P@ssw0rd -o encrypt

 

 

·         Sample Config.xml

 

<ConnectionDetail>
   <server>baocdp.bmc.com</server>
   <port>38080</port>
   <schedule-interval>270</schedule-interval>
   <enable-encryption>True</enable-encryption>
   <user>aoadmin</user>
   <encrypted-password>V1ZkU2RHRlhOSGhOYWswOQ==</encrypted-password>
   <GridID>urn:jxta:uuid-E5D1AB3B3CB94AA48A93A7E2BE2814A702</GridID>
   <GridName>MyGrid</GridName>
   <AllowInsecureRequest>True</AllowInsecureRequest>
   <print-onscreen>True</print-onscreen>
   <monitor-peers>True</monitor-peers>
<!--    <peers peerType="HACDP">
        <peer></peer>
    </peers>-->
   <peers peerType="AP">
        <peer>https://baoap1.bmc.com:48080</peer>
   </peers>
<!--    <peers peerType="LAP">
        <peer></peer>
    </peers> -->
   <Threshold-limit>
     <memory>200</memory>
     <threads>500</threads>
     <runningJob>256</runningJob>
   </Threshold-limit>
   <repoUrl>https://baorepo.bmc.com:28080/baorepo</repoUrl>
   <rsso type="embedded">
     <url>https://baorepo.bmc.com:28080/rsso</url>
     <url>https://baocdp.bmc.com:38080/rsso</url>
   </rsso>
   <report-compensatedJob>True</report-compensatedJob>
   <logging-level>DEBUG</logging-level>
   <console-logging>False</console-logging>
   <Notification>
        <EmailSetting>
           <SMTPServer>localhost</SMTPServer>
           <SMTPPort>587</SMTPPort>
           <secure>False</secure>
           <starttls>False</starttls>
           <EmailUsername>noreply@test.local</EmailUsername>
           <password>admin123</password>
           <encrypted-password>V1ZkU2RHRlhOSGhOYWswOQ==</encrypted-password>
           <NotificationEmailAddress>support@test.local</NotificationEmailAddress>
           <Subject>BAO/TSO Monitoring tool reported error for monitored Grid</Subject>
           <Message>Error details are mentioned below</Message>
           <enable-email-notification>False</enable-email-notification>
        </EmailSetting>
          <ARS-Config>
            <ARServer>arserver.bmc.com</ARServer>
            <ARSAPIPort>8008</ARSAPIPort>
            <ARUsername>appadmin</ARUsername>
            <password>appadmin</password>
            <encrypted-password>V1ZoQ2QxbFhVblJoVnpROQ==</encrypted-password>
            <secure>False</secure>
            <first-name>Allen</first-name>
            <last-name>Allbrook</last-name>
            <impact>1-Extensive/Widespread</impact>
            <urgency>1-Critical</urgency>
            <default-incident-status>New</default-incident-status>
            <short-description>BAO/TSO Monitoring tool reported error for monitored Grid</short-description>
            <description>Error details are mentioned below</description>
            <enable-remedy-incident-creation>True</enable-remedy-incident-creation>
          </ARS-Config>
        <TSOM-Config>
            <tsps-host>tsps.bmc.com</tsps-host>
            <tsim-host>tsim.bmc.com</tsim-host>
            <cell-name></cell-name>
            <userid>aoadmin</userid>
            <password>P@ssw0rd</password>
            <encrypted-password>VlVWQ2VtTXpZM2RqYlZFOQ==</encrypted-password>
            <secure>True</secure>
            <event-title>BAO/TSO Monitoring tool reported error for monitored Grid</event-title>
            <message>Error details are mentioned below</message>
            <enable-event-creation>False</enable-event-creation>
        </TSOM-Config>
        <SNOW-Config>
            <snow-host>testinstance.service-now.com</snow-host>
            <snow-port>443</snow-port>
            <snow-username>aoadmin</snow-username>
            <password>admin123</password>
            <encrypted-password>V1ZkU2RHRlhOSGhOYWswOQ==</encrypted-password>
            <secure>True</secure>
            <impact>1</impact>
            <urgency>1</urgency>
            <category>Software</category>
            <subcategory></subcategory>
            <caller-id>486e3a122fd74010d72657ab2799b635</caller-id>
            <default-incident-status>1</default-incident-status>
            <snow-short-description>BAO/TSO Monitoring script reported error for monitored Grid</snow-short-description>
            <snow-description>Error details are mentioned below</snow-description>
            <enable-snow-incident-creation>False</enable-snow-incident-creation>
        </SNOW-Config>
    </Notification>
</ConnectionDetail>

 

Steps to Run or Deploy the script or executable.

 

In Windows with .exe: After Configuring the "Config.xml" file double click on executable to run directly or run it from the command prompt.

Example: Open Cmd> BAOMonitoring_v3.0.exe

 

In Windows from .py: After Configuring the "Config.xml" file, Open command prompt and Type "python" then space followed by the script file name.

Example: Open CMD>python BAOMonitoring_v3.0.py

 

To Stop the script press CTRL+C

 

To run in background type pythonw then space followed by the script file name.

Example: Open CMD>python BAOMonitoring_v3.0.py

 

To stop the script which is running in the background you have to find task-id of pythonw and kill it using taskkill command.

 

In Linux from .py: After Configuring the "Config.xml" file, from terminal type python3 then space followed by the script file name.

Example: Terminal>python3 BAOMonitoring_v3.0.py

To Stop the script press CTRL+C

 

To run in background type python3 then space followed by script file name, space followed by "&"

example of running in the background

Example: Terminal>python3 BAOMonitoring_v3.0.py &

To stop the script which is running in the background you must find the process id of python and kill it using kill -9 command.

 

PLEASE NOTE: THIS IS NOT AN BMC OFFICIAL SCRIPT OR TOOL FOR MONITORING BAO/TSO, BMC SUPPORT WILL NOT BE ABLE TO PROVIDE YOU ANY ASSISTANCE FOR THE SAME.

Share This:

Key Features

 

  • New user interface for Operator Control Panel (OCP), which is now independent of Flash
  • Support for Remedy Single Sign-On (RSSO) version 20.02
  • Security Enhancements
    • Encrypted passwords for silent installation
    • No hard coded passwords in installers or configuration files

 

 

For more details please take a look at the documentation here:

20.02 - https://docs.bmc.com/docs/TrueSightOrchestrationPlatform/2002/20-02-enhancements-911446424.html

Share This:

Key Features

 

New Jira Adapter

New application adapter for Jira that integrates with Jira REST APIs to perform operations for managing Issues. With this adapter, you can create new issues, update issues, add comments, and notify users for changes made to any issue in Jira. 

 

New CyberArk Adapter

New application adapter for integrating with CyberArk is introduced in this release. This adapter consists of an actor adapter and provides operations for session management, to retrieve passwords, and work with safes, safe members, and accounts.

 

New Kafka Adapter

New application adapter that integrates with Apache Kafka, which is a distributed streaming platform that can be used for building real-time data pipelines and streaming apps.

 

New Orchestration Actions in the Event Orchestration runbook

In this release, 12 new out-of-the-box Orchestration Actions have been added to the Event Orchestration runbook:

 

  • Free up disk space
  • Start Apache Web Server
  • Start Microsoft SQL service
  • Start Microsoft Exchange service
  • Start SNMP service
  • Start Print Spooler
  • Start PATROL Agent
  • Start Oracle service
  • Start Microsoft Skype service
  • Start BMC Remedy AR System Server service
  • Start RSCD agent
  • Start TrueSight Server Automation service

 

Support for encrypted headers in the REST adapter

With this release, the REST adapter now supports specifying encrypted data in the headers element in a request.

 

Support for PowerShell Core in the PowerShell adapter

PowerShell adapter now supports the new edition of Microsoft PowerShell Core. By default, the adapter invokes PowerShell commands using either the PowerShell.exe or Xcmd utility. To use PowerShell Core, you must specify the executable in the adapter configuration.

 

Support for invoking multiple commands using the Common Operations Actions utility

With this release, you can now use the Invoke Command Common OA utility workflow to invoke multiple commands using the <commands> element. This can only be done using the SSH mechanism for invoking commands.

 

Support for new operations in TrueSight Network Automation adapter

In this release, the following new operations are added to the TrueSight Network Automation adapter, which support the TrueSight Network Automation Web Services API.

 

API class

Operations

The RuleService class provides services to retrieve and import rules.

  • Import Rules
  • Get Rule
  • Get Rules
  • Get Abbreviated Correctable Rules

The UserService class provides services to add, modify, delete,
retrieve all users, and retrieve a particular user by using the user name or user key.

  • Get Users
  • Get User by Key
  • Get User by Name
  • Add User
  • Modify User
  • Delete User

The ComplianceService class provides calls related to
TrueSight Network Automation compliance.

  • Create Compliance Predefined Job
  • Execute Compliance Job
  • Get Compliance Detail Results
  • Get Compliance Summary Results

 

 

For more details please take a look at the documentation here:

https://docs.bmc.com/docs/display/tsoc201902/20.19.02+enhancements

Share This:

BMC Change Automation 2.0 is an integration between BMC Server Automation and BMC Remedy Change Management. The communication between the two applications is achieved through BMC Atrium Orchestrator. This solution improves overall efficiency and effectiveness of IT Operations through improved automation and coordination of Change Management activities.

 

The goal of this use case is to automate the change tracking process whenever an automated job execution requires approval.

 

Products needed in this use case

  • An automation system such as BMC Server Automation (running on premises)
  • An intermediate transport layer such as BMC Atrium Orchestrator (running on premises)
  • A change management system such as BMC Remedy Change Management (running on premises or on demand)
Share This:

TrueSight Orchestration platform v8.2 has been certified against external RSSO 19.08

Share This:

Remedy and CMDB adapters from TSO content version 20.19.01 have been certified against Remedy version 19.08.  Click here for related documentation.

Share This:

TrueSight Orchestration platform v8.2 has been certified against external RSSO 19.05

Share This:

Version v3.0 is available on below link

TSO/BAO Monitoring Script v3.0

 

The Script is designed to Monitor Grid Manager, Repository Manager, CDP's and Peers for critical attributes like for Peer it keeps a tab on Available Memory, Used Memory, Total Heap Memory, JVM Uptime, Management Grid Status, Main Grid Status, CDP/Peers Components Status (Health, Library Manager, Configuration, Context, Scheduler, Metrics, Job Manager, Adapter Manager, Activity Processor) and All Adapter status active on any Peers in the Grid. In case script find any issue in the adapters, grid or peer components it sends an email notification to the eMail address mentioned in the "Config.xml"

 

The script/tool has been written in python 3.6.6 version and can be run Windows or Linux machine irrespective of your BAO environment, Script leverages BAO REST API and Python web scraping techniques to collect data from REPO, Grid Manager and Peers.

 

To run the Script/Tool in Windows you can either directly run the executable file without the need of installing python 3.6.6 and its supporting library or you can install the python 3.6.6 and add required modules. (required module : requests)

 

To run script in Linux you would have to download and install python 3.6.6 or above and add "requests" module via pip or manually.

 

There are two version of the script attached, version v1.0 has been designed and tested primarily for BAO version 7.9.x and version v2.0 has been designed for BAO/TSO 8.x and above. All configurable parameter of the script/tool are controlled by "Config.xml" which should be kept in the same folder as script.

 

Version v1.0 features :

  • Monitors Grid Status, Active Threads,  Available Memory, Uptime etc

  • Peer Components Status

  • Adapter Status on all peers

  • Send Email Notification

  • Silent mode where all the result of the script get logged in log file.

 

Version v2.0 features: (version 2 has optimized code as from BAO/TSO 8.x peer components status are available through API and web scraping in not required to collect the same)

  • Monitor Repository

  • Monitors Grid Status, Active Threads,  Available Memory, Uptime etc

  • Peer Components Status

  • Adapter Status on all peers

  • Send Email Notification

  • Silent mode where all the result of the script get logged in log file.

Version v2.1

  • Password Encryption in Config.xml file
  • Password encryption tool

 

Version v2.1.1 (Fixes and Enhancement)

  • Reacquire authentication token when session expires.
  • Deduplication of Email Notification: Email notification are now only sent once to report unique issue unless there is a change in status of the issue email notification will not be sent in each iteration.

 

Enhancement in development:

  • Create Incident ticket in ITSM tool (Remedy or ServiceNow) to report the issue. (available in v3.0)
  • Create Event in Truesight Infrastructure Management aka TISM via REST API (available in v3.0)
  • Run Script/tool as Windows Service (In development)
  • Basic Remediation to fix identified problem (In development)

 

Version v3.0 is available on below link

TSO/BAO Monitoring Script v3.0

 

Enhancements in v3.0
----------------------
- Create Incident ticket in ITSM tool (Remedy or ServiceNow) to report the issue.
- Create Event in TrueSight Operations Management to report the issue.
- Monitor Running, Compensated and Completed Job Count in Grid and peers and notifications will be trigger when threshold
limit is reached or when any Job compensate.
- Monitor Embedded and External RSSO Status.

 

Fix
- Deprecated library message comes while reading values from Config.xml has been fixed
- Use of python minidom library to read xml has been removed as its support in future version of Python is coming to end
- InsecureRequestWarning message issue has been fixed
- Logging improve in console and in logs

 

Steps to configure the script. (Note: Ensure script or executable and Config.xml file are kept in same folder)

1. Getting the Grid ID for your Grid Manager, login to the Grid Manager and go to Manage>Grids>Select your Grid Name and click on pencil sign for edit. copy the ID  and Grid Name as show below and past it in "Config.xml"

2. Provide your CDP server IP/FQDN and port details along with BAO/TSO admin account in the "Config.xml", also in "schedule-interval" provide the time interval in secs for script to check Grid Status, default is set to 90 sec however I would recommend to use at least 300+ sec (i.e. 5 mins + ) as "schedule-interval".

3. If you have only one Peer (i.e CDP) set "monitor-peers" to "False", else to monitor additional peers like HACDP, AP's and LAP's set it to "True" and provide peer details as show below in the respective peer tag.

4. SMTP server details are crucial for this script and you can customize email notification subject or body text, script support both "secure" and "unsecure" connection, for my local mail server I have set the field "Secure" as "False" however most mail servers required secure connections so set it to true.

 

5. If you are using self signed or CA signed certificates in your grid and peers set the "AllowInsecureRequest" as "True", else for manage MPKI signed certificate this can be set as "False", If you are running the script for initial test and wants to print the status/result on screen, set "print-onscreen" as "True". However I would suggest to set this on "False" once the configuration is completed properly so that script can be run in background and you can review things from "BAOMonitioring.log" (Note: Set the logging-level to "DEBUG" when 'print-onscreen' is set to "False" and if 'print-onscreen' is set to "True" set the logging-level to "INFO" )

 

6. Set the threshold limit for "Available Memory" is set via memory tag, its basically the memory limit after which script will start sending email notification to inform that available free memory of Java heap has dropped below set limit (default has been set as 200 MB) and Active Threads is set via threads tag, it basically is a trigger if BAO/TSO is consuming more thread than set limit as shown below

7. Repository URL, needs to be set only for version v2 script as show below.

Sample Config.xml

<ConnectionDetail>
   <server>192.168.32.123</server>
   <port>38080</port>
   <schedule-interval>90</schedule-interval>
   <user>aoadmin</user>
   <password>admin123</password>
   <GridID>urn:jxta:uuid-44D91B15DA074253825D94A184EE308802</GridID>
   <GridName>MyGrid</GridName>
   <AllowInsecureRequest>True</AllowInsecureRequest>
   <print-onscreen>True</print-onscreen>
   <EmailSetting>
   <SMTPServer>127.0.0.1</SMTPServer>
   <SMTPPort>587</SMTPPort>
   <Secure>False</Secure>
   <EmailUsername>support@test.local</EmailUsername>
   <EmailPassword>admin123</EmailPassword>
   <NotificationEmailAddress>admin@test.local</NotificationEmailAddress>
   <Subject>BAO Monitoring script found some error in the Grid</Subject>
   <Message>BAO Monitoring script reported concerns for below components</Message>
   </EmailSetting>
   <monitor-peers>True</monitor-peers>
   <peers peerType="HACDP">
   <peer>https://hacdp.test.local:38080</peer>
   </peers>
   <peers peerType="AP">
   <peer>https://ap1.test.local:58080</peer>
   <peer>https://ap2.test.local:68080</peer>
   </peers>
   <peers peerType="LAP">
   <peer>http://lap.test.local:48080</peer>
   </peers>
   <Threshold-limit>
   <memory>200</memory>
   <threads>400</threads>
   </Threshold-limit>
   <repoUrl>https://bao.test.com:28080/baorepo</repoUrl>
   <logging-level>INFO</logging-level>
</ConnectionDetail>

 

Note: If you don't have HACDP or AP or LAP, comment the particular tag in Config.xml using <!-- <tag>--> or remove the tag.

 

Sample Config.xml for 2.1 version.

<ConnectionDetail>
   <server>bao.test.local</server>
   <port>38080</port>
   <schedule-interval>90</schedule-interval>
   <enable-encryption>True</enable-encryption>
   <user>aoadmin</user>
   <encrypted-password>V1ZkU2lhOSGhOYWswOQ==</encrypted-password>
   <GridID>urn:jxta:uuid-E5D1AB3B3CB94AA48A93A7E2BE2814A702</GridID>
   <GridName>MyGrid</GridName>
   <AllowInsecureRequest>True</AllowInsecureRequest>
   <print-onscreen>True</print-onscreen>
   <EmailSetting>
   <SMTPServer>smtp.test.local</SMTPServer>
   <SMTPPort>465</SMTPPort>
   <Secure>True</Secure>
   <EmailUsername>admin@test.local</EmailUsername>
   <Email-encrypted-password>V1ZkU2RHRlhOSGhOYWswOQ==</Email-encrypted-password>
   <NotificationEmailAddress>support@test.local</NotificationEmailAddress>
   <Subject>BAO Monitoring script found some error in the Grid</Subject>
   <Message>BAO Monitoring script reported concerns for below components</Message>
   </EmailSetting>
   <monitor-peers>True</monitor-peers>
<!-- <peers peerType="HACDP">
  <peer></peer>
  </peers> -->
   <peers peerType="AP">
   <peer>https://ap1.test.local</peer>
   </peers>
<!-- <peers peerType="LAP">
  <peer></peer>
  </peers> -->
   <Threshold-limit>
   <memory>200</memory>
   <threads>400</threads>
   </Threshold-limit>
   <repoUrl>https://bao.test.local:28080/baorepo</repoUrl>
   <logging-level>INFO</logging-level>
</ConnectionDetail>

 

Note: For password encryption to work set "enable-encryption" to true and provide BAO password and SMTP password as encrypted through encryption tool.

 

Steps to Run or Deploy the script or executable.

  • In Windows with .exe file.

        After Configuring the "Config.xml" file double click on executable to run directly or run it from command prompt.

  • In Windows from .py file

        After Configuring the "Config.xml" file, Open command prompt and Type "python" then space followed by the script file name or to run in background type pythonw then space followed by the script file name.

  • In Linux from .py file

        After Configuring the "Config.xml" file, from terminal type python3 then space followed by the script file name and to run in background type python3 then space followed by script file name space followed by "&"

       example for running in background

               python3 BAOMonitoring_v2.py &

 

 

Encrypting Password for version 2.1

  • To encrypt password run the passwordtool.exe in windows and provide the password string as show below along with operation as "encrypt" and copy the encrypted output to the config.xml file for respective encrypted password tag.

        passwordtool.exe -p P@ssw0rd -o encrypt

PLEASE NOTE: THIS IS NOT AN BMC OFFICIAL SCRIPT OR TOOL FOR MONITORING BAO/TSO, BMC SUPPORT WILL NOT BE ABLE TO PROVIDE YOU ANY ASSISTANCE FOR THE SAME.

The Script/Tool has been designed only as a proof of concept by me, so kindly use it at your own discretion.

 

 

Share This:

At times it is required to reset the Test Env. CDP or any other peer back to freshly installed state, to do that, follow these simple steps and take a backup file system before doing so.

 

  • Stop the CDP or Peer Service.
  • Removed files from KahaDB located at AO_HOME/server/.jms/activemq-data/ao-grid-framework-embedded-broker-<guid>/KahaDB
  • Removed log files located at AO_HOME/tomcat/logs

 

Reset Peer:

Removed following:

  • "server" folder located on AO_Home
  • "messages" folder located on AO_Home
  • all XML files in "config" folder except authentication.xml, tuning-config.xml and installation_audit.xml
  • all files in tomcat/work/Catalina/localhost (except RSSO folder for embedded RSSO)
  • all files in tomcat/temp

Then start peer service.  It will re-create all those files and directories, just like the first time it starts up.

 

NOTE: These steps are only for non production environment, do not try these step in production.

 

 

Share This:

TrueSight Orchestration v8.2.00

A containerized deployment version combined with a refreshed repository UI and event orchestration enhancements drives value for customers:

 

  • Containerized Deployment:  The solution can now be deployed in a containerized version on the Docker engine.
    • Benefits: Faster adoption and time to value for orchestration use cases; seamless upgrade and install experience; container benefits of elastic scalability, portability and OS independence extended to Orchestration
  • Refreshed Repository UI: new, modern UI for the repository where customers can manage content and create new workflows.
    • Benefits: Improved user experience for building customized automation workflows.
  • Event Orchestration runbook (TrueSight Orchestration Content 20.19.01): Tighter integration with TrueSight Operations Management enables an operator to initiate actions from the TrueSight console which trigger triage and remediation workflows in TrueSight Orchestration. New use case “Host Down” introduced as an OOTB feature as well as support for custom orchestration use cases.
    • Benefits: A more automated and streamlined way to deploy automated remediation workflows to decrease MTTR and drive ITOps efficiencies and cost savings. 

 

Any question or feedback? comment below

For more information, see BMC Docs release notes here:

8.2 - TrueSight Orchestration

20.19.01 - Event Orchestration runbook

Share This:

Key Features

 

8.2

 

  • For the first time, Containerised deployment of TrueSight Orchestration platform and content
  • Refreshed user interface and improved user experience for Repository
  • Support for RSSO 18.11 and 19.02

 

20.19.01

 

Event Orchestration

 

Event Orchestration provides a seamless and out of the box orchestration capability via TrueSight Operations Management (TSOM) to automate event life cycles.  In this release we have introduced below features which are available from upcoming TSOM v11.3.02 onwards;

 

  • TSO Component registration in TSOM
  • Context aware orchestration actions in TSOM
  • Intelligence to detect and update incidents created via BSR
  • Support for custom orchestration actions
  • New out of the box “Host Down” use case

 

Adapter Certifications

 

  • VMware Infrastructure adapter now supports VMware vSphere version 6.7
  • BMC TrueSight Operations Manager adapter now supports BMC TrueSight Operations Manager 11.3.01
  • BMC Server Automation adapter now supports TrueSight Server Automation 8.9.04
  • BMC Network Automation adapter now supports TrueSight Network Automation 8.9.04
  • BMC Remedy AR System adapter now supports BMC Remedy AR System 18.08
  • BMC Atrium CMDB adapter now supports BMC CMDB 18.08

 

Adapter Enhancements

 

  • HTTP adapter now supports application/json content-type in the body
  • REST adapter now supports encrypted headers

 

 

Updates

 

  • 8.2 onwards, Oracle Java 8 has been dropped as the bundled java platform.  It has been replaced by Azul Java 8.
  • Support for Oracle Solaris for platform TSO installation has been dropped 

 

 

For more details please take a look at the documentation here:

8.2 -  https://docs.bmc.com/docs/TrueSightOrchestration/82/8-2-00-enhancements-821041332.html

20.19.01 - https://docs.bmc.com/docs/TruesightOrchestrationContent/201901/20-19-01-enhancements-823454918.html

 

Share This:

For a quick product overview, answers to How To questions, understanding product fundamentals and some advance topics please refer to this Youtube playlist with more than 100 videos on TrueSight Orchestration;

 

https://www.youtube.com/watch?v=xzFzfaUYXD4&list=PLr4ck07lc-F90c2U2Qxd2RYbeYiEKylkr

Share This:

Remedy and CMDB adapters from TSO content version 20.18.01 have been certified against Remedy version 18.08.   Click here for related documentation.

Share This:

TSO content version 20.18.01 has been certified against TrueSight Server Automation (TSSA) version 8.9.03.

Share This:

TSO platform v8.0 SP1 (8.0.01) and v8.1 Patch 1 (8.1.00.001) now support Remedy Single Sign-On version 18.08 for external RSSO implementation.

Filter Blog

By date:
By tag: