locked
How do we implement user service mapping in profile manager.... RRS feed

  • Question

  • How does this user service mapping implemented in profile manager and where does the se mappings stored?

    If we have a large number of of services subscribed for one user profile then how do we provide the code for mapping?

    Why do we use service id,application context and service context?

    Monday, May 21, 2007 12:08 PM

Answers

  • Neha - All the features you have mentioned already exist in our Profile Integrator component. You should be able to leverage that by just setting up the event subscription between Profile Manager and Profile Integrator.

     

    Thanks

    Sunday, July 8, 2007 6:53 AM

All replies

  • Hello Neha - Please refer the following URL in terms of how to use the user to service mapping.

     

    http://msdn2.microsoft.com/en-us/library/aa303489.aspx

     

    The mappings are stored in ProfileManager database in RDF format.

     

    User id &  service id combine together to make a composite primary key. As the name denotes, it maps the relationship between user and a service. User can be mapped to any number of service. There is no limitation.

     

    usually the user id is UPN of the user and the service id is binding key in UDDI.

     

    Service context is kind of free text field where you store some user specific information for instance some service may expect you to pass date of birth or specific id which got created during provisioning in the header whenever you try to consume the service. In such scenarios you shouldn't be replicating the data again. You should be able leverage this feature.

     

    Similarly OSS/BSS applications may want to save some user specific information. In such scenarios you would use the application context.

     

    All the data is stored in the Profile Manager database.

     

    Thanks

     

     

     

    Sunday, June 10, 2007 7:35 AM
  • Hi Senthil,

     

    I want to know how we can crate the mappings if a user has to be mapped for hundreds of service as the code will be to long n that wil not b right approach?

    I want to know about profile manager notifications also like user service mapping is mandatory to be used or we can user WS-eventing also to notify the services for the updation on profile changes?

    What I have undestod this USM implementation is long and if we subscribe services  n notify them using eventing ,it will be easier.

     

     

    Plz reply as soon as possible.

     

     

    Thanks,

    Neha

     

     

    Monday, June 11, 2007 10:07 AM
  • Neha - Let me try to explain how you could achieve this.

     

    Let us take a scenario where you have Service A, Service B & Service C in your environment and you have User 1, User 2, User 3  to User N

     

    User 1 may subscribe to Service A & Service B

    User 2 may subscribe to Service A & Service C

    User 3 may subscribe to Service B alone and so on

     

    When you provision the service A & Service B for User 1, you will create a user to service mapping as follows via CreateUSM API

     

    User 1 subscribed to Service A

    User 1 subscribed to Service B

     

    Similarly for User 2 you will have

     

    User 2 subscribed to Service A

    User 2 subscribed to Service C

     

    and so on.

     

    In your service logic or orchestration you would have a a step where it will call the CreateUSM API once the user is successfully provisioned for a service.

     

    Similarly when you deprovision a user from a service you will delete this mapping by calling DeleteUSM API.

     

    So it does matter how many services you have, the orchestration or the service logic which you write to provision the service will have one step to manage the USM.

     

    Regarding the profile manager notifications, let us consider if the User 1 is provisioned for Service A & B. Now he/she changes his profile information like Address or Movie preferences etc you can subscribe to those changes if you are building an application which is interested in those changes.

     

    Profile Integrator is another CSF component subscribes to the ProfileUpdate notifications and propagates those changes to the services the User has subscribed to by looking up the USM.

     

     

    Thanks

    Wednesday, June 13, 2007 12:29 AM
  • Hi Senthil,

     

    Thanx a lot for your reply.

     

    According to your reply,

    1.I got that creation of usm is mandatory in order to have profile notifications work.

    2.Subscrbiption is for the changes(or updates) which the user will perform for update profile  operation.

    3.For profile integrator we dont have any separator tool and we have to implement it through coding only.

     

    Do we have to follow the steps for update profile not

    ifications?

     

    1.user has to subscribe the update events(eg updation of mailid,updation of phone number) for which to send notifications.

    2.user will take service ids from usm.

    3.it wil then go to service catalog to take uris.

    4.It will then create session and send updated data to those services eg address,emailid etc.

     

    Waiting for reply.

     

    Thanks,

    Neha

     

     

     

    Wednesday, June 13, 2007 6:34 AM
  • check
    Wednesday, June 13, 2007 7:19 AM
  • Neha - All the features you have mentioned already exist in our Profile Integrator component. You should be able to leverage that by just setting up the event subscription between Profile Manager and Profile Integrator.

     

    Thanks

    Sunday, July 8, 2007 6:53 AM