TIBCO JasperReports Server on the AWS Cloud · 2020-01-29 · Amazon Web Services – TIBCO...

Page 1 of 21

TIBCO JasperReports Server on the AWS Cloud

Quick Start Reference Deployment

October 2019

Last update: January 2020 (revisions)

TIBCO Jaspersoft team

AWS Quick Start team

Visit our GitHub repository for source files and to post feedback,

report bugs, or submit feature ideas for this Quick Start.

Contents

Overview .................................................................................................................................... 2

TIBCO JasperReports Server on AWS................................................................................... 2

Cost and licenses .................................................................................................................... 3

Architecture ............................................................................................................................... 4

Planning the deployment .......................................................................................................... 5

Specialized knowledge ........................................................................................................... 5

AWS account .......................................................................................................................... 5

Technical requirements ......................................................................................................... 5

Deployment options ............................................................................................................... 6

Deployment steps ...................................................................................................................... 7

Step 1. Sign up for a TIBCO Jaspersoft license...................................................................... 7

Step 2. Sign in to your AWS account ..................................................................................... 7

Step 3. Subscribe to the TIBCO Jaspersoft Reporting and Analytics AMI ........................... 7

Step 4. Launch the Quick Start ..............................................................................................8

https://fwd.aws/XQbkP

Amazon Web Services – TIBCO JasperReports Server on the AWS Cloud January 2020

Page 2 of 21

Option 1: Parameters for deploying cluster TIBCO JasperReports Server into a new

VPC.................................................................................................................................... 10

Option 2: Parameters for deploying cluster TIBCO JasperReports Server into an

existing VPC ...................................................................................................................... 12

Option 3: Parameters for deploying single-instance TIBCO JasperReports Server into a

new VPC ............................................................................................................................ 14

Option 4: Parameters for deploying single-instance TIBCO JasperReports Server into

an existing VPC ................................................................................................................. 16

Step 5. Apply your TIBCO JasperReports Server license .................................................... 17

Step 6. Test the deployment ................................................................................................ 18

Security .................................................................................................................................... 18

Troubleshooting ...................................................................................................................... 18

Send us feedback ..................................................................................................................... 19

Additional resources ............................................................................................................... 19

Document revisions ................................................................................................................ 20

This Quick Start was created by TIBCO Jaspersoft in collaboration with Amazon Web

Services (AWS).

Quick Starts are automated reference deployments that use AWS CloudFormation

templates to deploy key technologies on AWS, following AWS best practices.

Overview

This Quick Start reference deployment guide provides step-by-step instructions for

deploying TIBCO JasperReports Server on the AWS Cloud, following best practices from

AWS and TIBCO.

TIBCO JasperReports Server on AWS

JasperReports Server is a reporting and analytics server for creating, sharing, and

managing reports, dashboards, and data visualizations. It can run on its own as a

standalone server, or it can be embedded into web applications by using comprehensive

APIs and a flexible, open source architecture. JasperReports Server is designed with

http://aws.amazon.com/quickstart/


Page 3 of 21

automatic detection functionality for connecting to Amazon Relational Database Service

(Amazon RDS), Amazon Redshift, and Amazon EMR.

This Quick Start uses AWS CloudFormation templates to generate an automatically scaling,

highly available infrastructure for your JasperReports Server deployment, complete with

multi-tenant support. Using these templates is the preferred method for securely launching

an instance.

This Quick Start is for developers, IT professionals, architects, and other technical users who are planning to implement or extend their deployment of JasperReports Server to the AWS Cloud.

Cost and licenses

You are responsible for the cost of the AWS services used while running this Quick Start

reference deployment. There is no additional cost for using the Quick Start.

The CloudFormation template for this Quick Start includes configuration parameters that

you can customize. Some of these settings, such as instance type, affect the cost of

deployment. For cost estimates, see the pricing pages for each AWS service you will be

using. Prices are subject to change.

Tip After you deploy the Quick Start, we recommend that you enable the AWS Cost

and Usage Report to track costs associated with the Quick Start. This report delivers

billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your

account. It provides cost estimates based on usage throughout each month and

finalizes the data at the end of the month. For more information about the report,

see the AWS documentation.

Complete the Jaspersoft signup form to receive a free evaluation license, valid for 30 days.

Without the key, this Quick Start allows only 3 days of free usage in a non-production

environment. You will need to place the license key in an Amazon S3 bucket and specify its

