4.18.01.01 - Edge for Private Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

On Tuesday, April 10, 2018, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure on the Edge nodes:

On all Edge nodes:
1. Clean Yum repos:
```
sudo yum clean all
```
2. Update the Edge 4.18.01 bootstrap_4.18.01.sh file in /tmp/bootstrap_4.18.01.sh:
```
curl https://software.apigee.com/bootstrap_4.18.01.sh -o /tmp/bootstrap_4.18.01.sh
```
3. Install the Edge 4.18.01 apigee-service utility and dependencies:
```
sudo bash /tmp/bootstrap_4.18.01.sh apigeeuser=uName apigeepassword=pWord
```
  where uName:pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.
4. Update the apigee-setup utility:
```
sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
```
5. Source the apigee-service.sh file:
```
source /etc/profile.d/apigee-service.sh
```
Update all Router nodes:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```
where configFile specifies the config file you used to install Edge.
(If installed) Update all API BaaS Stack nodes:
```
/opt/apigee/apigee-setup/bin/update.sh -c b -f baasConfigFile
```
where baasConfigFile specifies the config file you used to install API BaaS.
(If installed) Update the New Edge Experience node. The New Edge Experience is in Beta and you must install it on its own node.
This fix includes the new MANAGEMENT_UI_SKIP_VERIFY property. If Edge SSO uses a self-signed cert, you must set MANAGEMENT_UI_SKIP_VERIFY to "y" in the configuration file used to install New Edge Experience. See Installing the New Edge Experience (Beta).

To update the New Edge Experience node:
1. ```
/opt/apigee/apigee-service/bin/apigee-service edge-management-ui update
```
2. ```
/opt/apigee/apigee-service/bin/apigee-service edge-management-ui setup -f newUIConfigFile
```
  where newUIConfigFile specifies the config file you used to install the New Edge Experience.
3. ```
/opt/apigee/apigee-service/bin/apigee-service edge-management-ui configure-sso -f newUIConfigFile
```

Bugs fixed

The following bugs are fixed in this release.

Note: The build number in the table specifies the earliest version of the component that contains the fix. Use that build number to determine if you already have the fix installed, or if you need to perform an update. The apigee-service utility displays the build number of the currently installed component:

/opt/apigee/apigee-service/bin/apigee-service comp version

where comp is the name of the component without the build number extension. For example:

/opt/apigee/apigee-service/bin/apigee-service apigee-setup version

or get the build number of all components:

/opt/apigee/apigee-service/bin/apigee-all version

Issue ID	Description	Build number
74586724	4.18.01 update script now updates Nginx for the Router.	`edge_gateway.4.18.01-0.0.1553`
76016757	New Edge Experience now supports TLS access to Edge SSO using a self-signed cert If Edge SSO uses a self-signed cert, you must set `MANAGEMENT_UI_SKIP_VERIFY` to "y" in the configuration file used to install New Edge Experience. See Installing the New Edge Experience (Beta). .	`edge_management_ui.0.1.0-0.0.20015`
77575870	API BaaS installation failed on apigee-tomcat version dependency	`apigee_tomcat.7.0.82-0.0.897`
72651279	Upgrade BaaS UI to use reCAPTCHA V2	`baas_usergrid.2.2.0-0.0.369`

4.18.01.02

4.18.01