Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. LDAP User Authentication
  16. Auditing
  17. Running Jobs from External Applications
  18. Upgrading Oracle History Data
  19. Upgrading PeopleSoft History Data
  20. Data Archive Maintenance
  21. Storage Classifications
  22. Appendix A: Datetime and Numeric Formatting
  23. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Creating the FTP Connection

Creating the FTP Connection

Install the FTP server and user. Specify the connection properties in the source and target connections.
To create the FTP connection, perform the following high-level steps:
  1. Install the FTP server in the same location as the Data Archive staging folder.
  2. Create the FTP user.
  3. Assign the FTP user with read, write, append, and delete permissions to the FTP folder.
  4. Create and maintain an entry in the SAPFTP_SERVERS table.
    For instructions on configuring SAPFTP and the list of SAP supported versions, see
    SAP Note 1605054
    .
  5. Set the FTP property
    Connection Timeout
    to a value between 1,200 and 2,000 seconds.
  6. 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\
    .
    Depending on the OS, the path must end with "/" or "\".
    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.
    FTP User
    User name to connect to the FTP server.
    FTP Password
    Password for the FTP user.
    FTP Host
    Host name of the FTP server.
    FTP Port
    Port number of the FTP server. Default port is 21.
    FTP Folder Location
    Name of the FTP folder on the Data Archive server. For example,
    ERP\
    .
    Depending on the OS, the folder name must end with "/" or "\".
  7. 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.
  8. Configure the Data Vault target connection.
    For the
    Staging Directory
    property, enter the full directory path of the FTP folder on the Data Archive server. For example,
    C:\user\FTP\ERP\
    .
  9. 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!