API Connect v5 on Pure Application System Multi-Cloud Environment
MarcoZobbi 1100007WWM Visits (3902)
On PureApplication System with Multi Cloud Environment is not possible install API Connect via OVA file as Virtual System Pattern so you need to deploy as Virtual Appliance, here there is some how during my work and a special thanks to my colleague Abdoul Gadiri Diallo.
In PureApplication System Console, navigate to Patterns - > Virtual Appliances. Click the blue + button in the top-left corner. You'll need to have an available HTTP server to upload your image from or you can also SCP the image over from any accessible server running sshd. You *must* give the image a unique name as well, and I also choose a cloud group for the images to belong to.
Once the image finishes importing, you'll need to deploy it using the 'Deploy' button near the top-right.
During the deploy give it a unique name, you MUST also assign an IP address to the image. Optionally you can modify the CPU and memory of the image as well.
Once the image is deployed, it will appear in Patterns -> Virtual Machines. It will also be stopped,go ahead and start it up by clicking the 'power on' button in the top right.
After it reaches running state, you can login to the server. However, due to the limitation with eth0, the image is not network accessible at the moment. You will have to reach it via the vmware console. Simply click the 'console' button near the top.
API CONNECT PORTAL
Login to the dev portal - the default login is admin and the default password is !n0r1t5@C
After you login you'll see a warning about disk size - I didn't modify this image's disk, but this can be done easily using just about any virtual disk management software.>
Alright, two things left to do:
1) Setup eth1 as a functional network
2) Modify the configuration of the dev portal to use eth1
For the first, we simply need to edit the network configuration settings.
sudo vi /etc
You'll need the basic network info for your PureApplication System - that can be obtained from Cloud -> IP Groups using the appropriate cloud group chosen for the IP assigned to the image.
Leave eth0 alone with DHCP - we don't want to touch it (in fact, if you DO try to enable eth0, it will bring down the entire networking capability of the image, so you can't reach it at all).
After that is done, you'll need to bounce the network to get eth1 functioning:
sudo ifdown eth1
sudo ifup eth
Once completed, you should be able to ping and/or ssh into your image.
Finally, we just need to change the dev portal customization configuration to use eth1 instead of eth0:
sudo vi /config/config.ini
The first section has a commented out setting for eth0. Remove the # and change eth0 to eth1.
API CONNECT MANAGEMENT
Login on shell
Reboot the Virtual Image with commando system reboot
From here on out you can treat it like a standard developer portal configuration by following the instructions from this knowledge cent