Exchange Connector Guide

You must accept the FirstClass License Agreement before you can use this product. If you do not accept the terms of the License Agreement, do not install the software and return the entire package within 30 days to the place from which you obtained it for a full refund. No refunds will be given for returned products that have missing components.

Information in this document is subject to change without notice. Certain features and products described in this document may not be currently available in all geographic regions. Distribution or reproduction of this document in whole or in part must be in accordance with the terms of the License Agreement.

All rights reserved. FirstClass is a registered trademark of a Centrinity Inc. subsidiary used under license. Centrinity, the Centrinity logo, and the FirstClass logo are trademarks of Centrinity Inc. All other trademarks are property of their respective owners.

This edition applies to Release 7.0 of FirstClass and to all subsequent releases and modifications until otherwise indicated in new editions. This document is bound by international copyright law and the FirstClass Software License Agreement and Limited Warranty included with every FirstClass product.

Technical support

Telephone technical support is available to registered administrators at the following numbers:

Toll free in North America: 1-800-346-9108

Toronto: 905-762-7060

International: +353-61-725-200.

Online support questions may be directed to support@centrinity.com.

Introduction

The FirstClass® Connector for Microsoft® Exchange Server (FirstClass Connector) is a transport mechanism for real-time communication between FirstClass Server (minimum version 6.2) and Microsoft® Exchange Server 5.5. It translates messages and user information into a readable format as they are transported to another server, and maintains Directory synchronization between the two servers.

Because the information transfer is performed in real time, the need for intermediate storage is eliminated. The connection to Microsoft Exchange Server is implemented using MAPI for mail and calendaring, and using ADSI for Directory synchronization. The connection to FirstClass is implemented using FCP/Internet Client for mail and calendaring, and using FirstClass batch administration for Directory synchronization.

Who should read this book

This book is intended for the FirstClass Server and Microsoft Exchange Server administrator(s) who will install and run this application.

What you will find in this book

This book describes how to install and use the FirstClass Connector. It also lists the installation requirements and discusses the current features and considerations about this application.

This book does not document how to use FirstClass or Microsoft Exchange Server features. For that information, see our online help and applicable product documentation.

What you should already know

This book is intended for administrators who want to establish a mail flow between their Micorosft Exchange Server and FirstClass Server systems. We assume you are familiar with your Windows® operating system, Microsoft Exchange Server, MS-DOS®, and FirstClass functionality.

Requirements

The FirstClass Connector runs on the same computer as Microsoft Exchange Server 5.5. This server machine must meet the following minimum requirements:

• Windows NT® Server 4.0 (SP6)

• minimum 128 MB RAM

• minimum 10 MB free HDD space

• connection to a LAN.

FirstClass Connector features and considerations

Mail features

• Basic mail transport (includes message body, subject, recipient list, copylist, subject, time sent, priority, and sensitivity).

• Mail transport containing one or more attachments.

• Mail transport containing embedded messages (from Microsoft Exchange Server to FirstClass).

All embedded messages are serialized into a flat list of attachments.

• Transfer of Microsoft® Outlook® Contacts as mail messages where the Contact body is an attachment.

• Transfer of Microsoft Outlook Notes as mail messages where the Note body is an attachment.

• Mail delivery confirmation report upon request.

• Mail read confirmation report upon request.

• Automatic mail nondelivery report.

Mail considerations

• Microsoft Exchange Server embedded or attached OLE objects in mail messages (such as signatures, Excel spreadsheets, and database tables) will not be delivered to FirstClass.

• Microsoft Outlook tasks are delivered to FirstClass (with all task information) as a mail message, not a FirstClass task.

• With the exception of the calendar form, all FirstClass forms will be delivered to Microsoft Exchange Server as mail messages. However, nonstandard form fields are omitted from the delivered mail message.

Calendar features

• Single meeting requests are transported with all their attributes (message body, subject, participants, subject, time sent, start/end date and time, reminder, sensitivity, time display pattern, location, one or more attachments).

• Microsoft Exchange Server meeting requests delivered to FirstClass are inserted directly into participants’ calendars.

• FirstClass meeting requests delivered to Microsoft Exchange Server are delivered into the participants’ Inboxes as meeting requests.

• Meeting RSVP is supported in both directions for Accepted and Declined.

