Pegasystems fits into enterprise architectures and offers:

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