Adding new dispatcher to existing environment on new server

[tel03]

HI,

I am trying to add new dispatcher(on new serverC) for our existing prod environment.

currently we installed APP and CM on  serverA and GW on another serverB.

Can you help me in steps on how to configure and install a new dispatcher server C?

thanks very much for the help

[sdf]

This was an old post but i think this will somehow give you idea.

http://www.cognoise.com/index.php?topic=14292.0

[sunosoft]

I think it would be much straightforward task. Once you finish with installation, just replicate your configuration from existing dispatcher. Add new dispatcher URL to gateway configuration. And just restart the complete environment once.

[tel03]

Thanks for reply.

Just want to confirm, after I install new dispatcher, i need to configure

Gateway URI - which points to GW server B
Content Manager URIs - which points to server A

Should I need change below things or just leave default values (localhost)
External dispatcher URI
Internal dispatcher URI
Dispatcher URI for external applications   

In GW server B, I need to add additional new dispatcher  in "Dispatcher URIs for gateway". right?

[sunosoft]

Yes, you should be ok to go with the steps which you mentioned for new dispatcher configuration.

However its better to change the values from localhost otherwise how will you identify your dispatcher server in distributed environment ?
also how other servers in distributed environment will identify your new dispatcher? You can leave local host as default in case of single server installation. You should change it if you are using distributed environment.

Change it to your server name instead of keeping as localhost.

Yeah, you will need to add this new dispatcher URL to gateway config.

[tel03]

Cool!! Thanks very much Sunosoft!! Able to configure successfully

Yes, I changed localhost to server name.

The next step is we need to route the reports (which are from same package) to the second dispatcher always for particular user group. Do you know these steps?

[sunosoft]

Great.

Go through below document for your routing question.

http://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/page510.html

[sdf]

The next step is we need to route the reports (which are from same package) to the second dispatcher always for particular user group. Do you know these steps?

I personally haven't encountered this setup.

Im thinking of having another GW setup where the first dispatcher to be set is your recently added dispatcher2. Then an external loadbalancer or configured router to handle the "particular user group" user request.

Am not 100% sure, let's wait for the experts. Would be great to be enlightened with this.

[sunosoft]

I personally haven't encountered this setup.

Im thinking of having another GW setup where the first dispatcher to be set is your recently added dispatcher2. Then an external loadbalancer or configured router to handle the "particular user group" user request.

Am not 100% sure, let's wait for the experts. Would be great to be enlightened with this.

No need of such setup. This should be achieved by advance dispatcher routing functionality available in cognos.

Below link gives steps to do the same.
http://www-01.ibm.com/support/docview.wss?uid=swg21427147

[sdf]

Good read, thanks sunosoft! ;)

[tel03]

Thanks Sunosoft for all the info and your help!!

I am testing the routing rules with the steps in the link that you provided.

For new dispatcher , I named Server group name as "Servergrprouting" and on the package I set routing name as "packagerout". I created a new user group with name Routing grp (with member me) and set the routing name as "grpuserrout".

Then I went to specify routing rules added a new rule - sequence:1; package: packagerout; Group routing set: grpuserrout; Role routing set:Any role; Server group: Servergrprouting.

When I run the report, all the reports(either in batch or interactive) are routing to second dispatcher  which is successful (with minor issues:like reports goes to pending status).

when my teammate runs the same report, it executes with second dispatcher. Ideally I thought it will throw error because he is not the member of user group Routing grp. right? or  it has to run on first dispatcher?

Can please clarify my question?

[sunosoft]

This looks like bit tricky, but I think Cognos is doing right thing.

Below is my guess from theory whatever i understood.Happy to hear any corrections from anyone on this :)

Note that routing in cognos is based on server groups. You have defined server group for one of your dispatcher, so other dispatcher in your environment is now in default server group. Matching a request against routing rule will be done by content manager, once CM finds a match for particular request it will return a specified server group to target service and your request will be executed on the dispatcher which comes under that server group. I believe in your scenario, routing rule is not matching for the request done by your team-mate whose is not a part of particular security group(which is defined in routing rule), hence this request is being passed to default server group where your dispatcher exists. So this request is executing on dispatcher1.

[tel03]

Thanks for details...you are great for all your patience and replies and sharing

yes getting tricky...small correction.. when My teammate runs it always going to dispatcher2? instead of original dispatcher1 as he is not in user group.

At the time of run no reports are running. both the dispatchers are available. Will this is reason y it always going to dispatcher2 as the load balance setting is in round robbin?