Building resource extensions

To build extensions to application resources, you must rebuild the resources.jar file by running the deployer.sh (or deployer.cmd on Windows) utility from the INSTALL_DIR/bin directory. For example:

./deployer.sh -t resourcejar

This applies to all application resources, including:

To incorporate your JSP or JS file modifications, rebuild the Selling and Fulfillment Foundation EAR.

If you are extending any resource XML files, place your extended *.xml files in the <INSTALL_DIR>/extensions/global/template/resource folder.

If you are extending any event.xml files, place your extended *.xml files in the <INSTALL_DIR>/extensions/global/template/event folder.

If you are extending an *.xsl file, place your extended .xsl files in the <INSTALL_DIR>/extensions/global/template/xsl folder. But when providing the name of the template.xsl file during service definition, the path should be /global/template/xsl/<CUSTOM-TEMPLATE-XSL>.

Ensure that all the extended JSP and JS files are stored in the <INSTALL_DIR>/extensions/global/webpages directory, if they are not already there.

Customizing resource bundles

You can define new bundle entries and override out-of-the-box bundle entries.

Server side bundle files are located in the <INSTALL_DIR>/resources directory. To change bundle files, add or override the appropriate entries in the <INSTALL_DIR>/extensions/global/resources/extnbundle.properties file.

For example, you can add a new entry such as Detailed_Description=Detailed Description key-value pair as follows:

  1. Add the key-value pair to the <INSTALL_DIR>/extensions/global/resources/extnbundle.properties file.
  2. Build resources.jar.
  3. Build the EAR.