• The Canceled option from Microsoft Exchange Server is supported; it appears in FirstClass as a Meeting Canceled mail item.

• Automatic meeting request nondelivery reports are sent when the meeting requests cannot be delivered.

• Recurring meetings are fully supported for the following recurring patterns only:

• daily

• weekly

• weekdays

• weekends

• monthly (same day)

• monthly (same weekday)

• annually (same date).

• Time zones are automatically adjusted for FirstClass Server and Microsoft Exchange Server.

Calendar considerations

Although recurring patterns are supported, note:

• scheduling a "weekends" recurring pattern from FirstClass to Microsoft Exchange Server will not insert the first occurrence into the series if it occurs on a weekday.

• scheduling a "weekdays" recurring pattern from FirstClass to Microsoft Exchange Server will not insert the first occurrence into the series if it occurs on a weekend.

Directory synchronization features

• Upon startup, the FirstClass Connector synchronizes all mailboxes from Microsoft Exchange Server into FirstClass as Remote Names, and all Remote and Regular Users in FirstClass are synchronized into the Microsoft Exchange Server directory as Custom Recipients.

• Full synchronization can be scheduled, performed automatically whenever a change occurs (incrementally), or performed manually. Incremental synchronization occurs whenever an addition, modification or deletion has been made in the FirstClass Directory or the Microsoft Exchange Server directory.

Note

The FirstClass Connector takes approximately one minute to check for changes to the Microsoft Exchange Server directory, so there might be a slight delay to see the changes reflected in the FirstClass Directory.

• A Microsoft Exchange Server mailbox’s First Name, Last Name, Initials and SMTP email address are mapped to a corresponding FirstClass Remote Name’s First Name, Last Name, Initials and Mail Aliases. The Mail Alias format is <SMTP:smtp email address>.

• A Regular or Remote FirstClass User’s First Name, Last Name and Initials are correspondingly mapped to a Microsoft Exchange Server Custom Recipient's First Name, Last Name and Initials. The FirstClass Client ID is combined with the FirstClass Site Name to create an Alias for the Custom Recipient (clientId_SiteName). The FirstClass email address of the Custom Recipient has the following format: FC:Display Name,SiteName_clientId.

• FirstClass downstream server directories can be selectively synchronized (see SORC_SYNC_SITE_NAME_XX configuration parameter).

Directory synchronization considerations

• Microsoft Exchange Server distribution lists, public folders and Custom Recipients are not synchronized.

• FirstClass Remote Names, conferences and mail lists are not synchronized.

• Supplemental attributes are not synchronized at this time (for example, addresses, phone numbers).

Note

To run the FirstClass Connector directory synchronization, the host machine must have Microsoft Active Directory Services installed. If it is not installed run ADS.EXE to install it. This file can be found in the directory where you installed the FirstClass Connector application.

Configuring and installing the FirstClass Connector

Step 1: Create the Windows NT account for the FirstClass Connector

Create a Windows NT account that will be used by the FirstClass Connector. This account will be used:

• to create the Microsoft Exchange Server connector profile service for the connector logon profile

• as a logon account for the FirstClass Connector running as a Windows NT service

• as a Windows NT account with administrative rights to Microsoft Exchange Server objects.

Using the Windows NT User Manager for Domains:

1 Create a Windows NT account with an arbitrary name and password.

2 Assign the following Windows NT rights and permissions to the newly created account:

• Windows NT Logon as Service rights to the hosting server

• Windows NT Administrative rights to the hosting server.

Note

Further rights and permissions for this account will be assigned in Step 6.

Step 2: Create the "ExchangeConnector" object on FirstClass Server

You must install the ExchangeConnector object and create the Enterprise Services folder with the connector monitor on FirstClass Server. The created Enterprise Services folder will contain the connector monitor.

This ExchangeConnector object is the connection point for the FirstClass Connector on FirstClass Server. The values defined in this step will be required again in Step 9.

Create the ExchangeConnector object, Enterprise Services folder and the connector monitor

1 Log into FirstClass Server as the administrator.

2 optional

Edit the connector object creation script file exchange.ags.

Note

This is recommended only for expert installations where customization is required. Normally, the following default values in the exchange.ags file are sufficient:

connector name

ExchangeConnector

connector node id

500000000

connector user id

500000000

3 Submit the connector creation script to Batch Admin for processing.

The connector creation script is supplied in the file <connector name>.ags.

4 Verify that the Gateways folder contains the newly created ExchangeConnector object.

Configure the ExchangeConnector object

1 Open the Gateways folder.

2 Select the newly created connector object.

3 Open the Connection tab and set the connector object password. Make note of this password.

4 Open the Network tab and set the Server IP address.

5 Set Zone/Port to 510 on the Network tab.

6 Open the Multisite (Outbound) tab and select Export Directory names.

7 Select Directory and enter the connector object password again.

8 Close the Gateways folder.

Configure the connector monitor in the Enterprise Services folder

1 Select File > Upload from the FirstClass Server administrator's Desktop.

2 Navigate to the installation directory and select the file "monitorform.fc".

After uploading the monitorform.fc file:

3 Double-click on the form file object that has been placed on the Desktop.

4 Select Update on the Resource Updater form that opens.

5 Open the Enterprise Services folder.

6 Open the Connector Monitor object.

7 Confirm the form is actually the monitor form and not a default mail form.

Step 3: Create the FirstClass connector object on Microsoft Exchange Server

This object is the connection point for the FirstClass Connector on Microsoft Exchange Server.

Run the Connector.exe utility from the command prompt with the following parameters:

Connector <ADD|REMOVE> "<server>" "<site DN>" "<account>"

ADD

Add (new) connector object

REMOVE

Remove (delete existing) connector object

server

Name of machine running Microsoft Exchange Server

site DN

Exchange Server site distinguished name as: "/o=<organization name>/ou=<site name>"

account

NT account with administrative rights to the connector object as: "<domain name>\<NT account name>"

For the ADD command only, the FirstClass Connector will be installed with the following default values:

Connector display name

FirstClass Connector

Connector store name

FirstClass Connector

Connector traffic type

Step 4: Create the connector profile service for Microsoft Exchange Server

This service is created on the machine running Microsoft Exchange Server. It is required by the Windows NT mail logon profile, which enables the FirstClass Connector to log (connect) into the FirstClass connector object on Microsoft Exchange Server.

Use the following parameters to run the Service.exe utility from the command prompt on the machine running Microsoft Exchange Server:

Service <ADD|REMOVE> <server> <site DN> <account> <password> <path>

ADD

Add (new) FirstClass Connector profile service

REMOVE

Remove (delete existing) FirstClass Connector profile service

server

Name of Microsoft Exchange Server

site DN

Microsoft Exchange Server site distinguished name as: "/o=<organization name>/ou=<site name>"

account

Windows NT account with administrative rights to the connector object as: <domain name>\<Windows NT account name>

password

password of the Windows NT account with administrative rights to the Microsoft Exchange Server connector object

path

FirstClass EXE path only (\escon.exe is appended by default)

For the ADD command, the service display name will be installed with the default value: FC Connector Profile Service.

Step 5: Create the FirstClass Connector logon profile for Microsoft Exchange Server

This profile is created on the machine running Microsoft Exchange Server. It is used by the FirstClass Connector to log (connect) into the FirstClass connector object on Microsoft Exchange Server.

Use the following parameters to run the Profile.exe utility from the command prompt on the machine running Microsoft Exchange Server:

Profile "<profile name>" <ADD|REMOVE> [<service name>]

profile name

Name of profile to ADD/REMOVE

ADD

Add (new) specified profile

REMOVE

Remove (delete existing) specified profile

service name

Applies to ADD only: Name of associated service; defaults to "FC Connector Profile Service"

Step 6: Assign Microsoft Exchange Server permissions to the Windows NT account

You must assign additional Microsoft Exchange Server rights and permissions to the Windows NT account created in Step 1.

1 Start the Microsoft Exchange Server Administrator utility.

2 Choose Tools > Options and select the Permissions tab.

3 Select both "Display rights for roles on Permission page" and "Show Permission page for all objects".

4 Click Apply.

5 Open the Permissions page.

6 Add the account created in Step 1, with Service Account Admin rights to the following Microsoft Exchange Server objects:

• Organization

• All sites

• FirstClass connector object under the Connections container.

Step 7: Customize the configuration file

The configuration file, ESCON.CFG, defines the required parameters for FirstClass Connector operation. This file must be located in the same directory as the ESCON.EXE file unless the FirstClass Connector is registered to run as a Windows NT service. If this is the case, the ESCON.CFG file must be located in the \\WINNT\system32\ directory.

