14 Managing the Instant Messaging and Presence Service

This chapter describes how to configure and manage the Instant Messaging and Presence (IMP) service for WebCenter Spaces and custom WebCenter applications.

Always use Fusion Middleware Control or WLST command-line tool to review and configure back-end services for WebCenter applications. Any changes that you make to WebCenter applications, post deployment, are stored in MDS metatdata store as customizations. See Section 1.3.5, "Oracle WebCenter Configuration Considerations."

Note:

Changes that you make to WebCenter services configuration, through Fusion Middleware Control or using WLST, are not dynamic so you must restart the managed server on which the WebCenter application is deployed for your changes to take effect. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

This chapter includes the following sections:

Audience

The content of this chapter is intended for Fusion Middleware administrators (users granted the Admin or Operator role through the Oracle WebLogic Server Administration Console). See also, Section 1.8, "Understanding Administrative Operations, Roles, and Tools."

14.1 What You Should Know About Instant Messaging and Presence Connections

The IMP service enables you to observe the presence status of other authenticated application users (online, offline, busy, or away) and provides instant access to interaction options, such as instant messages (IM) and mails.

A single connection to a back-end presence server is required.

WebCenter is certified with Microsoft Office Communications Server (OCS) 2007 and Microsoft Office Live Communications Server (LCS) 2005, and it can integrate with other presence servers. Oracle WebLogic Communications Services (OWLCS) 11g is available for download on Oracle Technology Network (OTN) at http://www.oracle.com/technology/index.html. For information on OWLCS installation, see Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

Note:

To add or remove buddies to your account, you must use the OCS, LCS, or OWLCS client. In WebCenter applications you can see buddies, but you cannot add or remove buddies. For more information, see the Oracle WebLogic Communication Services Administrator's Guide.

You can register the presence server connection for your WebCenter application through the Fusion Middleware Control Console or using WLST. You must mark a connection as active for the service to work. You can register additional presence server connections, but only one connection is active at a time.

14.2 Instant Messaging and Presence Server Prerequisites

This section includes the following subsections:

14.2.1 Microsoft Office Communications Server (OCS) Prerequisites

This section describes the Microsoft Office Communications Server 2007 (OCS) prerequisites as the presence server for the Instant Messaging and Presence service.

This section includes the following subsections:

14.2.1.1 OCS - Installation

Refer to the Microsoft Office Communications Server 2007 documentation for installation information.

14.2.1.2 OCS - Configuration

To use Microsoft OCS 2007 as the presence server for the IMP service, you must install the Microsoft Unified Communications Managed API (UCMA) 2.0 SDK, and you must install the Oracle RTC Web service for Microsoft OCS 2007.

  1. To install Microsoft UCMA 2.0, navigate to one of the following locations:

    • For OCS2007 R1 installation (32 bit):

      http://www.microsoft.com/downloads/details.aspx?FamilyID=768efa33-6606-4b2b-809a-6c69274621d3&displaylang=en

      Download and run the UcmaSdkWebDownload.msi file. The file extracts the setup files at C:\Microsoft Unified Communications Managed API 2.0 SDK Installer package\i386.

    • For OCS2007 R2 installation (64 bit):

      http://www.microsoft.com/downloads/details.aspx?FamilyID=b20967b1-6cf5-4a4b-b7ae-622653ac929f&displaylang=en

      Download and run the UcmaSdkWebDownload.msi file. The file extracts setup files at C:\Microsoft Unified Communications Managed API 2.0 SDK Installer package\amd64.

    Go to the directory and run vcredist_x86.exe. This installs the Visual C++ 2008 redistributable. Then navigate to the Setup directory and run UcmaRedist.msi. This installs the UCMA 2.0 assemblies in the GAC.

  2. To install the Oracle Web service for Microsoft OCS, extract the owc_ocs2007.zip from the Oracle Fusion Middleware companion CD. This creates a directory named OCSWebServices.

  3. Open the Internet Information Services (IIS) Manager.

  4. Expand the server node and then Web Sites in the (IIS) Manager window.

  5. Right-click Default Web Site, choose New, and then select Virtual Directory to create a site for the Oracle RTC Web service, as shown in Figure 14-1. The Virtual Directory Creation Wizard displays.

  6. Click Next.

  7. Enter an alias for the virtual directory in the Alias field, for example RTC.

  8. Enter the path to the directory where you extracted the owc_ocs2007.zip file; for example, C:\OCSWebServices. Alternatively, use the Browse button to navigate to that directory.

  9. Click Next.

  10. Ensure that the virtual directory has the Read, Execute, and Browse privileges.

  11. Click Next.

  12. Click Finish. The newly created virtual directory appears under Default Web Site in the IIS Manager window.

  13. Right-click the newly created virtual directory for the Oracle RTC Web service, and choose Properties to open the Properties dialog.

  14. In the Virtual Directory tab, under Application settings, click Create. Notice that the button label changes to Remove, and the name of your newly created virtual directory appears in the Application name field.

  15. Select Scripts and Executables from the Execute permissions dropdown list

  16. Under the ASP.NET tab, select the ASP.NET version as 2.0 or higher from the ASP.NET version dropdown list. IIS should be configured to consume ASP.NET 2.0 applications.

  17. Click OK.

  18. Test the Web service by accessing the Web site from the following URL format: http://localhost/default_website/OCSWebService.asmx

    where default_website is the virtual directory that you created for the Oracle RTC Web service. For example:

    http://localhost/RTC/OCSWebService.asmx

