Configure resource management

Overview

To retrieve metadata for resource management on remote systems, 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.

Map URL patterns for the content management server to the resource_manager_policy dynamic policy

Log in to the WAS administrative console and go to...

Resources | Resource Environment | Resource Environment Providers | WP ConfigService | Additional Properties | Custom Properties | New

Enter 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:

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.

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

If you use an alternative portal context, update the site management portlet. Go to:

Administration | Portlet Management | Portlets | Configure portlet | Resource Manager portlet

and change the value of proxy.servlet.path to the new portal context value.

Save changes.

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 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.

   Save changes and restart the portal server.

   
   

   Parent

   Manage the site

   
   

   Related tasks

   
   Enable remote access to servers
   Manage the servers
   Publish page
   Provide reviewer access to a published page
   Promoting page
   Demoting page
   Republishing and promoting a page
   Portal Scripting Interface extension for site management

   
   

   +

   Search Tips   |   Advanced Search