Micro Focus® ™ Enterprise View Installation Guide

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

Micro Focus (IP) Ltd. has made every effort to ensure that this book is correct and accurate, but reserves the right to changes without notice its sole discretion at any . The software described in this document is supplied under a license and may be used or copied only in accordance with the terms of such license, and in particular any warranty of fitness of Micro Focus software products for any particular purpose is expressly excluded and in no event will Micro Focus be liable for any consequential loss.

Animator®, COBOL Workbench®, EnterpriseLink®, Mainframe Express®, Micro Focus®, Net Express®, REQL® and Revolve® are registered trademarks, and AAI™, Analyzer™, Application Server™, Application to Application Interface™, AddPack™, AppTrack™, AssetMiner™, CCI™, DataConnect™, Dialog System™, Enterprise Server™, Enterprise Server with MTO™, EuroSmart™, FixPack™, LEVEL II COBOL™, License Server™, Mainframe Access™, Mainframe Manager™, Micro Focus® COBOL™, Micro Focus® Studio™, Micro Focus® Server™, Object COBOL™, OpenESQL™, Personal COBOL™, Professional COBOL™, Server Express™, SmartFind™, SmartFind Plus™, SmartFix™, SourceConnect™, SupportLine™, Toolbox™, VS COBOL™, WebSync™, and Xilerator™ are trademarks of Micro Focus (IP) Ltd.

IBM® and CICS® are registered trademarks, and IMS™, DB2, DB2/390, DB2 Connect Enterprise Edition, DB2 Connect Personal Edition, COBOL for OS/390, Enterprise.

Systems Architecture/390, ESA/390, MVS, MVS/ESA, OS/390, S/390, System/390, VSE/ESA and MFS are trademarks, of International Business Machines Corporation.

Netscape Enterprise Server™ is a trademark of Netscape Communications Corporation.

Internet Information Server®, Windows 95®, Windows 98®, Windows NT 4.0®, Windows ME® and Windows 2000® are registered trademarks of Microsoft Corporation.

Pentium® is a registered trademark of INTEL Corporation.

Borland Database Engine™ and Midas™ are trademarks of Inprise Corporation.

Oracle™ is a trademark of Oracle Corporation Inc.

UNIX® is a registered trademark of The Open Group.

Solaris™, Ultra Sparc™ and Java™ are trademarks of Sun Microsystems, Inc.

Linux, GCC compiler, GNU CTAGS, GNU , Samba and KDE/GNOME refer to Open Source tools.

This product includes modified versions of software developed by the Apache Software Foundation (as described on the Apache web site).

The YGrep Search Engine is Copyright (c) 1992-2004 Yves Roumazeilles. All other trademarks are the property of their respective owners.

No part of this publication, with the exception of the software product user documentation contained on a -ROM, may be copied, photocopied, reproduced, transmitted, transcribed, or reduced to any electronic medium or machine-readable form without prior written consent of Micro Focus (IP) Ltd. Contact your Micro Focus representative if you require access to the modified Apache Software Foundation source files.

Licensees may duplicate the software product user documentation contained on a CD-ROM, but only to the extent necessary to support the users authorized access to the software under the license agreement. Any reproduction of the documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification.

U.S. GOVERNMENT RESTRICTED RIGHTS. It is acknowledged that the Software and the Documentation were developed at private expense, that no part is in the public domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under Federal Acquisition Regulations and agency supplements to them. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFAR 252.227- 7013 et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at FAR 52.227-19, as applicable. Contractor is Micro Focus (IP) Ltd, 9420 Key West Avenue, Rockville, Maryland 20850. Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software.

5

Table of Contents:

1. ABOUT THIS DOCUMENT ...... 7 2. PROCESS PHASES...... 9 3. REQUIREMENTS ...... 11 4. BEFORE YOU START...... 15 5. DATABASE SCHEMA CREATION ON ORACLE SERVER...... 17

5.1. RUN THE SETUP OF DBINSTALL ...... 17 5.2. CREATE THE ORACLE REPOSITORY...... 17 5.3. RUN THE ENTERPRISE VIEW DATABASE CREATION TOOL MODULE ...... 18 6. ENTERPRISE VIEW INSTALLATION ...... 21

6.1. INSTALLING ENTERPRISE VIEW ON UNIX AND ...... 21 6.2. NON-CD INSTALLATION...... 27 6.3. POST-INSTALLATION ...... 28 6.3.1. Update .bash_profile...... 28 6.3.2. Create home directory for Enterprise View ...... 29 7. ENTERPRISE VIEW PORTAL INSTALLATION ...... 31 8. CLIENT INSTALLATION ...... 33

8.1. CLIENT MODULES INSTALLATION...... 33 8.2. STARTING NAVIGATOR FOR THE FIRST TIME ...... 34 8.3. WIZARD...... 34 8.4. SETTINGS ...... 36 8.5. STARTING NAVIGATOR...... 36 9. CLIENT INSTALLATION ON CITRIX SERVER ...... 39

9.1. ENTERPRISE VIEW PUBLISHING...... 39

6

Installation Guide 7

1. About This Document

This guide outlines the main steps to be performed when you start the installation of Enterprise View 5.6. It will guide you through the product installation procedures. The steps described in the chapters below must be followed in the order given.

8

Installation Guide 9

2. Process Phases

The four main steps to be followed are: 1. Database schema creation on the ORACLE server 2. Enterprise View Host setup 3. Enterprise View Client module installation 4. Enterprise View Portal installation

10

Installation Guide 11

3. Requirements

For hardware and software requirements, see the guide Hardware and Software Requirements.

Before you start the installation, you need to see if your machine meets the requirements of the product (for the engine and portal). This is done by the Pre- Check application. It creates an output that contains the collected information.

Step 1: Connect to the host machine and log on.

Step 2: The Pre-Check tool is in the CD folder /PreCheck as precheck.tar.gz. Untar it in the directory where Enterprise View will be installed by typing tar zxvf precheck.tar.gz, followed by the name of the directory.

Sometimes the tar version does not fully support unzip:

-bash-2.05b$ tar zxvf precheck.tar.gz Usage: tar -{c|r|t|u|x} [ -BdDEFhilmopRsUvw ] [ -Number ] [ -f TarFile ] [ -b Blocks ] [ -S [ Feet ] | [ Feet@Density ] | [ Blocksb ] ] [ -L InputList ] [-X ExcludeFile] [ -N Blocks ] [ -C Directory ] File ... Usage: tar {c|r|t|u|x} [ bBdDEfFhilLXmNopRsSUvw[0-9] ] [ Blocks ] [ TarFile ] [ InputList ] [ ExcludeFile ] [ [ Feet ] | [ Feet@Density ] | [ Blocksb ] ] [-C Directory ] File ...

If this is the case, you must perform the unzip in two steps as follows:

-bash-2.05b$ gunzip precheck.tar.gz -bash-2.05b$ tar xvf precheck.tar x precheck x precheck/precheck.sh, 427 bytes, 1 tape blocks x precheck/aix x precheck/aix/precheck_aix.sh, 12091 bytes, 24 tape blocks x precheck/doc x precheck/doc/readme.txt, 1222 bytes, 3 tape blocks x precheck/linux x precheck/linux/precheck_linux.sh, 12045 bytes, 24 tape blocks x precheck/sun x precheck/sun/precheck_sun.sh, 12161 bytes, 24 tape blocks

Step 3: Go to the directory where Enterprise View will be installed and run the Pre-Check application by typing the command ./precheck.sh and click Enter. Note: If an error occurs when untarring and the executable attribute is lost, +x precheck.sh.

You must run the Pre-Check in the folder where the product will be installed, and with the user will run it, because Pre-Check will check for permissions are necessary for the installation of the product.

12

If you want to use the default Oracle login credentials, type n. If you prefer to use other login credentials, type y.

To obtain the Oracle version, the Pre-Check needs to connect to Oracle. You must login as an actual Oracle user (by default, the user is system and the password is manager).

Step 4: To see how the Pre-Check works, type ./precheck.sh –h.

The options are: -v verbose - > Displays a print table of the collected information. -o "output file" -> Writes an output filename if you do not want to use the default one which is "ev_precheck.out". -j "path to Java" -> Types the path to Java to inform the Pre-Check where the Java version is. If you do not write it, the Pre-Check will perform a check with the default Java for the current machine (on machines, the default Java set in the environment is not SUN Java but, for example, GCJ). -h -> Displays the options.

Step 5: To see the print table of the gathered information, type ./precheck.sh (–v by default). To see information about Java, type –j and the java path. e.g. ./precheck.sh -v -j /usr/java/jdk1.5.0_09/bin

Step 6: View the output.

This is an example of the Linux Pre-Check output:

======Enterprise View Linux Pre-Check ======Host Name : srv008bg.microfocus.com

======Hardware Requirements for Linux ======

Processor : OK (i686) Min. Memory : OK (5067 MB : required 2048 MB, recommended 4GB) Disk Space ./ : OK (183603 MB : required 150 MB)

======Software Requirements for Linux ======

Oracle launched : OK Oracle Client : FAIL () Samba launched : OK LIBGCC : OK (/usr/lib/gcc/i386-redhat- linux/3.4.6/libgcc.a) LIBSTDC++ : OK (/usr/lib/gcc/i386-redhat- linux/3.4.6/libstdc++.a)

Installation Guide 13

GNU CTAGS : OK (5.5.4) GNU DIFF : OK (2.8.1) Java : OK (1.6.0) Java Location : /usr/bin/java

Write permissions ./ : OK

======Software Requirements for Portal ======

JAVA_HOME : OK (/usr/java/default) Java version : OK (1.6.0) Java Location : /usr/bin/java

======

Host Name: Displays the name of the host machine.

Engine Hardware Requirements: Processor: Shows if the processor complies with the requirements (OK if it does, FAIL if it does not), and its type, in brackets. Min. Memory: Shows if the minimum requirements for memory are met. The information in the brackets refers to the memory of the host machine, the required minimum memory and the recommended memory. Disk Space: Shows if there is enough disk space. The information in the brackets refers to the free disk space of the machine and the disk space required by the product.

Engine Software Requirements: Oracle launched: Shows if Oracle is launched (OK) or not (FAIL). Oracle Client: Shows if there is an Oracle Client and its version. Samba launched: Shows if Samba is launched (OK) or not (FAIL). LIBGCC: If this library is present (OK), the brackets display its path. If it is not present (FAIL), the brackets display its name. LIBSTDC++: As above. GNU CTAGS: If present (OK), the brackets display its version. GNU DIFF: If present (OK), the brackets display its version. Java: If found (OK), the brackets display its version. Java Location: Shows the path to the Java whose version is being checked. If you have not specified a path to a specific Java, it will display the path to the default Java. Write permissions: Shows whether you have write permissions (OK) or not (FAIL). You must run the Pre-Check in the folder where the product will be installed, and with the user who will run it, because Pre-Check will check for write permissions which are necessary for the installation of the product.

Portal Software Requirements:

14

JAVA_HOME: Shows if this has been exported (OK) or not (FAIL). Java version: Shows the Java version. The minimum requirements for the Java version for the Portal (1.5.0) differ from those for the Engine (1.3.0). Java Location: Shows the path to the Java whose version is being checked. If you have not specified a path to a specific Java, it will display the path to the default Java.

The AIX Pre-Check output table is very similar to that of Linux. The only difference between it and Linux is that the Pre-Check checks if the AIX version complies with the requirements of the product. If so (OK), the information displayed in the brackets refers to the version.

The Sun Pre-Check result table is similar to that of Linux.

Note: On Linux and Sun, the paths to LIBGCC and LIBSTDC++ must be contained in the environment variable LD_LIBRARY_PATH, while on AIX they must be included in the environment variable LIBPATH.

Installation Guide 15

4. Before You Start

Find the following components, which are part of the product that you have received: • The software CDs or DVD, labeled Enterprise View. • License Key Card (also called Product Information), which contains the product license key (comprising the serial number and license number), information on the number of users licensed to use your copy of Enterprise View, and information about which environment the license is for. • License Management Guide.

If you have a previous Micro Focus Enterprise View product installed:

• We recommend that you make a backup of any Enterprise View system files that you might have changed. After you have installed Enterprise View, you might want to re-apply any changes you previously applied to these files. • If you are installing Enterprise View over an existing Enterprise View system, you must delete the existing Enterprise View system first. Alternatively, you might prefer to move your existing Enterprise View system to another directory until you have verified the new installation (though this will stop Enterprise Server in your existing Enterprise View system from working). • Before starting the installation, you must copy all files with .cfg and .conf extensions from the Job directory in the engine into the new Job subfolder created by the current installation when the Host installation of the Enterprise View is complete.

The files that must be copied from the Job folder are: KbCustAgent.conf, KbXAgentEnv.conf, and FileTab.txt (if present).

Two of the .conf files (kbAim.conf and KbXAgent.conf) will be regenerated if you log in as ADMIN user after you install this version of the product. kbAimEnv.conf will be regenerated after you run a job. Note: Before you start the migration, please send this file to SupportLine ([email protected]), and we will provide a specific database update, if needed.

16

Installation Guide 17

5. Database Schema Creation on Oracle Server

5.1. Run the Setup of DBInstall

The client modules are installed using the classic setup procedure on the Windows platform.

Step 1: Start the setup.exe program on the Enterprise View installation CD. Your default browser will open and display the “Welcome to Micro Focus Enterprise View” page.

Step 2: Click Install Database Creation Module under Step 3 on the page.

Step 3: The Enterprise View 5.6 setup wizard will appear. Click Next to continue. Note: If your default browser is Mozilla Firefox, the “Opening dbinstall” dialog box will appear. When you click OK, the Setup Wizard will appear.

Step 4: The License Agreement window will appear. Read the License Information and select ‘I Agree’ to accept the License Agreement. Click Next.

Step 5: The Select Installation Folder window will appear. The setup program proposes a default folder where DBInstall will be installed. We recommend you accept it. If you want to change the default folder, use the Browse button. If you click Disk Cost, you will see a list of all drives where you can install DBInstall, along with their required and available disk space. This form lets you choose whether to install the tool only for yourself or for all users working on this machine. Click Next to continue.

Step 6: This window lets you select whether to start the Navigator after the installation is completed. Click Next to continue.

Step 7: The Confirm Install window will appear. Click OK to start the installation.

Step 8: The next window shows the progress of the installation and when it is completed, you will be informed that DBInstall has been successfully installed. Click Close to the Wizard.

Step 9: At the end of the installation process, a window will appear asking if you want to run DBInstall now. Click to confirm the end of installation and start the Enterprise View Database Creation Tool.

5.2. Create the ORACLE Repository

18

In order to create an Enterprise View repository schema on the Oracle server, you need to provide the ORACLE Service Name and Schema Name.

5.3. Run the Enterprise View Database Creation Tool Module

Step 1: Run the Enterprise View Database Creation Tool by clicking its icon on your desktop (Enterprise View 5.6 - DB Install). The System Account Information window will appear.

Provide the following options: • Database Name: Enter the name of one of your registered databases. If your service name does not appear in the dropdown box, you can simply type it manually. • Username/Password: Provide credentials for the user “SYSTEM” or another user with SYSTEM privileges. • Off Line: This mode is used to produce Enterprise View schema creation scripts that will be manually executed using SQL*Plus or similar tool. Provide Datafile Path and Oracle Version (9 or 10). If you work online, the properties are taken directly from the database.

Click to ensure the provided information is correct. If it is correct, the window informing you that the connection test is successful will open. Click OK to close it.

If the test is correct, click Next to continue.

Step 2: The Target Schema Information window will appear.

Provide the following information. • Schema Name: Specify any name. • Index Tablespace Size: You can change the default values (500Mb) as necessary for your disk space requirements depending on the amount of your source code. • Blob Tablespace Size: You can change the default values (100Mb) as necessary for your disk space requirements. • Logging: If you check these boxes, the Oracle REDO LOG feature will be enabled: all the changes to the data will be logged (this means that your data will be better protected). • Temporary Tablespace Size: When creating a new Temporary Tablespace you can adjust the default size (100Mb) as necessary for your disk space requirements. • Create New Temporary Tablespace: By checking this box you can create your own new temporary tablespace. Otherwise you can choose an existing one.

The following fields are automatically updated but you can change them as necessary for your requirements: • Primary Tablespace Name • Primary Tablespace File Name • Primary Tablespace Size (Mb)

Installation Guide 19

• Index Tablespace • Index File Name • Index Tablespace Size (Mb) • Blob Tablespace Name • Blob Tablespace File Name • Blob Tablespace Size (Mb) • New Temporary Tablespace Name • New Temporary Tablespace File Name • New Temporary Tablespace Size (Mb)

Additional Options: Create Empty Schema box – use this option when you want to create an empty schema in order to restore a schema from a backup file. If you want to load an existing schema, check this.

Click Next to continue.

Step 3: There are two ways of creating a schema (from the Final Generation step): 1/ Manual (Save to file) 2/ Automatic (Interactive generation)

Step 3.1 Manual - Click Save to file and all the scripts needed for schema creation will be saved to disk and can be executed later using a batch file that is automatically created for convenience. When you click Save, a window will inform you that the Save to file operation is successful.

Step 3.1.1: The action log and the progress bar below it inform you of the progress of the process and when the creation is successfully completed. Click Close to exit.

Step 3.2: Automatic - Click Interactive generation and all the required scripts are executed from the Creation Tool interactively so you can track the current progress in the action log that is displayed.

Note: When you are in off-line mode, the Interactive generation button is inactive.

Step 3.2.1: A window informing you that the creation is successful will appear. Click OK to continue.

Step 3.2.2: The action log of the Database Creation process is visible in the Final Generation window. Click Close to exit.

Step 3.3: Storage Parameters – Before you create a schema (manually or automatically), you can check and edit the storage parameters. When you click Storage Parameters, a window with three tabsheets appears: Primary Key, Indexes, and Tables. You can edit the parameters directly in them.

Step 3.4: Drop Schema Script – Click this button to generate a script that you can use to drop a schema. You cannot drop the schema directly from here, but you can

20 use this script when you want to drop it. You can edit the script directly in the Drop Schema Script window.

When you click OK or Cancel, the Save Action Log as text file window appears, which allows you to save the script as file, whether you have made changes to it or not.

Installation Guide 21

6. Enterprise View Host Installation

This section provides information on extracting the software from CD or DVD and installing it in the target environment. If the target environment does not have a CD-ROM drive, go to the section Non-CD Installation.

6.1. Installing Enterprise View on UNIX and Linux

The following instructions explain how to install Enterprise View on UNIX and Linux. In the examples, product defaults are used for directory names and paths. All example command lines are specific to sh and bash. If you are using csh, you should use the equivalent csh commands for the examples provided.

Reference Environments

This product is built using a combination of components, referred to collectively as the reference environment. They include the operating system itself, the C/C++ development system, the system , the assembler, Java and specific operating system patches, where known. The version levels of these components are displayed during the installation of the product.

You can run this product on component versions that differ from those listed, but the product is only fully guaranteed on identical environments. The greater the difference between the reference environment and the user environment, the greater the likelihood of there being compatibility issues.

The details of the reference environment for your chosen environment are available in the file EnterpriseView/Documentation/.txt.

Step 1: Connect to the host machine and log in as root.

Step 2: Insert either the DVD or the CD labeled Enterprise View into the drive. If you are using a CD, make sure you have the correct CD for your environment.

Step 3: Go to the directory where the CD or DVD is mounted.

Step 4: Run the setup script with the following command. sh ./setup.sh

The License Agreement will appear. Type y to accept it.

Step 5: When you confirm the agreement you will get the list of the Enterprise View products that require host installation:

22

• Enterprise View • Enterprise View Portal • UNIX Custom Agent • Data Integration for Enterprise View • Java Development Kit 1.5

In order to perform the proper installation, you must start with one of the first three products. The installation of Data Integration for Enterprise View and Java Development Kit 1.5 can be started only if you have Enterprise View already installed. Launch the Enterprise View installation by choosing option 1. If you want to quit, type q.

Step 6: You will be informed of the available disk space requirements. Confirm the installation by typing y.

Step 7: When you confirm the installation, you will be asked if the default directory where the product will be installed is convenient or if you want to create a custom one. Press Enter to select the directory given by default, or type the name of the custom one.

The default location where you install your Enterprise View product is: /opt/microfocus/enterpriseview.

If you choose a different directory, the name of the path must be no longer than 51 characters.

Step 8: You will be asked if you want the directory that you choose to be created.

