J2EE Architecture!

Hi All,
I know that J2EE architecture is multitiered distributed architecture consisting of Client tier, Business component( Web components + EJB) and EIS or database at the back end. Looking at this architecture, the Client is nothing more than a user's Browser that is, IE or Netscape etc. Now why do we consider these IE or Netscape or any browsers as a client tier as if we develop them? I would appreciate if you could educate me.
thanks.

Similar Messages

Java & J2EE Architecture & Development

can soomebdy provide me a link to a pdf on Java and J2EE architecture and development in XI .
Thanks in advance ,
divya

Hi,
XI-J2EE for Java programmer
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ada5ef-0201-0010-1f8b-c935e444b0ad
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7bf6e190-0201-0010-83b7-cc557eb76abe
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee7fa790-0201-0010-5aac-a0b2f0e94982
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c1311203-0701-0010-dba2-9f42e9a74ea9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0482c490-0201-0010-cc9c-91c5a538a0a6
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/13926f23-0a01-0010-149c-c1170e7a25db
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/423f5046-0a01-0010-2698-b2dc7c3185f1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7ac6ae90-0201-0010-50b4-f71fa2cc271a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0332d790-0201-0010-46b1-a0530fe87c1fhttps://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c75ee690-0201-0010-7baf-af868a642918https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/13d02057-0601-0010-abba-be4a86d47f9e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0f00c890-0201-0010-beb2-c96050edc426
Regards
Chilla..

J2ee architecture/framework books/pointers

hello,
can you suggest me some good j2ee architecture as well as books/pointers?
thanks

There are more than one way to do all this, depending on your particular application:
- servlet's init() method, if it's a Web application
- JMX MBeans
- EJB Timer service or some other job scheduling like Quartz
- batch programming (Unix shell + cron, or Win batch)
- etc...
Also, EJB is merely one technology inside the J2EE stack. You can use J2EE without EJB, and in many cases, this is the best option.
Sun's J2EE tutorial.

J2EE Architectural Design Solution Needed

Hi,
I am coming up with an issue in designing the application architecture. It would be great if some one suggest solution for the problem.
The basic flow of application:
1. Client initiates a transaction from a Portlet.
2. Portlet invokes business service component (Coarse grained Stateless Session Bean) by passing XML document.
3. Corse grained SLSB process the incoming XML and invoke local session beans by passing relevant Document objects built by using service API.
4. Based on Incoming Message, message splits and placed on multiple destinations (Linked by Message Queues) hosted on Enterprise Service Bus (ESB).
5. A Message driven bean listens to the incoming request at Queue and invokes external services/Web services
6. Response xml is built and placed Response Queue in ESB by invoking business service API.
6. A MDB listening to the Response Queue will process outgoing messages which needs to be routed to original request invoker.
The Messages are linked with correlation ID and request and response are tied by some rules and business logic.
The design problem I am facing now is, how do my client waits till response comes from response queue as application need to give response to the client in synchronous manner.
The other issue is some of the incoming requests need to be executed (placing in queue) in orderly fashion and run in a transaction. (Which I am trying to process them as command Lists in prototype using Message sets and flows in MQ, but is there any implications if try to push this logic to J2EE container)
Thanks,
Madhu Palutla

I think that you need not worry about the client waiting for the response..since this is a simple request response cycle and is synchronous...thus the invoker need to wait for the response anyway.
Secondly, I hope that you would definitely carry the points 4,5, and 6(the actual 6
) in a transaction, the option to choose the programmatic or declarative always remains on you.

Oracle Report in a J2EE Architecture

Dear All,
I have for this architecture:
- Database Layer Oracle 8i in future 9i
- Application Server Tomcat
is possible to integrate this architecture with a Oracle Report Server?
If yes how to transform the architecture?
Thank's bye

Hi,
Download samples of Web Services SDK code from link below
http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2/en/devsuite.htm
Web Services SDK -
> Business Objects Web Services Java and .NET Code Samples-----> Download the Java code samples
and go for sample code "viewReportWebi".
This should help up.
Thanks,
Praveen.

Appreciating J2EE Architecture

I was asked a question in an Interview, I did not give a convincing answer. I request for a Convincing answer:
Question: How do you appreciate J2EE Architecture

Just putting my thoughts..
The ultimate goal of this is Customer Satisfaction. Customer can be Software architects, Developers or the most important END USER. J2EE has advatages in all the three category.
For architects..
Nothing much to say, cuz I am developer and I haven't yet designed a complete system yet. Since the Containers take care of the complex issues like resource pooling, Transaction management, Security Issues and other low level jobs, it just give enough time to concentrate on business logic. Also the componentisation and platform independace helps in concentrating on specialising in software development roles like Web Component Developers, assembler, administrator and so on.
Watch out for Web-Services, this will introduce one more specialisation area for Software Vendors.
For Developers...
Java is easy to learn, tame and use. :)
J2EE, each component development, EJB, JSP, Beans, Servlets and so on..is a specialised job and although they are integrated, we can make them independent entities during development stage. Efforts to learn each of them, nothing more than few weekends. :)
For End Users...
XML, the back-bone of future IT. will make Any One, Any time and Any where usage of end products. J2EE has advantage in this end since it can be easily used for this scenario along with XML and related Technologies. We can have wide range of Clients i.e. users like thick client, browser, mobile, plamtop, and even land line phone. But the Back end application is SAME for all these.
So I feel J2EE applications is just not "Write once and Run anywhere"... its Write Once, Run Anywhere, and Feel Everywhere. :)
Cheers.

J2EE Architecture (EJB)

I have become increasing disillusioned with J2EE and EJB�s in particular. I am no longer sure what they are trying to achieve and how the �objectives� are implemented. Writing the simplest EJB by hand is time consuming. Using something like XDocolet produces mountains of �Pseudo-Code� in comment blocks. The very idea of using comments in code to write code seems perverse to me. Surely comments are for comments and code is for code. After all this what is generated? The simplest of SQL statements. What are the benefits ? More efficient code ? More robust code ? Easier to maintain code ? More portable code ?
Would somebody care to point out what I am missing ?

Excellent thoughts, Annie, as usual.
Performance and learning curve seem to be the biggest complaints about J2EE and EJBs.
I think stateless session and message beans are winners. Entity beans are the red-headed stepchildren: nobody seems to like them much, even with local interfaces. There is so much disagreement about how to handle persistence in Java (e.g., raw JDBC, JDO, O/R mapping, CMP, etc.) that how to "best" handle it is still open to question.
I'm not aware of the same level of thrashing in the .NET community. (I'm not aware of much in the .NET community.) How have they solved the O/R impedence mismatch to everyone's satisfaction?
Scott Ambler wrote some terrific papers about O/R mapping. I'll have to go back and re-read them to see if I can figure out which of the competing persistence technologies best address the problem.
The whole point of J2EE and its containers, IMO, is that the smart developers who write the container relive mere mortal programmers like me from writing a lot of difficult plumbing. The container worries about threading, transactions, persistence, clustering, security, and all sorts of other things that I'd have to write a lot of code to reproduce without it. (Or worse, just leave it out and hope for the best.) I think that's still a worthy thing to do. The trick is to take as much advantage of the container as you can without distorting your application's design or compromising its performance.
EJB 3.0 is debating this again. POJOs sound like they'll be much more prominent. It'll be interesting to see where this goes.
Personally, I'm astonished at how complex entity beans and persistence are in J2EE. Entity beans map to database rows, but that's not a good match for the set-like SQL and relational databases. Remote entity beans are a disaster: Do I really need a remote call for each and every field? Local interfaces help, but we still need the Session Facade Pattern, DTOs, all kinds of machinery just to get a bloody value out of a database and into a JSP. How much layering is too much?
%

J2EE architecture question

Suppose you have a distributed application consisting of a number (max 100) of webservers (Servlets/JSPs technology) which send information (e.g. a random number) to one central system (using EJBs). The central system receives the random numbers through a session facade and adds the contributions from the various webservers. When the total reaches a certain level, the central system needs to inform all contributing webservers of the new total.
My question:
- What is the best (simple, low-cost, easy to implement) way for the central system to inform the webservers?
Options I've thought of:
1. messaging (probably too complicated?)
2. polling from the webservers (too much traffic?)
3. central system invoking a Servlet on each webserver (is this practical?)
Any comments will be greatly appreciated!

