Zip Get

ZipGet

zipget extracts a file from the specified zipfile and places it into the current DropZone. Unless it is subsequently removed, the file will be deployed to the appropriate Endpoint(s) in any subsequent transfer operation. WAR, JAR and EAR files are simply ZIP files with a different extension. You can thus use zipget (and zipadd and zipdel) with WAR, JAR and EAR files as well as with ZIP archives. This provides a powerful way of manipulating WAR, JAR and EAR files in the DropZone before onward deployment to the target Endpoints.

zipget is useful for extracting a file from a zip archive, modifying the file and then replacing the original version of the file in the archive with zipadd. You can use a combination of zipget and zipadd to manipulate XML configuration files that are embedded in a web archive.

zipget takes a mandatory named parameter. Other parameters can be specified depending on what is being extracted from the zipfile:

NOTE: You can call dir() on a DropZone File object representing a zipfile to return an array of DropZone File objects that you can then pass to zipget.

Example 1

Extract all the files in a zipfile:

// get a list of myapp.war files in the _DropZone_ (probably only one)

set warfilearr = ${_DropZone_.find("myapp.war")};

// Need to iterate since find returns an array keyed by filename.

// However, if there's only one "myapp.war", this will only execute once.

iterate(warfile: $warfilearr) {

// get list of files in myapp.war

set files = ${warfile.dir()};

// Now extract all those files

zipget(zipfile: "myapp.war", files: $files);

}

Example 2

Modify a configuration file within a WAR file

// Step 1 – extract web.xml from the WAR file

//

zipget(zipfile: "mywapp.war", file: "web.xml");

// Step 2 - Set the ODBC connection string to the correct value for

// the target _Environment_. Note DBSTRING will be on the stack and is

// _Environment_ specific.

//

modify(file: 'web.xml', modifier: "xml") {

set\_attribute(

xpath: "/web-app/context-param/[@param-name=DBConnectionString]/@param-value",

value: $DBSTRING);

}

// Step 3 – put the modified web.xml file back in the WAR file. Remove the

// modified file from the _DropZone_ so we don't end up deploying it.

//

zipadd(zipfile: "myapp.war", file: "web.xml", delete: true);