Resin, Deployment, Cloud, Clustering and EC2 (How To) Part II

Resin, Deployment,
Cloud, Clustering and
EC2 (How To) Part 2
Session Replication,
App Deployment and Clustering on EC2

Caucho Home | Contact Us | Caucho Blog | Wiki | Application Server / Web Server
Copyright (c) 1998-2012 Caucho Technology, Inc. All rights reserved.
caucho® , resin® and quercus® are registered trademarks of Caucho Technology, Inc.

Thursday, April 5, 12

Related
links

• Part 1 Resin Java EE Application Server clustering and
deployment to EC2
• Part 2 Resin clustering and deployment to EC2, session
replication, Amazon Load Balancer (This in WIKI form)

• Resin Java EE Application Server’s Cloud Support and Clustering
Support

• Resin White Paper on Java EE Cloud Computing

• Short video describing key concepts: Resin Clustering and
Cloud Deployment.


Java EE Certiﬁed



Gartner names Caucho
in "Cool Vendors in Platform
and Integration Middleware"
Java EE Certiﬁed



Resin
works
well
in
the
cloud

• This tutorial covers setting up a Resin cluster in Amazon EC2
• This is part 2, make sure you start with part 1
• Much of the cluster setup would be the same in other
environments as well
• Resin is only mainstream Java EE application server with
clustering and cloud deployment built-in and fully elastic that
works in an EC2 environment
• No add-ons, hacks, or tricks needed
• Resin simply designed to work well in cloud.
• Resin supports EC2,
• This EC2 support can equally apply to other Virtualization 2.0
environments like Xen, and VMWare


Overview

• IP addresses are ephemeral in EC2, public IP addresses are not
known (can’t see them with ifconfig b/c NAT)
• If you restart a server, it loses its IP addresses.
• Think of DHCP, but the lease expires instantly if the box is not
using it
• In a spoke / hub architecture, you need to know how to find the
hub. The hub is like a cluster DHCP server. It knows the
topology of the cluster.
• Resin clustering works around these issue by allowing Resin to
use public IP to find Triad members, and then members
exchanging private IP addresses
• Resin typically discovers the server id by looking up the address
combination of the instance. In this case, the local boxes do not
know any address so you have to tell Resin what the server id is
so it can look up the address it


Overview
how
to
overcome

• Create two Elastic IP addresses
• assuming you are using two machines both in a single Cluster
• Use Amazon Console to create another instance of the server
you setup in the ﬁrst tutorial.
• The ﬁrst three static servers in a cluster make up the Triad

• Before you continue, you may want some more background on
how Resin's spoke and hub (Triad) clustering architecture
works. Read White Paper: cloud and clustering technology
optimized for EC2.
• If you are in a hurry at least watch this short video: Resin
Clustering and Cloud Deployment.


Resin
Pro:
Clustering
and
Session
Replica;on

• You will need to get an evaluation license or a license to use
Resin's clustering support. To get an evaluation license go here:
Contact.
• Once you have a license, you can copy it to /var/www/licenses


Se<ng
up
second
Elas;c
IP
Address


New
Amazon
AMI
instance


Installing
a
Resin
Pro
License
4.0.27
and
below


Installing
a
Resin
Pro
License
4.0.28
and
above


Setup
Amazon
AMI
user-‐data
passing
list
of
triad


4.0.27:
Pass
Server
Id
Part
1
of
3


4.0.27:
Pass
Server
Id
Part
2
of
3


4.0.27:
Pass
Server
Id
Part
3
of
3


4.0.28:
Pass
Server
Id
Part
1
of
1

• 4.0.28 is much easier to pass the server id


Amazon
Load
Balancer

• Create an Amazon Load Balancer.
• Add the two instances to the LB. (Use the smallest possible
recheck interval for testing).
• Use sticky cookie support, use application cookie, set the name
to JSESSIONID.
• For more information on how to setup the Amazon Load
Balancer go to this Amazon Load Balancer tutorial.
• Now you have a Load Balancer and session replication should
just works.


Se<ng
up
Amazon
Load
Balancer
(Part
1
of
2)


Se<ng
up
Amazon
Load
Balancer
(Part
2
of
2)


Deploy
war
ﬁle
and
show
it
is
deployed

• Deploy the war ﬁle and show that it is deployed to every server


Se<ng
up
third
Triad
Member


4.0.27:
Se<ng
up
a
Dynamic
Spoke
Server


4.0.28:
Se<ng
up
a
Dynamic
Spoke
Server


Managing
deployments

• Deploying to one Server deploys to every server in the cluster


Summary
of
Servers
and
such


Resin, Deployment, Cloud, Clustering and EC2 (How To) Part II

Recomendados

Recomendados

Más contenido relacionado

Último

Último (20)

Destacado

Destacado (20)

Resin, Deployment, Cloud, Clustering and EC2 (How To) Part II