This section contains information about enhancements in version 20.14.02 of BMC Atrium Orchestrator Content.
For information about issues corrected in this release, see Known and corrected issues.
Application adapter enhancements
The following new features and changes have been added to the BMC Atrium Orchestrator application adapters:
Introducing the DNS adapter
The DNS adapter allows you to create an A record, or a PTR record for a DNS server. The application adapter for the Domain Name Server contains an actor adapter. For more information, see DNS adapter.
Introducing the Microsoft Hyper-V Server 2012 adapter
The BMC Atrium Orchestrator application adapter for the Microsoft Hyper-V Server invokes a request to the Hyper-V Server 2012 R2 by executing PowerShell commands. The application adapter for Hyper-V Server consists of an actor adapter that supports empty, single, and multiple configuration formats.
For more information, see Microsoft Hyper-V Server 2012 adapter.
Ability to specify the working directory for Infoblox NIOS adapter
For the Infoblox NIOS actor adapter, you can now specify the working directory from where you want to run the Infoblox perl scripts. The element is added to the adapter configuration. For more information, see Configuring the Infoblox NIOS adapter.
Supported application versions
BMC Remedy IT Service Management 8.1.02
BMC Remedy AR System 8.1.02
BMC Atrium CMDB8.1.02
BMC Service Request Management 8.1.02
|BMC Remedy AR System adapter||Change Management module||-|
|BMC Atrium CMDB adapter||ConfigurationManagement||-|
|-||Task Management module||-|
|-||Incident Management module||-|
|-||Problem Management module||-|
|-||Work Order Management module||-|
|BMC BladeLogic Automation Suite 8.6||BMC Server Automation adapter||-||BMC Continuous Compliance for Servers|
|BMC Network Automation adapter||-||BMC Continuous Compliance for Networks|
|BMC Database Automation adapter||-||BMC Continuous Compliance for Databases|
|BMC ProactiveNet Performance Manager 9.5||BMC ProactiveNet Performance Manager adapter||-||BMC Triage and Remediation Run Book|
|BMC Remedyforce Summer ' 14||BMC Remedyforce Summer adapter||-||-|
|Microsoft Hyper-V Server 2012 R2||Microsoft Hyper-V Server 2012 adapter||-||-|
|VMware vSphere 5.5||VMware Infrastructure adapter||-||-|
|VMware vCloud Director 5.5||VMware vCloud adapter||-||-|
Base adapter enhancements
The following new features and changes have been added to the BMC Atrium Orchestrator base adapters.
Support for Windows PowerShell 3.0 and 4.0
The PowerShell adapter now supports Windows Powershell version 3.0 and 4.0. You can now run the adapter requests on any of the supported versions of Windows PowerShell. For more information, see PowerShell adapter.
Support for SITE command in FTP adapter
The FTP adapter now supports site command, which can send site specific commands to remote server.
For more information, see FTP adapter request and response for site command.
xCmd utility supports command timeout
The Windows Command and PowerShell adapters utilise the underlying xCmd utility to run adapter requests on a remote host. You can specify the adapter timeout value, in seconds, for both the adapters. However, you cannot change the default timeout value (15 minutes) in the xCmd utility. If the adapter request takes a long time to execute, the adapter terminates the process under which the xCmd utility is launched, and the xCmd process is terminated forcefully.
When terminated, the xCmd utility does not perform the post command execution process, which includes stopping the xCmd service, uninstalling the service, and deleting the xCmd service binary. The command or the script remains in hung state forever and one needs to manually terminate the process by accessing the target computer.
In this release, a new timeout command line argument is supported for the xCmd utility, which allows you to specify the command timeout, in seconds, while executing the adapter request. The xCmd timeout should be lesser than that of the adapter request to ensure that the xCmd utility expires before the adapter request.
HTTP adapter request supports timeout
For the HTTP adapter, one could specify the timeout value in the adapter configuration. With this release, you can now specify timeout value dynamically, that is while running the adapter request. The timeout value determines the amount of time after which the adapter request expires. For more information, see HTTP adapter.
Operations Actions Management Modules enhancements
The following new features and changes have been added to the BMC Atrium Orchestrator operations actions management modules.
Introducing a new DNS Integration Module
A new DNS Integration module contains workflows that enable you to perform basic operations while handling DNS servers. These workflows speed up the development of solutions while providing recommended implementations for performing some basic operations for the DNS servers. The DNS Integration module includes TSIG Key mappings and ReverseDNSZoneMapping . For more information, see DNS Integration module.
New Tokenize Large String process to handle large input
The Tokenize Large String process overcomes the limitation of the traditional tokenizer against large inputs by setting up a loop that detects the size of the input and parses it in 10,000-character segments, appending the segments together to create a fully-parsed result. For more information, see Tokenize Large String process.
IP Address Management module for VitalQIP now included with BMC Atrium Orchestrator Content 20.14.02
The IP Address Management module for VitalQIP is now bundled with BMC Atrium Orchestrator Content 20.14.02 installer. This module is already available as a part of the larger use case for BMC Cloud Lifecycle Management. For more information about setting up the VitalQIP module, see Enabling IP Address Management in BMC Cloud Lifecycle Management online documentation.
The following new features and changes have been added to the BMC Atrium Orchestrator run books.
Support for BladeLogic Automation Suite 8.6
The Continuous Compliance for Servers, Networks, and Databases run books now support BMC BladeLogic Automation Suite 8.6.
New modules in the Continuous Compliance for Servers run book to integrate with any ITSM application
Part of Compliance Automation, the BMC Continuous Compliance for Server Automation run book automates the integration of BMC Server Automation monitoring, auditing, compliance, and remediation processes with IT management systems such as BMC Remedy ITSM. The 20.14.02 release simplifies the configuration and customization of the solution by replacing the earlier Closed_Loop_Server-SA-Compliance module with the following modules:
This change effectively breaks out the BladeLogic Server Automation workflows from the ITSM workflows enabling them to be installed and tested independently of each other. This change should make it simpler to configure the solution and customize if required. The BladeLogic-SA-ITSM_Integration module, which is also optionally required to support this use case, remains unchanged.
You cannot upgrade from earlier versions of the run book to the current version. To use the simplified modules available in the latest release, you must deactivate the earlier Closed_Loop_Server-SA-Compliance module installed on the grid and ensure that you move any customized workflows to the new modules.
Before activating the new modules on the grid, ensure that you deactivate the existingClosed_Loop_Server-SA-Compliance module. While installing the run book, the Closed_Loop_Server-SA-Compliance module is not visible in the content installer.
For the Closed_Loop_Compliance-SA-Servers module, you must create a new COMPLIANCE JOB NAME property to the Batch and Deploy Job system objects in BMC Server Automation. For more information about creating a new property, see Creating a new job property for Closed Loop Server Audit and Closed Loop Server Compliance topic in the BMC BladeLogic Automation Suite 8.6 online documentation.