How to install Worklight Server on Amazon EC2
AndyDingsor 120000QS1R Comments (2) Visits (9556)
AbstractThis article explains how to install IBM Worklight Server on a Linux Virtual Machine (VM) at the Amazon Elastic Compute Cloud (Amazon EC2) service. Amazon EC2 allows account holders to create, start, stop, and terminate VM instances on-demand. Because Amazon encourages consumers of the Linux VMs to use command-line operations instead of graphical interfaces, this article explains how to perform a command-line silent install of Worklight Server using a response file with the IBM Installation Manager.
Main steps- Create account at Amazon Web Services
- Create and start an Amazon Linux Virtual Machine
- Procure installables for IBM Installation Manager and IBM Worklight Server
- Create a response file for Installation Manager silent install
- Install and start Worklight Server
Prereqs- Access to physical media containing installables for IBM Worklight Server
- A linux laptop or real linux desktop computer (required temporarily to create the response file used to install Worklight Server)
- A valid email address, credit card, and working telephone (required to create an Amazon account)
Create an account at Amazon Web ServicesFamiliarize yourself with the Amazon EC2 service: http
Have your email, credit card, and telephone handy, then browse to http
Create and start a Virtual MachineSign in to Amazon with your new ID and password: http
Click in the upper-right "My Account / Console" -> "AWS Management Console" -> EC2.
In Panel "Navigation", click "Instances"
In Panel "My Instances", click "Launch Instance" -> Classic Wizard -> Continue
Click tab Quick Start-> Amazon Linux-> 64-bit-> Select.
Number of instances: 1 -> Instance Type: Micro (t1 micro 613 MB) -> Launch into EC2 -> No preference -> Continue
Request instances wizard: Instance details: Accept all defaults -> Continue.
Storage Device Configuration: accept defaults -> continue.
Name: Pick a name to identify the VM in the management console. Example: "WL 220.127.116.11 on Amazon Linux 64-bit" -> continue
One-time task: Create a new SSH Key Pair: give it a name. Example: myawskey -> Click the link "Create & Download" -> Save the PEM file.
Note: Amazon creates a new key pair and lets you download the private identity key in a PEM file. It will be used to identify yourself (using option -i) when you SSH into the VM.
Note: On subsequent VM creations, you may re-use your existing PEM file.
Copy the PEM file to a safe location for future use.
Security groups: Names: worklight-server -> Specify open firewall ports: SSH/22 is in the list by default.
Note: I also specified port 8080 here, since that is the port I will select for the WL server to listen upon in a later step. (You may open additional ports as desired.)
Summary -> Launch.
Wait patiently several minutes while the instance is launching.
At the management console, wait for green dot "running", and all checks passed. Example: "2/2 checks passed"
Click on instance name, scroll down to detailed list of information at bottom. Take note of instance hostname (aka Public DNS).
Verify access. SSH to the VM using your PEM file.
Note: On VMs running Amazon Linux, the default userid is ec2-user. (Some other VMs have different default userids.)
Example: ssh -i /hom
For future reference: To stop or restart the VM, check the desired VM, then pull down 'Instance Actions'
Procure IBM installablesThese steps are performed on your laptop or real desktop computer...
IBM Installation Manager
Fetch zip for Installation Manager 1.5.3 (or later) for linux: http
Unzip the Installation Manager zip to a tmp directory.
IBM Worklight Server
Copy Worklight Server installables to a tmp directory. Find the installable repository directory for Worklight Server 18.104.22.168 (or later) on your physical media. Files include:
atoc/, native/, plugins/, repository.config, repository.xml
Copy these files and subdirectories (recursively) to a tmp directory. Example name: 'wee' (for Worklight Enterprise Edition)
Create a zip file containing the Worklight Server files. Example:
Example: zip -rq wl.5
Install the Installation Manager on your laptop or desktop computerThis step is performed on your laptop or real desktop computer...
Install the Installation Manager. Go to the tmp directory where you unzipped the agent installer and issue the install command, then follow the instructions.
Create response file for Installation Manager silent installThese steps are all performed on your laptop or real desktop computer...
Create a temporary directory to store the agent data from Installation Manager.
Define an environment variable to point to your installed IM:
Use the Installation Manager to create response file for installing Worklight Server.
Note: Be sure to specify option skipInstall in order to suppress actual installation of Worklight Server on your laptop
Optional: Specify a meaningful file name for the response file. Example: ec2.
Point IM to the directory where you fetched the Worklight Server installables (ie, directory where atoc/, native/, repository.xml, etc are located)
File-> Preferences-> Repositories-> Add Repository-> Browse->
Select your desired install options for Worklight Server on the VM. For this article, I chose the self-contained Derby database and Liberty Profile server. Example:
Click Install-> check 22.214.171.124-> Next-> accept -> Shared resource directory /opt
IM finishes instantly because nothing is really installed on your laptop (thanks to option skipInstall).
Verify response file was created. Example
This response file will be used for the silent install on the Amazon EC2 VM.
Edit response file. If desired, modify parameters for use on the Amazon EC2 Linux VM. Possible parameters to be changed include:
<profile id='Worklight' inst
Transfer files to the VMFrom your laptop, transfer 3 files from to the Amazon Linux VM using SCP with your PEM file.
- The original Installation Manager zip file
- The Worklight Server zip file which you created
- The response file which you created
scp -i /hom
scp -i /hom
scp -i /hom
InThe remaining steps are performed in the VM...