1. messaging (probably too complicated?)Actually quite easy, especially since your app server probably already has a JMS provider. And, if all of your Servlet servers are basically running the same application (e.g. same deployments), you'll only have to write one MessageListener to be placed in the application.
2. polling from the webservers (too much traffic?)Too much traffic, threading issues, wasteful of processing power - a whole host of problems with that approach.
3. central system invoking a Servlet on each webserver
(is this practical?)Then your main EJB application would have to "know" the address of each and every webserver - which gets you into a maintenance nightmare. Not practical at all...

Help needed. General question about J2EE architecture.

Hello,
On the one hand, I have a java class (actually a set of classes) that does a lot of low level input/output operations.
On the other hand I have a web console in jsp/servlets.
I want to be able to invoke a method on the "low-level" java app from the web console bearing in mind that the war will run on one computer on the network and the "low-level" app on another computer on the network.
What is the best way to invoke a public method of the "low-level" app from the web console????
Do I need to use RAR adapters?
Any clue very welcome,
Julien.

There are a number of ways it COULD be done. What I would do would be to wrap the low level handler classes in web services that run in an application server on the other machine so that you could call them from the web application that you currently have.
Among other things that maintains the isolation and integrity of your operations and prevents you from building a dependency between the two code bases.
Hope this helps,
PS

What the hell j2ee is

it is said write once, run anywhere, but one month passed, I still could not have a simple application client run on a machine(solaris) rather than the machine running the j2ee server(windows), I 've copied j2ee.jar, tired setting classpath, re-jar the appClient.jar, tried to correct the manifest.mf.... how trouble it is!
I like C/C++, how easy to let it work once I can compile a server and a client program, I can copy them to any machine and run them without such kind of trouble setting.
really dislike Java now

You cannot compare C/C++ Client/Server with a J2EE architecture. They deal with very different issues.
About your deployment issue, I don't understand why you tried and changed your manifest file. We work on two platforms : one is an NT plateform, the other is Linux. We use BEA weblogic on both. I do my testing on NT and then I juste have to copy my file on Linux to have it work. However, it is true that we sometimes have difficulties with classpath settings and packaging. but once it's done...
If you could be a bit more precise in your problem description, maybe someone could help...
/Stephane

Shine J2EE Appplication Framework - A New MVC -JWMS-Ajax Framework

Hi Dears
Shine is a Java-J2EE Application Framework/JWMS(Java Web Model Service)Framework/MVC Framework/Service Oriented Framework. Shine Includes Ajax Libs/Server API/J2EE Architecture. Shine Supported JSF/Spring/AspectJ/Struts/Hibernate/...
You can use Shine Framework for Implement ERP Web Based Application, Web Based Operating System, WFM Web Based Application, CRM Web Based Application, HRM Web Based Application, BPR Web Based Application, Or ... Web Based Application, Shine Registered in Source Forge.
This Framework is a Java Service Oriented Framework for Web Based Project. This Framework include:
* MVC (Model View Controller)
* Ajax
* Service Oriented Scope
* JWMS (Java Web Model Service)
Shine Framework is a Java Web Model Service Framework.
Shine Framework is very easy, stable. You can use other Framework by Shine Framework:
*Hibernate
*Struts
*Spring
*And Other Framework
JWMS And Shine J2EE Framework ?
JWMS is a J2EE Architecture for implement Service Oriented Web-Based Appliction you can get more information about this and Shine J2EE Application Framework by -> J2EE And Service Oriented Programming :
http://j2sos.googlegroups.com/web/J2EE_And_Service_Oriented_Programming+(English).doc?gda=VCp-YWkAAABaK1bFJn7XMhSpdkjvrT6Pd5MA3H6uh5taxEUxR6gwSUWwa05VcrqgHRSC0l_xcf_5FoxLEBXNbyq4-bBifvraWOZGQE6LgzeTU5Q6eFny4M-fIZvKNC5H8bRWhAn1psCECKgQbmraGdxlZulaYnsh
Or
http://j2sos.googlegroups.com
Report: http://sourceforge.net/tracker/?group_id=244136
Forum: http://sourceforge.net/forum/?group_id=244136
News: http://sourceforge.net/news/?group_id=244136
Wiki: http://shine-app.wiki.sourceforge.net/space/pagelist
Rank: http://sourceforge.net/project/stats/rank_history.php?group_id=244136&ugn=shine-app
Shine J2EE Framework Rank in Sourceforge is 14!
Shine J2EE Framework: http://sourceforge.net/projects/shine-app/
Site: www.J2SOS.org
Special Thanks Oracle! For this Part! Your Site is very Active about J2EE - Java!
This paper is no image paper !!!!!!!!!!!!!!!!!!!
J2EE and Service Oriented Programming
Authored by: AmirSam Bahador
Level:
Advanced
Contents:
Introduction
- The purpose of compilation this essay
Chapter 1: Basic concepts of J2EE
- Servlet and JSP
- MVC
- MVC or JWMS? That is the problem? Perhaps both!
Chapter 2: Basic concepts of Shine Framework
- What is "Shine Frameworkâ€�?
- The components of Shine Framework
- Implimentation of an application by Shine Framework
Chapter 3: The objects of Shine Framework
- The types of objects in Shine Framework
Chapter 4: Engineering & Communication items
- The communication of Shine Framework with the other
existing Frameworks
- The major purpose of Shine Framework
Introduction
The purpose of compilation of the this paper
A few years ago, when I was the software architect of a big project with J2EE, I advised some of the modern tools of that time to the project manager. He acknowledged it. Therefore, we began deploying our Enterprise on Java platform. However, we encounterd with many problems, as we got ahead the project. Our tools were included Struts Framework, Spring Framework & Hibernate.
I convinced that MVC architecture is the best option to develop macro projects! However, I believe it now, as well. Couldn't it be more completed? In developed Enterprise projects, an advanced architecture is required to divide the project, technically. The project was successfully finished after one year, but my mind was busy with it for a long time!
Then, I began implementing an Application Framework and registered it in Sourceforge.net as an Open Source Framework. I developed some Enterprise projects & some other J2EE frameworks, as well. I achieved a good result! The velocity of implemention & developing projects increased up to 50%. Subsequently, by cooperation of my elected students who had worked with Application Framework, I established an organization, named J2SOS, to protect & develop this Application Framework.
Fortunately, my students were so skilled that each took a chief task in big J2EE projects.
Their experiences had a practical affect on development of Application Framework as well as the organization.
Therefore, it is required to write down my & my yesterday students (my today co-workers) experiences. This was the outset to write the present paper!
Chapter 1
The basic concepts of J2EE
Purposes
In this chapter, we do our best to introduce J2EE basic concepts.
Servlet & JSP
If you ahve ever worked with JSP & Servlet, you know that Servlet is so proper for processing functions but there are particular problems with it in displaying functions.
JSP is applied reverse to Servlet. Thus, what is the solution? To apply both JSP and Servlet together!
What is MVC?
MVC is an easy way to use JSP & Servlet together. In MVC architecture, the request will be processed by a Class (Servlet) and the appropriate response will be showen by JSP.
n the above Servlet Class, the validation operation, etc will be done.
Nowadays, there are numerous Frameworks which will assist you to use MVC Framework architecture. Struts Framework is the most well-known one.
MVC or JWMS ? That is the problem! Perhaps both!
MVC is a powerful architecture, but it is required an advanced architecture to implement developed projects.
Today, web applications are well developed which complicatethe work for programmers & developers.
To clarify it, see Google site! Google Web Application enjoys numerous services, each have a special service for the users.
For Instance, Gmail service, E-Mail or by SearchEngine, the users can search for websites, pictures, etc.
These services have certaily close communication with each other.
If the services do not use a particular architecture, the Google will encounter with various problems.
In Service Oriented architecture, each part of the program is a service programme. For example, E-Mail service, SearchEngine service, etc.
for get full this paper plz goto : J2EE And Service Oriented Programming
in :
http://groups.google.com/group/j2sos
Or
http://j2sos.googlegroups.com/web/J2EE_And_Service_Oriented_Programming+(English).doc?gda=-C13JmkAAABaK1bFJn7XMhSpdkjvrT6PLb1WFhhPKkBftsH3LvtvGEWwa05VcrqgHRSC0l_xcf_5FoxLEBXNbyq4-bBifvraWOZGQE6LgzeTU5Q6eFny4M-fIZvKNC5H8bRWhAn1psCECKgQbmraGdxlZulaYnsh

