Configuration Roadmaps for the Events Service

15-6 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

15.3.1.2 Microsoft Exchange Server 2007 - Configuration

To use Microsoft Exchange Server 2007 as the server for the Events service, you must edit the Microsoft Exchange Server 2007 Web service WSDL to specify the location of the Web service. To specify the location of the Microsoft Exchange Server 2007 Web service:

1. Open the WSDL file for the Microsoft Exchange Server Web service, for example:

C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews\Services.wsdl

2. Add a service section that points to your Microsoft Exchange Server Web

service, for example: wsdl:definitions ... wsdl:service name=ExchangeServices wsdl:port name=ExchangeServicePort binding=tns:ExchangeServiceBinding soap:address location=https:server.example.comEWSExchange.asmx wsdl:port wsdl:service wsdl:definitions

15.3.1.3 Microsoft Exchange Server 2007 - Security Considerations

The Events service includes a Microsoft Exchange Server 2007 adapter that communicates with the Microsoft Exchange Server 2007 generic Web service through a JAX-WS proxy. To set up the communication between the adapter and the Web service, you must edit the Microsoft Exchange Server security settings. To edit security settings: 1. On the Microsoft Exchange Server, open Internet Information Services IIS Manager.

2. Under Node computer_name Web Sites Default Web Site EWS, click

Properties .

3. On the Directory Security tab, in the Authentication and access control, click Edit.

4. Select Basic authentication.

5. Click OK.

You must enable anonymous access to Services.wsdl, Messages.vsd, and Types.vsd so that JAX-WS can access them to create the service port before committing any Web service call.

6. Right-click Services.wsdl and choose Edit.

7. On the File Security tab, in the Authentication and access control, click Edit.

8. Select Enable anonymous access.

9. Click OK.

10. Repeat steps 6 through 9 for Messages.xsd and Types.xsd.

The Events service uses Basic Authentication to communicate with the Microsoft Exchange Server. To secure the communication, you should enable SSL. For more information, see: http:www.microsoft.comtechnetprodtechnolWindowsServer2003L ibraryIIS56bdf977-14f8-4867-9c51-34c346d48b04.mspx?mfr=true Managing the Events Service 15-7

15.3.1.4 Microsoft Exchange Server 2007 - Limitations

There are currently no known limitations.

15.3.2 Microsoft Exchange Server 2003 Prerequisites

This section describes the Microsoft Exchange Server 2003 prerequisites when used as the server for the Events service. This section includes the following subsections: ■ Section 15.3.2.1, Microsoft Exchange Server 2003 - Installation ■ Section 15.3.2.2, Microsoft Exchange Server 2003 - Configuration ■ Section 15.3.2.3, Microsoft Exchange Server 2003 - Security Considerations ■ Section 15.3.2.4, Microsoft Exchange Server 2003 - Limitations

15.3.2.1 Microsoft Exchange Server 2003 - Installation

Refer to the Microsoft Exchange Server 2003 documentation for installation information.

15.3.2.2 Microsoft Exchange Server 2003 - Configuration

Microsoft Exchange Server 2003 does not provide a Web service, so to use Microsoft Exchange Server 2003 as the server for the Events service, you must install the WebCenter Personal Events Web Service Plug-in on the IIS computer. The plug-in is available on the Companion CD. To install the WebCenter Personal Events Web Service Plug-in: 1. Extract the contents of the ExchangeWebService.zip file to a folder on the computer where Microsoft Exchange Server is installed. You can find the ZIP file in the following directory on the Oracle Fusion Middleware companion CD: Disk1WebCenterservicescalNTExchangeWebService.zip 2. Open Internet Information Services IIS Manager.

3. Under Node computer_name Web Sites Default Web Site, create a new

virtual directory called ExchangeWS. 4. Point the new virtual directory to the folder to which you extracted the ZIP file.

5. Make sure the folder has Read privileges.

6. Right-click the virtual directory and choose Properties.

7. On the Virtual Directory tab, under Application settings, click Create.

8. Set the Execute permissions to Scripts and Executables.

9. On the ASP.NET tab, ensure that the ASP.NET version is 2.0.XXXXX.

10. Click Edit Configuration.

11. In the ASP .NET Configuration Settings dialog, make sure the ExchangeServerURL has the correct value, for example: http:localhost:portExchangeusercalendar Change the port, if necessary, to reflect the IIS port number. 12. Apply the changes and close the dialog. 15-8 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter 13. Create a folder called C:\WSErrorLogs. 14. Test the Web service by launching a Web browser and going to the following URL: http:localhostExchangeWSPersonalEventsWebService.asmx

15.3.2.3 Microsoft Exchange Server 2003 - Security Considerations

The Events service uses Basic Authentication to communicate with the Microsoft Exchange Server. To secure the communication, you should enable SSL. For more information, see: http:www.microsoft.comtechnetprodtechnolWindowsServer2003L ibraryIIS56bdf977-14f8-4867-9c51-34c346d48b04.mspx?mfr=true

15.3.2.4 Microsoft Exchange Server 2003 - Limitations

There are currently no known limitations.

15.4 Registering Events Servers

You can register multiple events servers for WebCenter Spaces but only one is active at a time. To start using a new active connection you must restart the managed server on which WebCenter Spaces is deployed. This section includes the following subsections: ■ Section 15.4.1, Registering Events Servers Using Fusion Middleware Control ■ Section 15.4.2, Registering Event Servers Using WLST

15.4.1 Registering Events Servers Using Fusion Middleware Control

To register an events server for WebCenter Spaces: 1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces. For more information, see Section 6.2, Navigating to the Home Page for WebCenter Spaces.

2. From the WebCenter menu, choose Settings Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, select Personal Events .

4. To connect to a new events server instance, click Add

Figure 15–3 . Figure 15–3 Configuring Events Connections Managing the Events Service 15-9 5. Enter a unique name for this connection, specify the version of Microsoft Exchange Server, and indicate whether this connection is the active or default connection for the application Table 15–3 . 6. Enter connection details for the events server Table 15–4 .

7. Click OK to save this connection.

8. To start using the new active connection you must restart the managed server on

which WebCenter Spaces is deployed. For more information, see Section 8.2, Starting and Stopping Managed Servers for WebCenter Application Deployments.

15.4.2 Registering Event Servers Using WLST

Use the WLST command createPersonalEventConnection to create an events service connection. Use setPersonalEventConnection to alter an existing connection. For command syntax and examples, see the sections, “createPersonalEventConnection” and “setPersonalEventConnection” in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. For information on how to run WLST commands, see Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands. Table 15–3 Personal Events 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. Connection Type Choose the Microsoft Exchange Server you want to connect to: ■ Microsoft Exchange Server 2003 ■ Microsoft Exchange Server 2007 Active Connection Select to use this connection for the Events service in WebCenter Spaces. While you can register multiple events server connections, only one connection is used by the Events service—the default or active connection. Table 15–4 Personal Events - Connection Details Field Description Web Service URL Enter the URL of the Web service exposing the event application. Use the format: protocol :host:portappWebServiceInterfaceWSName For example http:myexchange.com:80ExchangeWSPersonalEventsWebSe rvice.asmx http:myexchange.com:80EWSServices.wsdl Associated External Application Associate the events service with an external application. External application credential information is used to authenticate users against the Microsoft Exchange Server hosting events services.