Set 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. We configure some of these services.

The configuration for each service is stored in and accessible through the WAS console. Each service is registered as a separate resource environment provider with custom properties representing the service configuration. Initially in a default installation, only the most common properties are shown as custom properties. We 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.

To set configuration service properties:

1. Open the WAS console in a browser...
   http://example.com:admin_port/ibm/console

   ...and go to...

   Resources | Resources Environment | Resource Environment Providers

2. Select the appropriate node or cluster from the scopes list, or uncheck 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.

3. Select the service to which to make changes.

   The WebSphere Portal configuration service is WP ConfigService. The WCM configuration service is WCM WCMConfigService.

4. Click Custom Properties.

5. Do one of the following as needed:
   • Select a property and change its value.
   • Select one or more properties for removal.
   • Create a new property.

   If we create a new property, use java.lang.String as its type and do not mark the property as required. Otherwise, we may not be able to delete it later.

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

7. Click Save again when prompted to confirm the changes.

8. If we have a cluster configuration, replicate the changes to the cluster.

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

Alternatively, set the properties in the properties files, and then enable them using a configuration task. This option for setting service configuration properties is not available for all properties.

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

   The properties files are located in the directory...

   WP_PROFILE/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 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/PortalServer/config/DynamicContentSpotMappings.properties

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 WebSphere Portal properties files to take effect...

   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh update-properties -DPortalAdminPwd=foo -DWasUserid=username -DWasPassword=foo

   For changes to Web Content Manager properties files...

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

Results

Your service configuration properties updates are now in effect.

See also

• Overview of configuration services
• Portal service configuration
• Web Content Manager service configuration

Parent Configure portal behavior

Related concepts:
Pre-rendering a website
Syndication properties
Web content authoring options
Data cache configuration
WCM v8 Wiki
Control the behavior of authoring tools components
Configure authoring portlet search
Access the pre-rendered site
Pre-rendering options
Create category selection trees
Text, rich text and HTML elements
Syndication troubleshooting
User roles and access
Use the web content member fixer task
Cache tuning for federated documents
Import large files and images
Enable connect tags
Control access to hosts specified in a URL
Enable email
Use a page navigation element
Web Content Manager
Configure remote server access for links
Configure access to remote systems for federated documents
Enable People Finder for anonymous users
Filter the content model