This chapter contains the following topics:
Section 5.4, "Generating Serialized Objects for the HTML Server"
Section 5.5, "Configuring the HTML Server for Non-Western European Languages"
Section 5.6, "Enabling the Browser Side Debugging Feature on the Web Client"
Section 5.7, "Customizing the Disclaimer for the Sign-In Page"
Section 5.8, "Setting Up Quick Links for Pervasive Device Support"
Section 5.9, "Clearing File Attachments from the Browser Cache"
Tip:
In order to enable any modifications, you should always stop and restart the Application Server any time you modify the configuration.Note:
Beginning with Tools Release 8.97, many administrative tasks (such as starting and stopping services) for both the HTTP server and the JD Edwards EnterpriseOne HTML Web server can be performed through the Server Manager Console.The JD Edwards EnterpriseOne HTML Server is installed in the instance of the application server that you defined when you installed the Web Server (for example, AS_JS_81). Complete this task to start the server.
To start the HTML Server:
Start the Server Manager console.
Select the Server and Instance you want to start.
Select the Start button.
If you are using the 64-bit instance of DB2 8.1, 8.2, 9.1 on a 64-bit kernel, open the startServer.sh script and verify that the environment variable is correct for your platform.
Note:
This step does not apply to the Linux platform, since JD Edwards EnterpriseOne is not supported on 64-bit db2 on Intel 32 hardware.Note that $<DB2_Instance_Home>/sqllib/lib32 must be in the path. If the path to lib32 is missing, add the path as shown in these examples:
For AIX:
LIBPATH="$WAS_LIBPATH":$<DB2_Instance_Home>/sqllib/lib32:$LIBPATH
For Solaris:
LD_LIBRARY_PATH="$WAS_LIBPATH":$<DB2_Instance_Home>/sqllib/lib32:
$LD_LIBRARY_PATH
For HP-UX:
SHLIB_PATH="$WAS_LIBPATH":$<DB2_Instance_Home>/sqllib/lib32:$SHLIB_PATH
The JD Edwards EnterpriseOne HTML Server is installed in an instance of the application server that you defined when you installed the Web Server (for example, AS_JS_81). Complete this task to stop the server.
To Stop the HTML Server:
Start the Server Manager console.
Select the Server and Instance you want to stop.
Select the Stop button.
You can access the HTML Server from any web browser connected to your network.
To access the HTML Server:
Open the JD Edwards HTML client by opening a browser and entering this URL:
http://<web_server_name>:<port_number>/jde/owhtml or
http://<web_server_name>:<port_number>/jde/E1Menu.maf
For example:
http://jdewebs1.myserver.com:81/jde/owhtml or
http://jdewebs1.myserver.com:81/jde/E1Menu.maf
Starting with application release 8.12, JD Edwards EnterpriseOne specs are delivered in XML format, which allows for on-demand generation of serialized Java objects from these XML specs. Objects are now automatically generated when the first user accesses an application, and the only objects not automatically generated are FDA-created portlets.
eGenerator can still be used to manually generate serialized objects. eGenerator is the only method for generating FDA-created portlets, so it is required if you installed a Portal and created portlets in the FDA application.
To install the eGenerator and manually generate serialized objects, refer to Appendix A, "Generating JD Edwards EnterpriseOne Serialized Objects".
If you are setting up the HTML Server to run Non-Western European Languages, complete this task to ensure that the Application Server is properly configured for Unicode.
To configure the HTML Server for Non-Western European Languages:
Open the WebSphere Administrative Console, and select the Application Server for the JD Edwards HTML Server.
Using Server Manager, verify this code page parameter and setting:
codePage=1252
Using Server Manager, verify this UBE queue parameter and setting:
UBEQueue=QB900
In past releases, a user working on a form in the web client could press the Ctrl+D keys to display GUI elements at the bottom of the page that are used for browser side debugging. Starting with release 8.96, this feature is disabled in the default mode, and the web client no longer displays this debugging feature when Ctrl+D is pressed. To enable this feature for developers and support personnel, the system administrator must modify the JDEDTA.js file as described in this task.
To enable the browser side debugging feature:
On the HTML Server, navigate to the webclient.war/js/ directory, and open the JDEDTA.js file in a text editor.
Search for the following line:
var allowDebug=false;
and change the value to true.
Save the file.
You do not need to restart the server to activate the change.
Open Internet Explorer, and press the Refresh button to reload the page.
This action refreshes the .js files cached in the browser to activate the Ctrl-D feature.
When web-based clients log on to JD Edwards EnterpriseOne, the sign-in page includes a default disclaimer that is included in a file shipped with the HTML Server software. This task describes how to modify this file to include your own disclaimer.
To specify an additional disclaimer for the sign-in page:
Open this file in a text editor:
<JAS_HOME>\webcontent\share\html4login.jsp
where <JAS_HOME> is the installation directory of the HTML Server.
Make a backup of this file.
Locate the following line and specify your disclaimer with the following element:
String companyDisclaimerHTML = "";
For example:
String companyDisclaimerHTML = "By signing in, you agree to the <a href=\"http://server/path-to/privacypolicy.html\">privacy policy</a>.";
Tip:
This element is Java code. Therefore, quotation marks must be preceded by a back-slash character, as shown above.Save the file.
Your changes should take effect immediately. If not, restart the portal.
JD Edwards EnterpriseOne offers support for Pervasive Devices. Developers can write custom applications for PocketPC 2003 devices using the EnterpriseOne toolset. However, JD Edwards EnterpriseOne menus are not supported on Pervasive Device clients, so a new XML file (PervasiveAppQuickLinks.xml) was added to the HTML Server that allows a system administrator define the list of applications that can be executed on the Pervasive Device client. This file can be edited to add, modify, or delete JD Edwards EnterpriseOne applications that are accessible to Pervasive Device clients. Each application listed in this file is defined by a quick-link tag that describes the application, form, and version of the object, and includes a description. A sample quick-link tag is shown below:
<quick-links>
<quick-link launchAction="launchForm"
appID="P0411"
formID="W0411G"
version="ZJDE0001"
description="3 G0411 - Standard Voucher Entry
(P0411_W0411G_ZJDE0001)"/>
</quick-links>
Quick-link tags can include the following attributes:
| Attribute | Required? | Description |
|---|---|---|
| launchAction | yes | Specifies the action that occurs when users click on the quick-link. Valid values are:
|
| appID | yes | Program number of the application. For UBE type objects, the AppID is the UBE name. |
| appType | Required for promptForVersion action. | Type of application.
Valid values are:
|
| formID | Required for launchForm and promptForValue actions. Also required with the appType attribute. | Number of the specific form within the application. |
| version | No | Version number of the form. |
| description | Yes | Description of the form. This description appears in the list displayed on the Pervasive Device client. |
To edit the PervasiveAppQuickLinks.xml file
On the HTML Server, navigate to this directory: <JAS_Home>/installedApps/<node_name>/EA_JS_81.ear/webclient.war/classes.
Open the PervasiveAppQuickLinks.xml file in a text editor.
Add quick-link tags for each of the JD Edwards EnterpriseOne applications you want to make accessible to Pervasive Devices.
You can also delete or modify existing tags to remove or change the forms that Pervasive Device clients can access. When clients access JD Edwards EnterpriseOne from a Pervasive Device, the forms are listed as links in the same order they appear in the PervasiveAppQuickLinks.xml file.
Save and exit the file.
Below is an example of the PervasiveAppQuickLinks.xml file:
<?xml version="1.0" encoding="UTF-8" ?> <quick-links> <quick-link launchAction="launchForm" appID="P0411" formID="W0411G" version="ZJDE0001" description="3 G0411 - Standard Voucher Entry (P0411_W0411G_ZJDE0001)" /> <quick-link launchAction="launchForm" appID="P01012" formID="W01012B" version="ZJDE0001" description="P01012_W01012B" /> <quick-link launchAction="promptForValue" appID="P01012" formID="W01012B" version="ZJDE0001" mode="1" appType="APP" description="Prompt for Values(P01012_W01012B,ZJDE0001,1,APP)" /> <quick-link launchAction="promptForValue" appID="P4210" formID="W4210E" description="Prompt for Values(P4210_W4210E)" /> <quick-link launchAction="promptForVersion" appID="P01012" formID="W01012A" appType="APP" description="Prompt for Version(P01012_W01012A)" /> <quick-link launchAction="promptForVersion" appID="R0006P" appType="UBE" description="Prompt for Version(R0006P)" /> <quick-link launchAction="launchForm" appID="P98TREE" formID="W98TREEA" description="P98TREE_W98TREEA" /> <quick-link launchAction="launchForm" appID="P98SYSGR" formID="W98SYSGRB" description="P98SYSGR_W98SYSGRB" /> <quick-link launchAction="launchForm" appID="P98CTRL" formID="W98CTRLA" description="P98CTRL_W98CTRLA" /> <quick-link launchAction="launchForm" appID="P98RUNPC" formID="W98RUNPCM" description="P98RUNPC_W98RUNPCM" /> <quick-link launchAction="launchForm" appID="P98SYSFM" formID="W98SYSFMA" description="P98SYSFM_W98SYSFMA" /> <quick-link launchAction="launchForm" appID="P98SYSFM" formID="W98SYSFMB" description="P98SYSFM_W98SYSFMB" /> <quick-link launchAction="launchForm" appID="P98FRMFL" formID="W98FRMFLA" description="P98FRMFL_W98FRMFLA" /> <quick-link launchAction="launchForm" appID="P98MEDIA" formID="W98MEDIAA" description="P98MEDIA_W98MEDIAA" /> <quick-link launchAction="launchForm" appID="P90CB050" formID="W90CB050A" description="P90CB050_W90CB050A" /> <quick-link launchAction="launchForm" appID="P55SFRU1" formID="W55SFRU1A" description="P55SFRU1_W55SFRU1A" /> <quick-link launchAction="launchForm" appID="P99WIZ01" formID="W99WIZ01B" description="P99WIZ01_W99WIZ01B" /> <quick-link launchAction="launchForm" appID="P99WIZ03" formID="W99WIZ03A" description="P99WIZ03_W99WIZ03A" /> <quick-link launchAction="launchForm" appID="PMODAL" formID="WMODALA" description="PMODAL_WMODALA" /> <quick-link launchAction="launchForm" appID="P42101" formID="W42101C" description="New Sales Order Application" /> </quick-links>
In a typical environment, file attachments (such as Media Object attachments and JD Edwards EnterpriseOne reports) are automatically cached into the \Temporary Internet Files directory on web-based client machines when these attachments are opened from a browser. This situation allows copies of confidential documents, such as Media Objects, images, and web pages, to proliferate across workstations on which these objects are opened.
To prevent these objects from persisting in the internet cache, administrators should configure the browsers to automatically clear the cache when the client closes the browser. This protection is particularly important in a kiosk environment. The procedure for clearing the cache depends on the type of browser. Refer to the relevant task below to secure the browser used in your system.
In addition to securing the browser cache, Media Object Security was added in 8.96 to ensure that media objects can be secured within the application. For more information on this topic, see "Managing Media Object Security" in the JD Edwards EnterpriseOne Tools Security Administration Guide.
This section describes these tasks:
Complete this task to automatically clear the cache in Internet Explorer.
In Internet Explorer, select Tools, Internet Options from the drop down menu.
Click the Advanced tab.
In the "Settings" box, scroll down to the section labeled "Security," and select the check box next to Empty Temporary Internet Files folder when browser is closed."
Click OK to save the change.
This option does not delete cookies, but will clear your cache of other files when you close the browser.
Tip:
Access the following web page for more details:http://www.microsoft.com/windows/ie/using/howto/customizing/clearcache.mspx
Activate the Private Browsing feature of Safaris to secure the browser. When activated, no web addresses, personal information, or pages are saved or cached on the browser, and no trace of any activity is recorded.
Activate the Clear Private Data tool to secure Firefox. This tool allows you to delete all personal data, including browsing history, cookies, Web form entries and passwords with a single click. Mozilla Firefox can also be configured to automatically clear this information when you close the browser.