To start viewing statistics in the web console, you must
first connect to catalog servers that you want to monitor. Additional
steps are required if your catalog servers have security enabled.
Procedure
- If your catalog servers have Secure Sockets Layer (SSL)
enabled, you must configure a keystore, truststore, and client properties
file. You enable SSL for a catalog server by setting the
transportType attribute to SSL-Required in
the Server properties file.
- Configure a keystore and truststore, and then exchange,
or cross-import the public certificates. For example, you
might copy the truststore and keystore to a location on the server
that is running the web console.
- Edit the client properties file on the web console server
to include the properties for SSL configuration. For example,
you might edit the wxs_install_root/ObjectGridProperties/sampleclient.properties file.
The following properties are required for outbound SSL connections
from the web console:
#------------------------------------------------------------------------------
# SSL Configuration
#
# - contextProvider (IBMJSSE2, IBMJSSE, IBMJSSEFIPS, etc.)
# - protocol (SSL, SSLv2, SSLv3, TLS, TLSv1, etc.)
# - keyStoreType (JKS, JCEK, PKCS12, etc.)
# - trustStoreType (JKS, JCEK, PKCS12, etc.)
# - keyStore (fully qualified path to key store file)
# - trustStore (fully qualified path to trust store file)
# - alias (string specifying ssl certificate alias to use from keyStore)
# - keyStorePassword (string specifying password to the key store - encoded or not)
# - trustStorePassword (string specifying password to the trust store - encoded or not)
#
# Uncomment these properties to set the SSL configuration.
#------------------------------------------------------------------------------
#alias=clientprivate
#contextProvider=IBMJSSE
#protocol=SSL
#keyStoreType=JKS
#keyStore=etc/test/security/client.private
#keyStorePassword={xor}PDM2OjErLyg\=
#trustStoreType=JKS
#trustStore=etc/test/security/server.public
#trustStorePassword={xor}Lyo9MzY8
Important: If you are using Windows, you must escape any backslash (
\ )
characters in the path. For example, if you want to use the path
C:\opt\ibm,
enter
C:\\opt\\ibm in the properties file.
- Establish and maintain connections
to catalog servers that you want to monitor. Repeat the following
steps to add each catalog server to the configuration.
- Click .
- Add a new catalog server.
- Click the add icon (
) to register an existing catalog server.
- Provide information, such as the host name and listener port.
See Planning for network ports for more information about
port configuration and defaults.
- Click OK.
- Verify that the catalog server has been added to the navigation
tree.
- Group the catalog servers that you created
into a catalog service domain. You must create a catalog
service domain when security is enabled in your catalog servers because
security settings are configured in the catalog service domain.
- Click page.
- Add a new catalog service domain.
- Click the add icon (
) to register a catalog service domain. Enter a
name for the catalog service domain.
- After you create the catalog service domain, you can edit the
properties. The catalog service domain properties follow:
- Name
- Indicates the host name of the domain, as assigned by the administrator.
- Catalog servers
- Lists one or more catalog servers that belong to the selected
domain. You can add the catalog servers that you created in the previous
step.
- Generator class
- Specifies the name of the class that implements the CredentialGenerator interface.
This class is used to get credentials for clients. If you specify
a value in this field, the value overrides the crendentialGeneratorClass property
in the client.properties file.
- Generator properties
- Specifies the properties for the CredentialGenerator implementation
class. The properties are set to the object with the setProperties(String) method.
The credentialGeneratorprops value is used only if the value of the
credentialGeneratorClass property is not null. If you specify a value
in this field, the value overrides the credentialGeneratorProps property
in the client.properties file.
- eXtreme Scale client properties path
- Specifies the path to the client properties file that you edited
to include security properties in a previous step. For example, you
might indicate the c:\ObjectGridProperties\sampleclient.properties file.
If you want to stop the console from trying to use secure connections,
you can delete the value in this field. After you set the path, the
console uses an unsecured connection.
- Click OK.
- Verify that the domain has been added to the navigation tree.
To view information about an existing catalog service domain,
click the name of the catalog service domain in the navigation tree
on the page.
- View the connection status. The Current
domain field indicates the name of the catalog service
domain that is currently being used to display information in the
web console. The connection status displays next to the name of the
catalog service domain.