Take extra precaution when running multiple HL7 Listeners in production. Make sure your configuration satisfies the following requirements:
-
Only one service should be used for each type of HL7 feed (for example, one for ADT and one for MDM). Do not use multiple HL7 Listeners for a single feed.
Note:An exception to this requirement is if your system is configured to receive SIU messages. SIU messages must be received by the same HL7 Listener as ADT messages in order to prevent the creation of duplicate charts. See -HL7PORT=# for how to configure a listener to listen on multiple ports.
-
If the services are on the same server, each service should be configured to listen on a different port. Use the -HL7PORT=# switch to specify the port for each instance of the HL7 Listener.
See the Configuration module help for more information about configuring multiple OnBase services to run on the same server.
You should not attempt to run more than two OnBase Clients as a Windows service under the built-in Windows accounts, such as the Local System account. Since the built-in accounts use the same session for every service, the workstation can run out of memory if too many services are run simultaneously under them, which can cause one or more of the OnBase Clients to fail. Multiple OnBase Clients can be safely run as Windows services under a single distinguished (named) account (e.g., domain\username) because a separate session is created for each service, so they do not share the same memory pool. However, the total number of services that can be run is still limited by the total amount of memory available on the workstation.
In case only one or two accounts need to be shared on the server, be sure to apply the -INIFILE="[Full Path]\[File Name]" switch and point each Windows service to its own onbase32.ini file. Then, edit each onbase32.ini with its own TEMP Parse Path.