proxy.config.xml file

The proxy.config.xml file controls the web service and environment configuration, and provides processing directives for using broker function to complete IHE transactions.

When you first open the proxy.config.xml file, you see REPLACE_ME_WITH... entries. Each of these entries must be updated with the specifics of your installation. The examples in this topic show an edited file. The easiest way to handle this edit is to do a search for “REPLACE_ME_WITH”. For example:

<config.file.path>REPLACE_ME_WITH_PATH_TO_BROKER_ROOTDIR/config/IHE/
msgBrokerconfig.file.path>REPLACE_ME_WITH_PATH_TO_BROKER_ROOTDIR/config/
IHE/msgBroker>

Attention: Regardless of the operating system on which you are installing, the proxy.config.xml file accepts only forward slashes (/). For example, if you are installing on a Microsoft Windows platform your home directory path might be D:\MDM_INSTALL_HOME\MDM\MessageBrokerSuite. However, the path must be entered as D:/MDM_INSTALL_HOME/MDM/MessageBrokerSuite in the proxy.config.xml file.

The first section of the file contains some standard broker global configuration environment variables. For example, these variables identify log directories (mad.log-dir=), installation directories (mad.root_dir=), connection information (mad.conn.str=), and so on.

Environment variable use, such as ${MAD_ROOTDIR}, is not supported inside of configuration files running under web services. You must enter the full path.

The second part of the file, the body, is where the actual transactions (services) are defined. There are two types of services: IHE services and generic services.

The IHE handler.config portion of the body contains the name of the service (for example, handler.config serviceName="PIXManager") and the service action (for example, “PRPA_IN201301UV02”). The service name identifies an associated IHE web service (which contains a grouping of IHE actions or profiles). The action name or element is the action (profile) to be performed, followed by the type of broker (for example, broker.inbound or broker.query) that processes the profile. The associated configuration file (for example, MsgReaderSuccessPIX_PDQ.ini) used for the action is also identified. The broker.inbound processes requests to register or record information in the document registry. The broker.query processes service requests for information from the registry.

All supported IHE profiles are automatically listed in the proxy.config.xml file. The profiles defined are PIX Manager and PDQ Supplier. Unless you have a reason to deviate from the IHE standards, you do not have to edit this section.

An optional attribute can be added to the handler.config sections to turn on ATNA logging: atnaLogger="129.6.24.109:8087". (This section is commented out in the actual proxy.config.xml file.)

The parser.handler.lib setting is operating-system-specific. For Microsoft Windows, use a library extension of .dll. Other operating system (OS) libraries have the OS-specific extension and follow the convention set by all of our native libraries. The libraries are named in the /lib folder of the proxy installation directory.

Following the IHE-specific actions, there is a section for generic broker services that is used for custom services and actions. Services can be defined to process the addition of patient records to the MDM database using XML, delimited, fixed-length, or HL7v2 messages. The message type is defined by the <message.type.*> tag (for example, <message.type.xml>).