Unable to connect CMC & BI Launchpad through HTTPS Connection

bassam — Sat, 03 Feb 2024 23:05:55 GMT

Hello Experts,

I am trying to connect CMC through HTTPs connection on SAP BO 4.1 SP8. I have created a JSK keystore file. I have followed all the steps in admin guide 12.1.4. After restarting the server it does not connect via https://localhost:8443/BOE/CMC. I am unable to go to the login page, instead it redirects me to a page showing "404 Missing page"

Where as when connecting through http://localhost:8080/BOE/CMC In the matrix section of the WACS server I am able to see HTTPS & HTTP in Web Application Container Server Metrics. I am able to connect via a HTTP fine and the Web Application Container Server is running with out any error.

Where can be the problem?

Thanking you in advance.

Best Regards,

Bassam Jamil

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

denis_konovalov — Mon, 24 Apr 2017 17:44:36 GMT

8080 is a default tomcat port, so is 8443 are you sure you're connecting to WACS and WACS is not running on same ports as tomcat ?

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

bassam — Wed, 26 Apr 2017 06:50:07 GMT

Dear Denis,

Thank you for your response.

As from the attached image 1.jpeg I assume that I am connecting to WACS.

Can you please elaborate "WACS is not running on same ports as tomcat"? How do check that?

Regards,

Bassam

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

bassam — Wed, 26 Apr 2017 07:17:19 GMT

Please find below the latest logs after restarting the WACS server from WACS_trace file in logging folder:

|83C2FBC915A84D5AB135F16FEE7635021|2017 04 26 12:07:49.840|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||java.lang.ArrayIndexOutOfBoundsException: while trying to load from index 0 of an object array with length 0, loaded from field com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POANameHasher.poaID_ of an object loaded from local variable 'this' |83C2FBC915A84D5AB135F16FEE7635022|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POANameHasher.<init>(POANameHasher.java:48) |83C2FBC915A84D5AB135F16FEE7635023|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POALocator.locate(POALocator.java:66) |83C2FBC915A84D5AB135F16FEE7635024|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POAManager_impl._OB_locatePOA(POAManager_impl.java:709) |83C2FBC915A84D5AB135F16FEE7635025|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POAOAInterface_impl.createUpcall(POAOAInterface_impl.java:119) |83C2FBC915A84D5AB135F16FEE7635026|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorker.executeRequest(GIOPServerWorker.java:569) |83C2FBC915A84D5AB135F16FEE7635027|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorker.execute(GIOPServerWorker.java:439) |83C2FBC915A84D5AB135F16FEE7635028|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorkerThreaded.receiverRun(GIOPServerWorkerThreaded.java:456) |83C2FBC915A84D5AB135F16FEE7635029|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorkerThreaded$ReceiverThread.run(GIOPServerWorkerThreaded.java:129) |83C2FBC915A84D5AB135F16FEE763502a|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||Exception in thread "ORBacus:Server:ReceiverThread" com.crystaldecisions.thirdparty.com.ooc.OB.AssertionFailed: ORBacus encountered an internal error |83C2FBC915A84D5AB135F16FEE763502b|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.Assert.assertTrue(Assert.java:42) |83C2FBC915A84D5AB135F16FEE763502c|2017 04 26 12:07:49.856|+0500|Error| |>>|E| |wacs_BISSBOP.WebApplicationContainerServer| 5416| 42|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorkerThreaded$ReceiverThread.run(GIOPServerWorkerThreaded.java:134) |A0ECF496B61F439F8AA38F23BA5A1D330|2017 04 26 12:08:04.981|+0500|Error| |==|E| |wacs_BISSBOP.WebApplicationContainerServer| 1692| 22|ManagedService Update Queue| ||||||||||||||||||||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

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

Former Member — Mon, 25 Sep 2017 12:27:22 GMT

Hi,

have resolved this issue? We have exact the same trouble on aix. Thank you much.

David M.

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

denis_konovalov — Mon, 25 Sep 2017 13:40:58 GMT

image 1 shows that you're connecting to something that runs on port 8443, second picture shows that you're connecting to tomcat.
So your issue is either you have tomcat with enabled connector on port 8443 and it conflicts with port 8443 you setup for WACS, or you do not have CMC and Bilaunchpad deployed to WACS.

What options have you selected during install in respect to webapp and wacs deployment options ?

As to your question about "Can you please elaborate "WACS is not running on same ports as tomcat"? How do check that?" - you looks into tomcat and wacs configurations to see which ports are enabled, and you check netmon to see which ports are shown as being listening.

Question Re: Unable to connect CMC & BI Launchpad through HTTPS Connection in Technology Q&A

Unable to connect CMC & BI Launchpad through HTTPS Connection

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection

Re: Unable to connect CMC & BI Launchpad through HTTPS Connection