Setting Up Third-Party Email and Calendar

This chapter provides overviews of the Email pagelet and Calendar Events pagelet, basic email and calendar setup steps, application and mail server configuration, and the Microsoft Exchange/Outlook integration. This chapter also discusses how to:

Integrate with Microsoft Exchange 2000 or 2003.
Integrate with Lotus Notes email and calendar.
Configure the server for POP mail.
Assign primary mail systems.
Set up additional mail systems.

Understanding the Email Pagelet and Calendar Events Pagelet

PeopleSoft Enterprise Portal offers homepage pagelets that enable users to access email and calendar information without leaving the portal. The portal administrator sets up a default mail system and can also (optionally) enable external Post Office Protocol 3 (POP3) mail systems. Users then configure their own homepage Email pagelet and Calendar Events pagelet with their IDs and passwords. If multiple mail systems are enabled, users can include mail from multiple systems on their Email pagelet.

Because the Email pagelet and Calendar Events pagelet share the same integration technology, users need to install and set up these pagelets only once. For the homepage, however, users must separately select each pagelet that is to be included.

Email Integration

The Email pagelet displays a list of the latest email messages. If the email system is web-enabled, users can navigate to that email system from a link on the pagelet. Integrations are delivered for:

Lotus Notes/Domino.
Microsoft Outlook Web Access/Exchange.
Post Office Protocol (POP) mail systems.

POP-enabled mail can be used as a primary or secondary email. At one time, you can have Exchange, Lotus Notes, or POP3 as the primary email in the pagelet along with multiple POP-enabled systems as the secondary email.

Calendar Integration

The Calendar Events pagelet displays appointments for the current day. Integrations are delivered for:

Lotus Notes/Domino.
Microsoft Outlook Web Access/Exchange.

See Also

Email Pagelet

Calendar Events Pagelet

Understanding Basic Email and Calendar Setup Steps

The following steps provide a roadmap for setting up the Email pagelet and Calendar Events pagelet.

Note. Detailed setup instructions for each third-party email system are described later in this chapter.

The portal administrator configures application and email servers.
- Lotus Notes.
  
  Download and install the necessary files from Java and Lotus sites.
  
  Make the relevant changes on the Domino server end and perform other operating-system-related setting changes.
  
  See Integrating with Lotus Notes Email and Calendar.
- Microsoft Exchange.
  
  Install the delivered PeopleSoft Active Server Page files in the relevant places and change the security.
  
  See Integrating With Microsoft Exchange 2000 or 2003.
- POP mail.
  
  Download and install the required files from the Java site.
  
  See Configuring the Server for POP Mail.
The portal administrator and individual users complete the integration with the Email pagelet and Calendar Events pagelet:
1. The portal administrator selects and sets up the primary email and calendar on the E-mail and Calendar Defaults page.
  
  See Assigning Primary Mail Systems.
2. Each user sets up the pagelet's user ID and password.
  
  See Email Pagelet, Calendar Events Pagelet.

Understanding Application and Mail Server Configuration

In accordance with the primary email and calendar systems that are selected for the Email pagelet and Calendar Events pagelet, system administrators must configure servers with special settings, files, and views. It might also be necessary to configure the servers for any additional POP mail systems.

This chapter provides information about setting up the following supported applications and mail server configurations:

Microsoft Exchange/Outlook 2000 Email on Windows.
Microsoft Exchange/Outlook 2003 on Windows.
Lotus Notes Email and Calendar using a local Lotus Notes client.
Lotus Notes Email and Calendar using a remote Lotus Notes client.
POP mail.

See Also

Setting Up Additional Mail Systems

Enterprise PeopleTools 8.46 PeopleBook: Internet Technology, "Administering Portals"

Integrating With Microsoft Exchange 2000 or 2003

This section provides an overview of prerequisites for integrating with Exchange 2000 or 2003 and discusses:

How to install and configure ASP files for Exchange 2000 or 2003.
Implementation tips for integrating with Exchange 2000 or 2003.

Understanding Integration With Microsoft Exchange

The Email pagelet on the portal homepage can display email from Microsoft Exchange when it is designated as the primary mail system. It requires Outlook Web Access (OWA), which enables access to Outlook using a browser. OWA requires that a Microsoft Internet Information Server (IIS) be running with access to an Exchange server. PeopleSoft Enterprise Portal supports integration with the following Microsoft configurations:

Microsoft Exchange/Outlook 2000 on Windows.
Microsoft Exchange/Outlook 2003 on Windows.

