The CORE HL7 MySQL Schema Engine, in addition to the 3 PRIMARY MS Windows Services (see Running as a Service) we also allow you to create Private Services which run separately and will only run 1 Schema profile. The 3 PRIMARY services are fully multi-threaded and can have multiple Schema Profiles running in them simultaneously. There is really no "right" or "wrong" answer when it comes to which Windows Service you assign your Schema Profile to, it depends purely on your preference.

 

 

 

Why would I need to choose a Private Service?

 

 

Of course, your reasons are your own, we just want to give you the most flexible system that we can. There is theoretically nothing wrong with running ALL of your Postmaster profiles in a single service instance. That being said here are a few scenarios that we think might apply.

 

 

•If you have many Schema Profiles you might want to always bring in NEW clients using a Private Service. This would allow you to run any testing or certification you need done in a separate space, allowing you to Stop, Start, Install, Remove, etc. WITHOUT impacting any of your other PRIMARY interfaces running in other services. Once you are done with this, you can assign the profile to one of the 3 PRIMARY services and remove the Private Service.

•Troubleshooting problems. If a single MySQL Schema Profile interface starts to "misbehave", you can "cut it from the herd" and assign it to a Private Service.

•Isolating High Value or High Traffic clients.

 

 

To assign a Schema Profile to a private service all that you have to do is select Run In Private Service when you are creating or editing your profile.

 

 

 

It's really that easy. Once done you will be able to see your private service in the Windows Service Status area where you can Install, Start, Stop, Remove the service just as easily as the 3 PRIMARY service instances.