Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Seamless Access Setup for Oracle R12 in Data Archive
  21. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  22. Using Multiple Engines in an ILM Environment
  23. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  24. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Appendix B

Appendix B

  1. Issue:
    Change user's access rights to "Read Only" for all Pages they currently have access to in Production. This solution assumes that users will not be doing any kind of security or account maintenance in the Seamless Access environment.
    Solution:
    This is controlled by the DISPLAYONLY flag in the PSAUTHITEM table. A value of "1" means the page is display only. A value of "0" states the page is updateable. We modified the view of PSAUTHITEM table to add select statement to return pages that are flagged as display only.
  2. Issue:
    Enable user's access to in-page buttons so users can perform drilldown to detail information (i.e. PO Inquiry)
    Solution:
    The PO Inquiry page by definition is a display only page. To allow the user the ability to click on buttons on the page it must not be set as display only. The view PSAUTHITEM will not set this page to display only.
    Future Inquiry Pages:
    For future pages that are by nature inquiry only, the DISPLAYONLY flag in the PSAUTHITEM view should be set to 0 for these pages. A value of "0" states the page is updateable. The item should be added to the 1
    st
    and 2
    nd
    select statement in the PSAUTHITEM view as noted below where "PO_INQUIRY" is located.
    CREATE OR REPLACE VIEW &&DATAACCESSSID..PSAUTHITEM (CLASSID, MENUNAME, BARNAME, BARITEMNAME, PNLITEMNAME, DISPLAYONLY, AUTHORIZEDACTIONS) AS
    select a1.CLASSID, a1.MENUNAME, a1.BARNAME, a1.BARITEMNAME, a1.PNLITEMNAME, 1 DISPLAYONLY, a1.AUTHORIZEDACTIONS from &&ACCESSID..PSAUTHITEM a1 WHERE a1.BARITEMNAME NOT IN ('PROCESSMONITOR','QUERY_MANAGER', 'PO_INQUIRY') -- This Allows the user to click on buttons in PO Inquiry and a1.BARNAME NOT IN ('REPORT') union select a2.CLASSID, a2.MENUNAME, a2.BARNAME, a2.BARITEMNAME, a2.PNLITEMNAME, 0 DISPLAYONLY, a2.AUTHORIZEDACTIONS from &&ACCESSID..PSAUTHITEM a2 WHERE a2.BARITEMNAME IN ('PROCESSMONITOR','QUERY_MANAGER', 'PO_INQUIRY') -- This Allows the user to click on buttons in PO Inquiry and a2.BARNAME NOT IN ('REPORT')
  3. Issue:
    Don't allow the user the ability to revise nVision parameters (Scope, Report Requests).
    Solution:
    nVision pages access rights are set to "Read Only" with the resolution for issue 1.
    Report layouts are not controlled via the 3 tier environment. There is no programmatic way to remove the user's ability to create or modify report layouts. They are controlled via 2 tier installation of nVision.
  4. Issue:
    Have a way to turn on/off the user's ability to run a query to HTML.
    Solution:
    This is controlled by the flag QRY_OUT_LISTBOX in the table PS_SCRTY_QUERY. We added a new view (PS_SCRTY_QUERY) based off this table. A value of "N" will prevent the user from being able to run a query to HTML. A value of "Y" will give the user the ability to run to HTML.
  5. Issue:
    Have a way to turn on/off the user's ability to run a query to Excel.
    Solution:
    This is controlled by the flag QRY_OUT_NVISION in the table PS_SCRTY_QUERY. We added a new view (PS_SCRTY_QUERY) based off this table. A value of "N" will prevent the user from being able to run a query to Excel. A value of "Y" will give the user the ability to run to Excel.
  6. Issue:
    Remove user's ability to create/edit Public or Private Queries. Users will still be able to run all queries that they have access to in Production.
    Solution:
    This is controlled by the flag QRY_RUN_ONLY in the table PS_SCRTY_QUERY. We added a new view (PS_SCRTY_QUERY) based off this table. A value of "Y" will prevent the user from being able to edit or create queries. A value of "N" will give the user the ability to create/edit queries.
  7. Issue:
    Have a way to turn on/off user's ability to Schedule a query (thru the Process Scheduler)
    Solution:
    There is no way without a customization to the page to remove the "Schedule Query" Link on the query page. To prevent them from scheduling a query we are setting the field AUTHORIZEDACTIONS in the 3
    rd
    sql for the PSAUTHITEM to 0. The users will receive a security error saying they are not authorized to access this component which prevents them from scheduling queries.