Any thoughts on whats going to happen with Nexus, Siebels composite application platform, given its similarity to Fusion Middleware? If you look at the objectives for Nexus and Fusion, they are remarkably similar. You need to move to much more component-based architecture that allows people to extend. Its exactly the same thing. What were really looking at is, How do we bring some of the Nexus developers on-board and try to accelerate overall the project? But they were in kind of similar points in some ways, a little further ahead in others, and a little behind in others.Absolutely. A good example is one of the things we think is very important in the future is that, if you think about skinning the application, and then theres capabilities like where were focused called a DHTML interface, which is kind of like Java scripting but is an AJAX principal, and thats a very common design pattern that weve been moving to. Microsoft has been building much more of whole rendering kit around that in Nexus, and we think that is a very attractive option that we want to have in the architecture. So thats something that were hoping actually that there are just some nice components that well reuse those. Theyre still in Java class libraries, so theoretically some of the stuff is still usable. But its really the people who designed that, really what they learned in going through this process thats really what we inherit as part of this. You talk about on-demand applications as being a big part of your business in 2010. In terms of how youre building your applications today for the future, how is that going to move you forward with on-demand? The biggest area we focus on in terms of on-demand is this idea of superior ownership experience. We think a lot about, How do you make a more productive on-demand business? How you make a more productive on-site deployment is you have to really focus on automationthings like the configuration setup, definition process, how you orchestrate a business process and have the applications inherit that behavior. Thats going to have a huge impact, and make our customers much more productive in deploying applications. And its going to make our on-demand much more successful as well, because [users] can really fine-tune the application, even when were running it on our premises, to an individual customer requirement. So its not running a separate iteration of an application for on-demand specifically? Yes. One thing that Siebel has done is they have a separate code line around their on-demand business and they iterate very fast. That is one thing were actually looking at. Were going to keep that code line around CRM [customer relationship management]. Were going to continue to support it. The same thing with Contact On Demand, which is a business they started last year. Were going to continue to iterate those code lines. Well adopt the Fusion architecture, but we actually think theres a reason why they did that and why they wanted to go more quickly. Check out eWEEK.coms for the latest news, reviews and analysis about productivity and business solutions.
I know youre not talking about merging code, but will you take some of the development work theyve done over the past three or four years and bring it into Fusion?