Configuring the Eclipse user interface

Before you can use the Eclipse user interface (UI) to access the objects in WebSphere® Service Registry and Repository (WSRR), you must configure the UI with the connection details that it needs, including any security details for making a secure connection.

Before you begin

Before you start, you must have completed the following tasks:

Install: Prerequisites for installing the Eclipse user interface
Ensure that your default installed Java™ Runtime Environment (JRE) for your Eclipse environment is set correctly, according to the JRE that you are using.
If your underlying JRE is an IBM® JRE, ensure that your default installed JRE for your Eclipse environment is set to a WebSphere Application Server Version 6 JRE (WAS6 JRE) or equivalent. This JRE has IBM specific security handshaking JAR files that let the plug-in communicate with an instance of WSRR running on a secured WebSphere Application Server.

The WebSphere Application Server JRE location is:
<WebSphere Application Server installation directory>\java\jre

If your underlying JRE is a Sun JRE, ensure that your default installed JRE is set accordingly.

About this task

After you have configured a connection to an instance of WSRR, you can view the objects stored in that registry. You can configure connections to multiple WSRR instances, and switch between them in the Eclipse UI.

Procedure

To configure the Eclipse UI to connect to WSRR:

Start the Eclipse workbench and ensure that the WSRR Content view is open.
Select Window > Preferences. The Preferences dialog opens.
In the Preferences dialog, click WebSphere Service Registry and Repository (WSRR). The WSRR Locations page is displayed.
Note: If you are using IBM Integration Designer, you will also see an entry for IBM WebSphere Service Registry and Repository under Window > Preferences. This relates to additional functionality provided by IBM Integration Designer. If you wish to use the features of the WSRR Eclipse plug-in you must still configure the section labelled WebSphere Service Registry and Repository (WSRR).
On the WSRR Locations page, click Add. The Add a new WSRR location alias dialog opens.
In the dialog, enter your connection details:
1. In the Alias field, type a meaningful name for the connection. For example, type the name of the remote computer to which you are connecting.
2. In the Protocol field choose the appropriate HTTP protocol (for a non-secured WSRR choose http or for a secure WSRR choose https).
3. In the Host field, type the fully-qualified name or IP address (IPv4 or IPv6) of the remote computer to which you are connecting. For example, jiffy.hursley.ibm.com or 192.168.0.3
  Note: If the WebSphere Application Server node name is different from the computer name that it is running on, the Eclipse plug-in fails to resolve the IP address given to it. To check this compare the computer name to the name of the node in WebSphere Application Server, by using the WebSphere Application Server administrative console.
  The solution is to edit the hosts file (/etc/hosts or C:\windows\system32\drivers\etc\hosts) on the computer running the Eclipse plug-in, to map the IP address of the WSRR server to the WebSphere Application Server node name.
  For example:
    IP address of WSRR server is 9.20.198.52
    WebSphere Application Server node name is    wasserver
    Append to the hosts file          9.20.198.52   wasserver
4. In the Port field, type the port number of the WSRR listening port on the host computer for your WSRR (by default, this is 9080 for an non-secured WSRR and 9443 for a secure WSRR).
5. If security is enabled, you must provide security credentials so that the plug-in can communicate with a secure WSRR. To do this, perform the following actions:
  1. Select the Connect to server with security check box.
  2. Provide the user ID and password with which to log in.
  3. (Optional) Provide keystore and truststore details according to your underlying JRE.
    If you are using an IBM JRE, provide the keystore and truststore files, with their passwords. An example trust store file directory location is D:/IBMRAD/Rational/SDP/6.0/runtimes/base_v6_stub/profiles/default/etc/.
    If you are using a Sun JRE, create a file called ssl.client.props and provide the location of the file. The ssl.client.props file must contain the following settings:
```
com.ibm.ssl.protocol=SSL
com.ibm.ssl.trustManager=SunX509
com.ibm.ssl.keyManager=SunX509
com.ibm.ssl.contextProvider=SunJSSE

com.ibm.ssl.keyStore=eclipse_install_dir/
plugins/com.ibm.serviceregistry.preferences.sun_3.0.0/security/DummyServerKeyFile.jks
com.ibm.ssl.keyStorePassword=WebAS
com.ibm.ssl.keyStoreType=JKS
com.ibm.ssl.keyStoreProvider=SUN

com.ibm.ssl.trustStore=eclipse_install_dir/
plugins/com.ibm.serviceregistry.preferences.sun_3.0.0/security/DummyServerTrustFile.jks
com.ibm.ssl.trustStorePassword=WebAS
com.ibm.ssl.trustStoreType=JKS
com.ibm.ssl.trustStoreProvider=SUN
```
6. Click OK. The new connection is listed on the WSRR Locations page of the Preferences dialog.
Select the new location, checking the appropriate location, then click OK.
(Optional) Add the signer part of the personal server certificate to the client key and trust store files. To do this, export the signer part of the personal certificate, from the WebSphere Application Server where WSRR has been installed, to a file (see Secure installation for client signer retrieval in SSL in the WebSphere Application Server Information Center), then add the file to the key and trust store files on the client (where Eclipse is installed) by using a key management utility such as iKeyman. If you do not do this, then the first time that you attempt to connect to WSRR from the Eclipse user interface, you are prompted to accept or reject the certificate; if you accept, the certificate is added to the trust store automatically, and you are not prompted again.