Just looking for some clarification before we push Install for our SP10 test environment. We've never heard support ask to get on our Interop or GUI servers, just our app or db. We think we've got it right, but want to make sure. GUI=app/jboss server; Interop=DB/MIK server? I assume a single server configuration is for environments where this is all on the same box.
I tried to get the same clarification as well from GE. Below is the response I got.
From the documentation(Press F1 from Configurator) it appears that the interop server is for the Qvera Interface server.
From: GE
Date: August 28, 2015 at 10:47:47 AM CDT
To: Nick
Subject: RE: 1-716038091
Nick,
Okay what I did find out is yes it is due to load balancing is why it RECOMMENDS those other servers. But that is all I could find. That and the brief useless help explanation. Most everyone is doing the one server though to not have issues. I think that is the smart thing to do for now until it is further evolved.
GE
From: Nick
Sent: Thursday, August 27, 2015 2:52 PM
To: GE
Subject: RE: 1-716038091
Importance: High
Hey GE,
I’m going through the Service Pack 10 documentation you sent me, and currently working on performing the install in our test environment. I was wondering if you have a second for a call to discuss which settings should be used in the screenshot below? Or if it’s something that can be answered via email that’s fine too.
The recommended Configuration says: 1 GUI Server, and 1 Interop Server.
1. Do I only need to add those 2 servers below?
2. Is GUI server going to be our Jboss server(same server I am running the Confguration Utility from)
3. Is Interop Server going to be our Qvera server or our DTS server? If Qvera, we don’t have a test Qvera server, so do I just leave this blank for the test install?
4. Is the database server supposed to be added here as well?
So did you ever install an interop in your test environment? We're like you and don't have a qvera box for test. How about your database server? Did you add it to the list?
If you are installing Service Pack 10 in a Test Environment, I would not worry about setting an InterOp server or GUI server separately. Those are meant for large installations based on my knowledge. My suggestion is to change the "Concurrent Users" number to what you think your Test environment will have and click on Calculate, which should adjust the "Recommended Configuration".
However, when you get to Production, you will have to ensure you have enough resources allocated to the JBOSS server to accommodate the load of your environment.
We have a separate DB/ MIK and JBOSS/App server. I had a GE tech do our upgrade. He chose single server. He explained that GUI and INTEROP are new for multiple JBOSS servers for load balancing.
Single server applies to 1 DB with a single stand alone JBOSS.
Our upgrade on Server 2008R2 went very smoothly. We had to install Powershell 3 prior to the upgrade. I did not have to change or add any group policy settings.
Hope this helps.
JJC
This is the response I got back from GE, so not really helpful information passed what I hadn't already told them. The confidence in some of the answers doesn't comfort me either.
John, it sounds like we have the same type of setup with a single website and single DB/MIK and and APP/JBOSS servers. We went with single server config in our test upgrade, so that's what were going with on Saturday for our prod upgrade.
- JBoss and App server are one and the same. JBoss is the Java equivalent of Window’s IIS function. The Jboss/App server provides the front-end functionality of Centricity (aka CPS).
- The DB Server hosts the SQL Database which carries all of the patient EMR information.
- I have not heard the term single server unless you are referring to putting both the DB and the JBoss server on the same box, which is not recommended by GE.
- The GUI server is likely a lose term for the JBoss/App server.
- The Interoperability server is an advanced feature where one server handles the normal front-end (JBoss) requests and another (Interoperability) server handles the subscriptions/batches etc.