Step 9: Confirming the previous step by typing y, you will get the levels and combinations of the operating system components which are used for building the product. You can run this product on component versions that are different from those listed, but the product is only fully guaranteed on identical environments. Note: You can see the details of the reference environment for your chosen environment, which are available in the file EnterpriseView/Documentation/env.txt.

Below is an example of env.txt for Linux (the layout for AIX and Sun is similar):

------Micro Focus Enterprise View 5.6.0 ------

This product is certified on the following reference environments:

Installation Guide 23

The commands used to gather the information are listed below their corresponding entry.

Operating System ------Linux 2.6.9-42.0.8.ELsmp Linux 2.6.9-55.0.2.ELsmp Linux 2.6.9-55.ELsmp -s uname -r

C Compiler ------cc gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-3) gcc --version | -1

C++ Compiler ------g++ g++ (GCC) 3.4.6 20060404 (Red Hat 3.4.6-3) g++ --version | head -1

Assembler ------as GNU assembler 2.15.92.0.2 20040927 as --version | head -1

Linker ------ld GNU ld version 2.15.92.0.2 20040927 ld --version | head -1

Unicode ------Unicode mapping tables must be installed for J2EE and Web Services to function correctly. These tables are required for converting between any combination of UTF-16/UCS-2, UTF-8 and other installed locales.

------

Confirm the step by typing y and Enterprise View 5.6 will be installed on your host machine.

Step 10: When the Enterprise View installation is complete, you will be asked if you want to continue with the installation of Data Integration for Enterprise View and Java Development Kit 1.5 products. Follow the instructions displayed to complete both installations. The steps are basically the same as those described above.

24

Note: After you install Data Integration, you need to perform some configurations:

1. Change the "kitchen.sh" script as follows : Replace the line :

JAVA_BIN=java

With the full path of Java installed on your machine, for example:

export JAVA_BIN=/usr/java/jre1.5.0_05/bin/java

where 'java' is the executable.

Remove all the following section from the kitchen.sh script:

********************************************************************** case `uname -s` in AIX) LIBPATH=libswt/aix/ ;;

OS400) LIBPATH=libswt/aix/ ;;

SunOS) LIBPATH=libswt/solaris/ ;;

Darwin) LIBPATH=libswt/osx/ JAVA_BIN=libswt/osx/java_swt chmod +x $JAVA_BIN ;;

Linux) ARCH=`uname -m` case $ARCH in x86_64) LIBPATH=libswt/linux/x86_64/ ;;

i[3-6]86)

Installation Guide 25

LIBPATH=libswt/linux/x86/ ;;

ppc) LIBPATH=libswt/linux/ppc/ ;;

*) "I'm sorry, this Linux platform [$ARCH] is not yet supported!" exit ;; esac ;;

FreeBSD) ARCH=`uname -m` case $ARCH in x86_64) LIBPATH=libswt/freebsd/x86_64/ echo "I'm sorry, this Linux platform [$ARCH] is not yet supported!" exit ;;

i[3-6]86) LIBPATH=libswt/freebsd/x86/ ;;

ppc) LIBPATH=libswt/freebsd/ppc/ echo "I'm sorry, this Linux platform [$ARCH] is not yet supported!" exit ;;

*) echo "I'm sorry, this Linux platform [$ARCH] is not yet supported!" exit ;; esac ;;

26

HP-UX) LIBPATH=libswt/hpux/ ;; CYGWIN*) ./Kitchen.bat # exit ;;

*) echo Kitchen is not supported on this hosttype : `uname -s` exit ;; esac

**********************************************************************

In the JAVA execution, add the two variables as follows ($VARSOURCE $VARTARGET):

$JAVA_BIN $OPT $VARSOURCE $VARTARGET be.ibridge.kettle.kitchen.Kitchen "$1" "$2" "$3" "$4" "$5" "$6" "$7" "$8" "$9"

After you open the client and log in as ADMIN, some configurations are performed on the EVKitchen.sh file which is situated in the directory:

enterpriseview\job\DBAlias_

If you are using direct connection, all configurations are performed automatically. If you are using OCI connection, you must perform some configurations on this file manually. Fill in the IP address or machine name of the Oracle server. The default port number is 1521, but if you are using a different port, you must change it.

VARSOURCE="-Ddb.source.host= - Ddb.source.name=orasr629 -Ddb.source.port=1521 - Ddb.source.usr=MVT17255 -Ddb.source.=MVT17255" VARTARGET="-Ddb.target.host= - Ddb.target.name=orasr629 -Ddb.target.port=1521 - Ddb.target.usr=MVT17255 -Ddb.target.pwd=MVT17255"

Save the file using UNIX separator.

Installation Guide 27

Step 11: Follow the same operations as described in the previous steps (from 5 to 10) in order to perform the installation of the Enterprise View Portal and UNIX Custom Agent products.

6.2. Non-CD Installation

If the UNIX or Linux system does not have a CD or DVD drive, install the product by mounting the appropriate disc on another machine, transferring the product to your machine, and then running the installation.

The instructions below take you through this procedure. Before you start, make sure you have enough disk space for the product. The space needed is the same as the size of the tar files you use (See Step 2 below). In addition, you need the same amount of temporary space to store the tar files.

