When using WebSphere®, you can test the modifications that you have made to Sterling Selling and Fulfillment Foundation.
To configure WebSphere to run the application in exploded mode:
-Dsci.opsproxy.disable=Y
-Dvendor=shell -DvendorFile=/servers.properties
After deployment, any files copied to the <WAS_HOME>/AppServer/profiles/<PROFILE_NAME>/installedApps/<CELL_NAME>/<APP_NAME>/ directory can be modified as needed. For example, if you are extending a custom code written as part of the database extensibility, the custom code files can be directly moved to the appropriate directory under <WAS_HOME>/AppServer/profiles/<PROFILE_NAME>/installedApps/<CELL_NAME>/<APP_NAME>/ directory for testing. IBM calls this ability to modify and move files as needed "hot deployment."
The custom JSPs written as part of UI extensibility can be directly incorporated into the application WAR file.
For example, if you have some customizations in the Catalog module, add the files in the <WAS_HOME>/AppServer/profiles/<PROFILE_NAME>/installedApps/<CELL_NAME>/<APP_NAME>/smcfs.war/ycm directory.
If you modify... | In these files... | Then... |
---|---|---|
Startup parameters | properties | Restart WebSphere. |
UI extensibility | JSP, JavaScript, CSS, theme XML | Load dynamically. |
Localization literals | alertmessages and localization bundle files | Restart WebSphere. |
Database extensions | entity XMLs | Rebuild the entities.jar file. Include
the jar in the following directory:
Restart WebSphere. |
APIs and other template files | template XMLs | Rebuild the resources.jar file. Include the jar
in the following directory:
Restart WebSphere. |