Solaris Package Container Components

Containers are components that reference other components. Use the Package containers to create components that include a Package component and its corresponding Response File component. For more information about containers, see Chapter 1, Plan and Component Development Concepts, in N1 Grid Service Provisioning System 5.0 Plan and Component Developer’s Guide.

Package Container Component and Datastream Package Container Component

If you want to deploy a Solaris package with a response file, from the Solaris Common Tasks page, click the Package with Response File: Create Package with Response File Container link. This link enables you to create a container component of the type com.sun.solaris#PackageWithResp. When you create this container component, include the Package component and its corresponding Response File component in the container component.

If you want to deploy a Solaris datastream package with a response file, from the Solaris Common Tasks page, click the Datastream Package with Response File: Create Datastream Package with Response File Container link. This link allows you to create a container component of the type com.sun.solaris#StreamPackageWithResp. When you create the container component, include the Datastream Package component and its corresponding Response File component in the container component.

Package Container Components and Datastream Package Container components contain the same component variables and component procedures. The variables and procedures are described below.

Component Variables

installPath

The path on the target host where the package file and the response file will be downloaded.

Component Procedures

default: install

Use this procedure to install a package with its response file on a target system or systems.

mark Only: install

If you manually installed a package with its response file on a target system or systems but want the provisioning system database to be aware that the package is installed on those systems, use this procedure.

default: uninstall

Use this procedure to uninstall a package and its response file from a target system or systems.

markOnly: uninstall

If you manually uninstalled a package and its response file from a target system or systems but want the provisioning system database to be aware that the package has been uninstalled from those systems, use this procedure.