Apex day 1.0 speedy case study_kamil schvarcz
0 likes202 views
Case study
![RESTful
CUSTOMIZOVAN
GET:
URI Template m哲転e obsahovat promnnou nap. Sync/step2/store/od/{ID}
V source potom existuje bindovan叩 promnn叩: ID
Typ zdroje:
SQL result set z SQL Query (obsahuje next/previous URL), v箪stup v JSON alebo CSV
SQL jeden 叩dek ak SQL Query vr叩t鱈 jen jeden z叩znam, v箪stup v JSON
FEED result set z SQL Query (obsahuje next/previous URL, obsahuje odkaz na detail, prvn鱈
sloupec mus鱈 b箪t ID), v箪stup v JSON
IN parametry pro GET v APEXu nefunguj鱈 (v REST povolen辿 jsou)
SOURCE:
SELECT 'OK' status, 'Survey '||:ID||' successfully updated' msg from dual
RESPONSE:
SQL - {"next":{"$ref":"http://kozel.quickcode.cz/apex/cnb2/hr/iks/10?page=1"},"items":[{"id":"10"}]}
SQL jeden 叩dek - {"id":"10"}
FEED - {"next":{"$ref":"http://kozel.quickcode.cz/apex/cnb2/hr/iks/10?page=1
"},"items":[{"uri":{"$ref":"http://kozel.quickcode.cz/apex/cnb2/hr/iks/10"},"id":"10"}]}](https://image.slidesharecdn.com/apexday1-150924192446-lva1-app6891/85/Apex-day-1-0-speedy-case-study_kamil-schvarcz-15-320.jpg)
Apex day 1.0 speedy case study_kamil schvarcz
- 2. V PRAZE, 17-9-2015APEX DAY 1.0 CASE STUDY - SPEEDY
- 3. IT PROJEKT - KOMUNIKACE APEXU S MOBILNM ZAZENM POMOC WEBOVCH SLU貼EB
- 4. VALUSTRAT Firma se s鱈dlem v Dubaji, kter叩 podnik叩 v oblastech: Strategick辿 poradenstv鱈 Znaleck辿 posudky a odhady - Nemovitosti - Auta - Tov叩rny a stroje - Znaky a nehmotn箪 majetek - Prodej aktiv
- 5. VALUSTRAT "For our company to have a competitive advantage, in a highly competitive market, we needed to a build a product that would make our processes faster and more e鍖cient. We also needed many complex integrations which included mobile compatibility and google map integrations. Apex was quick to understand our requirements and was able to address our requirements. The team was very professional and understanding of our needs. Their product has helped us achieve our desired results in quicker times." Saad Mehmood,Chief Operating O鍖cer www.valustrat.com
- 7. SPEEDY Desktopov叩 verze Kop鱈ruje procesy na vytv叩en鱈 odhad哲 V箪stupem je PDF resp. MS Word dokument s popisem, mapou a obr叩zky - Technologie - Oracle Linux - Oracle DB - Apache - Apache Tomcat - APEX Listener - APEX - Google Maps - JasperReports - PhantomJS Mobiln鱈 verze (iOS) Phonegap Google Maps jQuery Mobile NSTROJ PRO ODHAD NEMOVITOST Klientsk箪 port叩l Google Maps
- 9. SYNCHRONIZACE Data jen pro pihl叩邸en辿ho u転ivatele Penos dat o nemovitosti Penos polohy nemovitosti Penos obr叩zk哲 Mo転nost pracovat o鍖-line Synchronizace pes 3G, 4G a public wi-鍖 Vych叩z鱈me z pedpokladu, 転e na jedn辿 nemovitosti pracuje v転dy jen jeden odhadce
- 11. LOGICK MODEL Identi鍖kace u転ivatele mobiln鱈 verze Zobrazen鱈 pehledu aktu叩ln鱈ch po転adavk哲 pihl叩邸en辿ho u転ivatele Ulo転en鱈 zmn o nemovitosti - poloha - vygenerov叩n鱈 nov辿ho obr叩zku z google maps - data obr叩zky - obr叩zek na disk - metadata o obr叩zku - gps souadnice - orientace v prostoru - datum a as vytvoen鱈 obr叩zku
- 12. REST V APEXU
- 13. RESTful Representational state transfer (REST) je cesta jak jednodu邸e vytvoit, 鱈st, editovat nebo smazat informace ze serveru pomoc鱈 jednoduch箪ch HTTP vol叩n鱈. REST (Representational State Transfer) je architektura rozhran鱈, navr転en叩 pro distribuovan辿 prosted鱈. Rozhran鱈 REST je pou転iteln辿 pro jednotn箪 a snadn箪 p鱈stup ke zdroj哲m (resources). Zdrojem mohou b箪t data, stejn jako stavy aplikace (pokud je lze popsat konkr辿tn鱈mi daty). REST je tedy na rozd鱈l od zn叩mj邸鱈ch XML-RPC i SOAP, orientov叩n datov, nikoli procedur叩ln. V邸echny zdroje maj鱈 vlastn鱈 identi鍖k叩tor URI a REST de鍖nuje tyi z叩kladn鱈 metody pro p鱈stup k nim. GET, PUT, POST, DELETE
- 14. RESTful V APEXu: Automatick辿 REST API z report哲 Customizovateln辿 rozhran鱈 Vyu転鱈v叩 Oracle REST Data Services (APEX Listener) Mus鱈 b箪t povolen箪 v Internal Workspace pre celou instanci
- 15. RESTful CUSTOMIZOVAN GET: URI Template m哲転e obsahovat promnnou nap. Sync/step2/store/od/{ID} V source potom existuje bindovan叩 promnn叩: ID Typ zdroje: SQL result set z SQL Query (obsahuje next/previous URL), v箪stup v JSON alebo CSV SQL jeden 叩dek ak SQL Query vr叩t鱈 jen jeden z叩znam, v箪stup v JSON FEED result set z SQL Query (obsahuje next/previous URL, obsahuje odkaz na detail, prvn鱈 sloupec mus鱈 b箪t ID), v箪stup v JSON IN parametry pro GET v APEXu nefunguj鱈 (v REST povolen辿 jsou) SOURCE: SELECT 'OK' status, 'Survey '||:ID||' successfully updated' msg from dual RESPONSE: SQL - {"next":{"$ref":"http://kozel.quickcode.cz/apex/cnb2/hr/iks/10?page=1"},"items":[{"id":"10"}]} SQL jeden 叩dek - {"id":"10"} FEED - {"next":{"$ref":"http://kozel.quickcode.cz/apex/cnb2/hr/iks/10?page=1 "},"items":[{"uri":{"$ref":"http://kozel.quickcode.cz/apex/cnb2/hr/iks/10"},"id":"10"}]}
- 16. RESTful CUSTOMIZOVAN POST, PUT, DELETE: Oek叩v叩 IN, INOUT a OUT parametry Mus鱈 volat PL/SQL blok Na konci mus鱈 nastat HTTP pesmrov叩n鱈 Parametry pro pesmrov叩n鱈: X-APEX-FORWARD location OUT HTTP Header String X-APEX-STATUS-CODE status OUT HTTP Header Integer SOURCE: Begin my_package.action(); :status := 201; :location := '/apex/jaj/speedy/sync/step2/store/ok/'||:id_survey; exception when others then :status := 201; -- alebo iny HTTP status code :location := '/apex/jaj/speedy/sync/step2/store/err/'||:id_survey; end;
- 17. GET A POST METODY SPEEDY
- 18. GET A POST METODY Get User List Get Surveys List Post Survey Update - Get OK Message - Get Error Message Get Images List Post New Image - Get OK Message - Get Error Message Get Image Detail Delete Image
- 20. VIDEO
- 21. 禽楢悪雨干掘珂掘