VMware

VMware vCenter Orchestrator Plug-In for vCenter Server 5.0.2 Release Notes

VMware vCenter Orchestrator Plug-In for vCenter Server 5.0.2 | 4 Oct 2012 | Build 256

VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581

VMware vCenter Orchestrator 4.2 | 24 Aug 2011 | Build 5277

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 Server

The vCenter Orchestrator Plug-In for vCenter Server 5.0.2 runs on VMware vCenter Orchestrator 4.1.x and VMware vCenter Orchestrator 4.2.x. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCenter Server 5.0.x.

For information about vCenter Orchestrator and vCenter Orchestrator plug-ins, see:

What's New in This Release

Version 5.0.2 of the plug-in improves the performance with the Inventory Service and resolves problems with the property collector.

To upgrade the plug-in, you must install version 5.0.2 on your existing installation. You can download version 5.0.2 from the VMware vCenter Orchestrator Plug-In for vCenter Server download page.

Resolved Issues

The following issue is resolved in this release:

  • Property collector issues and Inventory Service slow performance

    When you install the vCenter Orchestrator plug-in for vCenter Server you may experience some problems with the property collector, and slow performance with the Inventory Service.

    For more information, see KB 2032840

    This issue is resolved in this release.

Top of Page

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator Plug-In for vCenter Server 5.0.2 release:

  • When you install the vCenter Server 5.0.2 plug-in, the vCenter Server 4.1 plug-in is not removed from your system
    When you install the vCenter Server 5.0.2 plug-in, the vCenter Server 4.1 plug-in installation is not removed. Having both versions of the plug-in might cause some issues.
    Workaround: Remove the vCenter Server 4.1 plug-in before installing the vCenter Server 5.0.2 plug-in. To uninstall the plug-in:
    1. Log in as an administrator to the machine on which the Orchestrator server is installed.
    2. Navigate to the vCenter Server 4.1 plug-in .dar file.
      • If you installed Orchestrator with the vCenter Server installer, the default path is:
        install_directory\VMware\Insfrastructure\Orchestrator\app-server\server\vmo\plugins\o11nplugin-vsphere41.dar.
      • If you installed the standalone version of Orchestrator, the default path is:
        install_directory\VMware\Orchestrator\app-server\server\vmo\plugins.
    3. Restart the vCenter Orchestrator configuration service and the vCenter Orchestrator server.
  • Stopping the vCenter Inventory Service causes an error in the plug-in
    If you stop the vCenter Inventory Service on a vCenter Server instance that is registered with the plug-in, the Inventory view of the plug-in in the Orchestrator client displays an error message.
    Note: If you start the vCenter Inventory Service again, you can refresh the Inventory view of the plug-in in the Orchestrator client to use the plug-in with enabled vCenter Inventory Service.

    Workaround: Restart the Orchestrator service to use the plug-in with disabled vCenter Inventory Service.

  • Certificates required for vCenter Server instances in a linked mode group
    If you register a vCenter Server instance that is in a linked mode group, you must import the certificates of all vCenter Sever instances that you added to the configuration in this operation, so that Orchestrator can recognize all vCenter Server instances in the linked mode group.
  • The vCenter Server 5.0.2 plug-in might run out of memory
    The vCenter Server 5.0.2 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 vCenter Server 5.0.2 plug-in are installed.

    1. Log in as an administrator to the machine on which the Orchestrator server and the vCenter Server 5.0.2 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=256.
    6. Save and close the file.

    Top of Page