Java Composite Application Platform Suite (CAPS or JCAPS), is a standards-based extensible software suite from Sun Microsystems involved in the Open ESB initiative. It is used to develop software infrastructure when a service-oriented architecture approach has been adopted. Java CAPS is composed of several packages which help to integrate existing investments and deliver new business services in a SOA environment. As with other Java technologies, Java CAPS provides no specific vendor lock-in and supports a variety of operating systems.
Java caps was originally product of SeeBeyond Technology Corporation having name Integrated Composite Application Network Suite (ICAN) was renamed to the Sun Java Composite Application Platform Suite (Java Caps), after the acquisition of SeeBeyond by Sun Microsystems on August 25, 2005. ICAN suite was a Java EE compliant platform and provides application-to-application integration, business-to-business integration, business process management along with integrated human workflow, portal, extract transfer and load, business activity monitoring and composite application development capabilities.
Version History 
- Initially project was named as DataGate which was later renamed to eGate around late 90's with new distributed architecture and version shifted from Datagate 3.6 to eGate 4.0. Monk, a LISP variant was used for translation of the message.
- In 21st century, eGate 4.5 was released in 2001 having enhanced support of Java support including introduction of JMS.
- The new architecture based on J2EE was launched in 2003 with version 5.0 using enterprise designer IDE(based on Netbeans) and named as ICAN. The Table Runtime Environment(TRE) upgrades Data Gate 3.6 system to take advantage of eGate 5.0 tools, such as Enterprise Manager etc.
- In 2005, Sun took over SeeBeyond and first updated release from sun was JCaps 5.1 with few enhances in architecture.
- In 2008, JCaps 6 was launched which includes Netbeans 6.1, Glassfish v2 and OpenESB v2.
- In 2009, Java caps 6.2 version was launched with NetBeans IDE 6.5.1 and GlassFish Enterprise Server 2.1 patch 2. This version also introduced adapter for HL7 messaging.
- In 2010, Sun was acquired by Oracle and In 2011, Oracle releases Java CAPS 6.3 version which includes NetBeans IDE 6.9 and GlassFish Enterprise Server 2.1.1.
Suite components 
- ICAN 5.0 consists of following components:
- eGate Integrator,
- eInsight Business Process Manager,
- eVision Studio,
- ePortal Composer,
- eTL Integrator,
- eXchange Integrator,
- eView Studio,
- eIndex Global Identifier Compsite Application and
- eBAM Studio.
- Since Java CAPS 5, the suite comprises adapters, libraries and an IDE critical for designing, writing, monitoring and testing business processes, although, in practice, the principal ones are:
- Logicalhost: in charge of hosting the applications deployed in it. Until Java CAPS 5, the chosen server was the Sun Java System Application Server 9, and since the latest version, it became Glassfish to support JEE. Typically, the logicalhost runs on a dedicated machine (Solaris, OS Tiger, etc.) and when started, refers to a domain, which is an instance of the Sun Enterprise Service Bus.
- Repository: a version control system which allows shared projects, version history and file-lock capabilities. As expected, users can log-in to the repository and access and modify files contained in it.
- Enterprise designer: Enterprise designer is an Integrated development environment necessary to see the repository, create business processes, collaborations, connectivity maps and deployment profiles. Business processes here are meant to be made following BPEL. The standard of BPEL here is not tied specifically to web services as it is to execution of activities, its inputs/outputs and possible exceptions in the message flow.
- Enterprise manager: the web portal to monitor the information flow through the BPEL diagrams, server logs, activity details, business processes' parameters and data.
All components can be customized during installation although default options are recommended. One of the major features exposed by Java CAPS is its adapters; these adapters are JCA compliant and offer legacy system integration.
The latest release from Sun before its acquisition by Oracle is JCAPS 6.
JCaps 6 vs JCaps5 
JCAPS 6 has some distinct features when compared to JCAPS 5.1.x
- NetBeans 6.1 is used for Java CAPS IDE .Netbeans 6.1 has plugins to support the standard JCAPS 5.1.3 editors and it has a unified project view, editors for JCD, BPEL etc. and a runtime environment of IDE.
- Sun Java application server 9.1(Glassfish V2) is used as JCAPS runtime environment and its admin console can be used for management and administration of JCAPS runtime components.
- JCAPS 6 provides support for JBI. JBI has two types of component: Binding component(communication protocols) and SE service Engine(business logic). Both JBI container and EE container are in sun app server. JCAPS 6 provides interoperability between Java EE and JBI components via JBI bridge.
- JCAPS 6 support three types of messaging servers:
* JMS IQ manager(stcms),
* Java message service grid
* Java MQ4.1
- JCAPS 6 also provides supports for sub Java collaboration.
JCAPS 6 includes installation enhancement (wizard based JCAPS installer) and management and monitoring improvements.
Future of JCAPS 
As Sun was acquired by Oracle, Oracle experts incorporated features and functions of Sun SOA products to Oracle SOA products. Oracle offers migration tools which helps in migration of JCaps projects to Oracle SOA. The premier support of JCAPS 6.2 is unto Jan 2014, extended unto Jan 2017.
See also 
- Oracle SOA Suite
- SeeBeyond Technology Corporation
- Business Process Execution Language
- Java EE Connector Architecture
- Jcaps Version History by oracle
- JCaps blogspot
- SeeBeyond ICAN Suite Deployment Guide
- Java CAPS Basics - Implementing Common EAI Patterns; Chapter 10.2, Java CAPS Monitoring and Management
- Migrating from JCAPS to Oracle