Step 1: the CD or DVD on the target machine.

Step 2: Look at the file v5600.txt which is in the main setup directory. This lists the directory names and the products those directories contain. It also shows the sizes of the tar files.

Step 3: Change to the directory containing the product you want to install.

Step 4: Select the product you want to install, and transfer that file (you can copy it on the target machine by using ftp or other transfer protocol) to a temporary directory on the target machine.

Step 5: Log in as root on the target machine where the host installation will be performed.

Step 6: Create the directory where you want to install the product. For example: /opt/microfocus/enterpriseview

Step 7: Decompress and extract the contents of the tar file into one directory. For example: cd /opt/microfocus/enterpriseview

by using the command below: /tmpdir/enterpriseview.tar.gz | gzip -d - | tar xf -

Step 8: Run the install script in that directory: sh ./install.sh

The rest of the installation is the same as in the previous part. Follow the instructions to complete the installation.

28

6.3. Post-Installation

When you have installed the product, ensure that the environment is set correctly so Enterprise View can access the Oracle OCI libraries. Add to the environment variable LD_LIBRARY_PATH the location of the OCI libraries, and of any other required run-time libraries like libgcc.

6.3.1. Update .bash_profile Below is an example of .bash_profile file for Enterprise View user (if the user shell is bash):

# .bash_profile

# Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi

# User specific environment and startup programs export ORACLE_BASE=/opt/oracle export ORACLE_HOME=/opt/oracle/ora92 export ORACLE_SID=orabg2 export ORACLE_TERM=xterm export ORACLE_OWNER=oracle export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib:/usr/local/lib

PATH=$PATH:$HOME/bin export PATH unset USERNAME

• LD_LIBRARY_PATH: lets you retrieve all the required run-time libraries Note: On AIX, you must replace LD_LIBRARY_PATH with LIBPATH. On Sun, instead of LD_LIBRARY_PATH use LD_LIBRARY_PATH_64. • ORACLE_BASE: the ORACLE base directory. • ORACLE_HOME: the ORACLE engine home directory. • ORACLE_SID: the unique database identifier. • PATH: includes the ORACLE bin directory for access to the ORACLE applications. • Samba sharing: the users must be also configured to directly access the server machine by using Samba. • If you have installed Enterprise View Portal, you must export the JAVA_HOME or JRE_HOME environment variable. If jdk is installed in the default location, enterpriseview/jdk1.5.0_11/, the row which must be added to .bash_profile is:

export JRE_HOME=/home/apm/enterpriseview/jdk1.5.0_11/jre

Installation Guide 29

Note: Enterprise View now provides NLS (National Language Support). To have NLS support, write and export the following three variables in your profile file:

LANG=en_US.ISO8859-1 export LANG

ORA_NLS33=/opt/oracle/ora92/ocommon/nls/admin/data export ORA_NLS33

NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 export NLS_LANG

Note: For ORA_NLS33, you must specify the correct location, depending on your Oracle installation folder. Note: In the environment properties (see Work with Environment Properties in Configuration Manager), there is a section ‘COMMON’ where you can the NLS_ENCODING property. The values of this property can be NONE (no NLS support) and ISO8859-1. The languages covered by ISO8859-1 are:

Albanian Greenlandic Basque Icelandic Breton Irish Gaelic (new orthography) Catalan Italian Danish Latin Dutch Luxemburg English Norwegian Faroese Portuguese Finnish Rhaeto-Romanic French (almost complete coverage) Scottish Gaelic Fresian Spanish Galician Swedish German

6.3.2. Create home directory for Enterprise View

Go to /opt/microfocus and create three new directories. Create these directories when you are still logged in as root. mkdir Source mkdir Repository mkdir AWD

The “Source” directory will be used to store source files for analysis. The “Repository” directories will be used to store previously analyzed sources. “AWD” is the Agent Working Directory for any incoming transmission.

30

Specify the user and group that you want to have access to the Enterprise View directories. The example for user “evuser” and group “evgrp” is: –R evuser /opt/microfocus –R evgrp /opt/microfocus

In order to allow direct access to the product installation directory for the users, each of them can create a symbolic to it in their home directories. From the user’s home directory type: -s /opt/microfocus/enterpriseview enterpriseview

Installation Guide 31

7. Enterprise View Portal Installation

In order to setup the Portal, follow the same steps as for the installation of the Host. Go to the chapter Enterprise View Host Installation and follow these steps: • From Step 1 to Step 10 - if you have not installed any other Enterprise View product (Host or Custom Agent) yet. • From Step 5 to Step 10 – if you have already installed any of the other Enterprise View products.

When you get to Step 5, select Option 2 from the list of products.

Perform some configurations:

Step 11: Enter the default web server port. If you do not enter anything, the default one is 8080. You can select it if you press Enter.

Step 12: Enter the Oracle server machine name. The name written in brackets is the default one. Press Enter to select it if you do not want to enter a different Oracle server machine name.

Step 13: Enter the Oracle database port. If you want to use the default one (1521), press Enter.

Step 14: Enter the Oracle service name.

Step 15: Enter the Oracle user name.

Step 16: Enter the Oracle user password. The default one is the same as the user name. To select it, press Enter.

Step 17: The installation is completed successfully.

