It is not the intention at this stage in the book to investigate how BusinessObjects Enterprise can be configured to work with proxy servers in any great detail. This is covered in some depth in the Administrator's guide that accompanies BusinessObjects Enterprise. However, some sample Socks configurations will be shown and there will be a brief discussion as to how BusinessObjects Enterprise would operate effectively with each configuration. Socks settings for each of the BusinessObjects Enterprise servers are defined using the Crystal Configuration Manager (through the Connection tab). SocksThe WC and WCSFigure 36.9 illustrates the operation of Socks between the WC and the WCS. Figure 36.9. Socks configurationWC to WCS.
Given this scenario, the Socks setting through the Crystal Configuration Manager should be the following:
Access control rules on the Socks server should be set to something similar to that shown in Table 36.5.
There are a couple of points worth noting:
Firewall Configuration: SocksWCS and CMSFigure 36.10 illustrates the operation of Socks between the WCS and the CMS. Figure 36.10. Socks configurationWCS to CMS.
In this instance, the Socks setting at Crystal Configuration manager should be the following:
Access control rules on the Socks server should be set to something similar to that shown in Table 36.6.
Please note that when WCS makes the initial connection to CMS on port 6400, it will pass the host name to the Socks server. Thus, the Socks server must resolve the CMS hostname. SocksMultiple BusinessObjects Enterprise ServersFigure 36.11 illustrates the operation of Socks between multiple servers in the BusinessObjects Enterprise environment. Figure 36.11. Socks configurationmultiple servers.
When multiple Socks servers are deployed in the network, the BusinessObjects Enterprise Socks setup can facilitate the traversal of them. However, due care and attention should be taken in how the Socks servers are placed and traversed. In general, the BusinessObjects Enterprise servers see these Socks servers as a chain, and the setup in the Crystal Console Manager should specify how to traverse them from the outermost to the innermost link. In this instance, the Socks setting at Crystal Configuration Manager should be the following:
Access control rules on the Socks server should be set to something similar to that shown in Table 36.7.
The point to note is that in the IOR for the CMS, the Socks server chain B-A is embedded. However, because the WCS has been configured with a local Socks server B, the program will do a comparison of these two Socks server lists and deduce that WCS only needs to go through A to reach the CMS. |