Jump to content
JasperReports Library 7.0 is now available ×
  • This documentation is an older version of Jaspersoft for AWS User Guide. View the latest documentation.

    This section describes the processes for creating a JasperReports Server instance from a CloudFormation template, including how to create a JasperReports Server instance inside a Virtual Private Cloud (VPC), or from your EC2 console.

    Before taking the steps described in this section, open the Launching Jaspersoft for AWS page, on the Jaspersoft Community website:

    http://community.jaspersoft.com/jaspersoft-aws/launch

    This web page includes information you'll need for creating and launching your instance.

    Select the option that applies to your set-up:

    Create a Jaspersoft AMI instance in an EC2 Classic environment, see Creating a JasperReports Server Instance from a Jaspersoft CloudFormation Template
    Creating a Jaspersoft application with an auto-scaling cluster of instances, See Creating a JasperReports Server Cluster
    Create a Jaspersoft AMI instance in a VPC, see Creating a JasperReports Server Instance Inside a VPC
    Creating a JasperReports Server application with an auto-scaling cluster of instances inside a VPC, see Creating a JasperReports Server Cluster Inside a VPC

    The above methods use Jaspersoft's CloudFormation templates to generate an instance and its permissions and roles automatically, which gives you a secure and easy-to-maintain instance of the Jaspersoft BI.

    Launch a server manually in the EC2 console, see Creating a JasperReports Server Instance from the EC2 Console

    We don't recommend this method, because it doesn't provide the auto-connect feature for Amazon RDS and Redshift included with the CloudFormation templates. If you choose this method, and you're using a VPC, be sure to define that option during the setup process.

    note-icon-ns.png.6f9d0ababad2cfb4c557ad90684d6f8d.png

    Your Jaspersoft software is charged separately from the AWS EC2 instance charges. Please make sure you follow these instructions to turn off your EC2 instance server running Jaspersoft after use. If not, you will continue to be charged by the hour for EC2 use. Note that when you stop your EC2 instance server no one will have access to the reports or dashboards you've created until you restart the EC2 instance server. When you stop an EC2 instance server, you will still be charged the small EBS charge. If you don't want to be charged for EBS, make sure you terminate your EC2 instance server. Note that in this case none of your work will be retrievable, unless you are you're using an auto-scaling cluster.

    Creating a JasperReports Server Instance from a Jaspersoft CloudFormation Template

    A stack is a collection of AWS resources you create and delete as a single unit. Our CloudFormation template creates the following resources and bundles them into a usable stack:

    IAM role with permissions on RDS and Redshift
    EC2 instance with JasperReports Server installed, configured, and using the IAM role for appropriate credentials.

    note-icon-ns_28x28.png.9a4375aba363379fe60d515b5a68fa24.png

    For non-VPC instances, the CloudFormation Template is not available for the EU-Central (Frankfurt) or Asia Pacific (Seoul) regions due to the way AWS has standardized VPC.

    To create a new JasperReports Server instance:

    1. Open the Launching Jaspersoft for AWS web page.
    2. Click the Launch Jaspersoft for AWS tab.
    3. Click the URL for your region. The Select Template page appears.

    By default, AWS provides a stack template source URL. Do not change this.

    Select Template page

    create-stack_600x318.png.8bf0c6d647f07db5db31b68e8beffc2b.png

    4. Click Next. The Specify Details page appears.

    Specify Details page

    create-stack-specify-parameters_600x334.png.b575bb816379c479015038273457cdf7.png

    5. In the Stack Name field, give your CloudFormation stack a unique name.
    6. Select an InstanceType from the drop down. See Supported Instance Types for more information.

    Performance may vary based on system attributes, such as network bandwidth, memory requirements for a given use case, query requirements, and the like.

    For more information about EC2 instance types, see the AWS documentation:

    http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html

    7. In the KeyName field, enter an existing key pair name.
    8. In the SecuredIp field, enter the IP address and mask for SSH access.
    9. Click Next. The Options page appears.
    10. 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 tags for each instance.

    11. Expand the Advanced section of the Options page and set your notification, timeout, and other options. Click the Learn more link for an explanation of these options.
    12. Click Next. The Review page appears.

    Double-check your template, parameter, and option information.

    13. Click the acknowledgment check box, then click Create.

    You'll see your Stack Name listed in a table. While it's being created the Status column will display CREATE_IN_PROGRESS. After a few minutes the status should change to CREATE_COMPLETE.

    If the status changes to ROLLBACK instead of CREATE_COMPLETE, you may need to accept the Terms of Use. Check the Events tab for more information.

    note-icon-ns_28x28.png.d1e1680d1a03eba89a663b4fbf8c72f5.png

    It may be another few minutes before the JasperReports Server URL becomes available. If you get a message saying “Unable to Connect”, try again in a few minutes.

    14. Select your complete instance and click the Outputs tab. Here you'll find information you'll need when you're ready to log into JasperReports Server:
         The URL for Getting Started with JasperReports Server (Key: GettingStartedURL)
         The generated password (Key: Password).

    Creating a JasperReports Server Cluster

    Jaspersoft provides an auto-scaling cluster using Amazon Relational Database Service (RDS) that ensures that there are enough EC2 instances to handle the workload for your JasperReports Server application. With the cluster, instances are created and removed depending on CPU usage. It also provides a failover mechanism by storing your repository in an external database, so if something happens to an instance it will be replaced and connected to your existing repository. The cluster uses the Amazon Elastic Load Balancer (ELB) to route traffic and currently supports PostgresSQL databases only.

    The CloudFormation template for the cluster creates the following AWS resources:

    An Auto Scaling group that contains the EC2 instances for your JasperReports Server cluster. When creating the stack, you'll define the maximum number of instances in your cluster. The Auto Scaling group defines the thresholds for increasing and decreasing the instances in your cluster. For more information about auto scaling groups, see the AWS documentation: 

    https://docs.aws.amazon.com/autoscaling/latest/userguide/AutoScalingGroup.html

    An Amazon ELB that works as a static endpoint (DNS Name - URL) and monitors the clustered JasperReports Server instances. If something happens to one of your instances—the instance fails or JasperReports Server stops responding—it will be replaced with a new one. For more information on ELB, see the AWS documentation: 

    https://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-internet-facing-load-balancers.html.

    The following options are available:

    Automatic Deployment—This option doesn't support VPC, but the CloudFormation Template automatically creates a JasperReports Server application with an auto scaling group, Postgres RDS database, then automatically deploys your initial data. The automatic deployment setup will create a Postgres RDS instance for which you will be charged by Amazon.
    Manual Deployment - non VPC—Automatically provides a failover mechanism, but you'll need to manually create and initialize your Postgres RDS or other Postgres database.
    Manual Deployment - with VPC—Automatically provides a failover mechanism, but you'll need to manually create and initialize your Postgres RDS or other Postgres database.

    note-icon-ns_28x28.png.4c69c8aff1dff3260bacf0965df51663.png

    If you are using a BYOL license, make sure to delete any existing instances after applying your license. Deleting an instance before applying your license may result in the automatic creation of a new instance using an older license. See Applying a Jaspersoft License for AWS BYOL for more information.

    Automatic Deployment of a JasperReports Server Cluster

    To create a JasperReports Server with a cluster to deploy automatically:

    1. Open the Launching Jaspersoft for AWS web page.
    2. Click the Launch Jaspersoft for AWS tab.
    3. Click the URL for your region. The Select Template page appears.

    By default, AWS provides a stack template source URL. Do not change this.

    note-icon-ns_28x28.png.da81631d6b7eca8aa861fac49b9b5982.png

    For non-VPC instances, the CloudFormation Template is not available for the EU-Central (Frankfurt) or Asia Pacific (Seoul) regions due to the way AWS has standardized VPC.

    Select Template page

    create-stack-ha_600x320.png.cbf4431396db477008da0a397410e453.png

    4. Click Next. The Specify Details page appears.

    Specify Details page

    SpecifyParameters-ha_600x667.png.453f0fb0d567cc3909713bcb6df1ec99.png

    5. In the Stack Name field, give your CloudFormation stack a unique name.
    6. Choose whether to use RDSMultiAz to create the RDS database in Multi-AZ configuration.

    Enabling Multi-AZ Deployment spans the cluster's EC2 instances across multiple availability zones in your region and protects the RDS database from failures. Follow this link for more information: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html

    7. Choose your database size from the RDSDbSize drop down.
    8. Enter the user name for your RDS database in the RDSUser field.
    9. Enter the password for your RDS database in the RDSPassword field

    Save this password. You'll use it again when you first log into your instance.

    10. Choose your InstanceType and Key Name from the drop downs. See Supported Instance Types for more information.
    11. In the SecuredIp field, enter the IP address and mask for SSH access.
    12. Enter the maximum number of instances for your auto-scaling cluster in the MaxInstancesCount field. You can have a maximum of 10 instances in your cluster.
    13. Choose your AvailabilityZones.
    14. Enter a valid email address in the OperatorEMail field. You will receive an email with a subscription link. Click on the link to receive updates, including updates when new instances are created.
    15. Click Next. The Options page appears.
    16. 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 tags for each instance.

    17. Expand the Advanced section of the Options page and set your notification, timeout, and other options. Click the Learn more link for an explanation of these options.
    18. Click Next. The Review page appears.

    Double-check your template, parameter, and option information.

    19. Click the acknowledgment check box, then click Create.

    You'll see your Stack Name listed in a table. While it's being created the Status column will display CREATE_IN_PROGRESS. After a few minutes the status should change to CREATE_COMPLETE.

    If the status changes to ROLLBACK instead of CREATE_COMPLETE, you may need to accept the Terms of Use. Check the Events tab for more information.

    note-icon-ns_28x28.png.c116bb511dca93ee5a6e94ee47dca734.png

    It may be another few minutes before the JasperReports Server URL becomes available. If you get a message saying “Unable to Connect”, try again in a few minutes.

    20. Select your complete instance and click the Outputs tab. Here you'll find information you'll need when you're ready to log into JasperReports Server:
         The URL for Getting Started with JasperReports Server (Key: GettingStartedURL)
         The generated password (Key: Password).

    Database Recovery with Automatic Clusters

    The automatic cluster setup creates an RDS database for your repository and assigns a termination policy that will create a final snapshot in case of RDS instance termination. You can use this snapshot to recover from an accidental deletion of your stack or RDS instance. The snapshot is stored in your AWS account. In your AWS account go to RDS Dashboard > Snapshots.

    Monitoring Your Cluster

    AWS provides multiple tools for monitoring the instances in your cluster:

    Email updates. AWS sends updates to the operator's email address when instances are added or removed from your cluster.
    Load Balancers in the EC2 Dashboard. This dashboard shows metrics for the load balancer and instances, the health check policy for the cluster, the DNS name for the ELB, and more. Go to EC2 Dashboard > Load Balancing > Load Balancers in AWS to view the dashboard.
    Auto Scaling Groups in the EC2 Dashboard . This dashboard lets you monitor the instances in your cluster. You can view information on the thresholds for scaling your cluster, the history of instances added and deleted to the cluster, the email notification settings for the operator, and more. Go to EC2 Dashboard > Auto Scaling > Auto Scaling Groups in AWS to view the dashboard.

    Manual Deployment of a Cluster

    Make sure you have an existing Postgres database before manually deploying a cluster.

    To create an application with a cluster to deploy manually:

    1. Open the Launching Jaspersoft for AWS web page.
    2. Click the Launch Jaspersoft for AWS tab.
    3. Click the URL for your region. The Select Template page appears.

    By default, AWS provides a stack template source URL. Do not change this.

    note-icon-ns_28x28.png.854d186f9e9ad72aa860469795f9a325.png

    For non-VPC instances, the CloudFormation Template is not available for the EU-Central (Frankfurt) or Asia Pacific (Seoul) regions due to the way AWS has standardized VPC.

    Select Template page

    create-stack-ha_600x320.png.a1e56b6d0099f1fe7014569df8d4bfb7.png

    4. Click Next. The Specify Details page appears.

    Specify Details page

    SpecifyParameters-ha-manual_600x681.png.7a04348b674c5e2902c5a4297c38233b.png

    5. In the Stack Name field, give your CloudFormation stack a unique name.
    6. Enter your database information: DBHost, DBName, DBPasword, DBPort, and DBUser.
    7. Choose an InstanceType. See Supported Instance Types for more information.
    8. Choose the KeyName of your EC2 KeyPair.
    9. In the SecuredIp field, enter the IP address and mask for SSH access.
    10. Enter the maximum number of instances to create for your cluster in the MaxInstancesCount field. You can have a maximum of 10 instances in your cluster.
    11. Chose your AvailabilityZones from the drop down.
    12. To enable notifications about your instance state, enter a valid email address in the OperatorEMail field. Leave this field blank to disable notification.
    13. Click Next. The Options page appears.
    14. 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 tags for each instance.

    15. Expand the Advanced section of the Options page and set your notification, timeout, and other options. Click the Learn more link for an explanation of these options.
    16. Click Next. The Review page appears.

    Double-check your template, parameter, and option information.

    17. Click the acknowledgment check box, then click Create.

    You'll see your Stack Name listed in a table. While it's being created the Status column will display CREATE_IN_PROGRESS. After a few minutes the status should change to CREATE_COMPLETE.

    If the status changes to ROLLBACK instead of CREATE_COMPLETE, you may need to accept the Terms of Use. Check the Events tab for more information.

    note-icon-ns_28x28.png.a3a82c4c797736f36788ba16b83c8841.png

    It may be another few minutes before the JasperReports Server URL becomes available. If you get a message saying “Unable to Connect”, try again in a few minutes.

    18. Select your complete instance and click the Outputs tab. Here you'll find information you'll need when you're ready to log into JasperReports Server:
         The URL for Getting Started with JasperReports Server (Key: GettingStartedURL)
         The generated password (Key: Password).
         The name of your ProvisionInstance.
         The name of your Auto Scaling group.

    Manually Deploy Your Cluster

    Manually create a new Repository database in an external Postgres database and initialize it.

    To deploy your cluster manually:

    1. Log into your instance by ssh using the ssh -i EC2_KeyPair ec2-user@instance_name command.

    You can find the instance name on the Outputs tab. See Amazon's documentation for more information on connecting to the instance:

    http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstances.html

    2. Change the directory to:

    /usr/share/jrs_dist/jasperreports-server-bin

    3. Run the initialization script:

    sudo ./deploy-database-to-external-repo.sh normal if you want to create the sugarcrm and foodmart sample databases or sudo ./deploy-database-to-external-repo.sh minimal if you don't want those databases.

    note-icon-ns.png.111faba77bb1ede9209178a80e0adf01.png

    You may want to skip the initialization script If your external database already contains a valid JasperReports Server repository that you want of use. The script will create (or recreate) a JasperReports Server repository database (for example from a previous dump or RDS snapshot) with a minimal set of resources or with samples.

    4. If initialization is successful, halt the instance: sudo halt -p

    If initialization is unsuccessful, troubleshoot the database, then run the initialization script (step 3).

    5. Go to the EC2 Console and increase the instance count from 0 to 1 in the Autoscaling group (name is provided on the Outputs tab of the CloudFormation template).
    6. Use the Getting Started URL from the Outputs tab to access your clustered JasperReports Server appliance.

    Creating a JasperReports Server Instance Inside a VPC

    You have additional options on the Specify Parameters page if you're creating your instance inside a VPC.

    To create a new JasperReports Server instance in a VPC:

    1. Open the Launching Jaspersoft for AWS web page and scroll down to "Start an EC2 instance with Jaspersoft BI, either in or outside of VPC".
    2. Click the Launch Jaspersoft for AWS into VPC tab.
    3. Click the URL for your region. Choose a URL specific to the type of AMI you're using. The Select Template page appears.

    By default, AWS provides a stack template source URL. Do not change this.

    Select Template page

    create-stack_600x318.png.014294cb93ca4fb05697fb7ea03f8148.png

    4. Click Next. The Specify Parameters page appears.

    Specify Parameters page for VPC users (non-cluster)

    SpecifyParametersVPC_600x501.png.4fcb6348334afb40843f1fc1bd5a354a.png

    5. In the Stack Name field, give your CloudFormation stack a unique name.
    6. Choose an InstanceType. See Supported Instance Types for more information.
    7. Choose the KeyName of your EC2 KeyPair.
    8. Choose the VpcId from your account.
    9. Choose the SubnetId from the VPC.
    10. Choose whether to create a publicly accessible IP address for the instance using EnablePublicIp. Default is True. Select False to refuse.
    11. In the SecuredIp field, enter the IP address and mask for SSH access.
    12. Click Next. The Options page appears.
    13. Add any tags you want use 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.

    14. Expand the Advanced section and set your notification, timeout, and other options.
    15. Click Next.
    16. On the Review page double check your template, parameter, and option information.
    17. Click Create. You'll see a message telling you your stack has been created. The Services web page, shows your stack's initial status as CREATE_IN_PROGRESS. It generally takes two to four minutes for the status to change to CREATE_COMPLETE.
    18. Select your complete instance and click the Outputs tab. Here you'll find information you'll need when you're ready to log into JasperReports Server:
         The URL for Getting Started with JasperReports Server (Key: GettingStartedURL)
         The generated password (Key: Password).

    Creating a JasperReports Server Cluster Inside a VPC

    Make sure your Postgres database and VPC are in the same cloud before creating the cluster.

    To create a new JasperReports Server cluster in a VPC:

    1. Open the Launching Jaspersoft for AWS web page and scroll down to "Start an EC2 instance with Jaspersoft BI, either in or outside of VPC".
    2. Click the Launch Jaspersoft for AWS into VPC tab.
    3. Click the URL for your region. Choose a URL specific to the type of AMI you're using. The Select Template page appears.

    By default, AWS provides a stack template source URL. Do not change this.

    Select Template page

    create-stack_600x318.png.5eb79adcf197a9c7e21a212f80f3c7b0.png

    4. Click Next. The Specify Details page appears.

    Specify Details page

    SpecifyParametersVPCHA_600x806.png.b5877a7b9a08cc4360b0c6e2776f8445.png

    5. In the Stack name field, give your CloudFormation stack a unique name.
    6. Enter the host name of your database connection in DBHost, the database name in DBName, the database port number in DBPort, and the database password in DBPassword.
    7. Enter the database user name in the DBUser field.
    8. Choose an InstanceType. See Supported Instance Types for more information.
    9. Choose the KeyName of your EC2 KeyPair.
    10. Choose your SubnetId and VpcId from the drop downs.
    11. EnablePublicIp defaults to true. Unless you change this setting, your initialization instance will be assigned a public IP address and ELB (if enabled) will be configured as "internet-facing". See Amazon's documentation about internet-facing load balancers here:

    http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-internet-facing-load-balancers.html

    12. In the SecuredIp field, enter the IP address and mask for SSH access.
    13. Enter the maximum number of instances to create for your cluster in the MaxInstancesCount field. You can have a maximum of 10 instances in your cluster.
    14. Chose your AvailabilityZones from the drop down.
    15. To enable notifications about your instance state, enter a valid email address in the OperatorEMail field. Leave this field blank to disable notification.
    16. Click Next. The Options page appears.
    17. 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 tags for each instance.

    18. Expand the Advanced section of the Options page and set your notification, timeout, and other options. Click the Learn more link for an explanation of these options.
    19. Click Next. The Review page appears.

    Double-check your template, parameter, and option information.

    20. Click the acknowledgment check box, then click Create.

    You'll see your Stack Name listed in a table. While it's being created the Status column will display CREATE_IN_PROGRESS. After a few minutes the status should change to CREATE_COMPLETE.

    If the status changes to ROLLBACK instead of CREATE_COMPLETE, you may need to accept the Terms of Use. Check the Events tab for more information.

    21. Select your complete instance and click the Outputs tab. Here you'll find information you'll need when you're ready to log into JasperReports Server:
         The URL for Getting Started with JasperReports Server (Key: GettingStartedURL)
         The generated password (Key: Password).
         The name of your ProvisionInstance.
         The name of your Auto Scaling group.

    Manually Deploy Your Cluster in VPC

    Manually create new Repository database in an external Postgres database and initialize it.

    To deploy your cluster manually:

    1. Log into your instance by ssh using the ssh -i EC2_KeyPair ec2-user@instance_name command.

    You can find the instance name on the Outputs tab. See Amazon's documentation for more information on connecting to the instance:

    http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstances.html

    2. Change the directory to:

    /usr/share/jrs_dist/jasperreports-server-bin

    3. Run the initialization script:

    sudo ./deploy-database-to-external-repo.sh normal if you want to create the sugarcrm and foodmart sample databases or sudo ./deploy-database-to-external-repo.sh minimal if you don't want those databases.

    note-icon-ns.png.1469b7f3e71752672f1290529d46c16a.png

    You may want to skip the initialization script If your external database already contains a valid JasperReports Server repository that you want of use. The script will create (or recreate) a JasperReports Server repository database (for example from a previous dump or RDS snapshot) with a minimal set of resources or with samples.

    4. If initialization is successful, halt the instance: sudo halt -p

    If initialization is unsuccessful, troubleshoot the database, then run the initialization script (step 3).

    5. Go to the EC2 Console and increase the instance count from 0 to 1 in the Auto Scaling group (name is provided on the Outputs tab of the CloudFormation template).
    6. Use the Getting Started URL from the Outputs tab to access your JasperReports Server appliance.

    Creating a JasperReports Server Instance from the EC2 Console

    If you have a complex network topology or special volume requirements, 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'll see the following error message:

    Missing Role Error Message

    no-role-error_524x104.png.b52aef8e9c4f3c170654bb5e203adcdf.png

    Create a Role for Your Instance

    If you launch your instance with a role, JasperReports Server will use that Role to generate temporary AWS security tokens for automatic discovery and management of security between your JasperReports Server instance and RDSRedshift instances.

    If no role is defined in your JasperReports Server Instance, you have 2 options:

    Provide Access and Secret keys in AWS Datasource for Discovery and Automatic Security management.
    Manage security manually. (In this case remember to disable Automatic security management in JasperReports Server Server Settings.)

    To create a CloudFormation role:

    1. Sign into Amazon Marketplace with your AWS account.
    2. Navigate to http://www.jaspersoft.com/jrs-create-role. The Select Template page appears.

    By default, AWS provides a stack template source URL. Do not change this.

    Select Template page

    create-stack_600x318.png.c6aa3956f5ca42c9e81f6c9396c10a30.png

    3. Click Next. The Specify Details page appears.
    4. In the Stack name field, give your CloudFormation stack a unique name.
    note-icon-ns.png.b206ca241b3eac3cbb475e57c85a2c97.png

    If you're using a template with VPC support, the Specify Details page includes options specific to that set up. See Creating a JasperReports Server Instance Inside a VPC

    5. Click Next. The Options page appears.
    6. 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 and set your notification, timeout, and other options. Click the Learn more link for an explanation of these 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 shows as CREATE_IN_PROGRESS then changes to CREATE_COMPLETE when it's ready to be used.
    11. Select your stack and click the Outputs tab.

    Outputs Tab Showing RoleName and Description

    outputs-tab-ec2_600x107.png.73dad5893ef5eeecad7f71ab8a83b2a3.png

    Note the RoleName for the stack you created. You'll 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 > EC2. The Resources page opens.
    4. On the left, click Images > AMIs.
    5. Expand the menu to the left of the Search text field and select Public Images.
    6. Enter Jaspersoft in the Search text field and press Enter.
    7. Select the AMI you want, and click the Launch button at the top of the page. The Choose an Instance Type page opens.

    note-icon-ns_28x28.png.2b9371ad3972f4bcb151e0edf475ad10.png

    Make sure you select the correct AMI for you license type (hourly, annual, or BYOL).

    8. Choose an Instance Type from the list. See Supported Instance Types for more information.

    Instance Type list

    instance-type_600x309.png.df20a971f1f99905e267d75c04b4ec2f.png

    9. Click Next: Configure Instance Details at the bottom of the page, and configure the following details. Hover over the information icon icon-info.png.f8fc791e2c05d973f67fb78088ee856c.png
         Number of instances
         Purchasing option
         Network
         Availability Zone (if using EC2) or Subnet (if using VPC)
         Auto-assign Public IP
         IAM role
         Shutdown behavior
         Enable termination protection
         Monitoring
         Tenancy
    10. Expand the Advanced Details section and configure the following details:
         Kernel ID
         RAM disk ID
         User data
    11. Click Next: Add Storage 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.
    12. Click Next: Tag Instance and add optional tags. To add more tags click the Create Tag button.

    A tag is a key/value pair that will flow to resources inside your stack. You can add up to 10 unique tags to each instance.

    13. Click Next: Configure Security Group and configure your firewall rules. Choose an existing security group or create a new security group.

    note-icon-ns_28x28.png.a6098620bf0286a4ae040d5019acab28.png

    We set up one AWS DB Security Group (using IP address) per JasperReports Server instance in each RDS region. The security group allows connections from the JasperReports Server instance to the specified AWS database instance.

    14. Click Review and Launch. Review your information and edit if necessary.
    15. Click Launch.
    16. When prompted, select an existing key pair, or create a new key pair, and click Launch Instances.

    You'll see a message telling you that your instance is now launching. Your instances may take a few minutes to launch, depending on the software you are running.

    note-icon-ns_28x28.png.d6ee0d5ff8361d2735b32d16bf058eb1.png

    Hours of use on your new instances will start immediately and continue to accrue until you stop or terminate your instances.

    17. 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'll find this URL in the Cloud Formation Outputs tab.

    The initial user is superuser and password is your AWS instance ID, located below the Getting Started URL in the Outputs tab or in the EC2 console. You can change the password after your initial login.

     

    To log into 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

    welcome_600x529.png.f4525adda2c6d872ca20bdb14ffdc6ba.png

    2. Choose what you want from the following:
         Your Customer Portal account to download a single-user registration of Jaspersoft Studio Professional, the commercial version of the open source, Eclipse-based report designer for JasperReports.
         Free online support through the Jaspersoft Community forums (requires separate registration).
         A single-user registration for the Online Learning Portal, Jaspersoft's self-guided training site.
         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

    getting-started_600x445.png.7f685a992fa9a30f9c177dc5cc1dc21b.png

    You can watch an introductory video, explore resources on our Community site, or go ahead and log in.

    Login Screen

    login-screen_600x456.png.e993d9d368d83f2648eceb7153457a57.png

    If you're using BYOL, you'll start with a 72-hour license. This page will display a reminder when your license is set to expire.

    Before you click the Login button on this page:

    1. Enter superuser as your User ID.
    2. Your password depends on whether you set up an auto-scaling cluster. With an auto-scaling cluster, your password is the DBPassword you provided in the CloudFormation template. If you did not set up an auto-scaling cluster, your AWS instance ID is your initial password.

    You'll find your AWS instance ID on the CloudFormation Outputs tab of your instance or in the EC2 console.

    Finding the default password in the CloudFormation stack

    stack.png.29f0d22a4d133751bc37b6b07cb45ea7.png

     

    Finding the default password in the EC2 console.

    EC2-console.png.1fe916cb184c240050c504c052870b08.png

    3. Click Change password and enter a new password.
    4. Log in again. The Home screen appears.

    Home Screen

    home-screen_600x302.png.091b15b7518ba330c62eef79799aa156.png

    warning-icon-ns_28x28.png.220198e11714206c7a3954b5c75ee9f0.png

    If you use PostgreSQL as your database, not all PostgreSQL-supported functions will work with Redshift. See the Redshift documentation for details about supported functions.


    User Feedback

    Recommended Comments

    There are no comments to display.



    Guest
    This is now closed for further comments

×
×
  • Create New...