Version 8.1 UNIX Quick Start Guide Product and License Installation Procedures Before You Begin Follow the directions in the next section to install any products from the extend8 family on your machine. You may install Acucorp products on either the client or the server with the following exceptions: The compiler and runtime can be run from a shared drive, but AcuBench® cannot. AcuBench and the AcuXDBC® client must be installed on each client machine. Server-side products such as AcuServer®, AcuConnect®, and AcuXDBC Server®, should not be installed on client machines. Important: Acucorp products (on some platforms) may be distributed as shared object libraries or statically linked. If you have ordered the shared object libraries, you may need to set a shared library path before you can successfully install and activate the Acucorp products. Refer to “Installing Shared Object Libraries” below for more information. Installation Instructions 1. Download the product from the Micro Focus supportline site. Using a tar command, extract the files in the archive to your installation directory. For example: tar–xvf archive-name.tar 2. Locate and run the Activator executable, which by default is located in the bin directory of “AcuGT”. The Activator is a program that you use to enter your product code and key information. 3. When prompted, enter Y to confirm that the port and operating system are compatible. Then enter the product code and product key for each product you’ve installed. Press Enter after each prompt. If you enter N, you will have to rerun the Activator executable to install the license files after you have transferred all the product files to a compatible system. The Activator utility creates a separate license file for each product you have purchased. If your license server will be accessed by users of the ACUCOBOL-GT Web Runtime, be sure to install a runtime license file on the server that accommodates the total number of concurrent Web runtime connections that you anticipate. Consult A Programmer’s Guide to the Internet for more information on Web runtime licensing. Each product searches for its corresponding license file in the same directory as the matching executable file. If you move the product executable to a new directory, be sure to move the license file as well. If you change the name of an executable file, you must change the base name of the license file to match. For example, if your runtime executable file is called “runcbl” and you change the name of this file to “runtime,” you must change the name of the corresponding license file from “runcbl.alc” to “runtime.alc.” In the future whenever you need to add a new license file, run the Activator executable to install the new code/key pairs. This executable is placed in the same directory as the runtime and other binary executables by default. Use the version of the Activator on this media to install the product(s) contained on this media. 4. Start the acushare service (acushare -start) before you execute Acucorp products. See section 8.2.2, “Starting and Stopping acushare,” in the Getting Started manual. Version 8.1 UNIX Quick Start Guide extend8 Product and License Installation Procedures Custom UNIX CD Installations 1. Mount the installation CD-ROM according to the directions in your operating system manual. Copy the files from the CD-ROM to the destination directory using the following command: cp -r /devicename/* . where devicename is the designation for your CD-ROM drive. This will unload all product files in the current directory. 2. Launch the Activator utility, which is used to enter your product codes and keys. Change to the “bin” directory and type: ./activator Be sure to use the version of the Activator provided with your product distribution to install the product(s). 3. When prompted, enter the product code and the product key that came with your product. Press Enter after the prompt and repeat for each product. The Activator utility creates a separate license file for each product you have purchased. If your license server will be accessed by users of the ACUCOBOL-GT Web Runtime, be sure to install a runtime license file on the server that includes permissions for the total number of concurrent Web runtime connections that you anticipate. Consult A Programmer’s Guide to the Internet for more information on Web runtime licensing. Each product searches for its corresponding license file in the same directory as the matching executable file. If you move the product executable to a new directory, be sure to move the license file as well. If you change the name of an executable file, you must change the base name of the license file to match. For example, if your runtime executable file is called “runcbl” and you change the name of this file to “runtime,” you must change the name of the corresponding license file from “runcbl.alc” to “runtime.alc.” 4. Use the acushare -start command to start the acushare service before you execute Acucorp products. See section 8.2.2, Starting and Stopping acushare, in the Getting Started book for details. Windows Client Installation If you are installing products on Windows client machines for use in your UNIX network, please refer to the Quick Start card that came with the Windows products. Note: If you use AcuConnect® for a distributed processing deployment, you must install an ACUCOBOL-GT runtime on each client machine in addition to installing AcuConnect on the server. Installing Shared Object Libraries On some platforms, Acucorp products are distributed as shared object libraries (instead of being statically linked). If you did not install your products in the default installation path, or did not create the symbolic Link (“/opt/acu”) to your products, you must set an environment variable to indicate the path to the shared objects. To do this, follow the instructions below for your platform. AIX 5.1 and later (32-bit and 64-bit): Set the environment variable LIBPATH to include the directory that contains the lib*.so files. In order to get information about executables and shared object libraries, execute the “dump -H” command. See your AIX documentation for more information. HP-UX 11 and later (32-bit and 64-bit): Set the environment variable SHLIB_PATH (32-bit) or LD_LIBRARY_PATH (64-bit) to include the directory that contains the lib*.sl files. In order to get information about executables and shared object libraries, execute the “ldd” command. See your HP-UX documentation for more information. Note that on this platform the shared library extension is “.sl” and not “.so”. Version 8.1 UNIX Quick Start Guide extend8 Product and License Installation Procedures Solaris 7.0 and later (32-bit and 64-bit): Set the environment variable LD_LIBRARY_PATH (32-bit) or LD_LIBRARY_PATH_64 (64-bit) to include the directory that contains the lib*.so files. To get information about executables and shared object libraries, execute the “ldd” command. See your Solaris documentation for more information. User’s Guides You can view or download PDF or HTML versions of the user’s guides from the support section of the Micro Focus website: http://supportline.microfocus.com Development System ACUCOBOL-GT Compiler To use the ACUCOBOL-GT compiler, first copy configuration files to the locations specified in your Getting Started manual. Then, launch the compiler by entering a ccbl command with options on the UNIX command line. For example, to see a list of compiler options, enter the following UNIX command line: ccbl -help For detailed information on compiler options, see section 2.1, Using the Compiler, in the ACUCOBOL-GT User’s Guide. ACUCOBOL-GT Runtime To execute an ACUCOBOL-GT program with the runtime, type a runcbl command on the UNIX command line. The general syntax is: runcbl [options] object-file [parameters] For information on command options and parameters, see section 2.2, Using the Runtime, in the ACUCOBOL-GT User’s Guide. Server-side Solutions TCP/IP connections are required for the following products. AcuServer To begin using AcuServer®, you must first set up user accounts and establish system configuration files on the server. For instructions, open the AcuServer User’s Guide and read Chapter 2, “Preparing your UNIX Network.” Once you have read this and have prepared the server accordingly, you can add the AcuServer “bin” directory to your UNIX PATH environment variable, and start the AcuServer daemon on the server using the acuserve -start command. AcuConnect To begin using AcuConnect, you must first prepare your application, configure the server, and configure the client. For instructions regarding configuration issues for the distributed processing deployment, refer to Chapters 2-4 of the AcuConnect User’s Guide. For an AcuConnect thin client deployment, you must set up user accounts and establish system configuration files. Instructions for using the thin client can be found in Chapters 6-7 of the AcuConnect User’s Guide. Once you have prepared the system accordingly, you can add the AcuConnect “bin” directory to your UNIX PATH environment variable, and start the AcuConnect daemon on the server using the acurcl -start command. Version 8.1 UNIX Quick Start Guide extend8 Product and License Installation Procedures AcuXDBC Server The use of AcuXDBC Server implies that AcuXDBC enabled clients will be accessing data files residing on a network server. This means there are steps to perform on both the client and server machine. Client steps will vary depending on whether it is a Windows or UNIX client. This guide provides the general steps for using AcuXDBC Server. Each step provides the section number of the AcuXDBC User’s Guide that corresponds to each step.