Set service configuration properties

HCL WebSphere Portal comprises a framework of services to accommodate the different scenarios that portals need to address. Services are available for both HCL WebSphere Portal and HCL Web Content Manager. We can configure some of these services.

Set service configuration properties from the command line

We can set the properties in the properties files and then enable them by running a configuration task. This option for setting service configuration properties is not available for all properties. If a properties file is not available, set service configuration properties through the Resource Environment Provider.

If the portal is installed in a cluster, use this procedure on the primary node. The configuration task update-wcm-service-properties does not take effect on secondary nodes.

Changes to properties configuration files do not affect runtime properties until we run the ConfigEngine tasks

1. Locate the properties file for the appropriate Resource Environment Provider:

   • The properties files for HCL WebSphere Portal are in...
     wp_profile_root/PortalServer/config

   • The properties files for HCL Web Content Manager are in...
     wp_profile_root/PortalServer/wcm/shared/app/config/wcmservices

   If there is no default properties file for a Resource Environment Provider, for example, for WP DynamicContentSpotMappings, create a new properties file as follows:

   1. Create a properties file by using a text editor.

   2. Give the file the name of the Resource Environment Provider without the WP prefix. Example: DynamicContentSpotMappings.properties. Save the file in the appropriate directory for the Resource Environment Provider as given earlier.

2. Edit the properties file and modify or add configuration properties as needed. Example:
   newDynamicContent=res:/CustomThemeContext/themes/html/MyTheme/dynamicContent.jsp

3. Save the updated properties file.

4. Run the appropriate configuration task to update the configuration properties:

   For changes to HCL WebSphere Portal properties files to take effect...

   cd wp_profile_root/ConfigEngine
   ./ConfigEngine.sh update-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password

   For changes to Web Content Manager properties files...

   ./ConfigEngine.sh update-wcm-service-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password

Your service configuration properties updates are now in effect.

Set service configuration properties from the user interface

The configuration for each service is stored in and accessible through the dmgr. Each service is registered as a separate resource environment provider with custom properties that represent the service configuration. Initially in a default installation, only the most common properties are shown as custom properties. You might need to add more properties with key and value as required. Or we might want to remove properties that can be used with their default values or are no longer required.

1. Select the appropriate dmgr, depending on the environment:
   • If the portal runs stand-alone, use the local console.
   • If the portal is installed in a cluster, use the console of the deployment manager.

2. Start the dmgr:
   http://example.com:admin_port/ibm/console

3. Go to...
   Resources > Resources Environment > Resource Environment Providers

4. Select the appropriate node or cluster from the scopes list, or clear the Show Scope check box and select one of the following options, depending on the portal environment:
   • If the portal is running as a single server, select Browse Nodes and select the node.
   • If the portal is installed in a cluster, select Browse Clusters and select the portal cluster.

5. Select the service in which to change a property.

   In the list, the service names are preceded by a product prefix and a blank space. For example, the HCL WebSphere Portal configuration service is identified as WP ConfigService. The Web Content Manager configuration service is identified as WCM WCMConfigService.

6. Click Custom Properties.

7. Do one of the following tasks as needed:

   • To set a property, select that property and change its value.

   • If the property to set does not exist yet, create it new. When creating a new property, use java.lang.String as its type and do not mark the property as required. Otherwise, we might not be able to delete it later.

   • Select one or more properties for removal.

8. When we are done, click Save at the start of the page under Message(s).

9. Click Save again when prompted to confirm your changes.

10. For a cluster configuration, replicate your changes to the cluster.

11. Restart the server for the changes to become effective.

Your service configuration properties updates are now in effect.