Connected Services Framework 3.0 Developers Guide Send comments on this topic.
How to Configure Your WES to Communicate with Session

To add a WES to the Connected Services Framework environment, perform the following tasks:

  1. Use the UDDI interface to add the necessary UDDI entries for the WES in the Service Catalog. For more information, see > How to Register Services By Using the UDDI Interface.
  2. Create a new application for the WES by using the Identity Manager Microsoft Management Console snap-in. Using this snap-in you can:
    1. Retrieve the unique service ID for the WES from the Service Catalog. The Identity Manager uses the service ID to identify the service in its user map tables, specifying the identities required to access the service.
    2. Specify the Microsoft Windows group for users that can manage this application.
    3. Specify the Microsoft Windows group for users that can access this application.
  4. (Optional) Modify the SessionPolicy.config file and add the policy required to access the WES. If you are using policy mapping to associate policy with service endpoints, update the SessionPolicyMapping.config file. For more information about configuring policy for services and the Session Web service, see >Using Policies.
  5. (Optional) If you have added a policy for the WES to the SessionPolicy.config file and you wish to use the Message Visualizer tool to trace messages flowing to the WES, add the following policy assertion to the policy, replacing traceserver with the address of the server running the CSFTraceService service.

    <traceAssertion remoteServerUri="http://traceserver:9502/LogWriter.soap"/>

    For more information about configuring the Message Visualizer tool, see >Configuring the Message Visualizer.
  6. (Optional) If the WES uses profiles, modify the ProfileIntegratorMapping.config file and add a new <ProfileIntegratorMapping> section for the service containing the following elements:
    1. ServiceUUID. The unique identifier of the service.
    2. Action. The action to apply to the message sent to the Session from the Profile Integrator.
    3. XSLT. The path to the XSLT to apply to an outgoing message so that the message will be in a format the service can consume. 
  8. For more information, see >The ProfileIntegratorMapping.Config File.
Page view tracker