Administer > Deploy > Deploying customized assets
Customized WebSphere Commerce Web server assets
If you customize or change the WebSphere Commerce Web server, package and deploy the changed assets. Packaging the Web server assets involves how the Web server finds assets, where to store the assets, and packaging the assets. You can then deploy the Web server assets using the partial application update procedure within WebSphere Application Server.
- Package custom Web server assets
Packaging Web server changes for deployment can be divided into different phases: how the Web server finds assets, where to store the assets, and packaging the assets.
- Deploy custom Web server assets
The method for deploying custom Web server assets depends on where static Web assets are stored.
- Validate changes have been deployed for a custom Web server
Once you have deployed the custom Web server assets, you should validate that the changes have been successfully deployed.
- Update static Web assets to a remote Web server
Several tools in the WebSphere Commerce, such as Administration Console, allow you to add or change content in the enterprise application. Store publishing, for example, adds assets such as JSP files, property files, image files, and so on. These assets are made available to either the application server or the Web server. If the Web server is on the same system as the enterprise application, the assets are readily available to the Web server. If the Web server is on a system remote from the enterprise application, then transfer the static Web assets.
Related tasks
Package custom Web server assets
Deploy custom Web server assets