Kbase P21900: How to set up Actuate with firewalls.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/25/2003 |
|
Status: Unverified
GOAL:
How to set up Actuate with firewalls.
GOAL:
Not wanting to use the HTTP client.
FIX:
The following information was obtained from the Actuate KBase.
SUBJECT:
What settings need to be specified for ports to make it work through a firewall?
DESCRIPTION:
QUESTION:
How can Actuate software be configured to work across a firewall.
SOLUTION:
For working through a firewall, both the report server and the client outside the firewall must be configured.
The case study below demonstrates how to deploy the Actuate Administrator desktop outside the firewall. The same settings apply for the Developer Workbench, ERD, ERDPRO, Report Cast. The base numbers and the ranges can be changed to suite the deployment.
ADT -------------------- Firewall -------------------------- Report Server
(Traffic going from ADT to RS is called Traffic in)
(Traffic going from RS to ADT is called Traffic out)
The following settings must be introduced on the report server machine as either registry keys or environment variables:
Report Server:
AC_SERVER_RPC_SOCKET_BASE 7401
AC_SERVER_RPC_SOCKET_COUNT 100 ( use ports 7401 - 7500)
AC_SERVER_REPLY_SOCKET_BASE 7501
AC_SERVER_REPLY_SOCKET_COUNT 100 (user ports 7501 - 7600)
AC_SERVER_SOCKET_BASE 7601
AC_SERVER_SOCKET_COUNT 100 (use ports 7601 - 7700)
AC_VIEW_SERVER_SOCKET_BASE 7701
AC_VIEW_SERVER_SOCKET_COUNT 100 (use ports 7701-7800)
ADT Machine:
AC_SERVER_SOCKET_BASE 7601
AC_SERVER_SOCKET_COUNT 100
Please note that the AC_SERVER_SOCKET_BASE / COUNT ports MUST match on both machines.
On the firewall, the rules should be setup so that the following traffic is allowed:
Ports for: Traffic In Traffic Out
AC_SERVER_RPC_SOCKET * TCP/RPC
AC_SERVER_REPLY_SOCKET * TCP/RPC/UDP
AC_SERVER_SOCKET * TCP/RPC TCP/RPC
AC_VIEW_SERVER_SOCKET* TCP/RPC TCP/RPC
PORTMAPPER (111) TCP/RPC