Installing the Blaze Trial AMI
The SQLstream Blaze Trial AMI is an Amazon Machine Image that contains an Ubuntu Server with Oracle JDK 1.7 and lsb-core installed, and SQLstream s- Using the AWS Marketplace Blaze AMI Server, and SQLstream StreamLab installed in the Ubuntu environment. In runs in the Amazon Compute Cloud, known in shorthand as EC2.
Amazon Machine Images run as virtual machines in the cloud. For more information, see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html.
To use the Blaze Trial AMI, it is helpful, but not mandatory, to have experience with Amazon EC2. If you haven't worked with EC2 before, you will need to both create an Amazon Web Services account and generate a public/private keypair for EC2. These are explained below.
To access the Blaze Trial AMI you first need an Amazon Web Services account. Once you have your AWS account set up, contact SQLstream support at firstname.lastname@example.org and give us your AWS account number. SQLstream support will enable then access to the Blaze AMI for your AWS account.
Note: The AMI default location is Northern California. If you need your AMI to be accessed from a different region, please let technical support know when you give them your account number.
Amazon EC2 uses public/private key crytography to secure login data. To log into an instance on EC2, you will need a public/private keypair. If you have used AWS in the past, you likely have one of these. They can also be created through the AWS site. See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html for more details.
For more information on launching images, see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/launching-instance.html.
Contents of AMI
The Blaze AMI is built on an Ubuntu Server with Oracle JDK 1.8.0_25 installed manually. Everything else (other than the SQLstream software) is installed from standard Ubuntu packages.
In order to accommodate s-Server's installation requirements, the following are preinstalled:
The installers for SQLstream Blaze are also included:
Both s-Server and StreamLab are installed as root with --mode unattended, so the following are all started as services on the AMI:
The AMI runs as an EC2 virtual server.
To launch an instance of the AMI:
Open https://console.aws.amazon.com/ and log in with your Amazon Web Services user name and password. If you do not have an AWS account, you will need to register for one before launching the Blaze AMI.
|1.||Click EC2 under Amazon Web Services:|
The EC2 dashboard opens.
|2.||On the bottom of the page, click the Launch Instance button.|
The AMI launch page opens.
|3.||In the left column, click Community AMIs.|
|4.||Enter "SQLstream" in the search box and press Enter or Return.|
SQLstream Blaze 5.1.0/StreamLab 2.1.1 should return as a search result.
|6.||Next, select an image type for the AMI. To run the Blaze AMI, you should select an image type of at least m3.large. We recommend this minimal requirement for demonstration purposes. For production use, you should choose an image type of m3.xlarge or higher. The key here is the number of virtual CPUs available. m3.large provides two CPUs, which is minimal to run s-Server and a data generator in order to run the Mochi demo.|
|7.||Click Next: Configure Instance Details. The Configure Instance Details page opens.|
|8.||In the Configuring Instance Details page, leave settings at their default and click Next: Add Storage.|
|9.||For demo purposes, you do not need to add additional storage. Accept defaults here and click Next: Tag Instance.|
Tags help you manage your AWS resources. These are not mandatory. See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html for more details.
|10.||The Marketplace Blaze AMI has configured a security to allow access to the ports listed below. With the exception of SSH (22) and HTTP(80), all other security groups should be set as a "Custom TCP Rule." Confirm that settings are as follows:|
|•||22 (SSH) if you want to be able to get to the shell|
|•||80 (HTTP) for the home page|
|•||5570 (SDP2) for sqlline and s-Server access|
|•||5585 (ROSE) used by StreamLab|
|•||5591 (StreamLab web socket)|
Note: Port 22 may be listed by default. The instance will not launch if two security rules are the same.
The next page asks you to review the instance details.
|11.||Once you have reviewed the details, click Review and Launch.|
The next page presents asks you to select a public/private key pair, as described above. If you are new to AWS, you need to generate a new key pair. If you have previously generated an AMI key pair, you can use that one. See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html for more information on generating key pairs.
|12.||Check the box next to I acknowledge that I have access and click Launch Instance.|
Note: In the screenshot above, a public/private key pair named Blaze has been previously created.
After you launch the instance, follow the steps below in order to access the Blaze AMI cover page:
|1.||Return to the EC2 dashboard and choose Instances in the left column.|
|2.||In the list of instances, find the instance of SQLstream Blaze.|
|3.||To the right, you will see a column labeled Public DNS Address. This will be something similar to ec2-54-193-200-69.us-west-1.compute.amazonaws.com. Select and copy this address and paste it into a browser address bar.|
Once you do so, you will see a web page with the SQLstream logo and a list of available options:
In order to use Blaze, you will need to enter registration information. When you first install SQLstream s-Server, you register for a license, and will receive an email from our license server with a link that lets you activate this license. Once you activate your license, you can run s-Server for 60 days of product evaluation. This trial license places no limit on the number of parallel number of threads in SQLstream s-Server. After the trial license expires, you need to request a new trial license from SQLstream. See the topic SQLstream s-Server Licensing for more details.
There is an indicator on the AMI home page at the bottom of the Welcome! section right before the Demonstration section, that indicates the status of s-Server. Once s-Server is connected, it will say "Server is listening on port 5570." This indicator will not display a "listening" message until installation completes.
From the Blaze AMI launch page, you can do the following:
|•||Run the Mochi demo|
|•||Use StreamLab, using a built-in stream of bus location data.|
|•||Download s-Studio for Windows to view the server and SQL.|
The Mochi demonstration application simulates clusters of failed logins at a bank, either by phone or web, as well as withdrawals or debits using the same customer id number. See the topic Running the Mochi Demo for more details.
To run the Mochi demo, click the "Start Mochi Demo" link. Like the installation of s-Server, this process takes some time to initiate. We recommend waiting 5 minutes to allow the Mochi demo to start.
Next, click the "View Mochi Demo" link. This will open a new tab or window in your browser pointing to the dashboard list. If it fails, it probably means you didn't wait long enough. Close the window, wait a little longer, and try again.
When you're done with the demo, you can either use the "Stop Mochi Demo" link to shut it down cleanly, or just terminate the EC2 instance if you're done using it. If you are going to move on to use StreamLab, you need to stop the Mochi demo cleanly.
StreamLab is a web application development environment that automatically generates streaming SQL. StreamLab lets you set up projects where you can parse incoming streaming data, generate real time analytics for it, visualize it, so that you can take action on it. See StreamLab Guide for more details.
The Launch page links to a video tutorial that walks you through using Stream
SQLstream provides sample data to use with StreamLab. This is a continually-updating file in JSON format. For more information on using StreamLab with bus data, see the topic Using StreamLab to Build a Streaming Application in the Building Streaming Applications with SQLstream Blaze guide.
To run StreamLab, click the Try StreamLab 2.1.1 link.
You can download and install SQLstream s-Studio. Once you do, you can configure s-Studio to connect with your AMI Blaze instance by taking the following steps:
|1.||Copy the JDBC address from the top of the AMI launch page.|
|3.||Right-click First SQLstream Server.|
|4.||Paste the JDBC address into the URL field and click OK.|
|5.||Right-click First SQLstream Server again and select Connect.|
|6.||Studio should connect to s-Server and display a list of schemas, data sources, plugins, and so on.|
When you're done using the instance, you should stop it, either from the EC2 Management Console or from the command line.