Deploy an Oracle Managed File Transfer Multinode Cluster by Using Oracle Cloud Marketplace

Oracle Managed File Transfer (MFT) is a high performance, standards-based, end-to-end managed file gateway. It features design, deployment, and monitoring of file transfers by using a lightweight web-based design-time console. The MFT console includes transfer prioritization, file encryption, scheduling, and embedded FTP and sFTP servers. This reference architecture depicts the multinode cluster configuration of Oracle MFT on OCI using a Marketplace image of Oracle SOA/MFT.

Architecture

This architecture shows deployment of Oracle Managed file transfer in a cluster configuration on Oracle Cloud infrastructure region by using Oracle Cloud Marketplace. The following diagram illustrates this reference architecture.


Description of deploy-mft-orm.png follows
Description of the illustration deploy-mft-orm.png

deploy-mft-orm-oracle.zip

The architecture has the following components:
  • Region

    An Oracle Cloud Infrastructure region is a localized geographic area that contains one or more data centers, called availability domains. Regions are independent of other regions, and vast distances can separate them (across countries or even continents).

  • Availability domains

    Availability domains are standalone, independent data centers within a region. The physical resources in each availability domain are isolated from the resources in the other availability domains, which provides fault tolerance. Availability domains don’t share infrastructure such as power or cooling, or the internal availability domain network. So, a failure at one availability domain is unlikely to affect the other availability domains in the region.

  • Virtual cloud network (VCN) and subnets

    A VCN is a customizable, software-defined network that you set up in an Oracle Cloud Infrastructure region. Like traditional data center networks, VCNs give you complete control over your network environment. A VCN can have multiple non-overlapping CIDR blocks that you can change after you create the VCN. You can segment a VCN into subnets, which can be scoped to a region or to an availability domain. Each subnet consists of a contiguous range of addresses that don't overlap with the other subnets in the VCN. You can change the size of a subnet after creation. A subnet can be public or private.

  • Route table

    Virtual route tables contain rules to route traffic from subnets to destinations outside a VCN, typically through gateways.

  • Security list

    For each subnet, you can create security rules that specify the source, destination, and type of traffic that must be allowed in and out of the subnet.

  • Internet gateway

    The internet gateway allows traffic between the public subnets in a VCN and the public internet.

  • Bastion host

    The bastion host is a compute instance that serves as a secure, controlled entry point to the topology from outside the cloud. The bastion host is provisioned typically in a demilitarized zone (DMZ). It enables you to protect sensitive resources by placing them in private networks that can't be accessed directly from outside the cloud. The topology has a single, known entry point that you can monitor and audit regularly. So, you can avoid exposing the more sensitive components of the topology without compromising access to them.

  • Load balancer

    The Oracle Cloud Infrastructure Load Balancing service provides automated traffic distribution from a single entry point to multiple servers in the back end.

  • MFT Cluster

    Oracle MFT enables secure file exchange and management between the cloud and both SaaS or on premise enterprise applications. Oracle Cloud provides the necessary cloud platform and infrastructure to provision your MFT environment. Together, they protect against inadvertent access to unsecured files at every step in the end-to-end transfer of files.

  • Autonomous database

    Oracle Cloud Infrastructure autonomous databases are fully managed, preconfigured database environments that you can use for transaction processing and data warehousing workloads. You do not need to configure or manage any hardware, or install any software. Oracle Cloud Infrastructure handles creating the database, as well as backing up, patching, upgrading, and tuning the database.

Recommendations

Use the following recommendations as a starting point when deploying an MFT multinode cluster on OCI Marketplace. Your requirements might differ from the architecture described here.
  • VCN

    When you create a VCN, determine the number of CIDR blocks required and the size of each block based on the number of resources that you plan to attach to subnets in the VCN. Use CIDR blocks that are within the standard private IP address space.

    Select CIDR blocks that don't overlap with any other network (in Oracle Cloud Infrastructure, your on-premises data center, or another cloud provider) to which you intend to set up private connections.

    After you create a VCN, you can change, add, and remove its CIDR blocks.

    When you design the subnets, consider your traffic flow and security requirements. Attach all the resources within a specific tier or role to the same subnet, which can serve as a security boundary.

  • Network security groups (NSGs)

    You can use NSGs to define a set of ingress and egress rules that apply to specific VNICs. We recommend using NSGs rather than security lists, because NSGs enable you to separate the VCN's subnet architecture from the security requirements of your application.

  • Security Zones

    For resources that require maximum security, Oracle recommends that you use security zones. A security zone is a compartment associated with an Oracle-defined recipe of security policies that are based on best practices. For example, the resources in a security zone must not be accessible from the public internet and they must be encrypted using customer-managed keys. When you create and update resources in a security zone, Oracle Cloud Infrastructure validates the operations against the policies in the security-zone recipe, and denies operations that violate any of the policies.

  • Cloud Guard

    Clone and customize the default recipes provided by Oracle to create custom detector and responder recipes. These recipes enable you to specify what type of security violations generate a warning and what actions are allowed to be performed on them. For example, you might want to detect Object Storage buckets that have visibility set to public. Apply Cloud Guard at the tenancy level to cover the broadest scope and to reduce the administrative burden of maintaining multiple configurations. You can also use the Managed List feature to apply certain configurations to detectors.

Considerations

When deploying an MFT multinode cluster on OCI Marketplace consider these factors.

  • Scalability
    • Application tier:

      You can scale the application server vertically by changing the shape of the compute instance. A shape with a higher core count provides more memory and network bandwidth as well. If more storage is required, increase the size of the block volumes attached to the application server.

    • Database tier:

      You can scale the database vertically by enabling additional cores for the database. Both the cores and storage can be scaled up without any database downtime.

  • Resource limits

    Consider the best practices, limits by service, and compartment quotas for your tenancy.

  • Security
    • Use Oracle Cloud Infrastructure Identity and Access Management(IAM) policies to control who can access your cloud resources and what operations can be performed.
    • To protect the database passwords or any other secrets, consider using the Oracle Cloud Infrastructure Vault service.
  • Performance and cost

    Oracle Cloud Infrastructure offers compute shapes that cater to a wide range of applications and use cases. Choose the shapes for your compute instances carefully. Select shapes that provide optimal performance for your load at the lowest cost. If you need more performance, memory, or network bandwidth, you can change to a larger shape.

  • Availability

    Consider using a high-availability option based on your deployment requirements and your region. The options include distributing resources across multiple availability domains in a region, and distributing resources across the fault domains within an availability domain. Fault domains provide the best resilience for workloads deployed within a single availability domain. For high availability in the application tier, configure your MFT with multinode cluster in which each of the managed MFT servers are distributed across different availability domains in a region, and use a load balancer to distribute client traffic across the application servers.

  • Monitoring and alerts

    Set up monitoring and alerts on CPU and memory usage for your nodes, so that you can scale the shape up or down as needed.

  • Database strategy

    When the service Type is MFT Cluster and the Database strategy is Autonomous Transaction Processing Database. Configuring a File storage is mandatory for the MFT Cluster service type on an Autonomous Transaction Processing (ATP) database.

Explore More

Learn more about Oracle Managed File Transfer and Oracle Cloud. Review these additional resources: .

Review these additional resources:

Acknowledgments

Author: Chethan B.R