ShowTable of Contents
Beginning with WebSphere Portal Server (Portal) Version 6.0, configuration properties are logically grouped as "services" and each
service is assigned a name. The properties associated to each service are stored in WebSphere Application Server (WSAS)
as Resource Environment Providers.
Implementation
The Portal configuration properties provide settings to change the way the portal behaves. For example, the LDAP Relative Distinguished Name
and other properties used by the Portal User Management Architecture (PUMA) are grouped in the PumaStoreService.
Session-related properties are group in the SessionValidatorService and so on. A complete list of the Portal services can be
found in the WebSphere Portal documentation.
The properties and their values are written to the file resources.xml in the WSAS directory structure under the Profile root directory:
In a cluster, the file is located on the Deployment Manager under the /clusters directory.
Each property-value pair will be contained on its own line under the name of the Resource Environment Provider.
For example, the XML for the PumaStoreService Provider will appear similar to this example:
<resources.env:ResourceEnvironmentProvider xmi:id="ResourceEnvironmentProvider_1257636024768"
name="WP PumaStoreService">
<propertySet xmi:id="J2EEResourcePropertySet_1257636024772">
<resourceProperties xmi:id="J2EEResourceProperty_1257636029601" name="store.puma_default.user.add.required.attributes"
value="sn" description="" required="false"/>
<resourceProperties xmi:id="J2EEResourceProperty_1257636029710" name="store.puma_default.user.nonsupported.attributes"
value="certificate,identifier" description="" required="false"/>
<resourceProperties xmi:id="J2EEResourceProperty_1268763772625" name="store.puma_default.user.fbadefault.filter"
value="uid" description="" required="false"/>
<resourceProperties xmi:id="J2EEResourceProperty_1268763774781" name="store.puma_default.group.fbadefault.filter"
value="cn" description="" required="false"/>
</propertySet>
</resources.env:ResourceEnvironmentProvider>
Property Updates
Portal properties can be modified using one of two methods:
1) Best Practice: Add or Update the property in the WebSphere Application Server Integrated Solutions Console under the "Resources" menu.
The example below shows the PumaStoreService. All the properties are defined under the "Custom properties" menu.
2) Add or update the property in the appropriate properties file and run the ConfigEngine task update-properties.
No matter which method is used, the Portal server must be restarted. In a cluster synchronize the nodes prior to restart.
Note: Manual modification of resources.xml is strongly discouraged. An incorrect entry could could cause Portal startup to fail and render the Portal inaccessible.
Support will often request a copy of resources.xml as part of the problem determination process. Examining the file is a
quick way to determine the value for all the Portal configuration properties in the environment.