This chapter describes back-end configuration requirements for the People Connections service.
This chapter includes the following sections:
Section 16.3, "Configuring People Connections for WebCenter Portal"
Section 16.4, "Setting Up a Proxy Server for Activity Stream"
Section 16.6, "Specifying a Management Chain for Organization View"
Section 16.8, "Synchronizing Profiles with the Identity Store"
Section 16.9, "Configuring Cache Options for the Profile Service"
Section 16.10, "Troubleshooting Issues with People Connections"
Permissions:
To perform the tasks in this chapter, you must be granted the WebLogic Server Admin
role through the Oracle WebLogic Server Administration Console and the Administrator
role in the deployed application:
WebCenter Portal: Administrator
role granted through Portal Builder Administration.
Portal Framework application: Administrator
role granted through the Administration Console.
For more information about roles and permissions, see Section 1.8, "Understanding Administrative Operations, Roles, and Tools."
The People Connections service provides social networking tools for creating, interacting with, and tracking the activities of one's connections. Its features enable users to manage their personal profiles, access the profiles of other users, provide ad hoc feedback, post messages, track activities, and connect with others.
It does this through a set of features that include:
Activity Stream for viewing user activities generated through application or social networking actions.
Connections for connecting to other application users to share information, comment on performance, exchange messages, and track activity
Feedback for giving ad hoc performance feedback to other users
Message Board for posting messages to other users
Profile for entering personal contact information and viewing the contact information of other users
Publisher for publishing status messages and posting files and links
The features of the People Connections service fall into the above five categories. Each category includes a set of task flows that expose People Connections features to end users.
See Also:
For information on adding People Connections functionality to a portal, see the "Adding Connections to a Portal" chapter in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.
Always use the Fusion Middleware Control or WLST command-line tool to review and configure back-end services for WebCenter Portal and Portal Framework applications. Any changes you make to WebCenter Portal or Portal Framework applications, post deployment, are stored in MDS metadata store as customizations. See Section 1.3.5, "Oracle WebCenter Portal Configuration Considerations."
Note:
Most changes you make to WebCenter Portal tools and services configuration through Fusion Middleware Control or using WLST are not dynamic. For your changes to take effect, you must restart the managed server in which the application is deployed. See Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."
For additional information about configuring People Connections, refer to Section 16.3, "Configuring People Connections for WebCenter Portal."
To use the People Connections service, you must have the WEBCENTER schema installed in your database.
In a production environment, an enterprise can leverage its back-end identity store as a means of providing People Connections with a population of potential connections. In a development environment, developers can add test-users to the jazn-data.xml
file.
For example, Profile takes the bulk of its information from the back-end identity store that provides WebCenter Portal or your Portal Framework application with its users. Additionally, Profile may offer opportunities for altering some of this information and for providing additional data not included in the identity store.
For information about connecting to a back-end (LDAP) identity store for the production version of your application, see Chapter 31, "Configuring the Identity Store."
This section steps you through the process of setting application-wide values for People Connections features. It includes the following subsections:
To access People Connections administrative settings:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page."
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
Activity Stream provides a means of publishing and tracking users' application activity. Activity Stream configuration settings specify from which users and activities are streamed, who can see a user's streamed activities, and whether liking and commenting is available on each streamed activity (Figure 16-1).
Figure 16-1 Administration Settings for People Connections
Who can view a user's activities and the types of activities tracked depend on Activity Stream configuration. Table 16-1 lists the types of activities that may be tracked by Activity Stream.
Table 16-1 Activities Tracked by Activity Stream
Feature Area | Tracked Activities | Scope | Activities Shared or Private |
---|---|---|---|
Announcements |
|
Portal |
Shared with other portal members |
Blogs |
|
|
|
Connections |
|
Home portal |
Shared with invitor and invitee's connections |
Discussions |
|
Portal |
Shared with other portal members |
Documents |
|
|
|
Events |
|
Portal |
Shared with other portal members |
Feedback |
|
Home portal |
Shared with whomever is permitted to view such activities. (For more information, see the "Setting Feedback Preferences" section in Oracle Fusion Middleware Using Oracle WebCenter Portal.) |
Lists |
|
Portal |
Shared with other portal members |
Message Board |
|
Home portal |
Shared with whomever is permitted to view such activities. (For more information, see the "Setting Message Preferences" section in Oracle Fusion Middleware Using Oracle WebCenter Portal.) |
Pages |
|
|
|
Profiles |
|
Home portal |
Shared with whomever is permitted to view such activities. (For more information, see the "Setting Profile Preferences" section in Oracle Fusion Middleware Using Oracle WebCenter Portal.) |
WebCenter Portal Management |
|
Portal |
Shared with other portal members |
Tagging |
|
|
|
Activity Stream configuration falls under the following categories:
People—For determining whose activities to show, either the current user's or both the current user and the user's connections.
WebCenter Portal—For determining whether to show activities from all available portals or just the Home portal.
Service Categories—For selecting the services from which to report activities and enabling users to override these default selections in their personal preferences or preventing users from overriding.
Privacy—For selecting who may see the current user's activities.
Comments and Likes—For enabling users to comment on a posted activity and express a liking for a posted activity
To configure Activity Stream for all users:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page."
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
Click the Activity Stream tab to bring it forward.
Under People, select whose activities to show:
Only Me—Show only the current user's activities in his or her view of the Activity Stream.
Me and My Connections—Show the current user's activities and the activities of that user's connections in his or her view of the Activity Stream.
No Personal—Omit all activities streamed from Home portals in the current user's view of his or her Activity Stream.
Under Portals, select to show activities from:
All Portals—All portals to which the user has access
My Portals—All portals of which the user is the moderator
No Portals—Only the Home portal
Under Service Categories, select the services from which to publish activity.
Note:
The activities of services that are not selected are still tracked, but they do not appear in the Activity Stream. If you select to show the activities at some later point, then all of the activities that occurred when it was not selected will appear in the Activity Stream.
Table 16-1 lists the activities tracked by the Activity Stream.
Optionally, select Allow Owner Override to enable users to override a setting for a given service through their personal preferences.
Deselect this check box to prevent users from overriding the application defaults you set here.
Under Privacy, specify who can view the current user's activities and whether users can override this setting in their personal preferences.
Table 16-2 lists and describes each option.
Table 16-2 Activity Stream Privacy Options
Option | Description |
---|---|
Allow all of my activities to be viewed by |
Specify who can view another user's activities. Choose from:
|
Allow Owner Override |
Enable users to override the application default settings using their own People Connections Preferences (for more information, see the "Setting Activity Stream Preferences" section in Oracle Fusion Middleware Using Oracle WebCenter Portal). |
Expand the Likes and Comments node, and specify whether liking and commenting are allowed:
Select Enable comments on objects in the Activity Stream to enable users to comment on a given Activity Stream item. Deselect the check box to prevent users from commenting.
Select Enable others to like objects in the Activity Stream to enable users to express a liking for an Activity Stream item. Deselect the check box to prevent users from commenting.
Tip:
Users can like and comment on streamed items that include objects. For example, users can like or comment on "Jack has updated doc.xml," but cannot like or comment on "Jack and Jill are now connected."
For more information, see the "Liking, Commenting On, and Sharing Items in WebCenter Portal" chapter in Oracle Fusion Middleware Using Oracle WebCenter Portal.
Click Apply to save your configuration settings.
Connections configuration involves specifying who can view another user's connections and whether users accept invitations to connect automatically (Figure 16-2).
Figure 16-2 Configuration Settings for Connections
To configure Connections:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page"
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
Click the Connections tab to bring it forward.
Table 16-3 lists and describes each option.
Table 16-3 Connections Configuration Options
Option | Description |
---|---|
Grant View Access to |
Classes of users to whom to grant automatic view access to a user's connections The users you select can view and interact with another user's connections. Choose from:
|
Allow Owner Override |
Option to allow or prohibit users from overriding the administrator View access setting:
|
Accept Invitations Automatically |
|
Click Apply to save your configuration settings.
Every authenticated user has a profile that displays personal information, such as the user's email address, phone number, office location, department, manager, direct reports, and so on. All but three attributes are stored and read from the LDAP identity store that is configured for the WebCenter Portal. The three exceptions include the Profile photo and expertise and Publisher status messages.
Use administrative configuration settings for Profile to specify whether users are allowed to change their application passwords, which profile sections display, whether users are allowed to update their profile details, and the profile attributes that users may update (Figure 16-3).
Figure 16-3 Configuration Settings for Profile
Personal profiles are presented in four sections: Summary, Employee, Business Contact, Personal Information. Each section provides information related to the section heading. For example, Summary includes a collection of basic details, such as the user's name, email address, and office location.
In configuration settings, the access setting for the Summary section controls who can search for the user (for example, through global search, people pickers, and the searches one uses to find and invite other users to connect). For example, if Everyone is allowed to view the Summary section, then the user can be searched for by unauthenticated (public) users. If only Authenticated Users can view another user's Summary section, then only logged in users can search for the user. If None is the selected value for Who can view this section, then the user will not appear in search results.
The Summary section is the only Profile section for which the privacy setting cannot be changed by the end-user through Preferences (for more information, see the "Setting Profile Preferences" section in Oracle Fusion Middleware Using Oracle WebCenter Portal). It is controlled at a global level for all users through the settings described in this section.
It is the administrator's job to specify the information to show in each section and determine whether users are allowed to edit their profile data and their application password within the WebCenter Portal.
To configure Profile:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page"
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
Click the Profile tab to bring it forward.
Table 16-4 lists and describes each option.
Table 16-4 Profile Configuration Options
Option | Description |
---|---|
Allow Password Change |
Specify whether users are allowed to change their application password
|
Profile Access |
Specify which Profile sections to show and whether users are allowed to update their profile details Set application defaults in the following table columns: Profile Section—Identifies the groups of information shown in a user profile. View Settings—Specify which users can view a particular profile section, and indicate whether users can change these defaults in their personal Preferences. View Settings for the Summary section control not only who can view summary details but also for whom the user appears in people search results. Set values for:
Can Edit—Select to enable users to edit the associated profile section of their own personal profiles; deselect to prohibit users from editing the associated profile section. This setting also controls whether an Edit link appears in the Profile task flow, but it does not affect the appearance of the Edit button or links on the default version of the Profile page. You can use the other Profile administrative settings to prohibit users from actually changing any Profile details. |
Profile Attributes - Edit Settings |
Indicate the section attributes that users are allowed to edit by default Under Allow Update:
|
Profile Cache settings |
A means of enabling and configuring a cache for Profile details Provide values for:
Cache settings take effect once you restart the WebCenter Portal. |
Click Apply to save your configuration settings.
Message Boards provide users with a means of viewing and posting messages to their connections. Configuration settings for Message Board provide controls for who can view and post messages, who can edit and delete the messages they leave, who can delete and change the visibility of messages they receive, and whether commenting and liking are available on each message (Figure 16-4).
Figure 16-4 Configuration Settings for Message Board
See Also:
For information about likes and comments, see the "Liking, Commenting On, and Sharing Items in WebCenter Portal" chapter in Oracle Fusion Middleware Using Oracle WebCenter Portal.
To configure Message Board:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page"
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
Click the Message Board tab to bring it forward.
Table 16-5 lists and describes each option.
Table 16-5 Message Board Configuration Options
Option | Description |
---|---|
Grant View Access to |
Specify who can view Message Board messages.
|
Grant Post Access to |
Specify who can post Message Board Messages.
|
Allow Owner Override |
Specify whether users can override these administrative defaults.
|
Enable users to act on messages they post on other Message Boards |
Specify whether users are allowed to act on the messages they post.
|
Enable users to act on messages they received from others |
Specify whether users can act on messages they receive from others
|
Enable commenting on messages from Message Board |
Specify whether users can comment on messages that are posted on a Message Board.
|
Enable liking of messages from Message Board |
Specify whether to enable users to indicate that they like a message.
|
Click Apply to save your configuration settings.
Feedback provides a means of viewing and posting user feedback for other application users. Configuration settings for Feedback (Figure 16-5).
Figure 16-5 Configuration Settings for Feedback
Feedback configuration settings offer controls for identifying who can view, post, and delete feedback.
To configure Feedback:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page"
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
Click the Feedback tab to bring it forward.
Table 16-6 lists and describes each option.
Table 16-6 Feedback Configuration Options
Option | Description |
---|---|
Grant View Access to |
Specifies who can view the current user's Feedback
|
Grant Post Access to |
Specifies who can post user Feedback
|
Grant View Feedback Given Access to |
Specifies who can see the View menu to switch between Feedback Given and Feedback Received in a Feedback task flow
|
Allow Owner Override |
Specifies whether users can override these administrative defaults
|
Enable users to act on the feedback given to others |
Indicates whether users can delete the Feedback they post
|
Enable owner of the feedback to act on feedback posted by others |
Indicate whether to enable users to hide or show Feedback from another user.
|
Click Apply to save your configuration settings.
To enable external people connection feeds in WebCenter Portal or your Portal Framework application, you must set up a proxy server.
A proxy server is also required if you want to display external links in Activity Stream task flows. Both the People Connections service and the Activity Stream service share the same proxy server settings.
You can configure a proxy server by using either Fusion Middleware Control or WLST. For information, see Section 8.2.4, "Setting Up a Proxy Server."
Administrators can use WLST commands to archive and restore data in the Activity Stream schema. The following commands are available:
archiveASByDate
—Archive activity stream data that is older than a specified date.
archiveASByDeletedObjects
—Archive activity stream data associated with deleted objects.
archiveASByClosedSpaces
—Archive activity stream data associated with portals that are currently closed.
archiveASByInactiveSpaces
—Archive activity stream data associated with portals that have been inactive since a specified date.
restoreASByDate
—Restore archived activity stream data from a specified date into production tables.
truncateASArchive
—Truncates activity stream archive data.
archiveASBySpace
—Archive activity stream data associated with a portal.
archiveASAllSpaces
—Archive activity stream data associated with all portals.
archiveASByUser
—Archive activity stream data associated with a user.
archiveASAllUsers
—Archive activity stream data associated with all users.
archiveASByDeletedActors
—Archive activity stream data associated with deleted actors.
showASStatistics
—Report activity stream statistics.
For more information, see the "Activity Stream" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
The Organization View task flow and the Organization tab on a Profile page can provide a visualization of your management chain, that is, they can render a view of a manager and the manager's direct reports (Figure 16-6).
Figure 16-6 Organization View of a Manager and the Manager's Direct Reports
By default, the values that define the management chain for these organization views are blank. This means that managers are not automatically specified for users in the back-end identity store that provides user details.
Tip:
The value for Manager on the Profile page's About tab is also defined by the methods suggested in this section.
For the management chain to be rendered in organization views, the back-end identity store that is used for WebCenter Portal authentication must be set up in such a way that direct report users have a manager
attribute. And the manager
attribute must be defined as the Distinguished Name (DN) of their manager user (see "Example Embedded LDAP Configuration").
Tip:
In an LDAP environment, a user can be managed by only one person; in the same environment, a user can manage many people.
Example Embedded LDAP Configuration
You can specify a management chain within the Oracle WebLogic Server (WLS) embedded LDAP or within an external LDAP, such as Oracle Internet Directory (OID). However, the management chain you define through the embedded LDAP is for testing or proof of concept and not for production. For production, you must use an external LDAP, such as OID, for the identity store for WebCenter Portal authentication.
See Also:
For more information, see Chapter 31, "Configuring the Identity Store," or refer to the documentation provided with your LDAP implementation.
This example describes how to define a management chain within the embedded LDAP in WebLogic Server for testing or proof of concept.
Note:
The steps provided in this example are similar to those you take for an external LDAP. That is, you create an attribute (manager
) and set a value on the attribute for each user. For this value, enter the DN of the selected user's manager.
In this example, there are three users:
user1
user2
manager_user
To define a management chain with these users:
Enable browsing of the embedded LDAP using an external viewer, such as Apache Directory Studio:
Go to the WLS Administration Console, and log in as the administrator user.
Click your domain, for example, wc_domain, then open the Security Tab and then the Embedded LDAP Sub-tab (Figure 16-7).
Figure 16-7 Oracle WebLogic Server Administration Console
Enter a value in the Credential field, and then reenter that value in the Confirm Credential field.
Tip:
The default credential is a randomly generated password. Set it to something memorable.
Restart your administration and managed servers.
Start up the LDAP viewer you selected in Step 1, and create a connection using the following details:
hostname
(for example, example.com
)
port
(the WLS administration port, for example 7001
)
Bind DN
(cn=Admin
)
Password
(that is, the credential you set in Step 1c)
Navigate to user1
by finding the users within the DIT tree (Figure 16-8).
For example, click in succession:
dc=wc_domain
ou=myrealm
ou=people
uid=user1
Figure 16-8 Selecting a User in the DIT Tree of an LDAP Browser
In the Attribute Description column, add a new attribute of type manager
.
Tip:
Press Ctrl-Shift-+ to open the New Attribute dialog.
For the attribute value, select the DN for manager_user
(Figure 16-9).
For example, under the root, select in succession:
dc=wc_domain
ou=myrealm
ou=people
uid=manager_user
Repeat Steps 3 through 5 for user2
.
Now user1
and user2
are managed by manager_user
. You can check this by logging in to WebCenter Portal as user1
and navigating to the About tab of the Profile page. The user manager_user
is displayed as the manager (Figure 16-10).
Figure 16-10 About Tab of the Profile Page
Tip:
Click the value for Manager (in this example, manager_user
) to view the manager's profile. Access the Organization tab to see the organization view associated with the currently viewed profile.
Administrators can use WLST commands to set profile configuration properties, such as setting the profile version that appears in the user interface. Administrators can perform the following actions:
Set the profile configuration properties by running setProfileConfig
.
Syntax:
setProfileConfigProperties(appName,[ProfilePageVersion], [ProfileCacheNumberOfObjects], [ProfileCacheTimeToLive],[ProfileSyncLDAPReadBatchSize], [ProfileSyncHourOfDay], [ProfileSyncFrequencyInDays], [server],[applicationVersion])
This command takes the following parameters:
appName
- The name of the WebCenter Portal application in which to perform this operation. For example, webcenter
.
ProfilePageVersion
- (Optional) The profile page version to use. Valid values for ProfilePageVersion are:
v1
- Use old-style Profile pages (11.1.1.7.0 and earlier)
v2
- (default) Use the new Profile page format (introduced in 11.1.1.8.0)
Note:
Profile page version changes will not take effect until you restart the server on which the WebCenter Portal application is deployed.
ProfileCacheNumberOfObjects
- (Optional) The number of profile objects to keep in the profile cache. Any value between 1 and 10000. The default value is 1000.
ProfileCacheTimeToLive
- (Optional) The length of time (in minutes) to keep a profile object in the cache. Any value between 1 and 1440. The default value is 60.
ProfileSyncLDAPReadBatchSize
- (Optional) The LDAP read batch size that is used during profile synchronization. Any value between 1 and 1000. The default value is 1000.
ProfileSyncHourOfDay
- (Optional) When (the hour) to start profile synchronization. Any value between 0 and 23. The default value is 23, equivalent to 11pm.
ProfileSyncFrequencyInDays
- (Optional) How often profile synchronization takes place (in days). Any value greater than 0. The default value is 7.
Note:
If you omit a parameter, the corresponding configuration remains unchanged.
List the current profile configuration settings by running listProfileConfig
.
Syntax:
listProfileConfig(appName)
This command takes the following parameter:
appName
- The name of the WebCenter Portal application in which to perform this operation. For example, webcenter
.
Get the current value of a profile property by running getProfileConfig
.
Syntax:
getProfileConfig(appName, key, [server], [applicationVersion])
This command takes the following parameters:
appName
- The name of the WebCenter Portal application in which to perform this operation. For example, webcenter
.
key
- Name of a the Profile Config property to get. Valid values include:
ProfilePageVersion
ProfileCacheNumberofObjects
ProfileCacheTimeToLive
ProfileSyncLDAPReadBatchSize
ProfileSyncHourOfDay
ProfileSyncFrequencyInDays
server
- (Optional) The name of the target server on which the application is deployed.
applicationVersion
- (Optional) The version number of the application.
Administrators can use WLST commands to synchronize profile information in the LDAP identity store with WebCenter Portal. Administrators can perform the following actions:
Start or stop profile synchronization for all users or a single user by running startSyncProfiles
or stopSyncProfiles
.
Check whether profile synchronization is currently in progress by running isSyncProfilesRunning
.
Set various profile synchronization options:
Specify whether to synchronize user profile photos in LDAP by running setProfilePhotoSyncEnabled
.
Synchronize profile information for a specific user by running syncProfile
.
For more information, see the "WebCenter Portal Identity Store" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Administrators can also use the WebCenter Portal user interface to control the LDAP batch size and turn on or off photo synchronization:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page"
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
On the right, click the Profile tab.
To change the LDAP batch setting, under Profile Cache settings, set the LDAP read batch size for profile sync task as desired.
To turn on or off photo synchronization, select or clear the box next to Synchronize user profile photos with LDAP when the cache expires.
The Profile service caches objects to save processing bandwidth, presenting information more quickly to users. The following are the default cache options for the Profile service:
Maximum number of objects in the cache: 1000
If the maximum number of objects in the cache is reached, older objects or unused objects will be removed from the cache as additional objects are added.
Maximum idle time in cache: 60 seconds
If an object in the cache has not been accessed for the maximum idle time it will be removed from the cache.
If you find that the profile service is performing more slowly than you want, you might want to increase the thresholds in the cache settings. If you feel that the data presented by the profile service is not updating frequently enough, you might want to decrease the cache thresholds.
Administrators can configure the Profile service cache options through the WebCenter Portal user interface or with WLST commands:
To set cache options through the WebCenter Portal user interface:
Open WebCenter Portal Administration.
For details, see Section 47.2, "Accessing the Portal Builder Administration Page"
Click Tools and Services, and then select People Connections.
Alternatively, use the following URL, and then select People Connections:
http://host:port/webcenter/portal/admin/tools
Tabs with the names of People Connections features appear to the right.
On the right, click the Profile tab.
Under Profile Cache settings, set the Number of profile objects to keep in cache and Length of time to keep a profile object in cache (in minutes) settings as desired.
To set cache options through WLST, use the setProfileConfig
command, described in Section 16.7, "Setting Profile Configuration Properties."
For command syntax and examples, see the "WebCenter Portal Identity Store" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."
This section provides information to assist you in troubleshooting problems you may encounter while using People Connections.
Profile photos added to WebCenter Portal using the JDeveloper workspace SampleWebCenterSpacesExtensions.jws
do not display
If you used WebCenter Portal's SampleWebCenterSpacesExtensions.jws
workspace to add profile photos, but old profile photos continue to be shown, complete the following steps to delete the current photo data from the database:
Determine the GUID associated with the user using the following EL expression in the portal:
#{webCenterProfile[securityContext.userName].guid}
Using SQLPlus, log in to the WebCenter Portal database as DBA (or another administrative user), and execute the following commands:
DELETE FROM WcPeopleConnProfilePhoto photo WHERE photo.userGuid =USER_GUID;
Replace USER_GUID
with the user GUID you recorded in step 1.