check-circle-line exclamation-circle-line close-line

vRealize Orchestrator Appliance 6.0.5 | 17 Nov 2016 | Build 4618785

Release Notes last updated on 27 Mar 2017.

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New in vRealize Orchestrator 6.0.5

vRealize Orchestrator 6.0.5 is a patch release that introduces a number of improvements and bug fixes.

  • Enhanced workflow logging, including messages that mark the start and the end of the workflow run. In case of failure, the log captures the workflow ID, the request ID, and the exception.
  • Added ability to run a Debugger in the Orchestrator client when the request is generated by an external system, such as vRealize Automation, the vCenter Web Client, or a REST endpoint.
  • Introduced Spanish locale support for the Orchestrator plug-in for vSphere Web Client.

vRealize Orchestrator 6.0.5 also introduces Control Center, which delivers a more flexible configuring, monitoring, and troubleshooting experience. Control Center contains multiple built-in capabilities:

  • Cancel workflow runs
  • vRealize Orchestrator runtime dashboard

Feature and Support Notice

The features listed below are deprecated in vRealize Orchestrator 6.0.5 and scheduled for removal in future releases. None of the deprecated features should be used as part of any vRealize Orchestrator based solution.

  • LDAP authentication.
  • The Orchestrator configuration interface has been deprecated in vCenter Orchestrator 5.5.1 and it is planned to be removed in the next major release of vRealize Orchestrator. The vRealize Orchestrator configuration should happen through vRealize Orchestrator configuration workflows and vRealize Orchestrator configuration API.
  • vRealize Orchestrator 6.0.5 is now available as an appliance and as a Windows installer. You can migrate the configuration of your existing Orchestrator to the Orchestrator Appliance. For more information, see Migrate Orchestrator Windows Deployment to Orchestrator Appliance 6.0.5. Alternatively, you can install or upgrade to version 6.0.5 the Windows-based installation of Orchestrator, by using the Windows installer. For more information, see Install and Upgrade vRealize Orchestrator 6.0.5 on Windows.

You can use the PowerShell plug-in with the Orchestrator Appliance to run PowerShell scripts on an external Windows host. See Invoke an External Script.

Deploying the VMware vRealize Orchestrator Appliance 6.0.5

VMware vRealize Orchestrator 6.0.5 is available as a preconfigured virtual appliance. The appliance significantly reduces the time and effort required to deploy vRealize Orchestrator and provides a low-cost alternative to the traditional Windows-based installation.

The Orchestrator Appliance is distributed as an OVF file. It is prebuilt and preconfigured with Novell SUSE Linux Enterprise Server, PostgreSQL, and OpenLDAP, and it can be used with vCenter Server 4.1 and later.

When the Orchestrator Appliance is used with an external database, it is suitable for any use case from lab evaluation to large-scale production environments. The appliance offers all of the components included in the regular Windows-based installation, along with the flexibility to use either the preconfigured database, or external ones like Oracle, Microsoft SQL Server or PostgreSQL. The Orchestrator appliance is certified to run at the same performance level as the Windows-based installation.

The Orchestrator Appliance is a fast, easy-to-use, and more convenient way to integrate the VMware cloud stack, including vCenter Server and vCloud Director, with your IT processes and environment.

Upgrading to vRealize Orchestrator 6.0.5

For instructions on deploying, upgrading, and configuring the Orchestrator Appliance, see Installing and Configuring VMware vRealize Orchestrator.

Important: For security reasons, the password expiry of the root account of the Orchestrator Appliance is set to 365 days. To increase the expiry time for an account, log in to the Orchestrator Appliance as root, and run the following command:

passwd -x number_of_days name_of_account

To make your Orchestrator Appliance root password last forever, run the following command:

passwd -x 99999 root

Install and Upgrade vRealize Orchestrator 6.0.5 on Windows

You can install vRealize Orchestrator 6.0.5 or upgrade Orchestrator to version 6.0.5 by running the Windows installer.


