Skip navigation
Share This:

Coming up on October 18, 2018 is BMC’s annual user event, the BMC Exchange in New York City!




During this free event, there will be thought-provoking keynotes including global trends and best practices.  Also, you will hear from BMC experts and your peers in the Digital Service Operations (DSO) track.  Lastly, you get to mingle with everyone including BMC experts, our business partners, and your peers.  Pretty cool event to attend, right? 


In the DSO track, we are so excited to have 3 customers tell their stories. 

  • Cerner will speak about TrueSight Capacity Optimization and their story around automation and advanced analytics for capacity and planning future demand.   Check out Cerner’s BizOps 101 ebook
  • Park Place Technologies’ presentation will focus on how they leverage AI technology to transform organizations.
  • Freddie Mac will join us in the session about vulnerability management.  Learn how your organization can protect itself from security threats.  Hear how Freddie Mac is using BMC solutions. 


BMC product experts will also be present in the track and throughout the entire event.

  • Hear from the VP of Product Management on how to optimize multi-cloud performance, cost and security
  • Also, hear from experts on cloud adoption.  This session will review how TrueSight Cloud Operations provides you visibility and control needed to govern, secure, and manage costs for AWS, Azure, and Google Cloud services.


At the end of the day, there will be a networking reception with a raffle (or 2 or 3).  Stick around and talk to us and your peers.  See the products live in the solutions showcase. Chat with our partners.  Stay around and relax before heading home. 


Event Info:

Date: October 18th 2018

When: 8:30am – 7:00pm

  • Keynote begins at 9:30am
  • Track Sessions begin at 1:30pm
  • Networking Reception begins at 5:00pm

Where: 415 5th Ave, NY, NY 10016


For more information and to register, click here.


Look forward to seeing you in NYC!  Oh, and comment below if you are planning to attend!  We are excited to meet you.

Share This:

TrueSight Orchestration platform v8.1.00 patch 1 has been released.  Below issues have been fixed in the same;


Issue IDDescription
DRAUM-23717Adapter executions with large datasets in the response take a long time to return a response.
DRAUM-23879If no input parameters are passed in the body for the Execute Process REST API call, a null-pointer exception occurs. This issue occurs only if the logging level is set to DEBUG for the Web Services component of the platform.


For details on downloading and installing the patch, please visit below link;

Share This:

Highlights of the release:



BMC TrueSight Orchestration has been re-branded to TrueSight Orchestration



New Runbooks

  • New ITSM Automation runbook with pre-built workflows to provide Closed Loop Change Automation.  Features include improved bidirectional integration between the Change ticket and the Automation tool it is used with, improved bulk CI association with ability to log failed CI associations, support for user defined Change Templates among others.
  • New Event Orchestration runbook to automate event life-cycles leveraging a scalable, extensible and configurable framework with out of the box support for BMC Remedy ITSM and TrueSight Operations Manager.


Adapter Certifications

  • BMC Database Automation adapter now supports BMC Database Automation v8.9.02
  • BMC Network Automation adapter now supports BMC Network Automation v8.9.02
  • BMC Server Automation adapter now supports BMC Server Automation v8.9.02
  • BMC TrueSight Operations Manager adapter now supports BMC TrueSight Operations Manager v11.0
  • BMC Remedy Adapter now supports BMC Remedy Action Request System 9.1.03


Adapter Enhancements

  • The TrueSight Operations Manager actor and monitor adapter now supports Transport Layer Security (TLS) mode encryption protocol.
  • New operations are added to the Remedy AR System actor adapter to support bulk transactions.

Any question or feedback? comment below

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

Share This:

Highlights of the release:


Remedy Single Sign-On support:

Support for following RSSO versions has been introduced in this release;

  • RSSO 18.02 (External only)
  • RSSO 9.1.04 (External only)


Infrastructure updates:

  • BAO Development Studio is now supported on Microsoft Windows Server 2016 (Standard edition) and Microsoft Windows Server 2012 R2 (Standard edition)
  • Platform metrics now supports Microsoft SQL Server 2016 (Enterprise edition)
  • Java version is updated to 1.8.0_162
  • Embedded Apache Cassandra database version has been upgraded to v3.11.2


User Interface enhancements -

Pagination has been introduced in Grid Manager permissions page for better user experience.


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


Share This:

Highlights of the release -


Job Dashboard

  • View historical job count in a dashboard view
  • Data can be pulled from  “Today” to “Last 365 Days”




Job List View

  • View historical job execution data for last 30 days
  • Ability to view job result for both Completed and Compensated jobs by clicking on the job status




Usage Dashboard

  • Provides a comprehensive view of the adapters usage on the Grid




Other Significant features

  • XSLT 2.0 Support
  • Kerberos support in HTTP adapter
  • Wrappers for Platform REST API


