Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #38

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ You may find it easier to view the different applications by running them from a
For convenience we are building a 'fat' executble jar whose start-class (main method entry-point) is defined to be in the class `io.pivotal.microservices.services.Main`. This application expects a single command-line argument that tells it to run as any of our three servers.

```
java -jar target/microservices-demo-2.0.0.RELEASE.jar registration|accounts|web
java -jar target/microservices-demo-2.1.0.RELEASE.jar registration|accounts|web
```

### Procedure
Expand All @@ -49,10 +49,10 @@ To run the microservices system from the command-line, open three CMD windows (W

1. In each window, change to the directory where you cloned the demo.
1. In the first window, build the application using either `./mvnw clean package` or `./gradlew clean assemble`. Either way the
generated file will be `target/microservices-demo-2.0.0.RELEASE.jar` (even if you used gradle).
1. In the same window run: `java -jar target/microservices-demo-2.0.0.RELEASE.jar registration`
1. Switch to the second window and run: `java -jar target/microservices-demo-2.0.0.RELEASE.jar accounts`
1. In the third window run: `java -jar target/microservices-demo-2.0.0.RELEASE.jar web`
generated file will be `target/microservices-demo-2.1.0.RELEASE.jar` (even if you used gradle).
1. In the same window run: `java -jar target/microservices-demo-2.1.0.RELEASE.jar registration`
1. Switch to the second window and run: `java -jar target/microservices-demo-2.1.0.RELEASE.jar accounts`
1. In the third window run: `java -jar target/microservices-demo-2.1.0.RELEASE.jar web`
1. In your favorite browser open the same two links: [http://localhost:1111](http://localhost:1111) and [http://localhost:3333](http://localhost:3333)

You should see servers being registered in the log output of the first (registration) window.
Expand All @@ -61,7 +61,7 @@ As you interact wiht the Web application, you should logging in the both the sec
For a list of valid accounts refer to the [data.sql](https://github.com/paulc4/microservices-demo/blob/master/src/main/resources/testdb/data.sql) that is used by the Account Service to set them up.

1. In a new window, run up a second account-server using HTTP port 2223:
* `java -jar target/microservices-demo-2.0.0.RELEASE.jar accounts 2223`
* `java -jar target/microservices-demo-2.1.0.RELEASE.jar accounts 2223`
1. Allow it to register itself
1. Kill the first account-server and see the web-server switch to using the new account-server - no loss of service.

Expand Down