Platform Administration
...
Automation
Graph Mail
Graph Mail Project
3min
The following properties must be set in the config.properties file of the Graph Mail Project, according to the client scenario:
JMS_CONNECTION_FACTORY_JNDI = jms/RemoteConnectionFactory
JMS_WILDFLY_REMOTING_URL = http-remoting://172.18.0.4:8080
JMS_QUEUE_JNDI = jms/queue/queue/graphMailQueue
JMS_READ_MAIL_QUEUE_JNDI = jms/queue/queue/readGraphMailQueue
JMS_USERNAME = jmsuser
JMS_PASSWORD = 352TEDDWtHpfRObR166VOuOBI1F4
GRAPH_APP_ID = 51255c25-165446-25d5sd5d5-dssdsd
GRAPH_USERNAME = [email protected]
GRAPH_PASSWORD = QsPlWSOK
GRAPH_MAIL_FOLDERS_LIST = Inbox
The correct file localization in the docker-compose.yml file from the Graph Mail Project must be set. Also, set the defined folders for image and attachment sharing.
The Graph Mail Project depends on the Service Management project, so it should only be executed when the Service Management one is running.
Functioning
- A Thread or Job:
- Obtains the e-mail messages occasionally and extracts the: sender, subject, body, and attachments from the parameterized list of folders;
- Registers messages received in a specific queue for registration of tickets in WildFly, containing the name of the folder, the queue, and the content of the email, including the list of attachments;
- Etches the attachments to a mapped folder on a volume that SM is able to access;
- Performs the "Email control procedure":
- Processing control: the system reads a predefined folder, allowing the user to create filtering rules, specific to the ticket registration. It can be an incident, problem, change or release ticket: what determines it is the automatic action registration;
- Destination of the processed message: the system marks the already processed message as read.
- Mailbox sharing:
- It can be used by the user and the system - if the folder for reading is implemented;
- It will also be used for sending e-mails.
Did this page help you?