Overall, Oracle's plan is that Fusion should be an open platform for building composite applications.
Supporting industry standards is regarded as an important step in making Fusion more open.
Charles Phillips, president of Oracle, said, "The idea of orchestrating services together cannot be done unless we have standard interfaces for these services."
He said while Oracle will regard its Fusion middleware as the preferred platform for building composite applications, a user should be able to slot in their choice of middleware.
"We have solved the middleware [issue]," by using the JSR168 standard, Phillips said.
JSR168 is a Java application programming interface for defining how application components, known as Portlets, can be aggregated to create a composite application.
This is the basis of the IBM and Oracle project to allow WebSphere to support Project Fusion.
Through the collaboration, users will be able to deploy IBM WebSphere as an application server environment for applications based on Project Fusion.
Phillips said the two companies began discussion two weeks ago and have begun working to assess which areas of cooperation are technically feasible.
JSR168 support is already possible in some Oracle applications. With JD Edwards applications, portlets can run within the IBM WebSphere portal.
Through the collaboration, the two companies will extend this to support PeopleSoft Enterprise and Oracle E-Business Suite applications.
Additionally, WebSphere and Tivoli identity management will be available, the two companies said, to support single sign-on and directories.