Technical Blog Post
Abstract
Problems connecting TCR and Framework Manager.
Body
Problems connecting TCR and Framework Manager.
For anyone that has not come across it before Framework Manager is a Cognos modeling tool available for Windows for creating and modifying business views of data models.
It is available with the TCR install media and details about configuring are here for 3.1x :
In this case the TCR was version 2.1.1 and on Linux; so the Framework Manager was installed on a separate windows machine.
The configuration from the 2.1.1 guide had been followed
(https://www.ibm.com/support/knowledgecenter/SSH2DF_2.1.1/ttcr_configure_frameworkmgr.html)
However the error when trying to connect from Framework Manager was:
[ ERROR ] CAM-CRP-1132 An error occurred while attempting to request a
certificate from the Certificate Authority service. Unable to connect
to the Certificate Authority service. Ensure that the Content Manager
computer is configured and that the Cognos 8 services on it are
currently running. Reason: javax.net.ssl.SSLHandshakeException: Remote
host closed connection during handshake
First this Tech Note was tried:
http://www-01.ibm.com/support/docview.wss?uid=swg21605324
The details of this are:
If Framework Manager is installed on a 32 bit Windows machine, it requires the installation of the Cognos Modeling Fix (FIPS) package only if it is expected to connect a 32 bit TCR.
If Framework Manager is used with a 64bit TCR, FIPS is not needed.
If you installed FIPS on the Framework Manager, error CAM-CRP-1132 can occur if connecting a 64 bit TCR environment.
Resolving the problem
If you need to use Framework Manager with a 64bit TCR and you have already installed FIPS, proceed as follow :
1) perform a full uninstall of the Framework Manager from the Windows machine
2) reinstall Framework Manager from scratch
3) DO NOT INSTALL Cognos Modeling Fix (FIPS) package
4) verify that Framework Manager is now able to talk with TCR as expected.
In this case Framework Manager had indeed been installed with the FIPS package on a 64 bit TCR.
On 2.1.1 the bitness can be checked with either:
TCR bitness (TCR 2.1.1 only):
- Check the value of the TCR_BITNESS parameter in the <TIP_HOME>/tipv2Components/TCRComponent/integration/properties/tcr.properties file
OR
- Run the following script: <TIP_HOME>/tipv2/profiles/TIPProfile/bin/tipBitnessMode.[bat|sh]
However even after an uninstall and reinstall the error message was still the same.
The TCR cogstartup.xml file from the TCR configuration was then reviewed.
In this file it was found that localhost was being used in some of the URI definitions, specifically the URI 's for gateway and external connections.
These were changed to be the fully qualified domain name of the machine TCR was installed on, and then TCR was restarted.
The connections configured on the Framework Manager side were checked to make sure the port numbers were correct, and then the connection was successful between Framework Manager and TCR.
Subscribe and follow us for all the latest information directly on your social feeds:
Check out all our other posts and updates: | |
Academy Blogs: | https://goo.gl/U7cYYY |
Academy Videos: | https://goo.gl/TLfMoF |
Academy Google+: | https://goo.gl/HnTs0w |
Academy Twitter : | https://goo.gl/HnTs0w |
UID
ibm11083807