Testing your object definitions for problems

When you define objects in WebSphere® MQ Explorer, certain properties of the objects are mandatory and you cannot create the objects without defining those properties. However, there are several properties that are not mandatory but which you should define so that your WebSphere MQ configuration works, so that the configuration is easier to maintain, or for audit purposes.

The WebSphere MQ Explorer tests check your object definitions for errors and potential problems. Each area of WebSphere MQ that can be checked is defined as a discrete test; for example, there is a test to check that you have defined matching channel pairs, a test to check that you do not have more than one TCP listener trying to listen on the same port, and a test to check that multiple queue managers on the same system are not using the same or similar names. The problems found by the core tests do not always indicate a serious error and sometimes just indicate where there is potential for confusion and mistakes when administering the objects; for example, two queue managers on the same system with similar names could cause problems.

A set of tests is supplied to check the main WebSphere MQ object definitions (for example, queues and channels); for the complete list of WebSphere MQ tests, see WebSphere MQ tests. There are also other tests available that are supplied with other parts of WebSphere MQ Explorer, such as JMS administered objects.

Test results are displayed in the Test Results view, as shown in the following figure, which opens the first time that you run the tests.

You can extend the supplied set of tests to include your own custom tests so that WebSphere MQ Explorer can provide feedback that is directly relevant to how you use WebSphere MQ. For instructions and sample custom tests, see Adding new tests.