In the PeopleCode, an iScript makes a call to a business interlink enterprise integration point (EIP) named EO_PE_MSINBOX_EMAIL, which makes a request to the ASPs on the Exchange server. The ASPs send back a response in HTML format through the business interlink. PeopleCode then extracts the HTML to get the relevant email and calendar data and then formats the information and displays it in the Email and Calendar Events pagelets.

Note. To research the technical details of any integration point used by PeopleSoft applications, refer to the Interactive Services Repository that can be found in the Documentation section of the Customer Connection website.

PeopleCode and PeopleSoft Business Interlinks are used on the PeopleSoft side. On the Exchange server side, ASPs, based on the Collaborative Data Objects (CDO) Rendering Library, are installed. You can search the Microsoft website to learn more about the CDO Rendering Library.

Prerequisites

Before integrating Microsoft Exchange 2000 or 2003 with the PeopleSoft Enterprise Portal, you must:

Plan for the functionality that you need.
Install the Windows 2000/2003 server and related systems.

Exchange must be installed in a domain that contains a Windows 2000/2003 server that is configured as a domain controller with a global catalog.

Note. During the Windows 2000/2003 server setup, you must install the Network News Transfer Protocol (NNTP) service.
Install SP1 for Windows 2000.
Address system security and maintenance issues. Refer to the Windows 2000 documentation.
Install the Microsoft Exchange 2000 or 2003 server. Refer to the installation guide.

The following installation instructions require this to be the only messaging server in your organization.
Create mailboxes for users on the Exchange server.

Select Active Directory Users and expand the domain name to see the Users folder.

Installing and Configuring Active Server Page Files for Exchange 2000 or 2003

You can perform the following steps only after the Microsoft Exchange 2000 or 2003 server has been installed.

To install and configure ASP files:

Create a new folder, such as c:\aspcode, on the Microsoft Exchange 2000 or 2003 machine.
Copy the following files into the newly created folder:
- Constant.inc.
- Amprops.inc
- Lang.inc
- Psmsinbox2003.asp
- Psmcal2003_1day.asp
Map the new folder to the Virtual Directory for Exchange 2000 or 2003 using Microsoft Internet Services Manager (ISM):
1. Access ISM from your Windows machine by navigating to Start, Programs, Administrative Tools.
2. Expand the left-side Domain name folder to see the Default Web Site folder.
3. Right-click and select New, Virtual Directory.
  
  This starts a wizard, which takes you through the relevant steps.
4. In the wizard, select the folder that contains all of the PeopleSoft ASP files as the source (for example, c:\aspcode).
  
  It is important that you select the same folder in which you installed the delivered PeopleSoft ASP files.
5. For easy reference, give the virtual directory the same name as the folder in which you installed the delivered ASP files (for example, aspfolder).
  
  Note. Once you have mapped the folder to the virtual directory, you will see your virtual directory and its contents in the ISM folder's Default Web Site.
Ensure that the Basic Authentication value is used as a part of the directory security for the default website.
1. Access ISM from your Windows machine by navigating to Start, Programs, Administrative Tools.
2. Go to the Default Web Site in the domain folder and find your mapped virtual directory, as specified in step 3e.
3. Right-click and select Properties.
4. Select the Directory Security tab and select Anonymous Access and Authentication.
5. Select Basic Authentication.

Important! The URL that you use on the Email and Calendar Defaults page must use the format http://<servername>/<aspfolder>, where aspfolder is the folder name that is used in the virtual directory specified above. If this folder name is not the virtual folder name, the integration will not work.

When the configuration of applications and mail servers is complete, proceed to assigning the primary mail system in the PeopleSoft Enterprise Portal.

See Assigning Primary Mail Systems.

Implementation Tips for Configuring Exchange 2000 or 2003

If the pagelet cannot display the messages, but the Microsoft Outlook link on the pagelet works, check the following:

In the browser, enter a URL using the following format, replacing the domain and user IDwith the individual user's email account and user ID:

http://<Outlook Web Access name>/aspfolder/Psmsinbox2003.asp?mailbox=<userid>&exchsvr=<Exchange Server name>&numrows=5
If there is an error on this website (that is, on an ASP page), then the folder in which you stored the delivered PeopleSoft ASP files is not properly mapped as a virtual drive.

If the virtual drive is correctly mapped, but this URL site still generates errors that are MAPI-related, then check the IMS security to ensure that the Basic Authentication value has been selected.

See Installing and Configuring Active Server Page Files for Exchange 2000 or 2003.
If after changing the security you still receive MAPI-related errors when trying to access the above URL, then perform the following verifications on the Members Of tab of the User Properties in Active Directory Users and Computers.
1. Navigate to the Members Of tab by going to Windows Start, Programs, Administrative Tools, Active Directory Users and Computers.
2. Select the Users folder in the left-side domain folder.
3. Right-click the appropriate user and select Properties.
4. On the Members Of tab, look at all domains for which the user is a member and try to make the user a member of the relevant domains and directories.
  
  Correcting the Member Of properties can resolve several MAPI-related permission issues with the above URL.

Identifying Typos in Output Parameters

Make the following setting changes to display debugging information on the pagelet. It displays data that is being fed to the business interlink. Check the accuracy of this data.

To identify typos in output parameters:

In PeopleSoft Application Designer, open the record WEBLIB_EMAIL.
Open the FieldFormula PeopleCode.
Search for the following iScript function:
```
Function IScript_mail()
```
Locate the second line of the function:
```
&Debug = False; 
```
Set the value to True.

The set of statements should now look like the following:

Function IScript_mail()
   /* Set the debug flag to True, for getting all the debug information, 
		/* otherwise set it to false */
   &Debug = True;
   &titleStyle = "PABOLDBLUETEXT";

Save. The debugging information will display on the pagelet.

Ensuring That Microsoft Exchange is Working Over the Web

To ensure that Microsoft Exchange is working:

Click the Microsoft Outlook link that displays on the Email pagelet.
Supply the user ID and password in the dialog box.

Ensure that you use the <DOMAIN NAME>\<User Id> format when specifying a user outside of the domain in which the Microsoft Exchange server resides.
If this link opens a web-based outlook, then proceed to the next section. If the link does not open, then contact the Exchange server administrator.

Checking the Outlook Web Access URL

To verify that the Outlook Web Access URL is working:

Use the following format for an Outlook Web Access URL:

http://<Outlook Web Access name>/aspfolder/Psmsinbox2003.asp?mailbox=<userid>&exchsvr=<Exchange Server name>&numrows=5

Open a new browser window and enter the appropriate URL for your version of Exchange. Tabular data consisting of mail headers should be returned.

If this step does not work, then the errors may possibly be the result of a setup issue. Return to the Exchange administration steps to verify the setup issues.

See Installing and Configuring Active Server Page Files for Exchange 2000 or 2003.

If this step works, but email is still not accessible, then add a few emails to the account and try again.

If this is working, then try the next section.

Verifying Business Interlink Settings

To verify the Business Interlink settings:

Note. Be very careful about any possible typographical errors. Review any changes you make carefully ensuring that there are no errors.

If the Outlook Web Access URL is working, open PeopleSoft Application Designer and open the Business Interlink EO_PE_MSINBOX_EMAIL.
Select the Input tab and set the following values:

mailbox

User's mailbox name.

exchsvr

The Microsoft Exchange server name.

numrows

Number of rows.
Select the Settings tab and set the following values:

Method

GET

SSL

No, if SSL is not enabled. Otherwise, set to Yes.

MerchantURL

Enter http://<Outlook Web Access name>/aspfolder
Test the Business Interlink.
1. Save the Business Interlink.
2. Launch the tester by clicking the last Launch Tester toolbar button.
3. Run the Business Interlink Tester. To run the Business Interlink Tester, select View, Run, or click the Run button on the toolbar.
  
  If the Business Interlink Tester returns a return_status of Error, there is a problem in the setup. Verify the security, the ASP files, and the OWA links.

Understanding Browser Errors

This section explains several browser error messages that may display for the Email pagelet integration, along with possible associated errors.

Page cannot be found error.

This error screen could mean that the file psmsinbox2003.asp is not available. This can happen because:
- Either the file is missing, or because the virtual folder is wrong or not mapped correctly.
- There's a typographical error in the file name.
Network password error.

If the Enter Network Password dialog box displays after executing the OWA that was formed, it may be because the domain name, user ID, or password entered for the user is missing or wrong.
Page cannot be displayed error.

This page can display under two circumstances.
- If this page appears when you place the OWA URL in the browser, verify that the OWA server name is correct.
- This page can also appear when the URL tries to access a resource that does not exist due to a wrong mailbox or a wrong Microsoft Exchange server name.
You are not authorized to view this page.

This page appears if the either the user ID or password are incorrect.

Integrating with Lotus Notes Email and Calendar

This section provides overviews of the Lotus Notes email and calendar integration and prerequisites, and discusses how to:

Integrate with a Lotus Notes email and calendar client running on a local application server.

Note. This integration can be used with Windows-based application servers.
Integrate with a Lotus Notes email and calendar client running on a remote application server.

Note. This integration can be used with Windows and UNIX-based application servers.
Complete the Lotus Notes email and calendar integration for both local and remote application server configurations.

Note. This documentation provides separate sections for configuring integrations in which the Lotus Notes email and calendar client is running on a local application server and in which the client is running on a remote application server. Once the servers are configured, the remaining setup steps are the same for both client configurations and are discussed in one common section.

Understanding Integration With Lotus Notes Email and Calendar

The Email pagelet on the PeopleSoft Enterprise Portal homepage can display email from Lotus Notes client or iNotes when Lotus is designated as the primary mail system. Integration requires a specific configuration of the portal application server and a hub Domino server.

There are different configuration instructions for integrations in which the Lotus Notes client is running on a local application server and in which the client is running on a remote application server. The principles are the same; however, an additional process runs on the Notes Super ID client/server machine for the remote configuration.

How the Integration Works

PeopleSoft Enterprise Portal integrates with Lotus Notes mail files to retrieve an individual's new email and calendar appointment lists. To retrieve this information from each user's mail file, PeopleSoft Enterprise Portal uses Java Data Base Connectivity (JDBC), which renders a Lotus Notes database as if it were a relational database of tables, rows, and columns.

For the JDBC solution to work:

Lotus Notes client software must be loaded on the same machine as the Java class that runs the PeopleSoft Enterprise Portal integration—usually the portal application server.
The Lotus Notes client application must be running and logged in with a particular ID file (Super ID).

This setup is required because JDBC needs several .dll files (which are installed with that Notes client on that machine) and because the JDBC solution must respect the security of Lotus Notes.
For JDBC to retrieve mail data, the machine running the application server must be logged into Lotus Notes with a Lotus Notes Super ID that has access to each user's mail data. Otherwise, users can bypass security measures to gain access to restricted Notes databases.
The Lotus Notes client must be running before the application server is booted.

Enabling iNotes

iNotes is the web-enabled solution for Lotus Notes. To enable users to launch iNotes from the Email pagelet, you must specify the iNotes URL on the Email and calendar Defaults page.

Working With Lotus Notes Remotely

If you have a UNIX application server installed, you must configure a Lotus Notes client system to run the JLotusServer process that will listen for Email and Calendar Event pagelet requests from the portal's UNIX application server. There must be a predefined network port identified in a configuration file that resides on both servers. The Lotus Notes client/server system processes a request from the portal application server and sends back the appropriate information.

Integrating With a Lotus Notes Client Running on a Remote Application Server

Completing the Lotus Notes Integration for All Supported Client Configurations

Assigning Primary Mail Systems

Prerequisites

The following prerequisites must be in place:

All mail files at an organization must refresh from a single mail file template, or there must be some other easy way for a Lotus Notes administrator to add two hidden custom views to each user's mail file.
There is a single Domino server that can run both the HTTP and DIIOP tasks for access by the portal.

This server should use Java security and have the corporate name and address book on it.
All users at the organization have an internet password stored in their Person document in the Lotus Name and Address Book on the Domino hub server.

A custom view that is added to the address book provides the location and file name of each user's mailbox.

Integrating With a Lotus Notes Client Running on a Local Application Server

When the primary email system is Lotus Notes and the Lotus client logged in with the Super ID runs on the same server as the portal application server, complete the steps outlined in this section to configure the Lotus Notes email and calendar functions.

Note. This integration can only be used with Windows-based application servers.

This section discusses how to locate .jar and .dll files.

Locating .jar and .dll Files using Lotus Domino Server 5.x

The Portal Administrator locates the .jar and .dll files.

Copy the Lotus Notes .jar and .dll files from their respective directories and set them up on the application server:

The following .jar files will reside in the PS_HOME\class directory:
- JdbcDomino.jar
- NCSO.jar
- Notes.jar
The following .dll files will reside in the winnt\system32 directory:
- JdbcDomino.dll
- JdbcDriver.dll
- JdbcRniDomino.dll

Note. When you transfer .jar files, use binary transfers, not ASCII transfers. Also, the required Java files must be installed in the proper directory for each portal application server.

Placing NCSO.jar and Notes.jar Files on Application Server Machine

You can copy the Notes.jar and NCSO.jar files onto the application server machine from your Lotus Domino Server installation.

The Notes.jar file can be located at C:\Lotus\Dominodirectory.
The NCSO.jar file can be located at C:\Lotus\Domino\Data\domino\javadirectory.

