[nikesh mohanlal]

Hi,

Thanks for your instant reply.Yes,I wanted a workable OTM server.I have made some changes as per the aDmin guide.I have placed the reports(sample .rdf I created) in the folder:glog/reports and then added a new GC3 entry in OTM with DBA.Admin username,Yet I am unable to see it when i click on the Reporting manager screen.Could you please let me know if any other changes to be done or else some othe process is there?

Regards,
Nikesh.

[nick.polites]

Nikesh,

Before trying to run a report first ensure that the View Scheduled Jobs link works. To access that, select Business Process Automation --> Reporting --> View Scheduled Jobs. Let me know what you get when you click this.

Thanks,
Nick

[sknmail@rediffmail.com]

Hi Nick,

We have a development instance, were we recently installed OTM 5.5 CU#4 with RU#1. The problem with this instance is -
- Run the reports from Report Manager (OTM UI) - works perfect
- View Schedule Jobs Page - When you click on the icon present in Job Status column, we receive exception as below -
"The requested URL is an invalid request. Can't process request"


Appreciate you help if you could let me know any clue on what is causing this issue.

Thanks,
Suresh

[nick.polites]

Ok since view scheduled jobs works then I would say you are connecting to the Oracle Reports server correctly. If you run other out of box (not custom) reports do they work? I'm guessing you have a setup issue with this custom report if the out of box ones work. You'll need to check the log files to try to figure where the problem is.
One additional thing I found out is that Oracle Reports has a scalability feature in which it will try other reports instances on the same network if the report server instance is the same i.e. Reports_OTM_55 on two different servers. This has caused a great deal of pain until I figured out what was going on. Keep that in mind as well.

[sknmail@rediffmail.com]

Hi Nick,

Thanks very much for the information you gave.

However even the OTM supplied reports are throwing the same exception. Please let me know if you have any clue.

Regards,
Suresh

[nick.polites]

If all reports are throwing errors, check your glog.properties file on your web and app servers to make sure all of reports configurations are correct. Sorry I can't help you out further without looking at your environment.

[sknmail@rediffmail.com]

Hi Nick,

We have raised a SR with Oracle for this issue today. I would be updating you on this issue once I get a fix.
Thanks very for the help.

Regards,
Suresh

[sknmail@rediffmail.com]

Hi Nick,

We did raise an SR with Oracle, however we could find that there was couple of properties which were defined as below in glog.properties
glog.webserver.reports.enableRWServletSecurity=tru e
glog.webserver.reports.usersWithAccess=true

This above values was screwing up the show job link and even all the report which as PAGESTREAM=YES as additional URL Arguments.

Now to resolve this issue we had to modify these properties as below -
glog.webserver.reports.enableRWServletSecurity (No value is as good as true)
glog.webserver.reports.usersWithAccess (The good values for this property is the GL USER GIDs if you want to restrict to specific OTM Logins, and if left with no values means for all GL USER GIDs)



So this is how these two issue got resolved in our environment.



Regards,
Suresh