search

ozoneplatform / owf-framework

OZONE Widget Framework
http://ozoneplatform.org
Apache License 2.0
329 stars 143 forks source link

Trouble migrating 7.0 dashboards into 7.16 #62

Open dfinkbeiner opened 9 years ago

dfinkbeiner commented 9 years ago

We're having trouble running: https://host:port/owf/administration/migrateToApps We've upgraded our 7.0.0 OWF to 7.16. The 7.16 "OWF Configuration Guide.pdf" secA.2.2.1 Migrate Legacy Dashboard Data directs us to run: https://host:port/owf/administration/migrateToApps to convert our old Dashboards and Stacks into 7.16 Apps and Pages. When I go to that URL in the stock owf.war running in tomcat, it returns an HTTP 200 with body: No dashboards to process This makes sense. But when I go to the same url in the owf.war we've deployed into JBoss, I get an HTTP 404 with title: JBoss Web/7.4.9.Final-redhat-1 - JBWEB000064: Error report The page body is: JBWEB000065: HTTP Status 404 - /owf/WEB-INF/grails-app/views/administration/migrateToApps.jsp JBWEB000309: type JBWEB000067: Status report JBWEB000068: message /owf/WEB-INF/grails-app/views/administration/migrateToApps.jsp JBWEB000069: description JBWEB000124: The requested resource is not available. JBoss Web/7.4.9.Final-redhat-1

Everything else we try to do in our JBoss OWF seems to work fine, so there doesn't seem to be any major problem. What actual underlying resource fulfills the request: /owf/administration/migrateToApps I'm guessing that we've mis-configured something in our OWFConfig.groovy and it's failing back to migrateToApps.jsp (which doesn't seem to exist in owf.war or its jars). Thanks, Dave

mparizernc commented 9 years ago

Can you please specify which version of JBoss you are using? I tried it against version 7.1.1 and was unable to see the issue. Also if you could specify which back end database you are using that would be helpful as well.

dfinkbeiner commented 9 years ago

Our db is Oracle 11.2.0.4. We're using JBoss EAP v6.3.2 (JBoss AS 7.4.2). Do you have any info on what class is supposed to handle the /owf/administration/migrateToApps url? That way I can investigate why our OWF can't seem to find that resource - causing it to try the migrateToApps.jsp resource (which ultimately returns the 404). Thanks, Dave

rpokorny commented 9 years ago

That endpoint should be handled by the migrateToApps closure in AdminstrationController.groovy (located in grails- app/controllers/ozone/owf/grails/controllers/ in the source code).

On Tuesday, September 29, 2015 10:22:20 AM dfinkbeiner wrote:

Our db is Oracle 11.2.0.4. We're using JBoss EAP v6.3.2 (JBoss AS 7.4.2). Do you have any info on what class is supposed to handle the /owf/administration/migrateToApps url? That way I can investigate why our OWF can't seem to find that resource - causing it to try the migrateToApps.jsp resource (which ultimately returns the 404). Thanks, Dave

Reply to this email directly or view it on GitHub: https://github.com/ozoneplatform/owf-framework/issues/62#issuecomment-144127 116

mparizernc commented 8 years ago

@dfinkbeiner if there are no more questions concerning this ticket will be closed.