Understanding channels

The server is configured into channels. A channel is a unidirectional stream of information. Hence, each channel has a source and a destination. A bidirectional connector would therefore have two channels, one in each direction. Each channel runs as a separate processing task (thread). However, all channels use the same connection to source and destination nodes.

Consequently, there is a section of configuration parameters for each channel in the ESCON.CFG file, and each channel consists of two sections defining the source node parameters and destination node parameters.

General format and syntax

The configuration file (ESCON.CFG) is an ASCII text file with the following general format and syntax:

[Common]

<Parameter keyword>=<Parameter value>CRLF

[Channel XX]

<Prefix><Parameter keyword>=<Parameter value>CRLF

where :

• [Common] is a common parameters heading

• XX is a two digit channel number starting with 01

• [Channel XX] is a channel XX heading

• Prefix can be SORC_ or DEST_ or CHANNEL_

• DEST indicates channel destination node parameter

• SORC indicates channel source node parameter

• CHANNEL indicates a channel common parameter.

Guidelines

• Parameter keywords cannot contain blank spaces or an equal sign.

• Parameter values can contain any character and must be terminated with a carriage-return/line-feed sequence.

• Parameter line must not contain any other text other than the keyword and its value.

• Parameter lines may appear in any order in the file as long as they are within their applicable heading.

• Comments must be placed on separate lines. A comment is any text that does not adhere to the above syntax.

Common configuration parameters

Common parameters do not have a prefix. Common parameters that can be defined in the configuration file are:

NUMBER_OF_CHANNELS=2

Total number of channels to be configured

LOG_LEVEL=NORMAL

How to process log information:

QUIET: do not log information

BASIC: log errors only

NORMAL: log warnings and errors (default)

DETAILED: log information, warnings and errors

DEBUG: record all logs

Channel Parameters

Below is a list of parameters and identifiers that may appear in a configuration file, with explanations. Within a configuration file, these parameters are repeated for each channel that exists.

--------Channel 01 MSX to FC--------

Comment

CHANNEL_01_TYPE=DIR-SYNC

Channel source information:

CONNECTOR: messaging transport channel

DIR-SYNC: directory synchronization channel

NODE_NAME=FirstClass Connector

Microsoft Exchange Server: connector name on Microsoft Exchange Server

FirstClass: connector name on FirstClass Server

LOGIN_ID=FirstClassConnectorProfile

Microsoft Exchange Server: FirstClass Connector logon profile name

FirstClass: connector user id

LOGIN_PASSWORD=

Microsoft Exchange Server: profile password (if any)

FirstClass: connector user id password on FirstClass Server

AUX_CONFIG_FILE=connector.fc

Microsoft Exchange Server: N/A

FirstClass: optional client fc file used for login

CONNECT_ADDRESS=192.168.20.77

Microsoft Exchange Server: N/A

FirstClass: IP address or name of FirstClass Server

CONNECT_PORT=500

Microsoft Exchange Server: N/A

FirstClass: if present will override default port number 510

CONNECTOR_OUTBOUND_FOLDER=FirstClass Connector (SERVER1)\MTS-OUT

Microsoft Exchange Server: set to "connector name (server name)\MTS-OUT"

FirstClass: not used - defaults to Mailbox

CONNECTOR_INBOUND_FOLDER=FirstClass Connector (SERVER1)\MTS-IN

Microsoft Exchange Server: set to "connector name (server name)\MTS-IN"

FirstClass: not used - defaults to Desktop

ADDRESS_TYPE=SMTP

Microsoft Exchange Server: set to SMTP

FirstClass: set to FC

AB_VIEW=GLOBAL

Microsoft Exchange Server:

GLOBAL: LDAP path points to the Microsoft Exchange Server Global Address List (GAL)

NON-GLOBAL: LDAP path points to the Microsoft Exchange Server site or local address book

FirstClass: N/A

ADDRESS_BOOK_01=ldap://SERVER1/cn=recipients,ou=ORGANIZATION1,o=SITE1

Microsoft Exchange Server: LDAP path to the desired address book container

If AB_VIEW=NON-GLOBAL then the LDAP path points to a specific address book container. Additional containers can be specified as:

