Legacy java app & Web Logic App Server

Question

Hi,
We have a legacy java application that we like to provide an EJB layer
for.
The legacy application provides a servelet interface, event queues, our
own
JDBC Conn Pools, etc...
Can we integerate legacy java code into the Web Logic App Server? That
is,
we like to use the Weblogic's api's for servelets and JDBC conn pools.
We would also
like to use the clustering feature to provide failover. Also, our
application creates bunches of
threads. Do we need to rewrite this code to use Weblogics thread
creation techniques?
If this cannot be done,
another option would be to provide an EJB layer where the entity beans
would map to
elements in the legacy application using our own version of the
connector.
Then the app server would only encapsulate the EJB
layer. Could we still use your JDBC Conn Pools and other services in
the java legacy app?
Still the problem with this solution is that we can't use your
clustering scheme around our legacy app,
or can we?
Any help would be appreciated.
-- tony

Answer 1

It can even be a standard production scenario if you want to run Oracle Portal 11g on a single box. The single sign-on part typically requires you to install an AS 10g SSO server which co-exists with other components such as WebLogic server.
Notice that there is a sharp division between everything which is inherit from the old OAS, the so-called instance components, typically started with OPMN and the new WLS stuff.