Administer > Deploy > Deploying customized assets > Customized WebSphere Commerce Enterprise Application (EAR) assets > Deploying custom Java EE assets


Deploy J2EE assets for a single file

This option provides the ability to deploy a single file asset into the J2EE application

Note that this option should not be used if this single file is a J2EE module. J2EE modules must be deployed as an entire module.

You will use this option to deploy any single assets such as:

If you are deploying more than one file, it is best to group the files together and use the partial application procedure. This will be faster than doing several single file updates.

Consider the following scenario: a problem has been found in a JSP file. The developer has made the change and tested it in the development environment. The functional tester has also validated the change in the quality assurance environment. It is now time to deploy the changed file into the production server. Note that regardless of whether you use the graphical or scripting tools, always back up the J2EE assets before you deploy.


Procedure


Related tasks

Deploy custom J2EE assets

Validate changes have been deployed for a custom Enterprise Application (EAR) file

Related reference

Troubleshoot: Deployment


+

Search Tips   |   Advanced Search