Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Engine Reference  
  Search  |  Index  
Concepts
  About attachments
  About the Component Integrator
  About launching a workflow
  About milestones
  About operations
About the RMI registry
About rosters
About routing
About rules
  About security
  About security queues
  About step processors
  About step states
  About system maps
  About transfer
  About workflow fields
  About workflow maps
  About workflow participants
  Component queue security issues
  Content Engine (CE) operations
  Coordinate information
  Custom web applications
  Eliminating port 32771 conflicts
  Java Runtime Environment (JRE)
  Maximum index key size
  Naming conventions
  System fields
  Troubleshooting
  Wildcards
  Workflow database field size limitations
  Workflow exceptions
Events & Statistics
Expressions
Procedures
   

About the RMI registry

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:

  • PPM
  • Process Router
  • Process Simulator
  • Component Manager
  • Process Analyzer

Process Engine 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 the PPM, the Process Router, and the Process Simulator. It is not necessary to run the PPM and the Process Router on the same port. For details on specifying PPM, Process Router, and Process Simulatorports at startup, see the online help for Process Task Manager or Process Service Administrator.

NOTE On Solaris-based systems, you must take additional steps in order to use port 32771. See Eliminating port 32771 conflicts for instructions.

CAUTION RMI requests to a server with an underscore (_) in the DNS name fail due to a limitation in JRE 1.4 and greater. If your server has a name containing an underscore, you must use the IP address or localhost if appropriate.

Under certain circumstances, your FileNet support representative might ask you to look at the RMI registry log file. For further information about this file, see RMI registry log.

For published information about the RMI registry or reserved ports, see the information available at:

http://java.sun.com/products/jdk/1.2/docs/guide/rmi
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1340.html