Before you begin this process, make sure you have a valid key pair. If you do not have one, follow the instructions on the AWS documentation site: http://docs.aws.amazon.com/gettingstarted/latest/wah/getting-started-create-key-pair.html.
| The procedures in this section work for both Professional and Enterprise AMIs. |
Creating a JasperReports Server Instance
A stack is a collection of AWS resources you create and delete as a single unit. Our CloudFormation template will create the following:
| • | IAM role with permissions on RDS and Redshift |
| • | EC2 instance with JasperReports Server installed and configured and using this role in order to have appropriate credentials. |
To create a new JasperReports Server instance:
| 1. | Navigate to the URL for your region. |
If you are using AWS hourly, choose from among the following links:
Region | AWS Hourly URL |
US East (N. Virginia) | http://www.jaspersoft.com/jrs-launch-instance?region=us-east-1 |
US West (Oregon) | http://www.jaspersoft.com/jrs-launch-instance?region=us-west-2 |
US West (N. California) | http://www.jaspersoft.com/jrs-launch-instance?region=us-west-1 |
EU (Ireland) | http://www.jaspersoft.com/jrs-launch-instance?region=eu-west-1 |
Asia Pacific (Singapore) | http://www.jaspersoft.com/jrs-launch-instance?region=ap-southeast-1 |
Asia Pacific (Tokyo) | http://www.jaspersoft.com/jrs-launch-instance?region=ap-northeast-1 |
Asia Pacific (Sydney) | http://www.jaspersoft.com/jrs-launch-instance?region=ap-southeast-2 |
South America (São Paulo) | http://www.jaspersoft.com/jrs-launch-instance?region=sa-east-1 |
If you are using AWS with Multi-Tenancy hourly, choose from among the following links:
Region | AWS Hourly URL |
US East (N. Virginia) | http://www.jaspersoft.com/jrs-launch-instance?region=us-east-1&type=JRSHourlyInstance&ami=hourly-mt |
US West (Oregon) | http://www.jaspersoft.com/jrs-launch-instance?region=us-west-2&type=JRSHourlyInstance&ami=hourly-mt |
US West (N. California) | http://www.jaspersoft.com/jrs-launch-instance?region=us-west-1&type=JRSHourlyInstance&ami=hourly-mt |
EU (Ireland) | http://www.jaspersoft.com/jrs-launch-instance?region=eu-west-1&type=JRSHourlyInstance&ami=hourly-mt |
Asia Pacific (Singapore) | |
Asia Pacific (Tokyo) | |
Asia Pacific (Sydney) | |
South America (São Paulo) | http://www.jaspersoft.com/jrs-launch-instance?region=sa-east-1&type=JRSHourlyInstance&ami=hourly-mt |
If you are using BYOL, choose from among the following links:
Region | AWS BYOL URL |
US East (N. Virginia) | http://www.jaspersoft.com/jrs-launch-instance?region=us-east-1&ami=byol |
US West (Oregon) | http://www.jaspersoft.com/jrs-launch-instance?region=us-west-2&ami=byol |
US West (N. California) | http://www.jaspersoft.com/jrs-launch-instance?region=us-west-1&ami=byol |
EU (Ireland) | http://www.jaspersoft.com/jrs-launch-instance?region=eu-west-1&ami=byol |
Asia Pacific (Singapore) | http://www.jaspersoft.com/jrs-launch-instance?region=ap-southeast-1&ami=byol |
Asia Pacific (Tokyo) | http://www.jaspersoft.com/jrs-launch-instance?region=ap-northeast-1&ami=byol |
Asia Pacific (Sydney) | http://www.jaspersoft.com/jrs-launch-instance?region=ap-southeast-2&ami=byol |
South America (São Paulo) | http://www.jaspersoft.com/jrs-launch-instance?region=sa-east-1&ami=byol |
The Select Template page appears.
Select Template page |
|
| 2. | On the Select Template page, perform the following steps: |
| a. | In the Stack section of the page, give your CloudFormation stack a unique name. |
| b. | By default, AWS provides a stack template source URL. Do not change this selection. |
| 3. | Click Next. The Specify Parameters page appears. |
Specify Parameters page |
|
| 4. | On the Specify Parameters page: |
| a. | In the Instance Type field, copy and paste any of the supported instance types from the descriptions: |
| • | Standard Medium (m1.medium) |
| • | Standard Large (m1.large) |
| • | Standard XL (m1.xlarge) |
| • | High-Memory XL (m2.xlarge) |
| • | High-Memory 2XL (m2.2xlarge) |
| • | High-Memory 4XL (m2.4xlarge) |
| • | M3 Medium (m3.medium) |
| • | M3 Large (m3.large) |
| • | M3 XL (m3.xlarge) |
| • | M3 2XL (m3.2xl) |
| • | High-CPU XL (c1.xlarge) |
Performance may vary based on system attributes, such as network bandwidth, memory requirements for a given use case, query requirements, and the like.
| b. | Enter an existing key pair name. |
 | For AWS with Multi-Tenancy Hourly, the only instances available are m1.medium and m3.medium.These two instances are recommended only for basic evaluation and development. |
