Educational Consultancy - Java Client-specific Training SYS-ED CETi


*Educational Consultancy - Java Application Development*	Java Training Sitemap


Submit Java Questions	Java Training Program	Java Courses New York Schedule
Definition of Service	Delivery Medium	Web-based Training Services

J2EE Application Development

Scalability and Coding Techniques

J2EE Web Application Isolation

Enhanced Loop

JCA: J2EE Connector Architecture

There has been a significant increase in the utilization of FOSS: Free Open Source Software - Java and commercial Java-based development platforms: IBM Corporation - WebSphere and Rational and Oracle Corporation - WebLogic and Oracle JDeveloper. The specific revision supported by a given server may vary, but competitive forces in the market inevitably mandate that all the offerings support the latest industry standards.

J2EE Web Application Isolation

The J2EE specification mandates that J2EE-compliant application servers partition web applications by assigning them different class loaders. As a result, two web applications cannot directly share resources even though they are in the same JVM instance and share the same process space. This ability to have multiple applications running independently in the same process space makes the Java platform well suited for developing scalable applications.

SYS-ED teaching assignments and feedback from CETi Technology Partners, indicate that there have been six major reasons for the utilization and support of the J2EE and web services standards.

J2EE WebSphere

Oracle Development Platform

Standard	Explanation
Web Services and SOA Standards Compliance	A fundamental tenet of SOA and network-based applications is the leverage and reuse of applications and business logic across the enterprise. This can be realized through the utilization of uniform industry standards.
Common Architectural Model	As an organization’s scale and needs change overtime, it will be necessary to migrate and redeploy applications on different physical hardware with minimal effort and disruption. Sharing a common architecture, facilitates the migration of web server applications.
Developer Leverage	A standardized application architecture, provides for an efficient and cost effective utilization of information technology staff in order to develop and maintain network applications.
Performance	Web server and application performance are essential for both user satisfaction and long-term efficiency and return on investment. Performance design provides headroom for future growth without mandating new capital investment.
Scalability	As an organization's information technology needs evolve, application servers need to be able to scale without requiring service disruptions or substantial redeployment efforts. Software scalability combined with savvy hardware choices can reduce energy, floor space, and operational management demands.
Application Infrastructure Virtualization	In order to realize the maximum return on investment, organizations will need their application environments to achieve a comprehensive level of virtualization: server, storage, networking, and application. The dynamic allocation of application infrastructure resources will result in a better utilization of existing hardware and application servers, reduce energy requirements, and minimizing expenditures on additional hardware and software.

Enhanced Loop

The enhanced for Loop eliminates the problems associated with using iterators and index variables when iterating over collections and arrays.

Examples, code snippets, and exercises demonstrate and explain its utilization in relation to the limitations in different base operating environments.

Facility	Explanation
Autoboxing/Unboxing	Eliminates the requirement for manual conversion between primitive types and wrapper types.
Typesafe Enums	This object oriented enumerated type facility allows enumerated types to be created with arbitrary methods and fields.
Varargs	Eliminates the need for manually boxing up argument lists into an array when invoking methods that accept variable-length argument lists.
Class Data Sharing	This features has been designed to reduce application startup time and footprint.
Garbage Collector Ergonomics	The parallel collector has been enhanced to monitor and adapt to the memory needs of the application.
Server-Class Machine Detection	The launcher can attempt to detect whether the application is running on a "server-class" machine.
Thread Priority Changes	Thread priority mapping has been changed allowing Java threads and native threads that do not have explicitly set priorities to compete on an equal footing.
Fatal Error Handling	This mechanism has been enhanced to provide improved diagnostic output and reliability.

Alternative to the Training Offered
by the Major Software Companies

Longstanding Experience in
Information Technology

Content Delivery Selection

JCA: J2EE Connector Architecture

JCA, the J2EE Connector Architecture, is an initiative towards EAI, Enterprise Application Integration. It is a standardized architecture in which J2EE Components have the capability to utilize plug and play access to heterogeneous EIS, Enterprise Information Systems. JCA provides a common API and a common set of services within a consistent J2EE Environment.

An EIS: Enterprise Information System provides the information infrastructure for an enterprise. This information may be in the form of records in the database, business objects in an ERP, a workflow object in a CRM: Customer Relationship Management system or a transaction program in a transaction processing application. Examples of systems include: 1- ERP: Enterprise Resource Planning applications - SAP and BAAN 2- CRM: Customer Relationship Management applications - Seibel and Clarify 3- Database applications: DB2 and Oracle 4- Main transaction processing applications: CICS 5- Legacy Database Systems - IMS.

Prior to JCA, vendors had to support a variety of custom adapters for integrating their EIS. These adapters provided custom native interfaces, which were complex to incorporate and limited to only one EIS. This meant that application programmers had to deal with as many adapters as the number of EIS their application communicated with.

The significant limitations were:

Application programming for the EIS was proprietary; there was no generic platform for integration with the open architectures.
Custom adapters lacked support for Connection Management, this meant that connection pooling had to be implemented in code.
There was no standard infrastructure solution available to provide a vendor-neutral security mechanism and generic transaction mechanism support to multiple EIS resource managers.