Troubleshooting
Problem
After upgrading Integration Server from 9.9 to 10.15 and updating the JAVA_SYSTEM_CLASSPATH property in the wrapper.conf file to include third-party application JARs, the server logs show the error 'OSGi service for SAML authentication not initialized'. Following this change, it was observed that My webMethods Server (MWS) was unable to connect to IS.
Error in logs:-
2025-07-10 01:01:35 EDT [ISS.0012.0041E] (tid=1824) Unable to initialize SAML authentication module. Cannot get reference of the OSGi service (&(objectClass=com.softwareag.security.identity.InternalSecurityTokenService)(samlVersion=2.0)).
2025-07-10 01:01:35 EDT [ISS.0012.0012E] (tid=1824) Authentication of user "null" failed with exception: com.wm.app.b2b.server.ServiceException: OSGi service for SAML authentication not initialized.Symptom
The OSGi service for SAML authentication is not initialized in the IS logs after updating the JAVA_SYSTEM_CLASSPATH property in the wrapper.conf file during an upgrade from 9.9 to 10.15. This update was necessary to maintain integration with a third-party system. However, after the update, MWS is unable to connect to IS.
The specific change in wrapper.conf was from set.JAVA_SYSTEM_CLASSPATH=/APPS/WebMethods1015/common/runtime/bundles/platform/eclipse/plugins/com.softwareag.platform.bootstrap_10.15.0.0000-0574.jar:/APPS/WebMethods1015/common/runtime/bundles/platform/eclipse/plugins/org.eclipse.equinox.launcher_1.5.300.v20190213-1655.jar
To:
set.JAVA_SYSTEM_CLASSPATH=/APPS/WebMethods1015/common/runtime/bundles/platform/eclipse/plugins/com.softwareag.platform.bootstrap_10.15.0.0000-0574.jar:/APPS/WebMethods1015/common/runtime/bundles/platform/eclipse/plugins/org.eclipse.equinox.launcher_1.5.300.v20190213-1655.jar:%CLASSPATH%
Cause
The issue was caused by the incompatibility of third-party JAR files with Java 17, which is required by wM 10.15. The current JAR files are only compatible with Java 8, leading to the failure in initializing the SAML authentication module.
Diagnosing The Problem
- Inspect the IS server logs for errors related to OSGi service initialization.
- Verify the JAVA_SYSTEM_CLASSPATH property in the wrapper.conf file.
- Test the impact of adding %CLASSPATH% to the JAVA_SYSTEM_CLASSPATH property.
- Check the compatibility of third-party libraries with Java 17.
- Update third-party libraries to versions compatible with Java 17.
- Enable wrapper debug mode to analyze classpath composition in working vs. failing scenarios.
- Collect IS diagnostics ZIP for both failing and working scenarios to compare classpath differences.
Resolving The Problem
The issue was caused by third-party libraries incompatible with Java 17, which is required by wM 10.15. To resolve:
- Identify all third-party libraries currently in use.
- Update these libraries to versions compatible with Java 17.
- Verify the updated libraries are correctly referenced in the wrapper.conf file.
- Restart the Integration Server (IS) and monitor logs for any further errors.
- Validate that the SAML authentication module initializes correctly and that there are no authentication failures.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
29 November 2025
UID
ibm17252676