|
How to: |
This section describes how to verify an Omni-Patient application by:
To verify that the Omni-Patient Server is active:
http://hostname:9999/ism
where:
Is the location where Omni-Patient was installed.
The iSM Administration Console opens, as shown in the following image.



Note: The initial start of Omni-Patient loads Omni Codes before becoming active, which may take several minutes.

To verify that the MDC Cleansing Server is active:
http://hostname:9502
where:
Is the server where Omni-Patient was installed.
The Server Health Status appears on the right pane of the iWay DQS Web Console, as shown in the following image.

http://hostname:9504
The DQS Matching Administration Console opens, showing the Server Health Status, as shown in the following image.

The Server Health Status page provides information on the successful connection to the Omni-Patient database.
http://hostname:9506
The DQS Merging Administration Console opens, showing the Server Health Status, as shown in the following image.

The following steps will verify the Omni-Patient application by copying a sample patient XML document to the File listener for Omni-Patient.
D:\OmniGenServer\samples\patient
[iway_home]\IDS\patient\in