7 Testing
For testing (and to initialize the system) you should first make sure that the DBMS server with the EMM database is already up and running. After that, start and stop the available services on all EMM servers (do not forget mailer service on frontend and redirect servers) and check the logs in /home/<user>/var/log/ for problems. The scripts create missing directories, too.
Please maintain the test sequence below for starting and the reverse order for stopping:
| Service | Run as User | Commands |
|---|---|---|
| mailloop service | mailloop | /home/mailloop/bin/mailloop.sh start /home/mailloop/bin/mailloop.sh stop |
| mailer service | mailout | /home/mailout/bin/mailer.sh start /home/mailout/bin/mailer.sh stop |
| merger service | merger | /home/merger/bin/merger.sh start /home/merger/bin/merger.sh stop |
| GUI service | console | /home/console/bin/sanity.sh console |
| GUI service | console | /home/console/bin/emm.sh start /home/console/bin/emm.sh stop |
| redirect service | rdir | /home/rdir/bin/sanity.sh rdir |
| redirect service | rdir | /home/rdir/bin/emm.sh start /home/rdir/bin/emm.sh stop |
It is especially important to start the mailloop service before the merger service!
The GUI service also starts the statistics service and the (optional) webservices. Please note: Most statistics of EMM are generated by the statistics service. For communication between the GUI of EMM (GUI service) and the statistics service, EMM users must enable cookies in the web browser which is used to access EMM. Otherwise, the GUI can not display the results provided by the statistics service.
Scripts sanity.sh for the GUI and redirect service have to be started only once after the installation of EMM. For later starts and stops of these selected services the scripts are no longer needed.
If you try to start or stop a service as user root, the script tries to change to the appropriate user with command su.
As soon as EMM is in production mode, we recommend to use global script /root/bin/agnitas.sh to start and stop EMM, like it is described in the following chapter EMM Start/Stop. Option status shows the current status of all EMM services installed on the server.
To test the correct operation of each service we recommend
- creating a new mailing (testing GUI service)
- sending the mailing to an existing email address (testing merger and mailer service)
- and sending it to an non-existing email address (testing mailloop service)*
- opening the mail and clicking the links (testing redirect service)
- checking in mailing statistics if openings and clicks were recorded (testing redirect service and statistics service)
*To test the bounce management you have to send the mailing not to admin or test recipients, but to normal recipients, because due to performance reasons mailings to admin and test recipients are sent out directly without using a mailer service. For that reason the bounce management process can not be applied to mailings for admin and test recipients.