English

How To: Configure WebSphere 4.0.3 for jspviewer sample on HP-UX

Summary

If you wish to use the jspviewer sample, you must configure your Web server.

Procedure

  1. Start IBM HTTP server by navigating to <IBM HTTP Server Installation Directory>/bin. Type:
    ./adminctl start
    ./apachectl start
  2. Make sure IBM WebSphere Application server is running. If not, start the server by navigating to <WebSphere Installation Directory>/AppServer/bin. Type:
    ./startupServer.sh
  3. Start the WebSphere Advanced Administrative Console by navigating to <WebSphere Installation Directory>/AppServer/bin. Type:
    ./adminclient.sh
  4. On the left sidebar, expand the WebSphere Administrative Domain, Nodes, computer name and Application Server to make sure that the 'Default Server' is running. If not, right click on it and click Start.
  5. On the tool bar, click on Wizards > Install Enterprise Application. This opens the Install Enterprise Application Wizard.
  6. Select Install stand-alone module (*.war, *.jar). For Path, Browse and navigate to <ArcIMS Installation Directory>/Samples/Java/jspviewer.war.
  7. For Application Name, type: jspviewer
  8. For Context root for web module, type: /jspviewer
  9. Click Next and accept all the defaults until you reach the Completing the Application Installation Wizard page. Click Finish. This deploys the application.
  10. The JSP Samples are installed under installedApps inside the IBM WebSphere installation directory.
  11. Open the plugin-cfg.xml file located under <WebSphere Installation Directory>/AppServer/config
    Create a esri UriGroup if you don't have one:
    <UriGroup Name="esri">
    </UriGroup>
    Add the following to Route ServerGroup session if you don't have one.
    <Route ServerGroup="<server name>/Default Server" UriGroup="esri" VirtualHostGroup="default_host" />
    Add <Uri Name="/jspviewer/*" /> to the esri UriGroup session:
    <UriGroup Name="esri">
    <Uri Name="/jspviewer/*" />
    </UriGroup>
  12. Save and close the file.
  13. Stop and restart the Default Server.

Related Information