Skip Headers
Oracle® Fusion Middleware Administering Oracle WebCenter Portal
11g Release 1 (11.1.1.8.3)

Part Number E27738-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
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 Mail

This chapter describes how to configure and manage mail for WebCenter Portal. It also describes how to configure the "Send Mail" feature, which allows application assets to send mail directly from them. The Send Mail feature does not require mail. That is, even if the Mail component has not been configured in WebCenter Portal, users can send mail notifications. For more information about using Send Mail notifications, see the "About the Send Mail Feature" section in Oracle Fusion Middleware Using Oracle WebCenter Portal.

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

Note:

Configuration changes for mail, through Fusion Middleware Control or using WLST, are not dynamic, so you must restart the managed server on which WebCenter Portal or your Portal Framework application is deployed for your changes to take effect. See Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

This chapter includes the following topics:

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 in the deployed application:

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

15.1 About Mail Server Connections

Oracle WebCenter Portal supports the Microsoft Exchange Server or any mail server that supports IMAP4 and SMTP. To enable users to access mail and perform basic operations such as read, reply, and forward within WebCenter Portal or your own Portal Framework application, you must first register the appropriate mail server. Mail is not configured out-of-the-box.

You can register multiple mail server connections:

15.2 Configuration Roadmaps for Mail

Use the roadmaps in this section as an administrator's guide through the configuration process:

15.3 Mail Server Prerequisites

This section includes the following subsections:

15.3.1 Mail Server - Installation

See your mail server documentation for installation information.

15.3.2 Mail Server - Configuration

For WebCenter Portal, you can allow WebCenter Portal to create and manage portal distribution lists. This feature is supported only with Microsoft Exchange.

If enabled, a portal distribution list is created automatically whenever a portal is created. Users added or removed from the portal are implicitly added or removed from the corresponding portal distribution list, provided that the LDAP Base DN does not change (only one LDAP Base DN is supported) and that users created on Microsoft Exchange Active Directory correspond with users created in the identity store used by WebCenter Portal. To disable this feature, do not enter the LDAP (Active Directory) server details in the mail connection.

For more information, see step 7 of Section 15.4.1, "Registering Mail Servers Using Fusion Middleware Control."

For information about adding users on a mail server, see the mail server's product documentation. For information about adding users to WebCenter Portal's identity store, see Section 31.3, "Adding Users to the Embedded LDAP Identity Store."

Microsoft Exchange 2007 is the only mail server for which there are configuration prerequisites. If you are working with a different mail server (including Microsoft Exchange 2003), then you can bypass the rest of this section.

15.3.2.1 Configuring Microsoft Exchange Server 2007 for WebCenter Portal

The Microsoft Exchange Server 2007 certificate must be added to the WebCenter Portal keystore. This requires the following steps.

  1. Section 15.3.2.1.1, "Obtain the Certificate from the Microsoft Exchange Server"

  2. Section 15.3.2.1.2, "Add the Certificate to the WebCenter Portal Keystore"

  3. Restart the server after the certificate is imported.

15.3.2.1.1 Obtain the Certificate from the Microsoft Exchange Server

Obtain the certificate from your mail server installation administrator. This section describes one way to get the certificate from the Microsoft Exchange Server.

Follow these steps to obtain the certificate from a Microsoft Exchange 2007 server.

  1. Open a browser and connect to your IMAP server with the following command:

    https://host_name/owa
    

    Where host_name is the name of the Microsoft Exchange Server.

  2. Place your cursor on the page, right-click, and select Properties, then click Certificate.

  3. In the popup window, click the Details tab, and click Copy to File...

    Be sure to use the DER encoded binary (X.509) format, and copy to a file.

  4. Convert the .DER format certificate to .PEM format.

    Note:

    WebLogic only recognizes .PEM format.

    Use Firefox 3.0 or later to download the certificate directly to .PEM format. For other browsers, use the WebLogic Server der2pem tool to convert to .PEM format. For more information about der2pem, see Oracle Fusion Middleware Command Reference for Oracle WebLogic Server.

15.3.2.1.2 Add the Certificate to the WebCenter Portal Keystore
  1. Import the downloaded certificate into the keystore, which is generally the file named cacerts in the JAVA_HOME. For example:

    keytool -import -alias imap_cer -file cert_file.cer -keystore cacerts -storepass changeit
    

    Where cert_file is the name of the certificate file you downloaded. In a standard installation, the JAVA_HOME is in the following location:

    /scratch/wcinstall/ps2/1225/wlshome/jrockit_160_17_R28.0.0-616
    

    See Section 33.4.2.1.3, "Configuring and Exporting the Certificates," for information about adding the certificate to the keystore.

  2. Restart the server.

15.3.2.1.3 Microsoft Exchange Server Considerations
  • The IMAP port is 993 and secured true. SMTP port is 587 and secured true.

    (Microsoft Exchange Server 2005 used 465.)

  • If you see the following error, then you must change the trust store entry in the domain startup file setDomainEnv.sh:

    Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
     at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:771)
     at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
     at java.security.KeyStore.load(KeyStore.java:1185)
     at com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl.getCacertsKeyStore (TrustManagerFactoryImpl.java:202)
     at com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl.getDefaultTrustManager (DefaultSSLContextImpl.java:70) 
    

    To change the entry:

    1. Shutdown the managed server on which WebCenter Portal is deployed.

    2. Edit the domain startup script setDomainEnv located at:

      UNIX: DOMAIN_HOME/bin/setDomainEnv.sh

      Windows: DOMAIN_HOME\bin\setDomainEnv.cmd

    3. Add the Java property, as follows:

      -Djavax.net.ssl.trustStore=<path to truststore> -Djavax.net.ssl.trustStorePassword=<truststore password>
      

      For example:

      set JAVA_PROPERTIES=
      -Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME%
      -Djavax.net.ssl.trustStore=C:\jive\mailtool\jssecacerts
      -Djavax.net.ssl.trustStorePassword=changeit
      
    4. Restart the managed server.

15.3.3 Mail Server - Security Considerations

For more information, see Section 35.8, "Securing the WebCenter Portal Connection to IMAP and SMTP with SSL."

Note:

If LDAP is configured to run in secure mode, then add the LDAP Secured property (set to true/false) to use LDAP while creating distribution lists. For more information, see Table 15-5.

15.3.4 Mail Server - Limitations

In WebCenter Portal, mail requires a Microsoft Exchange mail server connection to enable automatic WebCenter Portal distribution list management.

15.4 Registering Mail Servers

You can register multiple mail server connections. To start using the new mail connections you must restart the managed server on which WebCenter Portal is deployed.

This section includes the following subsections:

15.4.1 Registering Mail Servers Using Fusion Middleware Control

