Task C: Start the Manager

Start the Manager according to instructions in the Windows or UNIX section that follows.

Windows

Start the Windows Manager by running the server.bat file, located in the DS_MANAGER directory of the GridServer distribution. To test, open a command window and run server.bat run to launch the Manager and start GridServer. The command window contains log messages from the application server.

The server.bat script takes the following arguments:

Argument	Description
start	Start the Manager. The first time this runs, it copies volatile files into the data directory.
prepare	Copy volatile files into the data directory without running the server.

The Manager is typically run as a Windows Service in production systems. To do so, open a command window as administrator and run service.bat with the following arguments:

Argument	Description
install	Install the Manager as a Windows service.
remove	Remove the Manager’s service.
start	Start the installed service.
stop	Stop the service.
--user username password	Can be specified to use a Windows service as another user. For example, to install as user jsmith with password test123: service.bat install --user jsmith test123

For initial installation, install the Manager as a Windows service, then start the service.

UNIX

Launch the Manager by invoking the server.sh script, located in the DS_MANAGER directory of the GridServer distribution, with the following arguments:

Argument	Description
run	Start the Manager in the foreground. The first time this runs, it copies volatile files into the data directory.
prepare	Copy volatile files into the data directory without running the server.
start	Start the Manager in the background.
stop	Stop the Manager running in the background

You can configure the Manager to launch automatically at system startup and stop cleanly at shutdown. Since the server.sh script conforms to the standard start/stop argument convention (“rc script”), you can accomplish this simply by linking to the appropriate files in the /etc/rc.d directories. For more information about initialization and termination scripts, refer to the init and init.d man pages on your UNIX system and see A Sample UNIX rc.d Script

Note

When installing the Manager on cloud (AWS), you might have to perform a few additional actions to improve the performance of your system. If you are likely to launch a large number of Engines simultaneously, you must apply AWS auto-scaling concepts. Engine installation steps are the same as those described earlier. You can then perform the following steps: 1. Set JAVA_HOME to the latest version of JAVA being used by GridServer. 2. Run the following commands to set machine-level properties such as maxThreads: sudo ulimit -c unlimited sudo sysctl -w net.core.somaxconn=1024 sudo sysctl -w net.core.netdev_max_backlog=5000 sudo sysctl -w net.ipv4.tcp_max_syn_backlog=5000 sudo sysctl -w fs.file-max=100000 3. In the GridServer Administration Tool, navigate to Broker > Broker config and change the maximum number of Engines as per your requirement. 4. Go to DS_DATA/conf/ and update the server.xml file. Change maxThreads and acceptCount as per your requirement. In the following example, we have set the value of acceptCount and maxConnections as 500: <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" acceptCount="500" maxConnections="500"/> After the above changes, you must restart the Manager. The above steps might vary for other cloud service providers such as Azure or GCP.