Java CAPS Design Process Overview

Designing a repository-based Java CAPS project requires the following tasks:

• Start the necessary internal and external servers.

• Start the NetBeans IDE and open a new or existing CAPS project.

• Create, configure, and connect design elements.

• As needed, create business logic and orchestrate business processes, Collaborations, or page flows.

• Create a CAPS environment and deployment profile.

• Build the CAPS application, and then deploy and test it on an application server.

• As needed, bridge the CAPS application to JBI and combine it with other projects to create a composite application. Build the composite application and deploy/test it on an application server.

Java CAPS repository-based projects can include the following design elements, each with its own type of editor:

• Properties to be used for design-time components such as adapters, engines, and queues

• Properties to be used for runtime servers for external and internal systems

• Message libraries and object type definitions (OTDs) to model and encode data

• Java collaboration definitions (JCDs) to transform data

• Other data-transformation engines, such as for eTL collaborations or XSLT transformations

• Business processes (BPs) and page flows to implement business-logic rules and to orchestrate the execution of components and web services. Within Java CAPS projects, the editor uses Business Process Execution Language (BPEL) 1.0.

• Other specialized design elements, such as page layouts or cascading style sheets (CSSs)

• Connectivity maps (CMaps) to establish and configure connections between design-time components

• Deployment profiles (DPs) to assign engines, adapters, and queues with corresponding server resources

Composite applications can include the following additional design elements, each with its own type of editor:

• Properties to be used for Binding Components (BCs) and Service Engines (SEs)

• Business logic and orchestration. In the JBI container, composite applications use BPEL 2.0.

• Web Service Description Language (WSDL) elements with editable message definitions, port types, partner links, and so forth

• Composite Application Service Assembly (CASA) configurations between JBI module connections with WSDL ports and external modules