3.1Startup behavior configuration
Installing cmsWorks is pretty simple but a little bit of knowledge is necessary:
- You need to have a login/access to the machine on which you want to install cmsWorks at (i.e. to transfer files to or start cmsWorks from the command prompt).
- This server machine needs a Java JVM already installed.
- In best cases, at least for a productive system, a database server (MySQL) needs to be installed and a newly created (empty) database is needed.
Startup behaviour then is relying on three base mechanisms and tests:
- When starting the cmsWorks server software, a cmsWorks batch called "startup.batch" will be executed, all your services will be fired up by this batch (or an included batch within the startup.batch).
- cmsWorks will automatically test the compiled Java classes if there is something missing or not, please refer to the "exception.log" file (in the starting folder), if cmsWorks did not start up correctly or, rather, exits the startup with an error.
- In case everything worked out fine, login to the cmsWorks desktop and open up the cmsWorks-Explorer to preview any previously entered page.
The startup behaviour of cmsWorks depends on the startup of the Java Virtual Machine. In practice, you have to configure the memory settings so that cmsWorks can complete it's jobs.
Memory settings of the Java Virtual Machine
The memory settings of the virtual machine may be altered. Therefore, the two entries -Xms**M and -Xmx**M have to be set (in the cmsworks.sh or cmsworks.bat scripts) to a value corresponding to the later needed use of the overall memory usage.
The memory setting is one of the few settings that cannot be altered when the virtual machine is running. Altering these values requires a restart of cmsWorks.
How to set these values to get the best performance from cmsWorks will be discussed in chapter Optimization by using the JVM.
startup.batch
The batch file "startup.batch" is the first cmsWorks-batch-file loaded and executed when the server starts. It defines the order and count of the services that will be started. In case an other startup behaviour is intended, the startup batch may be modified or extended with telnet server commands.