Management Center web application file locations
The files that are used to define the Management Center web application are found within the LOBTools web project for IBM WebSphere Commerce Developer environments. In other WebSphere Commerce environments, these files are within the LOBTools web module.
The Management Center web application includes the following types of files.
Notes:
- All paths are relative to the workspace_dir\LOBTools directory within an IBM WebSphere Commerce Developer environment.
- The directory mycompany represents the name of the directory where you include your custom files. For example, you can replace the name mycompany with the name of your company.
- The directory component represents the name of a Management Center component, such as catalog, shell, or marketing.
| Directory or file path | Description | Customizable files |
|---|---|---|
| WebContent\index.html | The main HTML file that launches the Management Center client. | No. |
| WebContent\WEB-INF\src\xml\commerce\component | Definition files that are related to the tool or overall user interface for the specific
Management Center component. This directory also includes the subdirectories that include the component-related definition files. |
Only files that are not included within restricted directories. |
| WebContent\WEB-INF\src\xml\commerce\component\restricted Note: Depending
on the component, there can be subdirectories within the restricted
directory. |
Definition files that are related to the tool or overall user interface for the specific Management Center component. These files define objects and features that are provided by default and the files can be replaced when you apply maintenance of upgrade WebSphere Commerce. Do not add or modify files within these directories or any subdirectories. | No. To override files in these directories, create replacement versions of the files in custom WebContent\WEB-INF\src\xml\mycompany\component directories. |
| WebContent\WEB-INF\src\xml\commerce\component\listViewDefinitions | All list view definition files for the component. | Only files that are not included within restricted directories. To override restricted files, create replacement versions of the files in custom WebContent\WEB-INF\src\xml\mycompany\component\listViewDefinitions directories. |
| WebContent\WEB-INF\src\xml\commerce\component\objectDefinitions Depending on the component, this directory can include subdirectories for object definition files that are specific to an object type that belongs to the component. For example, the objectDefinitions directory for the promotion component includes subdirectories for definition files that are specific to promotion elements and to promotion types. |
All object definition files and validator definition files for the component. | Only files that are not included within restricted directories. To override restricted files, create replacement versions of the files in custom WebContent\WEB-INF\src\xml\mycompany\component\objectDefinitions directories. |
| WebContent\WEB-INF\src\xml\commerce\component\searchDefinitions | All search definition files for the component. | Only files that are not included within restricted directories. To override restricted files, create replacement versions of the files in custom WebContent\WEB-INF\src\xml\mycompany\component\searchDefinitions directories. |
| WebContent\WEB-INF\src\xml\commerce\component\propertiesViews
Depending on the component, this directory can include subdirectories for property files that are specific to an object type that belongs to the component. For example, the propertiesViews directory for the marketing component includes subdirectories for property files that are specific to the activity builder and to customer segments. |
All properties view definition files for the component. | Only files that are not included within restricted directories. To override restricted files, create replacement versions of the files in custom WebContent\WEB-INF\src\xml\mycompany\component\propertiesViews directories. |
| WebContent\WEB-INF\spring-ibm-component.xml | The IBM predefined URL mappings that are required for Management Center. These files contain only the URL mappings for the component. | No. Include any custom Spring configurations within the spring-extension.xml file. |
| WebContent\WEB-INF\spring-extension.xml | The Spring configuration file for customization. Use this file to add custom URL mappings. This file is initially empty and takes precedence over all Spring configuration files. | Yes. Include all custom Spring configurations within this file. |
| WebContent\WEB-INF\web.xml | The web module configuration that declares the Spring servlet configuration. This web module configuration picks up a new Spring configuration each time that a new tool with new URLs is added. | No. |
| WebContent\WEB-INF\config\com.ibm.commerce.component\wc-component-clientobjects.xml | The business object definition files that contain information that is used to map URL requests to BOD requests. | No. To override files in these directories, create replacement versions of the custom wc-component-clientobjects.xml files in custom WebContent\WEB-INF\config\com.mycompany.commerce.component directories. |
| WebContent\images | All images that display in the Management Center user interface. For example, toolbar and menu icons, object icons, and icons that are used in building activities and price rules. | Only files that are not included within restricted directories. To override restricted files, create replacement versions of the files in custom WebContent\images\mycompany\component directories. |
| WebContent\jsp\commerce\component | All JSP files that are used in Management Center for the component. | Only files that are not included within restricted directories. |
| Java Resources\src\com.commerce.component.client.lobtools.properties | All properties files and resource bundle files for defining Management Center text. | No. To override files in these directories, create replacement versions of the files in custom Java Resources\src\com.mycompany.component.client.lobtools.properties directories. |
JSP file naming conventions
- JSP files for search
- JSP files that are used for search follow this syntax: FindobjectType.jsp. For example, FindProduct.jsp, or FindActivity.jsp.
- JSP files for locating a single object
- JSP files that are used to locate a single object follow this syntax: GetobjectType.jsp. For example, GetMasterCatalog.jsp, or GetPromotion.jsp.
- JSP files for locating child objects
- JSP files that are used to locate child objects follow this syntax: GetobjectTypeChildren.jsp.
- JSP files for locating reference objects
- JSP files that are used to locate reference objects follow this syntax: GetobjectTypeReferences.jsp. For example, GetCatalogGroupReferences.jsp, or GetCatalogGroupReferences.jsp.
- JSP fragment files for serializing objects
- JSP fragment files that are used to serialize objects follow this syntax: SerializeobjectType.jspf. For example, SerializeCatalogEntry.jspf.