Identifying and packaging J2EE assets for a single file
Before you deploy your changed file, you first package it in a format that WebSphere Application Server understands. For a single file deployment, the packaging stage is more accurately described as identifying the changed file.
About this task
- Collect controller commands, data beans, or Java code
- Collect store assets
- Collect assets stored outside of the WebSphere Commerce development environment workspace
The result of this package is a single file exported or identified for deployment.
Collecting controller commands, data beans, or Java code
If you are deploying any number of controller commands, data beans, or Java classes, export and package the assets as a JAR file. You cannot deploy custom commands, data beans, and Java code unless the files are first packaged into a JAR file. If your controller commands, data beans, or Java classes span multiple JAR files, you must build a partial application that contains all of the JAR files.
Collecting store assets
If you are deploying store assets (JSP files, HTML files, images, property files, and other store assets), export the file from your WebSphere Commerce development environment: