Standard portlets

For HATS standard portlets, if you allow overrides in the project settings, then the user can override connection parameters and global variables by selecting Personalize from the portlet menu on the toolbar and switching to edit mode.
Note:
HATS does not support portlet edit mode on WebSphere® Application Server. If you deploy your HATS standard portlet to run directly on WebSphere® Application Server, instead of using portlet edit mode, the user can override connection parameters and global variables in the URL used to access the portlet.

Once in portlet edit mode, a settings page is displayed for the user. This page allows the user to override connection parameter and global variable settings. These functions are equivalent to the HATS functions for Web applications that allow a user to override settings using the URL when the application is first accessed.

On the settings page, in the connection parameter section, the connection parameter drop-down lists the Host On-Demand session parameters that you allow to be overridden in the project settings. The user sets an override by selecting a parameter from the drop-down list, entering a value in the Value field, and clicking Add. By default, the override setting is enabled when first added. It can be disabled by selecting false from the Enabled drop-down. An override can be deleted by selecting the check box next to the parameter name and clicking Delete.

In the global variable section, the user sets an override by entering a global variable name and value, and clicking Add. After adding an override, the global variable can be identified as a shared global variable by selecting true from the Shared drop-down. By default, the override setting is enabled when first added. It can be disabled by selecting false from the Enabled drop-down. An override can be deleted by selecting the check box next to the global variable name and clicking Delete.

When the user clicks Save and Exit, the settings are saved in the portlet preferences.
Note:
  1. The values entered by the user are not validated.
  2. The user must disconnect and restart the portlet application before the new values take effect.
In addition to allowing users to set overrides, you can programmatically provide connection parameter and global variable overrides by extending the HATS JSR 286 or JSR 168 entry portlet, as appropriate. For more information, see the section, Extending the Entry portlet.
Note:
If you supply connection parameter or global variable overrides through the extended portlet class and the user provides the same overrides using portlet edit mode, then the values provided by the user in edit mode override the values you supply in the extended portlet class.
.