iabstudio have been engaged in a persistent Usenet and webboard spamming and astroturfing operation since the beginning of this month. Google has the scoop at http://groups.google.com/groups?q=www.iabstudio.com&hl=en&lr=&c2coff=1&scoring=d&start=0&sa=N&filter=0 note in particular the same IP address is used to post both their spam from iabstudio themselves and from people who claim to be satisfied users. If you do not like spamming and dishonest, don't use the product.

Converting Oracle Forms to J2ee - (Focus on Form triggers/ Form Procedures)

Hi,
We are in the process of exploring the option of migrating forms to J2EE using JheadStart tool. After migration of forms using Jheadstart tool, what will happen to my Form triggers, Procedures? Does the GUI look and feel - canvases and tabbed pages etc will be exactly same?
Ex: I have created a sample master detail form with few buttons and triggers. After migrating the form using jheadstart evaluation copy, I am not finding the buttons and as well as any logic enforced on buttons. On top of that the GUI is not same as in FORM, it comes with one find window and then navigates to master detail block. Does that mean, I need to customize the pages also for each form to be migrated?
Would be very much thankful to you for your early response on the same.
Thanks and Regards,
Venkateswar NDT

Venkateswar,
JHeadstart Designer Generator does not transform all functionality of your Forms into J2EE. JHeadstart focuses on providing the same data reporting and manipulation capabilities.
The reason for this is that we want to produce an application that can easily and productively be maintained and extended. The migration is not the final stage of the trip, it is only the beginning of the journey. The migration result should be (close to) what you would have developed from scratch.
What is not migrated:
* Business logic coded in Forms
* Fancy layouts that cannot be built using HTML
* Complex, cross-forms navigation
We think this is preferrable over line by line translations of PL/SQL into Java, because the Forms architecture is so different from J2EE architecture. It would lead to a badly structured J2EE application that would be very hard to maintain. Instead, we want to give you a head start in creating a well structured, maintainable J2EE application.
You get a migrated application with:
* Professional and powerful HTML user interface
* Most common layout styles are fully generated
* Compliant with the Model-View-Controller Paradigm
* Component based architecture that enables you to wire different business component together
In the JHeadstart Developer's Guide (which is shipped with the evaluation copy), chapter 5, you can find more about the JHeadstart Designer Generator. Look for example at page 5-19 and onwards, for details about what parts of Designer Modules are transformed. You can also take a look at the JHeadstart Designer Generator Reference, to which a link is included in the JHeadstart Documentation Index ([JHeadstart Home]\jheadstart\doc\index.html)
Hope this helps,
Sandra Muller
JHeadstart Team

What exactly is J2EE?

I've been learning tomcat and jsp's. I have a few small applications under my belt and I wanted to move on to J2EE. Is J2ee basically just a file structure you add to your app, a bunch of librarys or something you add to each and every app you have? What exactly is it?
My webhost told me I can run j2ee apps with them. How is that different then the tomcat apps I've been running there? I just don't get it. What is the basic file structure of a j2ee app? I know all the little tomcat apps I do are basically just this....
WebApp ---------> WEB-INF/classes
WebApp ---------> index.jsp
thanks in advance

I've been learning tomcat and jsp's. I have a few
small applications under my belt and I wanted tomove
on to J2EE. Is J2ee basically just a file structure
you add to your app, a bunch of librarys orsomething
you add to each and every app you have? What exactly
is it?
My webhost told me I can run j2ee apps with them.How
is that different then the tomcat apps I've been
running there? I just don't get it. What is thebasic
file structure of a j2ee app? I know all the little
tomcat apps I do are basically just this....
WebApp ---------> WEB-INF/classes
WebApp ---------> index.jsp
thanks in advanceI don't think J2EE-ness has anything to do with file
structure.
I've worked on J2EE apps on and off for a few years
now, and I still can't give you a good definition. (If
you ask daFei he'll tell you you have to use EJBs for
it to be J2EE, but he's terribly confused about a
number of things.) If you look at Sun's J2EE page,
you'll see the pieces that form the J2EE architecture.
IMHO, if you're using one or more of those elements,
you have a J2EE app. I don't think it's a file
structure or a bunch of libraries.Okay I think I'm seeing the light at the end of the tunnel, thanks alot for that. I've also read the EJB's don't make it an enterprise app somewhere or other and there are different oppinions on this.
thanks

