PQ52281: PROBLEM WHEN APPLICATION HAS VIRTUAL HOSTNAME BINDING | |||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||
APAR status Closed as fixed if next. Error description Applications can have a virtual hostname binding coded in the EAR file. This causes problems in the WAS 4.0 390 environment. The value can be viewed/modified in the AAT supplied with WAS4.0 distributed. It is not available on the z/OS version of AAT. Since WebSphere 4.0 for z/OS honors the value, the AAT tool for that platform display the value. View the hostname binding using the AAT tool associated with the distributed version of WebSphere. There is an alternate way to bind web apps to virtual hosts by the use of a property in the web container's configuration file.Local fix See description for local fix.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: WebApplications being deployed onto * * WebSphere V4.0 for Distributed supports * * a virtual hostname binding during * * Application Assembly via WebSphere V4.0 * * for Distributed AAT. Whereas, WebSphere * * V4.0 for z/OS's AAT does not. There * * needs to be similar capability within * * WebSphere V4.0 for z/OS's AAT to allow * * modification of virtual hostname * * binding information for each * * WebApplications during Application * * Assembly. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere for z/OS supports virtual hostname for WebApplications only through webcontainer.conf (webcontainer configuration file) for each J2EE application server instances. As AAT for WebSphere V4.0 Distributed supports view/modify of this value, WebSphere V4.0 for z/OS should provide the same capability without limitation on the length of the classpath requiring users from having to modify webcontainer.conf separately.Problem conclusion Temporary fix Comments This APAR is being closed FIN with concurrence from the submitting customer. A solution to this problem will be delivered in a WebSphere Application Server for z/OS and OS/390 release within the next 18 months.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ52281
IBM Group: Software Group
Modified date: Sep 18, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.