Each command-line tool has its own start file with the ending
".jpif", which is executed on startup. The name of this
file corresponds to the name used for starting the application with the cm/
command (for example cm runlevel uses runlevel.jpif). You'll
find these files in the <COREM_HOME>/bin directory.
The JPIF files for applications determine which Java class should be executed on starting the application. Further settings for the operation of the application can also be stored in this file. This file can be used to modify the Java Virtual Machine (JVM) where the application runs, while parameters can be passed to the JVM.
The following CoreMedia relevant modifications can be configured for the Java Virtual
Machine in the JAVA_VM_ARGS section of the JPIF file:
The memory usage within the Java Virtual Machine can be configured using the
parameters -Xms<size> and -Xmx<size>.
-Xms specifies the initial object memory size and -Xmx the
maximum object memory size. The memory requirement for the applications is preconfigured
and depends on the main memory size according to the standard hardware recommendations,
but can be increased using this parameter if necessary.
The ORB can be configured to use a fixed CORBA port using the parameter
com.sun.CORBA.ORBServerPort as described in
Section 4.2, “Communication between the System Applications”.
Furthermore, the target of the log outputs of the Java process (see
Section 4.7, “Logging”) can be configured with the parameter
OUTPUT_REDIRECT.
Three JPIF files cannot be invoked directly with the cm command. They are
executed internally:
pre-config.jpiffor installation depending settings. In this file, the parameterVERBOSEcan be set tofalseto reduce JVM outputs. On a Unix system, the JVM to use is set in this file.module.jpiffor general environment settings for the Java programs in the CoreMedia system.post-config.jpiffor special CoreMedia JVM settings.
In general, these files need not be changed.
 |  |  |
 |