WebSphere Commerce Developer tools, plug-ins, and utilities
The WebSphere Commerce development environment provides plug-ins and tools.
The following plug-ins are provided with the WebSphere Commerce development environment:
- Compiling JavaServer Page files
Compiling the JavaServer Page (JSP) files in the site or store will significantly reduce the amount of time needed to load the store. As a result, IBM recommends that you batch-compile the store or site JSP files after publishing a store archive and after deploying JSP files to a production environment.- enableContentManagement
The development environment is not meant to be an authoring environment. Support is provided in the environment for customization purposes only. For example, to test changes to the content management functionality. The ability to propagate changes is not available. To change the content management workspaces, we cannot publish the changes out to another database.- restClassicSampleGen
The restClassicSampleGen utility automates the creation of mapping files with the configuration-based controller command and data bean mapping framework.- startWCServer
The startWCServer utility starts the Transaction (server1), Search, Store, and CustomizationWebSphere Commerce test servers in WebSphere Commerce Developer.- startWCToolkit
The Start WebSphere Commerce Developer (startWCToolkit) utility starts WebSphere Commerce Developer.- stopWCServer
The stopWCServer utility stops the WebSphere Commerce Developer test servers: Transaction (server1), Search, Customization, and Store.- xmlfMig
The xmlfMig utility updates the contents of the xmlfFileList.txt file and changes the file extensions of the listed XML files to XMLF. It also creates a backup of the existing file by appending a BAK extension.- setdbtype
After you install WebSphere Commerce Developer, we must run the setdbtype command to point the WebSphere Commerce Developer Version 9.0 environment to your restored database.- wcs_xpathkey
The XPath key generator command-line utility, wcs_xpathkey.bat, takes an XPath expression as input and generates an XPath key. This key is used to locate the XPATH_TO_SQL_STATEMENT template in the query template file.
Related concepts
WebSphere Commerce development environment
WebSphere Commerce common architecture