11 Managing Services

11.1.2.1 Discussion Server - Installation

The Oracle WebCenter Discussions software is available on the companion CD provided with Oracle Fusion Middleware. For information on installation, see Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

11.1.2.2 Discussion Server - Configuration

Oracle recommends using same Oracle Internet Directory (OID)-LDAP server for identity management in the discussion server and the WebCenter application. If you are not using OID-LDAP for identity management across the discussion server and the WebCenter application that uses the Discussions service, then users must be configured in the discussion server using the admin user interface at http://<host>:<port>/owc_discussions/admin. For more information, see the Jive Forums documentation on the WebCenter product page in the Fusion Middleware documentation library.

For information on reassociating the identity store, see Section 14.3, "Configuring the Identity Store."

11.1.2.3 Discussion Server - Security Considerations

By default, the Oracle WebCenter Discussions allows unsecured Web service calls. You can optionally configure Oracle WebCenter Discussions to enable the Web Services Security (WS-Security) trusted authentication. WS-Security establishes a trust relationship between your WebCenter application and Oracle WebCenter Discussions so that your WebCenter application can pass the user identity information to the server without knowing the user's credentials.

To enable the WS-Security trusted authentication for Oracle WebCenter Discussions, you must:

• Obtain a valid client and server certificate.

• Configure WS-Security-related properties on the system that hosts Oracle WebCenter Discussions.

• Add the WS-Security-related properties in your Oracle WebCenter Discussions connection created for integrating Discussions and Announcements services into your WebCenter applications. See also, Table 11-4, "Additional Discussion Connection Properties".

To configure WS-Security, on the server side you must edit the keystore certificate and delete the webservices.soap.permissionHandler.className system property.

For details, see Section 14.8.2, "Securing the Discussions Server with WS-Security."

11.1.2.4 Discussion Server - Limitations

Oracle WebCenter Discussions cannot be started or stopped from WebLogic Server Admin Console. To start or stop the discussion server, you must start or stop the WLS_Services managed server where Oracle WebCenter Discussions is deployed.

After Oracle WebCenter Discussions has been installed from the WebCenter installation, the only user name/password it will accept is weblogic/weblogic (regardless of the name/password you enter during installation). To change the password or to create another system admin user in the discussion server, you first must log on with weblogic/weblogic. For more information, see "Granting Administrator Role to a Non-Default User" in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

The Oracle WebCenter Discussions URL supports only English and Spanish languages for displaying lables; however, data can be entered in UTF-8 format. Oracle recommends to use the WebCenter application (with all WebCenter-supported languages) for user operations in the discussion server. All WebCenter-supported languages are supported for data, such as discussion topics or announcements, and they are displayed in discussion server also.

(WebCenter Spaces) Do not change user permissions in the discussion server, as this might cause unexpected behavior. Always manage user permissions for discussions and announcements in WebCenter Spaces. See also Section 19.1.4, "Understanding Discussions Server Role and Permission Mapping."

11.1.3.1 Registering Discussion Servers Using Fusion Middleware Control

To register a discussion server connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Discussions and Announcements.

4. To connect to a new discussion server, click Add (Figure 11-1).

   Figure 11-1 Configuring Discussion and Announcement Connections

   
   

5. Enter a unique name for this connection, and indicate whether this connection is the active (or default) connection for the application.

   See also, Table 11-1, "Discussion and Announcement Connection - Name".

   Table 11-1 Discussion and Announcement Connection - Name

   Field	Description
   Connection Name	Enter a unique name for the connection. The name must be unique (across all connection types) within the WebCenter application.
   Active Connection	Select to use this connection for discussion and announcement services in the WebCenter application. While you can register multiple discussion server connections for a WebCenter application, only one connection is used for discussion and announcement services— the default (or active) connection.

   
   

6. Enter connection details for the discussion server. For details, see Table 11-2, "Discussion and Announcement Connection - Connection Details".

   Table 11-2 Discussion and Announcement Connection - Connection Details

   Field	Description
   Server URL	Enter the URL of the discussion server hosting Discussions and Announcements. For example: http://discuss-server.com:8888/owc_discussions
   Administrator User Name	Enter the user name of the discussion server administrator. This account is used by the Discussions and Announcement services to perform administrative operations on behalf of WebCenter users. In WebCenter Spaces, this account is mostly used for managing group space discussions and announcements. It is not necessary for this user to be a super admin. However, the user must have administrative privileges on the application root category configured for the WebCenter Spaces, that is, the category (on the discussion server) under which all group space discussions and announcement are stored.
   Connection Secured	Indicate whether a secured (WS-Security) discussion server connection should be established. If selected, that is, a secure connection is required, use the Additional Properties section to specify the keystore information. See also, Table 11-4, "Additional Discussion Connection Properties".

   
   

7. Configure advanced options for the discussion and announcement connection. For details, see Table 11-3, "Discussion and Announcement Connection - Advanced Configuration".

   Table 11-3 Discussion and Announcement Connection - Advanced Configuration

   Field	Description
   Connection Timeout (in Seconds)	Specify a suitable timeout for the connection. This is the length of time (in seconds) the WebCenter application waits for a response from the discussion server before issuing a connection timeout message. The default is -1 which means that the service default is used. The service default is 10 seconds.

   
   

8. Sometimes, additional parameters are required to connect to the discussion server.

   For example, those listed in Table 11-4, "Additional Discussion Connection Properties".

   Table 11-4 Additional Discussion Connection Properties

   Additional Connection Property	Description
   keystore.location	Certificate file path in your local directory. Keystore information is needed only when the discussion forum connection should communicate with the discussion server over WS-Security. For more information, see Section 11.1.2.3, "Discussion Server - Security Considerations."
   keystore.password	Keystore password.
   keystore.type	Keystore type associated with the certificate. Valid values are: jks (Java Key Store) and pks.
   encryption.key.alias	Key alias to be used for encryption.
   encryption.key.password	Password for accessing the encryption key.
   group.mapping	(WebCenter Spaces only) Determines whether a subcategory or a single forum is created on the discussion server for new group spaces. When set to forum (the default), a single forum is created under the application root category per group space. When set to category, a subcategory is created under the application root category per group space. When a subcategory that supports multiple forums is more suitable, set group.mapping to category. If a group space template has been configured with forum-based taxonomy, then the template takes precedence over this connection entry. If a group space template does not define the mapping (the Blank template, for example), then this group.mapping property is used. If there is no value in the template or the connection, then the default setting is used (forum).

   
   

   If additional parameters are required to connect to the discussion server, expand Additional Properties and enter details as required (see Table 11-5, "Discussion and Announcement Connection - Additional Properties").

   Table 11-5 Discussion and Announcement Connection - Additional Properties

   Field	Description
   Add	Click Add to specify an additional connection parameter: Name -Enter the name of the connection property. Value - Enter the default value for the property. Is Property Secured - Indicate whether encryption is required. When selected, the property value is stored securely using encryption. For example, select this option to secure the admin.password property where the value is the actual password.
   Delete	Click Delete to remove a selected property. Select the correct row before clicking Delete. Note: Deleted rows appear disabled until you click OK.

   
   

9. Click OK to save this connection.

10. To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

For WebCenter Spaces, some additional configuration is recommended for the Discussions service. For details, see Section 18.8, "Setting Discussion Forum Options."

11.1.3.2 Registering Discussion Servers Using WLST

Use the WLST command createDiscussionForumConnection to create a discussion server connection. For command syntax and examples, see "createDiscussionForumConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To configure the Discussions and Announcements services to actively use the new discussion server connection, set default=true.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.1.4.1 Choosing the Active Connection for Discussions and Announcements Using Fusion Middleware Control

To change the active connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Discussions and Announcements.

   The Manage Discussion and Announcement Connections table indicates the current active connection (if any).

4. Select the connection you want to make the active (or default) connection, and then click Edit.

5. Select the Active Connection check box.

6. Click OK to update the connection.

7. To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.1.4.2 Choosing the Active Discussion for Discussions and Announcements Using WLST

Use the WLST command setDiscussionForumConnection with default=true to activate an existing discussion server connection. For command syntax and examples, see "setDiscussionForumConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To disable a Discussions and Announcements connection, either delete it, make another connection the 'active connection', or use the removeDiscussionForumServiceProperty command:

