Post Installation Tasks : Check and Update Properties Files

Check and Update Properties Files
Check the engine properties file to ensure that all settings are appropriate for your platform.
Enable Remote Connection to RMS from BusinessEvents Decision Manager
As shipped, the tibco.clientVar.RMS/hostname property is set to localhost. This setting enables the product to be used in non-production settings. For production settings take the following actions to ensure remote connectivity.
To Enable Remote Connection to RMS from BusinessEvents Decision Manager
1.
Open the BE_HOME/rms/bin/be-rms.tra file.
2.
   tibco.clientVar.RMS/hostname=localhost
3.
Set the rms.host property in the BE_HOME/DecisionManager/configuration/bui-config.tra file to use the same hostname and port. (This sets the default value. Users can also specify different values to connect to another server.)
As well as the hostname properties, also set the respective port properties as needed.
Update JVM Settings
Set the Heap Size as Needed
By default, the initial (–Xms) and maximum (–Xmx) heap size are set to 1GB for both BusinessEvents and BusinessEvents Decision Manager. Change the settings as needed to meet your requirements. For BusinessEvents, the settings are in the BE_HOME/bin/be-engine.tra file. For BusinessEvents Decision Manager they are in the BE_HOME/decisionmanager/DecisionManager.ini file.
For example, if you want to run both BusinessEvents Decision Manager and BusinessEvents on a machine with 1GB memory, you might reduce the initial heap size setting (–Xms):
java.extended.properties=-server –Xms512m -Xmx1024m
Alternatively, you could increase the machine’s memory.
As another example, if you use a machine with more memory, and you work with very large tables in BusinessEvents Decision Manager, you might increase the BusinessEvents Decision Manager heap size accordingly.
It can also be helpful to set the MaxPermSize as follows:
-XX:MaxPermSize=128m
Platform-Specific Settings
Some of the JVM settings do not work for all platforms, and some platforms use additional, platform-specific parameters.
For example, for AMD on Windows and 32 bit Sun JVM for Intel use:
JVM_LIB_PATH =%TIB_JAVA_HOME%/lib/i386/server/libjvm.dll
The IBM AIX platform uses parameters common to all JVMs, but does not use the -d64 parameter. AIX also uses additional parameters (using the format, -Xparameter).
Refer to the appropriate JVM reference manuals for the platform in question. For example, for AIX you could refer to the following resources.
http://www.ibm.com/developerworks/java/jdk/aix/j564/sdkguide.aix64.html
http://www.ibm.com/developerworks/java/jdk/aix/j532/sdkguide.aix32.html
Note that you can determine the version installed and other information using the following simple Java program:
System.getProperty("com.ibm.vm.bitmode");
The system property com.ibm.vm.bitmode enables applications to determine the mode in which JVM is running. It returns the following values:
* 32 - the JVM is running in 32-bit mode
* 64 - the JVM is running in 64-bit mode