test

Sun Java System Portal Server 7.1 Administration Guide

Chapter 5 Web Services for Remote Portlets

Sun JavaTM System Portal Server supports Web Services for Remote Portlets (WSRP). This chapter presents guidelines and best practices for using WSRP. This chapter contains the following sections:

Understanding the WSRP Standard

WSRP 1.0 is an OASIS standard that simplifies integration of remote applications and content into portals. The WSRP standard defines presentation-oriented, interactive web services with a common, well-defined interface and protocol for processing user interactions and for providing presentation fragments suited for mediation and aggregation by portals as well as conventions for publishing, finding and binding such services.

Because the WSRP interfaces are common and well-defined, all web services that implement the WSRP standard plug into all WSRP compliant portals – a single, service-independent adapter on the portal side is sufficient to integrate any WSRP service. As a result, WSRP is the means for content and application providers to provide their services to organizations running portals with no programming effort required.

See the WSRP 1.0 standard for more information:

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp

The implementation of the WSRP 1.0 standard in Portal Server includes both the WSRP consumer and the WSRP producer. The WSRP producer implementation supports publishing JSR 168 portlets for use by a remote WSRP consumer. The JSR 168 portlets are deployed locally on a portal server. These portlets can be published by an instance of the WSRP producer.

Another portal server, through its WSRP consumer, can subscribe to these remote portlets. While local portlets can be expected to provide a large part of the base functionality for portals, remote portlets allow the potential to bind to a variety of remote portlets without installation effort or code running locally on the consuming portal server.

Administering the Producer

This section discusses the following topics:

Create a producer if you want to offer locally deployed portlets remotely to other portals that act as WSRP consumers. A portal can host multiple producers. The consumer can import remote portlets offered by a producer. Based on the portlets that you want to provide to WSRP consumers, you may create one or more producers. A producer can support registration or it does not require registration. If a producer supports registration, then consumers must register to work with the producer.

Creating a Producer That Supports Registration

Registration is used to build a technical or business relationship between the consumer and the producer. While creating a producer, you can define any one of the following registration mechanisms: in-band registration or out-of-band registration:

If the producer requires registration and enabled in-band registration: the consumer can provide the details through WSRP interface and register with the producer. Consumer is also provided an option to register through out-of-band communication. That is, consumer can provide the registration handle obtained through out-of-band communication.

If the producer requires registration and enabled out-of-band registration: the consumer should obtain the registration handle through out-of-band communication and provide the registration handle during registration. Out-of-band registration happens with manual intervention such as phone calls, email, and so on. For a producer that supports out-of-band registration, the producer gets the details about the consumer through out-of-band communication, and it creates a registration handle for the consumer. The registration handle is communicated to the consumer through out-of-band communication.

ProcedureTo Create a Producer That Supports Registration

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click the WSRP tab.

  5. From the Select DN drop-down menu select any DN, and click the Producer tab.

    The WSRP Producers table displays all producers that are created.

    Note –

    Organizations are created in Sun Java System Identity Server. Select the DN of an organization or suborganization based on the availability of portlets.

  6. Click New to create a new producer.

  7. Type the name to identify the producer.

  8. Select Required for Registration.

  9. Select Supported for Inband Registration if you wish the consumer to enter the details, while adding the configured producer, using Sun Java System Portal Server application interface.

  10. To add a registration property, click Add Row. Enter the values. Enter the name of the registration property and description.

    Note –

    Registration properties are the details that you want to get from the consumer while the consumer registers to a specific producer. The registration properties entered by the consumer can be validated through the Registration Validation class.

  11. Select Supported for out-of-band Registration if you wish the consumer to provide the details through out-of-band communication, such as phone calls, email, and so on.

  12. Click Next.

    The Review screen displays the details that you entered. Review details. You can click Previous and change the details you entered.

  13. Click Finish.

Equivalent psadmin Command

psadmin create-producer

Creating a Producer That Does Not Support Registration

For a producer that does not require registration, consumer is not required to enter any information or get any information through out-of-band communication. In this case, the consumer can not customize (or edit) the portlets offered by the producer. The producer that does not support registration provides Read-Only portals to the consumers.