Back up the wrapper.conf, wrapper-auto.conf and log4j.xml files from your existing Orchestrator installation, if you have done any modifications to these files.


  1. If you run Orchestrator on Windows 8 or later, you must run the installer in Compatibility Mode.
    1. Right-click the vRealizeOrchestrator-6.0.5.exe and select Properties.
    2. In the Compatibility tab and select the Run this program in compatibility mode for: check box.
    3. From the drop-down menu, select Windows 7.
    4. Click Apply to apply the changes.
  2. Run the vRealizeOrchestrator-6.0.5.exe file to start the installation.
  3. (Optional) Reapply the modifications in the wrapper.conf, wrapper-auto.conf and log4j.xml files in the app-server\bin folder under the Orchestrator installation folder.

Migrate Orchestrator Windows Deployment to Orchestrator Appliance 6.0.5

You can migrate the system configuration and workflows from an earlier version of Orchestrator to the Orchestrator Appliance 6.0.5.


  • Deploy an Orchestrator Appliance on version 6.0.5.
  • Create a snapshot of the Windows-based Orchestrator virtual machine for backup purposes.
  • Back up the database of the source Orchestrator server.

    IMPORTANT: After the migration, the database cannot be used by the Windows-based Orchestrator.


  1. Stop the Orchestrator server services on the source and the destination Orchestrator servers.
  2. Export the configuration of the source Orchestrator through the Orchestrator configuration interface, see Installing and Configuring VMware vRealize Orchestrator.
  3. Install the custom plug-ins from the source to the destination Orchestrator server but do not configure them.

    NOTE: The custom plug-ins are not included in the exported configuration file.

  4. Import the exported .vmoconfig file to the Orchestrator Appliance, by using the Orchestrator configuration interface. See Installing and Configuring VMware vRealize Orchestrator.
  5. Log in to the Orchestrator configuration interface of the Orchestrator Appliance and verify that all the status indicators display a green circle.
  6. From the Troubleshooting page in the configuration interface of the Orchestrator Appliance, click the Reset current version link to force the plug-ins to reinstall with the next Orchestrator server service start.
  7. Use SSH to log in to the Orchestrator Appliance and check if all plug-in configuration files are available in the /etc/vco/app-server/plugins directory.
  8. INFO: If a configuration file is missing, you can copy it manually from the install_directory\conf\plugins folder.

What to do next

Start the Orchestrator Appliance server service and verify that all configurations are loaded correctly.

Plug-Ins Installed with vRealize Orchestrator 6.0.5

The following plug-ins are installed by default with vRealize Orchestrator 6.0.5:

  • vRealize Orchestrator vCenter Server Plug-In 6.5
  • vRealize Orchestrator Mail Plug-In 7.0.0
  • vRealize Orchestrator SQL Plug-In 1.1.4
  • vRealize Orchestrator SSH Plug-In 7.0.1
  • vRealize Orchestrator SOAP Plug-In 1.0.4
  • vRealize Orchestrator HTTP-REST Plug-In 1.1.0
  • vRealize Orchestrator Plug-In for Microsoft Active Directory 2.0.3
  • vRealize Orchestrator AMQP Plug-In 1.0.4
  • vRealize Orchestrator SNMP Plug-In 1.0.3
  • vRealize Orchestrator PowerShell Plug-In 1.0.7
  • vRealize Orchestrator Multi-Node Plug-In 6.0.5
  • vRealize Orchestrator Dynamic Types 1.0.1

Internationalization Support

vRealize Orchestrator 6.0.5 supports internationalization level 1. Although Orchestrator is not localized, it can run on non-English operating systems and supports non-English text.

How to Provide Feedback

Your active feedback over the next few weeks is appreciated. You can provide your feedback through:

  • Support Requests (SRs)
  • Orchestrator Discussion Forum

Support Requests

You can file all issues that you find as Support Requests (SRs), even if you report them to VMware by other means.