location when you launch the Quick Start. For more information, see step 3.

Tip To ensure a seamless evaluation experience, TIBCO Jaspersoft strongly

recommends that you secure an evaluation license before launching a deployment

with this Quick Start.

https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-reports-gettingstarted-turnonreports.html

https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-reports-gettingstarted-turnonreports.html

https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-reports-costusage.html

https://www.jaspersoft.com/aws-signup-byol


Page 4 of 21

Architecture

Deploying this Quick Start for a new virtual private cloud (VPC) with default parameters

builds the following TIBCO JasperReports Server cluster environment in the AWS Cloud.

Figure 1: Quick Start architecture for TIBCO JasperReports Server on AWS

The cluster Quick Start sets up the following:

A highly available architecture that spans two Availability Zones.*

A VPC configured with public and private subnets according to AWS best practices, to

provide you with your own virtual network on AWS.*

In the public subnets:

– Managed network address translation (NAT) gateways to allow outbound

internet access for resources in the private subnets.*

– A Linux bastion host in an Auto Scaling group to allow inbound Secure Shell

(SSH) access to EC2 instances in public and private subnets.*


Page 5 of 21

– Application Load Balancers to control the load on the EC2 instances, reachable

from the internet.

In the private subnets:

– TIBCO JasperReports Server cluster deployed on EC2 instances.

– A JasperReports Server repository based on Amazon RDS for PostgreSQL with

Multi-AZ deployment.

An Amazon S3 bucket for the license and for customization.

* The template that deploys the Quick Start into an existing VPC skips the components

marked by asterisks and prompts you for your existing VPC configuration.

Planning the deployment

Specialized knowledge

This Quick Start assumes familiarity with TIBCO JasperReports Server as well as with basic

concepts in the areas of networking, database operations, and cluster setup of web

application servers.

This deployment guide also requires a moderate level of familiarity with AWS services. If

you’re new to AWS, visit the Getting Started Resource Center and the AWS Training and

Certification website for materials and programs that can help you develop the skills to

design, deploy, and operate your infrastructure and applications on the AWS Cloud.

AWS account

If you don’t already have an AWS account, create one at https://aws.amazon.com by

following the on-screen instructions. Part of the sign-up process involves receiving a phone

call and entering a PIN using the phone keypad.

Your AWS account is automatically signed up for all AWS services. You are charged only for

the services you use.

Technical requirements

Before you launch the Quick Start, your account must be configured as specified in the

following table. Otherwise, deployment might fail.

https://aws.amazon.com/getting-started/

https://aws.amazon.com/training/

https://aws.amazon.com/training/

https://aws.amazon.com/


Page 6 of 21

Resources If necessary, request service limit increases for the following resources. You might need

to do this if you already have an existing deployment that uses these resources, and you

think you might exceed the default limits with this deployment. For default limits, see

the AWS documentation.

AWS Trusted Advisor offers a service limits check that displays your usage and limits

for some aspects of some services.

Resource This deployment uses

VPCs 1

Elastic IP addresses 3

VPC security groups 4

IAM roles 2

Auto Scaling groups 2

Application Load

Balancers 1

Regions This deployment includes JasperReports Server, which isn’t currently available in all

AWS Regions.

Key pair Make sure that at least one Amazon EC2 key pair exists in your AWS account in the

Region where you are planning to deploy the Quick Start. Make note of the key pair

name. You’ll be prompted for this information during deployment. To create a key pair,

follow the instructions in the AWS documentation.

If you’re deploying the Quick Start for testing or proof-of-concept purposes, we

recommend that you create a new key pair instead of specifying a key pair that’s already

being used by a production instance.

IAM permissions To deploy the Quick Start, you must log in to the AWS Management Console with IAM

permissions for the resources and actions the templates will deploy. The

AdministratorAccess managed policy within IAM provides sufficient permissions,

although your organization may choose to use a custom policy with more restrictions.

Deployment options

This Quick Start provides four deployment options:

Cluster setup

– Deploy cluster TIBCO JasperReports Server into a new VPC (end-to-

end deployment). This option builds a new AWS environment consisting of the

VPC, subnets, NAT gateways, security groups, bastion host, Amazon RDS

database, and other infrastructure components. It then deploys TIBCO

JasperReports Server into this new infrastructure.

http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html

https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-

http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html

