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 ports.

Opening Ports on AWS for SUP

The SUP documentation is very specific about required ports. You can find the specific list here. The documentation and a little common sense will help guide you through which ports need to be opened inbound vs. outbound vs. both. For example, port 5001, used by the SUP Messaging Service will require both inbound and outbound capabilities as it handles both requests and responses to client devices.

It is important to note that SUP is currently only supported in the Windows environment. The exact hardware requirements are detailed in the Sybase documentation here.  Since SUP has a Windows dependency you potentially have three tiers of security that you will have to create rules for in order to get started.

The first tier is probably the simplest. AWS has developed a security group feature by which you can define inbound rules for several protocols, such as TCP, UDP, and ICMP. There are also some standard ports that can be opened by name as well such as SSH (port 22), MYSQL (3306), and HTTP (port 80) to name just a few. You can also create custom rules for non-standard ports. Setting these up is pretty trivial and it shouldn’t take long to figure this portion out.

AWS port configuration for SUP installation

 

The next tier requires creating corresponding rules in the Windows firewall.  For anyone experienced in Windows Server administration this will be pretty simple. I recommend that you create a separate rule for each required port. This can be somewhat cumbersome, but it will give you a lot of flexibility in the long run.

The third tier may be the most difficult to tackle as it requires working with your internal IT organization to open required ports in the corporate firewall. Formulating the proper request is the most important aspect of this. Make sure you have all your ducks in a row and tell them exactly what you need and why you need it. Your IT group may look at some of these port requests with a jaundiced eye. Explaining their necessity will be easy if you do your homework. Know why you need it and what it is for and you should have no problem.

Generating The SUP License

Opening the port access may be the most challenging aspect of the cloud deployment. The next step is actually generating your license from the product page. Generating a license will require the MAC address, and your public DNS assigned to your instance after you have associated the elastic IP to it (see my previous post for more details). Generate this license and place the license file in the licenses folder in your SySAM Server installation (also covered in my previous post). During installation this file will be checked so it is absolutely necessary to place this there before moving onto the actual installation.

SUP Installation

The installation of the platform is actually very simple. Once you’ve grabbed your distribution from the product download page and set up your licensing server you’re ready to begin the process.

There are four separate distribution files for SUP. Unzip them into the same directory. This is important. I have found many wayward souls out in the SAP forums that can’t figure out why their workspace looks wrong, or why the Unwired Server won’t start but several of the other components are working. This is because they have unzipped these distributions into separate directories and attempted an install. The files and subdirectories found in the ~/module directories in the distributions must all be in the same place, or only part of the components will install when you run setup.exe. This is a huge source of frustration and I myself banged my head against the wall for quite some time as the installation guide assumes you’d be smart enough to just unzip everything in the same directory. Unfortunately I was not, and sadly I am not alone.

Once this is all sorted out simply begin the actual installation process by running setup.exe in the unzipped folder. You’ll be prompted to select your license type. Pick the served license option, agree to the license for your particular country, and then enter your public DNS for the license server hostname. The default license server port is 27000 and you shouldn’t have to change that. The installer will do a license verification against the server and you should be good to go.

If there is a license verification issue there are a couple things you should check. One, make sure you are using the public DNS for the licensing server. Two, make sure that you have set the computer name to not change on startup via the ec2ConfigService Settings tool that is available on the start menu.

When the license check is complete click through the defaults on the rest of the pages and SUP should begin installing! After this you should be ready to begin connecting to data sources and start creating Mobile Business Objects, which will be the topic for the next post.

Slalom Consulting's Seattle Office Slalom Consulting's Mobile Focus Area
More about Slalom Consulting’s Seattle office. More about Slalom Consulting’s Mobile focus.

subscribe by emailSubscribe to be emailed about new Mobility posts.

About 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.

2 Responses to Installing Sybase Unwired Platform in AWS Part 2 – Installation

  1. Trendy web resource Jesse Anarde

    Awesome blog Jesse Anarde

    Wow I actually your site. If I could make me personally a blog comparable to this, I should probably be as joyful as a speckled young pup.

  2. Mobile Undead says:

    Greetings Mr Anarde,

    Great read, thank you very much for the insight.

    I have a question, and would like to know the possibility of this. How would one go about “pointing” a production environment with a SUP farm and the Data tier on different machines, to a new Sysam server, with newly generated .lic files for this new server, without doing a reinstall of your SUP environment?

    Does SUP store the Sysam Server address somewhere, where it can be altered?

    Love to get some insight.

    Thanks in advance,
    Mobile Zombie

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: