Layer7 API Management

 View Only
  • 1.  CA API Portal 4.3 Form Factor

    Posted May 13, 2019 11:26 AM

    Can you please provide the differences in terms of operations (e.g. version updates, scaling the portal, HA etc) between the CA Provided Hardened image version of the portal and the Docker Swarm cluster deployment option?


    Any other differences would also be greatly appreciated. For instance, can the Hardened image be deployed on Azure ?

  • 2.  Re: CA API Portal 4.3 Form Factor

    Posted May 14, 2019 05:02 AM


    This is the release note for 4.3


    For your convenience, CA provides a hardened image to expedite the installation process. The hardened image is available in OVA format, which can be directly imported into VMware and most other common virtualization platforms. Use the CA provided a hardened image if you do not want to set up a VM with CentOS installed. See CentOS Hardened Image for requirements.

    You cannot install Portal on a platform such as AWS or Azure. The only currently supported format is the OVA.

    You can provision your own VM for API Portal. You assume the responsibility for having a working VM with CentOS 7.x installed and functional before proceeding.


    Please refer to the documentation




  • 3.  Re: CA API Portal 4.3 Form Factor

    Posted May 14, 2019 05:12 AM

    Thank you cheed04 for the response. The release notes does state that the Portal 4.3 version is not yet supported on Azure - I believe it applies to both the Hardened image mode or the Docker swarm mode. Please confirm otherwise.


    Could you please point me to some references around how HA/DR can be achieved in the hardened image format.

  • 4.  Re: CA API Portal 4.3 Form Factor

    Posted May 14, 2019 05:27 AM

    Thanks for the response. 

    Please check the documentation for scale CA API Portal. its has reference to high availability.

  • 5.  Re: CA API Portal 4.3 Form Factor

    Posted May 14, 2019 05:38 AM

    Thanks again cheed04 for the quick response. So the scaling would work the same way for the Hardened image form as well. Please let me know if there are any differences between the 2 approaches in terms of operations or being Azure/AWS supported in the future.