Commit 1d3caef8 authored by Kevin Di Lallo's avatar Kevin Di Lallo
Browse files

fixed demo3 doc links

parent f2e0e2b8

docs/usage/usage-demo3.md

+3 −1
Original line number Diff line number Diff line
@@ -33,7 +33,7 @@ The scenario includes: 
- 3 terminals with pre-defined routes to move interchangeably from _mep1_ to _mep2_



**NOTE:** To view terminal movement on a map, you must first provision maps in AdvantEDGE as described

[here](https://interdigitalinc.github.io/AdvantEDGE/docs/overview/features/gis/#map-provisioning)

[here]({{site.baseurl}}{% link docs/overview/features/gis/overview-gis.md %}#map-provisioning))



### Demo server

Demo server is a web server that interacts with the _Application Enablement_ & _Application Mobility_ services
@@ -90,6 +90,8 @@ cd ~/AdvantEDGE/examples/demo3 
### Deploy Demo3 scenario

After building & dockerizing the Demo3 application, the Demo3 scenario must be imported in AdvantEDGE and deployed within a sandbox.



_**IMPORTANT NOTE:** For the API calls to work correctly, the platform IP address or domain name must be properly configured in the [AdvantEDGE deployment configuration]({{site.baseurl}}{% link docs/platform-mgmt/mgmt-cheat-sheet.md %}#deployment-configuration) file._



### Start Demo3 application frontend

After deploying the Demo3 scenario, the Demo3 application frontend can be accessed as follows:

- _demo3-mep1_: `http://<AdvantEDGE IP address>:31111`