Limit dispatcher to 1 core or processor

[jbertrand]

Hi there. Does anyone know if it is possible to limit a dispatcher to 1 core? I have a single server available, and it needs to house named users and information distribution licenses (PVU). Obviously it would have been better to have 2 servers (blame it on the sales guys), but alas that is not the case, I only have 1. So I need to limit a second dispatcher to a single core for the information distribution license. Surely there are some deeply buried parameters to accomplish this? (rsvpproperties.xml, tomcat etc?). I know how to set up the routing rules, just looking to tie down the dispatcher.

Thanks.

John

[MFGF]

Hi there. Does anyone know if it is possible to limit a dispatcher to 1 core? I have a single server available, and it needs to house named users and information distribution licenses (PVU). Obviously it would have been better to have 2 servers (blame it on the sales guys), but alas that is not the case, I only have 1. So I need to limit a second dispatcher to a single core for the information distribution license. Surely there are some deeply buried parameters to accomplish this? (rsvpproperties.xml, tomcat etc?). I know how to set up the routing rules, just looking to tie down the dispatcher.

Thanks.

John

Hi,

You can't tie a Cognos instance to a specific cpu or core on the server it is installed on. To comply with your PVU license, you will need either a server with a single 1-core cpu (which is an impossible task these days) or you will need to set up a virtual machine that utilises one core of the physical server, and install Cognos in the virtual machine.

Cheers!

MF.

[Yunus]

Your entitlements from IBM should have a detailed license agreement and you can see your options for visualization in the agreement.  You can also see in that agreement that things like "set affinity" for Windows to limit the process are not supported in the PVU license, at least not mine.