If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Installing Cognos Gateway on Linux server using CHROOT

Started by cwillard, 06 Dec 2013 08:02:09 AM

Previous topic - Next topic

cwillard

I am looking for information on installing the Cognos gateway on a Linux server using CHROOT.  We have setup CHROOT, copied all the directories from the server root into the CHROOT, and then installed Cognos.  We are also running Apache from within the CHROOT, have installed Java in it and have updated the JAVA_HOME, LD_LIBRARY_PATH and PATH variables to point to the correct locations in CHROOT.  When we run the cogconfig.sh -s command and it appears to complete correctly but then we find the following error message in the log,

1     ERROR [main] - LogIPFControl::initCAMCrypto() - Cannot create CAM signing session.
CAM-CRP-1114 Unable to find the Certificate Authority self-signed certificate with alias 'ca' in the keystore '/chroot/httpd/etc/httpd/cognos_gateway/configuration/signkeypair/jCAKeystore'.
   at com.cognos.accman.jcam.crypto.misc.KeyStoreReader.getCACertificate(KeyStoreReader.java:590)
   at com.cognos.accman.jcam.crypto.misc.Configuration.isCAKeyPairValid(Configuration.java:1442)
   at com.cognos.accman.jcam.crypto.CAMFactory.initialize(CAMFactory.java:155)
   at com.cognos.indications.LogIPFControl.initCAMCrypto(LogIPFControl.java:526)
   at com.cognos.indications.LogIPFControl.initialize(LogIPFControl.java:147)
   at com.cognos.crconfig.CRConfigConsole.begin(CRConfigConsole.java:68)
   at CRConfig.main(CRConfig.java:201)
2     WARN  [main] - LogIPFControl::initialize() - initCAMCrypto() failed, return false.

When we try to access the assigned URL with get the Cognos Splash screen followed an error message saying it can not connect to the content manager.  We have tested the install outside of CHROOT, and on a different server and it works correctly.

Any information on what we need to do different when using CHROOT would be appreciated.

MFGF

Hmmm. That looks like a whole lot of unix mumbo-jumbo to me :)

I may be barking up the wrong tree but the error you are seeing looks like the cryptographic keys have not been copied across to the gateway. If you look in the c10/configuration directory created within CHROOT do you see signkeypair, encryptkeypair and csk subdirectories? What happens if you copy these over manually from the server hosting the content manager? Does it fix the issue?

Apologies if this is complete nonsense - I forgot how to spell uinx fifteen years ago :)

MF.
Meep!