J2EE Patch Upgrade Hangs

When executing the J2EE upgrade from PL19 to PL24, the install process hangs at 0% after clicking on 'start' button. Has anyone else encountered this issue? If yes, then how did you solve it?
We're in a standalone J2EE environment not cluster...therefore, the major J2EE architectural changes (between patch levels) don't apply according to the notes.

Just referring to one of the newest SAP Notes regarding J2EE engine upgrade (720148)...It says, "PL 21 Standalone version of SAP J2EE Engine contains no architectural changes and only bugfixes. If one applies SP21 standalone version, the recommendations for cluster version as well as the additional sizingestimations are not necessary. PL 21 Standalone version is pure bugfix release."
As of today, I don't see any notes regarding PL 23. At any rate, we're sort of off the main issue.
I've tried upgrading from PL19 to all other releases above that (PL20 and higher) and I get the same result of the install hanging at 0%...any ideas?
I want to upgrade beyond PL19 because of the EP6 SP2 Patch 4 requirements.

Design of first distributed architecture

Okay, so I'm trying to design and implement my first distributed project, and I want to make sure my general design is okay before I start. Like I say, I've never used J2EE before, and I'm still learning about it. This is very general.
Problem: Design a login system complete with the following aspects:
- A basic login window/applet that takes a username and password and verifies them. If they are valid (as determined by specific business logic), return a cookie (assume they are allowed for now) and allow the user access to the requested resources on the server. (Note: I think I'm using the term business logic correctly, but tell me if I'm not.)
- A basic registration window/applet that takes a user's information. Depending on the business logic, the user will be registered to the database for a certain access level or will become a �pending user,� which will be reviewed by an administrator before being allowed to access the server�s resources.
- An administrator�s window/applet that is basically a view of all that goes on in the server. This includes
* current users
* pending users
* audits
* files on the server
* any directory and access protocols
* server settings
Proposal: I plan to follow basic J2EE architecture patterns: The browser will allow access to all of the windows. The windows will call on servlets, which will call on EJBs to access the appropriate tables, all in the same database. I will make a servlet for each table category: UserServlet (for accessing the user list, maybe the list of pending users), AuditServlet, SettingsServlet, LdapServlet, etc.
Should I make a separate servlet and EJB for each category (as listed above)? I still have to read up on EJBs before I implement this.
So that is my basic skeleton, but I have no idea as to its quality. What do you think?
theAmerican

_dnoyeB said:
An EJB per table seems odd. You should consider some
form of ORM. Perhaps EJB3 will work for you. As I
understand it, and its beena while since i did j2ee,
EJB represents a thing, not a databaase table. i.e.
an EJB represents a person, not the person table.Okay, that makes sense. (The idea of one EJB/table didn't seem exactly right to me.) By ORM, you mean something like Hibernate or EJB3? (Could Spring be involved here? I know it isn't solely concerned with DBs.) I appreciate the advice.
Saish said:
I would also consider implementing an out-of-the-box controller
ala Struts or Spring rather than dozens of Servlets. I was thinking about using Spring. Would you recommend doing that before I even do my first distributed app? Also, which do you prefer: Struts or Spring? Thanks for the input.
Hoos said:
If you are using J2EE I would suggest you read up on the security services
provided by your J2EE container. It should provide you with instructions on
setting up realms etc and also provide components to access security data
in order to perform authentication and authorisation etc.
Unless you have need for extended security you will probably find that the
containers services means you wont need to write your own components e.g.
LoginEJB that checks usernames and passwords etc.Awesome. Thanks for the advice. I'll look into it. (This is just kindof an excercise to get my feet wet in distributed programming.) I may consider doing another project instead.
theAmerican

J2EE Architecture!

Similar Messages

Maybe you are looking for