Re: AW: JCA on Web server

Managed Environment:

A managed environment defines an operational environment for a J2EE-based,
multi-tier, web-enabled
application that accesses EISs. The application consists of one or more
application
components-EJBs, JSPs, servlets-which are deployed on containers. These
containers can be
one of the following:
. Web containers that host JSP, servlets, and static HTML pages
. EJB containers that host EJB components
. Application client containers that host standalone application clients

A container implementation typically provides the following functionality:
. It provides deployed application components with transaction and security
management,
distribution of clients, scalable management of resources, and other
services that are
generally required as part of a managed server platform.
. It provides application components with connectivity to an EIS by
transparently managing
security, resources, and transactions using the system-level contracts with
the EIS-specific
resource adapter.
. It insulates application components from the specifics of the underlying
system-level
mechanisms by supporting a simple, standard contract with the application
component.

Non-managed Environment:

In a non-managed two-tier application environment, an application client
directly uses a re-source
adapter library. A resource adapter, in this case, exposes its low-level
transactions and
security APIs to its clients. An application client has to take
responsibility for managing security
and transactions (and rely on connection pooling if done by the resource
adapter internally)
by using the low-level APIs exposed by the resource adapter. This model is
similar to the
way a two-tier JDBC application client accesses a database system in a
non-managed environ-ment.

Taken from the J2EE Connector Specification.
Please have a look at the specification if the above information is not
sufficient.

Thanks,
Allwin.
-----Original Message-----
From: Lim Huat Heng [mailto:[email protected]]
Sent: Tuesday, March 18, 2003 4:15 PM
To: [email protected]
Subject: Re: AW: JCA on Web server


Manish:
   You mentioned managed and non- managed environment several times, could
you briefly elaborate what's the differences between them and what are the
advantages/ disadvantages of using non- managed environment?

> Hi Lim,
>  You can use JCA adapter in non-manage environment also...but if you want
to
> use JCO, attached is a tutorial for your help.
>
> Regards.
> Manish.
>
> -----Original Message-----
> From: A public list for J2EE Connector architecture interest.
> [mailto:[email protected]]On Behalf Of Lim Huat Heng
> Sent: Tuesday, March 18, 2003 3:26 PM
> To: [email protected]
> Subject: Re: AW: JCA on Web server
>
>
> Iris Peter:
>   I am really glad for your reply. From your explanations, does that mean
> that if I use Java (but running in web server), then I can use JCO, thus
no
> need an application server? If so, could you please elaborate more on how
I
> could achieve it? Thanks.
>
> > Hi Lim,
> >
> > 1) The JCO is not conform to JCA standards as it doesnt use a common >
> lient interface to access the ERP but directlcy access SAP via RFC . >
Also
> JCo is a bi-direktional interface whereas the current JCA standards > only
> allows uni-directional interfaces .
> >
> > 2) yes it does need a J2EE server to faciliatate services like system >
> management, clustering, security etc. I think the only chance you can do >
> it without is directly calling the RFC although Im not sure about the >
> performance impacts and the scalibility.
> > if your application is not only JSPs but also java it would work with >
> JCo
> >
> > 3) Regarding JcO have a look at the SAP pages . Also look at the SAP >
> WebAS page for more infos
> >
http://help.sap.com/saphelp_webas620sp9/helpdata/en/e1/8e51341a06084de100>
> 00009b38f83b/frameset.htm
> > you can donwload the connector az service.sap.com/connectors but you >
> need authorization for that.
> > http://www.sap.com/australia/teched/tuesday/HO3Fewster.pdf is also an >
> interesting intro.
> >
> >
> > I hope that helps,
> >
> > Iris Peters
> > EAI Architect
> > SPM technologies Germany Berlin
> >
> > -----Ursprungliche Nachricht-----
> > Von: Lim Huat Heng [mailto:[email protected]]
> > Gesendet: Dienstag, 18. Marz 2003 09:38
> > An: [email protected]
> > Betreff: JCA on Web server
> >
> >
> > To anyone who may advice:
> >     I am currently evaluating the feasibility of integration between a >
> web- based application (written in JSP and running on Jakarta Tomcat) >
and
> SAP system, in which, I will only want to 'download' data from SAP.
> >     I have searched in the Internet and found that there are few >
> architectures that could help me in achieving the objective. However, I >
am
> confused and would like anyone who may advice to clear my following >
> doubts:
> > 1) What is the differences between J2EE Connector Architecture (JCA) and
>
> SAP Java Connector (JCO)?
> > 2) Does J2EE Connector Architecture really need to be implemented on an
>
> application server? In order words, can I achieve the above objective by >
> using JCA but still running the system on web- server (particularly >
> Jakarta- Tomcat)
> > 3) What is the best practice to develop such a system (to achieve the >
> above objective)?
> > 4) Any good examples/ references (including source code/ demo page) that
>
> I could refer to?
> >      Thanks.
> >
> > =========================> =========================>
> =========================>
> > To unsubscribe, send email to [email protected] and include in the >
> body
> > of the message "signoff CONNECTOR-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 CONNECTOR-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 CONNECTOR-INTEREST".  For general help, send email
> to
> [email protected] and include in the body of the message "help".
>
> ----------------------------------------------------
>      Name: JCOTutorial.pdf
>      Type: application/pdf
>  Encoding: base64
>    Length: 37.34 KB

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-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 CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".