removeDiscussionForumServiceProperty('appName='webcenter', property='selected.connection')

Using this command, connection details are retained but the connection is no longer named as an active connection. See also, "removeDiscussionForumServiceProperty".

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.1.5.1 Modifying Discussion Server Connection Details Using Fusion Middleware Control

To update discussion server connection details:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Discussions and Announcements.

4. Select the connection name, and click Edit.

5. Edit connection details, as required. For detailed parameter information, see Table 11-2, "Discussion and Announcement Connection - Connection Details" and Table 11-4, "Additional Discussion Connection Properties".

6. Click OK to save your changes.

7. To start using the updated (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments".

11.1.5.2 Modifying Discussion Server Connection Details Using WLST

Use the WLST command setDiscussionForumConnection to edit discussion server connection details. For command syntax and examples, see "setDiscussionForumConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

If additional parameters are required to connect to your discussion server, use the setDiscussionForumConnectionProperty command. For details, see "setDiscussionForumConnectionProperty".

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.1.6.1 Deleting a Discussion Server Connection Using Fusion Middleware Control

To delete a discussion server connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Discussions and Announcements.

4. Select the connection name, and click Delete.

5. To effect this change you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

   Note:

   Before restarting the managed server, mark another connection as active; otherwise, the service will be disabled.

11.1.6.2 Deleting a Discussion Server Connection Using WLST

Use the WLST command deleteConnection to remove a discussion server connection. For command syntax and examples, see "deleteConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

Ensure that another connection is marked active; otherwise, the service will be disabled.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.2.2.1 Oracle WebLogic Communications Server (OWLCS) Prerequisites

For OWLCS prerequisites, see the Oracle WebLogic Communication Services Installation Guide.

11.2.2.2 Microsoft Live Communications Server (LCS) Prerequisites

11.2.3.1 Registering Instant Messaging and Presence Servers Using Fusion Middleware Control

To register a presence server connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Instant Messaging and Presence.

4. To connect to a new presence server, click Add (Figure 11-6).

   Figure 11-6 Configuring Instant Messaging and Presence Services

   
   

5. Enter a unique name for this connection, specify the presence server type, and indicate whether this connection is the active (or default) connection for the application.

   See also, Table 11-6, "Instant Messaging and Presence Connection - Name".

   Table 11-6 Instant Messaging and Presence Connection - Name

   Field	Description
   Name	Enter a unique name for the connection. The name must be unique (across all connection types) within the WebCenter application.
   Connection Type	Specify the type of presence server you want to connect to: OWLCS - Oracle WebLogic Communications Server LCS - Microsoft's Live Communication Server Out-of-the-box, two presence connection types are available— OWLCS and LCS.
   Active Connection	Select to use this connection in the WebCenter application for instant messaging and presence services. While you can register multiple presence server connections for a WebCenter application, only one connection is used by the Instant Messaging and Presence service— the default (or active) connection.

   
   

6. Enter connection details for the server hosting instant messaging and presence services.

   For detailed parameter information, see Table 11-7, "Instant Messaging and Presence Connection - Connection Details".

   Table 11-7 Instant Messaging and Presence Connection - Connection Details

   Field	Description
   Server URL	Enter the URL of the sever hosting instant messaging and presence services. For example: http://myowlcshost.com:8888
   Domain	Enter the domain associated with this connection. The domain specified is used to construct each user's IM ID. For example, if the domain is oracle.com and presence is requested for user with name john then the IM address resolved will be john@oracle.com. If the user IM address needs to be resolved from the OID/LDAP server, then specify the user profile attribute that will provide the IM address here as profile:<attribute> where profile is a keyword and attribute is the user profile attribute name where the IM address is stored. For example, profile:primarySipAddress. The IM ID for OWLCS and LCS will be the SIP ID; that is, sip:john@oracle.com. SIP s short for Session Initiation Protocol - an Internet protocol for live communication between people.
   Administrator User Name	(OWLCS Only) Enter the user name of the presence server administrator. Administrative privileges are required for this connection so that operations can be performed on behalf of WebCenter users.
   Administrator Password	(OWLCS Only)Enter the password for the administrator.
   Authentication Method	(OWLCS Only) Specify how to authenticate users against the instant messaging and presence server. Choose from: Identity Propagation - Select this option if you want the application and OWLCS to use the same user identity. External Application - Use an external application to authenticate users against the instant messaging and presence server. Select this option if you want to use public, shared, or mapped credentials. If an external application is used for authentication, use the Associated External Application drop down list to identify the application. If the application you want is not listed, select Create New... to define the external application now.
   Associated External Application	Associate the instant messaging and presence server with an external application. External application credential information is used to authenticate users against the instant messaging and presence server. An external application is mandatory for LCS server connections. You can select an existing external application from the drop-down list, or click Create New to configure a new external application. The external application you configure for the Instant Messaging and Presence service must use the POST authentication method, and specify an additional field named Account (Name property) that is configured to Display to User (checked). See also Chapter 13, "Managing External Applications."
   LCS Pool Name	(LCS Only) Enter the name of the Microsoft Live Communication Server pool used for this connection. The pool name is mandatory for LCS connections. Refer to Microsoft Live Communication Server documentation for details on the pool name.
   Connection Timeout (in seconds)	Specify a suitable timeout for the connection. This is the length of time (in seconds) the WebCenter application waits for a response from the presence server before issuing a connection timeout message. The default is -1 which means that the service default is used. The service default is 10 seconds.
   Policy URI	(OWLCS Only) URI to the WS-Security policy that is required for authentication on the Oracle WebLogic Communication Server. Specify oracle/wss11_saml_token_with_message_protection_client_policy when OWLCS is WS-Security enabled.

   
   

7. Sometimes, additional parameters are required to connect to the presence server.

   If WS-Security is enabled on this connection, add an additional property named recipient.alias and enter the alias used to import the OWLCS certificate. Ensure that this value is unique and is not used already by some other service. If no alias name is supplied, then the default value is used (webcenter_owlcs).

   Table 11-8, "Additional IMP Connection Properties" lists additional parameters.

   Table 11-8 Additional IMP Connection Properties

   Additional Connection Property	Description
   presence.url	(OWLCS only) URL to the OWLCS Presence service. Required if the OWLCS Presence service is deployed on a separate node. When no value is specified, the Server URL property is used.
   contacts.url	(OWLCS only) URL to the OWLCS Contact Management service. Required if the OWLCS Contact Management service is deployed on a separate node. When no value is specified, the Server URL property is used.
   call.url	(OWLCS only) URL to the OWLCS Third Party Call service. Required if the OWLCS Third Party Call service is deployed on a separate node. When no value is specified, the Server URL property is used.
   call.method	(OWLCS only) Third party call method. Valid values are: sip and pstn. The default value is sip. When set to sip, the IMP service will forward the user's SIP address to the third-party call service. The third-party call service must decide on the routing of the call. If it is set to pstn, then the user's phone number is based on the user's profile attribute (BUSINESS_PHONE). This default profile attribute (BUSINESS_PHONE) can be changed to any other attribute with the connection property call.number.attribute.
   call.domain	(OWLCS only) Domain name of the PSTN gateway. Required when the call.method is pstn.
   contact.number.attribute	(OWLCS only) User profile attribute used to store users' phone numbers. The default attribute is BUSINESS_PHONE. Required when the call.method is pstn.
   primary.domain	(OWLCS and LCS) User domain. This property is required when WebCenter user names are qualified with a domain. For example, when user names are xyz@example.com, the primary.domain is example.com. This property is used by IMPAddressResolver to resolve user names to sip-address, and vice-versa. If this property is not supplied, then there could be inconsistencies in the resolver functions, which can affect IMP service performance.

   
   

   If additional parameters are required to connect to the presence server, expand Additional Properties and enter details as required (see Table 11-9, "Instant Messaging and Presence Connection - Additional Properties").

   Table 11-9 Instant Messaging and Presence Connection - Additional Properties

   Field	Description
   Add	Click Add to specify an additional connection parameter: Name -Enter the name of the connection property. Value - Enter the default value for the property. Is Property Secured - Indicate whether encryption is required. When selected, the property value is stored securely using encryption. For example, select this option to secure the admin.password property where the value is the actual password.
   Delete	Click Delete to remove a selected property. Select the correct row before clicking Delete. Note: Deleted rows appear disabled until you click OK.

   
   

8. Click OK to save this connection.

9. To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.2.3.2 Registering Instant Messaging and Presence Servers Using WLST

Use the WLST command createIMPConnection to create a presence server connection. For command syntax and examples, see "createIMPConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

To configure the Instant Messaging and Presence service to actively use a new IMP connection, set default=true. See also, Section 11.2.4.2, "Choosing the Active Connection for Instant Messaging and Presence Using WLST."

11.2.4.1 Choosing the Active Connection for Instant Messaging and Presence Using Fusion Middleware Control

To change the active connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Instant Messaging and Presence.

   The Manage Instant Messaging and Presence Connections table indicates the current active connection (if any).

4. Select the connection you want to make the active (or default) connection, and then click Edit.

5. Select the Active Connection check box.

6. Click OK to update the connection.

7. To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.2.4.2 Choosing the Active Connection for Instant Messaging and Presence Using WLST

Use the WLST command setIMPConnection with default=true to activate an existing presence server connection. For command syntax and examples, see "setIMPConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To disable a presence server connection, either delete it, make another connection the 'active connection' or use the removeIMPServiceProperty command:

removeIMPServiceProperty('appName='webcenter', property='selected.connection')

Using this command, connection details are retained but the connection is no longer named as an active connection. See also, "removeIMPServiceProperty".

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.2.5.1 Modifying Instant Messaging and Presence Connections Details Using Fusion Middleware Control

To update connection details for an instant messaging and presence server:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Instant Messaging and Presence.

4. Select the connection name, and click Edit.

5. Edit connection details, as required. For detailed parameter information, see Table 11-7, "Instant Messaging and Presence Connection - Connection Details".

6. Click OK to save your changes.

7. To start using the updated (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.2.5.2 Modifying Instant Messaging and Presence Connections Details Using WLST

Use the WLST command setIMPConnection to edit presence server connection details. For command syntax and examples, see "setIMPConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

If additional parameters are required to connect to your presence server, then use the setIMPConnectionProperty command. For details, see "setIMPConnectionProperty".

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.2.6.1 Deleting Instant Messaging and Presence Connections Using Fusion Middleware Control

To delete an instant messaging and presence server connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Instant Messaging and Presence.

4. Select the connection name, and click Delete.

5. To effect this change you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

   Note:

   Before restarting the managed server, mark another connection as active; otherwise, the service will be disabled.

11.2.6.2 Deleting Instant Messaging and Presence Connections Using WLST

Use the WLST command deleteConnection to remove a presence server connection. For command syntax and examples, see "deleteConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.3.2.1 Mail Server - Installation

Refer to your mail server documentation for installation information.

11.3.2.2 Mail Server - Configuration

To enable users to access mail services from within a WebCenter application, it is essential that users created on the mail server correspond with the users created in the identity store used by the WebCenter application.

For information about adding users on a mail server, refer to the mail server's product documentation. For more information about adding users to the application's identity store, see Section 14.3, "Configuring the Identity Store."

For group space distribution lists to work in WebCenter Spaces (or custom WebCenter applications leveraging the WebCenter Spaces group space management feature), WebCenter Spaces must use Microsoft Exchange where distribution lists are managed on an Active Directory server. Group space distribution lists are created automatically whenever a group space is created. To disable this feature with Microsoft Exchange, do not provide the LDAP (Active Directory) server details in the mail connection. See also, step 7 Section 11.3.3.1, "Registering Mail Servers Using Fusion Middleware Control."

11.3.2.3 Mail Server - Security Considerations

See Section 14.6.8, "Securing the WebCenter Spaces Connection to IMAP and SMTP with SSL."

11.3.2.4 Mail Server - Limitations

In WebCenter Spaces, the Mail service requires a Microsoft Exchange mail server connection to enable automatic group space distribution lists.

11.3.3.1 Registering Mail Servers Using Fusion Middleware Control

To register a mail server with WebCenter applications:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Mail Server.

4. To connect to a new mail server, click Add (Figure 11-7).

   Figure 11-7 Configuring Mail Servers

   
   

5. Enter a unique name for this connection, and indicate whether this connection is the active (or default) connection for the application.

   See also, Table 11-10, "Mail Server Connection - Name".

   Table 11-10 Mail Server Connection - Name

   Field	Description
   Name	Enter a unique name for the connection. The name must be unique (across all connection types) within the WebCenter application.
   Active Connection	Select to indicate whether this connection is the default (or active) connection for the Mail service. You can register multiple mail server connections: WebCenter Spaces supports multiple mail connections. The mail connection marked active is the default connection for mail services in WebCenter Spaces. All additional connections are offered as alternatives; WebCenter Spaces users can choose which one they want to use through user preferences. Custom WebCenter applications only use one mail connection—the connection marked active. Any additional connections are ignored.

   
   

6. Enter connection details for the mail server. For detailed parameter information, see Table 11-11, "Mail Server Connection Parameters".

   Table 11-11 Mail Server Connection Parameters

   Field	Description
   IMAP Host	Enter the hostname of the machine where the IMAP (Internet Message Access Protocol) service is running.
   IMAP Port	Enter the port on which the IMAP service listens.
   IMAP Secured	Indicate whether a secured connection (SSL) is required for incoming mail over IMAP. Valid values are true and false. The default is false.
   SMTP Host	Enter the hostname of the machine where the SMTP (Simple Mail Transfer Protocol) service is running.
   SMTP Port	Enter the port on which the SMTP service listens.
   SMTP Secured	Indicate whether a secured connection (SSL) is required for outgoing mail over SMTP. Valid values are true and false. The default is false.
   Associated External Application	(Mandatory) Associate the mail server with an external application. External application credential information is used to authenticate users against the IMAP and SMTP servers. The Mail service will use the same credentials to authenticate the user on both IMAP and SMTP. You can select an existing external application from the drop-down list, or click Create New to configure a new external application. The external application you configure for the Mail service must use the POST authentication method, and specify an additional field named Email Address (Name property) that is configured to Display to User (checked). See also Chapter 13, "Managing External Applications." If your WebCenter application offers a self-registration page with the facility to email user ID information on request, then you must ensure that public credentials are configured for the external application selected here. If public credentials are not defined, then emails cannot be sent to users on their request. WebCenter Spaces offers this feature on its self-registration page.

   
   

7. Specify LDAP connection details for the Active Directory server managing group space distribution lists. For detailed parameter information, see Table 11-12, "LDAP Directory Server Configuration Parameters".

   This section applies to WebCenter Spaces (or custom WebCenter applications leveraging the WebCenter Spaces group space management feature). WebCenter applications support Microsoft Exchange where distribution lists are managed on an Active Directory server.

   Note:

   Active Directory server details must be provided as part of the mail connection for group space distribution lists to work.

   Table 11-12 LDAP Directory Server Configuration Parameters

   Field	Description
   LDAP Host	Enter the hostname of the machine where the LDAP directory server (Lightweight Directory Access Protocol) is running.
   LDAP Port	Enter the port on which the LDAP directory server listens.
   LDAP Base DN	Enter the base distinguished name for the LDAP schema. For example, CN=Users,DC=oracle,DC=com.
   LDAP Domain	Enter the domain that will be appended to distribution list names In WebCenter Spaces, for example, if the domain value is set to oracle.com, then the Finance Project group space will maintain a distribution list named FinanceProject@oracle.com.
   LDAP Administrator User Name	Enter the user name of the LDAP directory server administrator. A valid user with privileges to make entries into the LDAP schema.
   LDAP Administrator Password	Enter the password for the LDAP directory server administrator. The password will be stored in a secured store.
   LDAP Default User	Enter a comma-delimited list of user names to whom you want to grant moderation capabilities. These users become members of every group space distribution list that is created. The users specified must exist in the base LDAP schema (specified in the LDAP Base DN field).
   LDAP Secured	Indicate whether a secured connection (SSL) is required between the WebCenter application and the LDAP directory server.

   
   

8. Configure advanced options for the mail server connection. For details, see Table 11-13, "Mail Server Connection - Advanced Configuration".

   Table 11-13 Mail Server Connection - Advanced Configuration

   Field	Description
   Connection Timeout (in Seconds)	Specify a suitable timeout for the connection. This is the length of time (in seconds) the WebCenter application waits for a response from the mail server before issuing a connection timeout message. The default is -1. When set to -1, the service default (10 seconds) applies.

   
   

9. Optional parameters can be added to the mail server connection. For example, those listed in Table 11-14, "Additional Mail Connection Properties".

   Table 11-14 Additional Mail Connection Properties

   Additional Connection Property	Description
   Various IMAP properties	Any valid IMAP connection property. For example, mail.imap.connectionpoolsize. For all valid list of protocol properties, see your mail server documentation. For a list of standard IMAP properties, see the Java Mail APIs: http://java.sun.com/products/javamail/javadocs/com/sun/mail/imap/package-summary.html
   Various SMTP properties	Any valid SMTP connection property. For example, mail.smtp.timeout. For all valid list of protocol properties, see your mail server documentation. For a list of standard SMTP properties, see the Java Mail APIs: http://java.sun.com/products/javamail/javadocs/com/sun/mail/smtp/package-summary.html

   
   

   If additional parameters are required to connect to the mail server, expand Additional Properties and enter details as required (see Table 11-15, "Mail Connection - Additional Properties").

   Table 11-15 Mail Connection - Additional Properties

   Field	Description
   Add	Click Add to specify an additional connection parameter: Name -Enter the name of the connection property. Value - Enter the default value for the property. Is Property Secured - Indicate whether encryption is required. When selected, the property value is stored securely using encryption. For example, select this option to secure the admin.password property where the value is the actual password.
   Delete	Click Delete to remove a selected property. Select the correct row before clicking Delete. Note: Deleted rows appear disabled until you click OK.

   
   

10. Click OK to save this connection.

11. To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.3.3.2 Registering Mail Servers Using WLST

Use the WLST command createMailConnection to create a mail server connection. For command syntax and examples, see "createMailConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To configure the Mail service to use the new mail server connection as its default connection, set default=true. See also, Section 11.3.4.2, "Choosing the Active (or Default) Mail Server Connection Using WLST."

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.3.4.1 Choosing the Active (or Default) Mail Server Connection Using Fusion Middleware Control

To change the default connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Mail Server.

   The Manage Mail Server Connections table indicates the current active connection (if any).

4. Select the connection you want to make the active (or default) connection, and then click Edit.

5. Select the Active Connection check box.

6. Click OK to update the connection.

7. To start using the new default connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.3.4.2 Choosing the Active (or Default) Mail Server Connection Using WLST

Use the WLST command setMailConnection with default=true to make an existing mail server connection the default connection for the Mail service. For command syntax and examples, see "setMailConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

A connection does not cease to be the default connection for the Mail service if you change the default argument from true to false.

To disable a mail connection, either delete it, make another connection the 'active connection', or use the removeMailServiceProperty command:

removeMailServiceProperty(appName='webcenter', property='selected.connection')

Using this command, connection details are retained but the connection is no longer named as an active connection. See also, "removeMailServiceProperty".

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.3.5.1 Modifying Mail Server Connection Details Using Fusion Middleware Control

To update mail server connection details:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Mail Server

4. Select the connection name, and click Edit.

5. Edit connection details, as required. For detailed parameter information, see Table 11-11, "Mail Server Connection Parameters".

6. Click OK to save your changes.

7. To start using updated connection details you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.3.5.2 Modifying Mail Server Connection Details Using WLST

Use the WLST command setMailConnection to edit existing mail server connection details. For command syntax and examples, see "setMailConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

If additional parameters are required to connect to your mail server, use the setMailConnectionProperty command. For details, see "setMailConnectionProperty".

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.3.6.1 Deleting a Mail Connection Using Fusion Middleware Control

To delete a mail server connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Mail Server.

4. Select the connection name, and click Delete.

5. To effect this change you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

   Note:

   Before restarting the managed server, mark another connection as active; otherwise, the service will be disabled.

11.3.6.2 Deleting a Mail Connection Using WLST

Use the WLST command deleteConnection to remove a mail server connection. For command syntax and examples, see "deleteConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.4.2.1 Oracle Secure Enterprise Search - Installation

For information on installation, see "Back-End Requirements for the Search Service" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

11.4.2.2 Oracle Secure Enterprise Search - Configuration

Make sure you have a trusted federated entity on the Oracle SES instance for the current instance of WebCenter.

For secure searches, your WebCenter application and your Oracle SES instance must be using the same identity management system.

11.4.2.3 Oracle Secure Enterprise Search - Security

See Section 14.6.9, "Securing the WebCenter Spaces Connection to Oracle SES with SSL."

11.4.2.4 Oracle Secure Enterprise Search - Limitations

None.

11.4.3.1 Registering SES Search Services Using Fusion Middleware Control

To register an Oracle Secure Enterprise Search server with WebCenter Spaces:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Search.

4. To connect to a new Oracle SES instance, click Add (Figure 11-8).

   Figure 11-8 Configuring Oracle Secure Search Services

   
   

5. Enter a unique name for this connection, and indicate whether this connection is the active (or default) connection for the application.

   See also, Table 11-16, "Search Connection - Name".

   Table 11-16 Search Connection - Name

   Field	Description
   Name	Enter a unique name for the connection. The name must be unique (across all connection types) within the WebCenter application.
   Active Connection	Select to use the SES instance defined on this connection to search repositories outside the WebCenter application and include Oracle SES search results in your result set.

   
   

6. In the Connection Name field, enter a unique name for the search connection.

7. Enter connection details for the Oracle Secure Enterprise Search instance.

   For detailed parameter information, see Table 11-17, "Oracle Secure Enterprise Search - Connection Details".

   Table 11-17 Oracle Secure Enterprise Search - Connection Details

   Field	Description
   SOAP URL	Enter the Web Services URL that Oracle SES exposes to enable search requests. Use the format: http://<host>:<port>/search/query/OracleSearch For example: http://myHost:7777/search/query/OracleSearch
   Application User Name	Enter the user name of the Oracle SES Federation Trusted Entity. Tip: This user is configured under Global Settings - Federation Trusted Entities (Oracle SES administration pages). The user must be present in both the Oracle Identity Management server configured for your WebCenter application and the Oracle Identity Management server configured for Oracle SES. The WebCenter application must authenticate itself as a trusted application to Oracle SES so that it may perform searches on behalf of WebCenter users.
   Application Password	Enter the appropriate user password.

   
   

8. Configure additional options for the Oracle Secure Enterprise Search connection.

   Note:

   With the exception of the "Oracle Secure Enterprise Search Data Group" parameter, configuration options are not specific to the current SES connection.

   For detailed parameter information, see Table 11-18, "Oracle Secure Enterprise Search - Advanced Configuration".

   Table 11-18 Oracle Secure Enterprise Search - Advanced Configuration

   Field	Description
   Oracle Secure Enterprise Search Data Group	Specify the Oracle SES data group in which to search. If a value is not provided, then everything in the Oracle SES instance will be searched.
   Execution Timeout	Enter the maximum time that a service is allowed to execute a search (in ms).
   Executor Preparation Timeout	Enter the maximum time that a service is allowed to initialize a search (in ms).
   Number of Saved Searches	Enter the number of saved searches displayed in the Saved Search drop down (on main search page).
   Results per Service - Saved Search Task Flows	Enter the number of search results displayed, per service, in a Saved Search task flow.
   Results per Service - Search Page	Enter the number of search results displayed, per service, for searches submitted from the main search page. Users can click Show All to see all the results.
   Results per Service - Search Toolbar	Enter the number of search results displayed, per service, for searches submitted from the global search toolbar.

   
   

9. Click OK to save this connection.

10. To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.4.3.2 Registering SES Services Using WLST

Use the WLST command createSESConnection to create a Oracle SES connection. Use setSESConnection to alter an existing Oracle SES connection. For command syntax and examples, see "createSESConnection" and "setSESConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To configure the WebCenter Search service to actively use a new SES connection, set default=true. See also, Section 11.4.4.2, "Choosing the Active Oracle Secure Enterprise Search (SES) Connection Using WLST."

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.4.4.1 Choosing the Active Oracle Secure Enterprise Search (SES) Connection Using Fusion Middleware Control

To change the active connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Search.

   The Manage Secure Enterprise Search Connections table indicates the current active connection (if any).

4. Select the connection you want to make the active (or default) connection, and then click Edit.

5. Select the Active Connection check box.

6. Click OK to update the connection.

7. To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.4.4.2 Choosing the Active Oracle Secure Enterprise Search (SES) Connection Using WLST

Use the WLST command setSESConnection with default=true to activate an existing Oracle SES connection. For command syntax and examples, see "setSESConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To subsequently disable an Oracle SES connection, run the same WLST command with default=false. Connection details are retained but the connection is no longer named as an active connection.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.4.5.1 Modifying Oracle Secure Enterprise Search (SES) Connection Details Using Fusion Middleware Control

To update connection details for an Oracle Secure Enterprise Search instance:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, choose Search.

4. Select the connection name, and click Edit.

5. Edit connection details, as required. For detailed parameter information, see Table 11-17, "Oracle Secure Enterprise Search - Connection Details".

6. Click OK to save your changes.

7. To start using the updated (active) connection you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.4.5.2 Modifying Search Service Properties Using WLST

Use the WLST command setSearchConfig to edit properties relating to the Search service, such as the number of search results displayed. For command syntax and examples, see "setSearchConfig" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.4.5.3 Modifying SES Connection Details Using WLST

Use the WLST command setSESConnection to edit an existing SES search connection. For command syntax and examples, see "setSESConnection " in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

Use the command setSearchSESConfig to set additional SES connection properties, such as the SES data group in which to search. For syntax details and examples, see "setSearchSESConfig".

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.4.6.1 Deleting Search Connections Using Fusion Middleware Control

To delete an Oracle Secure Enterprise Search server connection:

1. Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:

   • Section 6.2, "Navigating to the Home Page for WebCenter Spaces"

   • Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the Service Connection drop-down, choose Search.

4. Select the connection name, and click Delete.

5. To effect this change you must restart the managed server on which the WebCenter application is deployed. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

11.4.6.2 Deleting Search Connections Using WLST

Use the WLST command deleteConnection to remove a search connection. For command syntax and examples, see "deleteConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

11.5.1.1 BPEL Server - Installation and Configuration

For installation and configuration-related information, see the section "Back-End Requirements for the Worklist Service and WebCenter Spaces Workflows" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

11.5.1.2 BPEL Server - Security Considerations

The Worklist service displays tasks for the currently authenticated user. For WebCenter users to store and retrieve tasks on the BPEL server, their user names need to either exist in a shared user directory (LDAP), or set up similarly (same user name and password) on both the WebCenter application and the BPEL Server.

For example, if the user rsmith want to use the Worklist service to store and retrieve tasks from the BPEL server, you must ensure that the user rsmith exists (with the same password) on both the BPEL server and within your application.

For a secured connection to the Worklist service, a shared Oracle Single Sign-On (OSSO) between the WebCenter application and the Oracle SOA Suite instance must be configured. For information, see Section 14.7.2, "Configuring Oracle Single Sign-On (OSSO)."

For information on configuring WS-Security between SOA and WebCenter Spaces, see Section 14.8.1, "Securing the BPEL Server with WS-Security."

11.5.1.3 BPEL Server - Limitations

None.

11.5.2.1 What You Should Know About Worklist Connections

The Worklist service enables WebCenter applications to show authenticated users a list of BPEL worklist items currently assigned to them through the Worklist task flow. BPEL worklist items are open BPEL tasks from one or more BPEL worklist repository.

A connection to every BPEL server that must delivering worklist items is required. Multiple worklist connections are allowed so that WebCenter users can monitor and manage assignments and notifications from a range of BPEL servers.

Worklist connection details are stored in connections.xml. Another file, adf-config.xml, identifies which connections are actively used by the Worklist service.

If, for any reason, a BPEL server cannot be contacted, the Worklist will indicate that the connection is unavailable.

WebCenter Spaces

The WebCenter Spaces application requires a BPEL server connection to support its internal workflows, that is, group space membership notifications and group space subscription requests. The BPEL server providing this functionality is always a BPEL server included with the Oracle SOA Suite. See also, Specifying the BPEL Server Hosting WebCenter Spaces Workflows.

The Worklist service can share the SOA instance connection and by doing so, display worklist items relating to group space activity in each user's Worklist task flow.

11.5.2.2 Registering Worklist Connections

This section contains the following subsections:

• Registering Worklist Connections Using Fusion Middleware Control

• Registering Worklist Connections Using WLST

11.5.2.3 Activating a Worklist Connection

In WebCenter applications, multiple Worklist connections may be active at a time. This enables WebCenter users to monitor and manage assignments and notifications from a multiple BPEL servers. From time to time you may need to temporarily disable an active connection, or reactive a connection.

This section contains the following subsections:

• Activating a Worklist Connections Using Fusion Middleware Control

• Activating a Worklist Connections Using WLST

11.5.2.4 Modifying Worklist Connection Details

This section contains the following subsections:

• Modifying Worklist Connection Details Using Fusion Middleware Control

• Modifying Worklist Connection Details Using WLST

11.5.2.5 Deleting Worklist Connections

Before you delete a Worklist connection, check to see whether the WebCenter Spaces workflows, use the same connection.

This section contains the following subsections:

• Deleting Worklist Connections Using Fusion Middleware Control

• Deleting Worklist Connections Using WLST

11.5.2.6 Testing Worklist Connections

Log in to the SOA BPEL Worklist application with valid user credentials. A Worklist application is accessible through the URL in the following format:

protocol://host:port/integration/worklistapp

For example, http://mybpelserver.com:8001/integration/worklistapp.

You can also verify the status of the wsm-pm application, which manages the SAML policy web service authentication mechanism used by Worklist. To show the list of wsm-pm policies, log in to both, the SOA BPEL server and the server running the Worklist task flow using the following URL format:

protocol://SOA server host:port/wsm-pm/validator

For example, http://mybpelserver.com:8001/wsm-pm/validator and http://myWorklistHostingServer.com:8888/wsm-pm/validator.

11.8.1.1 About the General Menu

The General menu is a default menu and cannot be edited. You use the General menu to perform common operations on your wiki and blog server.

Table 11-22 describes the links available in the General menu of a domain.

11.8.1.2 About the Administration Mode

To configure your wiki and blog server, you use the Administration mode of the server. You access the Administration mode by clicking the Administration link on your wiki and blog server. (Figure 11-11)

Figure 11-11 Administration Link

Description of "Figure 11-11 Administration Link "

Figure 11-12 displays the Administration mode.

Figure 11-12 Administration Mode

Description of "Figure 11-12 Administration Mode"

The Administration mode contains various links that you can use to configure settings specific to the current domain or the entire wiki and blog server. Table 11-23 describes the links available in the Administration mode.

11.8.3.1 Adding a Domain

To create a new domain:

1. Log on to Oracle WebCenter Wiki and Blog Server as an administrator and access the Administration mode.

2. Under General in the navigation panel on the left, click Domains.

   The Domains page lists all the domains on the wiki and blog server.

3. Click add to create a new domain.

4. Enter a domain name, a description, and a name for the start page of your domain, as shown in Figure 11-13.

   Figure 11-13 Adding a New Domain

   
   Description of "Figure 11-13 Adding a New Domain"
   
   

5. Click Save.

   The newly created domain is listed on the Domains page, as shown in Figure 11-14.

   Figure 11-14 List of Domains

   
   Description of "Figure 11-14 List of Domains"
   
   

6. To navigate directly to the new domain, click its start page link in the Startpage column.

   To exit the Administration mode, under General, click Exit. This displays the wiki page of the last domain that you accessed before entering the Administration mode.

After creating a new domain, you can create wiki pages and blog entries in the domain. For information, see the "Working with Wikis and Blogs" chapter in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.

11.8.3.2 Editing a Domain Menu

As an administrator, you can create or edit the menu of a domain. The domain-specific menu appears at the top in the navigation panel. Figure 11-15 shows the menu of the default domain, owc_wiki.

A menu comprises menu topics, which display as headers. Menu topics contain menu items. For example, in the owc_wiki domain, Documentation is a menu topic and Home is a menu item. Menu topics display on the navigational panel in the order in which you create them.

A newly created domain contains an empty wiki page named Menu. You use this page to create or edit the domain-specific menu. You can edit the Menu wiki page by using the edit menu link on the navigation panel.

Figure 11-15 Domain Menu

Description of "Figure 11-15 Domain Menu"

To modify the menu of a domain:

1. Click the All domains link on the toolbar of links on the top-left corner of your wiki and blog server user interface.

   Note that you do not need to access the Administration mode to edit a domain menu.

2. Click the start page link of the domain for which you wish to edit the menu.

3. Click the edit menu link. Figure 11-16 shows the blank menu of a newly created domain.

   The Edit Page displays.

   Tip:

   You can also access the Edit Page by clicking All Pages under General on the navigation panel. This displays a list of all wiki pages of the current domain. You can click the Menu wiki page to view the menu, and then click the Edit tab to edit the menu.

   Figure 11-16 Menu of a New Domain

   
   Description of "Figure 11-16 Menu of a New Domain"
   
   

4. Specify the menu topic and menu items that you want to add or change. You can edit the menu the same way you edit a wiki page.

   Within each menu topic, you can define menu items and link them to the required wiki pages or to the targets that are external to your wiki and blog server. When you create a menu item, you must provide a name and specify either the name of a wiki page or a URL. The name that you specify displays in the menu on the navigation panel.

   Tip:

   When naming your page, ensure that you adhere to wiki markup standards, that is, you use the camel case notation for naming wiki pages. This notation uses an initial uppercase letter followed by lowercase letters, then another uppercase letter, and another series of lowercase letters, for example, MyWikiPage. To use an alternate name for your page, use the following convention: [alternate name | Wiki page name]. For example: [ My Page | MyPage ].

   For information about wiki markup language to format page content, see the "Using Wiki Mark-Up" section in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.

   Figure 11-17 Editing a Domain Menu

   
   Description of "Figure 11-17 Editing a Domain Menu"
   
   

   Tip:

   After you edit a menu, it is a good practice to change the mode to only admins are allowed to edit in the Mode dropdown list in the Edit tab. Although the Edit menu link is automatically removed from the menu if the registered user is not an administrator, users may accidentally edit the menu page.

5. Click Save.

11.8.3.3 Managing Domain Members

By default, all authorized wiki users can view and modify wiki pages in a domain. However, you can choose to specify the users who can access and manage wiki pages in a domain.

To manage domain members:

1. In the Administration mode, click Domains.

2. On the Domains page, click the manage members link of the domain for which you want to specify members.

3. From the username dropdown list, select the user whom you want to add as a domain member.

4. Click Add.

   The new user's name displays in the Members section, as shown in Figure 11-18.

   Repeat step 3 and 4 if you want to add any other user as the domain member.

   Figure 11-18 Adding a Domain Member

   
   Description of "Figure 11-18 Adding a Domain Member"
   
   

5. Click the remove link next to a member's name under Members if you do not want that member to be able to manage the domain.

While creating a wiki page in the domain, users can select the restricted to members of the domain option if they want only domain members to be able to edit the wiki page.

Figure 11-19 Restricting Access to Domain Members

Description of "Figure 11-19 Restricting Access to Domain Members"

11.8.3.4 Managing Blog Authors

By default, blog entries can be added only by a wiki administrator or the person who owns the blog. For a personal blog, blog author is the person who owns that personal blog. In a domain (such as a blog associated with a WebCenter group space), blog author is the domain creator, which is usually a wiki administrator.

A wiki administrator or the blog owner can specify additional users who can add blog entries. For information about enabling or disabling additional blog authors, see the "Adding and Removing Additional Blog Authors" section in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.

11.8.8.1 Managing Users

You can add a new user by using the Add new user link on the Users page in the Administration mode, as shown in Figure 11-24. Adding users by this method adds users to the local security store of the wiki and blog server. This security store is used when there is no single sign-on security or an LDAP-based identity store configured for the wiki and blog server.

Figure 11-24 Adding a User

Description of "Figure 11-24 Adding a User"

When you deploy the wiki and blog server by leveraging the single sign-on security, users are not initially imported from the external security store. Once a user is authenticated by the external security store, the wiki and blog server checks whether the user exists in its local security store. If not, a user entry is created upon first login by that user and a default role, like USER, is assigned to that user.

In the Administration mode, you can block users and reset passwords. These features are useful only when the wiki and blog server is used as a standalone application. Changing user passwords through the Administration mode changes passwords only in the local security store. If the server is integrated with another Oracle application through single sign-on or LDAP, then the user is authenticated through single sign-on and password are stored in the external security repository. In such a case, if a password needs to be changed, then you must change the password in the external security store.

11.8.8.2 Managing Permissions for a Role

For different wiki operations, you can create specific roles and assign required permissions to those roles. You can also modify existing roles to add or remove permissions. You can then assign the required roles to different users to define the operations that those users can perform.

To edit the permissions granted to a role:

1. In the Administration mode, under User Management, click Roles.

   The Roles page displays various roles and the permissions assigned to each role.

2. Click the edit link under the role that you want to modify. For example, to modify the ADMIN role, you click edit under ADMIN. (Figure 11-25)

   The Edit role page displays a list of all permissions that have been assigned or that can be assigned to the selected role. (Figure 11-26)

   Figure 11-25 Editing a Role

   
   Description of "Figure 11-25 Editing a Role"
   
   

   Tip:

   If you want to create a new role, then specify a role name in the Name box and then click Save on the Roles page (Figure 11-25). You can then click the edit link under the newly created role to add the required permissions.

3. In the Actions column, click the add link for a permission to add that permission to the selected role, or click the remove link corresponding to a permission to remove that permission from the selected role. (Figure 11-26)

   Tip:

   You can view the description of each permission by clicking Permissions under User Management on the navigation panel in the Administration mode.

   Figure 11-26 Specifying Permissions for a Role

   
   Description of "Figure 11-26 Specifying Permissions for a Role"
   
   

4. Click the Roles link at the bottom of the Edit role page to return to the Roles page.

11.8.11.1 Deleting a Wiki Page

To delete a wiki page:

1. Access the Administration mode.

2. Under Domain Related, click All Pages. This displays a list of all pages in the current domain.

   Note:

   To delete wiki pages of any domain, you must first navigate to that domain and then access the Administration mode.

3. For the wiki page that you want to delete, click the corresponding delete link in the Actions column, as shown in Figure 11-29. If you want to delete multiple pages, then select checkboxes for specified pages in the Delete column, and then click Delete Selected.

   Figure 11-29 Deleting a Wiki Page

   
   Description of "Figure 11-29 Deleting a Wiki Page"
   
   

4. Click the Delete all empty pages link at the top on the All Pages page if you want to delete wiki pages that do not contain any text.

   Click the reduce link to reduce the versions of a wiki page available on the server. It makes the current or the latest version of a wiki page as the only version and deletes all previous versions.

11.8.11.2 Deleting a Blog Entry

A wiki administrator or users who have the permission to manage blogs can edit and delete blog entries. For information about how to delete blog entries, see the "Deleting a Blog Entry" section in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.