Skip to Main Content

Endeca Experience Management

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!

developer studio does not update pipeline

user9327625Jun 26 2014 — edited Jun 27 2014

Hi

I created my first Endeca app, called testapp2.

The app seems correctly provisioned, then I created  a project in developer studio with the same name of the app.

I issue "set instance configuration" and it seems sto work , but in /app/oracle/product/endeca/apps/testapp2/config/pipeline  the file ar not updated.

The strange things is that if I make a change in the project, the I revert back by issuing "get instance configuration" the previous configuration is correctly loaded in the project. This gives me the idea that configuration are strored somewhere but not where I am looking to.

Any Idea?

Regards

Giuseppe

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 Jul 25 2014
Added on Jun 26 2014
5 comments
2,049 views