Installing Sybase Unwired Platform in AWS Part 2 – Installation

This is second in a series of posts by Jesse which he calls “Unwiring the Enterprise—Slalom Experiments in the Cloud” about deploying the Sybase Unwired Platform in the Amazon Web Services environment.

Slalom Consultant Jesse Anarde

Slalom Consultant Jesse Anarde is an experienced developer, DBA, and BI specialist who is a resident expert on the Sybase Unwired Platform with Slalom Consulting's National Mobility team.

Once you’ve configured Amazon Web Services (AWS) to accommodate the licensing requirements of the Sybase Unwired Platform (SUP)—for more about this, if you haven’t already you may want to read my previous post, Installing Sybase Unwired Platform in AWS Part 1 – Licensing—you’re ready to install.

Assumptions: This installation assumes that you are deploying SUP 2.0, onto a m1.large Amazon Machine Image (AMI) running Windows 2008 Server R2.

SUP is essentially a set of several Sybase products that work together to provide a series of interfaces and services to help facilitate rapid mobile application integration.  There are three components to SUP: The Unwired Server, the Data Tier, and the Unwired Workspace. Each of these requires specific port access for both internal and external functions. These port requirements introduce a certain amount of complexity when preparing an SUP installation in the cloud and it is easy to get lost in the morass of security tiers and port dependencies.

Let’s start with the required Read more of this post

Installing Sybase Unwired Platform in AWS Part 1 – Licensing

This is first in a series of posts by Jesse which he calls “Unwiring the Enterprise—Slalom Experiments in the Cloud” about deploying the Sybase Unwired Platform in the Amazon Web Services environment.

Slalom Consultant Jesse Anarde

Slalom Consultant Jesse Anarde is an experienced developer, DBA, and BI specialist who is a resident expert on the Sybase Unwired Platform with Slalom Consulting's National Mobility team.

One of the advantages of the Amazon Web Services (AWS) Elastic Compute Cloud (EC2) feature is the ability to quickly spin up an enterprise class server for a relatively low price. This can accelerate a project significantly and reduce costs in a very meaningful way. However, since AWS is essentially a huge virtualization farm, when it comes to Sybase licensing, there are several pitfalls that one can fall into while configuring a Sybase Unwired Platform (SUP) environment.  Most of these can be easily mitigated by keeping a couple of rules in mind and by using readily available tools in the AWS toolkit.

All AWS instances are virtual machines. Sybase’s license generation requires the physical address of the machine (MAC Address) and the hostname to bind the license to the SUP host.  So what does this mean?

Firstly it means you cannot terminate the instance without invalidating the license. You can reboot the instance, but you have to do a couple things to afford you this freedom. When you initially set up your AWS instance it must be initialized as an Elastic Block Storage (EBS) backed instance (rather than an EC2 instance store-backed AMI on S3). EBS instances can be rebooted (but still not terminated) without losing your MAC Address.

Secondly it means that you will also need Read more of this post

Follow

Get every new post delivered to your Inbox.

Join 126 other followers

%d bloggers like this: