RADE

Before Starting

Before starting, install the JID product provided on the RADE CD. Make sure that IBM Rational Software Development Platform has previously been installed on the machine because the RADE installation detects it and installs the JAVA Interactive Dashboard within the IBM Rational Software Development Platform environment. If you install IBM Rational Software Development Platform after JID, launch manually the Setup tool provided with RADE. Refer to [1] for more information on the Setup tool.

Once the JAVA Interactive Dashboard has been installed for IBM Rational Software Development Platform, you can start IBM Rational Software Development Platform. If the CAA Project menu is not available in your JAVA Perspective, customize IBM Rational Software Development Platform to make it available, as described in [2].

[Top]

Creating a Web Project in IBM Rational Software Development Platform and Opening it as a CAA V5 Workspace

1. From the File menu, select New->Project. The New Project window opens.
2. Expand the Web node and select Dynamic Web Project. Click Next. The New Dynamic Web Project window opens.
3. Enter the project name and click Browse in the Project location field to change the location if different from the default location.
4. In the Servlet version combo box, select 2.4. Click Show Advanced.
5. In the Target server combo box, select Websphere Application Server.
6. Select the DefaultEAR if different from the default one.
7. Do not modify the Context root.
8. Click Finish.

The new web project is created. Open it as a CAAV5 Workspace:

1. Right-click the new web project in the Navigator View and select Open CAAV5 Workspace from the contextual menu. The Open CAAV5 Workspace dialog box opens.
2. In the Open with combo box, select Mkmk. The Workspace directory is already valuated.
3. Select the tool level in the Tool Level combo box. Click OK when done.

[Top]

Retrieving a Use Case in IBM Rational Software Development Platform

1. From the CAA Project menu, select Copy Framework... The Copy Framework dialog box opens.
2. In the Reference WS list where FW are searched for field, click Add to add the origin directory of the framework containing your use case (ex: CAA_install_dir\CAADoc).
3. Enter the name of the framework to be copied, containing the use case (ex: CAAJDialog.edu) or click the ... button to select it.
4. Check at least the 2 copy options Module directories copied and Copy Data directories and click OK when done.

[Top]

Defining a Build Environment and Building the Use Case

1. Right-click the web project in the Navigator view, and select Run->Run on server from the contextual menu. The Server Selection window opens.
2. If you already have an existing server as Websphere v6.0 Test Environment, you can use this one. If not, you need to Create a new server and select Websphere version/ Test Environment.
3. From the CAA Project menu, select Update/Generate Source Folders..., and check the module containing the use case in the Select Java module to update Eclipse project source folders. Click OK when done.
4. From the CAA Project menu, select Get Prerequisites... to define you build prerequisites.
5. In the Prerequisites window, select the Access prerequisites from their origin location access mode.
6. Click Add to add the CAA installation directory in the Origin for prerequisites frameworks field. Click OK when done.

The java source of your use case should be automatically built. But you can also build it using the mkmk tool. To do so, from the CAA Project menu, select Mkmk...

7. Select you module directory containing the use case, and select at least the option Update makefiles (-u). Click OK when done.
8. Now that the use case is successfully built, create your runtime view before testing the use case execution. To do so, from the CAA Project menu, select Create /Update Runtime View... Do not modify the default options, and click OK.

[Top]

Testing the Use Case in a Websphere Test Server

If the Websphere Test Server is running, stop it, republish it and restart.

There are two ways to test the use case. You can run it inside IRAD itself, or through a simple Internet explorer browser:

1. Inside IRAD:

Go in the Server perspective and enter the following URL in the Web Browser:

http://localhost:9080/your_webproject_name/html/xmldlg_use_case_name

where xmldlg_use_case_name is the name of the XMLDlg file associated with your JDialog use case, without extension.

Example: http://localhost:9080/MyWebProject/html/SmartDictionary1

2. With Internet Explorer: Enter the same URL

Deploying the Use Case in a Websphere Application Server

Once your use case is running correctly in a Websphere Test Server in IRAD, you can deploy it in a WAS for production.

Prerequisites for this step are:

• You have a WAS 6.0.2 installation on your machine
• You have IBM db2 on your machine
• You have a 3dcom installation on your machine

All mandatory steps are described in the following documentation: 3dcom Installation guide / Installing Version 5 / Integrating Modular 3d com into IBM Websphere Application Server

In short, mandatory steps are:

• Creating a DB2 Database for Settings Persistency (to do only at the first Application deployment).
• Creating a DB2 Data Source in the Websphere Application Server (to do only at the first Application deployment).
• Generating and Deploying a 3d com Web Application in a WebSphere Application Server (For this step, there is only one difference, while using the WASSetupUI command. The difference is that you need to specify a concatenation of 2 directories in the Source tab page: enter first the runtimeview directory of your workspace containing the JDialog UseCase, and then the runtimeview directory of the 3dcom installation (ex: e:\3dcom\B14\intel_a). Note that the order of the 2 runtimeviews is important (your workspace must be before the 3dcom installation). This order can the changed with Up and Down buttons.

Executing the Use Case in Websphere Application Server

• Start the Application Server from the administrative console.
• Open Internet Explorer and enter the following URL:

  http://machine_name:port_number/rootURI_for_the_Application/html/xmldlg_use_case_name

  where xmldlg_use_case_name is the name of the XMLDlg file associated with your JDialog use case, without typing the extension.

[Top]

References

History

Copyright © 2006, Dassault Systèmes. All rights reserved.