Infrastructure updates

  • BMC Atrium Orchestrator Server is now supported on Microsoft Windows 2016
  • Support for Microsoft Edge Web Browser
  • Tomcat application server version is upgraded to 8.0.44
  • Java version upgraded from 1.8.0_66 to 1.8.0_144


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

Share This:

Highlights of the release -


Adapter Enhancements:


  • New REST adapter for a JSON friendly expereince
  • Support for vSphere 6.5 in VMware adapter
  • Session based support in PowerShell adapter
  • Support for NTLMv2 authentication protocol for the HTTP adapter
  • Support for multipart file upload by using the HTTP adapter
  • Support for Kerberos authentication protocol for the HTTP adapter
  • Java Mail API upgrade in Email adapters
  • Platform REST API for –
    • Schedule Management
    • Peer Management


Module Enhancements:


  • New common utilities to support the Tokenize Large String process
  • New operations added to the Microsoft Active Directory adapter under:
    • User Management
    • Quota Management
    • Group Management
    • Contact Management


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

Share This:

E-Bonding is a complex process as it involves intricate field mapping between two ITSM tools.  Many customers end up building bespoke solutions which are difficult to support, scale and extend.


BMC now provides an Out of the Box solution for E-Bonding called “VIPCON E-Bonding Runbook for BMC Atrium Orchestrator”.   Features include;

  • UI driven approach for creating an E-Bond
  • Support for bi-directional communication between interfaces
  • Scalable and Robust
  • Provides a transaction database to recap loss of communication


I am happy to announce that  “VIPCON E-Bonding Runbook for BMC Atrium Orchestrator v2.0.00" is now GA as of 31st August, 2017.


Please email me at if you have any queries.

Share This:

If you are new to using BAO with Remedy SSO authentication, you might find these new videos helpful when getting started.


For a demonstration of how to create a local user authentication realm, see the new video on the Working with realms - BMC Atrium Orchestrator Platform 7.9 - BMC Documentation  topic in the BMC Atrium Orchestrator Platform 7.9 wiki.


For a demo of how to create users and roles and how to add users to a role in Remedy SSO, see the video on the Creating and managing local users and roles in Remedy Single Sign-On - BMC Atrium Orchestrator Platform 7.9 - BMC Docume…  topic in the BMC Atrium Orchestrator Platform 7.9 wiki.


Let us know if you find the video helpful by rating the blog post or commenting on the wiki topics.

Share This:

I quite often get this sort of scenario where customer have a requirement to deploy a Peer in a different network or in DMZ while keeping communication between CDP's and Peer in other network using NAT IP address.


Below is a high level overview of how this sort of deployment configuration which provides connectivity with an LAP located in a different network/DMZ using NAT IP address. This deployment minimizing the impact to the DMZ firewall rules. The grid is deployed in a high-availability configuration to provide redundancy for the processing peers. Inside the DMZ or Other network, a lightweight activity peers exist which can host required adapters.


Lets understand some basic concept of Peer Discover and Peer Communication which is associated with JMS broker.

Each peer is associated with a JMS broker which hosts a set of queues which is involved to send messages targeted to the respective peer.  A given broker may host queues for any number of peers. The combination of broker URI and topology queue is referred to as an "advertisement".


Each peer engage and contribute in the management grid "discovery" topology, along with a subset of the peers being designed to provide discovery services to the other peers. The advertisements associated with discovery peers are persisted with each peer in the environment. Upon startup, a peer registers the advertisements for its topology with the master in the discovery topology, and periodically requests advertisements matching topology in which the peer participates.


Non discovery advertisements are never persisted and are maintained only in memory. When a peer learns about a new discovery server (this occurs when an HA CDP is added to a grid), the associated advertisement is persisted with that peer.




Broker Config

Most JMS configuration files are located in $AO_HOME/server/.jms


The broker-config.xml file specifies the JMS broker configuration for individual peer.

The XML document can have below nodes

  • external - indicates whether the broker is hosted within this peer's VM or externally
  • uri - the broker URI. This specifies the protocol, IP (or host), port, and any ActiveMQ parameters associated with the broker.
  • port-upper-bound - if present, indicates that the broker port may range from the port specified in the uri up to the number provided in this element. Upon peer startup, the first available port in the range will be used
  • listen-addresses — if present, this would enforce the server to listen only on the addresses specified
  • advertise-addresses — if present, this would enforce the server to advertise only the addresses specified


activemq-data - a directory used by ActiveMQ

certificate- the certificate used for SSL JMS connections.

disco - a directory used to hold discovery advertisements (Ideally you will find only CDP and HACDP disco file here)



