Sybase Version 2.2 manual Overview, Issues addressed in this release

Page 10

Overview

Overview

This upgrade to the PATRIOTcompliance Solution includes an updated ROLLUP version of the PATRIOT Compliance Starter Kit. Sybase recommends that you install this updated Software Release as soon as possible.

This upgrade is distributed as a zip file and is available for download from the

EBFs/Maintenance page at http://www.sybase.com/downloads.

Warning! Sybase strongly recommends that a backup of all components be done before you begin this upgrade. You must re-create any customization of the PATRIOT solution templates.

Issues addressed in this release

CR#	Description
CR#332858	Previous versions of PATRIOT Starter Kit sometimes allowed
	users to log in more than once with the same login name. Updates
	to the portalinterface.properties allow you to restrict users to a
	single login at a time.
	This step is optional and not required for successful deployment.

CR# 332855	Changes to security.properties allow you to set the number of
	days, months or years that a password remains valid; the default
	is 0, which means passwords are valid indefinitely.
	Duration parameters are expressed in the <number> of days,
	months, or years the password remains valid. Count begins from
	the day you create or modify the password. Changing the
	password via the Account Management portlet before the
	expiration date resets the count.
	EP Security locks users who fail to change their passwords
	within set duration parameters out of the system.

CR# 327011	Pat LoggedIn Users is a new portlet that identifies all users
	currently logged into the system.

4	PATRIOTcompliance Starter Kit

Image 10

Contents PATRIOTcompliance Solution VersionDocument ID DC00148-01-0220-01 Contents Contents About This Book Click MySybase and create a MySybase profile FontIntroduction PATRIOTcompliance Solution overview A P T E R 2 Upgrading to version HeadingIssues addressed in this release OverviewUpgrading to version Contents of the 2.2 release Verifying system environment variables Solaris example JAVAHOME=$JAGUAR/jdk/jdk1.3Windows example JAVAHOME=$JAGUAR\shared\sun\jdk\jdk.3 Upgrading the Patriot database$PATRIOT/release2.2/database directory Modifying Patriot connection caches PATRIOT%\release2.2\database directoryConnect to Jaguar Manager as jagadmin 39\bin\edl directory Upgrading Process Server process definitionsSYBASE%\ProcessServer-39\bin\edl . This overwrites the set $SYBASE/ProcessServer-39/bin/edlUpgrading formats Importing the new formatsTo the $SYBASE/nnsy/formats directory Expand Jaguar Manager Servers Jaguar Installed ServicesUpgrading EAServer components Expand Jaguar Manager PackagesExpand Jaguar Manager Servers Jaguar Installed Packages Expand Jaguar Manager Servers Jaguar and select ShutdownCreating the Loader component Compile Java Stubs Expand Servers Jaguar Installed Packages PatriotActGenerate Stubs Click GenerateUpdating the filter properties file Setting the PATRIOTAct component properties Right-clickFTPLoad, choose Component PropertiesRight-clickNightlyFilter, choose Component Properties Right-clickLoader, choose Component PropertiesRight-clickScheduler, choose Component Properties Configuring Portlets Extract onelogin.zip into $JAGUARSelect 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 Setting up Account Management for the pacuser For the Account Management portlet, do thisVerifying deployment of the new and updated portlets Creating the Account Management portlet for pacuserSetting up the new portlets for pacuser Creating portlet pages for pacuser Index Index Index Index