TIBCO Enterprise Message Service installations on 64-bit platforms usually include both 32-bit and 64-bit versions of the EMS server and multicast daemons. All daemons are installed in the
EMS_HOME/bin directory, and you may use either or both versions. There is no difference between the two versions other than the processing speed.
Table 5 shows the names given to each daemon version. Note that on a few 64-bit systems,
only the 64-bit version is provided. In such cases, the 64-bit daemons use the standard daemon name. This is the case, for example, on all 64-bit Windows systems.
Throughout the TIBCO Enterprise Message Service documentation, the EMS daemons are refered to by their standard daemon names. For example, server daemon is referred to as
tibemsd. The descriptions and instructions apply to both daemon 32-bit and 64-bit versions.
If TIBCO Enterprise Message Service is installed and the tibemsd is started as root, it drops root permissions after the server starts. This protects the EMS server from security exploits. Once the server has dropped root privileges, it cannot write to the files created during the installation. As a result, it is not able to create configuration and log files. To avoid this conflict, create the necessary directories and assign the appropriate privileges to the regular user ID with which the EMS server is started.
In order to install TIBCO Enterprise Message Service on Mac Intel systems, JDK version 1.7 must be pre-installed and included in the
PATH environment variable. JDK 1.7 must be installed on the target host machine when installing the
macosx_x86.tar.gz package. You will not be able to complete the EMS installation if an earlier version of the JDK is installed.
In order to load the IBM JVM on AIX, you must set module_path in the
tibemsd.conf to point to the directory containing the
libjvm.so and its dependent libraries. These libraries are part of your JRE installation.
The EMS server dynamically loads the SSL and compression shared libraries, rather than statically linking them. If the
tibemsd executable is executed from the
bin directory, it automatically locates these libraries. If the server is moved elsewhere, the shared library directory must be moved as well.