To register a mail server with WebCenter Portal:

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

  2. Do one of the following:

    • For WebCenter Portal - From the WebCenter Portal menu, select Settings > Service Configuration.

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

  3. On the WebCenter Portal Service Configuration page, select Mail Server.

  4. To connect to a new mail server, click Add (Figure 15-3).

    Figure 15-3 Configuring Mail Servers

    Description of Figure 15-3 follows
    Description of "Figure 15-3 Configuring Mail Servers"

  5. Enter a unique name for this connection, and indicate whether this connection is the active (or default) connection for the application (Table 15-3).

    Table 15-3 Mail Server 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.

    Active Connection

    Select to indicate whether this connection is the default (or active) connection for mail.

    You can register multiple mail server connections:

    • WebCenter Portal supports multiple mail connections. The mail connection marked active is the default connection for mail. All additional connections are offered as alternatives; users can choose which one they want to use through user preferences.

    • Portal Framework application only use one mail connection—the connection marked active. Any additional connections are ignored.


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

    Table 15-4 Mail Server Connection Details

    Field Description

    IMAP Host

    Enter the host name of the computer where IMAP (Internet Message Access Protocol) is running.

    IMAP Port

    Enter the port on which IMAP listens.

    IMAP Secured

    Indicate whether a secured connection (SSL) is required for incoming mail over IMAP.

    SMTP Host

    Enter the host name of the computer where SMTP (Simple Mail Transfer Protocol) is running.

    SMTP Port

    Enter the port on which SMTP listens.

    SMTP Secured

    Indicate whether a secured connection (SSL) is required for outgoing mail over SMTP.

    Associated External Application

    Associate the mail server with an external application. External application credential information is used to authenticate users against the IMAP and SMTP servers. Mail uses the same credentials to authenticate the user on both IMAP and SMTP.

    You can select an existing external application from the list, or click Create New to configure a new external application. For more information, see Chapter 23, "Managing External Applications."

    The external application for mail must use Authentication Method=POST, and you can customize some mail header fields (with Display to User enabled):

    • Property: mail.user.emailAddress (who the mail is from)

      Property: mail.user.displayName (display name from the mail)

      Property: mail.user.replyToAddress (address used to reply to the mail)

    These properties ensure that a specific mail address is the same in the external application and in the mail server. They are added to the mail connection and are used by mail for the From, Display Name and Reply To fields (Figure 15-4). See Table 15-8 for Additional Properties configuration.

    If your application offers a self-registration page with the facility to mail user ID information on request, then you must ensure that public credentials are configured for the external application selected here. If public credentials are not defined, then mail cannot be sent to users on their request. WebCenter Portal, for example, offers this feature on its default self-registration page.


  7. Specify LDAP connection details for the Active Directory server managing WebCenter Portal distribution lists (Table 15-5).

    WebCenter Portal supports Microsoft Exchange where distribution lists are managed on an Active Directory server.

    Note:

    Active Directory server details must be provided as part of the mail connection for distribution lists to work in WebCenter Portal.

    Table 15-5 LDAP Directory Server Configuration Parameters

    Field Description

    LDAP Host

    Enter the host name of the computer where the LDAP directory server (Lightweight Directory Access Protocol) is running.

    LDAP Port

    Enter the port on which the LDAP directory server listens.

    LDAP Base DN

    Enter the base distinguished name for the LDAP schema. For example, CN=Users,DC=oracle,DC=com.

    LDAP Domain

    Enter the domain appended to distribution list names.

    For example, if the domain value is set to example.com, then a portal named Finance Project maintains a distribution list named FinanceProject@example.com.

    LDAP Administrator User Name

    Enter the user name of the LDAP directory server administrator.

    A valid user with privileges to make entries into the LDAP schema.

    LDAP Administrator Password

    Enter the password for the LDAP directory server administrator.

    The password is stored in a secured store.

    LDAP Default User

    Enter a comma-delimited list of user names to whom you want to grant moderation capabilities. These users become members of every portal distribution list that is created. The users specified must exist in the base LDAP schema (specified in the LDAP Base DN field).

    LDAP Secured

    Indicate whether a secured connection (SSL) is required between WebCenter Portal and the LDAP directory server.


  8. Configure advanced options for the mail server connection (Table 15-6).

    Table 15-6 Mail Server Connection - Advanced Configuration

    Field Description

    Connection Timeout (seconds)

    Specify a suitable timeout for the connection.

    This is the length of time (in seconds) WebCenter Portal waits for a response from the mail server before issuing a connection timeout message.

    The default is -1, which means that the default is used. The default is 10 seconds.


  9. Optionally, you can add more parameters to the mail server connection (Table 15-7).

    Table 15-7 Additional Mail Connection Properties

    Additional
    Connection Property
    Description

    charset

    Characterset used on the connection.

    The default charset is UTF-8. To use a different characterset, such as ISO-8859-1, set the charset connection property.

    Various IMAP properties

    Any valid IMAP connection property. For example, mail.imap.connectionpoolsize.

    A list of valid IMAP properties are listed in documentation for the com.sun.mail.imap package at: http://javamail.java.net/nonav/docs/api

    Various SMTP properties

    Any valid SMTP connection property. For example, mail.smtp.timeout.

    A list of valid SMTP properties are listed in the documentation for the com.sun.mail.smtp package at: http://javamail.java.net/nonav/docs/api


    If additional parameters are required to connect to the mail server, expand Additional Properties and enter details as required (see Table 15-8).

    Table 15-8 Mail Connection - Additional Properties

    Field Description

    Add

    Click Add to specify an additional connection parameter:

    • Property Name -Enter the name of the connection property.

    • 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.


    Figure 15-4 Additional Properties for Mail Connection

    Description of Figure 15-4 follows
    Description of "Figure 15-4 Additional Properties for Mail Connection"

  10. Click OK to save this connection.

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

    For more information, see Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

15.4.2 Registering Mail Servers Using WLST

Use the WLST command createMailConnection to create a mail server connection. For command syntax and examples, see the "createMailConnection" section in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

