Deactivate (disable) a deployed archive

When you deactivate (disable) a deployed Genero Archive (gar) file, the applications and services provided by the archive are not exposed (no longer available to users).

As a prerequisite, you have a deployed Genero Archive (.gar) file that has been enabled.

Disabling an archive means disabling all applications and services provided by the Genero Archive (.gar) file. The archive remains deployed. Any running applications or services are not stopped.

Tip: To disable a single application or service, remove its configuration file from the group directory. The original configuration files remain available in the deployed archive directory.

Enter the gasadmin command with the appropriate arguments.

To disable a Genero Archive (gar) file named fuzzy.gar:

gasadmin gar --disable-archive fuzzy.gar

By default, the results are output in text format. When the console output uses the form of an XML document, it can be easier to parse by other applications than textual output. To output in XML, specify the --xml-output option:

gasadmin gar --disable-archive fuzzy.gar --xml-output

The exit status is a 0 (zero) in case of success, 1 in case of error.

XML output examples:

<DEPLOYMENT success="TRUE">
  <MESSAGE>Archive <archive-name> successfully undeployed</MESSAGE>
</DEPLOYMENT>

<DEPLOYMENT success="FALSE">
  <ERROR>Failed to undeploy <archive-name> archive.</ERROR>
  <ERROR>... and error messages indicating the reasons of the failure....</ERROR>
</DEPLOYMENT>

What to do next:

You can reenable an archive that is deactivated (disabled) as described in Activate (enable) a deployed archive with gasadmin, or if instead you need to undeploy it, follow the instructions in Undeploy an archive with gasadmin.

Tip:

You can view a list of all deployed archives (activated and deactivated) with the gasadmin gar --list-archives command. For details, go to List deployed archives.