Jump to content
Changes to the Jaspersoft community edition download ×

JMoralesGER

Members
  • Posts

    23
  • Joined

  • Last visited

JMoralesGER's Achievements

Explorer

Explorer (4/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges

0

Reputation

  1. Hi beverleym, the Feature Request (artf1526) is still open (priority 3), Jorge
  2. Many thanks, this subject was solved directly with JasperSoft, Jorge
  3. morning, I use tomcat 5.5.23 and the last JasperServer version (1.2.1) was running there. I have prepared new reports, using parameter-lists (that is, X at the place of $P). Only the new version (2.0.0) has this possibility implemented; that is the reason! I need only to upgrade from 1.2.1 to 2.0.0 (The JS software is ready, the DB still not). thanks a lot, Jorge
  4. I suppose you talk about "META-INF/context.xml attached! [file name=context.txt size=2630]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/context.txt[/file]
  5. I try again to send the images ... [file name=Images_Compressed.zip size=37729]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/Images_Compressed.zip[/file]
  6. Hi kidice, yes, I have created the hibernate sequence (see please everything attached); there is no table with this name (THIS_14_); and I have the hibernate.properties set to oracle (hibernate.properties). Many thanks for your help!, Jorge [file name=hibernate.txt size=371]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/hibernate.txt[/file]
  7. Hi kidice, thanks for your help. I could not use your file directly, but I have made some adaptations, to be near to the known sql-commands (used during the installation from JS 1.2.1), giving the attached sql-part as a result. I suppose, there are still some problems, because the upgraded (to JS 2.0.0) installation does not start, giving the attached log-part out. Please, take a look on that txt-file, to find possible errors on upgrading the oracle DB (Solaris'10 Oracle'10). Thanks in advance and have a nice weekend, Jorge [file name=upgradeOracle_JS_1.txt size=81922]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/upgradeOracle_JS_1.txt[/file]
  8. Sorry, now would be a TXT-File attached. [file name=upgradeMySql_JS_1.txt size=1346]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/upgradeMySql_JS_1.txt[/file]
  9. Hi kidice, many thanks, but I have already an installed JS 1.2.1 and need only the upgrade to JS 2.0.0 for Oracle (similar to the one for MySQL, attached) to install the new WAR-File. I'm not sure, if I can extract the parts which are to be changed from your SQL-File. Again, many thanks, Jorge
  10. Hello everybody, as the JasperServer PRO for Solaris has the Oracle-Access resolved, I wanted to install it (Demo from JasperSoft), but I founded only the Windows- and Linux-Software there. This Message is being inserted here, because the Community Link sent me through the JasperForge.org to this Forum. Many thanks, Jorge
  11. Hello everybody, has somebody already converted the mySQL Patch to Oracle? It was not included onto the JasperServer Version 2.0 Software. Thanks a lot, Jorge
  12. Hello everybody, how should be defined a NIS users Databank, at the place of i.e. LDAP, on the JasperServer? Many thanks, Jorge
  13. Hello everybody, how should be defined an XML Datasource with JasperServer? Many thanks, Jorge
  14. Hello Lucian, many thanks, but after installing Tomcat 5.5.23 (from another source!) the problems were solved. I have found LDAP (as alternative) for the user (Account/Password) access to JasperServer. Is there also the possibility of using NIS, so that our Users must be managed only once on our Product? Regards, Jorge
  15. Hi Lucian, many thanks for your prompt answer. I have put the connection to the database in ".../Catalina/localhost/context.xml" (Tomcat had not named it "jasperserver.xml") and in ".../webapps/jasperserver/META-INF out (As comments). I have changed the definition of "<bean id="dataSource" ..." to the one you told me in the ".../WEB-INF/applicationContext.xml"-file. There was a "Parse"-Problem (I didn't see!) with the Tomcat "digester", which I will try to solve first and also a Message "Context does not have docBase set" (I suposse because there is no "docBase"-Parameter on the "Context path" on those files). Now, the starting-up go ahead with the JasperServer, but another "beans" (i.e. related with the report scheduling) can not use the "dataSource" from the applicationContext (maybe, this bean must be also defined on this last file). After solving the Problem with Tomcat, I will tell you about the new results. In the mean time, you could give me more advices about this subject, because I could still not understand the use of the "quartzScheduler". Have a nice time, Jorge
×
×
  • Create New...