216 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
– jms.UserName, if the WebSphere MQ provider is remote, you need to
enter the user name that has access to the queue manager.
– jms.Password, if the WebSphere MQ provider is remote, you need to
enter the password for the user that has access to the queue manager.
– MessageFileName, which is JDBCConnector.txt.
2. On the Connector Specific tab, enter the following:
– ApplicationUserName, database user
– ApplicationPassword, database password
– CheckForEventTableInInit, false
– DatabaseURL, jdbc:db2:stocksys
– JDBCDriverClass, COM.ibm.db2.jdbc.app.DB2Driver
– RDBMSVendor, DB2
– EventTableName, null
3. On the Supported Business Objects tab, add the STOCKINFO business
object.
4. Save the configuration to the project by pressing Ctrl+S.
5. Save a copy of the configuration to a file, to be used to run the JDBC Adapter
later on, by pressing Ctrl+Alt+F. Save the file to the filename
C:ITFJDBCAdapter.cfg.
Configure the JDBC adapter start script
Now, you configure the start script to find the driver that is required to connect to
the DB2 database.
1. Right-click the start_JDBC.bat file found in the default JDBC directory,
C:IBMWebSphereconnectorsJDBC.
2. Click Edit to edit the file.
3. Modify the JDBCDRIVERPATH variable in the script to include the
<db2install>javadb2java.zip file.
4. Add a new variable JDBCDRIVERLIB to include the <db2install>in
directory.
5. Set the JDBCDRIVERLIB as the last value in the -Djava.library.path JVM
argument at the end of the script.
Chapter 8. Integration using WebSphere Business Integration Adapters 217
Example 8-3 shows the changes made to the start script.
Example 8-3 JDBC Start Script Variables
set JDBCDRIVERPATH=”C:Program FilesIBMSQLLIBjavadb2java.zip”
set JDBCDRIVERLIB=”C:Program FilesIBMSQLLIBbin”
%CWJAVA% ... ... -Djava.library.path=%MQ_LIB%..%JDBCDRIVERLIB%
6. Save the file by pressing Ctl+S.
8.5.4 Building and exporting the adapter project
In this step, you update the WebSphere Application Server project with the
connector and the business object integration component libraries. Then, you
export the project as a service with a JMS binding, to be incorporated in a service
project in WebSphere Studio Application Developer Integration Edition.
First, you update the JDBCAdapter WebSphere Application Server project by
importing the ICL components.
1. Right-click the JDBCAdapter WebSphere Application Server project and
click Update Project. Select JDBCAdapter from the connectors folder and
the STOCKINFO business object.
Figure 8-10 on page 218 shows the update of WebSphere Application Server
project with selected components.
Note: For WebSphere Business Integration Adapter for JDBC Version 2.6.0 or
later, you can use the LIBPATH variable in the script to set the
JDBCDRIVERLIB. You should use this variable instead of creating a new one
for this feature and property.
218 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
Figure 8-10 Update application server project using ICL project
2. Click Finish to update the project.
The WebSphere Application Server project now has all the business objects
and connectors included.
Figure 8-11 on page 219 is a view of the system manager after this step. The
WebSphere Application Server project now shows the business objects and
the connector configuration.
Chapter 8. Integration using WebSphere Business Integration Adapters 219
Figure 8-11 The JDBCAdapter WebSphere Application Server project updated
3. You now deploy the JDBCAdapter project as a WebSphere Application
Server project to create the service WSDL and bindings and to define the
business object in a XML schema document (XSD).
220 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
Figure 8-12 shows the deploy WebSphere Application Server project wizard.
Figure 8-12 Deploy JDBCAdapter WebSphere Application Server project
4. Right-click the JDBCAdapter folder in the WebSphere Application Server
project. Click Deploy WAS Project. Ensure that the JDBCAdapter connector
and the STOCKINFO business object are shown. Click Next.
5. Select Export to a Directory. Choose a folder to place the project in by
clicking the Browse button. Click Finish.
Note: The connector configuration shows only supported business objects. If
no business objects appear or if not all the business objects appear, you need
to add them. You can open the configuration, using the WebSphere Business
Integration Connector Configurator, by double-clicking the JDBC adapter in
the connectors folder. Then navigate to the supported business objects tab
and add the business object. Only business objects saved in the ICL project
will appear.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset