Reference Identifiers that are provided as part of the subcontributions within a tree.
Modules by profile
Use the Examine modules by profile
section to explore the modules of a specific profile. Select a profile in the Select Profile
screen and then advance to the Module Explorer to explore the modules in that profile.
The Select Profile
screen displays the themes and their profiles in the tree view and shows details on the selected branch in the details view. You can now learn more about the various artifacts that are installed in the system before you select a profile to examine.
The tree view also shows in parentheses which theme and profile is the default so this information is easily visible. All other information is shown in the details view, such as the location of the profile JSON file. The profile JSON file is an element that can be clicked and opens a new window and serves the resource right in the browser when clicked.
After you select a profile, the Module Explorer screen will display.
Use the Examine all modules
section to explore all modules available with the system, theme, or both. Select a theme or the system module branch on the Select Theme
screen and then advance to the Module Explorer.
The Select Theme
screen displays a system modules branch and all themes in the tree view. Select a theme to view more information about the various artifacts that are installed in the system before you decide on a theme and continue to the Module Explorer.
The module explorer displays the module hierarchy of your system in a split view. The tree view shows the module hierarchy, the details view shows details on the selected module from the tree view.
You can get to the module explorer from different paths in the UI.
- When you examine modules by profile, you have two root branches:
When you examine the system and theme modules, you have one or two branches:
- Modules: The root for all modules in the none deferred section of the profile.
- Deferred Modules: The root for all modules in the deferred section of the profile.
- System Modules: Contains all modules that are defined globally through a plugin.xml.
- Theme Modules: Contains all modules that are defined within the themes contribution folder as part of the JSON files. This branch is only shown when a theme is selected.
When you expand a tree or branch, if it is large and takes more than 30 seconds to expand, the expansion process is stopped. You must expand those branches individually.
The module hierarchy has three main views:
This view displays the root and a list of modules underneath as child branches. The child branches for each module then represent the prerequisite dependencies that each module defines. You can drill down until no prerequisites are defined. Therefore, within the tree various modules might display multiple times since they can be defined as a prerequisite for many different modules. Parent view of a selected branch
For example: The wp_toolbar module, which is referenced in the deferred profile, defines the dojo module as a prerequisite. Then, the dojo module defines the dojo_17 module as a prerequisite. When you look at the module explorer, you can drill down into the Deferred Modules section, which displays the wp_toolbar module. If you drill down further, you can see the dojo module is child of wp_toolbar and the dojo_17 module is child of the dojo module.
This view displays the parents of a module. The parent is a module that has a prerequisite of a child module. Module A has a prerequisite of module B, which means that B 's parent is A. It is useful to figure out who is using a specific module and verify whether the usage is correct.Child view of a selected branch
Note: The parent is displayed as a child branch within the view, the tree is upside down.
For instance: When you look at the wp_client_main module in the parent view, it has a child branch in the tree called wp_status_bar. Therefore, wp_status_bar is the parent of wp_client_main.
This view behaves identically to the complete hierarchy view except that it focused on a single branch as the parent. The dependencies of just this single branch are displayed.
The details view displays the details for the selected module such as:
- ID: Displays the module ID.
- Version: Displays the module version, if one was defined.
- Is system-module: Yes if the module is globally defined through a plugin.xml file.
- Is meta-module: Yes if the module does not contain any contributions, but instead contains only prerequisites.
- Is deprecated: Yes, if the module was deprecated.
- Location: Displays the file path for the module.
- Capabilities: Displays all capabilities for the module.
- Prereqs: Displays all prerequisites for the module.
- Parents: Displays all parent modules for the module
- Contributions: Displays all contributions by contribution and sub contribution. The resources are elements that can be clicked, which open a new window and serves the resource right in the browser when clicked.
Note: In simulation mode, the resources cannot be clicked.
Use the search bar to search the tree view and the details view for various information. The following search scopes are supported:
- Module Identifier: Search for a specific module by name. For example, wp_client_main.
- Capability: Search for the modules that are associated with a specific capability. For example, if you want to know which module provides the dojo capability. Then, you know which module you must add as a prerequisite for your own module.
- Reference Identifiers: Search for which dynamic content spot or module reference is exposed by which module.
Enter a term into the search field in the toolbar and press Enter or click the Find
icon. The found item is then highlighted for a short time with a yellow background. Pressing Enter again or clicking Find
icon again will find the next item. If no item is found, either a pop-up dialog opens to instruct you to start the search from the beginning or the background of the search field is marked in red.
Parent topic: Theme Optimization Analyzer for WebSphere Portal