| Author |
Message
|
| Vijay_d |
 Posted: Thu Jun 26, 2008 8:48 am Post subject: Implimenting J2ee in MB design decision |
 |
|
Apprentice
Joined: 09 Oct 2006
Posts: 26
Location: LONDON
|
Hi ,
Please comment your experience on using J2EE architecture in MBv6.0.0.7 using java node.
Say i have an a very complex back end database (ora -10g) with so many business rules on it.
I have an front end application which will interact with the database over webservices not thr JDBC/ODBC.
wat would be ur suggestion
1) MB broker host a service - where the message is got from the front end does the trasformation and route it to a q . The databsae acess layer is covered by a J2ee application and uses MDB to listen to q.
or
2) MB hosting the service - does the trasnformation and also MB acting as a database acess layer using java compute node ( where the complex java classes does the complex business logic)
Comment on the performance and also let me know ur suggestions. use of message broker is must and also it has to be a webservice call from front end. So kindly let me know ur thoughts with this in consideration.
Note: - I have no knowledge on java and how its powerfull with MB
we use message broker as there are other orchestration to be done other than hosting a service
Thanks
Vj |
|
| Back to top |
|
 |
| vsr |
| Posted: Thu Jun 26, 2008 9:08 am Post subject: |
|
|
Centurion
Joined: 04 Apr 2006
Posts: 104
|
As WMB is a tranformation engine keeping the business logic as less as possible would be a prefered method. If you have complex business logic and if your architecture allows you write a MDB, then I would prefer that method. In that way you can minimize database interactions and complex business logic in the broker.
We had a same situation here and we decided to use MDBs to achive this functionality as using broker flows involves complex business logic and log of i/o process. And it was proved a good decision later in several ways. |
|
| Back to top |
|
|
| Vijay_d |
| Posted: Thu Jun 26, 2008 9:27 am Post subject: |
|
|
Apprentice
Joined: 09 Oct 2006
Posts: 26
Location: LONDON
|
Thanks VSR
Ya i def go with you. But do u think using Java will be good replacement for it. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 26, 2008 9:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If there's nothing currently developed and deployed in J2EE, then I would use native broker database access methods (JDBC and ODBC) and NOT do the database calls in a JCN. Unless somehow the database is not accessible from Broker ODBC/JDBC native support.
And I wouldn't bother with J2EE/JEE data calls and MDBs at all, unless they were going to be called from things that are not Broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vijay_d |
| Posted: Thu Jun 26, 2008 11:10 am Post subject: |
|
|
Apprentice
Joined: 09 Oct 2006
Posts: 26
Location: LONDON
|
Hi Jef , Thanks for the response.
yes nothign have yet been developed. But when u say native acess methods..did u mean doing complex business logic using ESQL. can ESQL be expandable as Java?? ....
Say to create a record in a table .. there may be some pre-validation and dependency from other tables.( so many)
Can ESQL do all functions which Java is capable of..
note: i am not a java resource but ppl claim java does everything which esql doesnt  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 26, 2008 11:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
ESQL is Turing complete.
Java has more connectivity "natively" than ESQL - files, network sockets, etc.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 26, 2008 11:19 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The advantage of fronting your DB with an application (.NET, J2EE etc) lies in the independence of scalability.
The scalability of the DB no longer mandates the scalability of the flow, but depends on the scalability of the fronting app.
In short you may have only 5 flow instances but 20 front end instances. It all comes back to SLA.
Depends as well whether you use the request/reply pattern or the request/aggregation pattern...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
