Use the console to
update shared service instances to the next version.
Before you begin
Upload any new pattern types and images that are available
with the new fix pack release to the system. Then, any shared service
instances that are updated or deployed use the new pattern types and
images. Also, before you update shared service instances, be sure
to stop all activity in the console, including
deployments, deletes, and stops.Important: Do not use the steps in this task to update the System Monitoring for WebSphere®
Application Server, System Monitoring for HTTP Servers, System Monitoring for WebSphere MQ,
or System Monitoring for WebSphere Message Broker services. To
upgrade to a new version of these services, you must delete the existing
service and then deploy the new version. For more information, see
the Related reference section.
About this task
If a shared service instance is deployed in multiple clouds,
you must update each shared service instance in each cloud individually.Procedure
- Click .
- On the left side of the window, click the service instance
that you want to update, and then click Check for Updates in
the Pattern type section. A message is displayed
that prompts you to confirm the operation.
- Click Upgrade. The update starts,
and the status of the instance changes to launching and maintaining.
Note: Only a version release minor fixpack (VRMF) upgrade is
supported. A version release upgrade is not supported.
- Wait until the status of the instance changes to running, configuring, and upgrading. At this
point, the update process is complete. Commit and
Revert are available in the upper right side of the window.
- Click Commit. Now
the update process is committed, and the instance of the shared service
cannot roll back to the previous version, for example the previous
fix pack level. The status of the service instance changes to running.
- Optional: If you must roll the shared service
instance back to the previous version, click Revert.
Results
Your shared services instances are updated.
You might notice the previous version of the instance is shown on
the Shared Service Instances page.
This is because the appmodel.json file is not
modified during the update process. Instead, your existing application
model is updated to use the newer plug-ins that are provided by the
pattern type. As a result, the version remains the same after the
update is complete.