4.0

Table Of Contents
Appendix: Workflow Name Changes
Many workflow names have changed in this release. Workflow name changes can affect Web service
applications, if a Web service client uses the getWorkflowsWithName operation.
You must update Web services applications that use getWorkflowsWithName to reflect the new workflow names.
The following sections list all the workflows for which the names changed between Orchestrator 4.0 and
Orchestrator 4.0.1.
This appendix includes the following topics:
n
“JDBC Workflow Name Changes,” on page 337
n
“Locking Workflow Names Unchanged,” on page 338
n
“Mail Workflow Name Changes,” on page 338
n
“Orchestrator Workflows,” on page 338
n
“Refactoring Workflow Name Changes,” on page 338
n
“SSH Workflow Name Changes,” on page 339
n
“vCenter Server Workflow Name Changes,” on page 339
n
“XML Workflow Name Changes,” on page 342
JDBC Workflow Name Changes
The workflow library includes a set of workflows to demonstrate JDBC tasks.
Table A-1 lists the JDBC workflow names that changed.
Table A-1. JDBC Workflow Name Changes
Old Workflow Name New Workflow Name
Tests JDBC > JDBC url generator JDBC URL generator
Tests JDBC > Test All database JDBC Examples > Full JDBC cycle example
Tests JDBC > Test connection JDBC Examples > JDBC connection example
Tests JDBC > Test create table JDBC Examples > JDBC create table example
Tests JDBC > Test delete all from table JDBC Examples > JDBC delete all from table example
Tests JDBC > Test delete entry from table JDBC Examples > JDBC delete entry from table example
Tests JDBC > Test drop table JDBC Examples > JDBC drop table example
Tests JDBC > Test insert into table JDBC Examples > JDBC insert into table example
Tests JDBC > Test select from table JDBC Examples > JDBC select from table example
VMware, Inc. 337