Changing the configuration parameters for the WebSphere Service Registry and Repository nodes

To change the configuration parameters for the WebSphere® Service Registry and Repository nodes, edit the .conf.yaml configuration file for the integration node, or integration server.

About this task

Any properties that you set for an integration node in the node.conf.yaml file, are inherited by the integration servers that it owns. However, you can change any of the properties of an integration server that is owned by an integration node by modifying them in the appropriate server.conf.yaml file. You can change any of the properties of an independent integration server by modifying them in the appropriate server.conf.yaml file. For more information about configuring integration servers, see Configuring an integration server by modifying the server.conf.yaml file.

To set the WSRR parameters, you must edit the WSRRConnectorProvider entries in the ConnectorProviders section of the node.conf.yaml or server.conf.yaml configuration file. When you migrate your integration servers and integration nodes to IBM® App Connect Enterprise 13.0 by using the ibmint extract node or ibmint extract server command, the values of the DefaultWSRR configurable service properties are placed in the ConnectorProviders section of the .conf.yaml file. When you create a new integration node or a new independent integration server, the .conf.yaml configuration file contains the following subset of the WSRR parameters. All the other WSRR parameters have default settings, which generally do not need to be changed. If you need to change any of the other WSRR parameters, you must add them to the .conf.yaml configuration file.


ConnectorProviders:
    #WSRRConnectorProvider:    # Requires the optional WSRR component install
    #endpointAddress: 'https://host:9443/WSRR8_0/services/WSRRCoreSDOPort'   # WSRR server endpoint url
    #needCache: true                                                         # enable WSRR cache
    #predefinedCacheQueries: ''                                              # semicolon-separated XPath querys to initialize WSRR cache at start-up
    #enableCacheNotification: false                                          # enable WSRR cache notification
    #locationJNDIBinding:  'iiop://host:2809'                                # WSRR cache WAS JMS provider JNDI bindings url

For more information about configuration parameters that affect WSRR use, see Configuration parameters for the WebSphere Service Registry and Repository nodes.

Complete the following steps to update the configuration parameters for WSRR:

Procedure

Ensure that the integration node or independent integration server is running.
For more information, see Starting and stopping an integration node and Starting an integration server.
Edit the connectionFactoryName parameter in the .conf.yaml file to show the name of the WSRR WebSphere Application Server WebSphere® Application Server JMS provider JMS connection factory for Cache Notifications. The default value is 'jms/SRConnectionFactory.connectionFactoryName'
```
connectionFactoryName: 'jms/SRConnectionFactory' # The name of the WSRR Application Server JMS provider JMS connection factory for Cache Notifications. The default value is 'jms/SRConnectionFactory'.
```
Edit the connectionTimeout parameter in the .conf.yaml file to show the WSRR connection timeout period in seconds. The default value is 180 seconds (3 minutes).
```
connectionTimeout: 180 # The WSRR connection timeout period in seconds. The default value is 180 seconds (3 minutes).
```
Set the enableCacheNotification parameter in the .conf.yaml file to true to enable IBM App Connect Enterprise WSRR Cache Notification. The default value is false.
```
enableCacheNotification: true # The default value is false. Select true to enable IBM® App Connect Enterprise WSRR Cache Notification.
```
Edit the endpointAddress parameter in the .conf.yaml file to show the location or endpoint of the WSRR server.
```
endpointAddress: 'http://fill.in.your.host.here:9080/WSRRCoreSDO/services/WSRRCoreSDOPort'   #The location or endpoint of the WSRR server. The default value for all versions of WSRR is 'http://fill.in.your.host.here:9080/WSRRCoreSDO/services/WSRRCoreSDOPort'
```
The default value for all versions of WSRR is 'http://fill.in.your.host.here:9080/WSRRCoreSDO/services/WSRRCoreSDOPort'
For example, to connect to a server that uses WSRR v7.5 compatibility use the following values:
```
'http://fill.in.your.host.here:9080/WSRR7_5/services/WSRRCoreSDOPort'
```
For more information about WSRR endpoint addresses, see WSRR web service interface URLs.

