You can apply fixes to classic virtual system instances.
Before you begin
A classic virtual system instance can
require maintenance to the product code using a feature pack or emergency
fix, as well as to the operating system.You must be granted all access
to the classic virtual system instance or
have the Workload resources administration with Full permission to
complete this task. The classic virtual system instance must
be started for service to be scheduled or applied.
About this task
Important: This
task applies to classic virtual system instances that
were deployed from classic virtual system patterns.
A classic virtual system instance can
require maintenance to the product code and the operating system.
Updates to the operating system are managed by accessing the classic virtual system instance and
managing the operating system as you would in a physical environment.
Updating the level of product code (for example, IBM® WebSphere® Application Server)
with a feature pack is also done by logging in to the classic virtual system instance and
updating as you would in a physical environment, unless a virtual
image exists for this feature pack. Emergency fixes are used to update
product code to a new service level or to resolve errors. These fixes
are applied by using Cloud Pak System Software.
Emergency fixes are uploaded to the catalog and can be applied to
the classic virtual system instances managed
by the system.
Interim fixes and fix packs are applied to classic virtual system instances as
emergency fixes. When you add an emergency fix, you define the virtual
images for which the fix is applicable. The list of fixes available
when you schedule a service request is created by using all the fixes
applicable to the virtual image used to create your classic virtual system instance.
If a fix is already applied to your virtual system, you can see it
in the History listing and it is not included
in the list of available fixes.
Procedure
- Click .
- Select the virtual system instance for which you want to
apply service.
- Click the Service icon to select
and schedule service for this classic virtual system instance. If no service updates are available, a message is displayed.
- Schedule
a service request.
- Select Service now to schedule
your service request to start immediately.
- Click Schedule service to specify
when the service must be applied. The default date and
time for scheduled service is immediately. Modify these fields to
the date and time when the service request should be started.
- Click Select service level or fixes to
select what service must be applied with this request. The
available service is displayed in two groups. Any available fix packs
that can be used to update this classic virtual system instance are
listed under Move to service level. Any available
emergency fixes that can be used with this classic virtual system instance are
listed under Apply emergency fixes. Complete
one of the following steps:
- Select Move to service level and
select an available fix pack.
- Select Apply emergency fixes and
select the emergency fixes you want to apply. You
can select more than one emergency fix to be applied by using the
same service request.
If an emergency fix has
additional environment variables that need to be configured, the name
of the emergency fix is displayed as a link. Click the link to display
a dialog and provide values as needed to configure the additional
environment variables. These additional variables are included in
the list of environment variables displayed in the Environment section
of the Emergency Fixes pane.
- Click Product administrator user name and password and
specify an authorized user name and password in the fields provided.
Note: These credentials are not used to run
the script that is packaged with the emergency fix. The script runs
by using the root user context. These credentials
are passed to the running script as environment variables with the
key names ADMINUSERNAME and ADMINPASSWORD so
that they can be used by the script if needed for tasks such as product
administration. These environment variables are only valid in the
execution environment of the script package. If no credentials are
needed for the tasks that are carried out by the script, it completes
successfully even when these credentials are left blank.
- Click OK to complete the service
request. A snapshot
image of the classic virtual system instance is
automatically taken before a service request is performed.