forked from pivotal-cf/docs-apigee-bosh
-
Notifications
You must be signed in to change notification settings - Fork 1
/
installing.html.md.erb
55 lines (33 loc) · 3.44 KB
/
installing.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
---
title: Installing and Configuring Apigee Edge Installer for PCF
owner: Partners
---
This topic describes how to install and configure Apigee Edge Installer for Pivotal Cloud Foundry (PCF). Edge Installer for PCF lets PCF developers use [Apigee Edge for Private Cloud v4.17.09](http://docs.apigee.com/private-cloud/latest/overview) (Edge).
##<a id='overview'></a>Installation Overview
During the installation, the following events occur:
* Ops Manager creates a virtual machine (VM) for the Apigee Mirror Repo to host the Apigee `yum` repository, and makes sure that subsequent VMs have access to this repository.
* Ops Manager then creates VMs and installs the Edge components that do not depend on other components, such as Zookeeper. Each Edge component is installed on its own VM.
* Ops Manager then creates the next VM and installs the Edge components that do not depend on any other component except the components that have already been installed.
* The `apigee` user is created on each VM.
* The `apigee-service` utility is installed on each VM in case you have to log in to the VM to troubleshoot issues.
After the installation completes, use the Edge management API to provision an organization, and log in to the Edge UI to start creating API proxies.
For more information, see [Understanding APIs and API proxies](http://docs.apigee.com/api-services/content/understanding-apis-and-api-proxies).
##<a id='optional'></a>Install Optional Edge Components
During the install process, you can optionally choose to install additional Edge components, including the following:
* [Apigee BaaS](http://docs.apigee.com/api-baas)
* [Edge Monitoring Dashboard](http://docs.apigee.com/private-cloud/latest/apigee-monitoring-dashboard-overview)
* [Developer Services portal](http://docs.apigee.com/developer-services/content/what-developer-portal)
* [Edge SSO](https://docs.apigee.com/private-cloud/latest/supporting-saml-edge-private-cloud)
* [Monetization](http://docs.apigee.com/monetization/content/basics-monetization)
Installing these components may require you to perform additional onboarding or configuration steps.
Apigee BaaS and Developer Services portal both require an SMTP server. If installed, they use the same SMTP server as configured for Edge.
##<a id='install'></a> Install and Configure Apigee Edge Installer for PCF
1. Download the product file from [Pivotal Network](https://network.pivotal.io).
1. Navigate to the Ops Manager **Installation Dashboard** and click **Import a Product** to upload the product file.
1. Click **Add** next to the uploaded **Apigee Edge Installer for Pivotal Cloud Foundry** tile in the Ops Manager **Available Products** view to add it to your staging area.
1. Click the newly added **Apigee Edge Installer for Pivotal Cloud Foundry** tile.
1. Configure the install as described at [Installing Edge using Ops Manager](https://docs.apigee.com/private-cloud/v4.17.09/installing-edge-using-ops-manager).
1. Return to the Ops Manager Installation Dashboard and click **Apply Changes** to complete the installation.
1. Test the install as described in [Test the installation](https://docs.apigee.com/private-cloud/v4.17.09/installing-edge-using-ops-manager#testtheinstallation).
1. After the Edge Installer for PCF installation completes, you must provision Edge and any optional Edge components that you installed.
For more information, see [Provisioning organizations](https://docs.apigee.com/private-cloud/v4.17.09/provisioning-organizations).