Copyright © TIBCO Software Inc. All Rights Reserved

> Installation on Microsoft Windows
> This section gives information that is specific to Microsoft Windows platforms.
> Supported Platforms
> TIBCO Enterprise Message Service is available on the Windows platforms listed in Table 6. (For the latest changes, see the README file.)

> Table 6 Microsoft Windows Distribution Directories
> OS/Platform | Hardware | Installer Package Suffix | Notes
> Windows 7 64-bit Windows XP 64-bit Windows Server 2003 64-bit Windows Server 2008 64-bit Windows Vista 64-bit | Intel (64-bit) | win_x86_64_vc8.zip | For developers using Visual Studio 8.

> Installing on Windows Terminal Server 2003
> There are two modes in Windows Terminal Server: Execute and Install. Users are logged on by default in Execute mode, which allows them to run applications. To install an adapter so that everyone can use it, log on as administrator in Install mode. When the adapter is installed in the Install mode, the installation registry is maintained in %windir%\.

> | Windows Terminal Server must be running in remote admin mode, not application sharing mode. TIBCO Enterprise Message Service is not supported if installed on a machine that is using Windows Terminal Server in application sharing mode.

> The best way to install the TIBCO Enterprise Message Service on Windows Terminal Server is to use the Add/Remove Programs control panel applet. This automatically sets your mode to Install during the installation and then back to Execute afterwards. Alternatively, you can manually change your mode to Install before starting the installation by typing the following at a command prompt:
> C:\> change user /install
> Change back to Execute mode after installation is complete by typing:
> C:\> change user /execute
> To check your current mode, type the following:
> C:\> change user /query
> Installing on Windows Server 2008, Windows Vista, and Windows 7
> Windows Server 2008, Windows Vista, and Windows 7 have more strident file access control than earlier versions of Windows. The access control policies affect all users, even those with Administrator permissions.
> Administrator Permissions
> In order to ensure that an administrator has permissions to modify configuration and data files, TIBCO Enterprise Message Service now installs these files in a different directory on Windows systems. During installation, you are prompted to enter a Configuration Directory location. After installation, you will find configuration and data files in the specified directory.
> The default Configuration Directory is based on the value of your PROGRAMDATA environment variable. For example:
> C:\ProgramData\tibco
> Executable Prompt
> By default, Windows prompts for consent before starting the tibemsd or tibemsmcd as administrator. You can disable this elevation prompt for administrator users with the Windows Local Security Policy application. For more information, see the section on changing the elevation prompt behavior here:
> http://technet.microsoft.com/en-us/library/cc709691.aspx
> If you elect not to disable the prompt, the User Account Control screen opens each time you attempt to start the EMS server or multicast daemon. Click Allow to start the application.
> Works With Windows Server 2008 Certification
> TIBCO Enterprise Message Service version 5.x is certified to work with Windows Server 2008.
> .NET DLL Installation
> During installation, several DLL files are installed in the global assembly cache:
> TIBCO.EMS.DLL
> TIBCO.EMS.ADMIN.DLL
> TIBCO.EMS.UFO.DLL
> If an earlier release of TIBCO Enterprise Message Service is installed on the computer, the EMS 6.2 DLLs replace those of the earlier version.
> To reinstall the previous EMS release DLLs, you must first uninstall the 6.2 DLLs, then reinstall the DLLs from the previous release. Both of these tasks are accomplished using the Global Assembly Cache Tool (Gacutil.exe) provided by Microsoft. DLL files are located in the bin directory of the EMS installation.
> Policy Files
> Additionally, the following policy files can optionally be installed in the global cache:
> policy.1.0.TIBCO.EMS.UFO.dll
> policy.1.0.TIBCO.EMS.dll
> policy.1.0.TIBCO.EMS.ADMIN.dll
> When installed, these policy files facilitate upgrades by automatically redirecting existing EMS applications from an older assembly to the newest assembly.
> See Also
> For more information, see the section on Assembly Versioning in the TIBCO Enterprise Message Service User’s Guide.
> Dynamically Linked Libraries
> 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.
> Register the Server as a Windows Service
> Some situations require the EMS server to start automatically. The installer automatically installs the EMS server as a Windows service, and allows you to choose whether start the server manually or automatically. After EMS is installed, you can use the emsntsrg utility to change the service settings or unresgister an EMS server.
> See step 11 of Install in GUI Mode for more information.
> See Also
> emsntsrg on page 107 in TIBCO Enterprise Message Service User’s Guide.

Copyright © TIBCO Software Inc. All Rights Reserved