Getting Started with WOlastic All-In-One Images
Updated: June 2nd, 2009
Prerequisites:
* Amazon AWS Account (Register)
* SSH Client (Mac OS X Terminal is fine)
* Elasticfox (Optional Firefox Plug-In)
Suggested Readings:
* Amazon Elastic Computing Cloud (EC2)
* Introduction to WebObjects Deployment Guide Using JavaMonitor (Apple.com)
Getting Started
1. Log into the Amazon AWS Console (https://console.aws.amazon.com/) and click on the "Amazon EC2" tab above. If you are not already logged in, it will ask for your Amazon AWS credentials. Please furnish them to continue.
2. You will be brought to a screen with a "Navigation" pane on the left and the "Amazon EC2 Console Dashboard" on the right pane. There are usually four sub-sections in the right pane labeled, "Getting Started", "My Resources", "Service Health", and "Related Links". In the "Getting Started" section, click on "Launch Instances". Please note the information below the "Launch Instances" button if your instances will be launched either in "US-East" or "EU-West" regions.
3. You will be presented the "Launch Instance Wizard" with three tabs along the top. Those are "Quick Start", "My AMIs" and "Community AMIs". Click on the "Community AMIs".
4. At the present time, there are over 2,100+ community AMI's in the US-East region. Under the "Viewing:" section there are two pull-down menus and a search text box. Change the "All Images" pull-down to "Public Images" and enter "wolastic" as the search term. You should see something similar to this:
4. Always verify the AMI ID that you're about to launch (highlighted in red in the above picture) with the AMI IDs from the WOlastic.com homepage. At the time of this writing, the latest version of WOlastic 32-bit All-In-One for US-East region is 20090601 which has an AMI ID of ami-f736d09e. Find the proper AMI ID and hit "Select" to the right of the "Manifest" & "Platform" information.
5. If you have already used AWS in the past, you may skip the next three sections. If this is the first time you've used AWS, you will be presented with the following screens:
* You will now be presented with creating a new "Key Pair" for AWS. This is an SSH key pair that's used to allow you to login to your EC2 instances. You can either "Skip this" at this point, or create a new key pair but it is not necessary for the WOlastic images. If you wish to create a key pair, enter a name for it (i.e. firstinitial-lastname) and "Create & Download your Key Pair". Save the created PEM file in a safe place then click "Continue".
* Next screen you will be presented with if this is the first time using EC2 is the "Configure Firewall" screen. You can also either "Skip this" or continue. Ports at the very minimum that should be open are SSH (port 22) and HTTP (port 80). If you want access to JavaMonitor, you need to open port 56789. You can restrict by IP address and JavaMonitor does not have a set-password in WOlastic so if you want to open port 56789 to the world (0.0.0.0/0), make sure you set a JavaMonitor password as soon as the instance is brought up.
* If you want to fill this section out, create a "wolastic" security group and enter the "Description" as "WOlastic All-In-One Instances". Then click "Continue".
6. Finally, you'll be presented with the "Launch Instance Wizard". It should look similar to this:
7. It will show the "AMI Name", "Number of Instances" you wish to create, "Instance Type (32-bit)", "Key Pair Name", and "Security Groups" the instance should belong too. Since we're working with a 32-bit WOlastic CentOS-based image, we're only allowed two different instance types. Those are m1.small and c1.medium. You can read more about EC2 Instance types at Amazon EC2's documentation. Both instance types have 1.7GB of memory (RAM) but the c1.medium has two virtual cores versus one virtual core of the m1.small.
8. For the purpose of launching, again, check the AMI ID to make sure it's the one you want to launch. Enter the number of instances you would like to start, the "Instance Type" (e.g. m1.small), set the "Key Pair Name" to "No Key Pair" and choose which "Security Groups" the instance should be in (e.g. either "Default" or "wolastic" or combination of existing security groups if you have them). Then click "Launch".
9. You should see a confirmation in green stating, "Your instances are now launching". Click "Close" to be brought back to the "Amazon EC2 Console Dashboard". On the left "Navigation" pane, click the "Instances" link. You will be shown a list of "My Instances" running under your account. You should see your "Instance" with a yellow "Status" of "Starting". You can manually refresh the status of your instance by clicking the "Refresh" button towards the upper-right hand corner. The status should change from "Starting" to "Pending" to finally a green "Running" status which should look similar to this:
10. Also at this time, you will now see the public IP address given to your instance. You can now select the instance and a second pane will open below with information about your instance. You can copy the "Public DNS" entry to your clipboard and paste it into a browser. If you've allowed port 80 open with the associated "Security Group" for that instance, you should see the following screen:
11. If you don't have port 80 opened, select "Security Groups" on the left "Navigation" pane and select the security group which the instance is running under. Make sure "HTTP" is allowed; If not, add it, save it, and try again.
The "AjaxExample" WebObjects Application is installed by default from Project WONDER. You should be able to access it with the following URL:
* http://your-public-DNS-amazon-EC2-wolastic-instance/cgi-bin/WebObjects/AjaxExample
You should see a screen similar to this:
12. If you have opened up port 56789 for JavaMonitor, you would use the following URL to access JavaMonitor:
* http://your-public-DNS-amazon-EC2-wolastic-instance:56789/
You should see a JavaMonitor screen similar to this:
JavaMonitor Instance running on WOlastic All-In-One Image
Accessing your Instance
The default SSH credentials for the WOlastic All-In-One Images are:
* Username: appserver
* Password: wolastic1
Please SSH in and immediately change your SSH password! There are softlinks in the home directory for the "appserver" user to easily deploy WebObjects Applications and to access WebObjects logs. Use the "Application Configuration" of the included "AjaxExample" application in JavaMonitor as a skeleton of how to setup applications.
More advanced topics will follow including starting up and using MySQL and/or PostgreSQL which are pre-loaded on the WOlastic All-In-One Images and for more advanced configurations.
Updated: June 2nd, 2009
Prerequisites:
* Amazon AWS Account (Register)
* SSH Client (Mac OS X Terminal is fine)
* Elasticfox (Optional Firefox Plug-In)
Suggested Readings:
* Amazon Elastic Computing Cloud (EC2)
* Introduction to WebObjects Deployment Guide Using JavaMonitor (Apple.com)
Getting Started
1. Log into the Amazon AWS Console (https://console.aws.amazon.com/) and click on the "Amazon EC2" tab above. If you are not already logged in, it will ask for your Amazon AWS credentials. Please furnish them to continue.
2. You will be brought to a screen with a "Navigation" pane on the left and the "Amazon EC2 Console Dashboard" on the right pane. There are usually four sub-sections in the right pane labeled, "Getting Started", "My Resources", "Service Health", and "Related Links". In the "Getting Started" section, click on "Launch Instances". Please note the information below the "Launch Instances" button if your instances will be launched either in "US-East" or "EU-West" regions.
3. You will be presented the "Launch Instance Wizard" with three tabs along the top. Those are "Quick Start", "My AMIs" and "Community AMIs". Click on the "Community AMIs".
4. At the present time, there are over 2,100+ community AMI's in the US-East region. Under the "Viewing:" section there are two pull-down menus and a search text box. Change the "All Images" pull-down to "Public Images" and enter "wolastic" as the search term. You should see something similar to this:
Launching a WOlastic AMI from the Amazon AWS Console
4. Always verify the AMI ID that you're about to launch (highlighted in red in the above picture) with the AMI IDs from the WOlastic.com homepage. At the time of this writing, the latest version of WOlastic 32-bit All-In-One for US-East region is 20090601 which has an AMI ID of ami-f736d09e. Find the proper AMI ID and hit "Select" to the right of the "Manifest" & "Platform" information.
5. If you have already used AWS in the past, you may skip the next three sections. If this is the first time you've used AWS, you will be presented with the following screens:
* You will now be presented with creating a new "Key Pair" for AWS. This is an SSH key pair that's used to allow you to login to your EC2 instances. You can either "Skip this" at this point, or create a new key pair but it is not necessary for the WOlastic images. If you wish to create a key pair, enter a name for it (i.e. firstinitial-lastname) and "Create & Download your Key Pair". Save the created PEM file in a safe place then click "Continue".
* Next screen you will be presented with if this is the first time using EC2 is the "Configure Firewall" screen. You can also either "Skip this" or continue. Ports at the very minimum that should be open are SSH (port 22) and HTTP (port 80). If you want access to JavaMonitor, you need to open port 56789. You can restrict by IP address and JavaMonitor does not have a set-password in WOlastic so if you want to open port 56789 to the world (0.0.0.0/0), make sure you set a JavaMonitor password as soon as the instance is brought up.
* If you want to fill this section out, create a "wolastic" security group and enter the "Description" as "WOlastic All-In-One Instances". Then click "Continue".
6. Finally, you'll be presented with the "Launch Instance Wizard". It should look similar to this:
Final steps to launching a WOlastic All-In-One Instance
7. It will show the "AMI Name", "Number of Instances" you wish to create, "Instance Type (32-bit)", "Key Pair Name", and "Security Groups" the instance should belong too. Since we're working with a 32-bit WOlastic CentOS-based image, we're only allowed two different instance types. Those are m1.small and c1.medium. You can read more about EC2 Instance types at Amazon EC2's documentation. Both instance types have 1.7GB of memory (RAM) but the c1.medium has two virtual cores versus one virtual core of the m1.small.
8. For the purpose of launching, again, check the AMI ID to make sure it's the one you want to launch. Enter the number of instances you would like to start, the "Instance Type" (e.g. m1.small), set the "Key Pair Name" to "No Key Pair" and choose which "Security Groups" the instance should be in (e.g. either "Default" or "wolastic" or combination of existing security groups if you have them). Then click "Launch".
9. You should see a confirmation in green stating, "Your instances are now launching". Click "Close" to be brought back to the "Amazon EC2 Console Dashboard". On the left "Navigation" pane, click the "Instances" link. You will be shown a list of "My Instances" running under your account. You should see your "Instance" with a yellow "Status" of "Starting". You can manually refresh the status of your instance by clicking the "Refresh" button towards the upper-right hand corner. The status should change from "Starting" to "Pending" to finally a green "Running" status which should look similar to this:
Information on your WOlastic All-In-One Instance Running
10. Also at this time, you will now see the public IP address given to your instance. You can now select the instance and a second pane will open below with information about your instance. You can copy the "Public DNS" entry to your clipboard and paste it into a browser. If you've allowed port 80 open with the associated "Security Group" for that instance, you should see the following screen:
Default CentOS Apache HTTP Splash Page
11. If you don't have port 80 opened, select "Security Groups" on the left "Navigation" pane and select the security group which the instance is running under. Make sure "HTTP" is allowed; If not, add it, save it, and try again.
The "AjaxExample" WebObjects Application is installed by default from Project WONDER. You should be able to access it with the following URL:
* http://your-public-DNS-amazon-EC2-wolastic-instance/cgi-bin/WebObjects/AjaxExample
You should see a screen similar to this:
AjaxExample WebObjects Application running on WOlastic All-In-One
12. If you have opened up port 56789 for JavaMonitor, you would use the following URL to access JavaMonitor:
* http://your-public-DNS-amazon-EC2-wolastic-instance:56789/
You should see a JavaMonitor screen similar to this:
JavaMonitor Instance running on WOlastic All-In-One ImageAccessing your Instance
The default SSH credentials for the WOlastic All-In-One Images are:
* Username: appserver
* Password: wolastic1
Please SSH in and immediately change your SSH password! There are softlinks in the home directory for the "appserver" user to easily deploy WebObjects Applications and to access WebObjects logs. Use the "Application Configuration" of the included "AjaxExample" application in JavaMonitor as a skeleton of how to setup applications.
More advanced topics will follow including starting up and using MySQL and/or PostgreSQL which are pre-loaded on the WOlastic All-In-One Images and for more advanced configurations.
Leave a comment