Skip to main content

OOW2006 - Day 2 (Tuesday) : Developer Day

On this Tuesday I spent the whole day at the Hilton (only 1,5 block from our hotel) attending sessions from the Developer track. The day started of with the Developer keynote of the day : Tom Kyte with Things you think you know. The message was that things (read "Oracle software") changes over time and with every Oracle update your knowledge needs an update too. The quote of the day :
      "It ain't so much the things we don't know that get us into trouble.
      It's the things you know
      that just ain't so or
      just ain’t so anymore or
      just ain’t always so."
This great presentation (especially if it's presented by the master himself) is also downloadable from asktom. You can get an impression by watching the first 3 minutes on video from Eddy Awad's site.

The second session of the day was Oracle BPEL Process Manager Performance and High Availability by Francis Ip and Randy Stafford. This was the only session at OOW where I misjudged my knowledge (obviously I didn't read the abstract quite well): I got lost after 15 minutes and took the time to finish my notes from the previous day.

After that I went to Business Rules : Core to Agile Applications by Manoj Das. He explained the goals and working of Business Rules a new part of the SOA Suite - rules can be integrated in a BPEL process. The statement was that, because (some) business rules are not static, but dynamic, you need an easy way to change the rules (by the end user). Business Rules is Oracle's solution to that. You should use BR only for rules that are volatile, like discount percentages, client categorization (e.g. gold, silver or bronze customers) etc. He showed some screen prints of the tool, alas no live demo. The IT savings of using a business rule engine is estimated by Gartner on 5 up to 40%, so it looks quite promising - when the product is mature.

The next thing was a Hands-on-Lab Oracle ESB Synchronization. In this session we were challenged to create an end-to-end solution using ESB. A nice break: doing something yourself instead of listening....

The last session of the day was CERN: Building Real-World Solutions with Oracle Application Express by Giovanni Chierico. At CERN (the inventors of the internet!), APEX is used for developing small database centric applications for users all over the world. They managed to put as many as 10 applications in production in 1 year. He showed some screen shots that looked really nice and ended with giving some tips to the audience.

After that I headed over to the Blogger meetup, where I met around 10 of my fellow bloggers. Very good to meet the people you read! A couple of us broke up halfway the meeting to take a bus (one of the 250!) to the Cow Palace to watch the Elton John show. Arriving there I was astonished by the quantity and quality of the food and drinks (even when we arrived quite late). The show of Elton and Devo was great - sadly I had to miss Joan Jett. I went back rather early and had just to wait 10 minutes for a bus (in contrast to some colleagues who had to wait over an hour).

Comments

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...

APEX ReadOnly Pages - The easy way

If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...