JavaScriptin the Directory Hierarchy on the HTTP Server

Putting the JavaScript source code in the script repository makes it reusable, and it is easy to deploy in this manner.  However, it can still be done better.  This next step is better because it allows the users web browser to cache the easy_java.js script locally.  That way the next time the same script is referenced it does not need to be downloaded to the users’ browser since it was downloaded previously.

The following explanation assumes the user has the appropriate privileges to create files in the directories described below.  The directories mentioned are on the machine running the HTTP Server.  This also assumes the readers’ images directory is the same as the path shown here:

Windows: 

C:\oracle\product\10.2.0\ohs\Apache\Apache\images

Unix/Linux: 

/u01/app/oracle/product/10.2.0/ohs/Apache/Apache/images

At this point, a new directory named easy_htmldb should be created under the images directory.

C:\oracle\product\10.2.0\ohs\Apache\Apache\images\easy_htmldb

Then, copy the easy_java.js script from the code depot directory to the new easy_htmldb directory.  This places the file in the correct location from which it can be referenced on each of the application pages.  It also makes it available to all applications in all workspaces running from this HTTP Server.

To change the reference in the HTML Header region of the Java Script page navigate back to the page attributes page and make the changes as shown in figure 13.6.

The changes in figure 13.6 involve the substitution string and a reference to the new easy_htmldb directory.

<script src="#IMAGE_PREFIX#easy_htmldb/easy_java.js"
type="text/javascript"></script>

            The easy_java.js script can be referenced directly from a browser with the following URL.  What this shows is the URL path to the file on the file system:
               http://localhost:7777/i/easy_htmldb/easy_java.js