Configuring access to a remote spell checker

To configure access to a remote spell checker server, perform the following configuration task using the Customization Dialog (z/OS) on the local portal server: Running spell checker locally is not supported on z/OS . Spell checker must be run on a remote WebSphere Application Server where remote spell check service is installed and configured. See Install a remote spell checker for more information.

1. Update wkplc.properties with the remote server information:

   1. cd WP_PROFILE/ConfigEngine/properties

   2. Edit wkplc.properties

   3. Specify values for the following parameters:

      SpellCheckHost

      Specify the hostname for the remote spell check server.

      For example,

      //myserver.myurl.com

      SpellCheckPort

      Specify the port number for the remote spell check server.

      To determine the remote server port:

      1. Log in to the WAS admin console; for example...
         http://remote_server:port_number/ibm/console

      2. Select Servers > Server Types > WebSphere appservers > server1.

      3. In the Communications section, expand Ports.

      4. Locate the port for WC_defaulthost. This is the remote server port.

      5. Log out of the WAS admin console.

2. cd WP_PROFILE/ConfigEngine
   ConfigEngine.sh delegate-spell-checking -DWasPassword=foo

3. Save the changes.

4. Restart the server.

If the portal server is securely protected using SSL, then the remote spell checker must be configured to use SSL as well. The RemotePort property must be set to the secure SSL port on the remote application server that is hosting the spell checker service. The remote server must import the portal server's client certificate into its SSL configuration repertoire's truststore and into the cacerts file found under the /AppServer/java/jre/lib/security directory on the remote server. The portal server must also import the remote server's client certificate into its SSL configuration repertoire's truststore and into the cacerts file found under the /AppServer/java/jre/lib/security directory on the portal server.

1. Start the Customization Dialog.

2. Follow the instructions in the Configure Productivity Components topic.

3. Ensure that you have followed the instructions associated with the customization dialog for submitting the customization job.

   Steps 4, 5 and 6 are required only if we are using a context root other than the default (/wps/) on either the local portal server or the remote SpellCheck server.

4. Locate the SpellCheckConfig.properties file in the following directory: WP_PROFILE/PortalServer/config/com/ibm/wps/odc/spellcheck/util.

5. Update the SpellCheckConfig.properties file with the remote server information:

   • SpellCheck_Remote_Context=/remote_context_root/spellcheck

   • SpellCheck_Context=/local_context_root/spellcheck

     The remote_context_root is the context root of the spell checker service being hosted on the remote server. The local_context_root is the context root of the portal server accessing the remote server.

   Alternatively, define the following parameters related to the remote server in the WP_PROFILE/ConfigEngine/properties/wkplc.properties file:

   • Set SpellCheckHost to the name of the remote spell checking host

   • Set SpellCheckPort to the remote spell checking port number

   Run...

   cd WP_PROFILE/ConfigEngine
   ConfigEngine.sh delegate-spell-checking -DWasPassword=foo

6. Restart the server.

If the portal server is securely protected using SSL, then the remote spell checker must be configured to use SSL as well. The RemotePort property in the SpellCheckConfig.properties file must be set to the secure SSL port on the remote application server that is hosting the spell checker service. When using RACF as keystore, store the certificate in WebSphere's keyring keystore. The remote server must import the portal server's client certificate into its SSL configuration repertoire's truststore and into the cacerts file found under the WAS_HOME/java/jre/lib/security directory on the remote server. The portal server must also import the remote server's client certificate into its SSL configuration repertoire's truststore and into the cacerts file found under the WAS_HOME/java/lib/security directory on the portal server.

Parent: Set up a remote spell checker