ProcedureTo Create a Producer That Does Not Support Registration

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click the WSRP tab.

  5. Select DN.

    The Configured Producers table displays all producers that are already configured.

  6. Click New.

  7. Type the name of the producer.

  8. Select Registration not required.

  9. Click Finish.

Equivalent psadmin Command

psadmin create-producer

Enabling and Editing WSRP Producer Properties

A newly created Producer should be enabled for a consumer to register. A producer can be enabled by adding one or more portlets.

A producer can be disabled. But, all the consumers registered with the disabled producer will not be able to access the portlets offered by the producer.

ProcedureTo Enable and Edit the Producer's Properties

  1. In the Producer tab, click the producer name link.

    The Edit Properties screen appears. The screen displays WSDL (Web Services Definition Language) URL. WSDL URL is a unique URL for a specific producer through which the consumer accesses the producer.

  2. Add one or more published portlets to the producer.

    Note –

    The producer must have at least one published portlet to enable it. The screen displays all published portlets associated with the portal in which the producer is created.

  3. Select a portlet, and click Add.

  4. Edit the Registration Validation Class field if required.

    Registration Validator is used to validate the registration properties that are entered by the consumer. You can also customize this class based on the needs.

  5. Click Save. Now, the Enable check box displayed in the screen can be edited. Select Enable and click Save.

    Note –

    You can also edit other properties of the producer.

Equivalent psadmin Command

psadmin set-attribute

Customizing Registration Validation Class

You can customize the RegistrationValidator class. Using this class, you can process the registration properties. For example, verifying the zip code of the customer. RegistrationValidator is the SPI for registration validation in the WSRP producer. For more information on customizing the validation class, see http://portalID/portal/javadocs/desktop. You can also refer to WSRP: Validating Registration Data in Sun Java System Portal Server 7.1 Developer’s Guide.

Generating a Registration Handle

For a producer that supports registration, a registration handle needs to be generated for a specific consumer. After generating the registration handle, it needs to be communicated to the consumer to register with the producer through out-of-band communication. Consumer needs to enter the registration handle, while registering with the producer.

ProcedureTo Generate a Registration Handle

  1. Click the Consumer Registration tab.

    The screen displays all consumers that are already registered to the specific producer.

  2. Click New.

  3. Type details, such as name, status, consumer agent, and method.

    Consumer name

    A unique name to identify the consumer.

    Status

    Can be Enabled or Disabled.

    Consumer Agent

    Specifies the name and version of the consumer's vendor. Consumer Agent Name should be ProductName.MajorVersion.MinorVersion, where ProductName identifies the product the consumer installed for its deployment, and majorVersion and minorVersion are vendor-defined indications of the version of its product. This string can then contain any additional characters/words the product or consumer wishes to supply.

    Method

    Specifies whether the Consumer has implemented portlet URLs in a manner that supports HTML markup containing forms with method, get.

  4. Click Next.

    The screen displays the registration property values that are specified while creating the producer.

  5. Enter the values, and click Next. Click Finish.

Publishing Producer Details to ebXML Registry

Publishing a producer stores producer details in any one of the repositories, such as Sun Java System Service Registry Server or an ebXML Registry server. After a producer is published, you can search for the details of the producer using the application interface or using the command-line interface. For details on setting up Sun Java System Service Registry Server, see the Service Registry 3.1 Administration Guide.

You need to configure Sun Java System Portal Server for Registry to publish the producer details to the registry.

