This section describes the components in the new application logic layer. These components operate within the EJB container in WebSphere(R) Application Server.
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:
The JDBCServicesConnectionManager has the following new attributes: