IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Email > Plan for adapter implementation

Required folders for inbound processing

Several folders are required for activities such as archiving and storage before you run the adapter for inbound processing.


Required folders for inbound communication

Before running the adapter, create one or more poll folders on your mail server and a staging folder where the adapter saves all polled emails as files. These folders are required and neither type are created by the adapter. Also, to use the archiving functionality of the adapter to store successfully processed and failed email events create an archive folder and a failed event folder.

The adapter requires that there be a folder on the local drive that holds emails marked in progress in the event store. This folder is called the staging directory in the external service wizard. Because the adapter does not create a staging directory, create it before you start the external service wizard.


Required folders for archiving

You can configure the adapter to save, or archive copies, of both successful and failed emails by using the ArchiveFolder property. To use this property, create both of the following folders before you run the adapter.

When the ArchiveFolder property is specified, all successfully processed mail is moved into the archive folder from the staging folder.

If you leave this property blank all successfully processed mail is deleted from the staging folder.

If the FailedEventsFolder property is specified, all unsuccessfully processed mail is moved into the failed events folder from the staging folder. If you leave this property blank, all failed mail is deleted from the staging folder.

For more information about either of these folder properties, see the section on activation specification properties in the reference section of this documentation.


Use WebSphere Application Server environment variables

Instead of specifying the folder names when you run the external service wizard, you can use WebSphere Application Server environment variables. Refer more information about environment variables at: WebSphere Application Server environment variables.

Plan for adapter implementation


Previous topic: Security


Next topic: User authentication


Related tasks:

Defining WebSphere Application Server environment variables


Related reference:

Managed connection factory properties

Activation specification properties