ProcedureTo Configure Sun Java System Portal Server for Registry

  1. Create the directory, /soar/3.0/jaxr-ebxml/security, in the machine where Portal Server is installed.

  2. Copy keystore.jks from Registry Server's /var/opt/SUNWsrvc-registry/3.0/data/security directory to /soar/3.0/jaxr-ebxml/security.

  3. Log in to the Portal Server management console.

  4. Select the Portals tab.

  5. Select a portal server from Portals.

  6. Click SSO Adapter from the submenu.

  7. Click JES-REGISTRY-SERVER.

    The Edit Meta-adapter - JES-REGISTRY-SERVER screen appears.

  8. Type the details.

    If you are accessing the registry server through a proxy:

    http.proxy.host

    Hostname of the proxy server.

    http.proxy.password

    Proxy password if proxy server required authentication.

    http.proxy.port

    Port on which proxy server is available.

    http.proxy.user

    Proxy username if proxy server required authentication.

    If you are not using a proxy server:

    registry.keypassword

    Password that is required to get the key from the keystore.

    registry.keystorealias

    The key alias that is present in the keystore that is to be used for authenticating with the registry server.

    registry.keystorelocation

    Location of the keystore relative to /soar/3.0/jaxr-ebxml/.

    registry.keystorepassword

    Password used to open the keystore.

    registry.publishurl

    URL of the registry server where publish request should be sent. This URL should accept SOAP requests.

    registry.queryurl

    URL of the registry server where search request should be sent. This URL should accept SOAP requests.

ProcedureTo Publish Producer Details to Registry

The following steps explain how to publish a producer to the Registry Server:

  1. Create organization data and producer data files.

    Organization data file can contain the following entries:

    org.name=Sun Microsystems

    org.description=Description

    org.primarycontact.name=Henry

    org.primarycontact.phoneno=1234567

    org.primarycontact.email=someone@host.com

    Note –

    The org.name and org.description should be similar as that of the details in Identity Server unless the Registry is deployed internally.

    The producer data file should have the following entries:

    producer.name=Producer_name

    producer.description=Producer_Description

    producer.id=Producer_ID

    Note –

    It is not a must that you should create all the data files. But, for searching the details of producer, organization, or portlet, you should have created at least one file associated with that.

  2. Stop and restart the common agent container:

    /usr/lib/cacao/bin/cacaoadm stop

    /usr/lib/cacao/bin/cacaoadm start

  3. To publish the produce details, use the following command:

    ./psadmin publish-registry -u amadmin -f password_file -p portal1 -m producer -U producer_data_file -O organization_data_file -T portlet -L --debug

    Note –

    The portlet file specifies the portlets that are offered by WSRP producer. The portlets list is specified as a string within double quotes and elements separated by space. For example, "NotepadPortlet BookmarkPortlet WeatherPortlet."

    Note –

    You can check the log file by using the following command: more var/opt/SUNWportal/logs/admin/portal.admin.cli.0.0.log

Equivalent psadmin Command

psadmin publish-registry

Finding a Producer

The following section explains how to search for a producer:

ProcedureTo Search a Producer

  1. Create a Search Producer data file.

    Search Producer data file can contain the following:

    producer.name=producer_name

    producer.description=producer_description

    Note –

    The Search Producer data file contains a description of the producer to search for in the registry. Use the character % as a wildcard. For example, %acme% in producer.name any WSRP Producer that contains the string "acme" in its name.

  2. To search the registry, use the following command:

    ./psadmin search-registry -m consumer -u amadmin -f ps_password -C search_producer_datafile -p portal1

  3. Create a search Portlet data file.

    Search Portlet data file can contain the following:

    portlet.name=portlet_name

    portlet.description=portlet_description

    Note –

    The Search Portlet data file contains a description of the portlet to search for in the registry. Use the character % as a wildcard. For example, %stock% in portlet.name locates any Portlet that contain the string "stock" in its name.

  4. To search based on portlet details, use the following command:

    ./psadmin search-registry -m consumer -u amadmin -f ps_password -D search_portlet_datafile

  5. Create a Search Organization data file.

    Search Organization data file should contain the following:

    organization.name=organization_name

    organization.description=organization_description

    Note –

    The Search Organization data file contains a description of the organization to search for in the registry. Use the character % as a wildcard. For example, %acme% in organization.name locates any organization that contains the string "acme" in its name.

  6. To search based on the organization data file, use the following command:

    ./psadmin search-registry -m consumer -u amadmin -f ps_password -L search_organization_datafile -p portal1

Equivalent psadmin Command

psadmin search-registry

Administering the Consumer

This section explains the activities need to be performed at the consumer side.

The following topics are discussed:

Adding a Configured Producer

To communicate with the portlets offered by the producer, a consumer needs to add a configured producer. If a producer requires registration, add a configured producer using the following methods:

