
=================================
Trigo Enterprise 4.2.0.14#07  Installation
=================================

DISCLAIMER
Trigo Technologies, Inc. disclaims all warranties or representations herein, whether 
express, implied or statutory, to the fullest extent permissible by law, including the 
implied warranties of title, fitness for a particular purpose and merchantability.

COPYRIGHTS
Copyright # 2001, 2002 Trigo Technologies, Inc. All rights reserved.

Information in this document is subject to change without notice. No part of this 
publication may be reproduced, stored in a retrieval system, or transmitted in any form 
or any mean electronic or mechanical, including photocopying and recording for any 
purpose other than the purchaser's use, without the written permission of
Trigo Technologies, Inc.

Trigo Technologies, Inc.
8000 Marina Blvd, Suite 810
Brisbane, CA 94005
U.S.A.
www.trigo.com

TRADEMARKS
Trigo, Trigo Enterprise, Trigo Content Suite, Trigo Commerce Suite, and Trigo 
Platform are trademarks or registered of Trigo Technologies, Inc.  All other company 
and product names are trademarks or registered trademarks of their respective 
owners.



---------------------------
Trigo Technologies Overview
---------------------------

Trigo Enterprise is a highly scalable web-based enterprise-class 
application. It was designed to take advantage of modern 
technologies and maintain compliance with open standards. 



Key Architectural Elements
===========================

# 100% Web-based Application
# 3-Tier Architecture (Database, App Server, Client)
# 100% Java- based, J2EE Compliant



System Requirements
===================

To install Trigo Enterprise, the following minimum hardware and 
software are recommended:

Note:
    Plan hardware considerations based on the choice of software used and the
    projected load volume of the servers 
    (i.e. the number of SKU's and transaction rates.)



Web and Application Server Requirements 
=======================================

Hardware:
Intel Pentium III 1.2 GHz or
Sun UltraSPARC III Cu 900 MHz Processors


Number of CPUs: 2

Memory: 4GB

Hard Drive Space: 20GB

Operating System:
Sun Solaris 2.8 or
Linux or
Windows 2000

Application Server:    Tomcat 3.2.4 
                    or Tomcat 3.3.1
                    or WebLogic 6.1
                    or WebLogic 7.0

Web Server: Apache 1.3.26

Java Virtual Machine:
Java 2 Runtime Environment, Standard 
Edition (Build 1.3.1_02)



Database Management System Requirements 
=======================================

Database Management System: Oracle 8i Release 4

Hardware:
Intel Xeon 700 MHz or
Sun UltraSPARC III Cu 900 MHz Processors or higher

Number of CPUs: 4

Memory: 8 GB

OS Storage: 2 x 18 GB Drives

DB Storage -
Variable 4 x 18 GB drives or as determined 
by Trigo Storage Spec Calculations



Software Prerequisites for unix
===============================

The following applications are required for the run-time environment:

# GNU zip v1.3 or higher
# GNU bash v2.05 or higher
# GNU awk v3.1.0 or higher
# GNU grep v2.4.2 or higher
# GNU tar v1.13.19 or higher
# GNU textutils v2.0 or higher
# GNU sed v3.02 or higher

These packages can be downloaded from www.sunfreeware.com.

Note:
    On Solaris operating systems, install the Sun packages using:
    pkgadd -d <package name>


Software Prerequisites for windows
==================================

# cygwin 2.78.2.11



Client System Requirements
==========================

Browser: Internet Explorer 6.0 or higher

Operating System: Windows 2000



-----------------------------
Trigo Enterprise Installation
-----------------------------

To install and configure the Trigo 4.2.0.14#07  Enterprise environment on a Sun, 
Linux or the Windows 2000 operating system, perform the tasks as they are 
ordered in this chapter. 

Use the checklist on the following page and check each item as they are 
completed.

Things to note before installation:

# Create a user with the proper privileges and user profile, as required.
# Bash must be installed in the directory /bin/bash.
# It is assumed that bash is used as the default shell script. If using sh, execute bash first.

 

Trigo Installation Checklist
============================

UNPACK TRIGO FILES

SETUP SHELL ENVIRONMENT
1. Set TOP Variable
2. Verify Trigo Files
3. Set Common Unix Utilities (on windows and unix)
4. Set Path to SQLPlus
5. Set Home Directory for java
6a. Set Home Directories for DB2 client instance (for DB2 installation)
6b. Set Home Directories for tomcat (for tomcat installation)
6c. Set Home Directories for weblogic (for weblogic installation)
6d. Set Home Directories for websphere (for websphere installation)
6e. Setting memory flags for different modules
7. Source $TOP/setup/init_trigo_vars.sh

CONFIGURE RUN TIME PROPERTIES
1. Setup Database Information
2. Setup Timezone
3. Setup Ftp Directory
4. Setup Tmp Directory

SETUP APP SERVER PROPERTIES
1a. Set tomcat properties (for Tomcat 3.2.4 installation)
1b. Set tomcat properties (for Tomcat 3.3.1 installation)
2. Set trigo webserver port

SETUP DATABASE SCHEMA
1. Create Database User
2. Create Database Schema

SETUP THE DEMO COMPANY
1. Create a Company

TEST TRIGO INSTALLATION
1. Start Trigo Application
2. Check RMI Status
3. Login to Trigo
4. Stop the Trigo Application



UNPACK TRIGO FILES
==================

To extract the Trigo installation files, do the following:

1. Copy the Trigo tar file trigoV42014#07 .tgz to the user or temporary directory.

2. Unpack the tar file. 

GNU TAR - The following command extracts and unzips the tar file:
	tar xfz trigoV42014#07 .tgz

Note:
    GNU tar is needed to untar the Trigo application files.
    For windows, unpack the Trigo application files in cygwin
    console.

Note:
	The default subdirectory "trigoV42014#07 " is created. If needed, move 
    the subdirectory to an alternate location.
	
After the Trigo installation tar file has been extracted, the next step is to 
setup the shell environment.



SETUP SHELL ENVIRONMENT
=======================


1. Set TOP Variable
-------------------

Purpose:
To set the shell variable TOP to point to the Trigo 
installation directory.

Example on unix:
    If the application is installed in the directory:
        /home/user/john/trigoV42014#07 

    Then, from the command-line:
        export TOP=/home/user/john/trigoV42014#07 


Example on windows:
    If the application is installed in the directory:
        c:/trigoV42014#07 

    Then, from the command-line:
        export TOP=c:/trigoV42014#07 


2. Verify Trigo Files
---------------------

Purpose:
To verify that all files required by the Trigo installation are 
accounted for and have been installed correctly.
	
Execute the shell script:
	
	$TOP/setup/verify_filelist.sh
	
The result is the output of a regular diff command.
	
	# Lines starting with "<" refer to files added after the installation
	# Lines starting with ">" refer to files missing from the installation
	
Note:
    A successful installation shows the following:
	Status: Perfect. All the Trigo files are present.



3. Set Common Unix Utilities (on windows and unix)
--------------------------------------------------

Purpose:
    To set the properties to the common UNIX utilities.

Edit the following file:

    $TOP/setup/init_trigo_vars.sh

Set Properties:
    AWK
    CP
    ECHO
    GREP
    MKDIR
    RM
    SED
    TOUCH
    TR
    BC
    CAT


4. Set Path to SQLPlus
----------------------

If you plan on running any of the database scripts 
(to create the schema or create a new company), you
will need SQLPlus.

Edit the following file:
    $TOP/setup/init_trigo_vars.sh

Set Property:
    SQLPLUS

5. Set Home Directory for java
------------------------------

Purpose:
    To set the default home directories for Java.

Edit the following file:
    $TOP/setup/init_trigo_vars.sh

Set the following property
    JDK_HOME: home of the JDK Java Development Kit

ex on unix:
    JDK_HOME=/usr/local/j2sdk1.4.0

ex on windows:
    JDK_HOME=c:/jd2sdk1.4.0



6a. Set Home Directories for DB2 client instance (for DB2 installation)
-------------------------------------------------------------

Edit the following file:
    $TOP/setup/init_trigo_vars.sh

Set the following property:
    DB2_HOME: home of the db2 client instance

ex on unix:
    DB2_HOME=/home/db2inst1/sqllib



6b. Set Home Directories for tomcat (for tomcat installation)
-------------------------------------------------------------

Edit the following file:
    $TOP/setup/init_trigo_vars.sh

Set the following property:
    TOMCAT_HOME: home of Tomcat

ex on unix:
    TOMCAT_HOME=/usr/local/jakarta-tomcat-3.2.4

ex on windows:
    TOMCAT_HOME=c:/jakarta-tomcat-3.2.4



6c. Set Home Directories for weblogic (for weblogic installation)
-----------------------------------------------------------------

Edit the following file:
    $TOP/setup/init_trigo_vars.sh

Set the following property:
    WL_HOME: home of weblogic
    TRIGO_WL_PW: password to start the weblogic server
    TRIGO_WL_USER: user to start the weblogic server (only for weblogic 7.0)

You might also want to change the following options:
    TRIGO_WL_DOMAIN_DIR: home of the weblogic trigo domain
    TRIGO_WL_DOMAIN: domain name for the trigo domain
    TRIGO_WL_SERVER: server name for the trigo domain

On windows, you will also need to set:
    WL_HOME_UNIX_STYLE: home of weblogic, using a unix-like path.

ex on unix:
    WL_HOME=/usr/local/bea/wlserver6.1
    TRIGO_WL_PW=password
    TRIGO_WL_USER=user
    TRIGO_WL_DOMAIN_DIR=$TOP/etc/default/weblogic/config/trigo_domain
    TRIGO_WL_DOMAIN=trigo_domain
    TRIGO_WL_SERVER=trigo_server

ex on windows:
    WL_HOME=c:/bea/wlserver6.1
    WL_HOME_UNIX_STYLE=/cygdrive/c/bea/wlserver6.1
    TRIGO_WL_PW=password
    TRIGO_WL_USER=user
    TRIGO_WL_DOMAIN_DIR=$TOP/etc/default/weblogic/config/trigo_domain
    TRIGO_WL_DOMAIN=trigo_domain
    TRIGO_WL_SERVER=trigo_server


You also need to copy the files fileRealm.properties
(for weblogic 6.1 and 7.0) and SerializedSystemIni.dat
(for weblogic 6.1) from your default weblogic installation
directory into the domain directory for your trigo
weblogic domain.

The files should be located in the directory:
    $WL_HOME/config/mydomain (for weblogic 6.1)
    $WL_HOME/../user_projects/config/mydomain (for weblogic 7.0)

and should be copied into:
    $TRIGO_WL_DOMAIN_DIR

So, after if you have set the variables WL_HOME
and TRIGO_WL_DOMAIN_DIR, just do:
    cp $WL_HOME/config/mydomain/fileRealm.properties $TRIGO_WL_DOMAIN_DIR
    cp $WL_HOME/config/mydomain/SerializedSystemIni.dat $TRIGO_WL_DOMAIN_DIR



6d. Set Home Directories for websphere (for websphere installation)
-------------------------------------------------------------

Edit the following file:
    $TOP/setup/init_trigo_vars.sh

Set the following property:
    WAS_HOME: home of WebSphere

ex on unix:
    WAS_HOME=/usr/WebSphere/AppServer



6e. Setting memory flags for different modules
-----------------------------------------------------------------
    All the different trigo modules are run using a java virtual machine.
    The memory used for these modules can be specified by the user by changing
    the memory flags provided for this purpose. These are specified in the file 
    $TOP/setup/init_trigo_vars.sh. 

    For example, the entry: 

            export SCHEDULER_MEMORY_FLAG='-Xmx64m -Xms48m'

        specifies that the SCHEDULER module has the initial memory setting (specified 
        by the option -Xms) of 64MB and the maximum memory setting (specified by
        the option -Xmx) of 48MB.

    The default values are given for the Sun jdk
    If using the IBM jdk, remove the X character e.g. '-mx64m -ms48m'

    Please refer to the comments in $TOP/setup/init_trigo_vars.sh for more information.



7. Source $TOP/setup/init_trigo_vars.sh
---------------------------------------

Purpose:
    To define the location of the Trigo initialization script.

From the shell prompt:
    . $TOP/setup/init_trigo_vars.sh

    Note:
    The default shell init script .bashrc should be modified to set 
    TOP and source init_trigo_vars.sh.

    Edit .bashrc to include the following:

        # trigo init
        export TOP=<path to trigoV42014#07  directory>
        TRIGO_INIT_VARS=$TOP/setup/init_trigo_vars.sh

        if [ -f $TRIGO_INIT_VARS ]; then
            . $TRIGO_INIT_VARS
        else
            echo "Error: file '$TRIGO_INIT_VARS' not found"
        fi


CONFIGURE RUN TIME PROPERTIES
=============================

The following steps configure the runtime properties used by the 
system, which are defined in the file austin.properties.

Edit the following file:
$TOP/etc/default/austin.properties


1a. Setup Database Information (for Oracle installation)
--------------------------------------------------------

Purpose:
    To setup the information allowing access to the database.

Set Properties: 
    db_userName
    db_password
    db_url

Example:
    Assume the username is "pjenkins", password is "track1", database 
    box has the name "main_database", and the oracle database 
    instance is "pauprd."

The following properties are set:

    db_userName=pjenkins
    db_password=track1
    db_url=jdbc:oracle:thin:@main_database:1521:pauprd

    Note:	The referenced port is the listener port. In the example above, 
    the port is 1521.


1b. Setup Database Information (for DB2 installation)
--------------------------------------------------------

Purpose:
    To setup the information allowing access to the database.

Set Properties: 
    db_userName
    db_password
    db_url

Example:
    Assume the username is "pjenkins", password is "track1", db name is pauprd

The following properties are set:

    db_userName=pjenkins
    db_password=track1
    db_url=jdbc:db2:pauprd

    Note: The database pauprd must be catalog'ed on the current database client instance


2. Setup Timezone
-----------------

Purpose:
    To define the time zone property.

Property: timezone

Use the following values:

#	-8 for PACIFIC
#	-7 for MOUNTAIN
#	-6 for CENTRAL
#	-5 for EASTERN

Example:
If business hours are set for the West Coast U.S, then set the 
following:

    timezone=-8


3. Setup Ftp Directory
----------------------

Purpose:
    To define the directory where data files are transferred to 
    using ftp (for an aggregation).

Property: ftp_root_dir

ex on unix:
    ftp_root_dir=/u01/ftp/

ex on windows:
    ftp_root_dir=c:/u01/ftp/


Note:
    The ftp directory ends with a forward slash '/'. Trigo reads 
    from and writes to this FTP directory.


4. Setup Tmp Directory
----------------------

Purpose:
This setting identifies the temporary directory on the local box.

Property: tmp_dir

ex on unix:
    tmp_dir=/tmp/

ex on windows:
    tmp_dir=c:/tmp/


Note:
    The tmp directory ends with a forward slash '/'.



SETUP APP SERVER PROPERTIES
===========================

1. Set tomcat properties (for Tomcat 3.2.4 installation)
--------------------------------------------------------

The following steps configure the properties for Tomcat. The 
properties are defined in the file server.xml.

Edit the following file:
    $TOP/etc/default/tomcat/server.xml


Replace all string references "<PATH_TO_TOP>" with the location of 
the Trigo installation directory.


ex on unix:
    If the Trigo application is installed in:
        /home/user/john/trigoV42014#07 

    Replace <PATH_TO_TOP> with:
        /home/user/john/trigoV42014#07 


ex on windows:
    If the Trigo application is installed in:
        c:/trigoV42014#07 

    Replace <PATH_TO_TOP> with:
        c:/trigoV42014#07 



2. Set trigo webserver port
---------------------------

By default, the port used is 7507.
If you want to use a different port:

for tomcat 3.2.4:
    modify properties appsvr_port, tomcat_ajp12 and tomcat_ajp13 in $TOP/etc/default/tomcat/server.xml

for tomcat 3.3.1:
    modify properties trigo_ajp12 and trigo_ajp13 in $TOP/etc/default/tomcat/server.xml
    modify property appsvr_port in $TOP/etc/default/austin.properties

for weblogic:
    modify $TRIGO_WL_DOMAIN_DIR/confix.xml
    modify property appsvr_port in $TOP/etc/default/austin.properties



SETUP DATABASE SCHEMA
======================

Before the database schema is setup, create a separate table space 
for Trigo.

Note:
    The file austin.properties must be setup before creating the 
    database schema. (Refer to the section "Configure Run Time 
    Properties" in this chapter)


1. Create Database User
-----------------------

Verify that the database user referenced in austin.properties exists 
in the database with the proper privileges. 

Execute the following shell script to test the user's access to the 
database:

    $TOP/bin/test_db.sh

The script attempts to parse austin.properties and login to your 
database.

    # If the script executes without an error, the Oracle SQL prompt 
    appears. Exit SQLplus by typing "exit."
    # If the script produces an error, please modify the 
    austin.properties file or verify with the Database 
    Administrator that the database user was created correctly.

    Note: 	Please make sure 
    <oracle_home>/network/admin/tnsnames.ora is setup 
    correctly by the Database Administrator to allow connection 
    to the database.


2. Create Database Schema
-------------------------

Once the db user is setup correctly, the Trigo database schema can 
be created.

Execute the shell script:

    $TOP/src/db/schema/create/create_schema.sh

The script first shows which database it is trying to connect to. Then 
the system prompts the user to confirm with "y" to continue or "n" to 
stop.

Type "y" to continue.

Note:
    If this is the first time setting up a database schema, errors 
    may appear, which can be ignored. 



SETUP THE DEMO COMPANY
======================

This section sets up a company that is used to test the Trigo 
installation. A company must be created in order to login to Trigo.


1. Create a Company
-------------------

To login to Trigo, a company must be created. Do one (or both) of the 
following to create a company:

    1.Create Acme Company
    To create a demo company called "acme", execute the following shell 
    script:

        $TOP/src/db/schema/acme/create_acme.sh --code=acme

    2.Create Empty Company
    To create an empty company called "demo", with no predefined data 
    (quicker than creating the demo acme company), execute the 
    following shell script:

        $TOP/src/db/schema/cmp/create_cmp.sh --code=demo


    The company Acme is created with four users:
    #  Admin 
    #  bwilson
    #  jwilson
    #  vjackson

    The company demo is created with a single user:
    #  Admin

    Note:  The passwords are the same for all the users: trinitron. The 
    password is case-sensitive.

    The Admin user is created with full privileges and should be 
    used by an administrator.



TEST TRIGO INSTALLATION
========================


1. Start Trigo Application
--------------------------

To start the Trigo application, execute the following script:

    $TOP/bin/go/start_local.sh

The script starts all the services needed to run Trigo.

Note:
    This process should take approximately 30-40 seconds, 
    depending on the speed of the processor.

Note:
    On windows, you should not close the cygwin window
    otherwise all the currently running processes
    will be killed.

1b. Trigo Application Services and the License file
---------------------------------------------------
The $TOP/bin/go/start_local.sh script above starts all the trigo application
services (or modules) needed to run Trigo. Each module can be successfully
started only if there exists a valid license file: $TOP/etc/default/trigo_license.xml
and the license specifies that the module is valid.

Otherwise, the module will fail to start. The errors are logged in to the specific 
log files for each module in the directory: $TOP/logs/svc.




2. Check RMI Status
-------------------

Verify that the application is up and running by executing the following 
script:

    $TOP/bin/go/rmi_status.sh

This script contacts the RMI daemon on all the machines in the cluster 
and get a list of the local services on each machine.  A long list of names 
is returned.

Verify that the following services have started:
admin_<machine name>
appsvr_<machine name>
eventprocessor
queuemanager
scheduler
workflowengine


3. Login to Trigo
-----------------

Open the Internet Explorer web browser and enter the URL and port for 
the web server.

Example:
    http://www.acme.com:7507

Note:
    During the Trigo installation, the default port was set to 7507.
    If you want to use a different port, refer to is used, change the port reference in the file 
    server.xml.

Using the Acme company demo, login as:

Username: bwilson
Password:  trinitron
Company Code: acme

If the login to the Trigo application opens up the Trigo Home Page, the 
installation was successful. Logout of the application and continue to the 
next step.


4. Stop the Trigo Application
-----------------------------

To stop the Trigo application on the local machine, execute the following 
script:

    $TOP/bin/go/abort_local.sh

The script stops all the services started by Trigo.


================================================
YOU HAVE SUCCESSFULLY INSTALLED AND TESTED
TRIGO ENTERPRISE 4.2.0.14#07 !
