In addition to the -export and
-deploy options, the
AppManage utility allows you to use:
You can use the AppManage utility to upload an EAR file into an administration domain. Specifying the
-upload option is identical to importing an EAR in the TIBCO Administrator GUI. The application is loaded, but no deployment options are specified and the application is not deployed.
You can upload an EAR file and a deployment configuration file into an administration domain and not deploy the application. The -config option uploads the EAR file and the deployment configuration file, but does not deploy the application. You can omit the
-ear option if the EAR file is already loaded in the domain.
You can use the AppManage utility to start an application and all its associated processes, or use the utility to start just one service. The
-service tag takes the name of a service. Each service contains a name. For example, if there is a TIBCO BusinessWorks service element
<bw name="BW Processes.par"> in a deployment configuration file,
-service takes the value "
BW Processes.par".
In the case where -binding is provided without
-service, all services in the application are started.
You can use the AppManage utility to stop an application and all its associated processes, or use the utility to stop just one service. The
-binding tag takes the name of a binding. Each binding contains a name. For example, if there is a binding element
<binding name="BW Processes"> in a deployment configuration file,
-binding takes the value "
BW Processes".
You can use the AppManage utility to break the lock held on the application by other users. This will result in loosing uncommitted changes by the other users.
By default, a newly generated deployment configuration file preserves the value in the original deployment config file. Use this option with the -export option to create a deployment configuration file that uses the values defined for global variables in the archive file, rather than the values defined for global variables in the original deployment configuration file.
Use this option with the -export and
-ear options to create a small deployment configuration file that only includes XML tags for options you have changed in the EAR file. XML tags are not generated for default options that have values, which have not been changed from their defaults. Options for which XML tags are not generated will use default values.
Use this option with the -export option to create a deployment configuration file that includes all possible XML tags. For example:
Use this option with the -export option to create a deployment configuration file that includes XML tags for all options. Certain options, such as machine tags will include values defined within percent (%%) characters that can be searched for and replaced. For example:
Use this option with the -export option to encrypt sensitive data in the exported deployment configuration file. You will be prompted to enter an encryption password. For example:
Also use this option with the -deploy or
-config option to upload a deployment configuration file whose sensitive data is encrypted with your custom password. You will be prompted to enter the encryption password that you specified when generating the deployment configuration file. For example:
Use this option with the -export option to encrypt sensitive data in the exported deployment configuration file using a properties file. The properties file contains the password encrypted using the
obfuscate utility (Refer to
TIBCO Runtime Agent Installation for more information about Obfuscate Utility). For example:
Also use this option with the -deploy or
-config option to upload a deployment configuration file whose sensitive data is encrypted with your custom password. To use this option, you must provide a properties file which contains the password encrypted using the
obfuscate utility when generating the deployment configuration file. For example:
This option allows you to change the transport setting for a given application. It is similar to the -batchMoveAppData option, but operates against a single application. If the application is within a directory, use a forward slash (/) to separate it from the application name. For an overview of this option, see
, Changing the Transport for Applications.
The -deployconfig option can be used to configure the application with a given XML file.
