![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Install the EMS software release, which automatically includes the EMS jar files in the EMS_HOME/lib subdirectory.
•
All jar files listed in this section are located in the lib subdirectory of the TIBCO Enterprise Message Service installation directory.To use Entrust with an EMS client, you must separately purchase and install the Entrust libraries. If you use the Entrust libraries, you must include them in the CLASSPATH before the JSSE JAR files. To use Entrust with JDK, you must download the unlimited strength policy JAR files from Sun's website and install them in your local installation of JDK. For installation and configuration details, see Entrust documentation.See Security Considerations for a complete discussion of what is needed for a secure deployment.generates a MyApp.class file.Developers of EMS C programs can use this checklist during the five phases of the development cycle.
•
• Add EMS_HOME/include to the include path. (OpenVMS environments do not require an include path; skip this item.)
• Include the tibems.h header file:
• Programs that use the C administration API must also include the emsadmin.h header file:
• Programs that use the unshared state failover API must also include the tibufo.h header file:
• Call tibems_Open() to initialize the EMS C API and tibems_Close() to deallocate the memory used by EMS when complete.See the samples/c/readme file for details.
• UNIX If you use dynamic EMS libraries on a UNIX platform, the environment variable $LD_LIBARY_PATH must include the EMS_HOME/lib directory (which contains the shared library files). (On some UNIX platforms, this variable is called $SHLIB_PATH or $SYLIB_LIBRARY_PATH).
•
• OpenVMS The installation procedure automatically installs the shareable images required for using EMS dynamic libraries.
• All Platforms The application must be able to connect to a EMS server process (tibemsd).
•
Table 58 Linker Flags for 32-Bit UNIX To use 64-bit libraries, you must include TIBCO_HOME/ems/8.1/lib/64 in your library path, and it must precede any other EMS directory in the library path.
Table 59 Linker Flags for 64-Bit UNIX For a list of Windows platforms that Release 8.1 supports, see the file readme.txt in the installation directory. Both DLLs and static libraries are available. We recommend DLLs to ease forward migration.
With dynamic libraries (DLLs), use the /MT compiler option.
With static libraries (DLLs), use the /MD compiler option.
Table 63 Static Library Files for OpenVMS
• Install the EMS software release, which automatically includes the EMS assembly DLLs in the EMS_HOME\bin subdirectory.
Table 64 EMS Assembly DLL .NET Unshared State API
• To automatically upgrade to the latest .NET assemblies, include the appropriate policy file in the global cache. See Automatic Upgrades Between Versions for more information.Assembly VersioningTIBCO Enterprise Message Service assembly DLLs are versioned using the format 1.0.release.version, where release is the EMS release number and version is an arbitrary value. For example, the assembly version number for software release 8.0.0 is similar to 1.0.800.8.
Applications that use a release of EMS earlier than 6.0 do not use standard .NET versioning. Prior to TIBCO Enterprise Message Service release 6.0.0, all EMS .NET assemblies showed an assembly version number 1.0.0.0, which allowed client applications to upgrade to the latest version of EMS without rebuilding.This functionality is now available through the policy DLL files.
• A policy.1.0.assembly file. For example, policy.1.0.TIBCO.EMS.dll. The policy file must be included in the global cache to enable automatic upgrades.
• An assembly.config file. For example, TIBCO.EMS.dll.config. The configuration file must be present when the related policy file is added to the global cache.Table 65 shows the policy and configuration files for each EMS assembly.
Table 65 EMS Policy Files .NET Unshared State API If you do not want your older applications to automatically move to the newer version, do not include the policy DLL in the global cache. When the policy.1.0.assembly file is absent, the client application is not upgraded.
1. Build clients using the different .NET client assemblies.
2. Include all desired versions of the .NET client assemblies in the global cache.
3. Note that compression, SSL, and the LDAP lookup of administered objects features are available only with Microsoft .NET Framework 2.0.
Table 66 .NET Feature Support Modify socket buffer sizes (see Tibems.SetSocketReceiveBufferSize and Tibems.SetSocketSendBufferSize in the HTML reference) Daemon threads (see Tibems.SetSessionDispatcherDaemon in the HTML reference) When a program specifies an encoding, it applies to all strings in message bodies (names and values), and properties (names and values). It does not apply to header names nor values. The method BytesMessage.WriteUTF always uses UTF-8 as its encoding.
• Set a non-default global encoding (for all outbound messages) using Tibems.SetEncoding.
• Set the encoding for an individual message using Tibems.SetMessageEncoding.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |