generate_manifest_json
SYNTAX:
generate_manifest_json [options] [ear_location] [manifest_location]
|
Creates a
manifest.json or ear from EAR file.
Arguments: - manifest_location or ear_location - The destination folder that contains the created
manifest.json or
ear file.
- ear_location - The location of the EAR file
Options:
- -project - Name of the project for which the
manifest.json file is created. - -ear - Use this flag to generate a new EAR file from an EAR file created on earlier versions of TIBCO Business Studio for BusinessWorks.
|
system:export
SYNTAX:
system:export [options] [projects] [output folder]
Alternatively, you can use the
export command.
EXAMPLE:
export -ear test2.application -removeunused -path D:\Samples
|
Exports BW artifacts from the specified projects in the workspace to a folder. The artifacts can be ZIP or EAR files.
Arguments:
- projects - The name of the project(s) to export, separated by commas, for example, project[,project]*., Must specify at least one project. BW Applications can be exported as EAR files.
- -path -This flag is used to give an output or destination folder, where the content is exported. Defaults to local folder.
Options:
- -alsomoduleproperty - This parameter adds the module property in a property file.
- -bin, -binary - Export shared model as binary shared module. Can be used with the -zip option. Cannot be used with
-ear option.
- -cxf <CXF_Project_Name> - This command must be executed in the workspace where the CXF project exists. It installs the custom XPath function project into the TIBCO_HOME.
- -e, -ear - Export application as a deployable ear file (default). Can be used with application projects. Cannot be used with module projects.
- -force - Export the BW Application as an EAR file even though there are validation errors. By default, erroneous applications can be generated as ear files.
- --help - Display this help message.
- -includesystem - This parameter adds all the predefined properties in a property file. For example, BW.APPNODE.NAME
- -name [name] - Use the supplied name for the exported module.
- -noprofile - This parameter removes all the profiles from the EAR file.
- -pf {profile name} - Export the named profile of the given module. Multiple profiles can be exported by a comma-separated format.
- -pr {profile name} - Export the profile in property files. Multiple profiles can be exported by a comma-separated format.
- -removeunused - Exclude unused resources from the application when creating the EAR.
- -removediagraminfo - Removes process diagram information when creating the .EAR file.
- -substvar - Export the substvar file of a given profile to a given destination folder.
For example,
export -substvar {profile name} {application or module name} -path {path where substvar file should be exported} If no path is given, then the default path is taken.
- -t - This parameter tokenizes the property file if a project is deployed in
(Undefined variable: tci-bw-var.MAIN_PRODUCT_NAME_FIRST).
- -z, -zip - Export model as zip file. Cannot be used with -ear option.
- -dot - This parameter exports the profile using the dot separator.
|