You always need an update profile to update an Oracle Solaris Boot environment. You can use the update profile in an update deployment plan or the Update Job Wizard.
You can update an alternate boot environment as part of a Software Deployment / Update deployment plan by selecting the alternate boot environment as the target. See the Oracle Enterprise Manager Ops Center Updating Your Oracle Solaris 10 Operating System for an example of how to use this plan.
You can create a customized update job, including the option to use an alternate boot environment (ABE) to perform a live upgrade of your Oracle Solaris 10 operating system. With Live Upgrade, you create an inactive ABE, update and patch the ABE, synchronize the ABE and BE, and then switch boot environments. When you switch boot environments, the patched and tested ABE becomes the active boot environment.
Note:
Do not use Live Upgrade on your Enterprise Controller or Proxy Controllers. Live Upgrade does not synchronize all of the files that are required for these components.
You must run a separate update job for systems that use an ABE from those that do not use an ABE. When creating a job, you must define the following job parameters:
Name and description of the update job.
Alternate Boot Environment: Whether to use an alternate boot environment.
Profile: Defines what updates are to be installed, uninstalled, or updated on an operating system. Select a profile from the list of predefined and customized profiles.
Policy: Defines how a job is performed and sets the automation level of the job. Select a policy from the list of available policies. You can also create your own policies.
Target Settings: Defines whether the target is different or similar for each task in the job.
Actual Run: Defines whether this job is in simulation mode. You can choose to deploy the job, or to run a job simulation. A job simulation determines the actions and results of a job, and estimates how much time is required to complete the job. A job simulation also indicates whether your policy and profile responses will enable the job to succeed.
Task Execution Order: Specifies whether the tasks is run in parallel or sequentially.
Task Failure Policy: Specifies the action to take if a task fails.
Targets: Select one or more target hosts for this job.
To create an ABE as part of this job, you must write at least one script that uses the lucreate
command and then upload the script to the Local Content.
Note:
The ABE name defined in the script must match the ABE name that you use when you run the update job to create the ABE.