depends or conflicts in any of your packages.
a. Click
New External Package
and replace the text with the name you will use as an external
software package name.
b. Type a version number in the
Version
text box.
c. Select the
Architecture
in the drop-down list.
d. Click
Select Attribute Name
and select a registry property or WMI attribute in the drop-down list.
e. Add attributes. See
"Define External Software Attributes" on page 46
for more information.
f. To save a copy locally, click
Save
.
g. Click
Publish External SW
to publish to the repository.
Create Packages with Dependencies
Package dependencies are a way to specify prerequisites for the installation of the current package or to
install several packages with one action.
Dependencies can be used to identify and install prerequisite packages that must be installed before the
software package you are configuring can be installed. The packages on which a package is dependent on
are specified on the Depends tab, located on the Properties tab, when you create the package.
For example, you need to install SQL Server 2005 SP3 on your servers with SQL Server 2005 in order to
meet system requirements. You create a package for the service pack (sqlserversp) and include sqlserver
>= 9.00.1399.068 as a dependency for the sqlserversp installation. When the sqlserversp package is
installed, Package Manager checks for dependencies. In this example,sqlserver >= 9.00.1399.06 is a
dependency. It then checks the installed packages on the target machine for sqlserver >= 9.00.1399.06 as an
installed package. If Package Manager determines that the prerequisite package, sqlserver, is not installed,
it downloads this package from the software repository and installs it. After the dependency is installed,
package manager installs the files contained in the sqlserversp package.
You can also specify dependencies on applications that are not managed as packages and not installed
using Package Manager by using External Software. If you added sqlserver, version 9.00.1399.06, to your
external software application list, then the check for a dependency will begin with installed packages. If
sqlserver is not found as an installed package, Package Manager then checks the external software list for
an entry for sqlserver >= 9.00.1399.06. If it finds one, checks the attributes, verifies the application is
installed, it considers the dependency met and continues with the installation of sqlserversp.
A best practice is to add any package you use as a dependency to the External Software list. This ensures
that even externally installed software is processed by Package Manager at installation time. See
"About
External Software" on page 43
for more information.
Prerequisite
To use the dependency packages at installation time, they must exist in the repositories. If the specified
dependency packages do not exist in the repositories, the current package is not installed on the target
machines.
Procedure
1. Start the VMware vCenter Configuration Manager Package Studio.
2. Click
Manage Packages
.
The package configuration tabs appear.
3. On the
Properties
tab, click the
Depends
sub-tab.
Using Package Studio to Create Software Packages and Publish to Repositories
VMware, Inc.
25
Содержание PACKAGE MANAGER 1.1
Страница 38: ...vCenter Configuration Manager Software Provisioning Components Installation and User s Guide 38 VMware Inc...
Страница 48: ...vCenter Configuration Manager Software Provisioning Components Installation and User s Guide 48 VMware Inc...
Страница 64: ...vCenter Configuration Manager Software Provisioning Components Installation and User s Guide 64 VMware Inc...
