This topic describes the enhancements in BMC Atrium Orchestrator version 20.17.01. For a complete list of new features in this release, see What's new in 20.17.01.
Platform - Content compatibility
BMC Atrium Orchestrator Content 20.17.01 is compatible with the following versions of BMC Atrium Orchestrator Platform:
- 7.9 and its service packs and patches
For the latest released BMC Atrium Orchestrator Platform online technical documentation, see BMC Atrium Orchestrator Platform.
Support for VMware vSphere version 6.5
The VMware Infrastructure application adapter now supports VMware vSphere application version 6.5. The adapter configuration and processes remain unchanged.
For more information, see VMware Infrastructure adapter.
Updated values for the
<version> element for the CMDB adapter top-level processes
If your BMC Atrium CMDB version is 9.0 or 9.1, you can now specify the appropriate version in the
<version> element for the BMC Atrium CMDB adapter top-level processes (Create Items, Find Items, Update Items, and Delete Items processes). In earlier releases, one could only specify the value for the version up to 8.1 despite the BMC Atrium CMDB version 9.0 and 9.1 being supported.
For more information, see Top-level processes for the BMC Atrium CMDB adapter.
Support for Kerberos authentication protocol for the HTTP adapter
The HTTP adapter now supports Kerberos protocol to securely authenticate clients prior to executing HTTP requests on a remote host. To use Kerberos authentication, the application user must obtain ticket-granting tickets from the Kerberos server. For more information, see HTTP adapter.
Support for NTLMv2 authentication protocol for the HTTP adapter
The HTTP adapter now supports NT Lan Manager v2 (NTLMv2) authentication protocol for both secure and insecure communication for the proxy and target server. For more information, see HTTP adapter.
Support for multipart file upload by using the HTTP adapter
By using the HTTP adapter, you can upload multiple files and data as the adapter now supports multipart/form-data requests to a specified URL. By using the POST action, you can specify the
multipart/form-data in the HTTP request header to upload files or data in a single body. Each body part must be specified as a separate entry along with the
<value> elements specifiedin the adapter request.
For more information, see HTTP adapter request and response for a Post action.
Support for multiple commands in the same session for the PowerShell adapter
In earlier versions of the PowerShell adapter, you cannot run multiple commands in the same session on a remote server. A new element,
<enable-psremoting-session> is added to the adapter request, which enables to run a list of commands in the same session on a remote server. To use this feature, you must also specify the
<enable-psremoting> as true.
Only commands that are executed independently and do not return a PowerShell prompt can be run in the same session. For example, DiskPart commands, which are a set of separate commands that open another shell are are not supported by the adapter.
For more information, see Adapter request and response for the PowerShell adapter.
New common utilities to support the Tokenize Large String process
The following new utilities are added to the XML utilities module in the AutoPilot-AD-Common_Utilities module for parsing very large string input:
- Create For Loop XML
- String to XML using Delimiter
For more information, see XML utilities.
PowerShell version element deprecated from the PowerShell adapter
In earlier versions of the PowerShell adapter, if you want to run remote commands by using the PowerShell adapter, you must specify the
<powershell-version> element in the adapter configuration. Irrespective of the Microsoft Windows PowerShell version running on the host, one needed to specify the
<powershell-version> as 2.0 in the adapter configuration.
In this release, the
<powershell-version> element is deprecated and no longer needed while configuring the adapter.
You no longer require to specify the Microsoft Windows Powershell version to run remote commands on the specified host. Commands are run by using the PowerShell version available at the target system or the local system path.
For more information, see Configuring the PowerShell adapter.