Export (0) Print
Expand All

ProfileManager.config

Connected Services Framework

The following diagram shows how the Web.config file references the Common.config, EnterpriseInstrumentation.config, TraceSessions.config, PolicyCache.config, and ProfileManager.config configuration files:

Please see the previous sections for Web.config, Common.config, EnterpriseInstrumentation.config, TraceSessions.config, and PolicyCache.config. These files are used by all of the Connected Services Framework components.

ProfileManager.config

The ProfileManager.config file is located in the directory specified by the ProfileManager property of the Web.config file that is located in the Profile Manager deployment directory:


<Microsoft.Csf>
 …
 <ConfigFiles>
 …
 <add key="ProfileManager" value="C:\Program Files\Microsoft\Microsoft Csf\Configuration\ProfileManager.config" />
 …
 </ConfigFiles>
 …
</Microsoft.Csf>
 

Here is an example of ProfileManager.config:

<?xml version="1.0" encoding="utf-8"?>
<ProfileManagerConfigurationSettings>
 
    <!-- Configurable Items used by ProfileManager PropagateAttribute functionality-->
 
    <!-- outbound datahandling setting-->
    <OutboundDataHandlingSettings>
       <!--Value in seconds to Get response from ServiceCatalog before Orchestration can timeout -->
        <GetURIsReqTimeoutDurationInSeconds>600</GetURIsReqTimeoutDurationInSeconds>

        <!--Value in seconds to Get response from Session for Create SessionMethod before Orchestration can timeout -->
        <CreatingSessionTimeoutDurationInSeconds>600</CreatingSessionTimeoutDurationInSeconds>
 
        <!--Value in seconds to Get response from Vas / Session for RouteMessageToParticipant before Orchestration can timeout -->
        <RouteMessageToParticipantTimeoutDurationInSeconds>600</RouteMessageToParticipantTimeoutDurationInSeconds>
 
        <!--Value in seconds to Get response from Session for TerminateSessionRequest before Orchestration can timeout -->
        <TerminateSessionTimeoutDurationInSeconds>600</TerminateSessionTimeoutDurationInSeconds>
    </OutboundDataHandlingSettings>
 
    <!--Participant Specific Configuration Data-->
    <ParticipantDataHandling>
 
        <!--Value in seconds for participants to response before session can timeout-->
        <ParticipantTimeout>600</ParticipantTimeout>
 
        <!--Role of Participants, Participants roles can be service / Persona, Currently supported are "Service"-->
        <ParticipantRole>Service</ParticipantRole>
 
        <!--Mode of Participants, Participant Mode can be OneWay / TwoWay-->
        <ParticipantMode>OneWay</ParticipantMode>
 
        <!--Type of Participants components, Participant Components can be WebService/DotNetComponent, Currently supported are "WebService-->
        <ParticipantType>WebService</ParticipantType>
 
        <!--SOAP Action To be invoked at the participants end, Currently All participants needs to implement the same SoapAction -->
        <ParticipantAction>UpdateAttribute</ParticipantAction>
 
        <!--Identifier for ProfileManagerParticipant, This value will be used to route message to ProfileManager to Update CSF Databases-->
        <ProfileManagerParticipantServiceIdentifier>VASProfileManager</ProfileManagerParticipantServiceIdentifier>
 
        <!--Identifier for ProfileManagerOrchestrationParticipant-->
        <ProfileManagerOrchestrationServiceIdentifier>ProfileManagerOrchestration</ProfileManagerOrchestrationServiceIdentifier>
 
        <!--SoapAction to be invoke at VasProfileManager, Value should be "UpdateAttribute" when VasProfilemanager is used to udpate at csf databases-->
        <VasProfileManagerSoapAction>UpdateAttribute</VasProfileManagerSoapAction>
 
        <!--Identifier for ProfileManagerPersona Participant-->
        <ProfileManagerPersonaParticipantServiceIdentifier>Persona</ProfileManagerPersonaParticipantServiceIdentifier>

        <!--True: PM should use PMCredentials from Database to invoke SessionManagerAdmin calls
        False: PM should use the credentials from the incomming request message to invoke sessionmanageradmin Calls-->
        <UsePMCredentialsInSessionManagerAdminCalls>true</UsePMCredentialsInSessionManagerAdminCalls>
 
</ParticipantDataHandling>
    <!--
    This section contains a collection of special attributes that are intercepted
    by the profile manager and redirected to user defined services for processing.
    Each entry contains the attribute name and an appropriate URL to redirect to.
    -->
    <PropagateAttributeSpecialAttributes>
        <SpecialAttribute attributeName="orgStatusChange" redirectionUrl="http://localhost/OCProxy/Microsoft_Csf_Oss_OC_OrgChange.ashx" action="http://www.microsoft.com/csf/20/Microsoft_Csf_Oss_OC_OrgChange/ReceivePA"/>
    </PropagateAttributeSpecialAttributes>
</ProfileManagerConfigurationSettings>

 

 ProfileManager.config configuration values:

 GetURIsReqTimeoutDurationInSeconds                       

 

Description

Maximum duration in seconds for the GetServiceUris call to the Service Catalog component.

How it is used

The Profile Manager component will only wait this long for a response from the Service Catalog component before marking the request as expired.

Default value

600

Needs to be changed for each deployment

No

 CreatingSessionTimeoutDurationInSeconds

 

Description

Maximum duration in seconds for the CreateSession call to the  Session component.

How it is used

The ProfileManager component will only wait this long for a response from the  Session component before marking the request as expired.

Default value

600

Needs to be changed for each deployment

No

 RouteMessageToParticipantTimeoutDurationInSeconds

 

Description

Maximum duration in seconds for the RouteMsgToParticipants call to the  Session component.

How it is used

The ProfileManager component will only wait this long for a response from the  Session component before marking the request as expired.

Default value

600

Needs to be changed for each deployment

No

 TerminateSessionTimeoutDurationInSeconds

 

Description

Maximum duration in seconds for the TerminateSession call to the  Session component.

How it is used

The ProfileManager component will only wait this long for a response from the  Session component before marking the request as expired.

Default value

600

Needs to be changed for each deployment

No

 ParticipantTimeout

 

Description

Maximum duration in seconds for a participant to respond to calls from the Profile Manager (via Session).

How it is used

The ProfileManager component will only wait this long for a response from the participant service before marking the request as expired.

Default value

600

Needs to be changed for each deployment

No

 ParticipantRole

 

Description

The role of the participant service when generating the Session Manifest.

How it is used

When the Session Manifest is generated, each participant needs to have a role.

Default value

Service

Needs to be changed for each deployment

No – this value is not expected to change

 ParticipantMode

 

Description

The mode of the participant service when generating the Session Manifest.

How it is used

When the Session Manifest is generated, each participant needs to have a mode.

Default value

OneWay

Needs to be changed for each deployment

No – this value is not expected to change.

 ParticipantType

 

Description

The type of the participant service when generating the Session Manifest.

How it is used

When the Session Manifest is generated, each participant needs to have a type.

Default value

WebService

Needs to be changed for each deployment

No – this value is not expected to change.

 ParticipantAction

 

Description

The action in the message sent to the Profile Management participant.

How it is used

When the ProfileManager calls a participant, this action is used.

Default value

UpdateAttribute

Needs to be changed for each deployment

No

 ProfileManagerParticipantServiceIdentifier

 

Description

Name of the ProfileManager in the Session Manifest

How it is used

When the ProfileManager generates a SessionManifest, it needs a name for the ProfileManager participant that update the Connected Services Framework database.

Default value

VASProfileManager

Needs to be changed for each deployment

No

 

ProfileManagerOrchestrationServiceIdentifier

 

Description

Name of the ProfileManagerOrchestration in the Session Manifest.

How it is used

When the ProfileManager generates a SessionManifest, it needs a name for the orchestration participant.

Default value

ProfileManagerOrchestration

Needs to be changed for each deployment

No

 

VasProfileManagerSoapAction

   

Description

The action in the message sent to the value-added service (VAS) participants.

How it is used

When the ProfileManager sends a message to a VAS Participant (via Session) this is the action that is uses.

Default value

UpdateAttribute

Needs to be changed for each deployment

No

 

ProfileManagerPersonaParticipantServiceIdentifier

   

Description

Name of the Persona participant in the Session Manifest.

How it is used

When the ProfileManager generates a SessionManifest, it needs a name for the Session Persona Participant.

Default value

Persona

Needs to be changed for each deployment

No

 UsePMCredentialsInSessionManagerAdminCalls

Description

True or falsedetermines if the ProfileManager should use the user name and password of the original request, or if it should use the user name and password of the ProfileManager process.

How it is used

If true, the user name and password of the ProfileManager process is used when calling the CreateSession and Terminate session methods of the  Session component.

Default value

true

Needs to be changed for each deployment

No

 SpecialAttribute

Description

This attribute allows for the interception and redirection of propagate attribute requests that are sent to the Profile Manager connector.  

How it is used

The propagate attribute requests should be sent to the Profile Manager, who will then forward them on to the propagate attribute orchestration for processing.  In cases where the attribute is the same as the name specified in the attributeName, the url and appropriate action will be used to redirect the propagate attribute request to the other service.   This allows the user to create their own custom service to perform the propagation of special types of attributes.

Multiple attributes may be specified and redirected.

Default value

N/A

Needs to be changed for each deployment

Optional

 

Show:
© 2014 Microsoft