Name | Category and description |
Analysis. Administrators use this portlet to monitor all active My webMethods Server sessions. Administrators can also view the host name and IP address of logged in users and the node in the cluster to which they are logged in. | |
Tools. Administrators use this portlet to clear My webMethods Server caches, for example, the Resource Bundle Cache. An administrator might clear cache if it is not synchronizing properly. The administrator can also use the portlet to rebuild My webMethods Server user interface files, for example, some system JSP pages. | |
Administration. Administrators use this portlet to monitor the status of My webMethods Server in-memory caches. This information is useful when analyzing or troubleshooting memory footprint and performance issues with the My webMethods Server and Task Engine. | |
Configuration. Administrators use this portlet to search for CAF applications that are deployed to the current My webMethods Server instance. After locating a CAF application, the administrator can configure the run-time settings of the CAF application. | |
Configuration. Administrators use this portlet to view the results of a search for CAF applications that are deployed to the current My webMethods Server instance. Administrators can configure the run-time settings of the CAF application listed in the search results. | |
Configuration. Administrators use this portlet to configure, monitor, and control My webMethods Server in either a standalone or clustered deployment. | |
Administration. Administrators use this portlet to migrate content from one My webMethods Server to another, for example from a staging server to a production server. | |
Content. Administrators use this portlet to manage content services. Content services define the storage locations where content published to My webMethods Server is physically stored. | |
Administration. Administrators use this portlet to manage database connections for My webMethods Server. | |
Administration. Administrators use this portlet to configure connections for the SMTP server that My webMethods Server uses to send outgoing e-mail messages. Administrators can define one or more SMTP servers. When administrators define multiple SMTP servers, My webMethods Server load balances the traffic among all accessible servers. | |
Administration. Administrators use this portlet to install and uninstall My webMethods Server components, that is, portlet applications and web applications. This portlet displays the components that are available for installation, as well as, those already installed so that an administrator can select to uninstall them. | |
User Interface. Administrators use this portlet to configure the default My webMethods Server system locale. Additionally, using the Locale Rules portlet that is embedded in the Locale Administration portlet, administrators can configure locale rules. | |
Administration. Administrators use this portlet to configure My webMethods Server logging without restarting the My webMethods Server. From this portlet administrators can change the server-side logging categories and specify the threshold of the log messages that My webMethods Server is to log. | |
Administration. Administrators and page developers use this portlet to view the most recent messages written to the My webMethods Server log files. | |
Tools. Administrators use this portlet to manage portal renderers. The portlet lists all registered portal renderers and allows administrators to edit them. Additionally, administrators can create new UsePortlet portal renderers. | |
Administration. Administrators use this generic portlet to configure simple rules for any target. For example, My webMethods Server uses specific instances of the Rules Administrationportlet for configuration of Skin and Shell rules. | |
Administration. Administrators use this portlet to configure and manage existing, recurring events. The recurring events are events that other portlets registered when they were installed. | |
User Interface. Administrators use this portlet to create, edit, delete, import, and export shells. Additionally, the administrator uses this portlet to define the system default shell, which is the fallback shell to use when no shell rules are matched. | |
User Interface. Administrators use this portlet to edit the properties of a shell. Administrators can change a shell's name, description, and the parent shell. Additionally, administrators can change individual sections of the shell, such as, the header, footer, left navigation, right navigation, and the title bar. | |
User Interface. Administrators use this portlet to create, edit, delete, import, and export skins. Additionally, the administrator uses this portlet to define the system default skin, which is the fallback skin to use when no skin rules are matched. | |
User Interface. Administrators use this portlet to edit the properties of a skin, specifically the skin's colors, fonts, and images. | |
Configuration. Administrators and developers use this portlet to view general system and session information. The portlet displays My webMethods Server system information and information about the current session in the following categories: Request, Session, and Application. | |
Configuration. Administrators use this portlet to enable Universally Unique Identifier (UUID) resolution and to update the UUID attribute value for directory service users in My webMethods Server. In addition, you can use the Cleanup_InvalidUsers utility in this portlet to remove invalid users and memberships of invalid users from roles in My webMethods Server. | |
Administration. Administrators use this portlet to set up an unlimited number of webspaces for the My webMethods Server taxonomy. You can define webspaces if you want to provide URLs for My webMethods Server pages that users can bookmark and that are more descriptive. |