Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Oracle E-Business Suite Retirement Reports
  18. JD Edwards Enterprise Retirement Reports
  19. Oracle PeopleSoft Applications Retirement Reports
  20. Smart Partitioning
  21. Smart Partitioning Data Classifications
  22. Smart Partitioning Segmentation Policies
  23. Smart Partitioning Access Policies
  24. Language Settings
  25. Appendix A: Data Vault Datatype Conversion
  26. Appendix B: Special Characters in Data Vault
  27. Appendix C: SAP Application Retirement Supported HR Clusters
  28. Appendix D: Glossary

Step 3. Import Salesforce Metadata and Configure Entities

Step 3. Import Salesforce Metadata and Configure Entities

Connect to Salesforce in the Enterprise Data Manager to import Salesforce metadata and configure archive entities.
By default, the Salesforce application and an application version called "Sales" are visible in the Enterprise Data Manager application hierarchy. You can use the Sales application version to import metadata from standard and custom tables, or you can create a new application version. The Salesforce accelerator installs two entities called Event and Task. These entities contain standard Salesforce tables that you might want to archive. For more information on the tables in the Event and Task entities and their relationships, see the "Salesforce Accelerator" chapter of the
Enterprise Data Manager Guide
.
Before you can configure entities, you must connect to Salesforce to import metadata from Salesforce, just as you would for any ERP or custom application. You enter Salesforce connection details, such as the Salesforce username, password, security token, and host URL. You also provide the name and (optionally) the location of a database created by the JDBC driver for internal use. Next, you select the schema from which to import the metadata. There are special considerations for extracting and importing metadata from child tables in Salesforce entities, due to circular relationships between the tables that make automatic entity creation impossible. For more information about importing Salesforce metadata and configuring entities, see the "Salesforce Accelerator" chapter of the
Enterprise Data Manager Guide
.

0 COMMENTS

We’d like to hear from you!