Place both files in the PS_HOME\class directory.

Note. The PS_HOME directory is the directory where you installed the PeopleSoft Enterprise Portal.

Placing the JdbcDomino.jar, JdbcDomino.dll, JdbcDriver.dll and JdbcRniDomino.dll Files on the Application Server Machine

For Lotus Notes 6.5, you can copy the following files from the Lotus Notes Client install directoryC:\lotus\notes\JdbcSql\Lib

Place the Jdbcdomino.jar file in the PS_HOME\class directory:
Place the following files in the C:\winnt\system32 directory:
- JdbcDomino.dll
- JdbcDriver.dll
- JdbcRniDomino.dll

Note. If you are connecting to Lotus Notes 5.x, contact the PeopleSoft Global Support Center for the JdbcDomino.jar, JdbcDomino.dll, JdbcDriver.dll, and JdbcDomino.dll files.

Integrating With a Lotus Notes Client Running on a Remote Application Server

When the primary mail system is Lotus Notes and the Lotus Super ID client runs on a remote portal application server, complete the steps outlined in this section to configure the Lotus Notes email and calendar functions.

Note. This integration can be used with Windows and UNIX-based application servers.

Prepare the Domino hub server.
Prepare the NT Notes client system to receive UNIX application server requests.
Extract .jar and .dll files to the Notes client system.
Prepare the UNIX application server to send requests to the Lotus system.

Preparing the Domino Hub Server

The Lotus Administrator prepares the Domino Hub Server.

To prepare the Domino hub server for portal application server access, enable the HTTP task and the DIIOP task on the Domino hub server that will be accessed by the portal application server to check user mail file location information.

Preparing the Windows Notes Client System to Receive UNIX Application Server Requests

The Portal Administrator prepares the Windows Notes client system to receive UNIX application server requests.

To prepare the Windows Notes client system to receive UNIX application server requests:

Install Java Virtual Machine on the Notes client machine.

You can download the latest Java Virtual Machine from http://java.sun.com
Create the directory JLotusServer on the Lotus Notes client server. For example: C:\JLotusServer
Copy the following PeopleSoft delivered files to the JLotusServer directory (these files can be found in the PS_HOME\class directory):
- com.peoplesoft.pa.pp.jar
- activation.jar
- mail.jar
Copy the PeopleSoft JLotusServer.config file to the JLotusServer directory; it can be found in the PS_HOME\scripts directory on your file server.
Copy the following third-party files from your Lotus Domino Server installation to the JLotusServer directory:
- Notes.jar — located in C:\Lotus\Domino directory
- NCSO.jar — located in C:\Lotus\Domino\Data\domino\java directory
Copy the third-party JdbcDomino.jar file from your Lotus Notes Client installation to the JLotusServer directory. It is located in the C:\lotus\notes\JdbcSql\Lib directory.
Copy the following third-party files from your Lotus Notes Client to the C:\WINNT\System32 directory.
- JdbcDomino.dll — located in C:\lotus\notes\JdbcSql\Lib directory
- JdbcDriver.dll — located in C:\lotus\notes\JdbcSql\Lib directory
- JdbcRniDomino.dll — located in C:\lotus\notes\JdbcSql\Lib directory
On your Windows machine, set system variable CLASSPATH to point to C:\JLotusServer and C:\JLotusServer\com.peoplesoft.pa.pp.jar.
Locate the Jmail.config file in the PS_HOME\scripts directory on your file server and copy it to your application server machine <PS_HOME>\appserv\<PORTAL DB NAME>\ directory.

Since Lotus Notes Client is running on a different machine than the application server, set LocalLotusNotesAccess to NO and provide appropriate values for JLotusServerIP and JlotusServerPort in the Jmail.config file.
Open the JLotusServer.config file with a text editor.
Change the JLotusServerPort value to the appropriate port number.

Ensure the same port number is identified in the JlotusServer.config file on the Lotus Notes client machineand the Jmail.config file on the application server machine.
Start JLotusServer by running C:\JLotusServer\java com.peoplesoft.pa.pp.JLotusServer at the DOS command prompt.

Completing the Lotus Notes Integration for All Supported Client Configurations

After setting up your local or remote Lotus Notes client application servers, complete the following Lotus Notes setup steps that are common to both client configurations.

This section discusses how to:

Place custom views in Lotus templates.
Create the Super ID.
Set up the Lotus Notes mail client.

Placing Custom Views in Lotus Templates

