Blog Aggregator

• Design Time Service Discovery
  A registry can be used to catalogue existing services and associated artifacts.  This encourages re-use by making it easier to discover existing services.  The ability to promote items between registries also makes it possible to put in place a service approval process that vets new services before making them available to developers.  This again promotes re-use and generalisation of existing services.
  
• Run Time Service Discovery
  A registry can also be used at runtime to provide the physical endpoint for a service.  This makes it easy to change the physical provider of a particular service.  This also simplifies migration of services between development test and production environments as outlined in the next use case.
  
• Service Migration Mechanism
  The use of multiple registries provided a managed path for services to be promoted between environments, either from a development perspective or from a runtime perspective.

1. In the BPEL Console, go to the "Manage BPEL Domain" and set the following properties
• uddiLocation - the inquiry address of the registry
• uddiUsername - if it is a secured registry set it to a username for performing lookups, if not set it to urn:unknown
• uddiPassword - if it is a secured registry set it to a password for performing lookups, if not set it to urn:unknown
2. In a BPEL process for each service endpoint (partner link) that you want to go through a UDDI lookup
• Add a property "registryServiceKey" to the partner link with the "Entity Key" value assigned in the UDDI repository

• JavaWS includes a simple Java web service (GreetingWS) that can be registered in a service registry.  When registering it in the registry you will need to note the service key and copy it into the partner link property in Dynamic BPEL.
  
• DynamicBPEL is a BPEL process that looks up the web service (GreetingWS) and invokes it in three different ways
1. Static, it uses the endpoint defined in a WSDL file
2. Dynamic, it sets the endpoint explicitly (passed in as a parameter to the process), showing how you can be very dynamic in the endpoint you invoke.
3. UDDI, it uses the UDDI repository to lookup the endpoint, showing how unintrusive it is on the rest of the process.
• TestDynamic is a BPEL process that you invoke to test the DynamicBPEL process.  It iterates over all three methods and calculates how long each method takes to complete the given number of iterations.  The first invocation is not counted to allow the system to "warm up" for each call.
  

Please visit my personal blog at blog.jameskoopmann.com.

I’ve been so very busy lately, but not with bloggable activity. This week has been slow on Mix news; ENTP is putting the finishing touches on a big feature, and we did deploy a few bug fixes.

I did finally catch up on feed reading from a month ago, and a post from friend of the ‘Lab Jeff Nolan about TwitterFone caught my eye.

TwitterFone allows you to tweet by phone.

After you sign up for the invite-only service and verify your phone by SMS, all you need to do is call the TwitterFone number and speak your tweet.

Presto, minutes later, out comes your tweet into your tweetstream. The voice to text is pretty good, and they add a TinyURL to your tweet pointing to the recorded version, just in case you don’t enunciate properly. Case in point is my tweet about Beer and Blog. Yes, it’s a real thing we do here in PDX.

Wow Factor
A few things jump to mind here. First off, Jeff is right about the Wow Factor. This puppy just works, exactly as advertised, no additional setup required. Reminds me of TripIt, another Wow Factor Hall of Fame member. I hear Sandy is also that way, but I’ve yet to get that configured. Also noteworthy is Jott, which I’m told has the same capabilities as TwitterFone, plus more, for happy people in the US and Canada. Again, Jott is on my short list to try.

I am enamored with services that just work, especially if they work with other services I use all the time like email and phone. Simplicity is refreshing.

Here come the groans. Yet another way to tweet. W00t! TwitterFone opens the door to all manner of tweets; the first that came to mind was tweeting my annoyance with other drivers, as I was unceremoniously cut off in traffic. That stuff matters here in Portland, where we still have driving manners.

Beyond tweeting my road rage, I can imagine practical uses for TwitterFone. For example, it allows an even faster way to report events, e.g. the recent earthquake in China, as reported by our very own Dean Tan. Word has it Twitter reported that 3 minutes before the USGS did.

I have trouble tweeting with my iPhone because typing kills the immediacy of the moment. TwitterFone removes that barrier. So you can report news or other noteworthy events faster. Maybe you see a hit and run and tweet the license number and accident location using TwitterFone. Maybe you hear on the radio they’re giving away free gas and you want to share the love with your tweeple.

TwitterFone closes that news reporting gap very nicely.

Pat Phelan (@patphelan), who generously provided me with a few invites, tells me that although TwitterFone does not currently support direct messaging and @ replies, these are planned. I can’t wait. I frequently fill up my integrated messaging inbox with voicemail reminders, which are easy to leave when I think of stuff while I’m driving. I could use Twitter for short notes, which is a much lighter weight solution.

So I’m very pleased with TwitterFone so far and plan to use it a lot, especially with a conference coming up next week. Live blogging will be much easier by voice.

All Twitter, All the Time
I blab about Twitter a lot. It’s not for everyone, but more and more people are finding real value beyond sharing horribly mundane details about their lives.

Twitter’s ecosystem and API are why it matters (via WWD). Twitter’s API allows all manner of client apps and bots to use it and even monetize it (e.g. Twhirl), when Twitter itself has no public business model. The API has led to viral spread and (possibly) unintended uses like bots (e.g. Firebot, Timer).  Bots create a command-line widget, perfect for targeted tasks and accessible from all manner of clients, thanks again to the Twitter API.