You can find the VMware Support's commitment to SRs filed by customers and instructions on how to file an SR at

Include log files in your SRs. To gather log files from Orchestrator:

  1. Go to the Orchestrator configuration interface at https://orchestrator_server_ip_address:8283.
  2. Log in with your username and password.
  3. Click Logs.
  4. Click Generate log report.
  5. Save the generated ZIP file.
  6. Upload the saved ZIP file to VMware Support.

For Orchestrator configuration issues, include an exported configuration file in your SRs. To export your configuration from the Orchestrator configuration interface:

  1. Go to the Orchestrator configuration interface at https://orchestrator_server_ip_address:8283.
  2. Log in with your username and password.
  3. Click General.
  4. Click the Export Configuration tab.
  5. Click Export.

    IMPORTANT: Do not export your configuration with a password.

  6. Save the *.vmoconfig file.
  7. Upload the saved files to VMware Support.

Earlier Releases of vRealize Orchestrator

Features and issues from earlier releases of vRealize Orchestrator are described in the release notes for each release. To review release notes for earlier releases of vRealize Orchestrator, click one of the following links:

Resolved Issues

vRealize Orchestrator 6.0.5 resolves the following issues:

  • The Orchestrator workflow presentation logs multiple NULL error messages.
    When you use multi-line SQL queries to complete the presentation requests, the query runs repeatedly and checks every updated character, instead of an entire tab or field. This process generates a large amount of log records, including mutliple NULL error messages and ignored exceptions.

    The issue is resolved in this release.

  • Java object deserialization vulnerability (CVE-2015-6934).
    Serialized-object interfaces allow remote attackers to execute arbitrary commands through a crafted serialized Java object, related to the Apache Commons Collections library.

    The issue is resolved in this release.

  • Vulnerability in the taglibs-standard library that is used in vRealize Automation 6.2.5 (CVE-2015-0254).
    With Apache Standard Taglibs before 1.2.3 remote attackers can run an arbitrary code or conduct external XML entity (XXE) attacks by using a crafted XSLT extension.

    The issue is resolved in this release.

  • Vulnerability in the commons-fileupload library that is used in vRealize Automation 6.2.5 (CVE-2016-3092, CVE-2014-0050, CVE-2013-2186, CVE-2013-0248).
    With Apache Commons FileUpload before version 1.3.2 remote attachers can cause a denial of service and write to arbitrary files on the system, and local users can overwrite arbitrary files through symlink attacks.

    The issue is resolved in this release.

  • Vulnerability in Xalan (CVE-2014-0107).
    With the TransformerFactory in Apache Xalan-Java before 2.7.2 remote attackers can bypass expected restrictions and load arbitrary classes or access external resources, by using crafted content-headers, entities, or properties.

    The issue is resolved in this release.

  • Denial of service vulnerability in Apache Tomcat (CVE-2016-3092).
    With the MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7, and other products, remote attackers can cause a CPU consumption denial of service by using a long boundary string.

    The issue is resolved in this release.

  • After upgrading to vRealize Orchestrator 6.0.4, you can no longer connect to a Microsoft SQL Server database over SSL.
    JDK 1.8 that is included in version 6.0.4 supports a restricted set of cipher suites compared to earlier versions of JDK.

    The issue is resolved in this release.

  • Security vulnerabilities in PostgreSQL (CVE-2016-5423 and CVE-2016-5424).
    • CVE-2016-5423: Remote attackers can use SQL statements that contain CASE or WHEN expressions to cause PostgreSQL to crash.
    • CVE-2016-5424: When database or role names contain new line characters, carriage returns, double quotes, or backslashes, users with CREATEDB or CREATEROLE roles can raise their privileges to superuser.

    The issues are resolved in this release.

  • Incorrect identification of virtual machines in an ASD workflow.
    When you use the Resource Mappings Map to VC:VM workflow, the ID that maps a virtual machine to a specific vCenter might not be unique and the workflow might run for an incorrect virtual machine.

    The issue is resolved in this release.

  • You cannot access a schema element of a workflow that contains a decision activity element.
    An attempt to access a schema element of a workflow with decision activity fails with an Error in (Workflow:Bug / Scriptable task (item3)#10198) Wrapped java.lang.ClassCastException: org.mozilla.javascript.NativeJavaObject cannot be cast to ch.dunes.scripting.jsmodel.JSWorkflowItem error message.

    The issue is resolved in this release.

  • The vRealize Orchestrator plug-in fails to initiate in the Spanish locale of the vSphere Web Client.
    When you change the language to Spanish and start the vSphere Web Client, the vRealize Orchestrator plug-in displays an error.

    The issue is resolved in this release.

  • Changing a log level from Orchestrator Configurator does not work.
    When you change a logging level from the Orchestrator configuration interface, the setting is updated in the interface but does not apply over the logging service.

    The issue is resolved in this release.

Known Issues

The known issues are grouped as follows:

Installation Issues

  • Export of Orchestrator configuration might fail when you upgrade vSphere to version 6.0.
    If you attempt to upgrade vSphere to version 6.0 after installing it in a custom location, you receive an Export of source Orchestrator configuration failed error message, and your Orchestrator configuration data is not transferred.
  • Workaround: Manually export the Orchestrator configuration. For details about exporting the Orchestrator configuration files, see Create an Archive for Upgrading Orchestrator.

  • Restarting Orchestrator server service after reinstalling plug-ins adds Java exceptions to the logs.
    On the Troubleshooting tab of the Orchestrator configuration interface, if you reinstall plug-ins by clicking Reset current version and then restart the Orchestrator server, several Java exceptions are written to the Orchestrator server logs.
  • You might be unable to configure the LDAP settings if your LDAP password contains non-ASCII characters.
    While configuring the LDAP settings in the Orchestrator configuration interface, if the LDAP password that you enter contains non-ASCII characters, the attempt might fail with an Unable to connect to LDAP Server error message. This issue occurs under the following conditions:
    • When the LDAP password contains characters such as € and ÿ in German and French locales.
    • When the LDAP password contains any native characters in Japanese, Korean, and Simplified Chinese locales.
  • Problems handling non-ASCII characters in certain contexts.
    Using non-ASCII characters in input parameters results in incorrect behavior in the following situations:
    • If you run the SCP put or SCP get workflows from the SSH folder on a file with a name that contains non-ASCII characters, the workflow runs, but name of the resulting file on the destination machine is garbled.
    • If you try to insert non-ASCII characters into attribute names, the characters do not appear. The issue occurs for workflow attributes and action attributes.

Configuration Issues

  • You cannot log in to Control Center if the user name or the password contain a non-ASCII character.
    If the root user password contains any non-ASCII character or if you create a new user account, whose user name or password contains a non-ASCII character, you cannot log in to Control Center.
  • The plug-in configuration files, such as AD.xml and VC.xml, might not be imported to Orchestrator 6.0.5 when a plug-in configuration is exported from an earlier version.
    After importing a plug-in configuration to an Orchestrator Appliance version 6.0.5 by using the Orchestrator Configuration Interface, the configuration XML files corresponding to the Active Directory plug-in and the vCenter Server plug-in might not be available, if the configuration was exported from an earlier version of Orchestrator.

    Workaround: After you import the plug-in configuration, copy the XML files manually to the /etc/vco/app-server/plugins directory of the destination appliance and restart the server service.

  • Orchestrator does not support importing a mail server certificate to Trusted certificates when the used port requires issuing the STARTTLS command.
    When you import a mail server SSL/TLS certificate by using the Import from URL option and the URL contains SMTP port 587, the import fails with an Error! IOException. Message: 'Unrecognized SSL message, plaintext connection?' error message.

    Workaround: Export the certificate to a PEM-encoded file and import it to Orchestrator manually.

    1. Use SSH to access the Orchestrator appliance and log in as root.
    2. Run the command:
    3. openssl s_client -connect -debug -starttls smtp

    4. Copy the Server certificate from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE----- and save it in a file.
    5. Import the certificate file to Trusted Certificates in Control Center, by using the Import from a PEM-encoded file option.

  • If you experience issues connecting to a SOAP or a REST host, or importing a certificate, you might have to enable certain versions of SSL or TLS explicitly.
    For information about the problem, see

    Workaround: For information about enabling SSLv3 and TLSv1 for outgoing HTTPS connections explicitly, see Enable TLSv1 for outgoing HTTPS connections in vRealize Orchestrator 6.0.4 and 7.0.x manually (KB 2144318).
  • Exported configuration with a password cannot be reimported
    If you export your Orchestrator configuration with a password, and attempt to reimport it, you receive a Could not import the configuration.: javax.crypto.BadPaddingException: Given final block not properly padded error message and the import of the configuration fails.
  • Changes might not be added when exporting configuration settings from the Orchestrator configuration interface.
    If you are exporting Orchestrator configuration data through the Orhestrator configuration interface, changes might not be added to the exported configuration package. This can lead to incorrectly configured nodes when configuring a cluster.

    Workaround: Restart the Orchestrator configuration interface before exporting the configuration data.

  • The Orchestrator configuration interface might display a validation error.
    If you have a correctly configured vRealize Orchestrator with Single Sign-On authentication, you might see a validation error on the Authentication tab in the Orchestrator configuration interface.

    Workaround: Restart the Orchestrator configuration server.

  • Updated timeout values of a REST Host take effect only after the Orchestrator server is restarted.
    When you run the Update a REST Host workflow to change the REST Host timeout configuration, you must restart the Orchestrator server for the changes to take effect.

    Workaround: Restart the Orchestrator server.

  • The Orchestrator configuration interface does not load after a restart.
    If you restart the Orchestrator configuration server, the page does not load or loads without an applied style sheet.

    Workaround: Access the Orchestrator Configuration page after a minute.

  • vCenter Server objects are not accessible in the vSphere Web Client.
    Orchestrator cannot access vCenter Server objects in the vSphere Web Client if the vCenter Server instance that you are attempting to access is registered in Orchestrator by IP address.

    Workaround: Register the vCenter Server instance by host name.

  • The Orchestrator server might become unavailable, after you modify the Single Sign-On settings by running a workflow from the Configuration plug-in.
    You must always restart the Orchestrator server right after running a workflow for configuring the Single Sign-On settings, otherwise the Orchestrator server might become unavailable. The new Single Sign-On settings are applied after the server restarts. For this reason, if you are performing an automatic configuration of Orchestrator server through workflows, make sure that the Single Sign-On configuration is the last step of the process and is performed right before you restart the Orchestrator server.

  • Orchestrator authentication configuration might become invalid, if the vCenter Single Sign-On server certificate is changed or re-generated.
    When Orchestrator is configured to use vCenter Single Sign-On, if the certificate of the vCenter Single Sign-On server is changed or re-generated, the Orchestrator authentication configuration becomes invalid and the Orchestrator server cannot start.

    Workaround: Import the new vCenter Single Sign-On certificate:

    1. Log in to the Orchestrator configuration interface as vmware.
    2. Click Network.
    3. In the right pane, click the SSL Trust Manager tab.
    4. Load the vCenter Single Sign-On SSL certificate from a URL or a file.
    5. Click Import.
    6. Click Startup Options.
    7. Click Restart the Orchestrator configuration server to restart the Orchestrator Configuration service after adding the new SSL certificate.

  • Orchestrator does not work with forest and external trusts in Active Directory.
    Multiple domains that are not in the same tree but have a two-way trust, are not supported and do not work with Orchestrator. The only configuration supported for multi-domain Active Directory is domain tree. Forest and external trusts are not supported.
  • Support for TNSNames missing when you connect to an Oracle database.
    You cannot use TNSNames to connect to an Oracle database. You can connect to an Oracle database by using an IP address or a DNS name.

    Workaround: Follow the procedure to Add support for RAC and TNS configuration for Oracle 11g Database instances to vRealize Orchestrator (KB 1022828).

  • SSL certificate is not loaded when you import configuration from previous installation.
    If you import the configuration of a previous installation into the current installation, the SSL certificate from the old installation is not loaded. In the Orchestrator configuration interface, the Server Certificate tab shows a red triangle.

    Workaround: Import the certificate manually.

  • Restricted access to vCenter Server inventory can cause errors if you select Session per user.
    If you select the Session per user option on the vCenter Server tab of the configuration interface, attempting to access the vCenter Server inventory might result in some errors for a user with restricted access to inventory objects.

Client Issues

  • The Orchestrator client does not start on Mac machines running Java 8.
    If you are using the vRealize Orchestrator Java Web start application or the installable client on a Mac machine running Java 8, you are not able to start the Orchestrator client.

    Workaround: Use the Orchestrator client Mac App from vRealize Orchestrator Appliance Home page.

  • Adding parameters to a composite type might result in a JDBC error.
    If you use the Orchestrator client to define a composite return type and add parameters with long field names, the composite type name might exceed 100 characters, which results in a JDBC error. Consequently, you cannot save the composite type.
  • The Retrieve messages (via MailClient) workflow does not display the message content.
    If you are using the Retrieve messages (via MailClient) workflow with Office 365 or Microsoft Exchange Server, the received messages are empty.

    Workaround: Call the enableImapCompatibilityMode() method on a MailClient object and after that call the connect() method.

  • Use of the Orchestrator client through Java WebStart if the Orchestrator Appliance is behind Network Address Translation (NAT) is not supported.

  • The Revert option for the parameters table does not revert to the last saved state.
    When you add a parameter to an action script, you cannot remove it by using the Revert option on the Scripting tab of the Edit Actions view.

    Workaround: Right-click the parameter and click Delete Selected.

  • Invalid input is accepted as the input value for workflow attributes of number type.
    Format validation is disabled on workflow attributes that are of the number type. Invalid input values are accepted without any warning, and workflows are saved successfully, which can lead to unpredictable results.

Miscellaneous Issues

  • Versions 6.0.x and 6.1.x of the Site Recovery Manager plug-in and the vSphere Replication plug-in for vRealize Orchestrator are not compatible with vRealize Orchestrator 6.0.5.
  • The Orchestrator plug-in for vSphere Web Client does no support vSphere Web Client 6.5.
  • The automatic redirect from your_orchestrator_server_IP_or_DNS_name to the https://your_orchestrator_server_IP_or_DNS_name:8281/vco URL is not working.
    When you deploy an Orchestrator appliance on version 6.0.5 and try to access the Orchestrator home page by entering the appliance IP address or host name in your browser, the HTTP request is not automatically rewitten to the https://your_orchestrator_server_IP_or_DNS_name:8281/vco home page address.

    Workaround: Enter https://your_orchestrator_server_IP_or_DNS_name:8281/vco in the address bar of your preferred browser.

  • Custom event schema elements do not work in an Orchestrator cluster.
    Resuming a workflow run based on a Wait for custom event schema element does not work when the Orchestrator server is configured in a cluster. The custom event schema elements work only on single Orchestrator nodes.
  • The Send notification and Send notification to mailing list workflows fail when the configured SMTP port is 587.
    When you use the Send notification or the Send notification to mailing list workflows from the Mail plug-in, the workflow run fails with an error Cannot send mail: 'Could not convert socket to TLS' Cause: 'unable to find valid certification path to requested target', even though the SSL/TLS certificate of the remote mail server is imported to Trusted Certificates.

    Workaround: After you import the mail server SSL/TLS certificate, restart the Orchestrator server and run the workflow.

  • vCenter Server plug-in might not have valid credentials after upgrading to Orchestrator 6.0.x.
    If you upgrade Orchestrator to 6.0.x, the vCenter Server plug-in does not have valid credentials.

    Workaround: After upgrading Orchestrator, update the vCenter Server instance and configure a password for the user.

  • vRealize Orchestrator displays the vCenter Server plug-in as unusable.
    After you upgrade vRealize Orchestrator to version 6.0.x, if you have not upgraded the Site Recovery Manager plug-in to version 6.0.0, the vCenter Server plug-in becomes unusable.

    Workaround: Upgrade the Site Recovery Manager plug-in to version 6.0.0 or disable the Site Recovery Manager 5.8.0 plug-in.

  • The Orchestrator configuration interface might not be accessible with Internet Explorer 11.
    If you are using Internet Explorer 11, you might be unable to log in to the Orchestrator configuration interface.

    Workaround: Install Internet Explorer version 11.0.11 or a recent version of Google Chrome or Mozilla Firefox.

  • The workflow token remains uncompleted if a workflow has a slash in its name.
    If you have a workflow with a slash in its name, when you run the workflow, the workflow token might never change to completed, although the workflow itself has completed running.

    Workaround: Remove the slash from the name of the workflow.

  • The Convert disks to thin provisioning workflow does not handle virtual machines with snapshots correctly and does not convert the thick-provisioned disks.
    On completion, the Convert disks to thin provisioning workflow reports that the thick-provisioned disks of virtual machines with snapshots are successfully converted to thin-provisioned, but they are not.

    Workaround: Do not include virtual machines with snapshots in the workflow.

  • Windows Server 2008 automatically renames VMOAPP and DAR files to ZIP causing the application installation and plug-in upload in the Orchestrator configuration interface to fail.
    If you are running Orchestrator on Windows Server 2008, the extension of the archives you download is automatically changed to ZIP. When you are installing an application or uploading a plug-in by using the Orchestrator configuration interface, you must use a VMOAPP or DAR file.

    Workaround: Change the ZIP extension back to either VMOAPP or DAR to use the downloaded archive in the Orchestrator configuration interface.

  • Adding values to vCenter Server data object properties of type Array is impossible.
    When Orchestrator runs scripts, the vCenter Server plug-in converts JavaScript arrays to Java arrays of a fixed size. As a result, you cannot add new values to vCenter Server data objects that take arrays as property values. You can create an object that takes an array as a property if you instantiate that object by passing it a prefilled array. However, after you have instantiated the object, you cannot add values to the array.

    For example, the following code does not work:

    var spec = new VcVirtualMachineConfigSpec();
    spec.deviceChange = [];
    spec.deviceChange[0] = new VcVirtualDeviceConfigSpec();

    In the above code, Orchestrator converts the empty spec.deviceChange JavaScript array into the fixed-size Java array VirtualDeviceConfigSpec[] before it calls setDeviceChange(). When calling spec.deviceChange[0] = new VcVirtualDeviceConfigSpec(), Orchestrator calls getDeviceChange() and the array remains a fixed, empty Java array. Calling spec.deviceChange.add() results in the same behavior.

    Workaround: Declare the array as a local variable, as follows:

    var spec = new VcVirtualMachineConfigSpec();
    var deviceSpec = [];
    deviceSpec[0] = new VcVirtualDeviceConfigSpec();
    spec.deviceChange = deviceSpec;

  • You cannot start a workflow with a null value if that workflow takes a SecureString as an input parameter.
    If you start a workflow with a null value when that workflow takes a SecureString as an input parameter, the server loads attributes from the cache rather than from the Orchestrator database, resulting in a null input parameter.
  • Workaround: Start the workflow from within another workflow. If you change the workflow state to passive, by implementing a long-running workflow element, the attributes are reloaded from the database, converting the null value into an empty string.