ogavavka

I didn`t test this, but most probably you can rebuild your config files by using folowing command in buildomatic folder: js-ant clen-config gen-config this should regenerate all config files and put them in build_conf/default/ subfolder, then just pick related files and update them in deployed server

Server don`t care about provided email (it`s user or distribution list) it`s sending email to MTA (Mail Transfer Agent) usualy by SMTP and distribution is happening on MTA side. Check logs it`s possible that your MTA is refusing to accept emails to this addresses or credentials are invalid

Your Studio is located in same machine as Server or thouse are separate machines ? if they are different - most probably some firewall could block access from JasperServer instance to database.

Did you try this approach ? http://community.jaspersoft.com/wiki/allow-anonymous-access-reports

it`s already there, https://aws.amazon.com/marketplace/pp/B01BUD6LAI

it`s possible that something was wrong with AWS during License check, just try to reboot your instance.

This kind of scenarious (Mixed-VPCs) are not supported by AWS Datasource Automatic Security setup by now. you can use regular JDBC Datasource or you can still use AWS Datsource but disable automatic security setup in "Server SettingAWS Settings" then it should be silent about that.

What your logs are showing ?

in AWS when you launch Jasper from AMI - you are creating new server from image (AMI) and during that process you are specifying your SSH key which will be embeded inside - so you have complete control of your server and only you have it This image is build on Amazon Linux distribution, so just use same aproaches Use SSH with default AWS login for Amazon Linux "ec2-user" and your private key - you will get access to instance. About your issue: Export everything and import in new version - it`s usual case, but to undestand what went wrong - we need your log files from server. if usual way of importing/exporting by using UI don`t want to work - you can try to use console import/export tool which is inside of server, this tool is well documented, and it`s same as for any JasperServer. You can find usual war-binary distribution package in /usr/shared/jrs_dist which was used for server preparation, this distribution don`t have any AWS specific tweaks. about Anual plan: it`s already available on AWS Marketplace (same product, just have switch between Horly and Annual pricing model)

Well if you use AWS version (it`s commercial) - then actualy you don`t need to write them :-) just create DataSource, Create Domain and point to that DataSource, Create AdHoc on that domain - and you are ready to explore your data.

Most probably Bouncy castle library is causing this bcprov......jar try to update it to latest version: from here https://www.bouncycastle.org/latest_releases.html P.S. JRS 6.1 already have them updated.

yes AWS instances don`t have samples for external auth because it`s build from "WAR-Binnary" installer, most probably you need to contact support for Commercial external auth sample files.

beter use "High availability" setup which will do that - setup JRS with external RDS as database for repository. you can find more info on http://community.jaspersoft.com/jaspersoft-aws/launch and select "Launch Jaspersoft for AWS High Availability" tab here some docs about that http://community.jaspersoft.com/documentation/tibco-jaspersoft-aws-user-guide/v610/launching (seek "high availability" string) just launch new setup and then export data from old and import into new, if you will be satisfied - you can terminate old instance.

Seems it`s not complete stacktrace - i don`t see cause (that bean is defined in "applicationContext-externalAuth-LDAP-mt.xml" (atleast in samples)

Look at Diagnostic Feature. specialy look at Diagnostic Report which using Diagnostic DataSource

Confirm that your license have multitenancy feature (MT)

Please confirm that your license have Multitenancy <<<<<< This comment was blocked and unpublished because Project Honeypot indicates it came from a suspicious IP address.

Read doc http://community.jaspersoft.com/documentation/jasperreports-server-user-guide/creating-topics and pay atention to first lines

JRS 5.5 don`t support Hive2.

It`s pretty generic question, please add some details.....

If you are familiar with some programing language you can use REST API for Update/Delete Reports. How to do that - look at docs or samples for your language.<<<<<< This comment was blocked and unpublished because Project Honeypot indicates it came from a suspicious IP address.

You can delete Reports which you want update in destination, then import data without "update" Import will skip existing resources in this case.

Check Tomcat logs (catalina.......log), provide error <<<<<< This comment was blocked and unpublished because Project Honeypot indicates it came from a suspicious IP address.

Hi Please supply additional info: Apllication server JRS Version your regex <<<<<< This comment was blocked and unpublished because Project Honeypot indicates it came from a suspicious IP address.

Hi Pete By your error i can say - your database is inside of VPC. If you use CloudFormation to create JRS instance - then JRS working outside of database VPC. When you are creating AWS Datasource JRS attempt to setup security between JRS instance and your Database in VPC which is not very trivial .... in your case i can suggest 2 solutions: 1. Setup VPC security manualy so your database will be reachable from JRS instance, if you succeed - disable AWS JRS Automatic security setup/recovery in Manage -> Server settings -> AWS Settings ->Enable AWS Security Group Changes, but keep in mind if you stop JRS instance and then start it again - instance will change Public/Internal IPs, so your VPC Security may need be manualy updated after each JRS stop/start sequence - depend on Security setup approach. 2. Terminate old instance if you can and Start new AWS JRS instance manualy using EC2 console inside of same VPC as database, to accomplish this task please consult "Jaspersoft for AWS USER Guide" (http://community-static.jaspersoft.com/sites/default/files/docs/jaspersoft_for_aws_user_guide.pdf), it`s not very current in screenshots because AWS update their UI, but workflow and settings are correct. if you still will have problems - please share your Database info like Network setup, VPC Setup, Availability of Public/Private IPs, etc ... without some info we cannot help you. P.S. If you cannot terminate old instance and create new because you already have some work there already, you can try to create AMI from it, and use it for creation in VPC.