File based configuration
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:
On the drive/partition where WebSphere Application Server (WAS) is installed, create the text file
Operating System Path Notes Linux/Unix /opt/ephox/application.conf Windows WAS_INSTALLATION_DRIVE:\opt\ephox\application.conf WAS_INSTALLATION_DRIVE is the drive where Websphere Application Server is installed, e.g. "C", "D" or "E" etc
Edit this file as shown in section "Create a configuration file" on the installing the server-side components page and the configure the enhanced media embed service page in the Textbox.io documentation. In the example below we have chosen to only include the free Youtube oEmbed endpoint as an example but normally you would list many more or use an Iframely account for the best experience.
- When configuration is updated, please restart the EphoxTbioServices application via WebSphere Application Server.
JVM System properties based configuration
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.
Find your JVM settings according to the version of Websphere that you are running. Use this page to do so: http://www-01.ibm.com/support/docview.wss?uid=swg21417365
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.
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 -Dephox.allowed-origins.origins.0=domain, replacing the “0” with an incrementing number for each domain that is added.