S
sanjeev.atvankar
Currently I am working on J2EE project. I am describing the actual
project scenario as below.
Front-End (Application layer) : VXML
Middleware : JAVA(Servlet)
Back-End : Oracle 9i
VXML : This language basically used in IVRS system for playing the
promts,
accepting the user details, process the user details etc.
eg.
- When we call @ any Bank Call Center for asking the balance.
First it will plays IVR(Promts), ask for your Acct No. and
then it promt the balance detail.
- So basically it is as good as looking the balance on Net (Net
banking).
- But in case of net banking your Front end is JSP/HTML and here front
end is VXML.
- But VXML has certain limitation regarding DB
i.e. it cann't communicate with DB efficiently.
e.g. error trapping, error handling etc.
- Due to above limitation we are doing DB operation through
JAVA(JDBC).
DATABASE (Oracle 9i):
- Since Oracle provides Exception Handling, and all DB operation we
are implemented
through Stored Procedures.
- So if there is any errors like Constraints it will be handled by
oracle exception
and store it in tables.
- Also all the transactions like DML on more than one table (commit/
rollback)
we are doing through DB(Inside Stored Procedures only).
- No transactions from JAVA.
In short if there is any errors related to DB(Most probably like
constraints etc.).
It will be handled by DB itself (through exception Handling).
JAVA :
- We have developed an web application using J2EE(Servlet) that only
access request from VXML in URL format as below
http://localhost:8084/NCC/Banking?CTRL_CODE=UpdTpinByIVR&hoganid=1&tpin=5545&.....
i.e. VXML will just pass the parameter to Servlet as query string.
- But we have created in layered architecture(MVC) i.e. Business
layer(BO's),
Data Access Layer(DO's),Data transfer(VO's) etc.
- I know we can do the Exception Handling in JAVA.
- But my root problem is how will handle exception from corresponding
layer
(Bussiness layer,Data Access Layer etc.)
i.e. it should gives exact cause of error(methods).
Means from which class(methods)/Layer.
- Errors Like parsing data Error,DB Connection failed, or any error
from JAVA.
Because any error cause due to DB(internal) we are handle it from
DB.
but any error due to java side we are going to log it into .txt
file.
I think above details describes you the architecture and processing.
So could u suggest any modification. Especially for Exception
Handling.
Thanks in advance
Sanjeev
project scenario as below.
Front-End (Application layer) : VXML
Middleware : JAVA(Servlet)
Back-End : Oracle 9i
VXML : This language basically used in IVRS system for playing the
promts,
accepting the user details, process the user details etc.
eg.
- When we call @ any Bank Call Center for asking the balance.
First it will plays IVR(Promts), ask for your Acct No. and
then it promt the balance detail.
- So basically it is as good as looking the balance on Net (Net
banking).
- But in case of net banking your Front end is JSP/HTML and here front
end is VXML.
- But VXML has certain limitation regarding DB
i.e. it cann't communicate with DB efficiently.
e.g. error trapping, error handling etc.
- Due to above limitation we are doing DB operation through
JAVA(JDBC).
DATABASE (Oracle 9i):
- Since Oracle provides Exception Handling, and all DB operation we
are implemented
through Stored Procedures.
- So if there is any errors like Constraints it will be handled by
oracle exception
and store it in tables.
- Also all the transactions like DML on more than one table (commit/
rollback)
we are doing through DB(Inside Stored Procedures only).
- No transactions from JAVA.
In short if there is any errors related to DB(Most probably like
constraints etc.).
It will be handled by DB itself (through exception Handling).
JAVA :
- We have developed an web application using J2EE(Servlet) that only
access request from VXML in URL format as below
http://localhost:8084/NCC/Banking?CTRL_CODE=UpdTpinByIVR&hoganid=1&tpin=5545&.....
i.e. VXML will just pass the parameter to Servlet as query string.
- But we have created in layered architecture(MVC) i.e. Business
layer(BO's),
Data Access Layer(DO's),Data transfer(VO's) etc.
- I know we can do the Exception Handling in JAVA.
- But my root problem is how will handle exception from corresponding
layer
(Bussiness layer,Data Access Layer etc.)
i.e. it should gives exact cause of error(methods).
Means from which class(methods)/Layer.
- Errors Like parsing data Error,DB Connection failed, or any error
from JAVA.
Because any error cause due to DB(internal) we are handle it from
DB.
but any error due to java side we are going to log it into .txt
file.
I think above details describes you the architecture and processing.
So could u suggest any modification. Especially for Exception
Handling.
Thanks in advance
Sanjeev