Post installation tasks

This topic describes tasks to be completed after you have installed and deployed WSRR.

Configure user security

You can configure both coarse and fine-grained user access after you have installed WSRR and created a profile. You must modify the access control settings because the default values that are used during installation allow all users administrator access to WSRR.

To configure security, review the following information and update the configuration as required:

Check the J2EE role mappings to change which users are administrators. The default values used during profile creation (whether accessed through the profile management tool, or by using the command line) are used to set all users as administrators. For more information, see J2EE role mappings.
Refine the WSRR access control configuration to map users and groups to WSRR roles. The initial configuration includes all authenticated users in each of the roles, therefore you must configure these roles to be appropriate for your environment. See Defining WSRR access control roles.
Review the dashboard security configuration. The initial configuration gives users in the WSRRAdmin role editor access to all of the views that are created, and all other users can see all of the views. Any views that were created for you during installation have these access settings. The following information explains how to change these settings:
1. To refine the permissions used for the existing views, see Managing view access permissions.
2. To refine the default view permissions for the dashboard, see Setting user access to dashboard views.

(Optional) Turn off the WSRR JMS function

Various WSRR features use JMS. If you are not using any of these features, you can turn off the WSRR JMS function.

The following WSRR features use JMS:

Integration with Rational® Asset Manager (provided by WSRR Advance Lifecycle Edition).
Integration with WebSphere DataPower
UDDI synchronization
Email notification.
JMS notification.
Policy notification.
Asynchronous promotion.
Text search.

To turn off the WSRR JMS function, complete the following steps:

Turn off JMS notification and email notification in WSRR, by completing the following tasks:
1. Open the WSRR web user interface.
2. Switch to the Configuration perspective if necessary, by selecting Configuration in the Perspective list.
3. Click Active Profile > Notifiers.
4. Click Notification properties plug-in.
5. Set the value of the jmsNotification property setting to false. For example:
```
jmsNotification=false,7
```
6. Set the value of the emailNotification property setting to false. For example:
```
emailNotification=false,30
```
7. Click OK to save your changes.

Disable the JMS and ALE notifiers, by deleting or commenting out the following lines in the notification properties plug-in:

com.ibm.sr.api.ServiceRegistryNotifierJMS
com.ibm.sr.ale.wsrr.ALENotifier

For example:

#notifiers=com.ibm.sr.ale.wsrr.ALENotifier,com.ibm.sr.api.ServiceRegistryNotifierJMS

Stop the WSRR messaging engine, by completing the following steps:
1. Open the WebSphere® Application Server administrative console.
2. Click Service integration > Buses > ServiceRegistryBus > Messaging engines.
3. Select the check box alongside the ServiceRegistryBus messaging engine, and click Stop > Immediate.
4. Click the ServiceRegistryBus messaging engine entry to display its details.
5. Change the value of the Initial state field to Stopped.
6. Click OK, then click Save to save your changes to the master configuration.

Note: After turning off the WSRR JMS function, you might see the following error, which you can ignore:

[09/11/10 11:12:11:285 GMT] 0000000c email E com.ibm.sr.email.notify.config.EMailConfigUtil
disableEMailNotification GSR5000I: Captured exception [402]: javax.jms.JMSException:
...
CWSIT0088E: There are currently no messaging engines in bus ServiceRegistryBus running.
...
CWSIT0103E: No messaging engine was found that matched the following parameters:
...

(Optional) Turn off activity logging

If you do not plan to use the activity logging feature, you can improve WSRR performance by turning off this feature; for details, see Activity logging configuration.

(Optional) Switch to an EAR file without SSL enabled

You can configure WSRR so that application security is enabled but SSL is disabled. You do this by switching from the product EAR file ServiceRegistry.ear to the EAR file ServiceRegistryNoSSL.ear. For details, see Configuring a secure WSRR without requiring SSL.

Configure WSRR mail session

If you want to use the Email Owner or Email Consumer features in the dashboard, then you must configure the WSRR mail session. For details, see Configure the connection details and timeout for the SMTP server and Configure the IMAP settings

Enable storing of email

You can enable the feature to store copies of email notifications by editing the EMailSettings file. You also edit this file to specify the URL of the dashboard that is substituted for the URL token in an email template.

For details, see Storing copies of email notifications and configuring the URL for templates