282 Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator
Using the Web material
The additional Web material that accompanies this redbook includes the
File name Description
SG246875.zip The sample application and configuration instructions
System requirements for downloading the Web material
The following system configuration is recommended:
Hard disk space: 5MB for the code
Operating System: Windows 2000 Server with Service Pack 3
Processor: 1 GHz or higher
Memory:1 GB or more
How to use the Web material
Create a subdirectory (folder) on your workstation, and unzip the contents of the
Web material zip file into this folder. The contents of the .zip file are organized in
directories, you will find further instructions about installing and configuring the
application in Chapter 11, “Technical scenarios” on page 227.
Load the application into WebSphere Studio
The workspace for WebSphere Studio is packaged in the downloadable .zip file,
unzip the file to a directory, for example:
You will find the
install directory after unpacking the .zip file, open the index.html
under this directory to get detailed information about the development and
runtime environment configuration.
The development environment requires the following configuration steps in order
1. Start WebSphere Studio with the following command:
wsappdev -data C:\SG246875\Resources\Workspace
The directory is where the workspace for the project can be found.
Note: If you do not want to configure everything step-by-step, you can use the
scripts, with some modifications from the runtime environment configuration
Appendix A. Additional material 283
2. Select Window -> Preferences -> Java -> Classpath Variables, then create
a new variable with the name MQ_JAVA and the path
3. Import the projects to the workspace. Select
File -> Import -> Existing
Project into Workspace
. Click Next.
Browse next to the Project Contents field, then select the
CommonUtility folder under the workspace directory
6. Repeat steps 3 and 4 with the following projects:
7. After importing all existing projects, select
Project -> Rebuild All from the
menu. At the very end you should see only four warnings under the Tasks
view. If there are more, make sure that all the projects are imported.
8. Regenerate the deployed code for the EJBs. On the J2EE perspective, J2EE
Hierarchy view select
EJB Modules -> VendorBackEndEJB. Right-click the
item and select
Deploy and RMIC code...
9. On the next window click Select all, which selects all the EJBs, then click
Finish to generate the code.
10.Check the Tasks view to see if there is any error. There should be only four
warnings. If you find one or more, make sure you fix them before you
11.The application assumes that your Web application can be found at the
http://localhost:9080/ivcorp URL. If that is not the case you have to modify an
XSL file accordingly and re-compile the translets belonging to this XSL.
a. Open the ProcessOrderReply.xsl file from the VendorFrontEndUtility -> xsl
b. Change the http://localhost:9080/ivcorp/catalog/catalog.xml in the file
according to your environment.
There are two places in the file where you can find this string! This string
tells the style sheet where it can find the catalog.xml file to build the
284 Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator
catalog for the presentation. If you have the .xml file at another URL, for
example under an HTTP server, you can also use that URL.
c. Also change the URL in the file. Click
, and look for the CATALOG_URI
d. Delete the frontendtranslets.jar file from the VendorFrontEnd folder.
File -> New -> Other from the menu, then select XML -> Compile
. Click Next.
f. Provide the following information for the compiler:
Destination folder: /VendorFrontEnd
Java package: com.ibm.itso.msgtrx.frontend.translets
Jar file name: frontendtranslets.jar
12.Follow the steps from the configuration guide distributed in HTML format
together with the sample application.
13.5.1 Supplier application configuration
The following is a sample .xml configuration file for the supplier application.
Example: A-1 supplier-conf.xml
<?xml version="1.0" encoding="UTF-8"?>
<supplier-entity name="Red supplier">
<supplier-entity name="Green supplier">
<supplier-entity name="Blue supplier">