PHINMS compatibility with SQL Server 2016

[Christina Crawford]

Does anyone know if PHINMS 2.8.02 works with SQL Server 2016?

Thanks,

Christina Crawford

PADOH

[Preacher Man]

Cristina,

Now that I am retired I no longer have access to the "latest and greatest" MS (or other) vendor offerings so regretfully I can't directly answer.

However, if your organization is encouraging you to move to any particular version of OS, database, or whatever I would expect they provide you with a "scratch" server for compatibility testing. That provides you the opportunity to test compatibility and deployment strategies... both a GOOD THING. Having a test environment for PHINMS (even if it is just your work station) is extremely useful, even when people say "Oh yeah, you can do that".

While time consuming, the more you test the easier it gets and it does pay off down the road. I will note that I have had better luck in the past using third party JDBC drivers for MSSQL as opposed to the MS drivers.  However that may have changed with recent releases.  Google is your friend here.  If things don't work out of the box see what other users are saying (not just for PHINMS, but generally since lots of folks are using MSSQL with Java).

Best of luck and be sure to post your results!

cheers

Tom

---

From: phi...@googlegroups.com <phi...@googlegroups.com> on behalf of Christina Crawford <ccrawf...@gmail.com>
Sent: Tuesday, April 4, 2017 3:40 PM
To: PHINMS User Community
Subject: PHINMS compatibility with SQL Server 2016

 

--

---
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.

[Emily Cheng]

We have upgraded our PHINMS using SQL Server 2016.  Both PHINMS server and SQL servers are upgraded to Windows Server 2012.  I didn’t have to install new JDBC driver.  I got it work by changing the new db server name in the configuration files (after stopping the PHINMS service first).  It didn’t work when I tried to change via the PHINMS interface.  

Hope it helps and let me know if you need more info. 

Emily Cheng

SCDOH

[Ray Humphrys]

Off topic just a bit - I know it works fine with 2012 + 2014. I have 2016 but haven't tried that yet.

To unsubscribe from this group and stop receiving emails from it, send an email to phinms+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

---
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+unsubscribe@googlegroups.com.

[Preacher Man]

Nice Emily.  Thanks for posting the info!  I'm sure there are others that will benefit from your input.

I never had great faith in the PHIN-MS console.  But I'll note (as I believe I have posted previously) that in newer MS OS's one needs to start the PHIN-MS console with a right click and "Run As Administrator". Otherwise it appears to work, but can't update parts of the file system (likely due to permissions/security restrictions).

Same goes for lots of things even though you may be logged in as part of an admin group.  Curiously, I constantly had to fight the OS when trying to update files as a logged in admin (even with the "right click"), but had absolutely no issue with updates from a workstation over a mapped file share. Try as I might to understand, the peculiar MS file security never made a lot of sense to me coming from a *NIX background. But as they say, YMMV (:-).

Tom

---

From: phi...@googlegroups.com <phi...@googlegroups.com> on behalf of Emily Cheng <yche...@gmail.com>
Sent: Wednesday, April 5, 2017 9:39 AM
To: PHINMS group
Subject: Re: PHINMS compatibility with SQL Server 2016

 

[Christina Crawford]

Our PHINMS server was already Windows Server 2012 R2.  In order for the PHINMS console to update configuration files, you do have to right click the PHINMS console icon and select run as administrator.  Or, you can make that permanent by right clicking the icon and select properties.  Then select shortcut tab, select advanced button, check run as administrator box.  Then all you have to do is double click the icon, then enter the administrator credentials in the pop-up window.

We just did an in-place upgrade from SQL Server 2012 to SQL Server 2016.  I didn't have to update any JDBC drivers in PHINMS at all.  I googled the JDBC file name and found that they already were supported for SQL Server 2016.  I didn't have to update the server name as we just upgraded our current SQL Server database as an in-place upgrade. 

There was a SQL Server 2016 analysis done on the PHINMS database tables.  There some data types that were to be deprecated:

text

image

mtext 

replacement suggestions:

varchar(max)

nvarchar(max)

