6 Starting the Standalone Web Client

This chapter contains the following topics:

6.1 Overview

To start Standalone Client Web Applications

  1. Follow the steps in this section of this guide entitled: Chapter 5, "Starting the Standalone Client".

  2. From the menu on the main screen, select Tools > EnterpriseOne Menu.

The Standalone Client should automatically sign you into the Standalone Web Client.

6.2 Troubleshooting Standalone Web Client Startup Errors

This section discusses these troubleshooting topics:

6.2.1 General

If you have any trouble running the Web Client, look at the Web Client logs.

  1. In Microsoft Windows Explorer, drill down to the location of the Web Client logs. By default, the logs are located in this directory:


  2. Examine any logs that were recently created, especially logs that are prefixed with either:

    • jas

    • jde

  3. If you do not find any logs with the above prefixes, the logs may be in another folder. Use this procedure to determine the location of those logs:

    1. In Microsoft Windows Explorer, drill down to this directory:

      C:\JDEdwards\E910\system\OC4J\j2ee\home\applications\ webclient.ear\webclient\WEB-INF\classes

    2. Edit the file jdelog.properties.


      The information at the top of the jdelog.properties file explains the uses and possible values of all the keys in the file.

      Search through the file and note the value of the FILE key. In each of the sections that describe a log file there are section headers that are enclosed in square brackets ([ and ]). If a section header or the FILE key is commented out with a pound or hash sign (#), you can ignore that section. For example:

      # [E1LOG]


      # File=log\jderoot.log

      The value of the FILE key in each section is the name and path of a log file associated with that section. For example:


      The actual file name will be the value of the FILE key with an underscore and the current date appended. For example:


      If a log file name and path starts with a drive letter followed by a colon and slash, the path is absolute. This means that the log file will be located on the specified drive in the specified directory. For example:


      If a log file name and path starts with a slash, the path is also absolute. This means that the log file will be located on the drive on which the E1 Standalone Client is installed and in the specified directory. For example:


      If a log file name and path start with neither a drive letter nor a backslash, the path is relative to this folder:


      For example, if the value for the FILE key is log\jas.log and the Standalone Client is installed in C:\JDEdwards\E910, the log file is written to:


6.2.2 Cannot Connect to the Security Server


After starting the Standalone Web Client from the Standalone Client, you get an error on the screen indicating that the Web Client could not connect to the security server.


Verify that the local database services are running using this procedure:

  1. Go to Start > Control Panel -> Administrative Tools -> Services.

  2. Verify that the statuses of these services are Started:

    • OracleServiceE1LOCAL

    • OracleE1LocalTNSListener

    If not, for each stopped service click Action > Start in the menu.

  3. Try to sign in again by following these steps:

    1. Exit from the Standalone Web Client and Standalone Client.

    2. Run the Microsoft Windows Task Manager.

    3. Wait for these processes to die:

      • activConsole.exe

      • jdenet_n.exe

      • java.exe


      The java.exe program is used by a variety of programs written in the Java programming language. One of these programs is the Standalone Web Client; however, it could be running for any number of other Java programs. It is difficult to tell in Microsoft Windows Task Manager if the java.exe is associated with the Standalone Web Client or with some other program. If you wait for a minute or more and a java.exe remains running, you can assume that it is associated with a Java program other than the Standalone Web Client. In that case, continue to the next step.
    4. Rerun activConsole.exe to restart the Standalone Client, sign in, and start the Standalone Web Client (select Tools > EnterpriseOne Menu from the Standalone Client).