Venkataramanan S sent me an extreme example of what Twitter can do, Twitter + Bash, which I had to have explained to me (I know, shell fail).

Twitter is an essential tool for a distributed workforce too. I went to an informal tweetup yesterday, and everyone there had a flexible work environment, i.e. worked from home or from wherever. For those of us who don’t have a water cooler, Twitter serves this purpose.

Mobile New Web
TwitterFone joins Brightkite and Evernote as recent mobile New Web sites I’ve joined. Then I joined Jott, just for fun. I’m intrigued by the use of SMS commands to manipulate these web apps. I haven’t yet decided if they’ll stick for me, since I’m a bit of luddite when it comes to mobile web.

The main reason I bought an iPhone was to take Interwebs with me though, so I’m going to condition myself to use these services.

On its surface, mobile web seems like a huge are for opportunity, so I expect new apps will sprout up often.

Big thanks to Pat again for the invites, which I quickly dispatched.

It's actually quite simple to achieve this - but I got asked this a couple of times last week so here goes...

All you need to do is drag the first detail over and drop it as a master->detail.

Then drag the second detail over and drop it as a table or a form - and now you have the three tables on the page and you are almost done.
But if you'll run your page now you'll find that your second detail is not refreshing when you are switching between the master records the way that your first detail does. ADF did this synchronization part automatically for the first master-detail you dropped. All you are missing is a partial page rendering setting on your second detail. See the difference between the two detail tables here:


So let's set it up - all you need to do is go to the form or table that contains your second detail and set its partialTrigger property to point to the master component. (You can look at the setting for your first detail component and copy them).

Recently, while answering a question, I came across what appeared to be a change to the rules for licensing Oracle Standard Edition — a change that appears to be subtle on the surface, but one that could have significant and surprising repercussions.

It was with considerable fanfare that Oracle announced, several years ago, the last major change to the licensing rules for Standard Edition — that multi-core processors would be counted as a single CPU for the purposes of licensing Standard Edition products. (For Enterprise Edition, Oracle continued to count each core as a separate “processor”, but then provided price discounts, presumably in recognition that a 2- 4- or 8-core CPU rarely provides equivalent performance to an equivalent number of single-core processors running at the same clock rate).

The revised licensing rule went like this (I have highlighted the relevant text in bold):

Processor: shall be defined as all processors where the Oracle programs are installed and/or running. Programs licensed on a processor basis may be accessed by your internal users (including agents and contractors) and by your third party users. For the purpose of counting the number of processors which require licensing for a Sun UltraSPARC T1 processor with 4, 6 or 8 cores at 1.0 gigahertz or 8 cores at 1.2 gigahertz for only those servers specified on the Sun Server Table which can be accessed at http://oracle.com/contracts , “n” cores shall be determined by multiplying the total number of cores by a factor of .25. For the purposes of counting the number of processors which require licensing for AMD and Intel multicore chips, “n” cores shall be determined by multiplying the total number of cores by a factor of .50. For the purposes of counting the number of processors which require licensing for all hardware platforms not otherwise specified in this section, a multicore chip with “n” cores shall be determined by multiplying “n” cores by a factor of .75. All cores on all multicore chips for each licensed program for each factor listed below are to be aggregated before multiplying by the appropriate factor and all fractions of a number are to be rounded up to the next whole number. When licensing Oracle programs with Standard Edition One or Standard Edition in the product name, a processor is counted equivalent to a socket.

This is exactly the definition you will find today today in Oracle’s online store, for example here.1 In fact, being lazy and not having access to a two-year-old copy of the OLSA, that is exactly where I got the text above.

Now, that little bit of bold text was a pretty big deal. As I understood it, and everybody I could find seemed to agree, this affected both the licensing cost and the eligibility rules. These 23 simple words now meant that Oracle Standard Edition was limited to computers with a maximum capacity of four (4) CPU sockets, not four processor cores. Although multi-core processors were — at the time, several years ago — relatively new, at least in the “commodity hardware” space, we all new that Intel and AMD had near-term plans for 4-core and eventually event 6- and 8-core processors. Suddenly, we could build an Oracle database server with 16 processors (cores) and 16GB of RAM or more, for less than $200,000. (Prior to this change, you would pay $640,000 — list price — just for the Enterprise Edition database licenses.)

But now, it seems, all of this is changing again, only this time, not for the better.

So what exactly has changed? (more…)

I noticed today that Howard's Dizwell-Oracle Reliable Installation Script (DORIS) version 1.0a shell script is available again for download. This is a useful script and great for installing Oracle on Linux without resorting to reading loads of "how-to" sites. Howard....[Read More]

Posted by Pete On 16/05/08 At 07:50 PM

I posted a couple of days ago a link to an almost certain hoax of a license plate of a red mini that had been altered to include SQL Injection. This was in a post titled License Plate SQL Injection....[Read More]

Posted by Pete On 15/05/08 At 09:02 PM