Tuesday, August 06, 2019

WebSphere Application Server Network Deployment 7.0 security.xml corrupted.

On one of our internal WebSphere application server network deployment v7 environments, I hit the following error.

The error was: com.ibm.websphere.ssl.SSLException: Cannot get security object from WCCM


Security.xml appeared to have been corrupted. The security.xml file was blank.

To resolve this, I had to copy a security.xml file from another server, and then edit it to 
  1. replace the original server name with the name of my corrupted server 
  2. change it to disable security altogether as instructed here.
    1. NOTE: I had to use the 2nd method mentioned, since my Dmgr was stopped. 
Thanks so much to Chandan Kumar of GeekFlare for posting this very useful procedure :-) 

In case something should happen to GeekFlare,  I am copying it below. Please attribute all credit to Chandan for this! 

The Database is not accessible after creating Always On Availability Group

 Having created a fully functional SQL Server Always On Availability Group, I connect using SSMS. Upon trying to expand the database, I get ...