Chapter 12: Using jagtool and jagant

export

Exports an entity to a J2EE format EAR, WAR, J2EE JAR, or RAR file, or to an EAServer format JAR file.

Local mode support: Yes.

Command line:

export [ connect-args | local-args ] [-dir dirname] [-jagjar true|false] \
   [-xmlconfig=true|false] [-emptycachetags=true|false] entity

Ant build file:

<jag_export [ dir=”dirname”] [ jagjar=”true|false”] 
[-xmlconfig=”true|false”] -[emptycachetags=”true|false”]
entity=”entity” />

Option	Description	Default	Required
connect-args \| local-args	Arguments to specify a connection to the server or to run in local mode. See “Local versus connected mode”.	-	Yes
`dir`	The directory where the file is created.	Current directory	No
`jagjar`	Export to a Jaguar JAR file rather than a J2EE archive file.	true	No
`xmlconfig`	When exporting a J2EE archive, whether to include the EAServer-specific sybase-easerver-config.xml file. See “Using EAServer configuration files in J2EE archives” for more information.	true	No
`emptycachetags`	When exporting a J2EE archive, whether to export a no-operation version of the EAServer partial page caching tag library with Web applications to allow portability to other J2EE application servers that do not support this tag library	false	No
entity	Entity identifier for the entity being exported.	-	Yes

Return value	Indicates
0	The command ran successfully; the result is true/success.
1	The command ran successfully; the result is false/failure.
2	The command did not run successfully; an exception was thrown.

This example exports the application named “estore” to a J2EE EAR file in the e:\temp directory:

Command line:

jagtool export -dir e:\temp Application:estore

Ant build file:

<jag_export dirname="e:\temp" entity="Application:estore" />

This example exports the SVU package to a JAR file in the current directory:

Command line:

jagtool export -jagjar true Package:SVU

Ant build file:

<jag_export jagjar="true" entity="Package:SVU" />