These instructions apply to both local and remote Lotus Notes client application server configurations.

To place custom views in Lotus templates:

The portal administrator sends the Portal_Lotus_Views.nsf file to the Lotus Notes administrator.

This file is provided on the PeopleSoft Enterprise Portal CD and can be found in PS_HOME in the scripts folder.

The Lotus Notes Administrator performs the following steps.
Open the Portal_Lotus_Views.nsf file in the Lotus Domino Designer.
Copy the two views, PS_PORTAL_MAIL and PS_PORTAL_CALENDAR, into the mail file template that is used for all mail files in the organization.
Copy the view PS_PORTAL_MAIL_LOCATION either into the Name and Address Book template in the organization (if one is used) or into the Name and Address Book of the hub Domino server that the portal application server accesses to retrieve user mail file information.
1. If the organization uses customized Domino user names that are not any of the entries listed in the User Name field of the Person document in the Name and Address Book, then customize the PS_PORTAL_MAIL_LOCATION view that you just copied.
2. To customize this view, open it in Lotus Domino Designer and change the first column of the view to reflect the customized Domino user names used in the organization.
  
  For example, if the entries in the User Name field are John Smith/ACME Corp and John Smith, but a custom Domino user name of jsmith is used, the column formula is @Left(FirstName;1)+LastName.
3. Change the first column of the PS_PORTAL_MAIL_LOCATION view only if the system uses custom Domino user names that are not any of the entries in the User Name field.

Creating the Super ID

The Lotus Notes Administrator creates the Super ID.

For JDBC to retrieve mail and calendar information from each user's mail file, it must use an ID that has reader access. For most organizations, this Super ID is an administrator ID that has manager access control list (ACL) access to each mail file.

Note. These instructions apply to both local and remote Lotus Notes client application server configurations.

To create a super ID:

Create a Lotus Notes ID that the portal will use as a Super ID for accessing all mail files.
Add this ID to the LocalDomainServers group in the Name and Address Book or to the group that has access to each user's mail file on all servers.

The JDBC code that supports pagelet email message listing requires that LocalDomainServers have manager access to each user's mail file.

By default, the Domino directory contains two groups: LocalDomainServers and OtherDomainServers. The LocalDomainServers group includes all servers in the current domain. Domino automatically adds servers that are registered in the current domain to the LocalDomainServers group. Each group must have an owner, who is usually an administrator. The ID file, which each company creates to administer servers, can be added to this LocalDomainServers group; therefore, it is likely to have all the necessary access privileges to each mail file.

Either this ID file (if it is listed individually in the ACL) or the group (if the group containing this ID file is listed) must be selected from the Add User dialog box of the Address Book when it is entered into the ACL (not typed in directly). This is necessary because in Lotus Notes, users do not have access to a database if their names are not entered into the ACL by selecting from the address book (versus typing or copying them).
Allow for the overnight design refresh task to update the design of each user's mail file.

Important! Verify that the Java/COM unrestricted section under the Notes Administrator has the names of the users who access their mail through the portal.

Setting Up the Lotus Mail Client

The Portal Administrator sets up the Lotus Mail Client.

Note. These instructions are similar for both local and remote Lotus Notes client application server configurations. We point out any differences.

To run the Lotus mail client:

Install the Lotus Notes client software (the Super ID .id file is required for the installation).
- For local configurations , install the Lotus Notes client software on the portal application server machine.
- For remote configurations, install the Lotus Notes client software on the Lotus Notes client system that will be running the JLotusServer application.
On the Environment tab of the System Properties dialog box, add to the system variable path the directory path where the Lotus Notes Super ID file exists (for example, c:\apps\notes\data).

For UNIX application servers, do this on the Lotus Notes client machine.
Launch the Lotus Notes client and log on with the Super ID.
- For local configurations, launch the Lotus Notes client on the portal application server machine.
- For remote configurations, launch the Lotus Notes client on the Lotus Notes client system that will be running the JLotusServer application .
Check the Lotus Notes Super ID to make sure that the option Don't prompt for a password from other Notes-based programs is selected:
1. Select File, Tools, User ID from the Lotus Notes menu bar.
2. When prompted, enter the password for the Super ID file.
3. Select the Don't prompt for a password from other Notes-based programs located on the Basic Information tab.

Step 4 is critical for the portal application to use Lotus Notes in the back end without prompting for a Lotus Notes login each time.

When the configuration of application and mail servers is complete, proceed to assigning the primary mail system in the PeopleSoft Enterprise Portal.

See Also

Assigning Primary Mail Systems

