Several FileNet processes require the Remote Method Invocation (RMI) mechanism built into the Java™ environment. The client and server components communicate via RMI, which is an RPC mechanism designed for and built into the Java language. The processes using RMI are:
Process Engine (PE) Java objects are automatically registered in the RMI registry. Communication between an RMI object and RMI clients occurs via the RMI registry for the port with which the RMI object is registered. An RMI object binds itself to the RMI registry; the RMI registry then routes requests coming to and going from that RMI object appropriately through the system.
By default, processes that communicate via RMI run on port 32771. Generally, there is no need to change the default port unless you are working around a conflict with another software package that requires port 32771. You can specify a different port when starting PS. For details on specifying PS ports at startup, see Process Simulator general properties.
NOTE On Sun Solaris-based systems, you must take additional steps in order to use port 32771. See "To enable ports" in IBM FileNet P8 Platform Installation and Upgrade for instructions.
CAUTION RMI requests to a server with an underscore (_) in the DNS name fail due to a limitation in Java Runtime Environment (JRE) 1.4 and greater. If your server has a name containing an underscore, you must use the IP address or localhost if appropriate.
For published information about the RMI registry or reserved ports, see the information available at http://java.sun.com/products/jdk/rmi/.