elligence Deployment Scenarios

This document will help you figure out how to set up elligence in your office. It discusses different ways that elligence might be installed.

Server Roles

Depending upon the Deployment Scenario that you are using, multiple server roles may be performed by a single machine. Regardless of how many machines you use to run elligence, the following jobs must all be done. See the elligence System Requirements for the specific requirements of each role.

Workstation

This is the computer where a user logs into elligence. Internet Explorer 6.0 or higher is required on all workstations. The DSClient.exe file is installed here. It connects to the Application Server in order to log into elligence.

Application Server

This server sends data to the workstations. With a small number of users, the Application Server can also be a workstation, and send data to itself. In the other extreme, there may be multiple Application Servers in scenarios with more than 25 concurrent users.

Data Server

This server houses the Data. In most small to mid-sized implementations, the Data server and Application Server jobs are performed by the same computer. There is only one Data Server, regardless of the number of users or locations.

Transmission Server

The transmission server is a secondary Application Server that handles all the EDI Send/Receive activities. It is used when the Application Server is a dual-processor machine with any operating system, or when the Application Server uses the Windows 2003 operating system. Windows XP Professional is recommended for Transmission Servers, since it has the highest rate of compatibility with available dial-up modems.

If you do not wish to deploy a Transmission Server, then you should use a single-processor elligence Application Server, and it must not be running Windows 2003 Server.

Deployment Scenarios

elligence is a highly scalable application. Although it can run on a single computer, there will usually be multiple computers in an installation. Depending on the number of concurrent users, the requirements may vary. See the elligence System Requirements for detailed specifications of each machine.

• You must not give the elligence server(s) a publicly addressable IP address, or protected health care information may be compromised, and you would be in breach of HIPAA security and privacy regulations. See Running elligence Safely Over the Internet for more information on security and multiple locations.
• Installing network, modem, or IIS-related programs on the server other than those required by elligence is not recommended.
• Important: Modem support for Windows 2003 Server, and for servers with multiple processors using any operating system, is extremely unreliable. You must use the Transmission Server scenario for EDI Send/Receive if your elligence Application Server (a) is running Windows 2003 Server or (b) has multiple processors.

Single Server

• 1-25 Users
• Single dedicated elligence server that acts as both Data and Application server.
• With 1-5 users, the server may also be a Workstation.
• Dial-up Modem is connected to server.

This is the most common setup for small- to mid-sized practices and billing services. A single server means that maintenance and networking is relatively simple. Users always log into the same server, and updates are only performed in one place.

Dedicated Data and Application Servers

• 25-50 Users
• Two dedicated elligence servers.
• Application Server runs IIS, and has the elligence Application Server program installed.
• Users connect to Application Server, which in turn connects to Data Server.
• Neither server is a workstation.
• Dial-up Modem is connected to Application Server.
• Important: If the Application Server runs Windows 2003, or has multiple processors with any operating system, then a Transmission Server is required.

This scenario is common in mid- to large-sized offices and billing services. While the distributed configuration adds an additional level of complexity, it is also more versatile, robust, and can handle a bigger load. All access to the Data Server is through the elligence Application Server, which allows for greater security and accountability.

Most elligence maintenance operations are still performed at the Application Server. However, sometimes it may be necessary to access the Data Server directly. The connection between the two machines must be extremely reliable. It is highly recommended that they be in the same physical location, though this is not required. (See Running elligence Safely Over the Internet for more information on multiple locations.)

Multiple Application Servers

• 50 or More Users
• One dedicated elligence Application Server per 25 users.
• One dedicated elligence Data Server.
• Application Servers run IIS, and have the elligence Application Server program installed.
• Users connect to an Application Server, which in turn connects to Data Server.
• No servers are workstations.
• Dial-up Modem is connected to a designated Transmission Server. Regardless of which Application Server a user is logged into, the Transmission Server handles all EDI dialing.
• Important: If the Application Servers run Windows 2003, or have multiple processors with any operating system, then a Transmission Server is required.
• When updating to a new version of elligence, each Application Server must be updated individually.

This scenario allows elligence to scale to the largest offices and billing services. All of the benefits of Dedicated Application and Data Servers apply to this configuration, but by distributing the work of the elligence server, more users can be added indefinitely. This opens the door for virtually unlimited load-balancing capabilities.

It is not known at this time exactly what the upper limit would be for a single Data Server. If you have a very large number of users who must be accessing elligence at the same time, please contact us to discuss your situation.

Transmission Server

• Any number of users
• Similar to Multiple Application Servers, above. Primary server handles the majority of the load, and Secondary server is used for EDI transmissions only.
• Dedicated Application/Data server(s) may or may not be required, depending on the number of users.
• Application Servers run IIS, and have the elligence Application Server program installed.
• Dial-up Modem is connected to the Transmission Server. No matter where the user is logged in, all send-receives will automatically be performed at the Transmission Server.
• When updating to a new version of elligence, each Application Server must be updated individually.
• Important: Transmission Server cannot have multiple processors, or run the Windows 2003 Server operating system. Windows XP Professional is recommended.
• Transmission Server can double as a workstation if fewer than 5 users are logged into it at the same time.

This configuration demonstrates how elligence's versatility can help work around problems. Several common server configurations are incompatible with most dial-up modems. In particular, we have encountered numerous problems using Windows 2003 and multiple-processor machines with any OS. Of course, if you are going to use elligence to bill electronically, a stable modem connection is a necessity.

One solution is to set up a secondary elligence Application Server that acts as a "Transmission Server." Users log into the primary server, but when they click Send-Receive in the EDI Manager, the transmission actually occurs from the Transmission Server. Windows XP Professional is recommended for the Transmission Server.

Note: You need to use this configuration if you use Windows 2003 on your elligence Application Server, or if your elligence Application Server has multiple processors with any operating system.

Disclaimer

DSI does not support or guarantee compatibility with third-party software or hardware, even if DSI has recommended such products.

The information contained in this document is provided "as is" without warranty of any kind, and is subject to change without prior notice. Data Strategies, Inc. disclaims all warranties, either expressed or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Strategies, Inc. or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Strategies, Inc. or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential damages, so the foregoing limitation may not apply.