https://console.aws.amazon.com/trustedadvisor/home?#/category/service-limits

https://aws.amazon.com/about-aws/global-infrastructure/

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html

https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html


Page 7 of 21

– Deploy cluster TIBCO JasperReports Server into an existing VPC. This

option provisions TIBCO JasperReports Server in your existing AWS

infrastructure.

Single-instance setup

– Deploy single-instance TIBCO JasperReports Server into a new VPC

(end-to-end deployment). This option builds a new AWS environment

consisting of the VPC, subnets, NAT gateways, security groups, bastion host, and

other infrastructure components. It then deploys TIBCO JasperReports Server

into this new VPC on a single EC2 instance.

– Deploy single-instance TIBCO JasperReports Server into an existing

VPC. This option provisions TIBCO JasperReports Server in your existing AWS

infrastructure.

The Quick Start provides separate templates for these options. It also lets you configure

CIDR blocks, instance types, and TIBCO JasperReports Server settings, as discussed later

in this guide.

Deployment steps

Step 1. Sign up for a TIBCO Jaspersoft license

1. Sign up for a free evaluation license, valid for 30 days.

Step 2. Sign in to your AWS account

1. Sign in to your AWS account at https://aws.amazon.com with an IAM user role that has

the necessary permissions. For details, see Planning the deployment earlier in this

guide.

2. Make sure that your AWS account is configured correctly, as discussed in the Technical

requirements section.

Step 3. Subscribe to the TIBCO Jaspersoft Reporting and Analytics AMI

This Quick Start requires a subscription to the TIBCO Jaspersoft reporting and analytics

AMI in AWS Marketplace.

1. In AWS Marketplace, open the page for the TIBCO Jaspersoft reporting and analytics

AMI, and then choose Continue to subscribe.

2. Review the terms and conditions for software usage, and then choose Accept Terms.

https://www.jaspersoft.com/aws-signup-byol

https://aws.amazon.com/

https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=Jaspersoft+BYOL

https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=Jaspersoft+BYOL


Page 8 of 21

You will get a confirmation page, and an email confirmation will be sent to the account

owner. For detailed subscription instructions, see the AWS Marketplace documentation.

3. When the subscription process is complete, exit out of AWS Marketplace without

further action. Do not provision the software from AWS Marketplace–the

Quick Start will deploy the AMI for you.

Step 4. Launch the Quick Start

Notes The instructions in this section reflect the older version of the AWS

CloudFormation console. If you’re using the redesigned console, some of the user

interface elements might be different.

You are responsible for the cost of the AWS services used while running this Quick

Start reference deployment. There is no additional cost for using this Quick Start.

For full details, see the pricing pages for each AWS service you will be using in this

Quick Start. Prices are subject to change.

4. Sign in to your AWS account, and choose one of the following options to launch the

AWS CloudFormation template. For help with choosing an option, see deployment

options earlier in this guide.

Cluster

Deploy TIBCO JasperReports Server

into a

new VPC on AWS


into an

existing VPC on AWS

• new VPC

• workloadDeploy • workload onlyDeploy

https://aws.amazon.com/marketplace/help/200799470

https://fwd.aws/eaMRr



https://fwd.aws/ygmND






Page 9 of 21

Single-instance


into a

new VPC on AWS


into an

existing VPC on AWS

Important If you’re deploying TIBCO JasperReports Server into an existing VPC,

make sure that your VPC has two private subnets in different Availability Zones for

the workload instances, and that the subnets aren’t shared. This Quick Start doesn’t

support shared subnets. These subnets require NAT gateways in their route tables, to

allow the instances to download packages and software without exposing them to the

internet. You will also need the domain name option configured in the DHCP options

as explained in the Amazon VPC documentation. You will be prompted for your VPC

settings when you launch the Quick Start, as well as JasperReports Server Repository

Database on RDS. You can use the rds-postgres-cluster.template template, which

is provided by TIBCO Jaspersoft, to create the Repository Database for your

JasperReports Server installation.

Each deployment takes about 35 minutes to complete.

5. Check the Region that’s displayed in the upper-right corner of the navigation bar, and

change it if necessary. This is where the network infrastructure for TIBCO

JasperReports Server will be built. The template is launched in the US East (Ohio)

Region by default.

6. On the Select Template page, keep the default setting for the template URL, and then

choose Next.

7. On the Specify Details page, change the stack name if needed. Review the parameters

