Admin Production rocket
Current Publication

Installing

NetExpress Bookshelf Help V5.1 WrapPack 1
Rocket® Net Express™ (formerly a product of Micro Focus or formerly a product of Open Text) documentation, created before Rocket Software acquired certain products from OpenText, may include outdated references to "Micro Focus" or "OpenText", both of which are trademarks of OpenText or its affiliates. Rocket Software is not affiliated with Micro Focus or OpenText and has since rebranded these products as Rocket® products. You may also encounter outdated links in this documentation. If you do, please contact Rocket Support (support@rocketsoftware.com) for assistance.

Chapter 2: Installing

This chapter gives you additional information you may need when installing Server Express. Full installation instructions can be found on any of the Server Express software CDs or the DVD.

Environment Variables

After you install Server Express, you are asked to set the following environment variables:

  • COBDIR. Specifies the directory that contains Server Express
  • PATH. Specifies the directories to be searched by all UNIX and Linux programs, including the run-time system, when finding executables to be run
  • LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH, depending on your system. Specifies the directory or directories for the UNIX or Linux system, cob and the run-time system to search for shared libraries and callable shared objects.

For information on these environment variables, see the appendix Environment Variables in your User's Guide.

Installation Procedure

Refer to the installation instructions on your Server Express software CDs or DVD. To view them, mount the DVD, or the CD for the Unix or Linux environment you want to use, start a browser and open the index.htm file on the root directory of the CD or DVD.

After you have installed the system, we recommend you work through the section Verifying the Installation.

Verifying the Installation

As a quick check that you have installed the system correctly, start Server Express and check that it displays its main menu. Enter the following at the operating system prompt:

sde

If the system is working, the main menu appears, similar to the one shown in Figure 2-1.

The Server Express Development Environment Screen

Figure 2-1: The Server Express Development Environment Screen

Since you are simply checking that the system is installed, press Escape to return to the operating system prompt. Server Express asks you to confirm that you want to exit; reply Y.

If problems occur with your installation, this could be because:

  • There are problems with the tar file on the CD. The tar file might be corrupt, or errors might be occuring during the extraction of files from the tar file.

    To Fix: Make an exact note of any error messages, contact Product Support and arrange to return the CD.

  • You have installed a Development System in the same directory as Micro Focus Server.

    To Fix: Ensure the Development System is in a different directory to Micro Focus Server. Re-install in a different directory if necessary.

  • The License Management Facility is installed and you have no license.

    To Fix: Read your Development System Licensing Guide and ensure any requisite licenses are installed.

If you have any other problems with the installation, you should contact Product Support.

Installing, Uninstalling and Committing Fixpacks

We issue Server Express Fixpacks from time to time to correct problems that have been reported to us by users. The installation instructions for a Fixpack are included in the Fixpack readme available alongside the Fixpack itself on the Server Express download page on the Supportline Web site. Note that you should stop all programs running under $COBDIR before installing or uninstalling a Fixpack.

You can use Fixpack Administration to manage installed Fixpacks. This tool provides facilities for :

  • Uninstalling Fixpacks
  • Committing Fixpacks

When a Fixpack is uninstalled all the files it contains are removed and the system is restored to the state it was in before you installed the Fixpack.

When a Fixpack is committed all the updates in it are permanently applied to your system.

You cannot uninstall a Fixpack that has been committed.

Warning: Installing a Fixpack might replace product files (including the run-time system) that you have linked with non-Micro Focus modules. Please be aware that if you install this Fixpack you may need to relink these product files. Refer to the appropriate third-party vendor or in-house documentation for instructions on how to do this.

Starting Fixpack Administration

To run Fixpack Administration, log in with root privileges and enter the following at the command line:

sh $COBDIR/bin/mfadminfp

You see the following menu:

 Fixpack Administration

         1) Uninstall a Fixpack
         2) Commit a Fixpack
         q) quit

Uninstalling a Fixpack

You can only uninstall the last installed Fixpack, so if you have two or more installed and uncommitted Fixpacks, you must uninstall them one at a time.

To uninstall a Fixpack follow these steps:

  1. With the Fixpack Administration menu displayed, enter: 1

    The Fixpack Administration tool reminds you that you can only uninstall the last installed Fixpack, and asks you if you want to uninstall fixpack-name, where fixpack-name is the name of the Fixpack.

  2. Enter: y

    The Fixpack Administration tool asks you to confirm that you want to uninstall this Fixpack.

  3. Enter: y

    The Fixpack Administration tool warns you to stop all running programs before continuing and asks you if you want to continue.

  4. Enter: y

    The Fixpack Administration tool runs an uninstall script, which uninstalls the Fixpack. Messages are displayed indicating the progress of the uninstall.

  5. Press Enter to continue. You see the Fixpack Administration menu. If you want to uninstall another Fixpack, return to step 1. Otherwise, press q to quit.

If the uninstall script detects a running program, it reminds you again that you should stop all running programs before attempting to uninstall a Fixpack, and aborts. The uninstall script writes a log file called $COBDIR/fixpacks/install.log. You can view this to help you find out which program was running.

Committing a Fixpack

You can choose one Fixpack to commit. If there are earlier installed and uncommitted Fixpacks, they are also committed.

To commit a Fixpack follow these steps:

  1. With the Fixpack Administration menu displayed, enter: 2

    The Fixpack Administration tool lists the currently installed Fixpacks, for example:

    The following Fixpacks are currently installed:
                1) FixPack50.03_1 committed
                2) FixPack50.03_2
                3) FixPack50.03_3

    and reminds you that when you commit a Fixpack all earlier installed and uncommitted Fixpacks are also committed. It then asks you to select a Fixpack to commit or enter q to quit..

  2. Enter the number corresponding to the Fixpack you want to commit.

    The Fixpack Administration tool tells you which Fixpacks it will commit. In the example, if you entered 3 you would see.

    The following Fixpacks will be committed:
    FixPack50.03_2
    FixPack50.03_3

    It asks you if you want to continue.

  3. Enter: y

    The Fixpack Administration tool runs a commit script, which commits the Fixpack you chose and all earlier installed and uncommitted Fixpacks. Messages are displayed indicating the progress of the commit process.

  4. Press Enter to continue. You see the Fixpack Administration menu.
  5. Press q to quit.

Copyright © 2007 Micro Focus (IP) Ltd. All rights reserved.