VMware

VMware vCenter Orchestrator Plug-In for vCenter Update Manager Release Notes

VMware vCenter Orchestrator Plug-In for vCenter Update Manager 1.0 | 16 Jun 2011 | Build 229

VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581

VMware vCenter Update Manager 4.1 | 13 Jul 2010 | Build 256596

Last Document Update: 16 Jun 2011

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to the VMware vCenter Orchestrator Plug-In for vCenter Update Manager

The VMware vCenter Orchestrator plug-in for vCenter Update Manager simplifies the management of the vSphere-based cloud infrastructure by integrating the robust workflow automation of VMware vCenter Orchestrator with the patch management framework provided by VMware vCenter Update Manager. The Update Manager plug-in enables IT administrators to automate tasks such as scanning and remediation of ESX/ESXi hosts, virtual machines and appliances against established baselines. The plug-in also allows patching and upgrading ESX/ESXi hosts, as well as installation of third-party modules, to ensure compliance against the baselines. In addition to ESX/ESXi patch management, the plug-in also supports virtual machine operations such as the upgrade of VMware Tools and virtual hardware.

The VMware vCenter Orchestrator Plug-In for vCenter Update Manager 1.0 release runs on VMware vCenter Orchestrator 4.1 and the subsequent update releases. The plug-in is compatible with VMware vCenter Update Manager 4.1. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCenter Update Manager 1.0.

Top of Page

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator Plug-In for vCenter Update Manager 1.0 release:

  • The Update Manager plug-in might run out of memory

    The Update Manager plug-in might run out of memory with an OutOfMemory error message when you configure it to work with vCenter Orchestrator 4.1.

    Workaround: Modify the jetty-service.conf file on the machine on which the Orchestrator server and the Update Manager plug-in are installed.

    1. Log in as an administrator to the machine on which the Orchestrator server and the Update Manager plug-in are installed.
    2. Locate the jetty-service.conf file.
      The default location is: C:\Program Files\VMware\Infrastructure\Orchestrator\configuration\jetty\jetty-service.conf.
    3. Open the file in a text editor.
    4. Add the following line:
      wrapper.java.additional.7=-XX:MaxPermSize=128m.
    5. Change wrapper.java.maxmemory=64 to wrapper.java.maxmemory=128.
  • The Orchestrator method Server.findAllForType might not work as expected
    The Server.findAllForType method of the Orchestrator scripting object Server, and the SOAP service operation find(java.lang.String type, java.lang.String query, java.lang.String username, java.lang.String password) do not work as expected.

Top of Page