for the template. Provide values for the parameters that require input. For all other

parameters, review the default settings and customize them as necessary.

In the following tables, parameters are listed by category and described separately for

the four deployment options:

– Parameters for deploying cluster TIBCO JasperReports Server into a new VPC

• new VPC

• workloadDeploy • workload onlyDeploy

https://fwd.aws/Y5JdG



https://fwd.aws/Yr4x6



https://docs.aws.amazon.com/vpc/latest/userguide/vpc-sharing.html

https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html




Page 10 of 21

– Parameters for deploying cluster TIBCO JasperReports Server into an existing

VPC

– Parameters for deploying single-instance TIBCO JasperReports Server into a new

VPC

– Parameters for deploying single-instance TIBCO JasperReports Server into an

existing VPC

When you finish reviewing and customizing the parameters, choose Next.

OPTION 1: PARAMETERS FOR DEPLOYING CLUSTER TIBCO JASPERREPORTS SERVER

INTO A NEW VPC

View template

Network configuration:

Parameter label

(name) Default Description

Availability Zones

(AvailabilityZones)

Requires input The list of Availability Zones to use for the subnets in the VPC.

Only two Availability Zones are used for this deployment, and

the logical order of your selections is preserved.

VPC CIDR

(VPCCIDR)

10.0.0.0/16 The CIDR block for the VPC.

Private subnet 1 CIDR

(PrivateSubnet1CIDR)

10.0.0.0/19 The CIDR block for private subnet 1 located in Availability Zone

1.




2.

Public subnet 1 CIDR

(PublicSubnet1CIDR)

10.0.128.0/20 The CIDR block for the public (DMZ) subnet 1 located in

Availability Zone 1.


(PublicSubnet2CIDR)



Allowed bastion

external access CIDR

(RemoteAccessCIDR)

Requires input The CIDR IP range that is permitted to access the bastion

instances. We recommend that you set this value to a trusted IP

range.

Amazon EC2 configuration:

Parameter label


Key pair name

(KeyPairName)

Requires input The name of an existing public/private key pair, which allows

you to securely connect to your instance after it launches.

https://fwd.aws/m93d5


Page 11 of 21

Parameter label


Bastion AMI operating

system

(BastionAMIOS)

Amazon-Linux-

HVM

The Linux distribution for the AMI to be used for the bastion

instances.

Bastion instance type

(BastionInstanceType)

t2.micro The EC2 instance type for the bastion instances.

Servers instance type

(WorkloadInstanceType)

m4.xlarge The EC2 isntance type for the TIBCO JasperReports Server

instances.

TIBCO JasperReports nodes configuration:

Parameter label


Nodes minimum size

(WorkloadNodesMinSize)

2 The minimum number of nodes in the Auto Scaling group.

Nodes desired capacity

(WorkloadNodesDesired

Capacity)

2 The desired number of nodes in the Auto Scaling group.

Nodes maximum size

(WorkloadNodesMaxSize)

4 The maximum number of nodes in the Auto Scaling group

Operator email address

(OperatorEmail)

Requires input (Optional) The email address that notifications of any scaling

operations will be sent to.

S3 bucket for license

and customization

(NewBucket)

No S3 bucket creation. Choose Yes to create a new bucket where

you can upload third-party drivers, OSGI bundles, certificates,

plugins, etc., to extend the base image later.

Name of S3 bucket for

license and

customization

(S3BucketName)

new-bucket-for-

license-and-

customization

The name of the new S3 bucket. Enter a unique name that does

not include uppercase characters.

Database configuration:

Parameter label


RDS database instance

type

(RDSDbSize)

db.t2.medium The instance type for the Amazon RDS database. Must be one of

the following valid RDS instance types: db.t2.small,

db.t2.medium, db.t2.large, db.m4.large, db.m4.xlarge,

db.m4.2xlarge.

RDS database user

name

(RDSUser)

Requires input The master user name for the Amazon RDS database. It can

contain only alphanumeric characters and underscores.


Page 12 of 21

Parameter label


RDS database

password

(RDSPassword)

Requires input The master password for the Amazon RDS database. It can


RDS database name

(DBName)

jasperserver Database name that will be used for repository creation. It can


Include samples

(IncludeSamples)

No Sample sugarcrm and foodmart databases. Choose Yes if you

want to use the sample data.

AWS Quick Start configuration:

