Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Sybase PATRIOT compliance Solution Version 2.2
Summary of Contents for Sybase PATRIOT compliance Solution Version 2.2
- Page 1 Upgrade Guide PATRIOTcompliance Solution Version 2.2...
- Page 2 Copyright © 2002-2004 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement.
-
Page 3: Table Of Contents
Contents About This Book ..........................v CHAPTER 1 Introduction ..................1 PATRIOTcompliance Solution overview .......... 2 CHAPTER 2 Upgrading to version 2.2 ..............3 Overview ..................4 Issues addressed in this release ..........4 Contents of the 2.2 release ............6 Verifying system environment variables........... - Page 4 Contents PATRIOTcompliance Starter Kit...
-
Page 5: About This Book
Select the Certification Report filter, specify a time frame, and click Click a Certification Report title to display the report. Creating a personalized view of the Sybase Web site (including support pages) Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages. - Page 6 If you need help Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area.
-
Page 7: Chapter 1 Introduction
Introduction C H A P T E R This chapter introduces Sybase PATRIOTcompliance Solution to financial institutions. Upgrade Guide... -
Page 8: Patriotcompliance Solution Overview
PATRIOTcompliance Solution overview PATRIOTcompliance Solution overview The Sybase PATRIOTcompliance Solution allows financial institutions to automate name filtering, intra-day and historical transaction filtering, and enterprise wide customer activity monitoring to meet the requirements of the USA PATRIOT (Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism) legislation. -
Page 9: Upgrading To Version 2.2
Upgrading to version 2.2 C H A P T E R This chapter tells you how to upgrade your system to version 2.2 of the PATRIOTcompliance Solution. Heading Page Overview Verifying system environment variables Upgrading the PATRIOT database Upgrading Process Server process definitions Upgrading formats Upgrading EAServer components Configuring Portlets... -
Page 10: Overview
This upgrade is distributed as a zip file and is available for download from the EBFs/Maintenance page at http://www.sybase.com/downloads Sybase strongly recommends that a backup of all components be Warning! done before you begin this upgrade. You must re-create any customization of the PATRIOT solution templates. - Page 11 CHAPTER 2 Upgrading to version 2.2 Description CR# 333653 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, , that creates three new login names...
-
Page 12: Contents Of The 2.2 Release
PatAcctManagementPortlet.pz PatriotPortlets22.pz \tightlink clientNew.xml clientupdate212.xml Tightlink212Upgrade.doc Loading Release 2.2 You must have 2.1.2 installed or upgrade from 2.1.1 prior to adding the EBF. Backup the current PATRIOT related directories to a safe place. • %PATRIOT% • %JAGUAR%\java\classes\com\sybase\patriotact\filter PATRIOTcompliance Starter Kit... -
Page 13: Verifying System Environment Variables
Verifying system environment variables Follow these steps to verify or set the environment variables required for configuration. Verify 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). -
Page 14: Upgrading The Patriot Database
Upgrading the PATRIOT database Windows example: JAVA_HOME=$JAGUAR\shared\sun\jdk\jdk.3 Set the PATRIOT environment variable. This is the directory where you initially copied the contents of the PATRIOTcompliance Starter Kit Solution Template CD. Solaris example: PATRIOT=$PATRIOT Windows example: PATRIOT=%PATRIOT% Upgrading the PATRIOT database Release 2.2 includes scripts that allow you to upgrade the PATRIOT database (Patriotdb) and New Era of Networks database (NNSYdb). -
Page 15: Modifying Patriot Connection Caches
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. - Page 16 Upgrading the PATRIOT database Adding the PATRIOTdbConnection Connect to Jaguar Manager as jagadmin Expand Jaguar Manager | Connection Caches. Right-click PATRIOTdbConnection, choose Connection Cache Properties. When the Connection Cache Properties sheet appears, the General tab is in focus. In the User Name box, change the sa user name to patriotlogin. In the Password box, type password.
-
Page 17: Upgrading Process Server Process Definitions
Use these instructions if you are upgrading a Windows-based installation. Copy the contents of the %PATRIOT%\Release2.2\edl directory to %SYBASE%\ProcessServer-3_9\bin\edl. This overwrites the set of existing files. Open a command window, and change to the %SYBASE%\ProcessServer- 3_9\bin\edl directory. Run the following commands: call EDLUtil put ..\edl\lPatriot.edl call EDLUtil put ..\edl\pPostFilter.edl... -
Page 18: Upgrading Formats
Use these instructions if you are importing the formats to a Windows-based installation. Perform this step if you have not updated your formats. Create the directory %SYBASE%\nnsy\formats if it does not already exist. Copy the format files from the %PATRIOT%\Release2.2\formats\* directory to the %SYBASE%\nnsy\formats directory. -
Page 19: Upgrading Easerver Components
Use these instructions if you are importing the formats to a Solaris-based installation. Perform this step if you have not updated your formats Create the directory $SYBASE/nnsy/formats if it does not already exist. Copy the format files from the $PATRIOT/Release2.2/formats/* directory to the $SYBASE/nnsy/formats directory. - Page 20 Upgrading EAServer components Right click Scheduler, choose Remove Service, then click OK to remove the scheduler. Expand Jaguar Manager | Servers | Jaguar and select Shutdown. Right-click Jaguar, choose Shutdown. Make sure the %JAGUAR%\Repository\Component\PatriotAct directory (Windows) or $JAGUAR/Repository/Component/PatriotAct (Solaris) directory does not exist. If it does, start Jaguar again and redo steps 1 - 7. Start Jaguar Server.
- Page 21 In the Component Name box, type Loader, then click Finish. When the Component Properties sheet appears, the General tab is in focus. Modify the Java Class name to read com.sybase.patriotact.filter.LoaderImpl, then click OK to return to Jaguar Manager. Expand the new Loader component, right-click Interfaces, select Add Interfaces.
- Page 22 Upgrading EAServer components Three CtsServices appear in the right pane Select CtsServices::Generic Service, click Add, then click Install. The Loader component is now available. Expand Servers | Jaguar. 10 Right-click Installed Services, choose Install Service, select PatriotAct/Loader from the list, then click OK to return to Jaguar Manager.
-
Page 23: Updating The Filter Properties File
CHAPTER 2 Upgrading to version 2.2 • Generate Java Files and use the default directory • Compile Java Stubs • Generate Skeletons and use the default directory • Compile Java Skeletons and use the default directory • Leave everything else as default Click Generate. -
Page 24: Setting The Patriotact Component Properties
Upgrading EAServer components select_scoreMatchStopWords = select word from PatStopWords where priority = 1 and is_active = 1 QuickWordsThreshhold=30 Setting the PATRIOTAct component properties Follow the instructions in this section to set the PATRIOTAct component properties. Setting Controller component properties Expand Servers | Jaguar | Installed Packages | PatriotAct. Right-click Controller, choose Component Properties. - Page 25 CHAPTER 2 Upgrading to version 2.2 When the Connection Properties sheet appears, click the Transactions tab, choose Not Supported Click the EJB Refs tab, do this: In the EJBs referenced in code group, click ejb/NightlyFilter, then set the Link Value to PatriotAct/NightlyFilter. Click the Resource Refs tab, do this: In the Resource factories referenced in code group, set the Sharing Scope of the jdbc/CacheName to shareable, then set the Resource Link...
-
Page 26: Configuring Portlets
Back up the following files. Note Directory paths below are in UNIX notation. For DOS, change forward slashes to back slashes; change $JAGUAR to %JAGUAR%. Subdirectory Filename $JAGUAR/html/classes PI_Errors.properties $JAGUAR/html/classes/com/ Errors.class. sybase/ep/portalinterface $JAGUAR/html/classes/com/sybase/ep/ SecurityServiceImpl.class portalinterface/services $JAGUAR/META-INF MANIFEST.MF Extract onelogin.zip into $JAGUAR. PATRIOTcompliance Starter Kit... -
Page 27: Installing Updated Portlets
Select X and X to exit the PortalZipper tool. Shut down and restart Jaguar Server. Solaris Use these instructions in install the 2.2 portlets on Solaris. Copy the *.pz files from $PATRIOT/portlets to $SYBASE/PortalInterface- 2_5/bin. Upgrade Guide... -
Page 28: Creating Directories For The Class Files
Configuring Portlets With ASE and Jaguar Server running, open a command window, and change to the $SYBASE/PortalInterface-2_5/bin directory. Run pz.sh with the following syntax: pz.sh -H <ASE_hostname> -N <ASE_Port> -U <ASE_username> -P <ASE_password> -F PatriotPortlets22.pz. Select Import Portlet from Archive and press... -
Page 29: Installing The Account Management Portlet
Use these instructions to install the Account Management portlet on Windows. With ASE and Jaguar Server running, open a command window, and copy %PATRIOT%\Portlets\PatAcctManagementPortlet.pz to %SYBASE%\PortalInterface-2_5\bin. Change to the %SYBASE%\PortalInterface-2_5\bin directory. Run pz.bat with the following syntax: pz.bat -H <ASE_hostname> -N <ASE_port_number> -F PatAcctManagementPortlet.pz... -
Page 30: Verifying The Account Management Portlet Deployment
In both files, change the line that reads: <jtf:setProperty name="IIOP_URL" value="iiop://yongming-pc:9000"/> <jtf:setProperty name="IIOP_URL" value="iiop://<yourhost>:<yourport>"/> Change to the $JAGUAR/html/classes/com/sybase/ilab/pi/pim/tasks directory, and rename PIMControl.class to PIMControl.class.old Shut down and restart Jaguar Server. Verifying the Account Management portlet deployment This step tells you how to test the Account Manager portlet. -
Page 31: Setting Up Account Management For The Pacuser
CHAPTER 2 Upgrading to version 2.2 The PATRIOT Test page should display with the new portlet accessible. Setting up Account Management for the pacuser To enable access to each of the PATRIOT portlets for pacuser, you need to modify the properties for each portlet and include the PIUser Role as detailed below. -
Page 32: Creating The Account Management Portlet For Pacuser
Configuring Portlets Change to the %JAGUAR%\html\classes\com\sybase\ilab\pi\pim\tasks directory (Windows) or $JAGUAR/html/classes/com/sybase/ilab/pi/pim/tasks (Solaris) and rename PIMControl.class.old to PIMControl.class. Shut down and restart Jaguar Server. Creating the Account Management portlet for pacuser Multiple portlet pages will be created for the PATRIOTcompliance Solution, and each page includes a number of the portlets imported into the Portal Interface. -
Page 33: Setting Up The New Portlets For Pacuser
CHAPTER 2 Upgrading to version 2.2 On the Choose Portlets panel, choose the new and updated portlets from the Available Portlets box and move them into the Selected Portlets box. These include: • Pat Logged In Users • Pd Exp Notification •... -
Page 34: Creating Portlet Pages For Pacuser
Configuring Portlets Creating portlet pages for pacuser If you are not logged in as pacuser, start Internet Explorer, enter the URL: http://<jaguar_hostname>:8080/, and log into Portal Interface with the user ID pacuser and password pacuser. On the Home Page, click Add Page from the Portal Control, name the page, click Done. -
Page 35: Index
Index upgrade Process Server dispatcher jar Account Management portlet deploying creating deploying installing pacuser EAServer components component properties deleting PATRIOTAct package dispatcher jar compliance solution filter properties introduction loader overview scheduler component properties stubs and skeletons 16, 17 controller upgrading FTPLoad environmenatal variables loader... - Page 36 Index verifying deployment verifying new portlets loader preface component properties Process Server creating upgrade definitions stubs and skeletons process server definitions loading importing login properties upgrading NightlyFilter release contents component properties scheduler overview component properties 14, 19 compliance solution creating upgrading stubs and skeletons scripts...
- Page 37 Index EAServer components environmenatal variables formats issues addressed in this release loading modifying connection caches overview portlets Process Server definitions upgrading database variables verify system environment verify system environment version 2.1 upgrade Upgrade Guide...
- Page 38 Index PATRIOTcompliance Starter Kit...
Need help?
Do you have a question about the PATRIOT compliance Solution Version 2.2 and is the answer not in the manual?
Questions and answers