Stages of deploying customized assets
Stage 1: Package
The first stage is twofold: compiling and then packaging:
- Compiling involves taking source from your source code management system, and building or compiling it into the binaries that are required by the target server environment.
For example, you can take your .java files and compile them into .class files.
- Package involves taking the output of the build process and creating deployment packages for your target environment.
For J2EE assets, the format of your packaging will vary depending on the type of objects: a single file, a partial application, or an entire module.
Stage 2: Deployment
In this stage, the deployment packages are actually deployed to the target server environment. This process makes the assets created in the build process ready to be executed in the target environment. Each target environment will have a set of tools that are used to deploy of the packages.
Related concepts
What's changed for deploying customized assets
Package custom database assets
Deploy custom database assets
Package custom J2EE assets
Deploy custom J2EE assets
Package custom Web server assets
Deploy custom Web server assets
Minimize downtime during deployment
WebSphere Commerce deployment checklist
Top 10 tips to ensure a successful deployment of WebSphere Commerce
How to increase your success with WebSphere Commerce deployment
Additional deployment resources