Install and Configure JSpell Spell Checker SDK (Optional)

JSpell Spell Checker SDK is a third-party product from Page Scholar Inc (http://www.jspell.com/). You can use it to check the spelling of text objects in Oracle Clinical DCM and DCI graphic layouts. You must purchase the product separately.

For more information, see:

• Install JSpell on Oracle Application Server
  
• Install the JSpell WAR File on the WebLogic Server
  
• Update the mod_wl_ohs.conf File for JSpell
  
• Stop and Start Oracle HTTP Server (OHS)
  
• Test the JSpell Servlet
  
• Change the Lexicons Directory if Necessary
  
• Update the formsweb.cfg File for JSpell
  
• Update the Windows System Registry for JSpell
  
• Test JSpell in the Graphic Layout Editor
  

Install JSpell on Oracle Application Server

To install the JSpell on Oracle Application Server:

1. If you have not already done so, download and extract JSpell, following instructions in Download JSpell (Optional).
2. Identify the following files in the download directory:
   • jspellsdks.jar
   • jspellsdkn.jar
   • jspellsdk.war
3. Copy the two .jar files to the following location on the Oracle Application Server: middleware_home \ Oracle_FRHome1\forms\java; for example: C:\app\oracle\middleware\Oracle_FRHome1\forms\java.

Install the JSpell WAR File on the WebLogic Server

To install the JSpell .war file on the WebLogic server:

1. Copy the jspellsdk.war file to any location on the WebLogic server:
2. Extract the contents of jspellsdk.war to a folder named jspellsdk:
   
   Description of the illustration jspell_war_path.gif
3. Copy the jspellsdk folder to default Admin Server upload location: middleware_home\user_projects\domains\OPADomain\servers\AdminServer\upload.
4. Also copy the jspellsdk folder to the Target Server stage location. (middleware_home\user_projects\domains\OPADomain\servers\Server.Domain_OPA_1\stage)

   Note:

   If the stage directory does not already exist, create it.
5. Log in to the OPADomain Admin Server console at: http://server_namedomain:7101/console
6. Click the Deployments tab.
7. Click the Install button.
8. Check the Current Location. If it does not show the upload directory under AdminServer shown in Step 3 above, navigate to that location.
9. Select jspellsdk (open directory) and click Next.
10. Select Install this deployment as an application and click Next.
11. Select the Target Server Managed Server Name under OPADomain and click Next.
12. Under General, What do you want to name this deployment? enter jspellsdk in the Name: field.
13. Click Finish. In a moment the summary screen appears.
14. Restart the Managed Server of OPADomain process; see Start the Managed Server of OPADomain.
15. In the Summary of Deployments page in the OPADomain Admin Server console, check that jspellsdk is listed as Active and its Health value is OK.

Update the mod_wl_ohs.conf File for JSpell

By default JSpell uses port 7221. To make this work with either HTTP port 8888 or HTTPS port 443, edit mod_wl_ohs.conf and restart OHS.

To update the mod_wl_ohs.conf file:

1. Navigate to the following directory:
   middleware_home\Oracle_Home_FR\user_projects\domains\FRdomain\config\fmwconfig\components\OHS\instances\ohs1\moduleconf
2. Open the fmod_wl_ohs.conf file.
3. Add the following entry:

   <Location /jspellsdk>
   setHandler weblogic-handler
   webLogicHost localhost
   weLogicPort 7221
   </Location>

Stop and Start Oracle HTTP Server (OHS)

To restart OHS:

1. Open a DOS prompt.
2. To stop OHS enter:

   drive:\ORACLE_HOME\user_projects\domains\FRdomain\bin\stopComponent.cmd ohs1
   

3. To start OHS enter:

   drive:\ORACLE_HOME\user_projects\domains\FRdomain\bin\startComponent.cmd ohs1

Test the JSpell Servlet

To test the JSpell Servlet:

1. Open a browser.
2. Enter the following URL:
   https://server_namedomain:7221/jspellsdk/servlet/JSpellServlet? operation=status

If the status page opens without error, JSpell is installed properly.

Change the Lexicons Directory if Necessary

If the Application Server and JSpell directories are located under the same parent directory; for example, C:/oracle and C:/jspell, then you can skip this step. If they aren't in the same parent directory, you must map JSpell's lexicons directory:

1. Navigate to the following directory:

   ORACLE_HOME\j2ee\opa\applications\jspellsdk \jspellsdk\WEB-INF

2. Open the web.xml file.
3. Find the following lines in the web.xml file:

   init-param 
   param-name indexDirectory/param-name 
   param-value/jspell//param-value 
   /init-param 
   

4. Change the /jspell/ text string to the location of the lex_enUS.jdx file on the Application Server.

Update the formsweb.cfg File for JSpell

To update the formsweb.cfg file:

1. Navigate to the following directory:

   middleware_home\user_projects\domains\FRDomain\config\fmwconfig\servers\WLS_FORMS\applications\formsapp_12.2.1\config
   

2. Open the formsweb.cfg file.
3. Find the [opa54] text section.
4. Append the following text string to the end of the archive parameter value:

   jspellsdks.jar,jspellsdkn.jar

Update the Windows System Registry for JSpell

Update the Windows System Registry:

1. Open the Windows System Registry Editor.
2. Navigate to the following key:
   \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEYnumber where the Oracle Clinical and OPA registry settings are.
3. Add the following keys to the registry:
   • OPA_SPELL_ENABLED=Y
   • OPA_SPELL_LANGUAGE=English (US)
   • OPA_SPELL_URL= http://server_name/jspellsdk/servlet/JSpellServlet

     Note:

     In the above registry value, use either HTTP or HTTPS, depending on how your system is configured.

Test JSpell in the Graphic Layout Editor

If you already have a study set up that uses the Graphic Layout Editor:

1. In Oracle Clinical, navigate to a study DCM.
2. From the Special menu, select Graphic Layout, then Edit. The Graphic Layout Editor opens.
3. From the Edit menu, select Spell Check Current.
4. If you receive a warning that the application is unsigned, click Run. The system displays the first misspelled word it finds and suggests alternative spellings.
5. To find another misspelled work, select Find Next Misspelling from the Edit menu.

If you do not already have such a study set up, see Oracle Clinical Creating a Study.