Note We recommend that you keep the default settings for the following two

parameters, unless you are customizing the Quick Start templates for your own

deployment projects. Changing the settings of these parameters will automatically

update code references to point to a new Quick Start location. For additional details,

see the AWS Quick Start Contributor’s Guide.

Parameter label


Quick Start S3 bucket

name

(QSS3BucketName)

aws-quickstart S3 bucket name for the Quick Start assets. This string can

include numbers, lowercase letters, uppercase letters, and

hyphens (-). It cannot start or end with a hyphen (-).

Quick Start S3 key

prefix

(QSS3KeyPrefix)

quickstart-tibco-

jaspersoft/

S3 key prefix for the Quick Start assets. Quick Start key prefix

can include numbers, lowercase letters, uppercase letters,

hyphens (-), and forward slash (/).

OPTION 2: PARAMETERS FOR DEPLOYING CLUSTER TIBCO JASPERREPORTS SERVER

INTO AN EXISTING VPC

View template


Parameter label


VPC ID

(VPCID)

Requires input The ID of your existing VPC for deployment.

Private subnet 1 ID

(PrivateSubnet1ID)

Requires input The ID of private subnet 1 in Availability Zone 1 for the TIBCO

JasperReports Servers (e.g., subnet-a0246dcd).

Private subnet 2 ID

(PrivateSubnet2ID)

Requires input The ID of private subnet 2 in Availability Zone 2 for the TIBCO

JasperReports Servers (e.g., subnet-b1f432cd).

https://aws-quickstart.github.io/option1.html

https://fwd.aws/aNn5n


Page 13 of 21

Parameter label


Public subnet 1 ID

(PublicSubnet1ID)

Requires input The ID of public subnet 1 in Availability Zone 1 for the

Application Load Balancer (e.g., subnet-9bc642ac).

Public subnet 2 ID

(PublicSubnet2ID)


Application Load Balancer (e.g., subnet-e3246d8e).


Parameter label


Key pair name

(KeyPairName)



Bastion security group

ID

(BastionSecurityGroupID)

Requires input The ID of the bastion host security group to enable SSH

connections (e.g., sg-7f16e910).

Servers instance type


m4.xlarge The EC2 instance type for the TIBCO JasperReports Server

instances.

TIBCO JasperReports nodes configuration:

Parameter label


Nodes minimum size

(WorkloadNodesMinSize)

2 The minimum size of the Auto Scaling group

Nodes maximum size

(WorkloadNodesMaxSize)

2 The maximum size of the Auto Scaling group

Nodes desired capacity

(WorkloadNodesDesired

Capacity)

1 The desired capacity for the Auto Scaling group

Operator email address

(OperatorEmail)

Requires input (Optional) The email address that notifications of any scaling

operations will be sent to.

S3 bucket for

license and

customization

(NewBucket)

No A new S3 bucket. Choose Yes to create a new bucket, where you

can upload third-party drivers, OSGI bundles, certificates,



license and

customization

(S3BucketName)

new-bucket-for-

license-and-

customization



Database configuration:


Page 14 of 21

Parameter label


RDS database address

(RDSAddress)

Requires input The address of the Amazon RDS database. It can contain only

alphanumeric characters and underscores.

RDS database port

(RDSPort)

Requires input Port for the Amazon RDS database. The port number should be

higher than 1024.

RDS database user

name

(RDSUser)

Requires input The master user name for the RDS database.

RDS database

password

(RDSPassword)

Requires input The master password for the RDS database.

RDS database name

(DBName)

jasperserver The name of the new database that will be used for repository

creation. Enter a unique database name.

Include samples

(IncludeSamples)

No Sample data for the repository. Choose No if the foodmart or

sugarcrm databases already exist.

OPTION 3: PARAMETERS FOR DEPLOYING SINGLE-INSTANCE TIBCO JASPERREPORTS

SERVER INTO A NEW VPC

View template


Parameter label


Availability Zones

(AvailabilityZones)

Requires input The list of Availability Zones to use for the subnets in the VPC.

Two Availability Zones are used for this deployment, and the

logical order of your selections is preserved.

VPC CIDR

(VPCCIDR)

10.0.0.0/16 The CIDR block for the VPC.




1.




2.


(PublicSubnet1CIDR)




(PublicSubnet2CIDR)



Allowed bastion

external access CIDR

(RemoteAccessCIDR)

