Using Genappvieweritems.cmd During Installation Causes Appviewer Page To Fail And Required Second Run Of InitialSetup.cmd
(Doc ID 1353234.1)
Last updated on APRIL 03, 2024
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.0.1 and laterOracle Utilities Framework - Version 4.0.0 and later
Information in this document applies to any platform.
Symptoms
I logged on Mobile Workforce Management (MWM) and tried to look at the app viewer by accessing it through the MWM application (Menu->Admin->A->Appviewer). The appviewer came up but told me that it didn't have any data. It told me to run batch jobs to get the data so instead I ran: GenappviewerItems.cmd (as in batch admin guide). The command ran fine. I restarted my system and now the system throws the following error when I try to see the app viewer:
This is kind of strange because I logged into WLS and saw that the appviewer had deployed successfully.
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
I've also tried to run Initialsetup.cmd and CDFDeploy.cmd but It doesn't seem to make any difference.
What can I do to get my appviewer working ?
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |