Installation Notes

The notes below give information on installing reUZE Server.

• Installation Program
• Installing Silently
• Licensing Database Connectors
• License Database
• Shared reUZE Server
• Microsoft Terminal Server
• Offline Web Browser
• Repairing
• Uninstalling
• Windows Compatibility Mode

After installing, you need to install the latest updates from the Micro Focus Product Support Web site. See Updates and Product Support.

Installation Program

• reUZE Developer and reUZE Server cannot co-exist on the same machine.
• If, when you install reUZE Server, the machine does not have Microsoft Visual C++ 2008 Redistributable Runtime already installed, it will be installed as required by reUZE Server. The installation of Microsoft Visual C++ 2008 Redistributable Runtime will add a number of .dll files, without digital signatures, into the winsxs directory.
• If you are installing this as an upgrade, make sure that the product is not running on your machine when you start the installation. Also, the Visual Studio Help must not be open.
• To install the product, you need to be logged in with a user-ID that has write access to the registry structure under HKEY_LOCAL_MACHINE, HKEY_CLASSES_ROOT, and HKEY_CURRENT_USER so the installation software can set the environment appropriately. You also need to be logged on with Administrator privileges.
• Before installing reUZE Developer and reUZE Server, make sure that any existing Micro Focus Directory Server (MFDS) or CCITCP2 Windows service from an existing product is stopped and uninstalled, as follows:
  1. Stop the service, using either the Windows Service Management Console GUI or from a command line prompt by typing:

     net stop mf_ccitcp2

     Only one instance of the MFDS or CCITCP2 service can run on a Windows machine.
  2. Uninstall the MFDS or CCITCP2 service. For MFDS, from a command line prompt enter:

     mfds -u 

     For CCITCP2:

     ccitcp2 -u

  To run an earlier version of MFDS as a service after you have installed a later version:

  1. Stop and uninstall the MFDS service, as described above.
  2. Reinstall the earlier version, as follows:
     1. Open a COBOL command environment.
     2. Install the service. Enter the following command:

        mfds -i

     3. Start the service. Enter the following command:

        net start mf_ccitcp2

     Note that the two versions use different paths for environment and registry values, so the list of configured Enterprise Servers might be different depending on which version has been started, since, by default, different MFDS data repositories are used.

  MFDS 5.1 and later are able to import or use Enterprise Server configuration data generated by earlier versions of MFDS, but 5.0 or earlier versions of MFDS might not be able to read data generated by later versions.

  It is possible to run MFDS from a COBOL command environment ("mfds") rather than as a service, but by default the "mfcobol" port is used (86) and this can only be used by one process at a time

Shared reUZE Server

• When you install reUZE Server, you choose whether to install a shared reUZE Server that multiple applications can use, or a copy of reUZE Server specific to your application.

  If you use a shared reUZE Server, you can use the setup program supplied on the DVD, as described above. You install reUZE Server in its own directory and then you install your applications in their own directories. We strongly recommend that you use a shared reUZE Server if you run your application using one of the Micro Focus trigger programs, run*.exe. This ensures that your environment is set up correctly.

  If you use an application-specific reUZE Server, you install it in the same directory as your application. You either use the setup program supplied by your application supplier or you copy the files manually and set up reUZE Server.

License Database

• reUZE Server licenses are held in a license database. When you install reUZE Server, you choose the location of the license database on the local machine.
• You can use only one license database on a machine. Once it is created, you cannot move it. If you create another database, you cannot use the licenses in the original database, but you can reinstall them in the new database.
• You can use a shared license database on a network server. In which case the license database holds the licenses for multiple end-users' applications. You can set up a network license database. For details see the Licensing How to topics in your product help.
• Some features of reUZE Server are licensed by Sentinel RMS by SafeNet. A Sentinel RMS license server in installed onto you machine when you install the product.

Offline Web Browser

• To use your Web browser off line, you need the dial-up networking feature of Windows installed. Otherwise you may have TCP/IP errors such as being unable find "localhost" or the numeric equivalent (127.0.0.1).

Installing Silently

To install silently, from the setup folder of your Micro Focus product CD, use the following commands:

start /wait install-file.exe /s /v"/qn [parameters]"

For reUZE Server:

For 32-bit: start /wait vcredist_x86.exe /q 
For 64-bit: start /wait vcredist_x64.exe /q

start /wait Sentinel_setup.exe /s /v"/qn ADDLOCAL=ServerInstaller" 
start /wait NSP3260*.exe /s /v"/qn [parameters]"

Parameters

A silent installation creates a log file in the folder %temp%\LogFilename by default. To change the location, use the /l parameter on your Setup command line and specify the path and file name, for example: /l*v drive:\path\LogFilename. If the log file created ends with a "completed successfully" message, the silent install was successful.

Directory Considerations

• The log filename and folder name cannot contain spaces
• The log file folder must exist before beginning the silent install
• You can override the default installation folder using the INSTALLDIR parameter: INSTALLDIR=path
• You must have read and write access for every directory accessed during the install.
• If a path in a definition contains spaces, then the path must be preceded by a backslash and double quotation mark (\").

Examples

In the following examples, InstallFile refers to the installation file SRP32xxxxxxxx.

• To install the product using default options:

  start /wait InstallFile.exe /s /v"/qn" 

• To install the product in a non-default directory:

  start /wait InstallFile.exe /s /v"/qn INSTALLDIR=c:\DirectoryName" 

• To install and specify the log file as c:\install-log.txt:

  start /wait InstallFile.exe /s /v"/qn /l*vx c:\install-log.txt"

• To install with Serial Number and WO number:

  start /wait Installfile.exe /s /v"/qn SERIALNUM=SerialNumber WONUMBER=WONumber"

• To install with license information for Server only:

  start /wait InstallFile.exe /s /v"/qn SERIALNUM=SerialNumber 
        LICENSENUM=LicenseNumber DATABASEDIR=DatabasePath"

• To install the .msp for a WebSync and specify the log file:

  start /wait msiexec.exe /update InstallFile*.msp /qn /l*v wsinstall.txt

Licensing Database Connectors

• Database Connectors require a seperate license to run on reUZE Server. The information you need to install the license is included here.

  You may request a license file for one or more users. The number of users (user limit) is set in your license agreement with Micro Focus. When you receive your products, the package includes product codes and keys for Database Connectors. You must have the product codes and keys to create the license file. When you install or update your license file, place it in the bin directory of Database Connectors; Database Connectors expects the license file to be in the same directory as the executable file and must be able to locate its license file in order to function. If you have multiple users or interfaces, you may copy the license file onto each machine containing Database Connectors or place Database Connectors and your license file on a shared drive.

  The Activator utility automates the process of creating a license file. When you install Database Connectors, the Activator utility, activator.exe is installed for you in the installation directory by default. The last screen of the install has a check box for launching Activator. Launch the Activator to enter a new or updated product code and key. Note that Activator is case-insensitive and displays only uppercase characters. Activator also ignores embedded spaces and separating characters. License codes and keys do not contain the letters “O” or “I”. When you have entered your product codes and keys, Activator displays a dialog box that confirms whether license file activation was successful.

  Note: If license activation was successful, but you get a message during Database Connectors startup indicating that the license file cannot be found, the license file may not be in the proper directory. Activator determines where to place the license file based on entries in the Windows registry. If no registry entry is found, the license file is placed in the same directory as the Activator executable.

Microsoft Terminal Server

• Microsoft Terminal Server is an environment for running multiple instances of a single user product. It is not a platform where a single-user product can be made to perform as a multi-user product.
• You can use reUZE Server with Microsoft Terminal Server. Note that a separate end-user license is required for each user who accesses reUZE Server, even if the product is running on a single machine. See your End User License Agreement.
• To install onto a terminal server, log on to the physical terminal server with a user ID that has administrator privileges. Then use Control Panel > Add/Remove Programs and follow the instructions on the screen.
• When you install the product on Microsoft Terminal Server or similar terminal software, do not execute more than one installation at the same time.
• When you install Microsoft Terminal server, you must assign a unique port address to each user. Then the very first time that each user logs into reUZE Server and starts the terminal server, he or she should:
  1. Select Options > Project > Port address for Web Server.
  2. Type in the assigned port address.

  This is necessary because the default port address for the Web server is 80. Once this has been allocated to the first user, when the next user attempts to start the Web server, the software recognizes that this port is in use and rejects the attempt. Consequently each user requires an individual port address.

Repairing

• If any product files, registry settings or shortcuts are accidentally removed at any point, you can perform a Repair on the installation to replace them. To do this, use Control Panel > Add/Remove Programs and follow the instructions on the screen.

Uninstalling

• To uninstall the product, you need to be logged in with the same user-ID as you used when you installed it.
• To uninstall the product, you cannot simply delete its files from your hard disk. Instead, you uninstall by using Control Panel > Add/Remove Programs, on most Windows systems. You might need to ensure that Show Updates (at the top of the Add or Remove Programs dialog) is checked, so that any hot fixes or WrapPacks are listed.

  When you uninstall, the only files deleted are those that the installation software installed. If your reUZE Server directory has not disappeared, delete any unwanted files and subdirectories within it using Windows Explorer.

The following registry entries are not removed by the uninstall process:

• Registry entries that are created on the first time that an Enterprise Server that has been enabled for performance monitoring starts up:

  • Micro Focus Server\Performance\Active Servers
  • Micro Focus Server\Performance\PerfIniFile
• Registry entries for event logging, created at runtime:
  • SYSTEM\CurrentControlSet\Services\Eventlog
  • Micro Focus Server[<SERVER_NAME>] with the following entries:
    • CategoryCount
    • CategoryMessageFile
    • EventMessageFile
    • TypesSupported

Windows Compatibility Mode

• In Windows Vista and Windows Server 2008, if you have problems starting Enterprise Server instances using the Micro Focus Enterprise Server Administration HTML GUI, ensure that none of the Enterprise Server program files are configured to use a Windows compatibility mode. You can check for compatibility modes by examining the file properties for the program file using Windows Explorer. After opening the Properties dialog for the file, select the Compatibility tab; ensure the checkbox Run this program in compatibility mode for is not checked. If it is checked, clear the checkbox. Then click Show settings for all users and ensure the Run this program in compatibility mode for checkbox is not checked on the new dialog. Click OK on both dialogs to update the file properties.

  Verify that product-install-folder\base\bin\mfds.exe is not set to run in a compatibility mode. Then, for 32-bit Enterprise Server, check base\bin\cas*.exe and base\bin\mfcs.exe; for 64-bit Enterprise Server, check base\bin\win64\cas*.exe and base\bin\win64\mfcs.exe.