Skip to Main Content

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORDS 3.0 and mod_plsql migration

dmdamiyoAug 20 2015 — edited Sep 5 2015

Hello, Probably this is a naive question, but anyway:

I've configured and deployed ORDS on weblogic server. I've got a legacy architecture that connects to the same database but using OHS and mod_plsql.

In the legacy setup I have DADs configured with URLs and stuff. My question is how can I access these legacy applications that are accessible through mod_plsql via ORDS so I can switch off OHS?

How can I construct a proper URL? Because every ords app follows this pattern of f?p=1 etc. Do I have to modify ords configuration since it is the same database?

I don't really get the relation between these two connectors as I always worked with APEX listener (called now ORDS).

Any hints will be appreciated.

This post has been answered by rwendel on Sep 5 2015
Jump to Answer

Comments

User_H3J7U

The queue triggered event job only when the enqueue occurs. Moreover, if a new enqueue occurs during the job execution, the scheduler will skip that event.
Simplest way is to start a single non-event job with a continuous dequeuing. Or enable multiple event job instances and dequeue all messages on startup. The third option is to register the pl/sql callback, but you still need to read messages on startup. Pl/sql callback is starting up to 20 processes on simultaneous enqueue.

murali rishna

i enable this one as well, still ,it is not working.
DBMS_SCHEDULER.SET_ATTRIBUTE('<<jobname>>','parallel_instances',TRUE);
As per your comment " enable multiple event job instances and dequeue all messages on startup. "
do you have sample,please share it?

User_H3J7U

Parallel_instances is needed to solve this problem_:_
Note:
The Scheduler runs the event-based job for each occurrence of an event that matches event_condition. However, by default, events that occur while the job is already running are ignored; the event gets consumed, but does not trigger another run of the job. Beginning in Oracle Database 11g Release 1 (11.1), you can change this default behavior by setting the job attribute PARALLEL_INSTANCES to TRUE. In this case, an instance of the job is started for every instance of the event, and all job instances are lightweight jobs. See the SET_ATTRIBUTE procedure in Oracle Database PL/SQL Packages and Types Reference for details.
How to dequeue messages from queue, you can find in the documentation Advanced Queuing User's Guide (pl/sql). See also Administrators Guide about event based jobs.

murali rishna

i tried with parallel instance,it is not working.still event are the in que table.

1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 3 2015
Added on Aug 20 2015
4 comments
3,049 views