You have done everything and now you are ready to run your system. You have:

 

•Activated a license of some type.

•Configured your Global Settings.

•Created and Enabled 1 or more Sender Profiles.

 

 

Now you have 2 ways to run your profiles.

 

You can test your profile(s) by Running Locally, OR (if your license allows it) you can install and run your Windows Service(s). Your CORE HL7 TCP/IP Sender allows 2 different types of Windows Service.

 

The Private Service. When you assign a Sender Profile to a Private Service it means just that, it creates a MS Windows Service which will run ONLY that profile.

 

The Primary Service(s) Instance #1 up to Instance #20! The fact that there are so many available primary instances won't matter to you unless you have a license that allows you to create many Sender profiles. You can assign multiple profiles to a SINGLE instance or you can distribute all of your profiles amongst the available instances. There really isn't a "right" or "wrong" choice here, but IF you need to create dozens or even hundreds of CORE HL7 TCP/IP Senders you will probably want to distribute your profiles amongst the available primary service instances.

 

The benefits of profile distribution. IF you have many sender profiles assigned to 1 primary service instance and you want to create a new one you have to RESTART that instance after you create your new profile. This will cause a very slight disruption to all of the other profiles assigned to that instance. Likewise, if you ever need to EDIT a profile, or troubleshoot a profile by Running it Locally, you will have to STOP that service instance while you do this which also stops all other profiles assigned to that instance.

 

WARNING: We give you 20 primary services instances PLUS the ability to create a Private Service. You might be tempted to just run every profile in a service by itself, and this is certainly possible, and it wouldn't even cause a problem unless you have MANY sender profiles (like 60 or more, or less depending on your computer/server). Remember that the more Windows Services you have (not just ours, but in total) the longer it takes your computer/server to boot up. Also every instance has it's own base level of memory and CPU it will use in addition to the amount required for each profile, this means that you might have an instance with only 1 profile that uses 25 MB of RAM while the same instance with 5 profiles only uses 35 MB. In addition, remember that the CORE HL7 Sender software needs to REFRESH the Services Status which we do A LOT. The more services you have, the longer this takes. The longer it takes to START all the services, STOP all the services, etc.

 

Best Practice: We don't recommend that you create more than 40 total sender services (20 Primary and 20 Private), but remember, this is just our recommendation.

 

Optimization Hint: In the Tools Menu of the Main Window there is an option (Distribute Primary Service Profiles). If you click that option the software will automatically distribute ALL of your sender profiles evenly amongst the 20 available primary service instances while IGNORING any profile that is assigned to a Private Service. Example - You have 100 sender profiles all assigned to 2 or 3 different instances. You click this menu option and voila, you now have 5 profiles each assigned to primary instances 1-20.

 

New Profile / Troubleshooting Hints: When you are creating a new profile we recommend that you assign it to a Private Service. This allows you to make sure that the new interface works correctly, you can start or stop it all by itself without impacting other profiles. Once you are satisfied that everything is working the way that you want then PROMOTE it to a Primary Instance by stopping and uninstalling the Private Service, then edit the profile and assign it to the Primary Instance you want, then restart that instance (or install and start if it's a new one).

 

If you need to Troubleshoot an issue with a profile that is running in a Primary Instance with other profiles we recommend that you Edit that profile and assign it to a Private Service (only temporarily). Then you can treat it just like a new profile, make sure that works, Run it Locally, etc.