Deploy customized assets
Stage 1: Package
- Compile: Take source from the source code management system, and compile it into the binaries required by the target server environment. For example, can take .java files and compile them into .class files.
- Package: Take the output of the build process and create deployment packages for the target environment. For J2EE assets, the format of the packaging will vary depending on the type of objects:
- single file
- partial application
- entire module
Stage 2: Deploy
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.
See also
- What's changed for deploying customized assets
- Customized WebSphere Commerce database assets
- Customized WebSphere Commerce EAR assets
- Customized WebSphere Commerce Web server assets
Related concepts
What's changed for deploying customized assets
Related tasks
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
Related reference
Minimize downtime during deployment
WebSphere Commerce deployment checklist
Top 10 tips to ensure a successful deployment of WebSphere Commerce
How to increase the success with WebSphere Commerce deployment