14.2.1.3 OCS - Security Considerations

You must configure an external application for Microsoft Office Communications Server connections so that users can supply credentials to authenticate themselves on the OCS server.

With a secured application, users get buddies and presence status. With OCS, if security is required, then OCS should be on a private trusted network.

OCS provides an option for changing external credentials, which works as an alternative to using an external application. A logged-in user can click any Presence tag and select Change Credentials from the menu.

For more information, see Section 14.3.1, "Registering Instant Messaging and Presence Servers Using Fusion Middleware Control."

14.2.1.4 OCS - Limitations

WebCenter applications do not support phone conferencing.

14.2.2 Microsoft Live Communications Server (LCS) Prerequisites

This section describes the Microsoft Live Communications Server 2005 (LCS) prerequisites as the presence server for the Instant Messaging and Presence service.

This section includes the following subsections:

14.2.2.1 LCS - Installation

Refer to the Microsoft Live Communications Server 2005 documentation for installation information.

14.2.2.2 LCS - Configuration

To use Microsoft Live Communications Server 2005 as the presence server for the Instant Messaging and Presence service, you must install and configure the Microsoft RTC API v1.3, and you must install the Oracle RTC Web service for Microsoft LCS 2005.

  1. To install the Microsoft RTC API v1.3, download the RTC SDK from Microsoft RTC Client API SDK 1.3, and run the installer. The installer provides the necessary installation components. If you choose the default options, the following two installers are available at C:\Program Files\RTC Client API v1.3 SDK\INSTALLATION:

    • RtcApiSetup.msi

    • RtcSxSPolicies.msi

    Run the RtcApiSetup.msi installer first, then the side-by-side policy switcher installer (RtcSxSPolicies.msi), and restart the system.

  2. To install the Oracle RTC Web service for Microsoft Live Communications Server 2005, extract the owc_lcs.zip file from the Oracle Fusion Middleware companion CD. It is located in the directory /Disk1/WebCenter/services/imp/NT. The zip file contains the following:

    /Bin

    /images

    ApplicationConfigurationService.asmx

    BlafPlus.css

    ExtAppLogin.aspx

    ExtAppLogin.aspx.cs

    Global.asax

    Log4Net.config

    RTCService.asmx

    Web.Config

    WebcenterTemplate.master

  3. Open the Internet Information Services (IIS) Manager.

  4. Expand the server node and then Web Sites in the IIS Manager window.

  5. Right-click Default Web Site, choose New, and then select Virtual Directory to create a site for the Oracle RTC Web service, as shown in Figure 14-1. The Virtual Directory Creation Wizard displays.

    Figure 14-1 Creating a Virtual Directory

    Creating a virtual directory using IIS

  6. Click Next.

  7. Enter an alias for the virtual directory in the Alias field, for example RTC.

  8. Enter the path to the directory where you extracted the owc_lcs.zip file. Alternatively, use the Browse button to navigate to that directory.

  9. Click Next.

  10. Ensure that the virtual directory has the Read, Execute, and Browse privileges. (Figure 14-2)

    Figure 14-2 Virtual Directory Properties

    Virtual Directory Properties

  11. Click Next.

  12. Click Finish. The newly created virtual directory appears under Default Web Site in the Internet Information Services (IIS) Manager window (Figure 14-3).

    Figure 14-3 Adding a Virtual Directory

    Adding a Virtual Directory

  13. Right-click the newly created virtual directory for the Oracle RTC Web service, and then choose Properties to open the Properties dialog.

  14. In the Virtual Directory tab, under Application settings, click Create. Notice that the button label changes to Remove, and the name of your newly created virtual directory appears in the Application name field.

  15. Select Scripts and Executables from the Execute permissions dropdown list (Figure 14-4).

    Figure 14-4 Virtual Directory Properties

    Virtual Directory Properties

  16. Under the ASP.NET tab, select the ASP.NET version as 2.0 or higher from the ASP.NET version dropdown list. IIS should be configured to consume ASP.NET 2.0 applications.

  17. Click OK.

  18. Ensure that the LSC pool name in the LCS connection has been set.

  19. Test the Web service by accessing the Web site from the following URL format:

    http://localhost/default_website/ApplicationConfigurationService.asmx

    Where default_website refers to the virtual directory that you created for the Oracle RTC Web service.

    For example:

    http://localhost/RTC/ApplicationConfigurationService.asmx

14.2.2.3 LCS - Security Considerations

You must configure an external application for Microsoft Live Communications Server connections so that users can supply credentials to authenticate themselves on the LCS server.

With a secured application, users get buddies and presence status. With LCS, if security is required, then LCS should be on a private trusted network.

LCS provides an option for changing external credentials, which works as an alternative to using an external application. A logged-in user can click any Presence tag and select Change Credentials from the menu.

For more information, see Section 14.3.1, "Registering Instant Messaging and Presence Servers Using Fusion Middleware Control."

14.2.2.4 LCS - Limitations

WebCenter applications do not support phone conferencing.

14.2.3 Oracle WebLogic Communications Server (OWLCS) Prerequisites

This section describes Oracle WebLogic Communications Server (OWLCS) prerequisites as the presence server for the Instant Messaging and Presence service.

This section includes the following subsections:

14.2.3.1 OWLCS - Installation

For detailed OWLCS installation instructions, see the Oracle WebLogic Communication Services Installation Guide.

14.2.3.2 OWLCS - Configuration

OWLCS supports both identity propagation and external application-based connections. Oracle recommends using identity propagation for OWLCS connections, since additional security can be set with WS-Security.

OWLCS and the WebCenter application should point to the same LDAP-based identity store. If the OWLCS server and the WebCenter application use different LDAP-based identity stores, then you must configure an external application for the connection so that users can supply credentials to authenticate themselves on the OWLCS server.

For information on reassociating the WebCenter applications identity store, see Section 24.1, "Reassociating the Identity Store with an External LDAP."

If necessary, reconfigure OWLCS to use the same identity store. For more information, see the Oracle WebLogic Communication Services Administrator's Guide.

14.2.3.3 OWLCS - Security Considerations

If the OWLCS server is running with WS-Security enabled, then the administrator must set the policyURI parameter in the presence server connection.

If WS-Security is not required, then the administrator should disable WS-Security on the OWLCS server.

For more information, see Section 28.4, "Securing Oracle WebLogic Communication Services (OWLCS) with WS-Security" and Section 27.12, "Securing the WebCenter Spaces Connection to OWLCS with SSL."

14.2.3.4 OWLCS - Limitations

With OWLCS, user creation and deletion is manual. Any time a new user is added to (or removed from) the application's identity store, the same user must be created in (or removed from) the OWLCS user store.