Requires input The CIDR IP range that is permitted to access the bastion

instances. We recommend that you set this value to a trusted IP

range.

https://fwd.aws/Nnqew


Page 15 of 21


Parameter label


Key pair name

(KeyPairName)



Bastion AMI operating

system

(BastionAMIOS)

Amazon-Linux-

HVM

The Linux distribution for the AMI to be used for the bastion

instances.

Bastion instance type

(BastionInstanceType)

t2.micro Amazon EC2 instance type for the bastion instances.

TIBCO JasperReports Server node configuration:

Parameter label

(name)

Default Description

Server instance type


m4.xlarge The Amazon EC2 instance type for the TIBCO JasperReports

Server instance.

Storage configuration:

Parameter label

(name)

Default Description


and customization

(NewBucket)





license and

customization

(S3BucketName)

new-bucket-for-

license-and-

customization

The name of the new bucket. Enter a unique name that does not

include uppercase characters.

AWS Quick Start configuration:

Parameter label


Quick Start S3 bucket

name

(QSS3BucketName)

aws-quickstart S3 bucket name for the Quick Start assets. This string can

include numbers, lowercase letters, uppercase letters, and

hyphens (-). It cannot start or end with a hyphen (-).

Quick Start S3 key

prefix

(QSS3KeyPrefix)

quickstart-tibco-

jaspersoft/

S3 key prefix for the Quick Start assets. Quick Start key prefix

can include numbers, lowercase letters, uppercase letters,

hyphens (-), and forward slash (/).


Page 16 of 21

OPTION 4: PARAMETERS FOR DEPLOYING SINGLE-INSTANCE TIBCO JASPERREPORTS

SERVER INTO AN EXISTING VPC

View template


Parameter label


VPC ID

(VPCID)

Requires input The ID of your existing VPC for deployment.

Public subnet 1 ID

(PublicSubnet1ID)


Application Load Balancer (e.g., subnet-9bc642ac).


Parameter label


Key pair name

(KeyPairName)



Bastion security group

ID

(BastionSecurityGroupID)

Requires input The ID of the bastion host security group to enable SSH

connections (e.g., sg-7f16e910).

Server instance type


m4.xlarge Amazon EC2 instance type for the TIBCO JasperReports

instance.

TIBCO JasperReports Server node configuration:

Parameter label



and customization

(NewBucket)





license and

customization

(S3BucketName)

new-bucket-for-

license-and-

customization



8. On the Options page, you can specify tags (key-value pairs) for resources in your stack

and set advanced options. When you’re done, choose Next.

9. On the Review page, review and confirm the template settings. Under Capabilities,

select the two check boxes to acknowledge that the template will create IAM resources

and that it might require the capability to auto-expand macros.

https://fwd.aws/dWBzE

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-add-tags.html


Page 17 of 21

10. Choose Create to deploy the stack.

11. Monitor the status of the stack. When the status is CREATE_COMPLETE, the TIBCO

JasperReports Server cluster is ready.

12. Use the URLs displayed in the Outputs tab for the stack to view the resources that were

created.

Figure 2: TIBCO JasperReports Server outputs after successful deployment

Step 5. Apply your TIBCO JasperReports Server license

When creating your JasperReports Server cluster or instance, AWS creates an Amazon S3

bucket to store your JasperReports Server license. Your evaluation license is good for 30

days. Once it expires, you will need to purchase and apply a production license from TIBCO

to continue using Jaspersoft.

More information on how to apply a license is available on the Jaspersoft Community Site.

Make sure that you have all the prerequisites for applying your license:

A valid license file.

Access to the AWS Management Console.

A BYOL instance or cluster already running in AWS.

https://community.jaspersoft.com/documentation/tibco-jaspersoft-aws-user-guide/v720/applying-license-jaspersoft-aws-byol


Page 18 of 21

An Amazon S3 bucket. You can find the name of the bucket on the Outputs tab of your

CloudFormation stack.

Step 6. Test the deployment

Log in to TIBCO JasperReports Server by using the Getting Started URL that is provided on

the Outputs tab of the stack.

Security

Default login credentials are provided on the Outputs tab of the stack. Change your default

administrator password after you first log in to your TIBCO JasperReports Server.

Troubleshooting

Q. I encountered a CREATE_FAILED error when I launched the Quick Start.

A. If AWS CloudFormation fails to create the stack, we recommend that you relaunch the

