During installation, the CMS and the WCS are set up to use default port numbers. The default CMS port number is 6400, and the default WCS port number is 6401. These ports fall within the range of ports reserved by Crystal Decisions, Inc. (6400 to 6410). Thus, Crystal Enterprise communication on these ports should not conflict with third
The Web Component Adapter (which replaces the WCS on UNIX, and on Windows installations of Crystal Enterprise that use the Java SDK) is not a server. However, you can configure its listening port by changing the connection.listeningPort
context parameter in web.xml
. (See Configuring the Web Component Adapter for details.)
When started and enabled, each of the other Crystal Enterprise servers dynamically binds to an available port (higher than 1024), registers with this port on the CMS, and then listens for Crystal Enterprise requests. If necessary, you can instruct each server component to listen on a specific port (rather than dynamically selecting any available port). Also, when the WCS receives a request from the Web Connector (on port 6401, by default), the WCS dynamically selects a second port for all subsequent communication. You will likely need to specify this second WCS port explicitly (with
) if you are working with firewalls. (For more information on working with firewalls see Working with Firewalls.)
On Windows, you view and modify server command lines with the CCM. The Command field appears on each server's Properties tab. On UNIX, you view and modify server command lines (also referred to as launch strings) in the ccm.config
file, which is installed in the crystal
directory.
This table summarizes the command
Before modifying any port numbers, consider the following:
-n s
option in every other server's command line, to ensure that each server connects to the appropriate port of the CMS. (The -n s
option stands for "nameserver." The CMS functions as the nameserver in Crystal Enterprise, because it maintains a list that includes the host name and port number of each server that is started, enabled, and thus available to accept Crystal Enterprise requests.) If you are using the WCA (as you will if you have a UNIX installation of Crystal Enterprise, or a Windows installation that uses the Java SDK), you must also set the name and port number of the CMS with the connection.cms
context parameter in web.xml
. See Configuring the Web Component Adapter for details.
-p ort
interface:number for the WCS or CMS and -p ort
interface for the other servers. For details, see Configuring Crystal Enterprise on a multihomed machine or Configuring for Network Address Translation.
-p ort
option. For server's other than the CMS and the WCS, this default port is not actually in use (each server registers its -r equestPort
number with the CMS instead).
Replace number with the port that you want the CMS to listen on. (The default port is 6400.)
Replace hostname with the host name of the machine that is running the CMS. The host name must resolve to a valid IP address within your network. Replace number with the port that the CMS is listening on.
The CMS begins listening on the port specified by number, and the non
If you are using the WCA (as you will if you have a UNIX installation of Crystal Enterprise, or a Windows installation that uses the Java SDK), you must also set the name and port number of the CMS with the connection.cms
context parameter in web.xml
. See Configuring the Web Component Adapter for details.
Replace number with the port that you want the WCS to listen on. (The default port is 6401.)
Replace number with the port that you want the server to listen on.
The server binds to the new port specified by number. It then registers with the CMS and begins listening for Crystal Enterprise requests on the new port.
By default, each server registers itself with the CMS by IP address, rather than by name. This typically provides the most reliable behavior. If you need each server to register with the CMS by fully qualified domain name instead, use the
option in conjunction with
interface (where interface is the server's fully qualified domain name). Having the servers register by name can be useful if a NAT firewall resides between the server and the CMS. For more information, see Configuring for Network Address Translation.
You may also need to specify
interface
when Crystal Enterprise is running on a multihomed machine.
Crystal Decisions http://www.crystaldecisions.com/ Support services http://support.crystaldecisions.com/ |