Skip directly to searchSkip directly to the site navigationSkip directly to the page's main content

Data Admin System Documentation - Application Deployment

This page discusses the options on how to deploy the IBIS-PH Data Administration System. Listed below are some of the options:

NOTE: Deploying the application is relatively simple once the application web archive is created (file named something like: ibisph-admin.war). This section of the documentation does NOT cover how to build this "war" file. Since each deploying agency will have it's own site specific files they will either keep their files in the Utah repository and do a build from there or will have their own repository for their files and will have their own build process.

The following assumes that the correct .war file exists or that the appropriate files that comprise the application are managed and known to the system administrator who is doing the deployment.

  • Place the "ibisph-admin.war" file into the Java web application server's "webapps" directory (or the directory that has been setup by the system administrator). For servers that do not have "hot" deployment enabled (which should be the case for most production environments) the app server will need to be restarted before the app will be installed and recognized.
  • Manually create the app directory (typically named "ibisph-admin"). The directory is typically stored under Java web server's "webapps" directory but may reside anywhere based on how the app server is setup. Once a directory is established simply unzip the ibisph-admin.war file's contents to this location. Again the app server will likely need to be restarted depending on how it is configured.
  • A variation on the above method is to check out the appropriate files from the IBIS repository and manually copy them to the directory.
  • The easiest way to deploy the application is if the app server has system administration application installed. Every known app server has one of these available but not all system administrators install them for security reasons. If one is installed simply follow the wizard for application installation.

If hot deployment or when using an app server deployment tool, the META-INF/context.xml file will likely setup the web app's context which includes a JNDI JDBC lookup. See the internal documentation contained withing META-INF/context.xml type files for more information.

Depending on how the application server is configured and what path is desired for the IBIS-PH Data Admin application, the app server's server.xml configuration file might need to be modified to add a custom context for the application. This of course would also require an app server restart.

An ant XML build file is available in the repository that enables the Java class files to be compiled and which can produce an appropriate, deployable .war file. However, it should be noted that as of 7/2007 that this file is specific to the Utah fileset.

The information provided was retrieved on: Sat, 25 May 2019 12:31:43.

Content updated: Wed, 4 Nov 2015 09:26:28 MST