Registering Instant Messaging and Presence Servers Using WLST

16-20 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter ■ Section 16.6.2, Deleting Instant Messaging and Presence Connections Using WLST

16.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 the WebCenter application. For more information, see: ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications 2. Do one of the following: ■ For WebCenter Spaces - From the WebCenter menu, choose Settings Service Configuration . ■ For WebCenter Portal 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.

16.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 Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. For information on how to run WLST commands, see Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands.

16.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: Determines what to display if user display names are missing. When set to 0, and display name information is unavailable, only the user name displays in the application. When set to 1, and display name information is unavailable, display names are read from user profile data. Setting this option to 1 impacts performance. The default setting is 0. Note: Before restarting the managed server, mark another connection as active; otherwise, the service is disabled. Managing the Instant Messaging and Presence Service 16-21 Display names are not mandatory in presence data. If the WebCenter application does not always provide display names by default and you consider this information important, set resolve.display.name.from.user.profile to 1 so that display names always display. ■ im.address.resolver.class: Resolver implementation used to map user names to IM addresses and IM addresses to user names. The default setting is oracle.webcenter.collab.rtc.IMPAddressResolverImpl. This implementation looks for IM addresses in the following places and order: – User Preferences – User Credentials – User Profiles ■ im.address.profile.attribute: User profile attribute used to determine a user’s IM address. The default setting is BUSINESS_EMAIL. For command syntax and detailed examples, see the section, setIMPServiceProperty in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. For information on how to run WLST commands, see Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands.

16.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 :hostRTCApplicationConfigurationService.asmx ■ protocol :hostRTCRTCService.asmx ■ protocol:host RTCOCSWebService.asmx To verify an OWLCS connection, try accessing the endpoint for the following Web services. For example: ■ protocol :host:portPresenceConsumerServiceservicesPresenceC onsumer ■ protocol :host:portPresenceSupplierServiceservicesPresenceS upplier ■ protocol :host:portThirdPartyCallServiceservicesThirdPartyC all ■ protocol :host:portservices