varbinary(max)

tables:

message_errq.payloadtextcontent

message_inq.pahloadtextcontent

messagingcache.response

phinmns_errq.payloadtextcontent

ptd_outq.payloadtextcontent

sender_inq.payloadtextcontent

Most of these seem to be involved with the Receiver database tables. 

[Phill Lowe]

Has anyone managed to get integratedSecurity=true to work with SQL server?  Our new databases are not set up to allow SA authentication and I am not having any luck so far.

I have the sqljdbc4.jar and sqljdbc_auth.dll installed in C:\Program Files\PHINMS\appserver\webapps\receiver\WEB-INF\lib per the MS documentation.  I am still getting a failure to connect to the database.  Any other ideas?

[Christina Crawford]

We have had success with PHINMS 2.8.02 working with JDBC 2012 drivers.  The server PHINMS is installed on and the SQL Server 2016 have operating systems of Windows Server 201R2. 

A few months ago the server PHINMS is installed on had its operating system upgraded from Windows Server 2012 to Windows Server 2016.  The SQL Server 2016 still had operating system Windows Server 2012.  PHINMS worked just fine.

Recently, the SQL Server 2016 server operating system was upgraded from Windows Server 2012R2 to Windows Server 2016 for our development and production environments.  Our development and production servers that have PHINMS still have operating system Windows Server 2016 with Java 8.  Now, our PHINMS  can't connect to our SQL Server 2016 database to access the TransportQ_Out table.  Our production SQL Server 2016 had an additional server added and those 2 servers were clustered together to act as one so if one server fails the other one will take over.   

At first, it was thought that the SQL Server clustering was an issue so the one server was shut down and clustering turned off.  The PHINMS services was stopped and started.  There was no change.  We have Rhapsody 6.2.1 that has Java 7 or 8 on the same server that writes to the same SQL Server 2016 database table and works successfully.  We also have a ELR web service that is on the same server also accesses a different database on the same server and works OK. 

So we tried different JDBC drivers and still no success.  The log files were looked at and also the logs in the appserver file folder in PHINMS.  All seems to point to PHINMS that uses Java 6 and the 2012 JDBC drivers are not compatible with the SQL Server 2016 operating system Windows Server 2016.

CDC PHINTech help desk was contacted and they suggested to use Squirrel SQL JDBC client on the servers where PHINMS is installed.  This software is used for JDBC connection issues.  It is configured with the same values as PHINMS.  I installed it on our development server that has PHINMS.  It could connect to our SQL Server.  This now indicates there is an issue with PHINMS.  It was suggested by other PHINMS users in other states to upgrade to a newer PHINMS version 2.9.00 as it has Java 7.  So I sent an email to PHINTech requesting a link and username and password to download this PINMS version.  I received the information .

After fighting with IE, etc., from my laptop to download the software, I had to go to my desktop support area to use one of their computers as they had access to do the downloads.  I also can't access this Google forum from my laptop or from the desktop support area computer anymore.  It seams that our computers have been locked out from this user forum.  Have to put in help desk ticket to get it opened up again for ftp://sftp.cdc.gov and this user form. 

Anyway, I got PHINMS 2.9.00 installed on our development server,  I did an upgrade so it would copy the configurations from the current PHINMS 2.8.02 install and put it into PHINMS 2.9.00.  I did screen shots with some notes in a WORD document if anyone is interested.  There is no PHINMS 2.9.00 documentation.  You have to use the PHINMS 2.8.02 documents that does have an upgrade section.  SUCCESS!!!  PHINMS 2.9.00 now can access our development SQL Server 2016 with operating system Windows Server 2016.  The issue though is that the PHINMS 2.9.02 console can't be opened up the .exe in the bin folder as it displays a pop-up window stating JAVA 7 needs to be installed.  You have to use the phinms .bat file that opens up the PHINMS console that is also in the bin file folder.  Now, when trying to use NEW MESSAGE to send a test file to CDC Staging Receiver, there is an issue that it can't connect.  It can retrieve the CDC public LDAP information from VeriSign .