If, for some reason, you start the installation again, you might experience some problems so we recommend that you perform the configurations manually:

Change to "mfev-portal-server/conf/server.xml" Update the port number to match your settings in the following line, by updating the content of 'port' tag:

Change to "mfev-portal-server/webapps/ROOT/META-INF/context.xml" Update the database connection string and Username / Password.

Change to "mfev-portal-server/webapps/ROOT/WEB-INF/web.xml"

32

Update the 'solution-path' and 'base-url' to reflect the correct path and the Server's IP Address.

Before you start, make sure that the environment variable JAVA_HOME is correctly set, for example (extracted from .bash_profile):

PATH=/usr/java/jdk1.5.0_12/bin:$PATH export JAVA_HOME=/usr/java/jdk1.5.0_12

Note: For the Portal to function properly, you should install Data Integration for Enterprise View and Java Development Kit 1.5.

To start the server, go to the folder "mfev-portal-server/bin" and type:

./startup.sh

To stop it, type:

./.sh

in the same folder.

The Portal can also be started and shut down from the Enterprise View menu, ONLY if it is installed in the default directory together with the engine:

Choose application to start:

1. Start Daemon 1 2. Start Daemon 2 3. Start all Daemons 4. Start Agent 5. Start Custom Agent 6. Start Portal 7. Shutdown Portal 8. Back

Installation Guide 33

8. Client Installation

The client modules are installed using the classic setup procedure of the Windows platform. Follow these steps at this stage of the installation:

• Client modules installation • Database connection configuration • Alias Manager

8.1. Client Modules Installation

Step 1: Start the setup.exe program on the Enterprise View installation CD. Your default browser will open and display the “Welcome to Micro Focus Enterprise View” page.

Step 2: Click Install Client Modules under Step 3 on the page.

Step 3: The Enterprise View 5.6 Setup Wizard appears. Click Next to continue. Note: If your default browser is Mozilla Firefox, the “Opening client” dialog box will appear. When you click OK, the Setup Wizard will appear.

Step 4: The License Agreement window appears. Read the License Information and select ‘I Agree’ to accept the License Agreement. Click Next.

Step 5: The Select Installation Folder window will appear. The setup program proposes a default folder where the client modules will be installed. We recommend you accept it. If you want to change the default folder, use the Browse button. If you click Disk Cost, you will see a list of all drives where you can install the client modules, along with their required and available disk space. This form lets you choose whether to install the tool only for yourself or for all users working on this machine. Click Next to continue.

Step 6: This window lets you select whether to start the Navigator after the installation is completed. Click Next to continue.

Step 7: The Confirm Install window will appear. Click OK to start the installation.

Step 8: The next window shows the progress of the installation and when it is completed, you will be informed that Enterprise View 5.6 has been successfully installed. Click Close to exit the Wizard.

Step 9: Now Enterprise View Client Modules have been installed. You can start the Navigator from Windows Start Menu/Programs.

34

8.2. Starting Navigator for the first time

When starting Enterprise View for the first time, you must choose a Database Alias that establishes a connection to the database.

Step 1: Now you have the Navigator icon on your desktop. Click the icon to start the Navigator for the first time.

Step 2: The Import aliases window will appear, because you do not have any user- defined aliases yet. It offers you three options:

• Import alias from Enterprise View Portal • Import alias from XML file • Create alias manually

Step 2.1: If you choose the first option, you will be asked to enter the Portal URL. If you check Use Port, the port number will be included too. The link to the file containing the aliases that you want to import appears below the URL.

Step 2.2: If you choose to import aliases from an XML file, a dialog box will appear, from which you can select the file containing the aliases. The file generated by the installation procedure is in the job folder of the UNIX installation folder.

When the aliases are imported, a window with a list of Aliases will appear. It contains a grid with various columns giving information about the alias name, schema name, description, connection type (OCI or Direct), connection string, user name, and system flag. If System Flag is checked, the selected alias can be edited only by the Administrator. The Connection String column shows the OCI Alias if the connection type is OCI, and the host and port if the connection type is Direct. Use OCI (Oracle Call Interface) connection when you have Oracle Client installed on your client machine. Otherwise we recommend direct connection.

Save the changes in the common.cfg file by clicking Save in the lefthand part of the window. Then click Exit to close the window.

Step 2.3: If you choose to create an alias manually, the Alias Manager window will appear, with one alias (SAMPLE) in the grid. Click New to go to the Alias Wizard.

8.3. Alias Wizard

The Alias Wizard guides you through the creation of a new database connection definition.

Step 1: Fill in the following fields:

Installation Guide 35

Name: Enter a database name. You can fill in a mnemonic name for your database. Description: Enter a description of your choice.

Step 2: Click Next to continue.

Step 3: Fill in the fields to provide connection information:

Connection Type: Select the connection type from the dropdown list: OCI or Direct. Depending on the connection type you have selected, provide the following information: • OCI connection OCI Alias: Enter a valid OCI alias name. The OCI aliases are created and edited from the Oracle Client software. • Direct connection Oracle DB Name: Enter the name of the Oracle database (SID). Hostname: Enter the name of the Oracle host machine. Port: Enter the port number of the Oracle Listener. The default port number is “1521”. Please contact your System Administrator in order to obtain the Listener Port Number currently associated to the database.

Step 4: Click Next to continue.

Step 5: Provide the following information in the next window to define login information:

User Name: Enter the schema name. By default, the Enterprise View DB Install module creates a user with the same name as the schema.

Password: Enter the user name. By default, the DB Install module assigns a password which matches the user name. This field is encrypted. You can use and operations to fill it in.

Default Schema Name: Select the schema name previously created by the Enterprise View DB Install module.

Step 6: Click Test to verify the information provided.

Step 7: If the test is successfully executed, an information window telling you that the connection test is successful will appear. Click OK to continue.

Step 8: If the test has passed successfully, click Finish and then Close.

Step 8.1: If the parameters are wrong, an error window will appear. Click OK to correct the parameters.

Step 8.2: The Login to Database window will appear. Click Cancel without changing the username and password.

36

Step 8.3: An error message (“Connection test failed!”) will be displayed. Click OK to continue.

Step 8.4: Check the parameters again as in Step 5 until an information window telling you that the connection test is successful appears. Click OK to continue.

Step 9: The Alias Manager window will appear. Save the changes in the common.cfg file by clicking Save in the top lefthand part of the window. Then click Exit to close the window.

Step 10: A list of aliases will appear. • Check the Favorite box if you want to have this alias appear in your Favorites tabsheet. • Check the Default box if you want Enterprise View to start and connect to the defined database.

Click OK to confirm your settings.

Step 11: The Favorites tabsheet displays your favorite databases. Connect to the defined database by double-clicking the icon, or by clicking it once and then clicking OK.

8.4. Settings

Step 1: When you start the Navigator window for the first time, the following warning window will appear: ‘For the correct function of the application, some settings should be configured!’ Click OK to configure the mandatory settings.

Step 2: The Options window will appear. Provide the following information in this window using the Explore buttons :

• Root Path: The drive letter of the previously mapped Enterprise View host share. • Path of the Linux Module: The path where the host programs are installed. • Repository Path: The path where the host programs will store repository data. • Disk Directory: The host representation of the previously mapped network drive (Root Path). • Documents and Images shared path: Usually this is a network mapped share containing common documents and icons used by Enterprise View modules.

Step 3: Click Apply to load the new information. Click OK to finish.

8.5. Starting Navigator

Installation Guide 37

The Navigator module is now started.

Step1: Now Enterprise View will load the Navigator login window for the first time. Enter the user name and password in the Login form and click OK to continue. The default username and password are ADMIN/ADMIN. After the first connection, we strongly recommend you change the password for the ADMIN user.

Step 2: Model Selection:

A model is a combination of different organization views. Each model contains main organization views, which themselves contain organization views, where the data is grouped according to certain criteria. Each generated model preserves the information about the main parameters (database, schema name, file name) as well as the filtering parameters specified by the user.

If you have authorization for just one model, when you log in for the first time, this model will be automatically selected as default, and you will not be asked to select a model.

If you are authorized for than one model, the Select Model window will appear. From this form you can choose and activate a model.

Select it and click OK to confirm the model selection. The modules of the product will be loaded.

38

Installation Guide 39

9. Client Installation on Citrix Server

To install Enterprise View on a Citrix server (the supported version is Citrix Metaframe Presentation Server 4.0), perform the following steps:

Step 1: In Manage Your Server, click Administrative Tools.

Step 2: Click Control Panel.

Step 3: In Control Panel, click Add or Remove Programs.

Step 4: Click CD or Floppy.

Step 5: Insert the installation CD and click Next.

Step 6: Run the installation program.

Step 7: When the installation is complete, click Finish.

For Database Connection Configuration and Alias Manager, see the chapter Client Installation.

9.1. Enterprise View Publishing

When Enterprise View is installed, authorize users to use it by going through the following steps.

Step 1: Open the server management console and select Enterprise View.

Step 2: Click Actions > New > Published Application.

Step 3: The Application Publishing Wizard appears. Enter the name of the application that you want to publish (Enterprise View) and some description, then click Next.

Step 4: Specify What to Publish – choose application type (in this case – ‘Application’) and enter the command line and working directory (for example: C:\Program Files\Micro Focus\Enterprise View 5.6). To enter the command line, click Browse.

Step 5: Choose the application that you want to publish (Navigator.exe) from the directory where it is located (for example: “C:\Program Files\Micro Focus\Enterprise View 5.6\Navigator.exe”) and click OK.

40

Step 6: When you click Next, another window appears, which lets you specify some settings that control application launching in Program Neighborhood, such as application shortcut placement and the application icon. After you make the necessary settings, click Next.

Step 7: The next windows let you specify various settings: specify application appearance, client requirements, application limits, and configure access control. Then you are asked to choose the server on which Enterprise View will run.

Step 8: Specify the user who will run Enterprise View. Click Add List of Names and a window will pop up. Enter the names there and click OK. The names will appear in the Configured accounts field. Click Next to go to the next step.

Step 9: The next step lets you specify file type associations. Click Next and Enterprise View will be published.

The authorized users should have a Citrix client installed on their machines in order to access Enterprise View. If you want them to access it from within a familiar browser environment, then the Web Client should be installed. It is packaged in an MSI file called Ica32Pkg.msi (for 32-bit Windows).

Installation Guide