Use the WLST command setMailConnectionProperty to add additional required properties through your external application. The external application for mail must use Authentication Method=POST, and you can customize some mail header fields (with Display to User enabled). For example:

setMailConnectionProperty(appName='webcenter', name='NotificationSharedConn', key='mail.user.emailAddress', value='john.doe@example.com')

setMailConnectionProperty(appName='webcenter', name='NotificationSharedConn', key='mail.user.displayName', value='John Doe')

setMailConnectionProperty(appName='webcenter', name='NotificationSharedConn', key='mail.user.replyToAddress', value='feedback@example.com')

where:

  • mail.user.emailAddress = Email Address ('From' from the mail)

  • mail.user.displayName = Your Name (display name from the mail)

  • mail.user.replyToAddress = Reply-To Address (address when replying to the mail)

These properties ensure that a specific mail address is the same in the external application and in the mail server. These properties are added to the Mail connection and are used by mail for the From, Display Name and Reply To fields.

For Exchange 2007 only, create an universal distribution list which means that the default property value of 2 should be updated to 8. Specify a value of 8 for the mail property mail.exchange.dl.group.type, as follows:

setMailServiceProperty(appName='webcenter', property='mail.exchange.dl.group.type', value='8')

If your application offers a self-registration page with the facility to mail user ID information on request, then you must ensure that public credentials are configured for the external application selected here. If public credentials are not defined, then mail cannot be sent to users on their request. WebCenter Portal, for example, offers this feature on its default self-registration page.

For command syntax and examples, see the "setMailConnectionProperty" section in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To configure mail to use the new mail server connection as its default connection, set default=1 (true). For more information, see Section 15.5.2, "Choosing the Active (or Default) Mail Server Connection Using WLST."

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 new connections you must restart the managed server on which WebCenter Portal or your Portal Framework application is deployed. For more information, see the "Starting and Stopping Managed Servers Using the Command Line" section in Oracle Fusion Middleware Administrator's Guide.

15.5 Choosing the Active (or Default) Mail Server Connection

You can register multiple mail server connections with WebCenter Portal, but only one connection can be designated as the default connection. The default connection becomes the back-end mail server for:

This section includes the following subsections:

15.5.1 Choosing the Active (or Default) Mail Server Connection Using Fusion Middleware Control

To change the default connection:

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

  2. Do one of the following:

    • For WebCenter Portal - From the WebCenter Portal menu, select Settings > Service Configuration.

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

  3. On the WebCenter Portal Services Configuration page, select Mail Server.

    The Manage Mail Server Connections table indicates the current active connection, if any (Figure 15-5).

    Figure 15-5 Mail Server - Active Connection

    Description of Figure 15-5 follows
    Description of "Figure 15-5 Mail Server - Active Connection"

  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 default connection you must restart the managed server on which WebCenter Portal is deployed. For more information, see Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

15.5.2 Choosing the Active (or Default) Mail Server Connection Using WLST

Use the WLST command setMailConnection with default=1 (true) to make an existing mail server connection the default connection for mail. For command syntax and examples, see the "setMailConnection" section in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

A connection does not cease to be the default connection for mail if you change the default argument from 0 to 1 (true to false).

To disable a mail connection, either delete it, make another connection the 'active connection', or use the removeMailServiceProperty command:

