1. Administering Oracle WebCenter Portal
  2. Administering Tools and Services
  3. Managing Calendar Events

8 Managing Calendar Events

Configure and manage events to expose personal Microsoft Exchange calendars inWebCenter Portal portals.

Always use Fusion Middleware Control or the WLST command-line tool to review and configure back-end services for WebCenter Portal. Any configuration changes that you make, post deployment, are stored in the MDS metadata store as customizations.

Note:

Configuration changes for events, through Fusion Middleware Control or using WLST, are not dynamic, so you must restart the managed server on which WebCenter Portal is deployed for your changes to take effect.

Permissions:

To perform the tasks in this chapter, you must be granted the WebLogic Server Admin role through the Oracle WebLogic Server Administration Console and the Administrator role granted through WebCenter Portal Administration.

For more information about roles and permissions, see Understanding Administrative Operations, Roles, and Tools.

For troubleshooting, see Troubleshooting Issues with Events.

Topics:

About Events Connections

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

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 events 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, users must have an account on the Microsoft Exchange Server.

Configuring Personal Events for WebCenter Portal

Use the roadmaps in this section as a guide through the configuration process for providing access to personal events:

The flow chart (Figure 8-1) and table (Table 8-1) in this section provide an overview of the prerequisites and tasks required for personal events to work in WebCenter Portal.

Figure 8-1 Configuring Personal Events for WebCenter Portal

Description of Figure 8-1 follows
Description of "Figure 8-1 Configuring Personal Events for WebCenter Portal"

Table 8-1 Configuring the Personal Events for WebCenter Portal

Actor Task Subtask Link

Administrator

1. Install WebCenter Portal

See About Oracle WebCenter Portal Installation in Installing and Configuring Oracle WebCenter Portal

Administrator

2.Install and configure Microsoft Exchange Server release 2013 or 2010.

  • Install Microsoft Exchange Server 2013

2.a Configure MS Exchange Server 2013

2.b Edit security settings

2.c Ensure SSL is enabled

See Microsoft Exchange Server 2013 Prerequisites

Administrator

  • Install Microsoft Exchange Server 2010

2.a Configure MS Exchange Server 2010

2.b Edit security settings

2.c Ensure SSL is enabled

See Microsoft Exchange Server 2010 Prerequisites

Administrator

3. Configure a connection between WebCenter Portal and the events server using either Fusion Middleware Control or WLST

See Registering Events Servers

End User

4. Test that the personal calendar is working in WebCenter Portal

3.a Log in to WebCenter Portal and add an Events task flow to a page in your Home portal

3.b Click Login to Personal Calendar on the Events task flow and enter your Microsoft Exchange Server login credentials

In Building Portals with Oracle WebCenter Portal, see:

Events Prerequisites for Personal Events

This section includes the following subsections:

Microsoft Exchange Server 2013 Prerequisites

This section describes the Microsoft Exchange Server 2013 prerequisites when used as the server for personal events.

This section includes the following subsections:

Microsoft Exchange Server 2013 - Installation

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

Microsoft Exchange Server 2013 - Configuration

To use Microsoft Exchange Server 2013 as the server for personal events, you must edit the Microsoft Exchange Server 2013 web service WSDL to specify the location of the web service.

To specify the location of the Microsoft Exchange Server 2013 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>
Microsoft Exchange Server 2013 - Security Considerations

Events includes a Microsoft Exchange Server 2013 adapter that communicates with the Microsoft Exchange Server 2013 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. You must enable Basic authentication. Further, you must enable anonymous access to Services.wsdl, Messages.xsd, and Types.xsd so that JAX-WS can access them to create the service port before committing any web service call. This involves creating a virtual directory and enabling anonymous authentication and disabling Windows authentication.

