|
Configuration of O365MailRecverTest
The O365 Mail Receiver test periodically emulates a user on Exchange Online receiving an email that is uniquely tagged.
This unique tag is configured against the MAIL TAG parameter of the test, and is displayed as the descriptor of the test. Using the metrics reported by this test, administrators can find quick and accurate answers to the following performance queries related to the mail receiving operation of Exchange Online:
- Did authentication to the email service fail?
- Was any latency noticed when connecting to the email service?
- Is the receiver's mailbox accessible? Was it able to receive the emulated email successfully? If not, what could have caused the failure?
- Is email reception slow? If so, what could be slowing down email reception - is it because of a delay in connecting to the email service? or is it because Exchange Online is processing incoming email traffic slowly?
The default parameters associated with this test are as follows:
Specify a unique MAIL TAG in the MAIL TAG text box using which you want to tag the emulated email. This enables eG Enterprise to keep track of the simulated email. To be able to simulate the email activity end-to-end - i.e., from transmission to reception - you should configure both the O365MailRecverTest and the O365MailSenderTest tests with the same MAIL TAG.
Next, proceed to indicate which mailbox on Exchange Online should receive the emulated email. For this, configure the email ID of the O365 MAIL RECEIVER in the O365 RECEIVER text box. Make sure that you specify the same O365 MAIL RECEIVER for both the O365MailSenderTest and O365MailRecverTest tests.
The test should be able to access the receiver's mailbox, so it can check whether/not mails with the MAIL TAG have been received by it. To facilitate this check, specify the password of that mailbox in the O365 RECEIVER PASSWORD text box.
Confirm the password by retyping it in the CONFIRM PASSWORD text box.
As mentioned already, the test uses the Exchange Online email service to perform the simulation. In order to enable the test to connect to this service, type the WEBSERVICE URL of that service in the WEBSERVICE URL text box.
By default, the TIMEOUT parameter of the test is set to 30 seconds. This means that, by default, the test will wait for a maximum of 30 seconds to connect to the Exchange Online email service - i.e., to the configured WEBSERVICE URL. If the test is unable to connect to the email service even after the default period lapses, the test will automatically timeout. You can increase or decrease the timeout value, if you so need.
The DD FREQUENCY parameter refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY .
To make diagnosis more efficient and accurate, the eG suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.
The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.
Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.
When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.
|