Forum Discussion
multiple gateways on one server
kwschere No, you would need to deploy a new gateway on a different server.
Hi kwschere,
As the on-premise gateway runs as a windows service called "PBIEgwService" on the server where it is installed, I don't think it is possible to configure more than one on-premise data gateway on the same Windows server in this scenario.:smileyhappy:
Regards
kwschere No we can't do .
My question is y u r trying to install multiple gateway in single mechine ?
One gateway is enough to connect all the source know ?
This is purely for administrative reasons. At the present time, we are purely in a discovery mode for how to use Power BI and the On-Premise Data Gateway. From what I've been able to determine, the only person that is able to create/modify/delete data sources on the gateway is one who has been given administrator priveleges on the gateway. We are hoping to decentralize the administration of the data sources - with business units managing their own data sources. Thus we don't want people from different departments having the ability to touch another department's data sources. The only way I can see to provide this setup is to create multiple gateways. I was hoping to be able to do this without creating a glut of gateway servers.
Good afternoon shill1000
Today I have an environment where I host a cloud ERP, where I have something very similar to scenario 1.
I have a server that needs to share several gateways, where each gateway will be from a different client.
Clients do not have access to this server, every configuration is performed by my team.
But we need to create 5 or gateway services on the same server. Each service will log in with a separate domain account and connect to a different database.
We have all policies for this to work accurately.
The big problem is that we can not create more than one gateway service on the same server.
Do you have any idea how to solve this?
I'm not an infrastructure specialist and without knowing how your environment is set up I'm not going to venture a guess as to a specific solution. All I'd point out is that a gateway offers access to a data source on the same network as the gateway to anyone with access (and crdentials) to the gateway. If the gateway can comunicate with the data and the user can communicate with the gateway (and thus the data) then the gateway should work for you. If the gateway cannot see the data, then it needs to be set up on the network where the data resides, but the gateway itself must also still be available to the report creator. If your data is on separate domains, unless you have a method of bridging those domains so the gateway and user can see the data, then I don't think it will work. Likewise, the number of sources on one network isn't that big an issue for the gateway as long as you don't go daft with the number (not sure I can imagine an environment where a gateway has to access more than 5-10 sources on one network).
You don't have to use a new server for every single gateway, you don't even need to use a server. Depending on volume of data etc. you can install a gateway on any server, desktop or laptop, as long as it is always on. If each department has servers for their day to day use and some of these are under utilised, consider whether installing the gateway on these would impact perfromance of the server or the gateway. If you can stick a desktop in situ without risking it being turned off etc. and the data volume isn't too great for it to handle, it may be a cheap and simplem soluiton or at least a stop gap.