template with Rollback on failure set to No. (This setting is under Advanced in the

AWS CloudFormation console, Options page.) With this setting, the stack’s state will be

retained and the instance will be left running, so you can troubleshoot the issue.

Important When you set Rollback on failure to No, you will continue to incur

AWS charges for this stack. Please make sure to delete the stack when you finish

troubleshooting.

For additional information, see Troubleshooting AWS CloudFormation on the AWS

website.

Q. I encountered a size limitation error when I deployed the AWS CloudFormation

templates.

A. We recommend that you launch the Quick Start templates from the links in this guide or

from another S3 bucket. If you deploy the templates from a local copy on your computer or

from a non-S3 location, you might encounter template size limitations when you create the

stack. For more information about AWS CloudFormation limits, see the AWS

documentation.

Q. What can I do if the JasperReports Server instance cannot access the database?

A. Check the inbound rules on the VPC network access control list (ACL) for the database.

Verify that there is a rule that allows your instance to access the database.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html


Page 19 of 21

Q. What if a rollback occurs?

A. First, check the Events tab to see what errors occurred. If the error does not provide

enough information and if Rollback on failure was enabled, rebuild the instance and set

Rollback on failure to No. After the instance fails, check the System Log for additional

errors and the last steps or commands that were executed.

Q. What if deleting the instance fails?

A. Check the errors that occurred. If the error was caused by a dependency, that

dependency might need to be deleted before the instance can be deleted. In some cases,

when you retry deleting the instance, a page appears where you can choose to delete

whatever is causing the instance deletion to fail.

Q. What if I get an error saying that a db.m4.large Multi-AZ instance cannot be created

because at least two subnets must exist in Availability Zones with sufficient capacity for

VPC and storage?

A. Try a different set of Availability Zones. For example, if three Availability Zones are

available and deploying to the first two doesn’t work, try deploying to the first and third

Availability Zones.

Send us feedback

To post feedback, submit feature ideas, or report bugs, use the Issues section of the

GitHub repository for this Quick Start. If you’d like to submit code, please review the Quick

Start Contributor’s Guide.

Additional resources

AWS resources

Getting Started Resource Center

AWS General Reference

AWS Glossary

AWS services

AWS CloudFormation

Amazon EBS

Amazon EC2

https://fwd.aws/XQbkP

https://aws-quickstart.github.io/

https://aws-quickstart.github.io/



https://docs.aws.amazon.com/general/latest/gr/

https://docs.aws.amazon.com/general/latest/gr/glos-chap.html

https://docs.aws.amazon.com/cloudformation/

https://docs.aws.amazon.com/cloudformation/

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html

https://docs.aws.amazon.com/ec2/


Page 20 of 21

IAM

Amazon VPC

Amazon RDS

TIBCO JasperReports Server documentation

TIBCO Jaspersoft AWS User Guide for 7.2.0

Jaspersoft Business Intelligence for Amazon Web Services

Other Quick Start reference deployments

AWS Quick Start home page

Document revisions

Date Change In sections

January 2020 Licensing and subscription steps added Step 1, Step 3

October 2019 Initial publication —

https://docs.aws.amazon.com/iam/

https://docs.aws.amazon.com/vpc/

https://community.jaspersoft.com/documentation/tibco-jaspersoft-aws-user-guide/v720/introduction

https://community.jaspersoft.com/jaspersoft-aws

https://aws.amazon.com/quickstart/


Page 21 of 21

© 2020, Amazon Web Services, Inc. or its affiliates, and TIBCO Software. All rights

reserved.

Notices

This document is provided for informational purposes only. It represents AWS’s current product offerings

and practices as of the date of issue of this document, which are subject to change without notice. Customers

are responsible for making their own independent assessment of the information in this document and any

use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether

express or implied. This document does not create any warranties, representations, contractual

commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities

and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of,

nor does it modify, any agreement between AWS and its customers.

The software included with this paper is licensed under the Apache License, Version 2.0 (the "License"). You

may not use this file except in compliance with the License. A copy of the License is located at

http://aws.amazon.com/apache2.0/ or in the "license" file accompanying this file. This code is distributed on

an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and limitations under the License.

http://aws.amazon.com/apache2.0/

Date post:	03-Mar-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

TIBCO JasperReports Server on the AWS Cloud · 2020-01-29 · Amazon Web Services – TIBCO...

Documents