Understanding Default Deployment Names Understanding Application Naming Requirements

Preparing Applications and Modules for Deployment 3-3 ■ For an exploded archived Web application, in the absence of WEB-INFweb.xml descriptor, the name of the directory should have a .war suffix. ■ For an exploded archived Enterprise application without a META-INFapplication.xml descriptor, the directory should have an .ear suffix. Within the application, the directory of exploded Web module should have a .war suffix. Similarly, the exploded EJB module should have a .jar suffix and the exploded RAR module should have a .rar suffix. ■ If an exploded Enterprise application contains no META-INFapplication.xml descriptor, the order in which modules are deployed is undefined and is dependent on the underlying File.listFiles method order. To ensure a specific order in which modules are deployed, you must add an application.xml descriptor and list the modules in the desired order.

3.1.3 Creating an Exploded Archive Directory from an Archive File

If you have an archive file that you want to deploy as an exploded archive directory, use the jar utility to unpack the archive file in a dedicated directory. For example: mkdir myapp cd myapp jar xvf distmyapp.ear If you are unpacking an archive file that contains other module archive files for example, an Enterprise application or Web Service that includes JAR or WAR files and you want to perform partial updates of those modules, you must expand the embedded archive files as well. Make sure that you unpack each module into a subdirectory having the same name as the archive file. For example, unpack a module named myejb.jar into a myejb.jar subdirectory of the exploded Enterprise application directory.

3.2 Understanding Default Deployment Names

When you first deploy an application or standalone module to one or more WebLogic Server instances, you specify a deployment name to describe collectively the deployment files, target servers, and other configuration options you selected. You can later redeploy or stop the deployment unit on all target servers by simply using the deployment name. The deployment name saves you the trouble of re-identifying the deployment files and target servers when you want to work with the deployment unit across servers in a domain. If you do not specify a deployment name at deployment time, the deployment tool selects a default name based on the deployment source files. For archive files, weblogic.Deployer uses the name of the archive file without the file extension. For example, the file myear.ear has a default deployment name of myear. For an exploded archive directory, weblogic.Deployer uses the name of the top-level directory you deploy. Note: If you want to use different subdirectory names for the archived modules in an exploded EAR file, you must modify any references to those modules in the application itself. For example, you must update the URI values specified in application.xml and CLASSPATH entries in the manifest.mf file. 3-4 Deploying Applications to Oracle WebLogic Server For Java EE libraries and optional packages, weblogic.Deployer uses the name specified in the librarys manifest file. If no name was specified in the librarys manifest file, you can specify one with the -name option. See the following section, Section 3.3, Understanding Application Naming Requirements for information on application naming requirements; See Chapter 6, Deploying Applications and Modules with weblogic.Deployer to specify a non-default deployment name.

3.3 Understanding Application Naming Requirements

In order to successfully deploy an application to WebLogic Server, the application name must be valid. Application naming requirements are as follows: ■ Application names must only contain the following characters: – a-z – A-Z – 0-9 – _ underscore – - hyphen – . period No additional characters are allowed in application names. ■ Application names that contain the . character must contain at least one additional different character; . and .. are not valid application names. ■ Application names must be less than 215 characters in length.

3.4 Understanding Deployment Version Strings