In the below mentioned example, I have a data-center in which I have a CDP, HACDP, REPO and Authentication System (AM/ASSO/RSSO) based on the version of the production in use.
My CDP 1 has an host IP Address of and its NAT IP address is, My CDP - 2  has an host IP address of and NAT IP Address as Rest of my BAO components are in the same data center as CDP's expect for one LAP which is located in different location or different data center or in DMZ.  My LAP has an Host IP address as


It is possible to specify an address to advertise which can be a NAT IP other than the CDP's host IP address.

CDP Broker-config.xml (located in $AOCDPHOME\server\.jms)



<uri>ssl://CDP-IP:<Peer Communication Port>?connectionTimeout=1000</uri>


   <address>NAT IP Address of CDP</address>

    <address>CDP-1 FQDN</address>




Note: that it is also possible to use "hostnames" in the advertise-addresses block. and further host file mapping for the hostname can be done in the individual peer.

Share This:

The following table summarizes the supported upgrade paths for BAO upgrades from version 7.6.03 on. The table provides information about the authentication service option supported for each upgrade path.

For full details about upgrading to the 7.9 version of BMC Atrium Orchestrator, see Upgrading - BMC Atrium Orchestrator Platform 7.9  in the BMC Atrium Orchestrator Platform wiki.

Your current versionYour current authentication serviceSupported upgrade paths

Authentication service after BAO upgrade

Upgrades to...Use this authentication service...
7.6.03Access Manager

7.7.02, 7.8.00, 7.8.01, or 7.9.00

7.7.02Atrium Single Sign-On 8.1If your current environment is earlier than BMC Atrium Orchestrator Platform version 7.6.03, you must upgrade your platform server components to BMC Atrium Orchestrator Platform version 7.7 Service Pack 2 and then upgrade to 7.9.
7.8.00, 7.8.01Atrium Single Sign-On 9.0
7.9.00Remedy Single Sign-On
7.7.00Atrium Single Sign-On7.7.01, 7.7.02, 7.8.00, 7.8.01, 7.8.02, or, 7.7.02Atrium Single Sign-On 8.1


7.8.00, 7.8.01, 7.8.02, 7.9.00Atrium Single Sign-On 9.0
7.7.01Atrium Single Sign-On7.7.02, 7.8.00, 7.8.01, 7.8.02, or Single Sign-On 8.1


7.8.00, 7.8.01, 7.8.02, 7.9.00Atrium Single Sign-On 9.0
7.7.02Atrium Single Sign-On7.8.00, 7.8.01, 7.8.02, or, 7.8.01, 7.8.02, 7.9.00Atrium Single Sign-On 9.0


7.8.00Atrium Single Sign-On7.8.01, 7.8.02, or, 7.8.02, 7.9.00Atrium Single Sign-On 9.0


7.8.01Atrium Single Sign-On7.8.02 or, 7.9.00Atrium Single Sign-On 9.0Upgrades from 7.8.01 to 7.8.02 require a hotfix that you can get from BMC Customer Support.
7.8.02Atrium Single Sign-On7. Single Sign-On 9.0


Please provide your feedback by leaving a comment or rating the blog post.

Share This:

One of the biggest challenge which customer face who upgrade from BAO 7.6.x to BAO 7.7 or 7.8 is that ASSO doesn't allow multiple WebApp URL, and if you try to use a CNAME, Alias, VIP or Loadbalancer (to avoid single point of failure) it will alway rewrite the URL back to registered WebApp URL, which might eventually cause a  request failure if the URL is not resolvable from out network or in some case in restricted internal network.


Below example is valid for scenario where a VIP or Loadbalancer are used to access the ORCA webservice to avoid single point of failure for ORCA web service.

Lets start with an example: Assume that I have BAO CDP server named "cdp.bao.local", it’s the same name which is used during installation and is been used in web app url of ASSO, I also have an HACDP and it has a name "hacdp.bao.local", I also have a loadbalancer in front of these two server to manage the ORCA requests and avoid single point of failure, LB has Alias/CNAME as "" which I used in my code or 3rd part application to access ORCA webservice from outside the network now if I want access ORCA webservice using external url I will use "" however when the request reaches the server ASSO automatically rewrite the to registered WebApp URL  which is internal url in this case i.e.  "https://cdp.bao.local:28080/baocdp/orca" or "
https://hacdp.bao.local:28080/baocdp/orca" (based on where LB direct the request) which may not be accessible from outside network irrespective of whether ORCA is added in excluded URL in SSO. This is the default behavior of Atrium SSO and cannot be changed to the best of my knowledge.

To solve this if we re-register ASSO agent with external name (CNAME or Alias) or LB Name, ORCA will start to work fine however base on the way your infra is been design or number of redirection in your network you may find your self stuck in a re-direction loop in browser whenever you try to access grid console using internal url which is "https://cdp.bao.local:28080/baocdp" or
"https://hacdp.bao.local:28080/baocdp"  since URL rewrite to "" or end with a message saying too many re-directions. The same happen if a CNAMEor VIP is used.


