This section contains information on the following subjects:
com.bea.wlevs.deployment.Deployer
is a Java-based deployment utility that provides administrators and developers command-line based operations for deploying WebLogic Event Server applications. In the context of WebLogic Event Server deployment, an application is defined as an
OSGi bundle JAR file that contains the following artifacts:
The configuration files must be located in the META-INF/wlevs
directory of the OSGi bundle JAR file.
The EPN assembly file must be located in the META-INF/spring
directory of the OSGi bundle JAR file.
MANIFEST.MF
file that describes the contents of the JAR.See Assembling a WebLogic Event Server Application: Main Steps for detailed instructions on creating this deployment bundle.
The Deployer utility uses HTTP to connect to WebLogic Event Server, which means that you must configure Jetty for the server instance to which you are deploying your application. For details, see Configuring WebLogic Event Server.
WebLogic Event Server uses the deployments.xml
file to internally maintain its list of deployed application OSGi bundles. This file is located in in the DOMAIN_DIR
directory, where DOMAIN_DIR
refers to the main domain directory correspoding to the server instance to which you are deploying your application. See Deployment XSD Schema for information about this file.
WARNING: | The XSD for the deployments.xml file is provided for your information only; BEA does not recommend updating the deployments.xml file manually. |
To set up your environment to use the com.bea.wlevs.deployment.Deployer
utility:
com.bea.wlevs.deployment.client_2.0.jar JAR
file, located in the WLEVS_HOME
/bin
directory where, WLEVS_HOME
refers to the main WebLogic Event Server installation directory, such as /beahome/wlevs20
.
Alternatively, you can later use the -jar
option at the command line to call this JAR file, such as:
prompt> java -jar /beahome/wlevs20/bin/
com.bea.wlevs.deployment.client_2.0.jar -url ...
It is assumed in the remainder of this section that you have updated your CLASSPATH and are going to call the com.bea.wlevs.deployment.Deployer
class directly.
Sometimes it is useful to run the com.bea.wlevs.deployment.Deployer
utility on a computer different from the computer on which WebLogic Event Server is installed and running. To run the utility remotely, follow these steps:
-jar
argument when you run the utility; set the argument to the NEW_DIRECTORY/
com.bea.wlevs.deployment.client_2.0.jar file, where NEW_DIRECTORY
refers to the directory on the remote computer into which you copied the required JAR file. When you use the -jar
argument, you do not specify the com.bea.wlevs.deployment.Deployer
utility name at the command line. com.bea.wlevs.deployment.Deployer
utility as described in the next section.
The syntax for using the Deployer utility is as follows:
javacom.bea.wlevs.deployment.Deployer
[Connection Arguments]
[User Credential Arguments]
[Deployment Commands]
The following sections describe the various arguments and commands you can use with the Deployer utility. See Examples of Using the Deployer Utility for specific examples of using the utility.
The following table describes the connection arguments you can specify with the Deployer utility.
The following table describes the user credential arguments you can specify with the Deployer utility.
The following table describes the deployment commands you can specify with the Deployer utility.
Starts an OSGI bundle which was previously installed to the specified WebLogic Event Server instance.
|
|
The following examples show how to use the Deployer utility. In all the examples, WebLogic Event Server is running on host ariel
, listening at port 9002
, and the username/password of the server administrator is wlevs/wlevs
, respectively. For clarity, the examples are shown on multiple lines; however, when you run the command, enter all arguments and commands on a single line.
prompt> java com.bea.wlevs.deployment.Deployer
-url http://ariel:9002/wlevsdeployer -user wlevs -password wlevs
-install /application/bundles/com.my.exampleApp_1.0.0.0.jar
The preceding example shows how to install an OSGi bundle called com.my.exampleApp_1.0.0.0.jar
, located in the /application/bundles
directory. The next command shows how to start this application after it has been installed:
prompt> java com.bea.wlevs.deployment.Deployer
-url http://ariel:9002/wlevsdeployer -user wlevs -password wlevs
-start exampleApp
Finally, the next example shows how to uninstall the application, which removes all traces of it from the domain directory:
prompt> java com.bea.wlevs.deployment.Deployer
-url http://ariel:9002/wlevsdeployer -user wlevs -password wlevs
-uninstall exampleApp