4.0

Table Of Contents
Refactoring Orchestrator Applications
After Upgrading vCenter Server 10
If you upgrade the virtual infrastructure from VMware Infrastructure 3.5 to vCenter Server 4.0, you must
refactor any Orchestrator applications that you wrote for use with the older version. Orchestrator 4.0 provides
workflows to help you refactor the applications to the new version. Alternatively, you can run VMware
Infrastructure 3.5 on Orchestrator 4.0 by installing the VMware Infrastructure 3.5 plug-in.
This chapter includes the following topics:
n
“When to Refactor Applications,” on page 329
n
“Install the VMware Infrastructure 3.5 Plug-In,” on page 330
n
“Refactoring Packages with the Basic Refactoring Workflow,” on page 330
n
“Refactoring Packages with the Advanced Refactoring Workflows,” on page 333
When to Refactor Applications
If you upgrade the virtual infrastructure from VMware Infrastructure 3.5 to vCenter Server 4.0, you must take
action to continue to run your existing applications.
You develop Orchestrator applications as plug-ins. Plug-ins consist of one or more packages that can contain
workflows, actions, Java classes, XML files, Web views, configuration elements, or policy templates. The
package names and certain object types used by the vCenter Server 4.0 API are different from those used by
previous versions of VMware Infrastructure. The name and type changes are listed in Table 10-1.
If you upgrade the virtual infrastructure from VMware Infrastructure 3.5 to vCenter Server 4.0, one course of
action is to install the VMware Infrastructure 3.5 plug-in on an Orchestrator server 4.0 platform and then import
your applications. The VMware Infrastructure 3.5 plug-in communicates with the vCenter Server 4.0 plug-in
and allows you to run your applications without change.
Alternatively, to benefit from all the features of vCenter Server 4.0, you can refactor Orchestrator applications
that you wrote with the old version. Orchestrator 4.0 provides workflows to help you refactor the applications
to the new version.
Table 10-1. Object Name Changes from Previous Versions of VMware Infrastructure to vCenter Server 4.0
Object
Value in Previous Versions of
VMware Infrastructure Value in vCenter Server 4.0
Package name
vim3 vcenter
FinderResult type
VIM3 VC
Scripting type
Vim
Vc <ScriptName>
Host
VMware3:VimHost VC:SdkConnection
VMware, Inc. 329