Jump to content
We've recently updated our Privacy Statement, available here ×

Any difference in the process of import in 3.7


abinabraham

Recommended Posts

  • Replies 4
  • Created
  • Last Reply

Top Posters In This Topic

I exported/imported a 3.0.2 repo to a 3.7 repo (although the official docs say that the 3.5 has to be used as an intermediary...) Since I have reports that for the most part are simple (straight SQL, couple input controls, nothing very sophisticated going on)...I figured I would give this a try before creating a 3.5 repo instance (not trivial since I run on oracle and getting dba assist takes time...)

 

Anyway, the one difference is the multi-tenancy feature of 3.7 jasperserver...multiple organizations can be supported...this allows orgs to be completed seperated (org1 cannot see reports/datasources for org2)

 

At the root repo level there is now /organizations and under here is the default

/organizations/organization_1...When using js-import, it will default to placing the reports in organization_1 unless you specify --org-id newOrgName as parameter

 

QUESTION: Did you get any errors when running import?

 

ANOTHER GOTCHA with 3.7: New repo browser has bottom left hand search controls...titled "Refine" make sure second pull-down has "All Types" selected...

 

POSSIBLE PROBLEM: Do not try and "copy" the reports to a different organization...this appeared to work for me but of course all the references inside the reportUnits were referencing datasource, input controls from the default org1 where I moved them from...so no reports worked due to permissions problems...I just re-imported all using "--org-id portal" where portal was my organization id

Link to comment
Share on other sites

I am surprised that you seeing this result: folders being created but no resources added (ie reports, etc).

As mentioned in another post, double-check that the right instance/configuration is pointing to the right jasperserver repository database (ie the database named "jasperserver" by default).

Also, if your configs look good and the problem persists, you can turn on debugging on the import operation by editing the following file:

  <js-install>/scripts/config/log4j.properties  OR

  <js-install>/buildomatic/build_conf/import_export_config_ce/log4j.properties (if you are using buildomatic).

Also, take a look at the Install Guide for any configuration hints (chapters 7 and 8 - in the CE install guide).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...