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 \<jms queue name="graphmailqueue" entries="queue/graphmailqueue java\ jboss/exported/jms/queue/queue/graphmailqueue"/> \<jms queue name="readgraphmailqueue" entries="queue/readgraphmailqueue java\ jboss/exported/jms/queue/queue/readgraphmailqueue"/> 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 \<property name="jms readgraphmailqueue list" value="readgraphmailqueue"/> 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 version '2 2' services citsolr container name citsolr image registry cloud4biz com/templates/solr\ latest command solr create c base conhecimento d base conhecimento configs cittika container name cittika image registry cloud4biz com/templates/tika\ latest command tika sh ports 9998 9998 graphmail image registry cloud4biz com/templates/graphmail 1 1 2 container name graphmail restart on failure depends on "citsmart" volumes /storage/my4biz/attachments\ /opt/attachments/ /storage/my4biz/config properties\ /opt/graphmail/config properties citsmart container name citsmart image registry cloud4biz com/templates/itsmops 2 2 9 links citsolr cittika environment xms=9600 xmx=9600 min pool size=10 max pool size=600 statistics enable=true blocking timeout millis=60000 idle timeout minutes=2 gc client interval=1800000 gc server interval=1800000 parallelgcthreads=4 admin user=seuuser admin pass=qsplwso497665kderfij db citsmart=db seubanco jb confi xml=standalone full ha xml time zoneamerica/fortaleza db host=10 10 10 20 db user=seuuser db password=qsplwso497665kderfij db port=5432 citsmart url=10 10 10 30 graphmail read=readgraphmailqueue solr url=citsolr enable ssl=yes valid ssl=yes cert key file=seucertificado jks cert file=seucertificado com crt cert password=789321456 cert alias=seualias timeout deploy=60000 evm enable=false inv enable=false mongodb host= #citmongo mongodb port= #27017 mongodb user= #admin mongodb password= #admin esper threads=4 citsmart protocol=http citsmart login=consultor citsmart password=p\@ssw0rd citsmartinv id=citsmartinventory citsmartevm id=citsmartevm citsmart http port=8080 enable neuro=yes \#### ivm and evm parameters start monitora incidentes=false jdbc alias reports= jdbc alias bpm= jdbc alias bpm eventos= start verifica eventos=false quantidade backuplogdados=1000 start mode rules=false start mode itsm=false iniciar processamentos batch=true dbquartz=standalone \##### deploys citsmart app=helium 2 3 3 war citneuro app=citsmart neuro builder 1 3 7 7 war citprofile app= citsmartevm app= citsmartinv app= citaudit app= evm inv only=no # if evm inv only=yes you need to set full stack=yes full stack=yes log level=info db system=postgres itsm flavor=citsmart ports 8080 8080 443 8443 9990 9990 volumes /storage/my4biz/deploys\ /opt/deploys /storage/my4biz/citsmart /opt/citsmart /storage/my4biz/certs\ /opt/wildfly/certs /storage/my4biz/log /opt/wildfly/standalone/log /storage/my4biz/mp4 /opt/wildfly/mp4 /storage/my4biz/assets\ /opt/wildfly/assets /storage/my4biz/attachments\ /opt/attachments/ config file 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 = graph password = qsplwsok graph mail folders list = inbox 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