Configure resource management and site management in a cluster

To ensure that the portal can retrieve metadata information for resource management on remote systems after migration, configure the Resource Manager portlet with information about the remote system and the settings used to handle communication with the system.

Because the Resource Manager portlet uses the AJAX proxy component to access the remote system, you can use the global AJAX proxy configuration to customize the outgoing HTTP traffic, such as applying specific HTTP timeout values or configuring an outbound HTTP proxy server. You must list the individual content management servers to be accessed through the Resource Manager portlet as allowed request targets in the AJAX proxy configuration, and enable LTPA cookie forwarding for those requests. To do this, map the URL patterns for the content management server to the resource_manager_policy dynamic policy using the WP ConfigService configuration service.

1. Log in to the WAS administrative console.

2. Click Resources -> Resource Environment -> Resource Environment Providers.

3. Click WP ConfigService.

4. Under Additional Properties, click Custom Properties.

5. Click New, and enter the property name wp.proxy.config.urlreplacement.resource_manager_policy.suffix, and set the string value to the URL pattern of the content management server; for example http://server:port/*.
   For example, to enable the Resource Manager portlet to access information from the remote server over HTTP, you would add the following property:

   wp.proxy.config.urlreplacement.resource_manager_policy.1=http://server:port/*

   The value of the property key suffix can be any value as long as it is unique within the set of keys mapping to the resource_manager_policy dynamic policy.

6. Create additional properties as needed for any other content management servers that you need to access through the Resource Manager portlet.

7. Optional. If you use an alternative portal context, you need to update the site management portlet as follows:

   1. Click Administration -> Portlet Management -> Portlets.

   2. Select Configure portlet for the Resource Manager portlet.

   3. Change the value of proxy.servlet.path to the new portal context value.

   4. Save changes.

8. Optional. The Resource Manager portlet can also consume arbitrary ATOM feeds. To enable this, you can map the URL prefix of the ATOM feed to the default_policy dynamic policy.

   Do not perform this step if you set the resource_manager_policy for the same server by step 5. above.

   1. Click New, and enter the property name wp.proxy.config.urlreplacement.default_policy.suffix, and set the string value to the URL pattern of the server providing the ATOM feed.
      For example, to enable the Resource Manager portlet to access ATOM feeds from the server www.example.com, you would add the following property:

      wp.proxy.config.urlreplacement.default_policy.1=http://server:port/*

      The value of the property key suffix can be any value as long as it is unique within the set of keys mapping to the default_policy dynamic policy.

      To prevent security token forwarding to untrusted servers, be sure that you do not use the resource_manager_policy dynamic policy for those servers.

   2. Create additional properties as needed for any other ATOM feed servers that you need to access through the Resource Manager portlet.

9. Save changes and restart the portal server.

Parent

Migrate a V6.1.x clustered environment

Previous

v6.1 Web content post migration tasks

Next topic

Update custom themes and skins with hardcoded context root references in a cluster

 

+

Search Tips   |   Advanced Search