ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Does the Update jar create or only update the EAR file
Article ID: 126177
Output Management Document ViewerOutput Management Web Viewer
Upgrading Web Viewer (build 158 to build 191) and running the install process in OMVS. Issued the java -jar CA_OM_WEBVIEWER_12_1_Updt.jar command. Does this command create an EAR file or does it only update and existing one? Normally there is a CAOMWebViewer12.ear in our deployable directory but on one specific lpar it did not exist and was not created. Please clarify.
What is the difference between WAR files and EAR files from the 12.1 Web Viewer perspective?
Release: Component: WBVLUW
Wikipedia says: A WAR file (Web Application Resource or Web application ARchive) is a file used to distribute a collection of JAR-files, JavaServer Pages, Java Servlets, Java classes, XML files, tag libraries, static web pages (HTML and related files) and other resources that together constitute a web application.
An EAR file (Enterprise Archive) is a standard JAR file (and therefore a Zip file) with a .ear extension, with one or more entries representing the modules of the application, and a metadata directory called META-INF which contains one or more deployment descriptors.
Basically, EAR files are a superset containing WAR files and JAR files. Java Application Servers allow deployment of standalone web modules in a WAR file, though internally, they create EAR files as a wrapper around WAR files. Standalone web containers such as Tomcat do not support EAR files ― these are not full-fledged Application servers. Web applications in these containers are to be deployed as WAR files only. So from a CA / Broadcom 12.1 Web Viewer perspective, it installs/updates from WAR or EAR files depending upon which WAS (Web Application Server) hosts - EAR files are used for WebSphere and WAR files are used with Tomcat.
Customer did find the log and the previous log. The previous log shows they used the war file. We now suspect the Web Viewer on the problem LPAR was running under Tomcat. He OK'd closing the case. He will work with his WebSphere team to move forward.