Cognos Load balancing with same content manager DB

[raviahuja21]

Hi Folks,

I am trying to install cognos on 2 server machines for load balancing which will be done via an external mechanism called ELB.

Machine A:All Server components (Gateway, Dispatcher)
Machine B:All Server components (Gateway, Dispatcher)

What I want to achieve is session sharing between the two instances when the external router routs the request in between interaction by the user, ideally the user should not be prompted.

What I have done is kept the Content manager DB same for both the instances because of which I am able to start machine A but when i begin to start Machine B it doesnt starts and gives me the below given error.

I have added both the content manager URI in the cognos administration in the Content manager URI section.

My question is can I have the same content manager DB for 2 instances?


Also if someone could explain how session sharing is done between 2 server instances in cognos.

CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.

10.0.0.228:9300   3792   2014-09-15 06:30:04.198   +0   BootstrapConfigurePublish   na      0   Thread-25   DISP   5003   1   Audit.Other.dispatcher.DISP.com.cognos.pogo.contentmanager.coordinator.CMBootstrap   registerInCM   https://questcognos02.quest.bi-clinical.com:9300/p2pd      Failure   <messages><message><messageString>DPR-DPR-1026 Unable to register the dispatcher in Content Manager. questcognos01.quest.bi-clinical.com:9300/p2pd/servlet at this time. Will retry periodically.</messageString></message><message><messageString>Failed to send HTTP request or read HTTP response</messageString></message></messages>   Failed to send HTTP request or read HTTP response com.cognos.pogo.bibus.CommandExecutionIOException: Failed to send HTTP request or read HTTP response    at com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:367)    at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:206)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.getRegisteredDispatchers(CMBootstrap.java:267)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.testDispatcherRegistered(CMBootstrap.java:178)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.registerDispatcher(CMBootstrap.java:137)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.run(CMBootstrap.java:88)    at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.checkRegistration(BootstrapConfigurePublish.java:84)    at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.start(BootstrapConfigurePublish.java:59)    at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.startConfiguration(RuntimeInfoPublishHandler.java:252)    at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.start(RuntimeInfoPublishHandler.java:110)    at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:88)    at com.cognos.pogo.services.DispatcherServices.startInitialService(DispatcherServices.java:418)    at com.cognos.pogo.services.DispatcherServices.startInititalServices(DispatcherServices.java:404)    at com.cognos.pogo.transport.PogoServlet$PogoStartup.run(PogoServlet.java:803)    at com.cognos.pogo.util.threads.SafeThread.safeRun(SafeThread.java:70)    at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61) Caused by: java.io.IOException: Failed to send HTTP request or read HTTP response    at com.cognos.pogo.http.ServerConnection.executeMethod(ServerConnection.java:796)    at com.cognos.pogo.http.ServerConnection.sendRequest(ServerConnection.java:252)    at com.cognos.pogo.bibus.BIBusCommand.sendRequest(BIBusCommand.java:225)    at com.cognos.pogo.bibus.BIBusCommand.executeCommand(BIBusCommand.java:214)    at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:200)    ... 14 more Caused by: java.net.ConnectException: Connection timed out: connect    at java.net.DualStackPlainSocketImpl.connect0(Native Method)    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:69)    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:358)    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:219)    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:201)    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:165)    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)    at java.net.Socket.connect(Socket.java:579)    at java.net.Socket.connect(Socket.java:528)    at java.net.Socket.<init>(Socket.java:425)    at java.net.Socket.<init>(Socket.java:280)    at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80)    at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122)    at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)    at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)    at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)    at com.cognos.pogo.http.ServerConnection.executeMethodSynchronously(ServerConnection.java:825)    at com.cognos.pogo.http.ServerConnection.executeMethod(ServerConnection.java:777)    ... 18 more
10.0.0.228:9300   3792   2014-09-15 06:30:04.198   +0   BootstrapConfigurePublish   na      0   Thread-25   DISP   5003   1   Audit.Other.dispatcher.DISP.pogo   pogo   com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish      Failure   <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>Failed to send HTTP request or read HTTP response</messageString></message></messages>   Error configuring Failed to send HTTP request or read HTTP response com.cognos.pogo.bibus.CommandExecutionIOException: Failed to send HTTP request or read HTTP response    at com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:367)    at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:206)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.getRegisteredDispatchers(CMBootstrap.java:267)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.testDispatcherRegistered(CMBootstrap.java:178)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.registerDispatcher(CMBootstrap.java:137)    at com.cognos.pogo.contentmanager.coordinator.CMBootstrap.run(CMBootstrap.java:88)    at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.checkRegistration(BootstrapConfigurePublish.java:84)    at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.start(BootstrapConfigurePublish.java:59)    at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.startConfiguration(RuntimeInfoPublishHandler.java:252)    at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.start(RuntimeInfoPublishHandler.java:110)    at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:88)    at com.cognos.pogo.services.DispatcherServices.startInitialService(DispatcherServices.java:418)    at com.cognos.pogo.services.DispatcherServices.startInititalServices(DispatcherServices.java:404)    at com.cognos.pogo.transport.PogoServlet$PogoStartup.run(PogoServlet.java:803)    at com.cognos.pogo.util.threads.SafeThread.safeRun(SafeThread.java:70)    at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61) Caused by: java.io.IOException: Failed to send HTTP request or read HTTP response    at com.cognos.pogo.http.ServerConnection.executeMethod(ServerConnection.java:796)    at com.cognos.pogo.http.ServerConnection.sendRequest(ServerConnection.java:252)    at com.cognos.pogo.bibus.BIBusCommand.sendRequest(BIBusCommand.java:225)    at com.cognos.pogo.bibus.BIBusCommand.executeCommand(BIBusCommand.java:214)    at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:200)    ... 14 more Caused by: java.net.ConnectException: Connection timed out: connect    at java.net.DualStackPlainSocketImpl.connect0(Native Method)    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:69)    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:358)    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:219)    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:201)    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:165)    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)    at java.net.Socket.connect(Socket.java:579)    at java.net.Socket.connect(Socket.java:528)    at java.net.Socket.<init>(Socket.java:425)    at java.net.Socket.<init>(Socket.java:280)    at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80)    at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122)    at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)    at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)    at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)    at com.cognos.pogo.http.ServerConnection.executeMethodSynchronously(ServerConnection.java:825)    at com.cognos.pogo.http.ServerConnection.executeMethod(ServerConnection.java:777)    ... 18 more

