The Process Practice

Process engineering with the Eclipse Process Framework and Rational Method Composer

Entries Comments

Deploying RMC 7.2 and EPFC generated WAR files

12 September, 2007 (23:14) | Eclipse Process Framework, Rational Method Composer | By: Peter

The new IBM Rational Method Composer 7.2 and EPF Composer 1.2 add the capability to publish to a .war file in addition to publishing to local file system directories. Such .war files can be deployed to a JEE server and contain a Servlet that implements the Web Search function instead of the Java Applet that is used when publishing to a directory. Using the Servlet has a significant performance advantage over the Applet when deploying Composer sites to a web server. You can deploy to almost any JEE server on the market that realizes the Servlet 2.3 (or higher) specification and runs with a 1.4 or higher. My recommendation is to use the IBM Websphere server, but you could also use a free server such as Apache Tomcat.

I was asked by some Composer users that never set-up a JEE server for some simple instructions on how to test this feature. The easiest way to do this is to download and set-up the open source Apache Tomcat server and use its Management console to install the .war file.

Step 0: Publish the .war file from RMC or EPFC
To publish a .war file from Rational Method Composer 7.2 or EPF Composer 1.2 follow the instructions in the online help for publishing a configuration. On the last (fifth) page of the publication wizard you will be asked if you either want to publish a ‘Static Web site’ or a ‘Java EE Web application packaged in a WAR file’. Select the latter and tick the ‘Include search capability’ check box. Then provide a ‘Web application name’ such a ‘my-rup’ or ‘openup-company-abc’. This name will be used later in the address to your site, i.e. will be part of the URL such as ‘’. Also make sure you specified a valid directory at the top of the page. This is were the .war file will be placed by Composer after the publication is complete.

Step 1: Download and install a JRE and the Server
First you have to make sure that you have a Java runtime environment set-up. We currently recommend using version 5. Hence, if you do not already have Java installed on your machine download this JRE from IBM (only runs on IBM systems) or this one from Sun.

Go to the Apache Tomcat homepage ( and download the core package for your operation system (e.g. this one for Windows). Unzip the archive wherever you want your server to be located on your machine. This directory is referred to as <tomcat> below.

Step 2: Set-up and start the server
Before you can start the server you need to do some basic set-up. It would be safest to read and follow the instruction in the ‘RUNNING.txt’ file in the Tomcat top-level directory <tomcat>\. The key thing described in here is that you need to tell Tomcat were it can find the Java runtime environment by defining an environment variable named $JAVA_HOME. There are several ways of doing that. (1) You could create a .bat file that contains the line ‘SET JAVA_HOME=<path>’ (replace <path> with the directory where you installed the JRE, e.g. ‘C:\Program Files\Java\jre1.5.0_12’) that you run from a CMD shell (Start->Run…->cmd) just before you run the server. (2) You could also define this variable globally on your Windows computer by right-clicking ‘My Computer’->Properties->Advanced->Environment Variables. (3) Another possibility is to directly add this line at the beginning of the file <tomcat>\bin\catalina.bat using Notepad.

Second thing you should set-up is an admin user so that you can use the management functions of Tomcat. To do that open the <tomcat>\conf\tomcat-users.xml file in a text editor such as Notepad. Make the following changes:

<?xml version='1.0' encoding='utf-8'?>
<role rolename="manager"/>
<user username="admin" password="admin" roles="manager"/>

You can select any username and password you want, but make sure that the user has the role ‘manager’.

Now you are ready to start the server. Depending on how you set-up your $JAVA_HOME variable either double-click the ‘startup.bat’ file in <tomcat>\bin\ (if you followed method (2) and (3)) or use a CMD shell to start it (if you followed method (1)). A new shell window will open and display various startup messages. Once, you read the message ‘INFO: Server startup in 2753 ms’ (with a similar time) you are ready to go.

Step 3: Install the the .war file
(I demonstrate the following steps in the ‘New and noteworthy in EPF Composer 1.2‘ video as well.)

Now start a Web browser and type the URL ‘http://localhost:8080’. This one should take your to the Tomcat start page. On the left click on the link labeled ‘Tomcat Manager’ in the Administration section. You will be prompted to provide the user name and password that you specified in the tomcat-user.xml file.

Once you are on the ‘Tomcat Web Application Manager’ scroll down to the ‘WAR file to deploy’ section and use the browse button to navigate to the .war that you created in Step 0. You find it in the directory that you specified on the last page of the publication wizard. Click on the Deploy button and wait for the operation to finish.

Step 4: Test your site and Search
Now you see you application listed in the Applications section above. The application name is the one that you specified in Composer’s publication wizard. Click on the name and it will take you to your site.

On your site try using the ‘Search’ and see if it works correctly. An EPF Composer published site will open a new window with the search results. RMC generated sites display the results in a nice looking panel on the right hand side of the same browser page.

I hope that these instructions worked for you. Check out the Tomcat documentation for more advanced set-up instructions. For example, you can run the server as a service that starts automatically when your systems starts as well.


Pingback from Vydanie Rational Method Composer v7.2 « ján masaryk
Time: November 26, 2007, 7:48 am

[…] návod na nasadenie generovaného súboru .war v RMC v7.2 na J2EE server (použiteľný aj na EPFC 1.2) […]

Write a comment