webMethods Knowlegebase : MWS Unable to connect to IS

Problem

Customer have recently applied IS_10.7_Core_Fix12 in multiple environments.

After applying mentioned fix customer observe in all their environments the WmMonitor is not connected from MWS.

On checking IS logs customer found below entries were produced in all environments (hence issue is reproduced across 3 different environments - they didn't observe this issue before proceeding to apply in different environment):

[ISS.0012.0041E] Unable to initialize SAML authentication module. Cannot get reference of the OSGi service (&(objectClass=com.softwareag.security.identity.InternalSecurityTokenService)(samlVersion=2.0)).

[ISS.0012.0012E] Authentication of user "null" failed with exception: com.wm.app.b2b.server.ServiceException: OSGi service for SAML authentication not initialized.

[ISS.0012.0041E] Unable to initialize SAML authentication module. Cannot get reference of the OSGi service (&(objectClass=com.softwareag.security.identity.InternalSecurityTokenService)(samlVersion=2.0)).

[ISS.0012.0012E] Authentication of user "null" failed with exception: com.wm.app.b2b.server.ServiceException: OSGi service for SAML authentication not initialized.

On checking for KB articles on empower, e.g. 1800898 they proceeded to rebuild OSGi profile in one of our environments.

After trying with both the new custom_wrapper.conf as well as copying over the backed up custom_wrapper.conf before the new OSGi profile was built, the Integration Server fails to start with following error in server.log:

[ISS.0025.0017I] Repository Manager started

[ISS.0014.0054C] Error occurred while initializing server: java.lang.NoSuchMethodError: org.apache.logging.log4j.spi.LoggerContextFactory.isClassLoaderDependent()Z

at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:49)

at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:48)

at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:33)

at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)

at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)

at com.maverick.ssh.SshConnector.<clinit>(SshConnector.java:142)

at com.maverick.ssh.LicenseManager.addLicense(LicenseManager.java:18)

at com.wm.app.b2b.server.sftp.client.SFTPClientManager.initLicense(SFTPClientManager.java:118)

at com.wm.app.b2b.server.sftp.client.SFTPClientManager.init(SFTPClientManager.java:138)

at com.wm.app.b2b.server.sftp.client.SFTPClientManager.initialize(SFTPClientManager.java:110)

at com.wm.app.b2b.server.Server.run(Server.java:665)

Hence in one environment now Integration Server is unusable.

Customer requests are as follows:

1 They need to resolve the MWS unable to connect with IS Monitor, if possible without rebuilding OSGi profile otherwise precise steps that does not run us into this problem.

2 They need to recover the Integration Server that now wouldn't start after following the referenced KB for rebuilding the OSGi profile.