[edewerth]

I see HTTPS in the log file, is HTTPS setup on the servers already? If so maybe you should turn that off until you get everything setup and running.  I have a 8 server farm behind an ELB  split out for 2 gateways, 2 report servers, 2 batch report servers and 2 content managers.  I also let the ELB handle the SSL so it is offloaded prior ton hitting the gateways so that I can mange in one location and my Apache servers can run on port 80.  Can each of the servers see the other server?  Can each server talk to the database via whatever db Client?  it seems like one server is unable to see the other server so it can't register it into the content store as an active dispatcher.  Based on your ELB usage, It seems like you are running in AWS so you might want to check security groups and access between servers and database servers to make sure that everyone can talk to one another.  Also make sure that you can hit the front-end of each server outside of the ELB.  The session handling will take place at the ELB level and Cognos will send them around to where it thinks they should go depending on a myriad of things.  I'd start by getting it going first then circle back around to that.  AWS can get quite messy.....

[sdf]

Is it possible to share a common content manager between two Cognos BI server on different versions.

Cognos A, version 10.1.1
Cognos B, version 10.2.1

Is it possible for cognos B to use the content manager of cognos A?

[SomeClown]

Is it possible for cognos B to use the content manager of cognos A?

No

[edewerth]

@feds Not sure what your goal here is but if it is to keep the two environments synced with the same reports you could create a folder for people to dump any new reports of the day into then schedule an export of that folder nightly from one CS and schedule an import into the other. Then cleanup the export folder and move the imported reports the next day to the appropriate location or programmatically cleanup and move them.  They will be overwritten nightly if you don't move them.

[sdf]

yes im trying to synced the two servers so to save our selves from the steps you provided.

i tried to this but on 10.2.1, it says that after upgrading the cs (which is the cs of 10.1.1) previous version will not be able to use this.

So will just create a new instance of the same version.


Thanks anyway.