Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trouble migrating 7.0 dashboards into 7.16 #62

Open
dfinkbeiner opened this issue Sep 25, 2015 · 4 comments
Open

Trouble migrating 7.0 dashboards into 7.16 #62

dfinkbeiner opened this issue Sep 25, 2015 · 4 comments

Comments

@dfinkbeiner
Copy link

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
Copy link
Contributor

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
Copy link
Author

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
Copy link
Contributor

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:
#62 (comment)
116

@mparizernc
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants