Verifying That the Deployment Was Successful

Introduction to MapViewer 1-15 Click Deploy on the Deployment Setting page to start the deployment of MapViewer. If the deployment is successful, the Confirmation page is displayed indicating that deployment of the application was successful. After you complete the deployment, see Section 1.4.4 .

1.4.3 Installing MapViewer with a Standalone Installation of OC4J

To install and deploy MapViewer with a standalone installation of OC4J, you must have installed OC4J on your system. The standalone OC4J installation kit is a single zip file that you can download from OTN. It contains the Oracle Container for J2EE and also a lightweight Web server. After you unzip this file, you can start the OC4J instance up by entering the command java –jar oc4j.jar from the OC4J_ HOME j2eehome directory, where OC4J_HOME is the top directory into which you unzipped the installation file. Note that you must have the Java 1.5 SDK installation, not the JRE installation, in your environment path in order for OC4J to start up and function properly. Because standalone OC4J version 10.1.3 or later comes with its own Server Control Web interface, the deployment of MapViewer is almost exactly as described in Section 1.4.2 once you log in to its Server Control Web page. The only difference is that you will not be able to choose a different OC4J instance, because you are running in a single standalone OC4J instance. After you complete the deployment, see Section 1.4.4 .

1.4.4 After Deploying MapViewer

After successfully deploying MapViewer to Oracle Fusion Middleware 10gR3, standalone OC4J, or WebLogic Server, you may want to verify whether it is actually working, as described in Section 1.4.4.1 . It is also a good idea to become familiar with its Web interface, particularly the administration pages. You must also run at least one, and perhaps several, SQL scripts, as explained in Section 1.4.4.2 .

1.4.4.1 Verifying That the Deployment Was Successful

To test if the MapViewer server has started correctly, point your browser to that OC4J instance. For example, if MapViewer is installed on a system named www.example.com and the HTTP port is 8888, enter the following URL to invoke the MapViewer server with a simple get-version request: http:www.example.com:8888mapvieweromserver?getv=t If MapViewer is running correctly, it should immediately send back a response text string indicating the version and build number, such as the following: Ver10131_B060225 The actual version and build number will reflect the version that you installed. If the server has not been started and initialized correctly, there will be no response, or the message 500 internal server error will be displayed. If the response message includes wording like MapServer is not ready. Please try again later, it could mean that the MapViewer server is initializing, but the process will take some additional time for example, because the system is slow or because multiple predefined data sources are specified in the configuration file and MapViewer is 1-16 Oracle Fusion Middleware Users Guide for Oracle MapViewer attempting to connect to these databases. In this case, you can wait at least a few seconds and try the preceding request again. However, if you continue to get this response message, there may be a problem with the deployment. Check for any error messages, either in the OC4J console for a standalone OC4J deployment or in the redirected outputerrors log file of the OC4J instance for a full Oracle Fusion Middleware 10gR3 deployment. The following are common causes of this problem: ■ On a UNIX or Linux operating system, the Java virtual machine JVM was not started with the –Djava.awt.headless=true option, and no DISPLAY environment variable is set. This causes the MapViewer server to fail because the server accesses the Java graphics library, which on UNIX and Linux systems relies on the X11 windowing system. ■ You deployed the mapviewer.ear file to an incompatible version of Oracle Fusion Middleware or standalone OC4J. Note that the MapViewer 10.1.3.1 must be deployed to Application Server 10gR3 or standalone OC4J 10.1.3 or later. It will not work properly with earlier versions of Oracle Application Server or OC4J.

1.4.4.2 Running SQL Scripts