Administer > Deploy > Deploying customized assets > Customized WCS EAR assets
Package custom J2EE assets
Overview
J2EE applications are delivered as EAR files, which are JAR files with special deployment descriptors for passing information about the application to an application server.
Enterprise applications are divided into smaller parts:
- *.ejb modules
- *.war files
- *.jar logic or utilities
- *.rar connector modules
struts-config-ext.xml
If you edit struts-config-ext.xml, add it to the source code management system and package it along with other changed files. As store identifiers in the development environment, quality assurance environment, and production environment can be different, be sure to set store identifiers to match the target environment. After completing this, you can deploy the changes.
For more information about struts-config-ext.xml, see...
WCS assets and WAS deployment packages
Package WCS assets in a format compatible with WAS. You can combine the packaging options; for example, if you have updates for EJB files and JSP files, you can build two deployment packages:
- EJB module JAR file
- partial application ZIP file
WAS provides an option to replace the entire EAR file with a new version; however, this option is not supported for WCS.
All packaging options assume you are packaging from the WCS development environment.
WAS package types
Package method Description Explanation Single file Any single WCS asset:
- *.jar file containing...
- Controller commands
- Data beans
- Utility classes
- Store assets...
- JSP files
- HTML files
- Configuration XML files
- Images
- Properties files or resource bundles
Use if you only have updates for a single file in the application. The file must not be a module file such as an EJB module or Web module. The file can be inside any module of the application. For example, if you have changes to an XML file, use package as a single file.
If you are working with several single files, package and deploy the files as a partial application. A partial application deployment requires the application to be down and restarted only once, not once per file.
A single file is any one file within the EAR during deployment.
The single file can be a JAR file, which contains several command, data bean, or Java code changes. As long as these are packaged as a single JAR file for the EAR, then this is considered a single file deployment.
If the single "file" is a WAR file, EJB module, or other module, you should not use this option; use the "Module file" instead.
Partial application More than one of the WCS assets described in the "Single file" option. Use to update or delete several files in the application as defined in the single file method on the "Single file" option. The group of files do not have to be in the same module. You would typically use this option to update the follow types of files:
- Configuration files (not J2EE deployment descriptors)
- JSP files
- Images
- Utility JAR files
If you are working with several files, package and deploy as a partial application, as a partial application deployment requires the application to be down and restarted only once, not once per file.
If you deploy as a partial application, WAS adds a file if it does not already exist in the application, updates a changed file if the file exists, or deletes a file if the file matches something in the ibm-partialapp-delete.props file.
Module file An entire module, typically an EJB module. Use this option to:
- Add, update, or delete a new module in the application. To deploy more than one module, use this option multiple times
- Update an entire EJB module
- Deploy Management Center (packaged as *.war)
- Update changes to the deployment descriptors
See also
- Package commands, data beans, or Java classes for deployment
- Identify and packaging J2EE assets for a single file
- Package J2EE assets for a partial application
- Package J2EE assets for an entire module
Next topic: Deploy custom J2EE assets
Related tasks
Package commands, data beans, or Java classes for deployment
Identify and packaging J2EE assets for a single file
Package J2EE assets for a partial application
Package J2EE assets for an entire module
Deploy custom J2EE assets
Validate changes have been deployed for a custom EAR file
Related reference