If the producer does not require registration, the consumer is not required to enter any details while adding a configured producer.

ProcedureTo Add a Configured Producer

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click the WSRP tab.

  5. Select any DN and click New.

  6. Type the configured producer name. Select the identity propagation mechanism. By default, None is selected.

    Note –

    Identity propagation mechanism allows the users of the consumer portal to present their credentials to the producer portal. It is a mechanism by which users can federate their identity from consumer portal to the producer portal.

  7. Type the WSDL URL, and click Next.

    Note –

    You can also search for a WSDL URL based on the producer or portlet. The search result displays WSDL URL of a producer only if the producer is published.

  8. If the producer requires registration, you can register the producer in two methods: by entering the registration property values (in-band registration) or entering the registration handle (out-of-band registration). Click Next.

  9. If you selected the first method in step 7, enter the registration properties and click Next. If you selected the second method, enter the registration handle obtained through out-of-band communication, and click Next.

  10. Review the details and click Finish.

Equivalent psadmin Command

psadmin create-configured-producer

Identity Propagation Mechanism

Identity propagation is a mechanism by which the WSRP consumer supplies the identity of the user to the WSRP producer web service. It is a federation mechanism where the user federates its identity between the consumer and producer. After a successful federation, the consumer portal propagates the user identity to the producer portal. The WSRP producer, after receiving the user credentials from the consumer, validates the credentials and allows or denies access to the resource in the specified user context.

The user has two identities for each portal. That is, one for producer portal and the other for consumer portal. The user federates these identities using the identity propagation mechanism provided. This provides a single-sign on mechanism for the consumer and the producer portal. When the user logs into the portal through the consumer portal, the user gets the content that the user gets when logs directly into the producer portal. The changes that the user makes using the federated identity would be available when the user logs into the producer portal.

Sun Java System WSRP producer supports the following identity propagations:

In the above list, the last three options implement the OASIS WSS Username token profile specification. This specification describes how to use the Username Token with the Web Services. WSS specification describes how a web service consumer can supply a Username Token by identifying the requestor by username, and optionally using a password to authenticate that identity to the web service producer.

Note –

Many portal vendors support and implement the OASIS WSS Username token profile specification. Use one of the three options when interoperability is required.

There are two levels of identity propagation mechanism in Portal Server. First, the administrator of the consumer portal discovers that the producer portal supports one of the above specified identity propagation mechanisms. The administrator may allow the users to send their identity. Portal Server consumer supports all the above mentioned Identity Propagation Mechanisms.

After the consumer is created, the administrator has to create remote channels based on the identity propagation mechanism supported by the consumer. After the channels are available on the user Desktop, they are ready to accept identity propagation.

The identity propagation mechanism is set at the producer automatically. Portal Server checks for authentication from Sun SSO, then OASIS user name token profile, and then the No Identity Propagation mode.

Configuring Digest Passwords

Only new users can use the Digest Password facility after running the configuration command to store the LDAP passwords in plain text

Creation of a consumer should involve selecting the WSSO Username Token Profile (with Digest Password) option for User Identity Propagation Mechanism.

The Web Services SSO Portlet must be edited to select the appropriate Web service URL (producer) and provide the new username and password.

ProcedureTo Configure the Accept Digest Passwords

Do the following to configure Sun Java System WSRP Producer to accept Digest Passwords.

  1. Run the command /opt/SUNWdsee/ds6/bin/dscfg set-server-prop pwd-storage-scheme:CLEAR to change the password storage scheme of the Directory Server so that plain text passwords are stored.

    Note –

    It is assumed that the default installed location of the Directory Server is /opt/SUNWdsee.

  2. Create a new user in the AM console, to ensure that the Username Token Profile with Password Digest can be used.

Recommendations

Creating User Token Profiles Using WebServices SSO Portlet

You can create user token profiles to authenticate user credentials if the user uses identity propagation mechanism. You can define the user name and password for specific Web service that the producer offers.

ProcedureTo Provide User Credentials Using WebServices SSO Portlet

  1. Log in to Portal Server Desktop.

  2. In the WebServices SSO Portlet, click the Edit button.

  3. In the Create NewToken Profile section, select the WebService URL for which you want to create a user token profile.

  4. Type the user name and password. Click Add.

    You can also edit or remove an existing user token profile.

