J2EE LOGICAL ARCHITECTURE

Jiffy specializes in J2EE enterprise Logical Architecture and offers the following services:

• JAAS, which are used to access different directory services through a common API and support single sign-on for SmartBPM and other applications executing in the same framework.
• JNDI, that acts as a common naming and directory service for publishing its EJB services and also searching existing enterprise services.
• JDBC Connection Pooling, which is supported by the underlying J2EE application server. Following the J2EE application server protocol for connection pools, Jiffy initializes and reuses the connections in the JDBC connection pool repeatedly for the various database transactions involved in Jiffy applications.
• JCA/J2C, Jiffy uses resource adapters to integrate with back-end legacy databases or Enterprise Information Systems. Jiffy also uses JCA support to handle connection management, security management and lifecycle management of resource adapters.
• JTA, Jiffy leverages the Java Transaction API to support distributed transaction commits. Jiffy uses JTA compliant resource managers during its execution. SmartBPM activities can be executed with any of the container-managed transaction attributes. Through transaction support, multiple Enterprise Java Beans connecting to different enterprise information systems could execute in the context of the same transaction.
• JMX, Jiffy also relies on the application server's JMX for monitoring the various components of the Pegasystems engine and applications.

J2EE CLUSTERING

Jiffy supports J2EE clustering of application servers executing concurrently to provide both load balancing for scalability and failover for reliability.

In this figure, clients access clusters through thin but rich Internet interfaces. The richness comes both from a cohesive user experience involving the ability to instantaneously analyze, design, deploy and experiment with our applications; and from graphical-representation objects involving information objects, flows, and business rules.

Our applications can execute within J2EE application-server clusters and benefit from their scalability and failover support. Given its robust support of model-view-controller and model-driven architectures, Jiffy applications can also be deployed in the Web-container tier, EJB-container tier, or both.

With Jiffy technology, the Web and EJB containers can be deployed on different JVMs to provide horizontal scaling (multiple JVMs are used for the Web and EJB components). Jiffy also supports vertical scaling, in which our solutions are deployed on multiple Web containers, multiple EJB containers, or combinations thereof.