Creating an EAR file with Build Tool’s Assemble feature targeting Web View textually compresses static files, such as HTML, CSS, and JavaScript files. If these files are generated, they are compressed during the assemble process in Build Tool. If these files are delivered, these have been already compressed in advance.
However, in some cases, it is necessary to leave the files uncompressed. The OPT.DEBUG token in the Build Tool profile controls the behavior. When OPT.DEBUG is set to ‘YES’, all textual compression is disabled and the pre-packaged non-debug Web View JavaScript files, WebViewUI_Debug.zip file, and the debug version of YUI library files are packaged into the assembled EAR file.
To be able to run a Web View application, you need to first assemble and then deploy it to an Application Server. You can deploy a Web View application to the following Application Servers:
Follow these steps:
The EAR File Assemble Details dialog opens.
The Application Server specific settings appear.
The EAR file is stored in the following location:
\\<model directory>\java\deploy.j2ee
|
Copyright © 2013 CA.
All rights reserved.
|
|