PHINMS 3.0
Christina Crawford
Lowe, Phillip (DOH)
PHINMS 3.0 is a new version of PHINMS. PHINMS 3.0 now supports TLS 1.2 which we should all be using. It can be set up to use both TLS 1.0 and 1.2. We have already installed it on a few servers as we are slowly working on the migration to Win 2012.
MTS is the web based tool and was more like version .03 when the trial was started. There is no connection in the code between the two.
Phill Lowe – 360 236-4261
--
---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
phinms+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Christina Crawford
Christina Crawford
Francis de Wet
Lowe, Phillip (DOH)
Not really. The changes are new version of Tomcat and Java and addition of TLS 1.2. As I understand it nothing else.
Nope, still using the bat file to run the console.
Lowe, Phillip (DOH)
That is pretty new. It wasn’t there about three weeks back when we looked.
Christina Crawford
Christina Crawford
Lowe, Phillip (DOH)
It can be installed to use both versions of TLS. You should push your partners to also upgrade. We are pointing out that this is a good opportunity to move to Windows 2012 as well.
I don’t recall where the configuration happens. Once all of your partners are upgraded, you can turn off TLS 1.0 for a much more secure system.
We do not use the remote console and have not installed it that way.
Christina Crawford
phill
Emily Cheng
Preacher Man
Emily,
I would start by carefully reading https://tomcat.apache.org/connectors-doc/webserver_howto/iis.html. I believe it will provide enough information to search for the appropriate plugin (if not a direct link) as well as details related to configuration.
My cursory look suggests IIS 7 will only work with 64 bit applications (e.g. Tomcat 7... at least it wants 32 bit set to false). That may not play well with PHINMS 3.0. I haven't yet unpacked my copy to see if it is a 64 bit JVM. Hopefully others who have tried this can provide real life experience.
I've never been an IIS fan. An Apache proxy plays much nicer with Tomcat IMHO.
Good luck
Tom
Sent: Thursday, February 8, 2018 3:59 PM
To: PHINMS group
Subject: Re: PHINMS 3.0
Emily Cheng
Lowe, Phillip (DOH)
Lowe, Phillip (DOH)
That would be for PHINMS 2.8.2, and one instance of 2.9. Now moving to 64 bit of 3.0.
Phill Lowe – 360 236-4261
From: phi...@googlegroups.com [mailto:phi...@googlegroups.com] On Behalf Of Emily Cheng
Sent: Tuesday, February 13, 2018 8:49 AM
Preacher Man
Phil,
Was this (below) referring to your previous post saying you have been running 64 bit JVM (PHINMS) "for years"? Did you replace the JVM that 2.8.2 installs with? Mine copy is certainly a 32 bit JVM (otherwise it wouldn't run very nice on my old XP box :-). Maybe you could provide a few more details of your configurations. That might help Emily with her question.
It seems there are fewer issues running 64 bit JVM on *NIX with Tomcat apps, but note that Windows Tomcat has come in both 32 and 64 bit versions for quite some time (see their download site). I assume that is due to some kind of incompatibilities but I haven't gone to the trouble to nail down specifics.
There is certainly no issue with 32 bit JVM on a 64 bit MS OS (they way I always setup and ran PHINMS when I still worked), but it seems to me the issue here is between a 64 bit IIS and the JVM (version).
I gotta unpack my 3.0 and see what is inside (grin).
Tom
Sent: Tuesday, February 13, 2018 10:52 AM
To: phi...@googlegroups.com
Subject: RE: PHINMS 3.0
Lowe, Phillip (DOH)
Hmmm, Can’t say we did anything special. I do know we had the 64 bit PHINMS and the 64 bit SQL drivers. I assume that would require a 64 bit JVM. There was also a bit of trouble with the scans because it kept showing an older JVM after they had run an update process. That was back when you could use the web to do an update of the 32 bit but not the 64 bit versions. For a couple of years we had to update the JVM manually because our server folks could only push the 32 bit update.
Phill Lowe – 360 236-4261
Preacher Man
Phil,
I guess I'm just not getting it... I was never aware of a "64 bit PHINMS". Every version I ever got a hold of ran just fine on my old x86 boxes (e.g. 32 bit) and I never saw a 64 bit vs. 32 bit offering from CDC. That said, most of the stuff that follows relates to MS platforms. The *NIX guys have a whole 'nother experience.
I know there may be some confusion regarding Java virtual code versus the native code that interfaces the JVM to the hardware. It is that interface that is in question and that needs to match up AFAIKT. On MS boxes that native interface is generally implemented in .DLL binaries. In other words, a "64 bit JVM" and a "32 bit JVM" should run the same pure Java binaries (.class files) but could not be used cross platform. The naming references the native interface.
A 32 bit version of XP for example would not run a "64 bit JVM", although a 64 bit MS server OS could run a "32 bit JVM" because of downward compatibility - the "32 bit mode" and hence two different "Program Files" folders on MS 64 bit platforms.
I believe this is why people report that (64 bit) IIS needs a matching "64 bit Tomcat" in order to interface. That interface is typically ISAPI/AJP which is native machine code, not JAVA virtual code. OTOH, a straight HTTP reverse proxy connection shouldn't care and would even work across networks.
Loyall, David
According to my experience and https://stackoverflow.com/questions/2664424/tomcat-on-windows-x64-using-32-bit-jdk#comment2682778_2664456, a 64-bit Tomcat requires a 64-bit JDK.
Does anybody have a spare 32-bit windows laying around to try installing and running PHINMS 3.0 on?
I believe that 2.9 would successfully install, but not run. I speculate that manually replacing Tomcat with the 32-bit version would have solved the problem, but my customer (small hospital) simply provided a 64-bit Windows machine instead. If I recall correctly, it was specifically the 64-bit Tomcat exe files that were the problem.
Cheers,
--Dave L.
Tom
--
---
[older message trailers snipped out]
Preacher Man
I believe that is correct Dave. This is actually related to the PHINMS 3.0 topics that Phill Lowe has graciously contributed to. I finally got around to unpacking 3.0 on my ancient 32 bit XP box and it is indeed installed with a 64 bit JDK, so of course it would not run.
I could point the default HSQL dB at a 1.6x 32 bit JDK and run it, but not the PHINMS Tomcat which has class signatures requiring a minimum of 1.7 JRE. And while I have not yet confirmed, I believe there are parts that
may require a 64 bit JDK/JRE.
For development work I have commonly used the scripts in (Tomcat) appserver\bin to run PHINMS from the command line, rather than as a service. That of course requires some simple external wrapper scripts to set up needed environment variables including JAVA_HOME and JRE_HOME. I guess my next step will be to install a 1.7 JDK and see if I can get 3.0 to run 32 bit, but I don't have high hopes as I'm guessing that tcnative-1.dll will (eventually) get loaded and it will indeed be 64 bit.
The EXE Tomcat file are only needed for the service, but seem to be 64 bit as well. I'll post more of my findings after 1.7 32 bit JDK testing.
I do know that the ONLY difference in the PHINMS application libraries between 2.8.02 and 3.0 are ebxml.jar and resources.jar. And supposedly the only differences between 2.9 and 3.0 are updated Tomcat and JDK. I don't have 2.9 loaded at home and don't recall if it installed 32 bit or 64 bit, but I think it was 32 bit. If that is indeed the case I would tell (32 bit) clients just to stick with 2.9 or 2.8.02 and call it a day.
Of course that won't help with the TSL/SSL protocol issue, but if it turns out the PHINMS app is REALLY platform agnostic, putting 3.0 up on a 32 bit Tomcat/JDK that does support the newer TSL protocols might be doable with some work. I may look into that as well if I get bored (:-).
Tom
Sent: Wednesday, February 28, 2018 12:54 PM
According to my experience and https://stackoverflow.com/questions/2664424/tomcat-on-windows-x64-using-32-bit-jdk#comment2682778_2664456, a 64-bit Tomcat requires a 64-bit JDK.
Tom
