Setting service configuration properties

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

About this task

The configuration for each service is stored in and accessible through the WebSphere Integrated Solutions Console. 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 exposed as custom properties. You might need to add additional properties with key and value as required, or you might want to remove properties that can be used with their default values or are no longer required.

Procedure

To set configuration service properties, proceed as follows:

  1. Select the appropriate WebSphere Integrated Solutions Console, depending on your environment:
    • If your portal runs standalone, use the local console.
    • If your portal is installed in a cluster, use the console of the deployment manager.
  2. Start the WebSphere Integrated Solutions Console by entering the following in the URL location field of a Web browser: 
    http://example.com:admin_port/ibm/console
    where example.com is the name of your server or node host name of your server when on z/OS® and admin_port is the port assigned to the WebSphere Integrated Solutions Console.
  3. In the navigation click Resources > Resources Environment > Resource Environment Providers.
  4. In the Resource Environment Providers page, make the appropriate selection, select the appropriate node or cluster from the scopes pull-down list, or uncheck the Show Scope selection drop-down check box and select one of the following options, depending on your portal environment:
    • If your portal is running as a single server, select Browse Nodes and select the node.
    • If your portal is installed in a cluster, select Browse Clusters and select the portal cluster.
  5. Select the service to which you want to make changes.
    Note: In the list the service names are preceded by a product prefix and a blank space. For example, the 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 as required:
    • Select a property and change its value.
    • Select one or more properties for removal.
    • Create a new property. If you create a new property, use java.lang.String as its type and do not mark the property as required. Otherwise you will not be able to delete it later.
  8. When you are done, click Save at the start of the page under Message(s).
  9. Click Save again when prompted to confirm your changes.
  10. If running a cluster configuration, replicate your changes to the cluster.
  11. Restart the server to make the changes become effective.

By alternative, you can also set the properties in the properties files and then enable them by using a configuration task.

Notes:
  • This option for setting service configuration properties is not available for all properties.
  • Changes to properties configuration files do not affect runtime properties until you run the configuration tasks described in the following procedure.
Proceed by the following steps:

  1. Locate the properties file for the appropriate Resource Environment Provider. The properties files are located in the directory wp_profile_root/PortalServer/config. If there is no default properties file for a Resource Environment Provider, for example, 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. Save the file in the directory wp_profile_root/PortalServer/config. Example: 
      wp_profile_root/PortalServer/config/DynamicContentSpotMappings.properties
  2. Edit the properties file and modify or add configuration properties as required. 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 WebSphere Portal properties files to take effect, run the following task from the wp_profile_root/ConfigEngine directory.
    • Windows: ConfigEngine.bat update-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password
    • AIX® Linux Solaris: ./ConfigEngine.sh update-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password
    • IBM i: ConfigEngine.sh update-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password
    • z/OS: ./ConfigEngine.sh update-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password
    For changes to Web Content Manager properties files, run the following task from the wp_profile_root/ConfigEngine directory.
    • Windows: ConfigEngine.bat update-wcm-service-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password
    • AIX Linux Solaris: ./ConfigEngine.sh update-wcm-service-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password
    • IBM i: ConfigEngine.sh update-wcm-service-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password
    • z/OS: ./ConfigEngine.sh update-wcm-service-properties -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password

Results

Your service configuration properties updates are now in effect.