Application logic layer components

This section describes the components in the new application logic layer. These components operate within the EJB container in WebSphere(R) Application Server.

Business Process Component
This component prepares the data for a business process running in the Process Choreographer of WebSphere Business Integration Server Foundation and creates the response once the process flow has finished. WebSphere Studio Application Developer Integration Edition provides the Process Editor as a visual tool to facilitate in creating business processes. To reduce migration effort, the Business Process Component provides com.ibm.btt.server.flow.BTTOperActivity and BTTOperStepActivity. These classes replace DSEServerOperation and OperationStep.
Single Action EJBs
These are EJBs that perform business processes. They are functionally equivalent to business processes running in the Process Choreographer except that they can run on any edition on WebSphere Application Server and have better performance.
Startup beans
These do the initialization for the application logic layer components such as the CHA, CHA Formatter Service, and application logic layer services.
Communication services
These services support communication with back-end enterprise systems through the JCA. The toolkit provides the SNA JCA Lu0 and the SNA JCA Lu62 Connector as resource adapters that conform to the JCA standard. The SNA JCA Lu62 Connector is new to the toolkit.
Database services
The database services exist in the application logic layer and follow its architecture. The toolkit provides the Electronic Journal and Database Table Mapping services.

In the Electronic Journal, the JDBCJournal is the service requester and maintains the same API as it did in the previous version. Note that because WebSphere Application Server now handles the connection to the database, JDBCJournal no longer needs to get, set, or load the JDBC driver. The JDBCJournal communicates with the service object JDBCJournalImpl using local Java(TM) calls, EJB method calls, WSIF SOAP binding messages, or WSIF EJB binding messages. The service object has the task of accessing the database to perform the request sent to it by the requester.

Because the schema generator JDBCJournalSchemaGenerator and the JDBC driver must be in the same JVM, the Electronic Journal no longer allows an application to call the generator to create the tables. Instead, the database administrator uses the generator to create the tables so that they are available when the application starts.

In the Database Table Mapping service, the JDBCTable is the service requester and maintains the same API as it did in the previous version. Note that because WebSphere Application Server now handles the connection to the database, JDBCTable no longer needs to get, set, or load the JDBC driver. The JDBCTable communicates with the service object JDBCTableImpl using a WSIF interface. The service object has the task of accessing the database to perform the request sent to it by the requester.

With the new implementation, the externalizer for the service ignores the following attributes in the service definition:

  • databaseURL
  • JDBCDriver
  • poolName
  • sharedConnection
  • statementPoolSize

The JDBCServicesConnectionManager has the following new attributes:

  • orphanTimeout - the number of seconds that passes before the JDBCServicesConnectionManager discards an unused or idle connection.
  • reapTime -  the number of seconds that passes between runs of the pool maintenance thread.