Sybase Version 2.2 manual Verifying system environment variables

Page 13

CHAPTER 2 Upgrading to version 2.2

•%JAGUAR%\html\classes\com\sybase\ep\portalinterface\tasks

•%JAGUAR%\Repository\IDL\com\sybase\patriotact\filter

2Extract the PATRIOT EBF files into a temporary location.

The target directory of unzipping the EBF archive will be the installation directory of PATRIOT (%PATRIOT% for Windows; $PATRIOT for Solaris)

3Make sure you have ASE and EAServer up and running.

Verifying system environment variables

Follow these steps to verify or set the environment variables required for configuration.

1Verify that the SYBASE environment variable is set. The SYBASE environment variable is the root directory of Sybase applications. For example, SYBASE=/software/sybase (Solaris) or SYBASE=c:\Sybase (Windows).

2Verify that the SYBASE_ASE environment variable is set. This is the directory under $SYBASE (Solaris) or %SYBASE% (Windows) where Adaptive Server Enterprise has been installed. For example, SYBASE_ASE=ASE-12_5.

3Verify that the SYBASE_OCS environment variable is set. This is the directory under $SYBASE (Solaris) or %SYBASE% (Windows) where Open Client/Server has been installed. For example, SYBASE_OCS=OCS- 12_5.

4Set the JAGUAR environment variable. This is the directory under

$SYBASE (Solaris) or %JAGUAR% (Windows 2000) where EAServer has been installed.

Solaris example: JAGUAR=/software/sybase/EAServer

Windows 2000 example: JAGUAR=c:\Sybase\EAServer

5Set the $JAVA_HOME (Solaris) or %JAVA_HOME% (Windows) environment variable. This environment variable points to a directory where a Java JDK is installed.

Solaris example: JAVA_HOME=$JAGUAR/jdk/jdk1.3

Upgrade Guide

7

Image 13

Contents Version PATRIOTcompliance SolutionDocument ID DC00148-01-0220-01 Contents Contents About This Book Font Click MySybase and create a MySybase profileIntroduction PATRIOTcompliance Solution overview Heading A P T E R 2 Upgrading to versionOverview Issues addressed in this releaseUpgrading to version Contents of the 2.2 release Solaris example JAVAHOME=$JAGUAR/jdk/jdk1.3 Verifying system environment variablesWindows example JAVAHOME=$JAGUAR\shared\sun\jdk\jdk.3 Upgrading the Patriot database$PATRIOT/release2.2/database directory PATRIOT%\release2.2\database directory Modifying Patriot connection cachesConnect to Jaguar Manager as jagadmin SYBASE%\ProcessServer-39\bin\edl . This overwrites the set Upgrading Process Server process definitions39\bin\edl directory $SYBASE/ProcessServer-39/bin/edlImporting the new formats Upgrading formatsUpgrading EAServer components Expand Jaguar Manager Servers Jaguar Installed ServicesTo the $SYBASE/nnsy/formats directory Expand Jaguar Manager PackagesExpand Jaguar Manager Servers Jaguar and select Shutdown Expand Jaguar Manager Servers Jaguar Installed PackagesCreating the Loader component Generate Stubs Expand Servers Jaguar Installed Packages PatriotActCompile Java Stubs Click GenerateUpdating the filter properties file Right-clickFTPLoad, choose Component Properties Setting the PATRIOTAct component propertiesRight-clickNightlyFilter, choose Component Properties Right-clickLoader, choose Component PropertiesRight-clickScheduler, choose Component Properties Extract onelogin.zip into $JAGUAR Configuring PortletsSelect Import Portlet from Archive and press Enter Installing updated portletsSelect Import Archived Portlets and then press Enter Creating directories for the class files Installing the Account Management portlet Verifying the Account Management portlet deployment For the Account Management portlet, do this Setting up Account Management for the pacuserCreating the Account Management portlet for pacuser Verifying deployment of the new and updated portletsSetting up the new portlets for pacuser Creating portlet pages for pacuser Index Index Index Index