PQ67662: UPDATE J2EECLIENT_NT.ZIP TO INCLUDE MISSING CLASSES. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description There are classes missing in J2EEClient_NT.zip that need to be included and shipped with these files in order for NT clients to run correctly.Local fix Another option to running remote clients is to use the Java Technology Client. Obtain an updated copy of the Java Technology Client from the WebSphere for z/OS downloads page and install it on the workstation.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: The J2EE Application Client install * * image (J2EEClient_NT.zip) is missing * * several components (classes) needed * * for proper functionality and * * serviceability. * **************************************************************** * RECOMMENDATION: * **************************************************************** The J2EE Application Client install image (J2EEClient_NT.zip) is missing several components (classes) needed for proper functionality and serviceability. One of the reported symptoms of using the currently available J2EE Application Client install image is receiving the exception: ERROR: java.rmi.MarshalException: CORBA MARSHAL 0 No; nested exception is: org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : Mismatched serialization UIDsProblem conclusion The J2EE Application Client has been upgraded such that it can be serviced via the support available through the main WebSphere Application Server support website found at: http://www.ibm.com/software/webservers/appserv/support/ Once at this website the latest service can be located by selecting "All e-fixes, fixpaks, and tools" under Software downloads. Locate the most current WebSphere Application Server Version 4.0 FixPak maintenance available from the choices. At the closure of APAR PQ67662, WebSphere Application Server Version 4.0 FixPak 5 (Version 4.0.5) was the most current FixPak available. After installing the version of the J2EE Application Client provided by APAR PQ67662, the customer must download the latest service pack from the above website and apply it to the J2EE Application Client to ensure all the lastest bug fixes are included. Also, APAR PQ67662 ships the WebSphere for z/OS Java Technology Client. Previous to APAR PQ67662, the WebSphere for z/OS Java Technology Client was available from the WebSphere Application Server support website found at: http://www.ibm.com/software/webservers/appserv/zos_os390/ support.html Coinciding with APAR PQ67662, the website version of the Java Technology Client will be deleted from this website. All future servicing of the WebSphere for z/OS Java Technology Client will be through WebSphere Application Server V4.0.1 for z/OS and OS/390 APARs/PTFs. This APAR requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/ WebSphere Application Server V4.0.1 for z/OS and OS/390 Assembling J2EE Applications (SA22-7836-05) will be changed as follows: Chapter 9. Creating and running WebSphere for z/OS client applications Update the introduction on page 185 as follows: Once you have installed application components in a J2EE server, you are ready to create WebSphere for z/OS client applications that use those components. Figure 1 on page 4 illustrates the most likely types of client applications for components that run in a J2EE server: * Application clients that run only on non-z/OS or non-OS/390 platforms, such as Windows 2000. These application clients are specific module types defined in the Sun Microsystems J2EE specification: * J2EE application clients, which access Enterprise beans, JDBC databases and other resources, and depend on an application client run-time to configure its execution environment. * Java thin application clients, which use a light-weight Java client programming model. This type of client is best suited for use in situations where a Java client application exists but the application must be enhanced to make use of Enterprise beans, or where the client application requires a thinner, more light-weight environment than the one offered by the J2EE application client. * RMI clients that run on z/OS or OS/390. These Java programs have full access to J2EE application components installed in WebSphere for z/OS J2EE servers, but lack access to the java:comp JNDI namespace. In the first table on page 185, in the left column, second row, change "J2EE application clients..." to "Application clients." Update the topic "J2EE application clients" on page 185 as follows: Application clients that run on non-z/OS platforms Application clients that run on non-z/OS and non-OS/390 platforms can be the following specific module types defined in the Sun Microsystems J2EE specification: * J2EE application clients * Java thin application clients Although these clients cannot run on the z/OS or OS/390 platform, they can access J2EE application components (Enterprise beans or Web applications) that run in a WebSphere for z/OS J2EE server. Depending on the platform on which you plan to run these application clients, you need the following software: If your J2EE application Then you need this clients will run on this additional software: type of workstation: Windows NT or Windows 2000 You need to download one of the following z/OS packages: * WebSphere J2EE Client for NT * WebSphere Java Technology Client See "Steps for running application clients on Windows NT or Windows 2000" on page 186 for instructions. Update the topic "Steps for running J2EE application clients on Windows NT or Windows 2000" on page 186 as follows: Perform the following steps to prepare and run an application client on Windows: 1. Install the appropriate client package by downloading the following files from the WebSphere for z/OS HFS into a working directory on your workstation: * For J2EE application clients, download the WebSphere for z/OS J2EE Client for NT (J2EEClient_NT.zip). Unzip the file on your workstation. * For Java thin application clients, download the WebSphere for z/OS Java Technology Client (JavaTechnologyClient_setup.exe) The default HFS location for these packages is /usr/lpp/WebSphere/bin/ Once the files are on your workstation, run the setup.exe file. Tip: Always make sure you have the latest service for these WebSphere for z/OS packages by checking the Support Web site http://www.ibm.com/software/webservers/appserv/support.html The remainder of this topic is unchanged, with the exception of replacing references to "J2EE application clients" with "application clients." APAR PQ67662 is associated with SERVICE LEVEL W401407 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
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: 401
Software edition:
Reference #: PQ67662
IBM Group: Software Group
Modified date: Feb 5, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.