Development Guidelines

this implementation does not substitute the previous pop3 , s m t , and ima p integration for other e mail services it can also be parametrized for being utilized simultaneously with those integrations configuration the following steps must be accomplished in their presented order infrastructure azure parametrization inside microsoft azure create or choose an e mail to be utilized by the system in these integrations; it is not necessary to be a specific e mail account however, the user must be aware that the e mail readout and dispatch can modify and pollute the mail inbox; so the user must create rules and folders for messages clearing and organization, so the work of one does not interfere with another create or choose an application from this e mail account, in azure active directory it will be used for e mail readout and dispatch set the following permissions set the application access to the email account that will be used allow the public client flow for the application app id save this id for future configuration folders for e mail readout if the user wishes to define filtering folders and rules for the mail inbox readout, they must be created at this point in the first graph mail project version, the sweep for identifying the folders is only realized as it launches service management wildfly 1 1 2 activemq user set a user to have access to the activemq queues by executing the following command and parametrizing a secure password for the option " p", according to your environment sh add user sh a u jmsuser p 1 g guest activemq queues the e mail readout and dispatch queues must be set in the wildfly configuration file, the standalone xml file, for example add the tags with the names of the queues inside the main tag \<subsystem xmlns="urn\ jboss\ domain\ messaging activemq 3 0"> example system properties for the service management project to upload the listeners, who will listen to the e mail readout queues, it is necessary to set the following property in the tag \<system properties> of standalone xml it is possible to name a queue multiple times to be heard, only by separating with a coma file sharing folder for sharing images and file attachments a folder must be created and the writing and readout permissions must be set on the application server, for the volume mapping of the docker containers, which will upload the applications thus it will allow the sharing of files between them this folder will be used for the compose files and in parameter 479 graph mail parametrization docker 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 config file the following properties must be set in the config properties file of the graph mail project, according to the client scenario dependency 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 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