Configuring the Server for POP Mail

This section provides an overview of post office protocol (POP) configuration and prerequisites, and discusses how to extract .jar files.

Understanding POP Configuration

The setup for POP mail is optional. It is required only when the portal administrator has designated a primary mail system that is POP-based or has set up additional email selections for the email pagelet. POP mail requires correct placement of third-party .jar files from the Sun website to the portal application server.

POP mail integration requires the following:

If you access POP mail on an internal mail server, that mail server must be POP-enabled.
If you access POP mail from an external mail system, the remote POP mail server to which you point must be POP-enabled.

Also, users must set up their external mail accounts to POP forward.

Extracting .jar Files for POP Email Integration

This section discusses how to extract the following Sun .jar files into the <PS_HOME>\class Directory of the NT portal application server:

mail.jar
activation.jar
pop3.jar

Note. When you transfer .jar files, be sure to use binary transfers, not ASCII transfers. Also, you must install the required Java files in the proper directory for each portal application server.

Extracting mail.jar (JavaMail)

To download mail.jar:

FTP download mail.jar (JavaMail) from http://www.javasoft.com/products/javamail/index.html.
Extract the mail.jar file into the PS_HOME\class directory on each portal application server.
Delete the javamail1_1_3.zip file.

Extracting activation.jar (JavaBeans Activation Framework)

To download activation.jar:

FTP download activation.jar (JavaMail) from http://www.javasoft.com/products/javamail/index.html.
Extract the activation.jar file into the PS_HOME\class directory on each portal application server.
Delete the jaf1_0_1.zip file.

Extracting pop3.jar (POP3 Provider)

To download pop3.jar:

FTP download pop3.jar (POP3 Provider) from http://www.javasoft.com/beans/glasgow/jaf.html.
Extract the pop3.jar file into the PS_HOME\class directory on each portal application server.
Delete the pop31_1_1.zip file.

Note. The Sun Microsystems website from which the drivers are downloaded is external to PeopleSoft, and its content and layout might change at any time. For assistance in locating files on the Sun Microsystems website, contact Sun Microsystems.

Assigning Primary Mail Systems

The administrative information that you assign drives both the Email pagelet and Calendar Events pagelet. The portal supports Lotus Notes/Domino, Microsoft Outlook Web Access/Exchange, and various POP3 systems for email, and Lotus and Microsoft for calendars. Remember that only one email and calendar system is designated as the portal's default system. The default system is considered primary and is the first email section on a user's pagelet. It is possible to override the system default for an individual user.

This section discusses:

Designating the primary email and calendar system.
Overriding email and calendar settings for individual user IDs.
Support for SSL-enabled web servers.

Note. For the pagelets to be fully functional, you must complete setup procedures for the application and mail servers.

Email Pagelet

Calendar Events Pagelet

Pages Used to Assign Mail Servers

Page Name	Object Name	Navigation	Usage
E-mail and Calendar Defaults	EO_PE_ADMIN	Portal Administration, Pagelets, Email / Calendar, Email / Calendar Defaults	Designate the primary email and calendar system for the portal.
Email and Calendar by User	EO_PE_ADMIN_OPR	Portal Administration, Pagelets, Email / Calendar, Email / Calendar by User	Add overriding email and calendar settings for an individual user ID.

Designating the Primary Email and Calendar System

The Portal Administrator designates the primary email and calendar system.

Access the E-mail and Calendar Defaults page.

Note. The fields shown on this page vary depending on which email system is selected as the primary email system.

Primary E-mail System	Select the default email/calendar system for the portal. Additional fields display based on your selection. Microsoft (Outlook Web Access) Lotus Notes POP (No Calendar)
Microsoft Outlook Type	These fields when you select the Microsoft (Outlook Web Access) option in the Primary E-mail System group box. Select the MS Outlook type you want to use: MS Outlook Exchange 2000 MS Outlook Exchange 2003
Hardware Configuration	These fields when you select the Microsoft (Outlook Web Access) option in the Primary E-mail System group box. Single Box. Select if your hardware configuration is a single machine setup. Distributed (Different Boxes). Select if your hardware configuration is for a multiple machine setup.
URL for Mail Inbox	Enter a URL (the link on the pagelet transfers the user to this location in a new browser window): For Microsoft, enter the URL typically used for Outlook Web Access/Exchange Server URL. The URL should have the form: http://<server>/exchange, replacing <server> with the Exchange server name. Use the folder name exchange. The exchange name is the mapped folder name in the IIS installation. It maps to the physical folder in which Exchange is installed. Always use exchange as the folder name in the URL for Mail Inbox field. For Lotus, this field is relevant only for web-enabled iNotes mail. For POP mail, enter the mail server URL.
Server	This field displays when the Lotus Notes or POP (No Calendar) option is selected in the Primary E-mail System group box. Enter the server name. For Lotus Notes, enter the name of a Domino server on the network. Typically, this is a centralized hub server. This is the Domino server enabled with additional services and has the custom view PS_PORTAL_MAIL_LOCATION in the Name and Address Book. For POP mail, enter the POP mail server name. For example, for Yahoo!, enter pop.mail.yahoo.com.
File Name of Address Book	This field displays when the Lotus Notes option is selected in the Primary E-mail System group box. Enter the file name for the Lotus Notes name and address book.

