|
|
|
||||||||||
|
||||||||||||
|
» Buy |  |
» Try | |
» Map | |
» Contact | |
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||||||||||||||||
|
|
|
|||||||||||||||||||||||||||
|
|
Key Concepts:
"You struggle with your project trying to patch together multiple frameworks, from multiple sources, developed by different people for different purposes with different ideas, all of them differently configured and managed, with some of them dying off and some have never been properly tested..." Or you can just use xTier™
xTier™ Java Middleware Components provide a loosely-coupled set of pre-built services, for Java/J2EE. These services extend the utility of J2EE by providing reusable infrastructure-level "building blocks" which are not part of the J2EE specification and are often created and recreated for many development projects. The services provided by xTier™ are implemented utilizing the principles of Service Oriented Design (SOD) and Inversion of Control (IoC), which results in an integrated, yet loosely-coupled collection of services. This frees the developer to "mix and match" the components that are best suited to a given development project rather than being forced, by the product, to code to a "framework" all of the time. Many open source and commercial frameworks provide the developer with little more than an architectural design and in most cases is devoid of actual functionality. These "empty frameworks" leave the developer implementing the functionality behind the interfaces or connecting multiple third-party pieces to obtain a functioning whole. Often these frameworks have a "my way or the highway" mentality toward the developer and enforce their particular view of the appropriate design with little ability to use the technology in an appropriate fashion for the requirements. xTier™ avoids the "empty framework" or "framework for the sake of a framework" effect by providing full implementations for all the 20+ services contained in the xTier™ suite. With xTier™ there is no delegation to third-party software, no need for an additionally purchase, integration or worrying about versions compatibilities. All services - from simple to highly complex - are design and developed to maintain the strong conceptual integrity of xTier™ and the applications that are built using it. Coupled with xTier's™ clean and intuitive API and short learning curve, xTier™ quickly increases developer productivity while at the same time reduces the time to delivery and overall cost of the development project. The following diagram provides an overview of the architecture of xTier™, the services that it provides and its relationship to the different hosting environments.
By utilizing a small, environment specific micro-kernel, xTier™ provides a non-intrusive and easy integration path for a variety of deployment environments in both "clean-sheet" and maintenance projects, while at the same time maintaining a broad independence from the underlying technologies of this deployment environment. (Be it, for exampe a simple JSP Engine, a proprietary middleware or a full-fledged J2EE Application Server.) The Micro-kernel allows xTier™ to run in virtually any Java-based infrastructure. xTier™ Java Middleware Components is the first middleware suite offering totally componentized middleware where each component/service can be used independently while maintaining tight integration should they be used together. Furthermore, customers can buy only the components/services they need - and nothing more. xTier™ specifically avoids vendor lock-in by offering discreet yet highly integrated middleware services. This approach offers the best of two worlds: the ability to custom tailor middleware to the specific needs of the development project and at the same time provides a highly integrated solution that avoids any need for internal integration. xTier™ enables businesses to create faster, better, richer, more agile and flexible IT applications that can react and adapt to changes and new goals in a time and cost efficient way by removing the burden of writing and maintaining infrastructure level code.
xTier™ Services Navigator:
 More Information: xTier™ Overview - Technical Whitepaper
From its inception, xTier™ was designed and developed to provide clear and unambiguous additional value to J2EE and as such is meant to coexist within any Java/J2EE infrastructure. Further, xTier™ provides a consistent and uniform set of services across different Java-based environments and spans the Java/J2EE technology stack to provide a truely useful tool that can change the way enterprise applications are conceived and developed. It is important to note that xTier™ does not provide substitute services for those specified by Java/J2EE but rather provides additional services that extend and augment those currently provided. xTier™ provides a high degree of flexibility for the application architect or developer and can be deployed across Windows, Solaris and Linux across many different application servers. The only requirement is that there be a JVM version 1.4. Further, xTier™ can be used within the client, business logic, and/or back-end tier. In fact, xTier™ makes no assumption nor does it impose any particular design constraint on whether it is running on the client or server tier. Placing absolutely no inherent restrictions on how business applications use xTier's™ services developers can use one or two services, mix them with legacy services or use all of them in any combination. Business applications can continue to use any J2EE native services without any interruption while slowly migrating certain services to xTier™, thus leaving other functionality untouched and removing the need for expensive "rip & replace" integration. xTier™ can increase reusability and provides a new and unique way to accomplish middleware software reuse for customers with heterogeneous deployments.
xTier™ provides several simple to use, compact, and easily integrated micro-kernels for a variety of hosting environments. Developers using xTier™ can easily create their own environment specific micro kernel should they need to. (xTier™ ships with source code for the standard in-process micro kernel (J2SE) and the JBoss 3.x micro kernel to provide a detailed basis for custom implementations.) The micro kernel removes dependencies between the xTier™ Kernel and the specific underlying software infrastructure - whether it is a J2EE application server, a JSP/Servlet engine, or a proprietary Java middleware. This facilitates deployment and re-deployment of an application developed using xTier™ on different underlying infrastructures with only the requirement being a micro kernel change, as the application code that has been developed with xTier™ remains unchanged. (This statement obviously also implies, that to achieve total application portability, the application code does not make use of any environment specific features.) xTier™ ships with out-of-the-box micro kernels for the following hosting environments:
 xTier™ Micro Kernel Design - Technical Whitepaper.
 xTier™ Micro Kernel Examples (requires download)
xTier™ comes with GUI Management Console. Management Console provides unified view on xTier™ configuration combining familiar IDE look and feel with xTier™ customization. Developer can quickly navigate over multiple xTier™ installations, choose XML configuration files and edit them in embedded XML editor with specific syntax highlighting for xTier XML elements such as configuration regions. xTier™ comes with plugins for following IDEs:
Combined with IDEs, Management Console provide simple and quick way to change xTier configuration in a familiar environment:
xTier Management Console written in Java and provides consistent experience across platforms. Apart from managing xTier configuration,
Management Console provides other operations such as browsing Javadoc documentation and checking for software updates.
|
||||||||||||||||||||||||||||
|
Copyright © 2004-2008 Fitech Laboratories. All rights reserved. Legal and privacy notice. |
||||||||||||||||||||||||||||
