Changing the order of the callers for a token or message part

Specifying a caller in default and general bindings indicates which token or tokens to use to create authentication credentials. When there are multiple tokens on an incoming message, the order of the callers determines which token is used for the credentials. You can rearrange the order of the callers using the administrative console.

Before you begin

Before you can complete this task, you must create a new policy set and attach it to a service, or copy and edit one of the sample system policy sets. For more information, read the topics Creating policy sets using the administrative console and Attaching a policy set to a service artifact. You can also create multiple new callers in the default provider bindings associated with the policy set, as described in the topic Configuring the callers for general and default bindings

Procedure

  1. Edit the bindings for the policy by clicking Services > Policy sets > General Provider policy set bindings , then click on the name of the bindings. A caller is specified for the provider bindings only, not for the client bindings.
  2. Navigate to the Callers panel by clicking on the policy name, then click the Caller link.
  3. In the caller collection table, the callers are listed with the order of each caller displayed in the Order column. The order number indicates the order of preference in which the callers are used when multiple authentication tokens are received on an incoming message. Use the Move up and Move down buttons to change the order of the callers.
    1. To change the order of a caller to a higher priority, click the selection box next to the caller name, then click the Move up button. When a caller is moved up in priority, a caller that is above it will be moved down.
    2. To change the order of a caller to a lower priority, click the selection box next to the caller name, then click the Move down button.

Example

The order attribute is assigned only for callers on bindings in WebSphere® Application Server Version 7.0. Bindings created with earlier versions of WebSphere Application Server may have callers, but these callers do not have an order attribute. These callers can appear in the Callers collection table, but do not have an order number in the order column. If these bindings were migrated to Version 7.0, then order attributes must be assigned before saving and using these bindings. You can use the Move up and Move down buttons to assign orders to the callers.




In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=twbs_callerorder
File name: twbs_callerorder.html