The remote development support from the Eclipse IDE relies upon Visual COBOL Development Hub running on the UNIX machine and handling all requests from the IDE for building and debugging programs. Visual COBOL Development Hub provides a UNIX daemon, the Remote Development Option (RDO) daemon, which initiates the RDO as Eclipse clients connect to it. Whichever environment is used to start the RDO daemon will be inherited for all servers and hence all build and debug sessions.
You may need to configure some aspects of the environment before you start the daemon. This is because when a build or debug session is initiated on the Development Hub from one of the Eclipse clients, the environment used will be inherited from whatever was used to start the daemon. A typical example of the kind of environment that might need to be set up would include database locations and settings for SQL access at build/run time.
To start the daemon on the default port (4075) as a background process, perform this command with superuser authority:
The daemon will now listen for any Eclipse client processes connecting to that machine on port 4075. If you want to use another port, specify another port number on the startrdodaemon command.
The daemon can also be configured to instantiate the servers on a specified port or range of ports. This is particularly relevant when you want to only open certain ports through a firewall. To do this, perform this command with superuser authority:
$COBDIR/remotedev/startrdodaemon [<port> | <low port>-<high port>]
This command will start a daemon listening on port 4999 and will use random server ports.
$COBDIR/remotedev/startrdodaemon 4080 4090-4999
This command will start a daemon listening on port 4080 and server ports will be in the range 4090 to 4999.
To stop the daemon, type the following command with superuser authority: