Second Tomcat without Load Balanacing

johnmcnair
New Contributor III

We have a growing environment that is not Load Balanced yet. We have a need to have a second Tomcat instance for administrative tasks. I remember @jhbush1973 mentioned something about doing this. Is there an thread or article that can help us with this. We will eventually get Load balanced.
Thank you,
John

3 REPLIES 3

chriscollins
Valued Contributor

You really could just set up a second tomcat instance, point it at the database, turn on clustering, and just point your admins to the admin task one. Really shouldn't be any more difficult then that.

brad
Contributor

@johnmcnair Your master JSS does a lot of heavy lifting (calculating smart groups, sending push notifications, etc). If you can make it so your master does not serve clients you might see some benefits. Then, like @chriscollins said, you can point your admins to that master JSS to run admin tasks. I am not aware of any documentation on this topic. I would highly recommend replicating this in a dev environment.

Basically you would stand up a new JSS, turn on clustering, point the DNS for your original JSS to resolve to the new cluster node. Clients should then start checking in only on the new cluster node.

Good luck!

Brad

donmontalvo
Esteemed Contributor II

@brad Awesome, so basically:

  1. jss.domain.com <-- keep the same FQDN (day to day administration, APNS, Smart Computer Group calculations, reports, etc.)
  2. jss2.domain.com <-- point clients to the new Tomcat (policies/reporting)

For this scenario, a re-enroll using a new QuickAdd pointing to jss2.domain.com would work. Not sure if simply changing the URL works, or if that might break enrollment?

Don

--
https://donmontalvo.com