Upgrading Oracle Solaris Cluster HA for WebSphere Message Broker

Upgrade the Oracle Solaris Cluster HA for WebSphere Message Broker data service if the following conditions apply:

You are upgrading from an earlier version of the Oracle Solaris Cluster HA for WebSphere Message Broker data service, that was previously known as Oracle Solaris Cluster HA for WebSphere MQ Integrator.
You need to use the new features of this data service.

How to Upgrade to the New Version of Oracle Solaris Cluster HA for WebSphere Message Broker

Perform steps 1, 2, 3 and 6 if you have an existing Oracle Solaris Cluster HA for WebSphere Message Broker deployment and wish to upgrade to the new version. Complete all steps if you need to use the new features of this data service.

Note - If you intend to run all steps, you should consider if your current WebSphere Message Broker resources have been modified to have specific timeout values that suit your deployment. If timeout values were previously adjusted you should reapply those timeout values to your new WebSphere Message Broker resources.

On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

Disable the WebSphere Message Broker resources.

# clresource disable websphere-messabge-broker-resource

Install the new version of Oracle Solaris Cluster HA for WebSphere Message Broker to each cluster
Refer to How to Install the Oracle Solaris Cluster HA for WebSphere Message Broker Packages for more information.
Delete the WebSphere Message Broker resources, if you want to use new features that have been introduced in the new version of Oracle Solaris Cluster HA for WebSphere Message Broker.
```
# clresource delete websphere-message-broker-resource
```
Reregister the WebSphere Message Broker resources, if you want to use new features that have been introduced in the new version of Oracle Solaris Cluster HA for WebSphere Message Broker.
Refer to How to Register and Configure Oracle Solaris Cluster HA for WebSphere Message Broker for more information.
Enable the WebSphere Message Broker resources
If you have only performed steps 1, 2 and 3 you will need to re-enable the WebSphere Message Broker resources.
```
# clresource enable websphere-message-broker-resource
```

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Service for WebSphere Message Broker Guide