Re: deploying .war file to /htdocs -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: deploying .war file to /htdocs
From: Vern Hamberg <vhamberg@xxxxxxxxxxx>
Date: Fri, 05 Nov 2010 16:57:18 -0500
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Are you creating a simple apache server? Are you creating a WAS server? do you have tomcat running? Apache by itself won't serve war files without an application server in the middle of things.

On 11/5/2010 3:48 PM, Booth Martin wrote:

I created a new server, using the defaults, with

http://123.456.789.1:2001/HTTPAdmin

I used port 80.

I can enter

http://123.456.789.8/

and I see the expected sample web page.

I expected to be able to:

ftp a .war file and then be able to reach the .war file but I get 403
Forbidden by rule.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.