Problems restarting SOI following database password reset

Products

• CA Service Operations Insight (SOI)

Issue/Introduction

We have updated our database password for SOI, and are having problems starting SOI back up. We have confirmed that our new password is good, are are not seeing any login failures like we did last time we did this.

We have done the following:

1) Stop SOI Manager, UI & All connector services

 

2) Generate new encrypted password and update following files on SOI Manager

 

1. A) Generate new encrypted password "\SOI\Tools\EncryptSAMCreds.bat <new password>" and update below configuration file

 

\SOI\tomcat\lib\hibernate.cfg.xml

 

1. B) Generate new encrypted password using "\SOI\Tools\CatalystEncrypt\encryptor.bat <new password>" and update below files with new encrypted string

 

\SOI\tomcat\registry\topology\physical\node0\sor\restserver.xml
\SOI\tomcat\registry\topology\physical\node0\sor\sorapp.xml 
\SOI\tomcat\registry\topology\physical\node0\sor\ssaserver.xml 
\SOI\tomcat\registry\topology\physical\node0\sor\ssaweb.xml 
\SOI\wso2registry\repository\conf\registry.xml
\SOI\wso2registry\repository\conf\user-mgt.xml
\SOI\ME\ServiceDiscovery\connectivityContext.xml 

 

3) Open a command prompt on SOI Manager, CD to \SOI\tomcat\registry folder and run "registryloader.bat"

 

When restarting SOI, it appears to be failing to initialize. We are seeing the following error in our consolidated error logs:

 

2021-07-15 16:30:03,723 ERROR [Source=, Thread=SOICAT] ps.PersistentStorageWrapper - Cannot establish Catalyst PersistenceService reference. . com.ca.ssa.sor.injector.DependencyInjectorException: org.eclipse.emf.ecore.resource.Resource$IOWrappedException: XML document structures must start and end within the same entity.	at com.ca.ssa.sor.injector.DependencyInjector.load(DependencyInjector.java:81)	at com.ca.ssa.sor.app.Bootstrap.boot(Bootstrap.java:95)	at com.ca.sam.manager.catalyst.ps.PersistentStorageWrapper$1.run(PersistentStorageWrapper.java:227)Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException: XML document structures must start and end within the same entity.	at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:288)	at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:666)	at org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl.doLoad(SDOXMLResourceImpl.java:589)	at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResourceImpl.java:634)	at org.apache.tuscany.sdo.helper.XMLDocumentImpl.load(XMLDocumentImpl.java:266)	at org.apache.tuscany.sdo.helper.XMLDocumentImpl.load(XMLDocumentImpl.java:239)	at org.apache.tuscany.sdo.helper.XMLHelperImpl.load(XMLHelperImpl.java:97)	at com.ca.ssa.sor.injector.DependencyInjector.load(DependencyInjector.java:67)	... 2 moreCaused by: org.xml.sax.SAXParseException; systemId: registry://topology/physical/node0/sor/ssaserver.xml; lineNumber: 122; columnNumber: 1; XML document structures must start and end within the same entity.	at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)	at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)	at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.endEntity(Unknown Source)	at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown Source)	at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source)	at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)	at org.apache.xerces.impl.XMLEntityScanner.scanContent(Unknown Source)	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanContent(Unknown Source)	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)	at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)	at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:268)

 

Environment

Release : 4.2

Component : Service Operations Insight (SOI) Manager

Resolution

One of the XML files was mysteriously being cut off at line 122.
Customer was able to restored the missing text from a backup.