Publishing Studio Samples to WebSphere Application Server 3.0

Studio 3.x includes an extensive set of samples that you can publish to:

But, WebSphere Application Server Version 3 also has a similar set of samples. In fact many of them are identical to those in Studio.

This document describes:

The differences between the two sets of WebSphere samples

What happens if you publish the Studio samples using the default settings

How to avoid publishing the Studio samples over the Application Server samples

 

What are the differences between the WebSphere Studio samples and the Application Server 3.0 samples?

The majority of the samples are exactly the same. Studio includes the Banner sample for Applet Designer that does not come with either version of the Application Server. The Application Server includes samples for its newest features that you will not find in Studio: Auto Translation, Connection Pooling, Site Outliner for XML, and the User Profile class. And, the Application Server Advanced Edition has additional samples that demonstrate its Enterprise JavaBean (EJB) support.

 

Sample
Studio
App. Server Standard
App. Server Advanced
Auto Translation  
X
X
Banner
X
Connection Pooling
X
X
Database Setup
X
X
X
Enterprise Beans (EJB)
X
Expiring page
X
X
X
Feedback
X
X
X
Form
X
X
X
Page Hit Counter
X
X
X
Poll
X
X
X
Quote of the Day
X
X
X
Selection Box
X
X
X
Site Outliner
X
X
Survey
X
X
X
User Profile
X
X
YourCo Employee Center
X
X
X
YourCo TimeOut (EJB)
X

 

What happens if you publish the Studio samples using the default settings?

When you install WebSphere Application Server Version 3, the sample .class and .servlet files are put in the \WebSphere\AppServer\hosts\default_host\default_app\servlets directory. And, the HTML, JSP, and other files are put in the \WebSphere\AppServer directory and then copied to the document root directory of your Web server.

Typically, the default publishing targets in Studio point to these same (or equivalent) directories. For example, these might be the default publishing targets for a WebSphere Application Server and Domino Go Webserver on Windows NT:

html d:\www\html
servlet d:\WebSphere\ AppServer\servlets

It is important to remember that Version 3 of the Application Server treats the \WebSphere\ AppServer\servlets directory and the \WebSphere\AppServer\hosts\default_host\default_app\servlets directory as equivalent. When a request comes in, it searches both directories and serves which ever file it finds first.

When you publish the Studio sample projects using the Studio's default publishing targets to Version 3 of the WebSphere Application Server, the Studio samples will replace the WebSphere Application Server samples that have the same name.

Usually, because the Application Server and Studio versions of these samples are identical, this is not a concern. But, if you decide to modify either the Application Server or the Studio samples, this might be a problem.

How to avoid publishing the Studio samples over the Application Server Version 3 samples

The best way to keep the Studio 3x samples separate from the Application Server Version 3 samples is to publish them using the new Application Server's new web application model.

See the article on this Web site that explains how to publish Studio projects as Web applications. Follow the directions in the article, but because these samples were developed as a JSP .91 application, be sure to do make the following important choices:

Make these same choices every time you publish a Studio project that was developed for Application Server Version 2.0x with JSP .91 as a Web application on WebSphere Application Server Version 3.