Each OWLCS user has a watcher list, which is a list of the other users allowed to see his presence. This watcher list must be under 125 KB (approximately 400 users). In WebCenter, the presence of all users must be visible, even if they are not buddies of the logged-in user. To get their presence, WebCenter creates a new account on OWLCS with the group space GUID and adds this new user as a watcher of the visible users. In other words, each member of a group space has an entry of that group space GUID in his watcher list. A problem can arise when a user is part of many group spaces. Because the watcher list contains entries for each group space, its size can grow greater than 125KB. When that happens, updates to the watcher list are rejected, giving the user a "Subscription Request" popup with that scope GUID. If this happens, then the user should just cancel the subscription request.

14.3 Registering Instant Messaging and Presence Servers

You can register multiple presence server connections with a WebCenter application but only one of them is active at a time.

To start using the new (active) presence server you must restart the managed server on which the WebCenter application is deployed.

This section includes the following subsections:

14.3.1 Registering Instant Messaging and Presence Servers Using Fusion Middleware Control

To register a presence server connection:

  1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application. For more information, see:

  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 14-5).

    Figure 14-5 Configuring Instant Messaging and Presence Services

    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 (Table 14-1).

    Table 14-1 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:

    • LCS - Microsoft Live Communications Server

    • OCS - Microsoft Office Communications Server

    • OWLCS - Oracle WebLogic Communications Server

    Out-of-the-box, three presence connection types are available— LCS, OCS, and OWLCS.

    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 IMP service—the default (or active) connection.

  6. Enter connection details for the server hosting instant messaging and presence services (Table 14-2).

    Table 14-2 Instant Messaging and Presence Connection - Connection Details

    Field Description

    Server URL

    Enter the URL of the server hosting instant messaging and presence services.

    For example: http://myocshost.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 is john@oracle.com.

    If the user IM address must be resolved from the Oracle Internet Directory/LDAP server, then specify the user profile attribute that provides 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. WebCenter and the presence server should share the same Oracle Internet Directory/LDAP.

    The IM ID is the SIP ID; that is, sip:john@oracle.com. SIP is short for Session Initiation Protocol - an Internet protocol for live communication between people.

    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.

    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 Microsoft LCS and OCS connections.

    You can select an existing external application from the 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). For more information, see Chapter 22, "Managing External Applications."

    Authentication Method

    (OWLCS Only) Specify how to authenticate users against the instant messaging and presence server. Select 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 to use public, shared, or mapped credentials.

    If an external application is used for authentication, use the Associated External Application list to identify the application. If the application you want is not listed, select Create New... to define the external application.

    Policy URI

    (OWLCS Only) Specify the 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.

    User Domain

    (OCS Only) Enter the Active Directory domain on Microsoft Office Communications Server. The user domain is mandatory for OCS connections.

    OCS Server

    (OCS Only) Enter the name of the Microsoft Office Communications Server pool used for this connection. The pool name is mandatory for OCS connections.

    See the Microsoft Office Communications Server 2007 documentation for more information.

    LCS Pool Name

    (LCS Only) Enter the name of the Microsoft Live Communications Server pool used for this connection. The pool name is mandatory for LCS connections.

    See the Microsoft Live Communications Server documentation for details on the pool name.

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

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

    Table 14-3 lists additional parameters.

    Table 14-3 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 forwards 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 (Table 14-4).

    Table 14-4 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. For more information, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

14.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 the section, "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. For more information, see Section 14.4.2, "Choosing the Active Connection for Instant Messaging and Presence Using WLST."

Note:

To start using the new (active) connection you must restart the managed server on which the WebCenter application is deployed. For more information, see the section, "Starting and Stopping WebLogic Managed Servers Using the Command Line" in the Oracle Fusion Middleware Administrator's Guide.

14.4 Choosing the Active Connection for Instant Messaging and Presence

You can register multiple instant messaging and presence server connections with a WebCenter application but only one connection is active at a time.

For WebCenter Spaces and any custom WebCenter application, the active connection becomes the back-end presence server for the Buddies task flow.

This section includes the following subsections:

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

To change the active connection:

  1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application. For more information, see:

  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, select 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."

14.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 the section, "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. For more information, see the section, "removeIMPServiceProperty" 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."

Note:

To start using this active connection you must restart the managed server on which the WebCenter application is deployed. For more information, see the section, "Starting and Stopping WebLogic Managed Servers Using the Command Line" in the Oracle Fusion Middleware Administrator's Guide.

14.5 Modifying Instant Messaging and Presence Connection Details

You can modify instant messaging and presence server connection details at any time.

To start using an updated (active) connection you must restart the managed server on which the WebCenter application is deployed.

This section includes the following subsections:

14.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. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application. For more information, see:

  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, select Instant Messaging and Presence.

  4. Select the connection name, and click Edit.

  5. Edit connection details, as required. For detailed parameter information, see Table 14-2, "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. For more information, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments."

14.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 the section, "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 more information, see the section, "setIMPConnectionProperty" 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."

Note:

To start using the updated (active) connection you must restart the managed server on which the WebCenter application is deployed. For more information, see the section, "Starting and Stopping WebLogic Managed Servers Using the Command Line" in the Oracle Fusion Middleware Administrator's Guide.

14.6 Deleting Instant Messaging and Presence Connections

You can delete instant messaging and presence connections at any time but take care when deleting the active connection. If you delete the active connection, Buddies task flows does not work and user presence options are not available, as these require a back-end instant messaging and presence server.

When you delete a connection, consider deleting the external application associated with the instant messaging and presence service if the application's sole purpose was to support this service. For more information, see Section 22.5, "Deleting External Application Connections."

This section includes the following subsections:

14.6.1 Deleting Instant Messaging and Presence Connections Using Fusion Middleware Control

To delete an instant messaging and presence server connection:

  1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application. For more information, see:

  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, select 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. For more information, 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 is disabled.

14.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 the section, "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."

14.7 Setting Up Instant Messaging and Presence Service Defaults

Use the WLST command setIMPServiceProperty to set defaults for the IMP service:

  • selected.connection: Connection used by the Instant Messaging and Presence service.

  • rtc.cache.time: Cache timeout for instant messaging and presence data.

  • resolve.display.name.from.user.profile: Whether the display name of the user should be resolved by making an LDAP lookup. Valid values are true and false. If enabled (true), then the IMP service makes an LDAP lookup to find each user's display name. This should be enabled only when the same LDAP store is used for both WebCenter and the presence server. If different LDAP servers are used, then irrelevant information may display. This property can impact performance.

For command syntax and detailed examples, see the section, "setIMPServiceProperty" 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."

14.8 Testing Instant Messaging and Presence Connections

Web services expose a set of Web methods that you can invoke to test the validity.

To verify a Microsoft OCS or LCS connection, try accessing the endpoint for the WebCenter RTC Web services deployed on it. For example (assuming the application context path is /RTC):

  • protocol://host/RTC/ApplicationConfigurationService.asmx

  • protocol://host/RTC/RTCService.asmx

  • protocol://host/RTC/OCSWebService.asmx

To verify an OWLCS connection, try accessing the endpoint for the following Web services. For example:

  • protocol://host:port/PresenceConsumerService/services/PresenceConsumer

  • protocol://host:port/PresenceSupplierService/services/PresenceSupplier

  • protocol://host:port/ThirdPartyCallService/services/ThirdPartyCall

  • protocol://host:port/services

14.9 Troubleshooting Issues with Instance Messaging and Presence

This section contains troubleshooting tips for the IMP service.

Problem

Buddies are not visible in a custom WebCenter application. Further, the presence status of users is not available.

Solution

Ensure the following:

  • IMP connection is configured properly and the base URL and domain values are correct. See Section 14.3, "Registering Instant Messaging and Presence Servers."

  • Web Services for the presence server is installed properly and is up and running. For Web Services installation for Microsoft Live Communications Server, see Section 10.2.2.2, "Microsoft Live Communications Server (LCS) Prerequisites." For Web Services installation for Oracle WebLogic Communications Server, see the Oracle WebLogic Communication Services Administrator's Guide.

  • Back-end presence server (Microsoft Live Communications Server 2005, Microsoft Office Communications Server 2007, or Oracle WebLogic Communications Server) is up and running. A quick way to verify this is to ensure that the user can connect to the communications server by using a supported SIP client (Oracle Communicator or Microsoft Communicator).

  • User is logged in with valid user credentials and the user exists on the communications server. For Microsoft OCS or LCS, verify that user has provided correct credentials in the external application.