For more information about EC2 instance types, see the AWS documentation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html
| 5. | Click Next. The Options page appears. |
| 6. | On the Options page, add any tags you want to simplify administration of your infrastructure. |
A tag consists of a key/value pair and will flow to resources inside your stack. You can add up to 10 unique keys to each instance, along with an optional value for each key.
| 7. | Expand the Advanced section of the Options page and set your notification, timeout, and other options. |
| 8. | Click Next. The Review page appears. |
Double-check your template, parameter, and option information.
| 9. | Click Create. |
A message appears telling you that your stack has been created. On the Services web page, your stack probably says “CREATE_IN_PROGRESS”. It generally takes two to four minutes for the status to change to “CREATE_COMPLETE”.
| It can still take another few minutes for the JasperReports Server URL to become available after the stack shows create_complete. If you get a message saying “Unable to Connect”, try again in a few minutes. |
| 10. | Select your new instance once its status is create_complete, and then click the Outputs tab. |
Your URL for Getting Started with JasperReports Server appears.
Creating a JasperReports Server Instance from the EC2 Console
If you have a complex network topology, special volume requirements, or if your instance needs to be in VPC, you might need to create your instance from the EC2 Console.
Before you can create a JasperReports Server instance from the EC2 console, you need to create a CloudFormation role. If you skip this step, when you get to the Welcome screen, you will see the following error message:
Missing Role Error Message |
|
To create a CloudFormation role:
| 1. | Sign in with your AWS account. |
| 2. | Navigate to http://www.jaspersoft.com/jrs-create-role. |
The Select Template page appears.
Select Template page |
|
| 3. | In the Select Template page: |
| a. | Give your CloudFormation stack a unique name. |
| b. | By default, AWS provides a stack template source URL. Do not change this selection. |
| 4. | Click Continue. The Specify Parameters page appears. |
On the Specify Parameters page check the box to acknowledge that the template can create IAM (Identity and Access Management) resources. Checking the box is mandatory.
Be sure to select the correct AMI (hourly or BYOL).
| 5. | Click Next. The Options page appears. |
| 6. | On the Options page, add any tags you want to simplify administration of your infrastructure. |
A tag consists of a key/value pair and will flow to resources inside your stack. You can add up to 10 unique keys to each instance, along with an optional value for each key.
| 7. | Expand the Advanced section of the Options page and set your notification, timeout, and other options. |
| 8. | Click Next. The Review page appears. |
Double-check your information and parameters.
| 9. | Click Next. A window appears to say your stack is being created. |
| 10. | Click Close. The CloudFormation Stacks page appears. Your new stack will say CREATE_IN_PROGRESS until it is finished being created and CREATE_COMPLETE once it is ready to be used. |
| 11. | Click the Outputs tab. |
Outputs Tab Showing RoleName and Description |
|
You see the RoleName for the stack you created. Note the value carefully, because you need it in the next procedure.
To create a JasperReports Server instance from the EC2 console:
| 1. | Navigate to: http://aws.amazon.com/console/. |
| 2. | Sign in with your AWS account. |
| 3. | Go to Compute & Networking > EC2. |
The Resources page opens.
| 4. | On the left, click Images > AMIs. |
Make sure that the All Images option is selected and appears at the top of the page.
| 5. | Enter Jaspersoft BI Professional in the Search box. |
| 6. | Select the AMI Jaspersoft for AWS, the AMI for AWS with Multi-Tenancy Hourly, or the AMI Jaspersoft for AWS (BYOL), and click the Launch button at the top of the page. |
| Make sure you select the correct AMI for you license: Hourly or BYOL |
The Choose an Instance Type page opens.
| 7. | Choose an Instance Type from the list. |
Instance Type list |
|
Supported instance types are:
| • | Standard Medium (m1.medium) |
| • | Standard Large (m1.large) |
| • | Standard XL (m1.xlarge) |
| • | High-Memory XL (m2.xlarge) |
| • | High-Memory 2XL (m2.2xlarge) |
| • | High-Memory 4XL (m2.4xlarge) |
| • | M3 Medium (m3.medium) |
| • | M3 Large (m3.large) |
| • | M3 XL (m3.xlarge) |
| • | M3 2XL (m3.2xl) |
| • | High-CPU XL (c1.xlarge) |
If you choose an unsupported instance type, you receive an error message. Select a different image and continue following these instructions.
| 8. | Click Next: Configure Instance Details at the bottom of the page, and configure the following details. Mouse over the information icon  |
| • | Number of instances |
| • | Purchasing option |
| • | Network |
| • | Availability Zone (if using EC2) or Subnet (if using VPC) |
| • | IAM role |
| • | Shutdown behavior |
| • | Enable termination protection |
| • | Monitoring |
| 9. | Expand the Advanced Details section of the page and configure the following details. Mouse over the information icon  |
| • | Kernel ID |
| • | RAM disk ID |
| • | User data |
| 10. | Click Next: Add Storage at the bottom of the page, and review the details. Click items you want to edit. You can add EBS and instance store volumes by clicking the Add New Volume button. |
| 11. | Click Next: Tag Instance at the bottom of the page, and add tags, if needed, in the text entry boxes. Add additional tags by clicking the Create Tag button. |
A tag consists of a key/value pair and will flow to resources inside your stack. You can add up to 10 unique keys to each instance, along with an optional value for each key.
| 12. | Click Next: Configure Security Group at the bottom of the page, and configure your firewall rules. Choose an existing security group or create a new security group. |
| We set up one AWS DB Security Group (using IP address) in each RDS region, per JasperReports Server instance. The security group allows connections from the specific JRS instance to the specified AWS database instance. |
| 13. | Click Review and Launch. Review your information, and edit if necessary. |
Double-check your information and parameters.
| 14. | Click Launch. |
| 15. | When prompted, select an existing key pair, or create a new key pair, and click Launch Instances. |
A message appears telling you that your instance is now launching.
Your instances may take a few minutes to launch, depending on the software you are running.
| Usage hours on your new instances will start immediately and continue to accrue until you stop or terminate your instances. |
| 16. | Click Close. |
Logging in to JasperReports Server
Log into JasperReports Server using the Getting Started URL generated when you created your JasperReports Server instance. You can find this URL in the instance's Outputs tab
The initial user is superuser and password is superuser. You must change the password in order to log in.
To log in to JasperReports Server the first time:
| 1. | Click the GettingStartedURL link in your Outputs tab. |
The Welcome to jaspersoft BI page appears.
Welcome to Jaspersoft BI page |
|
| 2. | From the Welcome to Jaspersoft BI page, you can register to receive free online support and premium vixualizations, as well as: |
| • | Learn about Jaspersoft Studio, the open source, Eclipse-based report designer for JasperReports. |
| • | Connect to the Jaspersoft Community forums and the Online Learning Portal, Jaspersoft's self-guided training site. |
| • | Link to the AWS resource center. |
| • | View documentation for all Jaspersoft products, free of charge. |
| 3. | Complete the registration form and click the Sign Up for Free button. If you have already registered with Jaspersoft, click the I've Already Signed Up button. |
The Getting Started page appears.
Getting Started page |
|
| 4. | On the Getting Started page: |
| a. | Click the Watch Video button to watch a short video that shows you how to quickly connect to your AWS data sources. |
| b. | Click the Explore Resources button to visit the Jaspersoft Community Site. |
| c. | Click the Login button to go to the Jaspersoft login page. |
The Welcome to Jaspersoft page appears.
Login Screen |
|
If you are using BYOL, you have a 48-hour license to start. This page will include a reminder of when your license is set to expire and offer slightly different Getting Started links.
Before you click the Login button on this page:
| The initial password for superuser is superuser, but it is pre-configured as expired. You must change the password before your first login. |
| 1. | Enter the User ID superuser and password superuser. |
| 2. | Click Change password. |
| 3. | Set the new password to any password you will remember. |
| 4. | Now, click the Login button. |
The Home screen appears.
Home Screen |
|
| If you use PostgreSQL as your database, note that not all PostgreSQL-supported functions will work with Redshift. See the Redshift documentation for details about supported functions. |
Recommended Comments
There are no comments to display.