Maintenance outage for upgrade on Sunday, September 22

This site, docs.bmc.com, will be inaccessible for two hours starting at 8 AM CDT, Sunday, September 22, for a platform upgrade.

    Page tree

       

    To view the latest information for BMC Helix services and policies, go to BMC Helix Subscriber Information.

    Skip to end of metadata
    Go to start of metadata

    The managed file transfer (MFT) process defines how data files are imported and exported to/from your OnDemand environments. An example of incoming information includes initial and ongoing data loading of people, asset, and related data. Examples of outgoing information include Analytics reports and application debug logs. The BMC OnDemand cloud MFT service provides the centralized medium for information delivery in both directions. This topic contains the following information:

    Managed file transfer workflow

    To facilitate data in and out of your OnDemand environments, customers are provided distinct and separate accounts for each destination environment (for example, production, QA, and development) on the BMC cloud FTP servers. Within each account are separate directories for inbound and outbound transfers. For inbound transfers, customers should upload data to the ToOnDemand directory. Likewise, for outbound transfers, customers can download data from the FromOnDemand directory. When configuring your data transfer, you will need to obtain the full directory path from BMC OnDemand Operations. Data is automatically transferred between the FTP server and the OnDemand environments on a set schedule, typically every 15 minutes.

    Note:

    Design and development of the transfer job is the sole responsibility of the customer. If development assistance is needed, BMC offers development services for a fixed price fee via its Remote Enhancement service.


    Incoming data loading process

    In order to deliver data to the BMC cloud for import into an OnDemand environment, the MFT service should be utilized by first uploading the desired data to the designated environment using the specific environment account information provided. Once logged in to the FTP server, files should be placed in the ToOnDemand directory. Within 15 minutes, the files will be moved to the OnDemand environment and available to any import process within the application. For Atrium Integrator (AI) or Unified Data Management (UDM) data loading mechanisms, the files will be moved to the AR System server of the OnDemand environment. In either case, the final target path on the destination server is D:\BMCData\BMCXfer\ToOnDemand for a Windows AR System server and /opt/bmc/ars/data/ToOnDemand for a Linux AR System server.

     

    Outgoing information delivery process

    For information received from OnDemand, the reverse process is very similar. In the case of debugging logs to be sent to the customer, the MFT service will be utilized by first ensuring the desired data is placed in the D:\BMCData\BMCXfer\FromOnDemand directory path for a Windows AR System server and /opt/bmc/ars/data/FromOnDemand for a Linux AR System server. Within 15 minutes, an automated process will move the files to the FTP server where they can be retrieved. This data can then be found in the FromOnDemand directory on the FTP server for the designated environment’s account.
    In the case of Analytics reports delivered in this manner, the process would be identical except the source server is a different system than the AR System or Mid-Tier servers. In any case, outgoing data will be located in the FromOnDemand directory on the FTP server.

    Note:

    When scheduling a data export from within the BMC Analytics OnDemand service, the FTP option under the Destinations tab is not supported. The file must be exported to the local drive via the File destination option and then moved to the outbound directory of the BMC-configured FTP server. For security reasons, outbound connections and transfers to external networks are not supported.

    Supported MFT standards

    BMC supports a variety of protocols to allow maximum flexibility for customer connections utilizing the MFT service. Both encrypted and unencrypted connections and transfers are supported, however encryption is strongly recommended. For transfers using the FTP protocol, plain FTP and FTPS using Explicit SSL are both supported using passive mode only. File transfers using SFTP are also supported. User/password authentication for all protocols as well as key authentication for SFTP are supported. Port requirements are listed below.

    Required ports

    Ports used for the MFT process include:

    • FTP – TCP 21 for control channel
    • FTP – TCP 32000-40000 for passive port range (data channel)
    • SFTP – TCP 22

    2 Comments

    1. My ARS server is a Linux box (at least in DEV), so the directory structure is different than the Windows one, I believe it is "/opt/bmc/ars/data/ToOnDemand" and "/opt/bmc/ars/data/FromOnDemand". 

      1. Thanks John. I will confirm and update this page as necessary.