Ticket #2106 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

Deploy and undeploy scripts Site modification

Reported by: gpotts Owned by: sbortman
Priority: highest Milestone: OMAR Dec 2010
Component: omar Version: OMAR 1.8.8
Severity: blocker Keywords:
Cc:

Description

Site modifications were performs to add grails scripts for tomcat deployment and undeployment. We will use these as guidelines ut we will see if the tomcat plugin already supports deployment and undeployment and add whatever scripts are missing. The current snapshot of these are attached as jpeg images.

Attachments

DeployUndeployScripts-1.jpg Download (142.1 KB) - added by gpotts 3 years ago.
DeployUndeployScripts-2.jpg Download (141.4 KB) - added by gpotts 3 years ago.
DeployUndeployScripts-3.jpg Download (146.3 KB) - added by gpotts 3 years ago.

Change History

Changed 3 years ago by gpotts

Changed 3 years ago by gpotts

Changed 3 years ago by gpotts

Changed 3 years ago by gpotts

  • owner changed from sbortman to gpotts
  • status changed from new to assigned
  • version changed from OMAR 1.8.6 to OMAR 1.8.8
  • milestone changed from OMAR Sep 2010 to OMAR Dec 2010

Changed 3 years ago by gpotts

  • owner changed from gpotts to sbortman
  • status changed from assigned to new

Changed 3 years ago by sbortman

  • status changed from new to assigned

Changed 3 years ago by sbortman


Description:

An admin wants a script to generate a war and deploy/undeploy OMAR to a tomcat server. The server could be local or remote.


Design:

There is a mechanism in place already that lets you deploy/undeloy a grails based war file to a tomcat server. The scripts provided by site are a bit too specific to their environment. Will need to "genericize" it a bit.


Risks:

None.


Unit test:

From the OMAR source tree, run the script against a local Tomcat instance that does not have OMAR installed on it. Navigate to the web address to which OMAR was published and verify that it responds with the login page.

Run the undeploy script against the same local Tomcat instance. Verify that OMAR is no longer deploy at the published address (should receive a 404 error).

Repeat the steps above with a remove OMAR instance.

Changed 2 years ago by sbortman

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.