Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

How Does Server Configurator Work?

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

3 Posts

2 Users

0 Reactions

56 Views

RSS

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

Topic starter

Has anyone figured out how the Server Configuration actually rebuilds JBOSS? Inside the 12_2 staging folder, I have found lots of scripts, but so far, I haven't found anything that explicitly creates the folder tree and their contents.

I'm asking for two reasons:

I'm really curious how these folders are built out and want to see the inner workings
When you pull in a database from another environment, you have to run the Server Configurator to reconnect the JBOSS and DATA servers. I am trying to figure out where the specific references are to the other environment and why the Server Configurator needs to nuke it from orbit
Specifically, in our sandbox environment (SBX), our Centricity installation says "12.2" all over the place, but the actual JBOSS folder that is installed is from 12.0, with no standalone folder. We can't figure out why, and our last resort is to clear the JBOSS and DATA servers and start from a fresh Windows install. I'd rather determine why this has happened instead of pretend it never did.

Thoughts?

Posted : December 5, 2019 11:41 am

tnc

(@tnc)

Posts: 517

Honorable Member

That second reason is a weird one (no 'standalone' folder). The proprietary nature of this Athena/Jboss caused me a few headaches when I implemented the firewall for the API thing a few months ago. I hope you can post your findings here if you get them.

I assumed this was all done to build two servers simultaneously (like interop and application). It would be overkill just for that but maybe it is easier that way. I think it still does not work quite right because you have to strategically boot the Jboss servers if you have interop+app

Posted : December 9, 2019 5:25 am

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

Topic starter

We have a development pipeline: a sandbox, a development environment, a training environment, and our production environment. We keep our JBOSS and database on different servers, and we try to refresh our pipeline environments every month, but that's a tall order. This script should help that, assuming nothing weird happens, like the JBOSS tree rebuilds wrong...

We tried pulling an old installation disk from our training environment, which we built when we upgraded to 12.2 about two years ago. That didn't work.

Then we erased the JBOSS server and rebuilt it from scratch, then ran the installation disk. That didn't work either.

Next steps are, I guess, figuring out how to get a new installation disk from our vendor. Currently, no one seems to know what is causing this.

Posted : December 9, 2019 5:36 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0