Set service configuration properties
Overview
The configuration for each service is stored in and accessible through the IBM WAS administrative 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.
Set service properties using console
Start the dmgr console and go to...
Resources | Resources Environment | Resource Environment Providers | Scope | service | Custom PropertiesIf you create a new property, use type: java.lang.String.
Do not mark the property as required. Otherwise you will not be able to delete it later.
If running a cluster configuration, synchronize changes to nodes.
Restart the server to make the changes become effective.
Set service properties using properties files
You can set the service properties in the properties files and enable them by using a configuration task. Changes to config files do not affect runtime properties until the following tasks are run.
For changes to WebSphere Portal properties files:
cd >WP_PROFILE/ConfigEngine
./ConfigEngine.sh update-properties -DPortalAdminPwd=foo -DWasUserid=username -DWasPassword=fooFor changes to Web Content Manager properties files:
cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh update-wcm-service-properties -DPortalAdminPwd=foo -DWasUserid=username -DWasPassword=fooThis option for setting service configuration properties is not available for all properties.