WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Chapter 20. Features for application development and deployment 741

20.2 Integrated standards-base programming models and

extensions

Many of the core programming models in WebSphere Application Server V8.5 were available

through feature packs in Versions 7.0 and 8.0. Now, these programming models are built into

WebSphere Application Server V8.5. This section describes the available programming

models:

 Session Initiation Protocol applications

 WebSphere Batch programming model

 OSGi applications programming model

 Communications enabled applications

 Service Component Architecture programming model

 Extensible Markup Language programming model

 Integrated Web Services support

 Support for integrated IBM WebSphere Application Server Web 2.0 and Mobile Toolkit

 Simplified development of server-side REST applications using Java API for RESTful Web

Services

 IBM WebSphere SDK Java Technology Edition Version 7.0

20.2.1 Session Initiation Protocol applications

Session Initiation Protocol (SIP) applications are Java programs that use at least one SIP

servlet written to the JSR 116 specification. WebSphere Application Server V8.5 also

supports SIP Servlet Specification 1.1, also referred to as JSR 289. SIP is used to establish,

modify, and terminate multimedia IP sessions. SIP negotiates the medium, the transport, and

the encoding for the call. After the SIP call is established, the communication takes place over

the specified transport mechanism, independent of SIP. Examples of application types that

use SIP are voice over IP (VOIP), click-to-call, and instant messaging.

Session Initiation Protocol (SIP) applications are packaged as SIP archive (SAR) files, and

are deployed to the application server using the standard WebSphere Application Server

administrative tools. SAR files can also be bundled in a Java EE application archive (EAR

file), similar to other Java EE components.

In the application server, the web container and SIP container are converged and are able to

share session management, security, and other attributes. High availability of these

converged applications is made possible because of the integration of HTTP and SIP in the

base application server. For more information about SIP applications, see the following

resources:

 JSR 289 SIP Servlet API 1.1 Specification, found at the following website:

http://www.jcp.org/aboutJava/communityprocess/final/jsr289/index.html

 JSR 116, found at the following website:

http://jcp.org/en/jsr/detail?id=116

 RFC 3261, found at the following website:

http://www.ietf.org/rfc/rfc3261.txt

742 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

20.2.2 WebSphere Batch programming model

WebSphere Batch provides a transactional batch programming model (large number of small

and repetitive operations) and a compute-intensive programming model (small number of

CPU/Memory intensive operations). Both the transactional batch and compute-intensive

programming models are implemented as Java objects. They run as background jobs,

described by a job control language and are supported by infrastructure components that aim

to support batch workloads.

The control language for batch jobs is called XML job control language (xJCL). The xJCL

allows users to describe the job steps involved in a batch job. The application runs in batch

containers that run in designated WebSphere Application Server environments. The batch

container ultimately processes a job definition and carries out the lifecycle of a job.

Figure 20-1 shows a typical batch container.

Figure 20-1 Batch container

The batch container provides the following services:

 Checkpointing, which involves resuming batch work from a selected position.

 Result processing, which involves intercepting and processing step and job return codes.

 Batch data stream management, which involves reading, positioning, and repositioning

data streams to files, relational databases, native z/OS data sets, and many other different

types of input and output resources.

WebSphere

Application Server

WebSphere

Application Server

Batch

container

Java EE

Batch

application

JDBC

Scheduler tables

Container tables

Batch

applications

Classes

and APIs

xJCL

Job

scheduler

JDBC