Overview | Package | Class | Tree | Deprecated | Index | Help
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES

## Package com.plumtree.remote.profile

Provides classes and interfaces for querying remote systems for user profile information and augmenting/synchronizing Plumtree Corporate Portal user profiles.

See:
Description

Interface Summary
IProfileProvider | An interface used to initiate access to and obtain user profile information from a remote system.
IUser | An interface that allows the profile synchronization job to query the properties of a user profile in a remote system in order to update the user's profile in the portal.

Class Summary
ProfileConstants | Static SCI constants related to profile services.
ProfileInfo | A `NamedValueMap` specifically for storing information about administrative configuration settings for a profile service.
UserPropertyInfo | A `NamedValueMap` specifically for storing user information properties from a profile service.

## Package com.plumtree.remote.profile Description

Provides classes and interfaces for querying remote systems for user profile information and augmenting/synchronizing Plumtree Corporate Portal user profiles.

The purpose of a profile service is to import information about portal users from an external system into the portal so that the information can be used by the portal and other services.

The first step is to synchronize the user information in the external system with existing users in the portal; this is the process that must be handled by the remote service.

As with authentication services, the synchronization process is handled by the portal Automation Server, as scheduled in the Job associated with the Profile Source object in the portal. The profile information imported by the profile service must be associated with portal properties so that it can be accessed by portal objects and other remote services. The portal’s Profile Source editor allows you to map user information to Plumtree User Information properties, making it available to any service with the necessary access privileges.

You must configure the necessary User properties in the portal before running a profile service. To be stored in the portal, the data imported by a profile service must have corresponding User properties, configured in the Global Object Property Map.

To add user information to User Profiles, you must configure the portal. To associate imported User properties with User Profiles in the portal, you must configure the properties in the User Profile Manager. Profile services are used for existing portal users only. To import new users into the portal, you must use an authentication service.

To view the SOAP endpoint to enter in the Profile Web Service Settings of the Profile Web Service, open a browser and point it to http://<my_server>:<my_port>/<war_name>/services. For example, http://express-job1.devnet.plumtree.com:8080/HelloWorldProfile/services. The page should display "And now...Some Services." with a list of all defined services. The default endpoint for Synchronization URL is http://<my_server>:<my_port>/<war_name>/services/ProfileProviderSoapBinding, and for Service Configuration URL (if used) is http://<my_server>:<my_port>/<war_name>/services/SciProviderSoapBinding. If the DeployServlet was used to create the services, you will see the services with a developer-supplied prefix.

## Related Documentation

For examples, developer discussions and additional documentation, see Plumtree Developer Center

Overview | Package | Class | Tree | Deprecated | Index | Help
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES

For additional information on the IDK, including tutorials, blogs, code samples and more,see the AquaLogic User Interaction Developer Center on BEA dev2dev.

Copyright ©2007 BEA Systems, Inc. All Rights Reserved.