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. How to Create Business Rules to Archive and Purge Transactional Data
  9. How to Uninstall Data Archive 5.1
  10. How to Uninstall Data Archive 5.3
  11. How to Use Scripts to Change Database User Passwords in the ILM Repository
  12. IBM DB2 Database Connectivity and Setup for Data Archive
  13. Installing Data Visualization
  14. Integrating Third-Party Schedulers in ILM Engine
  15. Parallel Processing in Data Archive
  16. Seamless Access Configuration for Siebel Applications
  17. Seamless Access Setup for Oracle E-Business Suite
  18. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  19. Using Multiple Engines in an ILM Environment
  20. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  21. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Step 2. Set Up the Target Connection

Step 2. Set Up the Target Connection

In Data Archive, create a target connection to the Data Vault and set the archive store type to EMC Centera.
The following table describes the properties that you need to set for the target connection:
Property
Description
Connection Name
Archive target name. Use the name to differentiate archive target connections.
When you create an archive project and you assign a target, you select the connection name that you define here. You can use the connection name to display a list of all connection types or filter the list of connections by name.
Connection Description
Long text description for the connection name. To manage connections, you can use this field to filter the list of connections.
Connection Type
Type of target connection. The connection type determines the connection properties you need to define.
Set the connection type to Data Vault.
Application Version
Business application and application versions that the database connection type supports. The connection type determines the application version available.
Staging Directory
Location where the archive job creates the BCP files.
Number of Rows Per File
Maximum number of rows in the BCP files. When a BCP file reaches the maximum number of rows, the archive job creates another BCP file and adds subsequent rows to the new file.
Data Vault SCT Files Directory
Directory where the Data Vault Service creates the SCT files.
Data Vault Connection Name
Set to the default connection name
FAS
.
Data Vault Folder Name
Name of the folder in the Data Vault where you archive the data.
When you run the standalone job to create the archive folder, you provide the target connection. The job takes the folder name that from the target connection and creates the folder using the name you enter here.
Data Vault Host
Host name of the machine where the Data Vault Service is running.
Data Vault Port
Port number used by the Data Vault Agent to connect to the Data Vault Service. Default is 8600.
Data Vault Administration Port
Port number used by the Data Vault Administration Tool and command line program to connect to the Data Vault Service. Default is 8500.
Data Vault User
User name for the Data Vault Service administrator user account to log in to the Data Vault schema.
Data Vault User Password
Password for the Data Vault Service administrator user account.
Confirm Password
Confirmation of the Data Vault user password.
Add-On URL
URL for the Data Vault Service for External Attachments component. Required to convert external attachments from a proprietary format into regular format. Scripts are used to convert the attachments.
Use Mined Source Schema
Indicates whether to use the schema from the source instance mined in the Enterprise Data Manager. If enabled, the Data Vault Loader job uses the mined source schema structure from the Enterprise Data Manager to create the schemas in the Data Vault folder. The job creates the same schema structure in the Data Vault folder and adds the transactional tables to the corresponding schema. The job creates the dbo schema and adds the metadata tables to the dbo schema.
If not enabled, the Data Vault Loader job creates the dbo schema in the archive folder. The job adds all transactional tables across all schemas and metadata tables to the dbo schema.
The Data Vault Loader job uses the schema structure from the source instance that you mined in the Enterprise Data Manager. You may need to re-mine the source instance before you run the Data Vault Loader job if the source connection schema is different from the mined schema. Schema names can vary between instances. For example, you mined a development instance. You exported metadata from the development instance and imported the metadata into the production instance. If the schema names are different in development and production, you must re-mine the production instance.
Archive Store Type
Type of storage for the Data Vault. The store type can be an external storage platform.
Set to EMC Centera.
XRI
Extensible Resource Identifier (XRI) that describes the XAM server and the location of the XAM credentials file for the Centera XAM connection.