Hi,
<vendor>
If I understand correctly, the question you are trying to address is that since
Oracle DB is also a full fledged EJB Container, what level of (logical)
separation should be achieved between any web server (weblogic, websphere) and
Oracle DB while deploying EJBs. How does one decide which EJBs are to be
deployed at the database level and which ones are candidates for web server
deployment??
Oracle claims the folloing benefit for DB side EJB deployment :
In Oracle8I each database client (GUI, Servlet or command line) gets a different
database session with a different set of Java objects. There is little
contention between the clients. Other EJB servers typically pool many clients in
single process Java VMs and the performance can degrade when the number of
clients increases. Also since EJB's access persistent state in the RDBMS via the
embedded JDBC Driver, SQL Data access is very efficient from EJBs deployed in
Oracle8i.
I think the best choice that you have to start with is option 2. In Oracle the
concept of a session ensures that the the open cursors, the PL/SQL global
variables, the Java static variables and all the EJBs activated on behalf of the
Client who started the session are all in the same meory space and can point
directly to each other.
This will ensure that the calls between EJBs activated in the same session do
not cause any network round-trips and the arguments are passed by reference
instead of by value for the CMP EJBs atleast. I guess the road ahead from
here - that is to chose between Options 2 and 3 is hard - I guess the proof will
ie in successful testing of the app by redistributing the ejbs deployed between
the tiers. I would like to hear from you on your observations.
</vendor>
Regards
-------------------------------------------------------------------------------
Nitin Goyal
Software Development Manager,
Webrizon eSolutions Pvt. Ltd.,
B-31, Sector 5, Noida-201301 (UP) INDIA
Tel (O) : 91.118.4421319, 4421320 extn 245. Cell : 91.9810353030
Tel (R) : 91.118.4451789 (914451789 from Delhi)
email: [EMAIL PROTECTED]
-------------------------------------------------------------------------------
There is no failure except in no longer trying.
----- Original Message -----
From: "Srinivasan_S" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 20, 2001 10:33 PM
Subject: Oracle Entity Beans
Hi All,
In our system we need to access the Oracle 8.1.7 database from EJBs deployed
in the proprietary EJB 2.0 compliant Application Sever. The Oracle 8.1.7
supports the Entity Beans.
option 1
To use the relational database which can be accessed from the proprietary
EJBs using the JDBC
Option 2
Deploy CMP Enity Beans at Oracle for each table and the proprietary EJBs
access entity Beans. For access with joints there will be multiple calls
form the proprietary EJBs to Oracle Enity EJBs
Option 3
Deploy CMP Enity Beans at Oracle for each table and also deploy Session
Beans at Oracle to reduce the number of remote invocation from the
proprietary EJBs in case of joints.
The system is planned to handle hundreds of transactions per second with
more than 300 concurrent users. Scalability and Perormance are important
requirements.
Any reply/suggestion please.
Thanks and regards
S.Srinivasan
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
