Java options must be put in the isserver.vmoptions file, located in the isCOBOL bin directory, which is the default directory of the service. In this file comments are prefixed by a hash and each option is on a separate line.

The following snippet shows how to configure memory limits, pass a custom configuration file and alter the Classpath for the isCOBOL Server service. It also shows how to enable and disable specific functionalities using the corresponding isCOBOL property (in this case we enable Application Server and File Server and we disable HTTP Server and IDE’s remote project handling):

The isCOBOL Server service inherits the Classpath from the system and adds all jar libraries in the isCOBOL lib directory to it. Using the -classpath option you can add additional items to the active Classpath. The value of -classpath/p is prepended to the active Classpath. The value of -classpath/a is appended to the active Classpath.

Note: On some Windows distributions it’s necessary to reboot the system in order to make services aware of modifications to the system environment.

isCOBOL configuration properties to configure port number, hostname, rundebug, etcetera, can be set either in isserver.vmoptions with the syntax “-Dproperty=value” or in a file named iscobol.properties that will be loaded from:

In order to manage multiple services on the same machine, the sc command must be used instead of the isserver command.

In this example we show how to start two isCOBOL Server services listening on different ports on the same machine.

server2.properties:

Note - the two snippets above shows the basic configuration, they should be completed with the rest of settings that usually appear in a isCOBOL runtime configuration. We notice that different ports for each isCOBOL Server feature are referenced in the two configuration files.