Develop > Controller layer > Management Center Web application
Management Center Web application file locations
A list of the files in the Management Center Web application, indicating which files you can extend.
Names and descriptions of files in the Management Center Web application. In the WebSphere Commerce development environment, these files are found in the LOBTools project. In the WebSphere Commerce Server environment, these files are found in the LOBTools.war Web module.
Directory path and file name Description Extension file /index.html The main HTML file that launches the Management Center client. This HTML file automatically loads when the URL... https://hostname:8000/webapp/wcs/cmc
...is loaded in a browser.
No /ManagementCenter.swf The compiled Management Center code in a Flash binary. This is the Flash application loaded by the index.html file. No /jsp/commerce/foundation/*.jsp All JSP files that have been provided by the shell. These are JSP files that are used by the Management Center client to return data required by facilities provided by the shell. No /jsp/commerce/component/*.jsp Where component is one of catalog, foundation, marketing, promotion, or shell.
All JSP files that return Management Center objects for a component. These JSP files are for component specific function. Only files that are not contained in the restricted folder. /jsp/MyCompany/component/*.jsp Where MyCompany is the name of the company and component is the name of the custom component.
User-created JSP files that return Management Center objects for a custom component. Yes /WEB-INF/web.xml The Web module configuration that declares the Struts servlet configuration. This Web module configuration picks up a new Struts configuration each time that a new tool with new URLs is added. No /WEB-INF/struts-ibm-foundation.xml The IBM predefined URLs for any URL that is required by the shell. No /WEB-INF/struts-ibm-tools.xml The IBM predefined URL mappings required for the tools that are part of the Management Center. This file only contains URL mappings for the tools and is separate to distinguish URL mappings for tools that could be customized from URL mappings required by the shell that should not be customized. No /WEB-INF/struts-extension.xml The Struts configuration file for customization. Use this file to add custom URL mappings. This file is initially empty and takes precedence over all Struts configuration files. Yes /WEB-INF/src/lzx/commerce/component Where component is one of...
- catalog
- foundation
- marketing
- promotion
- shell
The source directory that holds component specific Management Center code. Only files that are not contained in the restricted folder. /WEB-INF/src/lzx/commerce/component/images Where component is one of...'
- catalog
- foundation
- marketing
- promotion
- shell
Images used for the Management Center client user interface. No /WEB-INF/src/lzx/MyCompany/component Where MyCompany is the name of the company and component is the name of the custom component.
The directory for custom Management Center source code. Yes /WEB-INF/src/lzx/MyCompany/component/images Where MyCompany is the name of the company and component is the name of the custom component.
The directory for custom images used by Management Center extensions that must be compiled into the Flash binary file. Yes /WEB-INF/config/com.ibm.commerce.componentname/wc-componentname-clientobjects.xml Where componentname is the name of the component.
The Management Center object definition files that contain information used to map URL requests to BOD requests and vice versa. These XML files conform to the definition in the url-to-oagis.xsd file. No