A saying used when someone you hate dies.

Opposite of "Rest in
Peace", where you would rather think of this person rotting/decaying
into pieces than resting in peace.
I'm glad that bastard finally keeled over. May he Rest in Pieces.

–Urban Dictionary

REST in pieces
Real life ORDS

IMDB 4.8
DEV TST PRD1 PRD2 PRD3 PRD4 PRD5

Use case 1
VAL1 VAL2 VAL3 VAL4 VAL5
Create PDF’s and e-mails
merging data with user
DEV1 DEV2 DEV3 DEV4 DEV5
defined templates
 nt
Use case 1
e Pri
c
Create PDF’s and e-mails
fi
Of
merging data with user
X
defined templates
E
AP

AOP server AOP server

Use case 2
Reduce DEV > TEST
lifecycles - easier
management of Text
DEV TST PRD1 PRD2 PRD3 PRD4 PRD5 Messages
 AOP server AOP server TST
declare
l_result clob;
begin
apex_lang.update_message
( p_id => :TRANSLATION_ENTRY_ID
, p_message_text => :MESSAGE_TEXT
);
l_result := apex_web_service.make_rest_request
( p_url => 'http://<REST URL>/application_messages/'||:TRANSLATION_ENTRY_ID
, p_http_method => 'PUT'
, p_body => :MESSAGE_TEXT
);
end;
DEV TST PRD1 PRD2 PRD3 PRD4 PRD5

DEV
begin
apex_session.create_session
( p_app_id => 300
, p_page_id => 100
, p_user_name => 'From Test'
);
apex_lang.update_message
Use case 3
( p_id => :id Master Data Management
, p_message_text => utl_raw.cast_to_varchar2( dbms_lob.substr( :body, 4000, 1 ))
);
:status := 200;
end;
 AOP server AOP server

Master Data Management Central Repo RESTful services Central Repo

All in one DB using VPD

All in one instance using PDB (and one as an Application Container)

Sync local data with a Central Repository

DEV TST REST Data Sources PRD1 PRD2 PRD3 PRD4 PRD5

APEX Automation
procedure sync_with_central_repo
is
l_session_created number;
begin

Use case 4
l_session_created := apex_session.create_session(...);

apex_rest_source_sync.synchronize_data
( p_module_static_id => 'Countries' );
-- Subscription management
apex_rest_source_sync.synchronize_data
( p_module_static_id => 'Languages' );
-
....
....
-
apex_session.detach;
--
end sync_with_central_repo;
 AOP server AOP server

Central Repo Central Repo

Subscription
RESTful service

Use case 5
Performance monitoring

REST call
DEV TST sets PRD1 PRD2 PRD3 PRD4 PRD5
Build Option(s)

AOP server AOP server

Define queries
Central Repo
against the Central Repo
Remote Server

DEV TST Enable REST SQL PRD1 PRD2 PRD3 PRD4 PRD5
 Use case 6
Enhance traceability

Read confirmation

<img
LOCAL
style="display:block;margin-left:auto;margin-right:auto;height:16px;"
border="0"
height="16"
begin
alt_text="Images are not displayed properly, please add noreply- email_accounts.htp_print_rest_footer_image(p_userid => :email
,p_message_id => :messageid);
roels_sponsor@mail-dev.psixchange.com to your safe senders list. " end;
src="https:/ ords/psixmail/footer/image?
email=noreply@mail-
dev.psixchange.com&messageid=3D20220324150830587965000.DAF861
6DBF89C19FE053180FA8C09FDF@mail-dev.psixchange.com"
>
 AOP server AOP server

Central Repo Central Repo

DEV TST PRD1 PRD2 PRD3 PRD4 PRD5

Email replies

Use case 7
Email reply classification
 email received

reply to what email

“Will the email (eventually) reach the recipient?”

… in any language .. what does it say

AOP server AOP server

what does it say
Central Repo Central Repo
ML service

REST call
DEV TST POST PRD1 PRD2 PRD3 PRD4 PRD5
classification
email received

reply to what email

Use case 8
Document & data upload
what does it say

take action

AOP server AOP server

Central Repo Central Repo

External system (Oracle Clinical)

DEV TST PRD1 PRD2 PRD3 PRD4 PRD5

Webservices &
ORDS
are the glue that connects all Q&A
parts of our solution.
@RoelH
roel@apexconsulting.nl