Get your own SAP Sybase ASE, developer edition on Amazon Web Services
You can now create your own SAP Sybase ASE, developer edition environment on Amazon Web Services (AWS).
SAP won't charge you anything for the license, but you will be responsible for operating your own AWS account. Together with our friends at Amazon, we have made two different environments available for you. To get an idea about associated cost, use the AWS pricing calculator here (pre-configured for 4 hours of daily usage on the smallest available size).
These are the environments we made available for you:
|Windows Server 2008 R2 SP1 64-bit||ASE Developer Version |
Red Hat Enterprise Linux 6.4 64-bit
ASE Developer Version
How to create your own developer edition environment
- An SCN user - if you don't have one yet, you can register free of charge here.
- An AWS account - if you don't have one yet, you can register here(click "Sign Up Now"). Have your credit card handy
- A key pair (what is a key pair?) to secure the access to your instance. Find documentation on how to create a key pair here. Remember the provided key name and store the *.pem file on your local hard disk.
- [Note: Make sure to store your *.pem file on your hard drive when prompted. Without the key pair, you will not be able to connect to the OS of your instance via SSH.]
- [Note: key pairs are region-specific. Make sure you create the key pair in the same AWS region you later create your instance in. If you get a ROLLBACK_COMPLETE status after instance creation, it is most likely that your key pair region doesn't match your instance region. In that case, simply create a key pair in the correct region and start the instance creation again]
Part 1 - Accept the SAP Developer License Agreement on SCN
Checked all the prerequisites? Then you're ready to create your own SAP ASE server on Amazon Web Services. The whole process should not take longer than about 15 minutes.
- Start here. Complete the required profile data and click the "Next" button.
- Enter your AWS User ID and click the "Next" button
- Confirm your data by clicking the "Confirm" button
- Read the license agreement carefully and, if you agree, click the "Accept" button.
- You will be handed over to the AWS cloud provisioning wizard for the next step
Part 2 - Create your own SAP ASE instance on AWS
- Once you have completed Part 1, the installation process will jump to the AWS website. You will see the next screen. It provides the default stack name and template URL. You can change the name and click the “Continue” button. Don't change the template URL, though.
- Configure instance size which is bundled choice. The bundle choices are listed in the table at the beginning of this document. The recommended option is m1.medium which should be sufficient for most. Please note, you can change this later in the AWS console if desired.
- You must provide the name of an existing key pair, or you will not be able to create an ssh connection to your instance. If you have not checked the prerequisites and still need to create a key pair, you can do so in the AWS console. [Note: keypairs are region specific]
- Check your ASE stack information summary, and then click on “Continue”.
- You can monitor progress by selecting the stack name and choosing the events tab in the AWS Management Console. You can refresh the status by clicking the refresh button.
- Once the stack has been created and you have CREATE_COMPLETE status, check the output tab for details on AWS instance name, host name and IP address which you will use to connect to your new ASE AWS instance.
- If your stack creation fails, check the events tab to get more information on which step failed. Specific information for each step can be seen in the status and reason columns. This should give you an idea about what went wrong and how to correct it.
- Congratulations! You're done with creating your own ASE image on AWS.
Part 3 - Connect to your SAP ASE server on AWS
- Log into Amazon EC2 and start your SAP Sybase ASE instance. In the “Navigation” frame, navigate to “INSTANCES>Instances”. This should show all your instances in Amazon EC2. Make sure the ASE instance you want to connect to is in “running” state. If not, choose the instance, then click on “Instance Actions” menu, and click on “Start” in the pull down menu.
- Associate your Elastic IP with SAP ASE instance and take note of the Elastic IP (What is an Elastic IP?). After each restart of our AWS instance, this procedure of mapping elastic IP to ASE instance must be repeated. During the first time the IP address is automatically associated. [Note: The Elastic IP makes sure you can connect to your instance with the same host name / IP address every time it's restarted.]
- To associate your Elastic IP with your SAP ASE Instance
- In the “Navigation” frame, navigate to “NETWORK & SECURITY > Elastic IPs”. Check if the IP address is mapped to the ASE Instance, by looking at the “Instance ID” field. If it is already mapped you don’t have to perform any additional steps. Otherwise...
- Choose the Elastic IP address that you want to associate to ASE instance.
- Click "Associate Address" and in the popup box choose your SAP ASE instance as shown.
- Click “Yes, Associate” to confirm association of Elastic IP to ASE instance.
- Make a note of your Elastic IP address. You will need it to connect to this ASE instance in AWS.
- Create rules in your Security group that allow TCP ports 5000-5002 to be accessed. This should be restricted to a known set of IP addresses.
- Edit interfaces file to replace ‘localhost’ with the machine IP address. Use your Elastic IP address for the instance. On Linux the interfaces file is found at $SYBASE/interfaces. On Windows the interfaces file is found at %SYBASE%\ini\sql.ini.
- The initial ASE user/password for ASE has been set to sa/sybase for Linux and sa/blank (no password) for Windows.
Part 4 – Log in to the Linux OS of your AWS instance
Sometimes you may want to connect to your AWS box on the OS level. For example to change the default password of an OS user or to start/stop your SAP ASE server.
The following blog has step by step instructions to connect to Linux Box in Amazon EC2 using the popular ssh client for Window puTTY: http://www.techrepublic.com/blog/datacenter/connect-to-amazon-ec2-with-a-private-key-using-putty-and-pageant/5085
Overview of steps contained in the blog:
- Download putty.exe and puttygen.exe
- From the Key pair (*.pem) file downloaded from Amazon EC2, create a private key file for putty using puttygen.exe
After setting up PuTTY and Pageant:
Open PuTTY on your computer, and enter the Elastic IP Address for your instance in the Host Name (or IP address) field. Click the 'Open' button.
When the connection is opened, enter ‘root’ as the user.
From Linux, you simply need to run ssh -i key.pem externalIP -l root from a terminal window (with key.pem being your downloaded key pair *.pem file and externalIP being the Elastic IP address or hostname of your instance)
- Some corporate firewalls may not allow SSH to Amazon cloud. You may have to work with your IT organization to resolve this.
- To restart the database without restarting the entire Linux instance, perform stop and start operations using the following commands
- Command to start ASE: $SYBASE/$SYBASE_ASE/install/Run_SAPASE
- Command to stop ASE: $SYBASE/$OCS/bin/isql –Usa –Psybase –SSAPASE
- At the prompt type ‘shutdown’, press enter, type ‘go’, press enter
Part 5 – Log in to the Windows OS of your AWS instance
Sometimes you may want to connect to your AWS box on the OS level. For example to start/stop your SAP ASE server.
Use Remote Desktop and specify the Elastic IP address as the server to connect to.
You will be responsible for operating your AWS account and you will have to pay for the hosting costs. In order to control your costs, we suggest you stop your instance when you are not using it. Starting your instance just takes a few minutes, so you can fire it up when you need it. To stop your instance, find it in the AWS console, right click the instance and choose "Stop" from the context menu. To start it again, choose "Start" from the same context menu.
Be aware that AWS also charges you very little money for stopped instances - if you want to stop using your ASE instance on AWS, and you don't want to pay any more monthly bills, make sure to terminate your instance. It will then be permanently deleted. To terminate your instance, choose "Terminate" from the context menu.
AWS also provides tools to monitor your usage, so there are no surprises when you get your monthly bill - from your "My Account / Console" menu on the top right corner of the screen on http://aws.amazon.com, choose "Account Activity" and you will see your activity for the current month.