Set service configuration properties

The configuration for each service is stored in and accessible through the WAS admin 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 we might want to remove properties that can be used with their default values or are no longer required.

Set configuration service properties

1. Select the appropriate WAS admin console:

   • If running standalone, use the local console.

   • If installed in a cluster, use the console of the dmgr.

2. Start the WAS admin console :

   http://example.com:admin_port/ibm/console
   

   where example.com is the name of the server or node host name of your server when on z/OS and admin_port is the port assigned to the WAS admin console.

3. In the navigation click...
   Resources | Resources Environment | Resource Environment Providers

4. 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 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 to which to make changes.

   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 we are done, click Save at the start of the page under Message(s).

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

10. If running a cluster configuration, replicate the changes to the cluster.

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

Configure using properties files

Changes to config files do not affect runtime properties until the following tasks are run.

For changes to WebSphere Portal properties files

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

For changes to WCM properties files

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

This option for setting service configuration properties is not available for all properties.

See also

1. Overview
2. Portal configuration services
3. WCM configuration services

Parent: Configure portal behavior
Related:
Enable People Finder for anonymous users
Filtering the content model