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

Cognos multi Gateway and Dispatchers configuaration

Started by joseph123, 08 Apr 2013 07:02:25 PM

Previous topic - Next topic

joseph123

Hi


Please clarify  the following with respect to my org environemnt.

Machine1: Gateway1 and Webserver1
Machine2: Gateway2 and Webserver2
Machine3: Dispatcher1, ContentManager1
Machine4: Dispatcher2, ContentManager2


Q1) How should I configure Gateways so that users can enter http://orgname/c10 to enter to cognos portal.

Q2) How internal loadbalancing will be implemented for these Gateways.

Q3) How Dispatchers will be configured and integrated for failover purpose.

Your help will be highly appreciated.

Thanks,
Joseph

SomeClown

Quote from: joseph123 on 08 Apr 2013 07:02:25 PM
Q1) How should I configure Gateways so that users can enter http://orgname/c10 to enter to cognos portal.
Q2) How internal loadbalancing will be implemented for these Gateways.
With an external appliance (load balancer), and a DNS entry.  Cognos does neither of these natively

Quote
Q3) How Dispatchers will be configured and integrated for failover purpose.
Load balancing is native to dispatchers.  Just add all dispatchers to the configuration for each Cognos gateway

If you are going to do fail-over for Content Manager, it's a good idea to put Content Manager on dedicated boxes.  Long story short, sharing CM on a report server can cause instability and environment crashes when system is under load (load being badly written reports/badly modeled FM packages, not just traffic).  Long-running tasks can cause the secondary CM to lose the heartbeat and take over the environment, then clashing with primary when it comes back -- I've seen it happen multiple times.