Firewall Blocking Access - Port Numbers/Ranges?

[Former Member]

In short, I need a specific, detailed list of the TCP/UDP ports (by protocol, not just a list of numbers) that are needed for the Data Services Designer client to communicate fully with the BusinessObjects Data Services server.

Our workstations are on a subnet apart from our servers and our firewall policy is very strict between them, so any answer must be very specific. I do not need information pertaining to server-to-server communications (i.e.: please don't burden the answer to this question with ports needed for SQL communications between the BusinessObjects Data Services server and the SQL Server repository, etc.). Thank you.

[scott_broadway]

Hi William,

All connections between Designer and the jobserver are via TCP.

As Werner mentioned, all Designer clients will need to be able to connect to the jobserver on its chosen listener port (default: 3500) using the hostname of the jobserver. (The Designer pulls the hostname of the jobserver from the AL_MACHINE_INFO table of the local repository it is using.)

The jobserver will then need to connect back to the Designer's listener port. This is either an arbitrary port above 1024 assigned by the operating system, or it can be locked to a specific port range under Tools - Options - Designer. So your firewall will need to allow the jobserver to connect to each Designer machine on a specific port using the IP address.

If these two connections do not work, Designer will show a Red X in the lower right corner over the jobserver icon. Your users may still be able to execute jobs if they can connect to the jobserver -- they just won't be able to see any logging messages in Designer if the jobserver cannot connect back to the Designer to send those notification messages.

The Designer clients should also have access to the Management Console port. This could be on port 8080 if you are using an external version of Tomcat, or 28080 if you are using the version of Tomcat shipped with the tool (I think the DS installer also allows you to customize the port).

Hope this helps -- let us know what errors you get.

Thanks,

~Scott

[werner_daehn]

The Designer initiates a connection to the jobserver, jobserver running under the port you specified in the server manager, typically 3500.

Then the Designer goes into a listen-mode on an arbitary port number and sends the port number to the jobserver so that it can initiate a connection back to the Designer (yes, it really creates a new session). The port range the designer is using to listen on can be restricted via the Designer -> Tools -> Options menu.

Then there is the accessserver on port 4000 if you happen to use realtime.

Adapters use more ports as well - if Adapter datastores are used at all.

Webadmin is a tomcat on port 28080 by default

And debugging is using some more ports - don't know which right now.