Overriding Email and Calendar Settings for Individual User IDs

Access the E-mail and Calendar by User page.

Select the user ID for which you want to define overriding email and calendar information. The remaining fields function like those on the Primary E-mail and Calendar Defaults page. Entries on this page override the primary email system settings entered on that page.

Support for SSL-Enabled Web Servers

If your web server is SSL-enabled, in addition to specifying an HTTPS URL on the E-mail and Calendar Defaults page, you must do the following:

Open PeopleSoft Application Designer.
Select the Project EO_PE_EMAIL_CAL.
Open the Business Interface EO_PE_MSINBOX_EMAIL.
Select the Settings tab and set the SSL flag to Yes.
Save your changes.

Setting Up Additional Mail Systems

To enable users to add external POP email accounts to their Email pagelets, the portal administrator must set up a URL identifier and a URL for each POP mail system. Once these entries are stored in the URL Catalog, the POP mail system appears in the server and URL drop-down list boxes of the pagelet's Personalize Email Options - Add a Personal Email Account page.

This section discusses how to add and maintain mail system URLs.

Note. The POP mail system must have POP forwarding on a user's individual profile. Each user needs to set this with the external mail system. Some mail systems automatically activate POP forwarding; some (such as Yahoo!) require the user to change a profile setting, while others (such as Microsoft Hotmail) do not allow forwarding. Non-forwarding mail systems do not appear on the Email pagelet.

See Also

Working With the Email Pagelet

Pages Used to Set Up Additional Mail Systems

Page Name	Object Name	Navigation	Usage
URL Maintenance	URL_TABLE	PeopleTools, Utilities, Administration, URLs	Add a URL identifier and maintain a URL for a POP mail server. This definition enables the selection on the Add a Personal Email Account page accessed from the Email pagelet.

Maintaining URLs

Access the URL Maintenance page.

URL Identifier

Enter a URL identifier. The URL identifier indicates whether the URL points to a web address or to a POP3 mail server that cannot be accessed through the web.

For a web URL, the URL ID must start with MAIL_.

For a POP3 mail server, the URL ID must start with SERVERMAIL_.

Whatever follows the MAIL_ or SERVERMAIL_ prefix must be unique for each MAIL or SERVERMAIL ID.

For example: MAIL_YAHOO or SERVERMAIL_YAHOO.

Description

This description appears in the Mail Account Server drop-down list box on the Add a Personal Email Account page. For example: Yahoo Mail Server or Yahoo Mail URL.

URL

Enter the URL associated with the URL identifier.

Comments

You may optionally enter comments. For example, you may enter your name and the date on which the URL was enabled for the Email pagelet.

See Also

Email Pagelet

mailbox	User's mailbox name.
exchsvr	The Microsoft Exchange server name.
numrows	Number of rows.

Method	GET
SSL	No, if SSL is not enabled. Otherwise, set to Yes.
MerchantURL	Enter http://<Outlook Web Access name>/aspfolder

URL Identifier	Enter a URL identifier. The URL identifier indicates whether the URL points to a web address or to a POP3 mail server that cannot be accessed through the web. For a web URL, the URL ID must start with MAIL_. For a POP3 mail server, the URL ID must start with SERVERMAIL_. Whatever follows the MAIL_ or SERVERMAIL_ prefix must be unique for each MAIL or SERVERMAIL ID. For example: MAIL_YAHOO or SERVERMAIL_YAHOO.
Description	This description appears in the Mail Account Server drop-down list box on the Add a Personal Email Account page. For example: Yahoo Mail Server or Yahoo Mail URL.
URL	Enter the URL associated with the URL identifier.
Comments	You may optionally enter comments. For example, you may enter your name and the date on which the URL was enabled for the Email pagelet.