RSCM Server Processes
The first process is iCDBNetLauncher. The RSCM Server runs only one instance of this process. The process runs continuously as a service on Windows and as a daemon on Linux/UNIX. The iCDBNetLauncher process listens for clients to request access to a project. When it receives a client request to open a project, the RSCM Server launches the second process to open the project and support concurrent design.
The second process that the RSCM Server runs is iCDBNetServer. Each open project that points to the RSCM Server gets its own iCDBNetServer process. The iCDBNetServer manages the client access to the data.
The iCDBNetLauncher requires minimal network resources. It simply manages iCDBNetServer processes. The iCDBNetServer processes, however, may demand significant system resources depending on the size of your project.
An RSCM Server can run up to 100 iCDBNetServers in the default configuration, but this number is actually limited by the available system resources. If your system lacks capacity, you should plan for your RSCM Server to support fewer iCDBNetServers. See Network and Hardware Recommendations.
See the topic RSCM Server Port Usage for more information on how the RSCM Server processes interact with clients on ports.
Example
The following example shows how the RSCM Server processes work in a typical concurrent design environment.
RSCM Server Processes:
iCDBNetLauncher runs continuously as a service or daemon.
A separate iCDBNetServer process runs for each open project that points to the RSCM Server.
File Server Contents:
Project 1 Data
Project 2 Data