Checking that the Web Application Is Running

After you've installed the Enterprise Archive file, you need to check that the Web Application in the WebSphere Application Server has been launched.
For this task, you will need the following:




<wasserver_name> the name of the WAS server the name of the server machine running the WebSphere Application Server
<http_port> the communication port for the IBM Http Server WebSphere administrator
<rootURI> name that appears in the URL your users will use to connect to the web application WebSphere administrator, same as in "Creating the Enterprise Archive File"

Checking the Web Application Status

Before the web application can be launched from a Web Browser, the web application must be launched on the WebSphere Application Server. The application is launched automatically by default when deployed.

  1. Launch the Integrated Solutions Console and select Applications->Enterprise Applications:

    In our example, the enterprise application name is:

    ENOVIA B18

    The Status icon at the left of the application name is a green arrow, meaning that the application has been started.

Testing the Web Application

At this stage, you can run a limited test in order to check whether or not the environment was properly configured, and if the application was correctly deployed.

For example, after deploying a webtop application:

  1. Stop and restart the WAS and LDAP servers if necessary.
  2. In a web browser, type the following URL:




    to display the ENOVIA V5 logon dialog box:


  3. Log on as wpsadmin/wpsadmin:

    If the Web browser displays the CATJadOptions page and there is no error message, the rest of the installation can proceed. Otherwise, re-check all the steps.


On UNIX, if WebSphere fails to start after the web application is installed, check the SystemOut.log file of this server. If the log ends with the following line:

[9/2/05 10:34:54:622 CEST] c15f886 SystemOut O + Registered servlet [hcb] Asynchronous Callback Servlet for HTML

then the problem is likely to be an invalid X11 display (refer to Creating the Enterprise Archive File).