Recently some customers are asking questions about Websphere Application Server(WAS) on Amazon EC2.
IBM also provides IBM Eligible Public Cloud BYOSL policy for Amazon EC2 Instances & Dedicated Instances.
I have capture 2 videos on how to set a WAS Network Deployment environment on Amazon EC2 instance.
Before watching two videos, you need to prepare following tools/account/knowledge:
1. An IBM ID IBM id registration
2. An AWS account Amazon Web Services
3. Putty Putty
5. WinSCP WinSCP(if your workstation is Windows)
6. Web browser
7. Basic concept of WAS Network Deployment environment.WebSphere Application Server V8.5 Concepts, Planning, and Design Guide
Part 1. Create an EC2 instance
This video will help you create a Linux instance with free Amazon account.
Amazon provide free tier offers for 12 moths (the services on AWS will NOT be stopped after 12 months, make sure to terminate all services to avoid charge) , please check this link for more information: AWS Free Tier
In the video I created 2 EC2 instances and each instance contains a node, because the free instance only has 1GB memory which is not enough for ND environment (at least 3 running jvms).
Part 2. Set up WAS Network Deployment environment
This video will provide steps to set up a network deployment environment on 2 Linux EC2 instances.
We will use WAS 18.104.22.168 ND Trial for test.
Here are the links that provided in the video:
As you know , AWS EC2 doesn't support multicast since all instances are using virtual network (VPC). However WAS will use multicast (NODE_MULTICAST_DISCOVERY_ADDRESS) between nodeagent and its managed jvms for discovering each other.
I did some tests and didn't see any discovery issue between nodeagent and managed processes. So I suspect that AWS do not support multicast between instances, but multicast within a instance is fine (nodeagent and its managed processes are always located within same instance).
But that's only my conjecture and I could not find official document for more details.
Here are some clue that may support my point:
"Currently, AWS do not officially support broadcast or multicast out of the box" --- How to enable broadcast and multicast support on Amazon (AWS) EC2
"Recently, for an Intershop on Amazon Web Services Proof of Concept, a requirement was to enable multicast traffic between two EC2 instances, each running in another availability zone. As you might know, multicast traffic is natively not supported on AWS VPC, not in an availability zone nor between availability zones." --- Multicast on AWS
So based on above I think multicast restriction will not affect WAS.
Please let me know if you have any question.