To edit Microsoft Exchange Server security settings:

  1. On Microsoft Exchange Server, open Internet Information Services (IIS) Manager.
  2. Under Node computer_name > Sites > Default Web Site > EWS, double-click Authentication under IIS.
  3. Right-click Basic Authentication and select Enable to enable Basic Authentication for the EWS application.
  4. Right-click Anonymous Authentication and select Enable to enable Anonymous Authentication for the EWS application.
  5. If IIS version is 7.5, then do the following:
    1. Under Sites, right-click Default Web Site and select Add Virtual Directory to create a virtual directory that will be used to provide anonymous access to Services.wsdl, Messages.xsd, and Types.xsd.
    2. In the Add Virtual Directory dialog, in the Alias field, specify the name of the virtual directory, for example ExchWS.
    3. In the Physical Path field, specify the path to the virtual directory. For example:
      C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\ews

      Figure 8-2 Creating a Virtual Directory

      Description of Figure 8-2 follows
      Description of "Figure 8-2 Creating a Virtual Directory"
    4. Click Connect as.
    5. In the Connect As dialog, ensure Application user (pass-thorough authentication) is selected.
    6. Click OK.
  6. If IIS version is 8.5, then do the following:
    1. Under Sites, right-click Default Web Site and select Add Application to create a application directory that will be used to provide anonymous access to Services.wsdl, Messages.xsd, and Types.xsd.
    2. In the Add Application dialog, in the Alias field, specify the name of the directory, for example ExchWS. Select Application pool as defaultApplicationPool.
    3. In the Physical Path field, specify a folder outside of Microsoft Exchange Server installation. For example, C:\MSExchange.
    4. Copy the web services files Services.wsdl, Messages.xsd, and Types.xsd from the folder C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\ews to the folder C:\MSExchange.
    5. Click Connect as.
    6. In the Connect As dialog, ensure Application user (pass-thorough authentication) is selected.
    7. Click OK.
  7. Under Default Web Site > ExchWS, double-click Authentication under IIS.
  8. Right-click Anonymous Authentication and select Enable (Figure 8-3).

    Figure 8-3 Enabling Anonymous Authentication

    Description of Figure 8-3 follows
    Description of "Figure 8-3 Enabling Anonymous Authentication"
  9. Right-click Anonymous Authentication and select Edit.
  10. In the Edit Anonymous Authentication Credentials dialog, ensure Application pool identity is selected.
  11. Right-click Windows Authentication and select Disable.

Events uses Basic Authentication to communicate with the Microsoft Exchange Server. To secure the communication, ensure that SSL is enabled. For more information, see:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/56bdf977-14f8-4867-9c51-34c346d48b04.mspx?mfr=true

You must also ensure that the SSLAlwaysNegoClientCert property is set to true in IIS. The SSLAlwaysNegoClientCert property controls SSL client connection negotiations.

For example, use the following command to set the SSLAlwaysNegoClientCert property:

CScript.exe adsutil.vbs SET w3svc/1/SSLAlwaysNegoClientCert true

For more information about the SSLAlwaysNegoClientCert property, see:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/bce0fb87-79ea-40cd-963f-239545b61a12.mspx?mfr=true

For information about setting the SSLAlwaysNegoClientCert property, see:

https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/d3df4bc9-0954-459a-b5e6-7a8bc462960c.mspx?mfr=true to understand how to use adsutil.vbs

Microsoft Exchange Server 2013 - Limitations

There are currently no known limitations.

Microsoft Exchange Server 2010 Prerequisites

This section describes the Microsoft Exchange Server 2010 prerequisites when used as the server for personal events.

This section includes the following subsections:

Microsoft Exchange Server 2010 - Installation

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

Microsoft Exchange Server 2010 - Configuration

To use Microsoft Exchange Server 2010 as the server for personal events, you must edit the Microsoft Exchange Server 2010 web service WSDL to specify the location of the web service.

To specify the location of the Microsoft Exchange Server 2010 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>
Microsoft Exchange Server 2010 - Security Considerations

Events includes a Microsoft Exchange Server 2010 adapter that communicates with the Microsoft Exchange Server 2010 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. You must enable Basic authentication. Further, you must enable anonymous access to Services.wsdl, Messages.xsd, and Types.xsd so that JAX-WS can access them to create the service port before committing any web service call. This involves creating a virtual directory and enabling anonymous authentication and disabling Windows authentication.

To edit Microsoft Exchange Server security settings:

  1. On Microsoft Exchange Server, open Internet Information Services (IIS) Manager.
  2. Under Node computer_name > Sites >Default Web Site > EWS, double-click Authentication under IIS.
  3. Right-click Basic Authentication and select Enable to enable Basic Authentication for the EWS application.
  4. Under Sites, right-click Default Web Site and select Add Virtual Directory to create a virtual directory that will be used to provide anonymous access to Services.wsdl, Messages.xsd, and Types.xsd.
  5. In the Add Virtual Directory dialog, in the Alias field, specify the name of the virtual directory, for example ExchWS.
  6. In the Physical Path field, specify the path to the virtual directory. For example (Figure 8-4):

    C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\ews

    Figure 8-4 Creating a Virtual Directory

    Description of Figure 8-4 follows
    Description of "Figure 8-4 Creating a Virtual Directory"
  7. Click Connect as.
  8. In the Connect As dialog, ensure Application user (pass-thorough authentication) is selected.
  9. Click OK.
  10. Under Default Web Site > ExchWS, double-click Authentication under IIS.
  11. Right-click Anonymous Authentication and select Enable (Figure 8-5).

    Figure 8-5 Enabling Anonymous Authentication

    Description of Figure 8-5 follows
    Description of "Figure 8-5 Enabling Anonymous Authentication"
  12. Right-click Anonymous Authentication and select Edit.
  13. In the Edit Anonymous Authentication Credentials dialog, ensure Application pool identity is selected.
  14. Right-click Windows Authentication and select Disable.

Events uses Basic Authentication to communicate with the Microsoft Exchange Server. To secure the communication, you must enable SSL. For more information, see:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/56bdf977-14f8-4867-9c51-34c346d48b04.mspx?mfr=true

You must also ensure that the SSLAlwaysNegoClientCert property is set to true in IIS. The SSLAlwaysNegoClientCert property controls SSL client connection negotiations.

For example, use the following command to set the SSLAlwaysNegoClientCert property:

CScript.exe adsutil.vbs SET w3svc/1/SSLAlwaysNegoClientCert true

For more information about the SSLAlwaysNegoClientCert property, see:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/bce0fb87-79ea-40cd-963f-239545b61a12.mspx?mfr=true

Microsoft Exchange Server 2010 - Limitations

There are currently no known limitations.

Registering Events Servers

You can register multiple events servers for WebCenter Portal, but only one is active at a single 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 topics:

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 WebCenter Portal.
  2. From the WebCenter Portal menu, select Settings > Service Configuration.
  3. On the WebCenter Portal Service Configuration page, select Personal Events.
  4. To connect to a new events server instance, click Add.
  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 WebCenter Portal.

    Table 8-2 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 WebCenter Portal.

    Connection Type

    Select the Microsoft Exchange Server you want to connect to:

    • Microsoft Exchange Server 2010

    • Microsoft Exchange Server 2013

    Active Connection

    Select to use this connection for events in WebCenter Portal.

    While you can register multiple events server connections, only one connection is used by events—the default (or active) connection.
  6. Enter connection details for the events server.

    Table 8-3 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 events with an external application. External application credential information is used to authenticate users against the Microsoft Exchange Server hosting events.
  7. Click OK to save this connection.
  8. To start using the new (active) connection you must restart the managed server on which WebCenter Portal is deployed.

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 createPersonalEventConnection and setPersonalEventConnection in WebCenter WLST Command Reference Reference.

Note:

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

Choosing the Active Events Server Connection

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

This section includes the following topics:

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 WebCenter Portal.
  2. From the WebCenter Portal menu, select Settings > Service Configuration.
  3. On the WebCenter Portal Services Configuration page, select Personal Events.

    The Manage Personal Events Connections table indicates the current active connection, if any.

    Figure 8-6 Active Connection for Personal Events

    Description of Figure 8-6 follows
    Description of "Figure 8-6 Active Connection for Personal Events"
  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 WebCenter Portal is deployed.

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 setPersonalEventConnection in WLST Command Reference for WebLogic Server.

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.

Note:

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

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 WebCenter Portal is deployed.

This section includes the following subsections:

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 WebCenter Portal.
  2. From the WebCenter Portal menu, select Settings > Service Configuration.
  3. 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 8-3

  6. Click OK to save your changes.
  7. To start using the updated (active) connection you must restart the managed server on which WebCenter Portal is deployed.

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 setPersonalEventConnection in WebCenter WLST Command Reference Reference .

Note:

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

Deleting Event Server Connections

You can delete events server connections at any time, but use caution 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:

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 WebCenter Portal.
  2. From the WebCenter Portal menu, select Settings > Service Configuration.
  3. From the list on the WebCenter Portal Service Configuration page, select Personal Events.
  4. Select the connection name, and click Delete.

    Note:

    Before restarting the managed server, select another connection as active; otherwise, the service is disabled.

  5. To make this change you must restart the managed server on which WebCenter Portal is deployed.

Deleting Event Server Connections Using WLST

Use the WLST command deleteConnection to remove an events server connection. For command syntax and examples, see deleteConnection in WebCenter WLST Command Reference Reference.

Note:

To effect this change you must restart the managed server on which WebCenter Portal is deployed.