Thanks, Josh.
Progress, I think. In my global properties, the value of idm.pric is just the bare domain ID. When I use this for WACS, it does start successfully. Surprising, since the documentation and the web.xml file itself say that it should be fully-qualified and start with the "HTTP" service name.
I tried testing it with http://idsbidev/biprws/logon/adsso. This throws an error box:
Cannot Start Application
Cannot continue. The application is improperly formatted.
Contact the application vendor for assistance.
Clicking Details produces the following:
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.18063
System.Deployment.dll : 4.0.30319.34244 built by: FX452RTMGDR
clr.dll : 4.0.30319.18063 built by: FX45RTMGDR
dfdll.dll : 4.0.30319.34244 built by: FX452RTMGDR
dfshim.dll : 4.0.41209.0 (Main.041209-0000)
SOURCES
Deployment url : http://idsbidev/biprws/logon/adsso
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://idsbidev/biprws/logon/adsso resulted in exception. Following failure messages were detected:
+ Exception reading manifest from http://idsbidev/biprws/logon/adsso: the manifest may not be valid or the file could not be opened.
+ Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
-HRESULT: 0x8007001f
Start line: 0
Start column: 0
Host file:
+ A device attached to the system is not functioning. (Exception from HRESULT: 0x8007001F)
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [1/22/2015 1:00:27 PM] : Activation of http://idsbidev/biprws/logon/adsso has started.
ERROR DETAILS
Following errors were detected during this operation.
* [1/22/2015 1:00:28 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from http://idsbidev/biprws/logon/adsso: the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
-HRESULT: 0x8007001f
Start line: 0
Start column: 0
Host file:
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
at System.Deployment.Application.Manifest.AssemblyManifest..ctor(FileStream fileStream)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Runtime.InteropServices.COMException
- A device attached to the system is not functioning. (Exception from HRESULT: 0x8007001F)
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IsolationInterop.CreateCMSFromXml(Byte[] buffer, UInt32 bufferSize, IManifestParseErrorCallback Callback, Guid& riid)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
and there are still errors in the WACS logs:
com.sap.security.saml2.cfg.SAML2GlobalConfigImpl||Could not initialize SAML2 global configuration
com.sap.security.saml2.cfg.exceptions.SAML2ConfigurationException: Could not load trusted Identity Providers
at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.loadAllTrustedIdPs(SAML2TrustedIdPsConfigImpl.java:151)
at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.<init>(SAML2TrustedIdPsConfigImpl.java:73)
at com.sap.security.saml2.cfg.SAML2ConfigImpl.initConfigurationObjects(SAML2ConfigImpl.java:79)
at com.sap.security.saml2.cfg.SAML2ConfigImpl.<init>(SAML2ConfigImpl.java:55)
at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.initGlobalConfiguration(SAML2GlobalConfigImpl.java:98)
at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.<init>(SAML2GlobalConfigImpl.java:69)
at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.createInstance(SAML2GlobalConfigImpl.java:85)
at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.getInstance(SAML2GlobalConfigImpl.java:78)
at com.sap.security.saml2.cfg.SAML2CfgFactory.getSAML2GlobalConfig(SAML2CfgFactory.java:24)
at com.sap.security.saml2.cfg.ljs.SAML2LJSConfiguration.updated(SAML2LJSConfiguration.java:64)
at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:181)
at org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)
Caused by: com.sap.security.saml2.cfg.storage.CfgStorageException: Could not obtain sub configurations for cfg path: default/trusted_providers/trusted_idps
at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.getSubCfgNames(CfgFileStorage.java:307)
at com.sap.security.saml2.cfg.storage.CfgObject.getSubCfgPaths(CfgObject.java:136)
at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.loadAllTrustedIdPs(SAML2TrustedIdPsConfigImpl.java:121)
... 11 more
Caused by: com.sap.security.saml2.cfg.storage.CfgStorageException: SAML 2 configuration directory (set to "null") is incorrect! Use system property "sys.global.dir" to specify it the correct one!
at com.sap.security.saml2.cfg.ljsadapters.SAML2LJSAdapters.getConfigurationRoot(SAML2LJSAdapters.java:46)
at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorageAccessor.getReadableConfiguration(CfgFileStorageAccessor.java:38)
at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.obtainReadableConfiguration(CfgFileStorage.java:408)
at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.getSubCfgNames(CfgFileStorage.java:287)
... 13 more
com.businessobjects.framework.servers.util.ModuleToBundle||Bundle D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\pjs\container\work\AD1HFDBOW010.WebApplicationContainerServer\modules\cdsframework.jar cannot be started
org.osgi.framework.BundleException: The bundle "cdsframework_0.0.0 [114]" could not be resolved. Reason: Missing Constraint: Require-Bundle: cdz_ext_lifecycle; bundle-version="0.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
at com.businessobjects.framework.servers.util.ModuleToBundle.installAndStartBundle(ModuleToBundle.java:165)
at com.businessobjects.framework.servers.util.ModuleToBundle.modulesToBundles(ModuleToBundle.java:128)
at com.businessobjects.framework.servers.util.ModuleToBundle.activate(ModuleToBundle.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
at org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
at org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
at org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
Not sure if these are related to my issue.