For more information about the specific levels of WSRR that are supported by IBM App Connect Enterprise, see IBM App Connect Enterprise system requirements web page.

Edit the initialContextFactory parameter in the .conf.yaml file to show the name of the WSRR WebSphere Application Server WebSphere® Application Server JMS provider JMS connection factory for Cache Notifications. The default value is 'com.ibm.websphere.naming.WsnIitialContextFactoryCopy'

initialContextFactory: 'com.ibm.websphere.naming.WsnIitialContextFactoryCopy' # The name of the WSRR WebSphere Application Server JMS provider JMS context factory for Cache Notifications.
                                                                                          The default value is 'com.ibm.websphere.naming.WsnIitialContextFactoryCopy'

Edit the locationJNDIBinding parameter in the .conf.yaml file to show the URL to the WebSphere Application Server JMS provider JNDI bindings. The default value is 'iiop://host_name:2809/'
```
locationJNDIBinding: 'iiop://host_name:2809/' # The URL to the WebSphere Application Server JMS provider JNDI bindings. The default value is 'iiop://host_name:2809/'
```
Edit the secureJNDIPropertiesFiles parameter in the .conf.yaml file to show the directory where your.props files are stored. For example, 'C:\SSLPropsFiles'
```
secureJNDIPropertiesFiles: 'C:\SSLPropsFiles' # The directory where your .props files are stored. For example 'C:\SSLPropsFiles'    
```
Set the needCache parameter in the .conf.yaml file to true to indicate that the IBM App Connect Enterprise cache is enabled. The default value is true
```
needCache: true # The default value is true, indicating that the IBM App Connect Enterprise WSRR cache is enabled.
```

Edit the predefinedCacheQueries parameter in the .conf.yaml file to show a list of semicolon-separated WSRR XPath query expressions with which to initialize the IBM App Connect Enterprise cache at start-up.

predefinedCacheQueries: "//*[@name='Wss100.wsdl'];/WSRR/WSDLService/ports[binding/portType[@name='DemoCustomer' and @namespace='http://demo.sr.eis.ibm.com'] and @PortProperty1='ValueOfPortProperty1' and exactlyClassifiedByAllOf(., 'http://www.ibm.com/xmlns/prod/serviceregistry/6/0/governance/DefaultLifecycle#InitialState1','http://www.ibm.com/xmlns/prod/serviceregistry/6/0/governance/DefaultLifecycle#Approve')]" #  A list of semicolon-separated WSRR XPath query expressions with which to initialize the IBM App Connect Enterprise WSRR cache at start-up.

These WSRR XPath query expressions are defined by the WSRR SOAP interface query expression language, and might include an optional depth specifier extension. For more information about XPath, see https://www.ibm.com/support/knowledgecenter/en/SSWLGF_8.5.6/com.ibm.sr.doc/twsr_xpath_query.html.

Set the refreshQueriesAfterNotification parameter in the .conf.yaml file to true or false according to your requirements.

The default value is true. When a notification is received from WSRR, and refreshQueriesAfterNotification is set to true, the Cache is updated with the new version of the object immediately. If it is set to false, the Cache is updated on the next request.

refreshQueriesAfter Notification: true # When a notification is received from WSRR, if refreshQueriesAfterNotification is set to true, the Cache is updated with the new version of the object immediately; if it is set to
                                                     false, the Cache is updated on the next request. The default value is true.

Edit the subscriptionTopic parameter in the .conf.yaml file to show topic name that is used to receive the WebSphere Application Server JMS provider Cache Notifications. The default value is 'jms/SuccessTopic'.
```
subscriptionTopic: 'jms/SuccessTopic' # The topic name that is used to receive WebSphere Application Server JMS provider Cache Notifications. The default value is 'jms/SuccessTopic'
```
Edit the timeout parameter in the .conf.yaml file to show the cache expiry time in milliseconds. The default value is 100000000, which is approximately 27.8 hours.
```
timeout: 100000000 # The cache expiry time in milliseconds. The default value is 100000000, which is approximately 27.8 hours.
```
Restart the integration node or independent integration server. For more information, see Starting and stopping an integration node, Starting an integration server, and Stopping an integration server.