Monday, November 21, 2005

Happy Turkey Day

Tomorrow, I'm off to Los Angeles for the remainder of the week to visit with my wife's family for Thanksgiving. While LA isn't exactly my favorite city, it should be a good time catching up with her family & friends. We're going to see a taping of the Jimmy Kimmel show on Wednesday, so that should be interesting. Amy Smart is the guest, and Def Leppard is performing outside – that alone is a reason to make the trip!

I'm putting the finishing touches on my MAOP Keynote and technical session. I've also changed the topic of my Technical Session to Integrating Oracle HTML DB with the Oracle eBusiness Suite. I simply didn'y have time to get the Oracle Forms presentation in order, hence the last minute change. At one of my current contracts, I've been working extensively with the eBusiness Suite and HTML DB, so I think that this will make for a good story, with lots of advise and best practices.

If you plan on attending the Keynote on Friday, I will say this – it will be something very different than I’ve done in the past. Hopefully, different will be a good different, not a bad different!

Anyways, to the US readers, have a Happy Thanksgiving! To those overseas, enjoy a full week of work! :)

4 comments:

ian said...

Scott, I'm using HTMLDb release 2 on a 10.2 RDBMS. This is the last paragraph of a TAR I've got open with Oracle at the moment. I would be extremely interested in your thoughts.
'The security clamp on the development server is bespoke, i.e. my customer's
business (MOD) requires this clamp, or something quite like it, to be in place
on all client and server machines in the production environment. We have
solved the problem of HTMLDb functionality when using the development server
effectively as a client, i.e. using IE6 on the server to try to access HTMLDb,
by using IE6 on the server to add the URLs that didn't work to the 'trusted
sites' list.
There is a possibility, therefore, that in the production environment the
client machines will have to be similarly configured, that is, adding the
production URLs to the 'trusted sites' list on every client (this would not be
acceptable to my customer). We are in the process of trying to obtain suitably
clamped clients for our development environment to try to test this theory.
All we can be sure of is that HTMLDb 1.6 did not and does not present a similar
problem.
In terms of the substantive reason for this TAR it could be closed as we now
have functionality, however, this has raised other questions which need to be
resolved urgently.'

Scott said...

Ian,

The major security component which changed from 1.6 to 2.0 is that all URLs require a valid Session ID.

Ensure that if you're calling HTML DB pages in your application that the &SESSION. or :APP_SESSION variable is being used.

Otherwise, you'll be prompted for a username and password.

Thanks,

- Scott -

Mark said...

Scott,
Any chance that you could publish the white paper on here ( or anywhere )? It'd be great to have some "real world" info on integrating 11i with HTMLDB.

Scott said...

Mark,

You can download the slides here.

Thanks,

- Scott-