Updating Service Description

After the consumer configures the producer, use the Update Service Description option to update any changes made to the producer later. For example, addition of new portlets or changes to the registration properties after the registration.

ProcedureTo Update Service Description

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click the WSRP tab.

  5. Select DN (Distinguished Name).

  6. Click the configured producer link.

  7. In the Edit Configured Producer screen, click Update Service Description.

Equivalent psadmin Command

psadmin update-configured-producer-service-description

Mapping User Categories to Roles

WSRP supports the concept of user categories, which are included in the service description of the producer. Mapping user categories to the roles allows the user to map the roles that are defined in the consumer portal to the roles that are defined in the portlet. Sun Java System Portal Server maps Java System Access Manager's roles to the portlet's roles. These roles can be mapped to the corresponding WSRP user categories.

You can perform the following tasks:

Roles can be defined in the portlet while deploying the portlet.

Note –

The roles defined in the portlet must exist in the Access Manger of the producer.

ProcedureTo Create Roles in Portlets

The following task creates a role in amconsole in Sun Java System Access Manager and Portlets.

  1. Log in to the Access Manager console.

  2. Create a role and add a user to it.

  3. In webxml of the portlet application, add the following code:

    <security-role>

    <role-name>PS_TEST_DEVELOPER_ROLE<role-name>

    </security-role>

  4. Add the following lines in portlet.xml of the portal.

    <security-role-ref>

    <role-name>PS_TEST_DEVELOPER_ROLE<role-name>

    <role-link>PS_TEST_DEVELOPER_ROLE<role-link>

    </security-role-ref>

  5. Create the portlet application war file.

  6. Create a roles file with the following entry.

    cn\=AM_TEST_DEVELOPER_ROLE,o\=DeveloperSample,dc\=india,dc\=sun,dc\=com=PS_TEST_DEVELOPER_ROLE

  7. Deploy the portlet using the following command.

    /opt/SUNWportal/bin/psadmin deploy-portlet -u amadmin -f ps_password -d "o=DeveloperSample,dc=india,dc=sun,dc=com"-p portal1 -i stockprice-8080 --rolesfile rolesfile TestPortlet.war

Equivalent psadmin Command

psadmin deploy-portlet

ProcedureTo Map User Categories to Role

Do the following to map user categories to role:

  1. In the Consumer tab, click the producer name link.

    The Edit Configured Producer screen displays the following: User Category: The roles in the producer portlet. Local Roles: The roles that are defined at the consumer's Sun Java System Access Manager.

  2. In the User Categories to Role Mapping section, map user categories to the roles defined at the consumer, and click OK.

Mapping Consumer Attributes

The Sun Java System Portal Server implementation of WSRP Consumer maps common user attributes stored in the user entry on the Sun Java System Directory Server to the standard set of user attributes that the WSRP specification mandates.

If a consumer portlet uses any of the attributes that are not specified in the LDAP schema, create a custom object class to store these attributes and add this object class to the user entry. After attributes are created, map the LDAP attribute to the corresponding WSRP attribute using Sun Java System Access Manager management console.

Configuring Proxies

Proxies need to be configured for consumer and for web container XML files.

You can perform the following tasks:

ProcedureTo Configure Proxy for Consumers in Common Agent Container

  1. Run ./cacaoadm get-param java-flags.

  2. Copy the values and paste it to ./cacaoadm set-param java-flags.

  3. Now add the following to the command: -Dhttp.proxyHost=webcache.canada.sun.com -Dhttp.proxyPort=8080 -Dhttp.proxyUser=Proxyuser -Dhttp.proxyPassword=Password

  4. Press Enter.

  5. Restart the common agent container server.

ProcedureTo Configure Web Container XML file

  1. Edit the following file:

    vi /var/opt/SUNWappserver/domains/domain1/config/domain.xml

  2. Set the following JVM options:

    • Dhttp.proxyHost

    • Dhttp.proxyPort

    • Dhttp.proxyUser

    • Dhttp.proxyPassword

Administering the WSRP Producer

This section describes how to administer the Sun Java System Portal Server Web Services for Remote Portlets (WSRP) service. The tasks to administer a WSRP producer are:

ProcedureTo Create a WSRP Producer

A WSRP producer is created with the following:

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click WSRP, then Producers from the submenu.

  5. From Select DN drop-down menu choose any DN.

  6. From WSRP Producers click New to launch the wizard

  7. Follow the instructions to create the specified producer.

    For more information about the attributes, see Sun Java System Portal Server 7.1 Technical Reference

Equivalent psadmin Command

psadmin create-producer

ProcedureTo Edit a WSRP Producer

You can edit the WSRP Producer as follows:

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click WSRP, then Producers from the submenu.

  5. From Select DN drop-down menu choose any DN.

  6. Select a WSRP producer and modify the configuration attributes as necessary

    For more information about the attributes, see Sun Java System Portal Server 7.1 Technical Reference

  7. Click Save to record the changes.

Equivalent psadmin Command

psadmin set-attribute

ProcedureTo Create a Consumer Registration

Each consumer registration represents a remote WSRP consumer that has established a relationship with the WSRP producer. A WSRP producer that supports allows multiple WSRP consumers to register with it. The registration mechanism allows a WSRP consumer to describe its capabilities to a WSRP producer.

A WSRP consumer is added out of band (such as by email or telephone). The information entered when adding a consumer registration must match the capabilities of the WSRP consumer that is given the registration handle. Consumer registrations allow a WSRP producer to scope artifacts (such as portlet preferences) that a WSRP consumer creates on the WSRP producer.

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click WSRP, then Producers from the submenu.

  5. From Select DN drop-down menu choose any DN.

  6. Select a WSRP producer, then Consumer Registrations.

  7. Click New to launch the wizard.

  8. Follow the instructions to create the specified consumer registration.

    For more information about the attributes, see Sun Java System Portal Server 7.1 Technical Reference

Equivalent psadmin Command

psadmin create-consumer-registration

ProcedureTo Edit a Consumer Registration

You can edit existing consumer registrations manually. Note that this could also be done via in-band registration from the WSRP Consumer end. Ensure that both out of band and in band registration are not used simultaneously.

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click WSRP, then Producers from the submenu.

  5. From Select DN drop-down menu choose any DN.

  6. Select producers, then select a WSRP producer, then Consumer Registrations.

  7. Select a consumer registration and modify the configuration attributes as necessary.

    For more information about the attributes, see Sun Java System Portal Server 7.1 Technical Reference

  8. Click Save to record the changes.

Administering the WSRP Consumer

This section describes the tasks to administer the WSRP Consumer:

ProcedureTo Add a Configured Producer

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click WSRP, then Producers from the submenu.

  5. From Select DN drop-down menu choose any DN.

  6. Under Configured Producer click New to launch the wizard

  7. Follow the instructions to create the specified configured producer.

    For more information about the attributes, see Sun Java System Portal Server 7.1 Technical Reference

Equivalent psadmin Command

psadmin create-configured-producer

ProcedureTo Edit a Configured Producer

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click WSRP, then Consumer from the submenu.

  5. From Select DN drop-down menu choose any DN.

  6. Select a configured producer and modify the configuration attributes as necessary.

    Note –

    Use the Update Service Description option to update any changes made to the producer. See Updating Service Description.

    For more information about the attributes, see Sun Java System Portal Server 7.1 Technical Reference

  7. Click Save to record the changes.

Equivalent psadmin Command

psadmin set-attribute

ProcedureTo Specify the Consumer Name

The WSRP consumer sends the consumer name to producers during registration. The value specified for the consumer name is used as the default unless a value is specified for consumer name at the organization or suborganization level.

  1. Log in to the Portal Server management console.

  2. Select the Portals tab.

  3. Select a portal server from Portals.

  4. Click WSRP, then Consumer from the submenu.

  5. From Select DN drop-down menu choose any DN.

  6. Under WSRP Consumer, click Edit.

  7. Specify the consumer name.

  8. Click OK.

Equivalent psadmin Command

psadmin set-attribute