Email event adaptor adapter is an internal event adaptor adaper that comes with WSO2 CEP by default.
Table of Contents |
---|
Before configuration begins,products by default. It can be configured with XML, text, and JSON input mapping types.
Excerpt | ||||
---|---|---|---|---|
| ||||
NOTE TO WRITERS: Add the TOC here.
|
Prerequisites
Follow the steps below to complete the prerequisites before starting the input adapter configurations.
- Enable the mail transport receiver in axis2 Axis2 level by uncommenting the following line in
<PRODUCT_HOME>/repository/conf/axi2/axis2.xml
file:
<transportReceiver name="mailto" class="org.apache.axis2.transport.mail.MailTransportListener"/> - Remove any rich text formatting from the email body. It must contain only plain text.
Configuring
...
input email event adapter
You can configure the email input event adapter using the management console or using an XML file as explained in step 5a configuration file.
Anchor | ||||
---|---|---|---|---|
|
Follow the instructions below to configure input email event adapter using the management console. This deploys the event adapter in the <PRODUCT_HOME>
/
repository/
deployment/
server/
inputeventadaptors/
directory.
- Log in to the CEP product's management console, go to Configure --> and click Configure.
- Click Input Event Adaptors in the Event Processor Configs --> Input Event Adaptors and click menu, and then click Add Input Event Adaptor. Then select 'email' as the Event Adaptor Type.
Enter
thedetails as shown in the
form that appears to create an input adaptor and click Add Event Adaptor. For example,
Fieldsbelow example.
screen
Properties of the aboveconfiguration are described below
:.
:Property Description Event Adaptor Name Name of the input event adapter Event Adaptor Type Type of the input event adapter Receiving Mail Address CEPMail address, where .the product used to retrieve the mails :Receiving Mail Protocol popCan be either imapPOP or imapIMAP (If you select IMAP, make sure it is enabled in your .email account settings) : In whichPoll Interval CEPThe time limit ., in which the product needs to check for new mails (Receiving Mail Protocol Host: pop.gmail.com pop)for (POP, and imap.gmail.com imap)for :IMAP Receiving Mail Protocol Port (995 pop)for (for imap)POP, and 993 Following values are used in the configuration above:
No Format Event Adaptor Name : emailAdaptor Event Adaptor Type : email Receiving Mail Address : wso2cep@gmail.com Receiving Mail Protocol : pop3 Poll Interval(in seconds) : 5 Receiving Mail Protocol Host : pop.gmail.com Receiving Mail Protocol Port : 995 User Name : wso2cep Password : wso2cep Receiving Mail Protocol Port SocketFactory Class : javax.net.ssl.SSLSocketFactory Receiving Mail Protocol Port SocketFactory Fallback : false
- After the adapter is successfully created, you can change its configuration and redeploy it. To do this, click the Edit link associated with it. You can also click the other links associated with it to delete it or enable statistics and tracing.
- An XML editor opens with basic code, allowing you to edit the event adaptor configuration from UI itself, without having to edit the file in the file system. Do your modifications and click Update.
- Alternatively,
Anchor step5 step5 you can specify an event adaptor configuration using an XML file and save it in<PRODUCT_HOME>/repository/deployment/server/inputeventadaptors
directory, which is the Input event adaptor deployment directory. Since hot deployment is enabled, you can simply add/remove files to deploy/undeploy from the server.
Create the XML file with the following Email input event adaptor configurations. Input event adaptor implementation must start with<inputEventAdaptor>
for IMAP User Name Username of the email account Password Username of the email account Receiving Mail Protocol Port SocketFactory Class Class of the receiving mail protocol port Receiving Mail Protocol SocketFactory FallBack To enable or disable fallback of the receiving mail protocol class - Click Add Event Adaptor.
Anchor | ||||
---|---|---|---|---|
|
Follow the instructions below to configure input email event adapter using a configuration file.
...
Create an XML file with the following input email event adapter configurations. Input event adaptor implementation must start with
<inputEventAdaptor>
as the root element.Code Block language html/xml <inputEventAdaptor name="emailAdaptor" type="email" xmlns="http://wso2.org/carbon/eventadaptormanager"> <property name="mail.protocol.socketFactory.fallback">false</property> <property name="transport.mail.Address">wso2cep@gmail.com</property> <property name="mail.protocol.password">mailpassword</property> <property name="mail.protocol.host">pop.gmail.com</property> <property name="mail.protocol.port">995</property> <property name="mail.protocol.user">wso2cep</property> <property name="transport.PollInterval">5</property> <property name="transport.mail.Protocol">pop3</property> <property name="mail.protocol.socketFactory.class">javax.net.ssl.SSLSocketFactory</property> </inputEventAdaptor>
...
Add the XML file to the
<PRODUCT_HOME>/repository/deployment/server/inputeventadaptors/
directory. Since hot deployment is enabled, you can simply add/remove files to deploy/undeploy to/from the server.
Info |
---|
After an adapter is successfully added, it gets added to the list of adapters displayed under Event Processor Configs in the Configure menu of the product's management console. Click Edit to change its configuration and redeploy it. This opens an XML-based editor allowing you to edit the event adapter configurations from the UI. Do your modifications and click Update. You can also delete it, enable/disable statistics or enable/disable tracing on it using the provided options in the UI. |
Info |
---|
If there is any exception occurred continuously when sending mail, Please check whether |
Configuring
...
input email event adapter message properties
Propert | Description |
---|---|
Email Service Name |
...
For an |
...
email to be processed through this event builder, the subject must |
...
be SOAPAction:urn:{Email Service Name} |
...
. |
Input Mapping Type |
...
The incoming event type to be mapped |
...
. |