Use the mqsichangeproperties command
to enable cache notification, so that the cache is notified of events
occurring in WebSphere® Service Registry
and Repository (WSRR).
WSRR publishes notification events by using WebSphere Application
Server. Cache notification allows
the cache to subscribe to these events.
To enable cache notification
complete the following steps to change the relevant properties on
the configurable service DefaultWSRR, and to add
a user ID and password if you are connecting to a secure WebSphere Application
Server:
- Ensure that the broker is running. If it is not, use the mqsistart command to start
it.
- Issue the mqsichangeproperties command
to change the enableCacheNotification property
to true. For
example:
mqsichangeproperties MB8BROKER -c ServiceRegistries -o DefaultWSRR
-n enableCacheNotification -v true
where:-c specifies the configurable service (in this case, ServiceRegistries)
-o specifies the name of the object (in this case, DefaultWSRR)
-n specifies the names of the properties to be changed
(in this case, enableCacheNotification)
-v specifies the values of properties defined by the -n parameter
(in this case, true)
- Issue the mqsichangeproperties command to change the locationJNDIBinding property to the value that you require for your WSRR server. For example:
mqsichangeproperties MB8BROKER -c ServiceRegistries -o DefaultWSRR
-n locationJNDIBinding -v iiop://localhost:2809/
where:-c specifies the configurable service (in this case, ServiceRegistries)
-o specifies the name of the object (in this case, DefaultWSRR)
-n specifies the names of the properties to be changed
(in this case, locationJNDIBinding)
-v specifies the values of properties defined by the -n parameter, such as: \"corbaloc::localhost:9810,localhost:9811\" or iiop://localhost:2809/ in this example.
- When you use WebSphere Application
Server Version 8.0 or later, the default IIOP secure setting is SSL-Required. Therefore if you connect to your server without changing this option to SSL-Optional, you must configure the sas.client.props and the ssl.client.props files in the following way:
sas.client.props- Set com.ibm.ssl.alias=AnotherSSLSettings
- Set com.ibm.CORBA.loginSource=properties
ssl.client.proprs-- Use the AnotherSSLAlias template that is already in the file, but comment ou the DefaultAlias Keystore and Truststore information to prevent it affecting the current configuration
-- Comment out the KeyStore part of the 'another SSL Alias' because the TrustStore is the only one that is required:
- Set com.ibm.ssl.enableSignerExchangePrompt=false in all scenarios
- Issue the mqsichangeproperties command to change the secureJNDIPropertiesFiles property to point to the directory where your .props files are stored. For example: For example:
mqsichangeproperties MB8BROKER -c ServiceRegistries -o DefaultWSRR
-n secureJNDIPropertiesFiles -v C:\SSLPropsFiles
where:-c specifies the configurable service (in this case, ServiceRegistries)
-o specifies the name of the object (in this case, DefaultWSRR)
-n specifies the names of the properties to be changed
(in this case, secureJNDIPropertiesFiles)
-v specifies the values of properties defined by the -n parameter (in this case, C:\SSLPropsFiles)
- If you are connecting to a secure WebSphere Application
Server you must use a user ID and
password. To set the user ID and password follow these steps:
- Stop the broker by using the mqsistop command.
- Issue the mqsisetdbparms command to set
up your user ID and password. For example:
mqsisetdbparms MB8BROKER -n jms::DefaultWSRR@jms/SRConnectionFactory
-u userid -p password
where:-n specifies the name of the data source
(in this case, jms::DefaultWSRR@jms/SRConnectionFactory)
-u specifies the user ID to be associated with this data source
(in this case, userid)
-p specifies the password to be associated with this data source
(in this case, password)
- Restart the broker by using the mqsistart command.