Page tree
Skip to end of metadata
Go to start of metadata

Spell checking in Textbox.io is provided by a spell-checking web service.  

For spell checking to function within Textbox.io this services must be installed and configured into the IBM Connections environment.  

This service can be installed and configured by following the instructions below.

  1. Install the Textbox.io Services for IBM Connections application, as outlined here: Textbox.io Services for IBM Connections Installation.
  2. Configure Textbox.io Services. You can specify configuration for the Textbox.io server-side features using one of 2 options:

    1. You can create an application.conf file and specify the settings as documented in the Configuring Textbox.io Services article with the following variations for Connections and WebSphere:

      1. On the drive/partition where WebSphere Application Server (WAS) is installed, create the text file /opt/ephox/application.conf (Unix/Linux) or WAS_INSTALLATION_DRIVE:\opt\ephox\application.conf (Windows, where WAS_INSTALLATION_DRIVE is the drive where WAS is installed, e.g. "C", "D" or "E" etc).

      2. Edit this file as shown in section "Create a configuration file" on the installing the server-side components page in the Textbox.io documentation.

      3. When configuration is updated, please restart the EphoxTbioServices application via WebSphere Application Server.
         
    2. If the file based mechanism is not appropriate, you can set JVM system settings for the configuration of the services. The following steps describe the process for setting the configuration using JVM system properties.
      1. Find your JVM settings according to the version of Websphere that you are running.

        1. Use this page to do so: http://www-01.ibm.com/support/docview.wss?uid=swg21417365

      2. Specify the domains where the editor is served from, and optionally other settings such as link caching and proxy configuration. For details, please review Server-Side Components - Installation and Setup for Textbox.io.
        Example:  -Dephox.allowed-origins.origins.0=http://connections -Dhttp.proxyHost=someproxy.internal.corp -Dhttp.proxyPort=8080

      3. When specifying the URL/s for the domains that will serve the Textbox.io editor, you may need to specify different combinations of the protocol, hostname and port based on the browsers you use. For more details, please review Server-Side Components - Installation and Setup for Textbox.io.
        If you need additional domains where the editor is served from, you need to specify additional allowed origins by repeating repeat step c, replacing the “0” with an incrementing number for each domain that is added.
        Example:

        • -Dephox.allowed-origins.origins.1=http://connections.yourdomain 

        • -Dephox.allowed-origins.origins.2=http://connections:10039 

        • -Dephox.allowed-origins.origins.3=http://connections.yourdomain:10039

      4. In order for these configuration properties to take effect, you will need to restart your WebSphere Application Server.

  1. Ensure Textbox.io Services can make outbound HTTP and HTTPS (SSL) connections to in-house servers and the public Internet. These are required by link checking, media embedding and advanced image editing services which make an outbound call for each link, media or image. WebSphere must be able to reach any web page, media or image potentially targeted by users of Textbox.io. 
    1. Ensure HTTP proxies are properly configured for outbound connections. See installing the server-side components.
    2. Ensure WebSphere has the proper SSL configuration - including certificate authority root certificates for verifying SSL connections in its trust store - for all potential targets of secure (SSL) connections. Targets usually include in-house servers potentially secured by an in-house certificate authority as well as servers on the public Internet secured by public certificate authorities.
      1. SSL security can be configured in the WebSphere console under Security > SSL certificate and key management. Textbox.io Services will honor dynamic outbound endpoint SSL configurations based on hostname and, optionally, port number, if configured. Optionally, Textbox.io Services can be configured to use a particular named SSL configuration instead using the configuration setting ephox.http.websphere.ssl-config-name. E.g. after creating an SSL configuration named "TbioServices", configure ephox.http.websphere.ssl-config-name=TbioServices.
      2. All of WebSphere's SSL security configuration - including trust stores and certificates but also protocol, cipher settings etc. - can optionally be bypassed and the JVM's SSL configuration - including the JVM trust store with its certificates - be used instead by configuring ephox.http.websphere.use-ssl-config=false.
      3. For use in evaluation or pre-production environments, all SSL security can be bypassed by both configuring ephox.http.websphere.use-ssl-config=false and ephox.http.trust-all-cert=true. This is not recommended for production environments.
    3. One way of creating a simple, adequate WebSphere SSL configuration would be to create a new keystore entry under "SSL certificate and key management > Key stores and certificates" and point the path to the trust store of WebSphere's JVM, usually something like /opt/IBM/WebSphere/AppServer/java/8.0/jre/lib/security/cacerts, with password "changeit", and the type to "JKS". Root certificates of in-house certificate authorities could then be added to this trust store, and the trust store then selected as the trust store of the default SSL configuration. No extra WebSphere related Textbox.io configuration settings are needed in this case.

For more information on service configuration, please consult Textbox.io's Services documentation.

  • No labels