Skip to content

Commit 1f707fc

Browse files
committed
Build Ticket Monster
1 parent 65abf76 commit 1f707fc

2 files changed

Lines changed: 55 additions & 1 deletion

File tree

12 KB
Loading

readme.adoc

Lines changed: 55 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,10 +138,64 @@ Once your Docker host has been created, it then has a number of commands for man
138138
. Upgrading Docker
139139
. Configuring the Docker client to talk to your host
140140

141-
You used Docker Machine already during the attendee setup. We won't need it too much further on. But if you need to create hosts, it's a very handy tool to know about.
141+
You used Docker Machine already during the attendee setup. We won't need it too much further on. But if you need to create hosts, it's a very handy tool to know about. From now on we're mostly going to use the docker client.
142142
Find out more about the details at the link:https://docs.docker.com/machine/[Official Docker Machine Website]
143143

144+
Check if docker machine is working with
145+
146+
[source, text]
147+
----
148+
docker-machine -v
149+
----
150+
151+
### Docker Client
152+
The client communicates with the demon process on your host and let's you work with images and containers.
153+
Check if your client is working with
154+
155+
[source, text]
156+
----
157+
docker -v
158+
----
159+
160+
The most important options you'll be using frequently are:
161+
162+
. `run` - runs a container
163+
. `ps`- lists containers
164+
. `stop` - stops a container
165+
166+
Get a full list of available commands with
167+
[source, text]
168+
----
169+
docker
170+
----
171+
144172
### Ticket Monster
173+
TicketMonster is an example application that focuses on Java EE6 - JPA 2, CDI, EJB 3.1 and JAX-RS along with HTML5 and jQuery Mobile. It is a moderately complex application that demonstrates how to build modern web applications optimized for mobile & desktop. TicketMonster is representative of an online ticketing broker - providing access to events (e.g. concerts, shows, etc) with an online booking application.
174+
175+
Apart from being a demo, TicketMonster provides an already existing application structure that you can use as a starting point for your app. You could try out your use cases, test your own ideas, or, contribute improvements back to the community.
176+
177+
.TicketMonster architecture
178+
image::images/ticket-monster_tutorial_architecture.png[]
179+
180+
The application uses Java EE 6 services to provide business logic and persistence, utilizing technologies such as CDI, EJB 3.1 and JAX-RS, JPA 2. These services back the user-facing booking process, which is implemented using HTML5 and JavaScript, with support for mobile devices through jQuery Mobile.
181+
182+
The administration site is centered around CRUD use cases, so instead of writing everything manually, the business layer and UI are generated by Forge, using EJB 3.1, CDI and JAX-RS. For a better user experience, Twitter Bootstrap is used.
183+
184+
Monitoring sales requires staying in touch with the latest changes on the server side, so this part of the application will be developed in HTML5 and JavaScript using a polling solution.
185+
186+
### Build Ticket Monster
187+
First thing, you're going to do is to build the application from source. Create a folder for the source
188+
[source, text]
189+
----
190+
mkdir /docker-java/
191+
----
192+
And checkout the sources from the instructor git repository.
193+
[source, text]
194+
----
195+
git clone -b WFLY8.1 http://root:dockeradmin@<INSTRUCTOR_IP>:10080/root/ticket-monster.git
196+
----
197+
198+
145199

146200
### Deploy Ticket Monster
147201

0 commit comments

Comments
 (0)