Samples/FreddysBBQ

Freddys BBQ Sample Application

This repo tree contains a polyglot (i.e. Java and .NET) microservices based sample app illustrating interoperability between Java and .NET based microservices running on CloudFoundry, secured with OAuth2 Security Services and using Spring Cloud Services.

To fully understand how this application is structured, you should have a good look at the Java based Freddys BBQ sample.

This application makes use of the following Steeltoe components:

• Spring Cloud Config Server Client for centralized application configuration
• Spring Cloud Eureka Server Client for service discovery
• Steeltoe Connectors for connecting to MySql using EF Core
• Steeltoe CloudFoundry Security Provider for SSO and REST endpoint protection

Getting Started

This repo contains two of the four components that make up the Freddys BBQ application ( i.e.Admin Portal UI and Order REST API). These two components have been writen using .NET and ASP.NET Core and will be used to illustrate interoperability between Java and .NET based microservices running on CloudFoundry.

To proceed you will first deploy the Java version of the app on CloudFoundry. To do this, follow the deployment instructions for the Java version of Freddys BBQ and verify that this version of the application is up and running properly.

Note: At one point in the deployment of the Java version, you are asked to run some scripts to configure the UAA Single Signon service. If you are on a windows machine, you will wish you had the .cmd versions of those scripts. You can find some in \scripts folder that you can edit and use.

Once the Java version is up and running then the next step will be to replace the two Java services, Admin Portal UI and Order REST API with the .NET versions found in this repo.

Once thats complete, you will have a running example of a Java and .NET based microservices based app running on CloudFoundry, secured with OAuth2 Security Services and using Spring Cloud Services.

Replace Java Services with .NET Services

Once you have finished deploying and verifing the Java version, you are then ready to proceed with this section.

Add MySQL Order Database

First you will need to create a new MySql service for our .NET version of the Order REST API service. Run the following commands:

cf create-service p.mysql db-small mysql-orders

Update admin-portal SSO Settings

Next, we have to make one small change to Redirect URIs for the admin-portal component in the SSO dashboard. To do this we need to access the SSO service dashboard. In order to access the dashboard, run the following command and go to the URL listed in Dashboard property:

$ cf service sso

Service instance: sso
Service: p-identity
Bound apps: customer-portal,menu-service,admin-portal,order-service
Tags:
Plan: auth
Description: Single Sign-On as a Service
Documentation url: https://docs.pivotal.io/p-identity/index.html
Dashboard: https://p-identity.mypcf.example.com/dashboard/identity-zones/{ZONE_GUID}/instances/{INSTANCE_GUID}/
...

Once you are in the dashboard select the admin-portal. Next in the Auth Redirect URIs box, duplicate current URI appending it to the current one (comma separating it). Then in the duplicated one, replace the https with http and append /signin-cloudfoundry to it.

So for example, if you started with:

https://admin-portal.apps.testcloud.com

then after making the changes, the Auth Redirect URIs would look as follows:

https://admin-portal.apps.testcloud.com,https://admin-portal.apps.testcloud.com/signin-cloudfoundry

Save your changes .... (i.e. Save Config)

Replace admin-portal & order-service

At this point you are ready to replace the existing Java based services with the .NET versions. To do this enter the following commands:

cd Samples\FreddysBBQ\src\OrderService
cf delete order-service -f
# Publish & Push to run on Windows
dotnet publish -f net6.0 -r win10-x64
cf push -f manifest-windows.yml -p bin\Debug\net6.0\win10-x64\publish
# OR for Linux
dotnet publish -f net6.0 -r linux-x64
cf push -f manifest.yml -p bin\Debug\net6.0\linux-x64\publish

cd ..\AdminPortal
cf delete admin-portal -f
# Publish & Push to run on Windows
dotnet publish -f net6.0 -r win10-x64
cf push -f manifest-windows.yml -p bin\Debug\net6.0\win10-x64\publish
# OR for Linux
dotnet publish -f net6.0 -r linux-x64
cf push -f manifest.yml -p bin\Debug\net6.0\linux-x64\publish

At this point the app should continue to work as it did before. Any orders you might have had before, will be gone as you are now starting with a new clean order database.

Note: If you happen to delete the services before pushing the new .NET services, you will have to configure the SSO service again for each of those two components.