Deploying customization
The procedure to test customizations is provided in this topic.
Building your changes
Perform the following steps, if you want to test your customizations in the exploded
wscdev.war file.- Create a soft link for the extension files.
- Update the gulp configuration file (
ngstore.local.extn.config.json) to use the<WSCDEVWAR_FOLDER>and<EXTN_FOLDER>. - Run the gulp script (
ngstore_local_extn_gulp.js) to generate minified files, CSS files. - Test the application for your customizations.
Perform the following steps, if you want to test your customizations in your local or
central runtime:
- Place all you extension code inside
<INSTALL_DIR>/extensions/wsc/webpages/ngstorefolder. - Update the gulp configuration file (
ngstore.build.extn.config.json) to use<INSTALL_DIR>/extensions/wsc/webpages/ngstoredirectory. - Run the gulp script (
ngstore_build_extn_gulp.js) to generate minified files and CSS files. - Build and deploy the application WAR or EAR. For more information about rebuilding EAR files.
- Test the application for your customizations.
Testing your customization
- If you have modified client-side files such as JS, HTML, CSS and so on, ensure that the changes are available in the exploded war, clear cache, and reload the browser.
- If you have modified server-side files such as mashup XMLs, java code, or any other server-related files, you need to ensure that the changes are available in the exploded war and restart the application server.