ADDRESS_BOOK_02=ldap://SERVER2/cn=recipients/cn=sales/ou=ORGANIZATION1,o=SITE1

ADDRESS_BOOK_03=ldap://SERVER5/cn=recipients,ou=ORGANIZATION1,o=SITE2

ADDRESS_BOOK_04=ldap://SERVER6/cn=recipients,ou=ORGANIZATION1,o=SITE3

where containers can be located on different servers and/or different sites.

FirstClass: not used - defaults to _FC_DirSync for SORC_ and to DeskTop for DEST_

INSTANCE_ID=0

Connector channel set identifier.

A set of connector and channel sources and dirsync channel sources and destinations with the same instance ID that share common Microsoft Exchange Server and FirstClass Server connection points.

Default is zero. Any set of channels with an instance of 1 or greater would connect to an entirely different Microsoft Exchange Server connection point and/or FirstClass Server connection point. This enables the FirstClass Connector to service multiple, unconnected Microsoft Exchange Server installations and/or multiple FirstClass Server installations.

Step 8: Configure the connection to Microsoft Exchange Server

Note

These steps must be repeated for each channel in the ESCON.CFG file.

Microsoft Exchange Server parameters that need to be known are listed below with sample values.

Configuration parameter: FirstClass Connector name

Sample: FirstClass Connector

Configuration parameter: Microsoft Exchange Server organization name

Sample: ORGANIZATION1

Configuration parameter: Microsoft Exchange Server site name

Sample: SITE1

Configuration parameter: Microsoft Exchange Server name

Sample: SERVER1

Configuration parameter: Microsoft Exchange Server connector logon profile name

Sample: FirstClassConnectorProfile

Configuration parameter: Microsoft Exchange Server Address Book LDAP path

Sample: ldap://MSXServer/cn=recipients,ou=ORGANIZATION1,o=SITE1

Setting Microsoft Exchange Server as the DIR-SYNC source

SORC_NODE_NAME=FirstClass Connector

SORC_LOGIN_ID=FirstClassConnectorProfile

SORC_ADDRESS_TYPE=SMTP

SORC_ADDRESS_BOOK_00=ldap://SERVER1/cn=recipients,ou=ORGANIZATION1,o=SITE1

SORC_AB_VIEW=GLOBAL

Setting Microsoft Exchange Server as the DIR-SYNC destination

DEST_NODE_NAME=FirstClass Connector

DEST_LOGIN_ID=FirstClassConnectorProfile

DEST_ADDRESS_TYPE=SMTP

DEST_ADDRESS_BOOK_00=ldap://SERVER1/cn=recipients,ou=ORGANIZATION1,o=SITE1

DEST_AB_VIEW=GLOBAL

Setting Microsoft Exchange Server as the CONNECTOR source

SORC_NODE_NAME=FirstClass Connector

SORC_LOGIN_ID=FirstClassConnectorProfile

SORC_CONNECTOR_OUTBOUND_FOLDER=FirstClass Connector (SERVER1)\MTS-OUT

SORC_CONNECTOR_INBOUND_FOLDER=FirstClass Connector (SERVER1)\MTS-IN

SORC_ADDRESS_TYPE=SMTP

Setting Microsoft Exchange Server as the CONNECTOR destination

DEST_NODE_NAME=FirstClass Connector

DEST_LOGIN_ID=FirstClassConnectorProfile

DEST_CONNECTOR_INBOUND_FOLDER=FirstClass Connector (SERVER1)\MTS-IN

DEST_ADDRESS_TYPE=SMTP

Step 9: Configure the connection to FirstClass Server

Note

These steps must be repeated for each channel in the ESCON.CFG file.

The setup is same for either DIR-SYNC or CONNECTOR type channels.

FirstClass Server parameters that need to be known are listed below with sample values.

Configuration parameter: FirstClass Connector name

Sample: ExchangeConnector

Configuration parameter: FirstClass Connector user ID

Sample: 500000000

Configuration parameter: FirstClass Connector object password

Sample: pass

Configuration parameter: FirstClass Server address/name

Sample: TANGO

Setting FirstClass Server as source (DIR-SYNC or CONNECTOR type channel)

SORC_NODE_NAME=ExchangeConnector

SORC_LOGIN_ID=600000000

SORC_LOGIN_PASSWORD=pass

SORC_CONNECT_ADDRESS=TANGO

