Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Install
  4. Data Archive Installation
  5. Data Vault Installation
  6. Application Accelerator Installation
  7. Application Retirement for Healthcare Accelerator Installation
  8. MongoDB Accelerator Installation
  9. Salesforce Accelerator Installation
  10. After You Install
  11. Data Archive Upgrade
  12. Data Vault Upgrade
  13. Upgrading Oracle History Data
  14. Upgrading PeopleSoft History Data
  15. ILM Data Validation Option Setup
  16. Data Archive Source and Target Database Requirements
  17. Data Archive Connectivity
  18. Data Archive Uninstallation
  19. SAP Application Retirement
  20. Database Users and Privileges
  21. Data Visualization Designer Installation
  22. Data Archive Installation Requirements Checklist and Architecture Options

Installation and Upgrade Guide

Installation and Upgrade Guide

Creating the NFS Mount

Creating the NFS Mount

Use an NFS mount to create a shared file system between the SAP application folder and the Data Archive staging folder. Specify the connection properties in the source and target connections.
To create the NFS mount, perform the following high-level steps:
  1. In the SAP application server file system, set up an NFS mount point to the Data Archive staging folder.
  2. Set up the user with access to the Data Archive staging folder. If the SAP system is on Windows, that user must have the standard read, write, append, and delete permissions to this folder.
  3. Configure the Data Archive source connection.
    Specify the required source connection properties. In addition, specify the properties specific to SAP application retirement.
    The following table lists the required properties for SAP application retirement with the FTP option:
    Property
    Description
    Source/Staging Attachment Location
    The directory path of the staging folder on the SAP application server. SAP downloads the attachments and saves the BCP files to this folder.
    Enter the full path of the location. For example,
    \\10.1.10.10\interfaces\CCO\
    .
    You must specify the same directory path for the
    Staging Directory
    target connection property.
    SAP Fetch Size
    Number of rows that the retirement job extracts at a time from the SAP cluster and pool tables to write to the BCP file.
    SAP Host
    Host of the SAP application that you want to retire.
    SAP Client
    Client in which the user logs in. Note that all clients in the SAP application are retired.
    SAP System Number
    System number in which the user logs in.
    SAP Language
    Language in which the user logs in. Note that all languages in the SAP application are retired.
    SAP User
    User that logs in to the SAP application. The user must be assigned to the ZINFA_RETIREMENT_PREPARATION role and include RFC connection authorizations.
    SAP User Password
    Password for the SAP user.
  4. If you want Data Archive to save the BCP files in compressed file format, enable the check box for the
    Compressed
    property in the source connection.
    If enabled, Data Archive compresses BCP files and saves them as
    .gz
    files in the Data Archive staging folder. If not enabled, Data Archive saves BCP files as
    .bcp
    files.
  5. Configure the Data Vault target connection.
    For the
    Staging Directory
    property, enter the same directory path that you entered for the
    Source/Staging Attachment Location
    source connection property.
  6. Create the SAP application retirement project.
    For more information, see the chapter "SAP Application Retirement" in the
    Informatica Data Archive User Guide
    .

0 COMMENTS

We’d like to hear from you!