To resolve this problem we would have to tweak the system a bit with below mentioned trick.
What we need to do is use a Name/FQDN which is accessible internally (i.e. it can be resolved internally) and it should be accessible externally (i.e. name should be resolved to your loadbalancer IP address). Since for accessing Grid console we need a direct access so that we don't get stuck in redirect loop. however for ORCA It usually work irrespectively.


Below are the high level overview of the steps we will be performing.
1. Register the CDP ASSO agent with LB or CNAME FQDN lets say
2. Add a mapping for CDP IP to Loadbalancer FQDN in hosts file of the machine from which Grid Manager will be called and Administrate through those machine.




Apart from above there is alternative option

1. Continue to use CDP and HACDP name in ASSO agent. However make the calling system resolve the CDP and HACDP name to a IP address of LB.

2. Add a hostname mapping for CDP and HACDP name to Loadbalancer IP/ VIP in the external system which are calling ORCA web service.




Note :

1. This workaround would offer you kind of High Availability for ORCA webservice with single end point (for consuming in 3rd party application and custom codes) considering the fact that the requests reached the respective CDP nodes without any failure from Network and OS end, although product was not originally intended to offer High Availability for ORCA  webservices with single point to consume, as per the Product design HA grid configuration with the CDP and HA-CDP manages all CDP failures by election. That is, configuration will provides redundancy for job processing elements of the grid.


2. This problem has been addressed in BAO 7.9 release when RSSO will be introduce as a new authentication system since for a typical new installation RSSO will be using the same tomcat instance as BAO and there will be no URL rewrite in it.



New Workaround


Recent Development showed as that there is one more workaround which can be implemented by modifying the web.xml of the CDP's which will by pass the redirection for Orca, RESTful and Legacy web service. 


Below are the changes which we need to make in the CDP's web.xml located in ("<BAO_CDP_HOME>\tomcat\webapps\baocdp\WEB-INF\web.xml")

Change SSO agent URL pattern to /gm/* instead of /* in web.xml as shown below thereby preventing SSO JEE filter from redirecting or rewriting URL to register WebApp URL when ORCA, Legacy or Restful Web Services are called.





            <!-- SSOPrincipal -->





            <!-- SSOToken -->





            <!-- Identifier from SSOToken -->





            <!-- Name from SSOPrincipal -->













With this new workaround you don't have to making any further changes in the host file mapping and you would be able to use Alias, VIP and CNAME while calling webservice.

Share This:

Here are two new videos to help you get started with Development Studio.

Navigating Development Studio

This video introduces the Development Studio UI and covers some of the basics about working in the interface.

Let us know if you find the video helpful by rating the blog post, commenting on the video, or commenting on the topic.


Connecting Development Studio to a BAO Environment

This video shows you how to connect Development Studio to a BAM Atrium Orchestrator environment.

Let us know if you find the video helpful by rating the blog post, commenting on the video, or commenting on the topic.

Share This:

We often hear from our customers that videos are a really helpful way to learn how to get the most out of our products. Well, we have been doing something about that feedback. The BMC Atrium Orchestrator (BAO) team, (including folks in Support, the field, and R&D) has been busy making more "how to" videos to help you harness the power of CLM. In fact, we have added over 75 new BAO videos in the past few months! Please check them out in the How to Videos - BMC Atrium Orchestrator playlist on the BMC Communities YouTube channel. The playlist is ordered by date, so you will see the newest ones listed first. Please look them over and let us know if you find these videos helpful by Liking or Disliking the video or leaving a comment.

If you would like to see the videos in context with the related technical documentation, you can access the listing of topics containing videos here:

Share This:



the integration with Remedy ARS / ITSM is always a very interesting task. The "orchestration" folks are usually not exposed to ARS / ITSM to the extend that they can help themselves and depend on an ITSM resource. To help the "orchestrator" within you handle this better, review these video's.






Once you have a handle on this, review "assignment" configuration, as this is most often overlooked and can prove to be a challenge for the orchestration. Assignment is a per company configured topic and therefore a bit challenging to explain. Each company has their own way of handling this and I suggest to get in touch with the ARS / ITSM admin to hash that out properly.


BTW, this is one of the building blocks for "Service Desk Automation"


Stay tuned 4 more ....


Regards, V.

Share This:



I've played around with the grid manager status page and the underlying JSP. My goal was to add the YouTube video links as RSS feed. A new BAO user will have an easy way to get to training material, the community and the like. This is of course not part of the product, not yet ....


Would you like something like this to be included in the GM?

See a working screenshot:


Custom GM Status.png


Regards, V.

Filter Blog

By date:
By tag: