Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Portal
11g Release 1 (11.1.1.6.0)

Part Number E12405-18
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

15 Managing the Events Service

This chapter describes how to configure and manage the Events service to expose personal Microsoft Exchange calendars in Oracle WebCenter Portal applications.

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

Note:

Configuration changes for the Events service, through Fusion Middleware Control or using WLST, are not dynamic so you must restart the managed server on which the WebCenter Portal application is deployed for your changes to take effect. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Portal 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."

15.1 What You Should Know About Events Connections

In WebCenter Portal: Spaces, the Events service provides space calendars that you can use to schedule meetings, appointments, and any other type of team, project, or group occasion. The Events service also enables you to access your personal Microsoft Exchange calendar, where you can schedule events that are not related to a particular space.

In applications built using WebCenter Portal: Framework, the Events service provides access to your personal Microsoft Exchange calendar only.

Personal calendars are available through a Microsoft Exchange Server; therefore, a connection to that server is required. You can register the Microsoft Exchange Server connection 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 Microsoft Exchange Server connections, but only one connection is active at a time.

To view personal events in WebCenter Portal applications, users must have an account on the Microsoft Exchange Server.

15.2 Configuration Roadmaps for Personal Events in the Events Service

Use the roadmaps in this section as an administrator's guide through the configuration process for providing access to personal events:

15.3 Events Service Prerequisites for Personal Events

This section includes the following subsections:

15.3.1 Microsoft Exchange Server 2007 Prerequisites

This section describes the Microsoft Exchange Server 2007 prerequisites when used as the server for personal events in the Events service.

This section includes the following subsections:

15.3.1.1 Microsoft Exchange Server 2007 - Installation

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

15.3.1.2 Microsoft Exchange Server 2007 - Configuration

To use Microsoft Exchange Server 2007 as the server for personal events, 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.com/EWS/Exchange.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.com/technet/prodtechnol/WindowsServer2003/Library/IIS/56bdf977-14f8-4867-9c51-34c346d48b04.mspx?mfr=true

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 personal events in the Events service.

This section includes the following subsections:

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 WebCenter Portal's Personal Events Web Service Plug-in on the IIS computer. The plug-in is available on the Oracle Fusion Middleware companion CD.

To install the Personal Events Web Service Plug-in:

  1. Extract the contents of ExchangeWebService.zip to a folder within the Internet Information Services (IIS) server. You can find the ZIP file in the following directory on the Oracle Fusion Middleware companion CD:

    /Disk1/WebCenter/services/cal/NT/ExchangeWebService.zip
    

    Note:

    Make sure that the folder where you extract the file has the proper Read privileges. If necessary add Server Operators with additional Modify and Write privileges and Authenticated Users.

  2. Open IIS Manager.

  3. Under server_name > Web Sites > Default Web Site, create a new virtual directory called ExchangeWS (as the Alias).

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

  5. Make sure the folder has Read and Run Scripts privileges.

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

  7. On the Virtual Directory tab, under Application settings, from the Execute permissions dropdown list, select Scripts and Executables.

  8. Click Apply.

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

    Note:

    If ASP.NET is not available by default, then install the .NET 2.0 Framework from:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en

  10. Click Edit Configuration.

  11. In the ASP .NET Configuration Settings dialog, make sure the ExchangeServerURL has the correct value, for example:

    http://localhost:port/Exchange/User/calendar
    

    Tip:

    The ExchangeServerURL is case-sensitive.

    Change the port, if necessary, to reflect the IIS port number. By default, this is 80.

  12. Apply the changes and close the dialog.

  13. Create a folder called C:\WSErrorLogs.

  14. Test the web service from the IIS server and the WebCenter Portal server by accessing the following URL in your browser:

    http://host:port/ExchangeWS/PersonalEventsWebService.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.com/technet/prodtechnol/WindowsServer2003/Library/IIS/56bdf977-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 a WebCenter Portal application but only one is active at a time.

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

This section includes the following subsections:

15.4.1 Registering Events Servers Using Fusion Middleware Control

To register an events server:

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

  2. Do one of the following:

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

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

  3. From the list of services on the WebCenter Portal 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

    Configuring Events Connection
  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-2).

    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 Portal 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 the WebCenter Portal application.

    While you can register multiple events server connections, only one connection is used by the Events service—the default (or active) connection.


  6. Enter connection details for the events server (Table 15-4).

    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:port/appWebServiceInterface/WSName
    

    For example

    http://myexchange.com:80/ExchangeWS/PersonalEventsWebService.asmx
    http://myexchange.com:80/EWS/Services.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.


  7. Click OK to save this connection.

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

15.4.2 Registering Event Servers Using WLST

Use the WLST command createPersonalEventConnection to create an events server 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."

Note:

To start using the new (active) connection you must restart the managed server on which the WebCenter Portal application is deployed. See, “Starting and Stopping WebLogic Managed Servers Using the Command Line” in the Oracle Fusion Middleware Administrator's Guide.

15.5 Choosing the Active Events Server Connection

You can register multiple events server connections with a WebCenter Portal application, but only one connection is active at a time.

This section includes the following subsections:

15.5.1 Choosing the Active Events Server Using Fusion Middleware Control

To change the active connection:

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

  2. Do one of the following:

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

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

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

    The Manage Personal Events 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 checkbox.

  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 Portal application is deployed. For more information, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

15.5.2 Choosing the Active Events Server Connection Using WLST

Use the WLST command setPersonalEventConnection with default=true to activate an existing events server connection. For command syntax and examples, see the section, “setPersonalEventConnection” in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To subsequently disable an events 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.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

Note:

To start using the active connection you must restart the managed server on which the WebCenter Portal 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.

15.6 Modifying Events Server Connection Details

You can modify events server connection details at any time.

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

This section includes the following subsections:

15.6.1 Modifying Events Server Connection Details Using Fusion Middleware Control

To update connection details for an events server:

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

  2. Do one of the following:

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

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

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

  4. Select the connection name, and click Edit.

  5. Edit connection details, as required. For detailed parameter information, see Table 15-4.

  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 Portal application is deployed. For more information, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

15.6.2 Modifying Events Server Connection Details Using WLST

Use the WLST command setPersonalEventConnection to edit an existing events server connection. For command syntax and examples, see the section, “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."

Note:

To start using the updated (active) connection you must restart the managed server on which the WebCenter Portal 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.

15.7 Deleting Event Server Connections

You can delete events server connections at any time but take care when deleting the active connection. If you delete the active connection, users cannot create events in their personal calendar.

This section includes the following subsections:

15.7.1 Deleting Event Server Connections Using Fusion Middleware Control

To delete an events server connection:

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

  2. Do one of the following:

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

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

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

  4. Select the connection name, and click Delete.

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

15.7.2 Deleting Event Server Connections Using WLST

Use the WLST command deleteConnection to remove an events 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.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

Note:

To effect this change you must restart the managed server on which the WebCenter Portal 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.

15.8 Testing Event Server Connections

To confirm the connection to the events server:

  1. Add the Events task flow to a page in your WebCenter Portal application.

    Tip:

    In WebCenter Portal: Spaces, add the task flow to a page in your Home space.

  2. Log in to your Microsoft Exchange Server account.

  3. Your personal events from Microsoft Exchange Server should display in the task flow.

15.9 Troubleshooting Issues with Events

If users cannot see their personal events, verify the following: