AnsweredAssumed Answered

CA API Dev Portal 4.2 Network Connectivity Help

Question asked by rick.reed2.2 on Feb 6, 2018
Latest reply on Feb 16, 2018 by robvanb

Working through the DevPortal 4.2 installation document and running into some issues.

(Prepare your Environment - CA API Developer Portal - 4.2 - CA Technologies Documentation )

 

My corporate VM team provisioned the VM using the OVA file specified in the documentation.  My question is towards the end of this list:

 

#19 states to Configure your network, NTP, or other configuration as needed.  

 

When I installed the API Gateway 9.2, there were detailed instructions on how to go in and setup network connectivity for the VMs but I am not seeing any of that within this documentation.

 

Can anyone provide these details so that I can get this VM connected to my network and to the point where I can configure the product?

 

To provision the OVA, follow these steps:

  1. Download the API Developer Portal Virtual CentOS 4.2 from support.ca.com.
  2. Using a vSphere client, connect to your vSphere server.
  3. Click File and select Deploy OVF Template.
  4. Click Browse and navigate to where the CA API Developer Portal OVA was downloaded.
  5. Select the OVA, click Open, and click Next to proceed.
  6. Verify the details and click Next to continue.
  7. Enter a name for this instance, select the Inventory Location and click Next.
  8. Select the  Host / Cluster to deploy to and click Next.
  9. Select the Resource Pool to deploy to and click Next.
  10. Select the DataStore to use and click Next.
  11. Select Thin Provision as the Disk Format and click Next.
  12. Click Next from the Network Mapping dialog.
  13. Review the settings and click Finish to provision the VM.
  14. Power on the VM.
  15. Click the Summary tab and wait for the IP addresses to be reported back. Click View all if there are several addresses.
  16. Copy the private IP address of the VM.
  17. SSH into the system and log in as the portal user.
    You are prompted to change the password.

  18. Change your portal password and log back in using the new password.
  19. Configure your network, NTP, or other configuration as needed.

Outcomes