Sybase Version 2.2 Modifying PATRIOT connection caches, $PATRIOT/release2.2/database directory

CHAPTER 2 Upgrading to version 2.2

Modifying PATRIOT connection caches

PATRIOTcompliance Starter Kit 2.2 includes a script which creates a mechanism for customers who want to make their EP instance use non-sa database logins. These logins include sufficient permissions to let EP applications(s) connect to the patriot database, portal interface, and search cache.

Adding a non-sa user connection involves running a script, ep_login.sql, that creates three new login names PATRIOTdbConnection, PortalInterfaceCache, and epSearchCache. You then open Jaguar Manager in EAserver to add the actual connections.

This step resolves CR# 333653 is optional and not required for successful deployment.

Executing the upgrade script

This section tells you how to execute the upgrade script. There are separate instructions for Solaris and Windows-based installations.

Solaris	Use these instructions if you are upgrading a Solaris-based installation.
	1	Open a command window, and navigate to the
		$PATRIOT/release2.2/database directory.
	2	Execute the ep_login.sql script, with the following syntax:
		isql -S <ASE server name> -U sa -P <ASE_password> -
		i ep_login.sql -o <outputfile>
	3	Review and correct any errors in the output file.
Windows	Use these instructions if you are upgrading a Windows-based installation.
	1	Open a command window, and navigate to the
		%PATRIOT%\release2.2\database directory.
	2	Execute the ep_login.sql script, with the following syntax:
		isql -S <ASE server name> -U sa -P <ASE_password> -
		i ep_login.sql -o <outputfile>
	3	Review and correct any errors in the output file.

Adding the connection caches

The next series of steps adds the connection properties for the new login names.

Upgrade Guide 9