removeMailServiceProperty(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 "removeMailServiceProperty" section 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."

Note:

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

15.6 Modifying Mail Server Connection Details

You can modify mail server connection details at any time.

To start using updated mail connections you must restart the managed server on which WebCenter Portal is deployed.

This section includes the following subsections:

15.6.1 Modifying Mail Server Connection Details Using Fusion Middleware Control

To update mail server connection details:

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

  2. Do one of the following:

    • For WebCenter Portal - From the WebCenter Portal menu, select Settings > Service Configuration.

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

  3. On the WebCenter Portal Service Configuration page, select Mail Server

  4. Select the connection name, and click Edit.

  5. Edit connection details, as required.

    For detailed parameter information, see Table 15-4, "Mail Server Connection Details".

  6. Click OK to save your changes.

  7. To start using updated connection details you must restart the managed server on which WebCenter Portal is deployed. For more information, see Section 7.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

15.6.2 Modifying Mail Server Connection Details Using WLST

Use the WLST command setMailConnection to edit existing mail server connection details. For command syntax and examples, see the "setMailConnection" section in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

If additional parameters are required to connect to your mail server, use the setMailConnectionProperty command. For more information, see the "setMailConnectionProperty" section 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."

Note:

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

15.7 Deleting Mail Server Connections

You can delete mail server connections at any time, but use caution when deleting the active (or default) connection. If you delete the active connection, Mail task flows do not work, as they all require a back-end mail server.

When you delete a connection, consider deleting the external application associated with the mail server connection if the application's sole purpose was to support this connection. For more information, see Section 23.6, "Deleting External Application Connections."

This section includes the following subsections:

15.7.1 Deleting a Mail Connection Using Fusion Middleware Control

To delete a mail server connection:

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

  2. Do one of the following:

    • For WebCenter Portal - From the WebCenter Portal menu, select Settings > Service Configuration.

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

  3. On the WebCenter Portal Services Configuration page, select Mail Server.

  4. Select the connection name, and click Delete.

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

    Note:

    Before restarting the managed server, mark another connection as active; otherwise, mail is disabled.

15.7.2 Deleting a Mail Connection Using WLST

Use the WLST command deleteConnection to remove a mail server connection. For command syntax and examples, see the "deleteConnection" section 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."

15.8 Setting Up Mail Defaults

Use the WLST command setMailServiceProperty to set defaults for mail:

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

15.9 Testing Mail Server Connections

Confirm that the mail server is running by connecting to the server using any client, such as Thunderbird or Outlook.

For Microsoft Exchange, go to Administrative Tools - Services to confirm that the following components are running (Status: Started):

15.10 Configuring Send Mail Notifications for WebCenter Portal

System administrators are responsible for setting mail options through WebCenter Portal administration settings (Figure 15-6).

Figure 15-6 Setting Mail Options

Description of Figure 15-6 follows
Description of "Figure 15-6 Setting Mail Options"

From this page, you can assign the mail client for the Send Mail feature. This feature allows application assets to send mail directly from their task flows, using the Send Mail icon (Figure 15-7).

Figure 15-7 Send Mail Icon

Send Mail icon

For example, from an announcement, users can click the Send Mail icon to open a mail window prepopulated with information including the announcement text, author, date created, and location. They can edit and add to the mail, as necessary. The way the mail window is prepopulated depends on the resource sending it. For example, from a wiki, Send Mail opens a mail window prepopulated with the name of the wiki, the size, who created it and when, who modified it and when, and a URL link to the wiki.

Within a portal, the mail can be addressed to all members of the portal, which is the default distribution list that is created when the portal is created. Moderators (and anyone granted the Manage Configuration permission on the portal) set this through the Tools and Services page in the portal's administration settings. See the "Configuring the Mail Distribution List for a Portal" section in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

For all Send Mail notifications throughout WebCenter Portal, you can choose to use the local mail client, such as Microsoft Outlook or Mozilla Thunderbird, or WebCenter Portal's own Mail service. The local mail client is the default. The Send Mail feature does not require the Mail service, that is, if the Mail service is not yet configured, you can still use the Send Mail feature with WebCenter Portal's Mail service. Application specialists or portal moderators can specify whether portal participants can override the default mail client setting.

Note:

With some browsers, Send Mail notifications are garbled for many non-English languages. When multibyte characters are encoded (required for the "mailto:" protocol), the URL length exceeds the browser limit. As a workaround, configure the Send Mail feature to use WebCenter Portal's Mail service instead of the local mail client.

As the system administrator, you can also specify whether users can override the default mail client setting.

15.10.1 Enabling Shared Mail Connections for Send Mail Notifications

Users do not need to specify credentials when sending mail using WebCenter Portal's Mail service when shared credentials are configured for the external application that is associated with the mail server connection.

To enable shared mail connections:

  1. Confirm that your portal is using WebCenter Portal's Mail service to send mail.

    1. Open the Administration tab.

    2. Click Tools and Services, and then select Mail.

    3. Ensure that Default Mail Client for 'Send Mail' is set to WebCenter Portal's Mail Service.

    See also Section 15.10, "Configuring Send Mail Notifications for WebCenter Portal."

  2. Set up a mail connection that uses an external application configured with the shared credentials and record the mail connection name.

  3. Open the portal where shared mail credentials are required and specify the name of the shared mail connection.

    For details, see the "Configuring a Shared Mail Connection for a Portal" section in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

15.11 Troubleshooting Issues with Mail

This section includes the following subsections:

15.11.1 Mail is Not Accessible in Secure Mode

Problem

You configured mail to function in secure mode, but it is not accessible.

Solution

Ensure the following:

15.11.2 Mail is Not Accessible in Non-Secure Mode

Problem

You configured mail to function in non-secure mode, but it is not accessible.

Solution

Ensure the following:

15.11.3 Unable to Create Distribution Lists in the Non-Secure Mode

Problem

You are unable to create portal distribution lists in non-secure mode; that is, SSL is not configured on the LDAP server.

Solution

Check if the mail server has been reinstalled or the user has been deleted. Also ensure that the following parameters are configured accurately in non-secure mode, in the LDAP server:

  • ldapHost

  • defaultUser

  • ldapAdminPassword

  • ldapBaseDN

  • ldapPort

See Section 15.4, "Registering Mail Servers."

15.11.4 Unable to Create Distribution Lists in the Secure Mode

Problem

You are unable to create WebCenter Portal distribution lists in secure mode, that is, SSL is configured on the LDAP server.

Solution

Check if the mail server has been reinstalled or the user has been deleted. Also ensure that the following parameters are configured accurately in secure mode, in the LDAP server:

  • ldapHost

  • defaultUser

  • ldapAdminPassword

  • ldapBaseDN

  • ldapPort

  • ldap.connection.secure, 'true'

15.11.5 Provisioning of Mail Fails in a Portal (Default Distribution List not Created)

Problem

In WebCenter Portal, when accessing a portal's Tools and Services Mail page, the following error message appears "Provisioning of Mail service for this portal has failed" and the Distribution List field is blank.

Solution

Make sure that the portal name is unique. If the portal name is not unique, a distribution list already exists. You can select the existing distribution list or select another distribution list.

15.11.6 Unable to Configure the Number of Mail Messages Downloaded

Problem

You cannot configure how many mail messages are downloaded to each user's Inbox.

Solution

Use the setMailServiceProperty WLST command. For example, to download 100 mail messages from the mail client, specify the mail.messages.fetch.size parameter as 100, as shown in the following example:

setMailServiceProperty(appName='webcenter',  property='mail.messages.fetch.size', value='100')

For command syntax and examples, see the "setMailServiceProperty" section in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

15.11.7 Unable to Publish and Archive WebCenter Portal Mail

Problem

You are unable to archive WebCenter Portal mail.

Solution

If the archiving fails, check the following:

  • In WebCenter Portal, navigate to Administration > Tools and Services > Discussions. Check whether the required configuration is accurate. For details, see the "Publishing Portal Mail in a Discussion Forum" section in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

  • Check whether the user account configured here is a member of the distribution list.

  • For a particular portal, check whether the forum configured is available in the discussions server. For details, see the "Publishing Portal Mail in a Discussion Forum" section in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

  • Check whether the user who sends mail to the distribution list is available in the discussions server and the mail address is the same.

15.11.8 Changing Passwords on Microsoft Exchange

Problem

If multiple users log on to Microsoft Exchange with the same user name and password, and then one user changes the password, the original password remains valid until all users log off.

For example, say the current password of the user monty is mypassword. Two users, A and B, log on from different clients using WebCenter Portal or Microsoft Exchange. Both log on as monty/mypassword, and both are able to see the mail messages. Now user A changes the password in Microsoft Exchange to oracle1. Because there currently are clients using the passwords oracle1 and mypassword, both are valid passwords; that is, new users can log on as monty/mypassword and still see the mail messages.

Solution

After all existing users with the original password log off, the new password takes effect. Until then, users can use both passwords to log on.

15.11.9 Mail Content Sent as Attachments

Problem

When users receive mail in Framework applications, message content is shown as an attachment (named content.html) rather than within the message body. This can occur if the mail server is running Microsoft Exchange Server 2003 and the "Update Rollup 3 for Microsoft Exchange Server 2007" is not yet installed.

Solution

Download and install "Update Rollup 3 for Microsoft Exchange Server 2007" which fixes this issue. For more information, see http://support.microsoft.com/kb/930468.