Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

Point-in-time recovery with referential ... > Prerequisites and environment for th... - Pg. 167

6.6.1 Scenario description In this scenario, we use the Trade6 application, which is a WebSphere application that is available to the public and that is useful for doing WebSphere performance benchmarks. We use the Trade6 application only to demonstrate a somewhat more real-life application. You can learn more about the Trade6 application at: We perform some simple tasks in the Trade6 application such as registering a new user, buying and selling some securities, and making a user profile change. Then, we want to use DB2 RE to back out to a point-in-time, but the undo will affect several tables. We intend to show how the DB2 Grouper integration will help us do this. 6.6.2 Prerequisites and environment for the scenario This scenario uses the Trade6 WebSphere application to drive transactions to a DB2 database. Our WebSphere server is at V6.0.1 and runs on a Windows serverTM named SIAM. The Trade database is named TRADSIMP and runs on a Linux server named LEAD. We use a Firefox browser on Windows to execute the transactions as a user would. We modified the database that comes with the Trade6 application in the following ways: Named the database TRADSIMP Created two DMS table spaces instead of using default Created two buffer pools instead of the default Altered all tables to include DATA CAPTURE CHANGES We made the following database configuration changes: db2 db2 db2 db2 db2 db2 update update update update update update db db db db db db cfg cfg cfg cfg cfg cfg for for for for for for tradsimp tradsimp tradsimp tradsimp tradsimp tradsimp using using using using using using logfilsiz 2000 logprimary 8 logsecond 5 applheapsz 1024 newlogpath /db2log/tradsimp logarchmeth1 "DISK:/db2logarch" We made the following instance registry change: db2set DB2_DETAIL_LOGGING=AUTHID Chapter 6. Backing out insert, update, and delete operations 167