SORC_ADDRESS_TYPE=FC

Setting FirstClass Server as destination (DIR-SYNC or CONNECTOR type channel)

DEST_NODE_NAME=ExchangeConnector

DEST_LOGIN_ID=500000000

DEST_LOGIN_PASSWORD=pass

DEST_CONNECT_ADDRESS=TANGO

DEST_ADDRESS_TYPE=FC

Step 10: Register the connector

Running as a Windows NT registered server

To register the FirstClass Connector for operation as a Windows NT registered server:

1 Open the command prompt.

2 Navigate to the installation directory.

3 Type

escon /RegServer

4 Start the FirstClass Connector by running escon.exe.

To unregister the server:

1 Open the command prompt..

2 Navigate to the installation directory.

3 Type

escon /UnregServer

Running as a Windows NT service

To register the FirstClass Connector for operation as a Windows NT service:

1 Copy the configuration file (ESCON.CFG) to the \WINNT\System32 directory, since this is the current system directory for all services.

2 Open the command prompt.

3 Navigate to the installation directory.

4 Type

escon /Service

5 Open the Services tab on the Windows Control Panel.

6 Select the service: FirstClass Sync Connector.

7 Click Startup.

8 Select This Account and input the account ID and password created for the connector service in Step 2.

9 Click Start service.

To unregister the connector service:

1 Open the command prompt.

2 Navigate to the installation directory.

3 Type

escon /UnregServer

Starting the connector

To launch the FirstClass Connector, click the FirstClass Connector icon:

When the FirstClass Connector application starts, you will see the FirstClass Connector console screen:

Double-click to enlarge:

This screen displays the current status of the application, synchronization results, and debugging information.

To force a full Directory synchronization from this screen choose Directory > Force Full Sync.

To increase or decrease the amount of information that displays on the console, choose Log Level and highlight one of the listed options: Quiet, Basic, Normal, Verbose, or Debug.

Connector monitor

The purpose of the connector monitor is to display the status of the synchronization.

To view the connector monitor, open the Enterprise Services folder on the FirstClass administrator’s Desktop, and double-click Connector Monitor.

Double-click to enlarge:

This screen indicates the number of active channels, the type of connector, the software version, the last time the FirstClass Connector was started, and displays the current status of any synchronization that is occurring. The Activity field indicates the current processing stage. If the field is blank, as in the above image, this means the FirstClass Connector is idle. The progress bar at the bottom of the screen will always be moving, to indicate the FirstClass Connector is still active.

There are also two buttons on this screen: Reset Monitor, which lets you reset the current values on the screen, and Full Dir-Sync, which forces a Directory synchronization.

Performing Directory synchronization

Warnings

• A Directory synchronization takes time. The amount of time required depends on the speed of your machine and the amount of information to synchronize.

• A synchronization cannot be halted once it has started.

Every time the FirstClass Connector is launched, it automatically performs a full Directory synchronization. To force a Directory synchronization at any time, choose Directory > Force Full Sync from the connector console, or click Full Dir-Sync from the connector monitor.

The console must always be running to maintain synchronization after the initial Dir Sync. When a change is made in FirstClass, Microsoft Exchange Server is updated immediately. This is called incremental synchronization based on notifications from FirstClass. When a change is made in Microsoft Exchange Server, FirstClass is updated within a few minutes, based on a set timeframe (hardcoded number of minutes). This is called incremental synchronization based on polling Microsoft Exchange Server. The is due to the difference in available incremental synchronization mechanisms between Microsoft Exchange Server and FirstClass.

If the information is required immediately, you can force a full Directory synchronization, but see the Warnings above before you do this.

Understanding the log file

The log file ESCON.LOG is located in the same directory as the FirstClass Connector executable. This file is recreated every time the FirstClass Connector is started, and is automatically backed up at midnight by saving the current file as ESCON_YYYY_MM_DD_HH_MM_SS.LOG, where YYYY_MM_DD_HH_MM_SS represents year_month_day_hour_second.

Note

If the FirstClass Connector is abnormally terminated (such as a power outage), you will need to rename, move, or copy the ESCON.LOG file before restarting the application, because the log file will not be automatically renamed from ESCON.LOG.

At startup, the entire configuration is written to the log file. There is a sample log file on your installation CD called SAMPLELOG.TXT.