|
|
United States-English | |
|
|
 |
|
 HP OpenVMS SystemsSecure Web Browser (based on SeaMonkey) |
|
HP Secure Web Browser for OpenVMS Alpha (based on SeaMonkey) Installation Guide and Release Notes
February 2009
Secure Web Browser V1.1-12 for OpenVMS Alpha
Contents
Before Installing the Secure Web Browser
Installing the Secure Web Browser
Running the Secure Web Browser
Known Problems and Restrictions
Before Installing the Secure Web Browser The HP Secure Web Browser for OpenVMS is available on Integrity servers and Alpha platform. If you encounter color problems when running the Secure Web Browser on an 8-plane video mode system, it is likely that you are running another application that uses a large number of colors (Navigator V3 is such an application). In this situation, start the Secure Web Browser before you start the other application. These problems usually do not occur on a 16 or 24-plane video mode system. The HP Secure Web Browser for OpenVMS Alpha compressed self-extracting archive contains 80,511 blocks. The expanded PCSI kit requires an additional 150,000 blocks of working disk space to install. For HP Secure Web Browser (SWB), based on SeaMonkey, the minimum memory requirement is 256 MB. However, 512 MB is highly recommended for more robust performance. The following software is required in order to successfully run the Secure Web Browser:
The Secure Web Browser has been tested and verified using HP TCP/IP Services for OpenVMS. HP has not formally tested and verified other TCP/IP network products, including the following TCP/IP network products from Process Software Corporation: TCPware Version 5.6 Important: The Secure Web Browser requires that local files be in Stream_LF record format. Files of other record formats are not supported and the results of attempting to use any such file is undefined. If you are using Java via the Java Development Kit (JDK) for the OpenVMS Operating System, for the Java™ Platform with the Secure Web Browser, you should add the PGFLQUOTA required for JDK to the Secure Web Browser requirement to obtain a total number. Do the same for the FILLM requirement. It is the total numbers that you must set in your SYSUAF entry. The current JDK PGFLQUOTA requirement is 2,000,000. The current JDK FILLM requirement is 4,000. See the JDK for the OpenVMS Operating System, for the Java™ Platform documentation website for more information.
If you use the supplied INSTALL.COM to install the Secure Web Browser images, the default FILLM of 100 is sufficient. See The FAQ section - insufficient resources for operation error for information about setting the amount of virtual memory available to your DECwindows X server process. The Secure Web Browser requires a relatively large number of process sections, so you may find that you have an insufficient number. (Note: If you install the Secure Web Browser images after you install the Secure Web Browser kit, you can avoid this problem completely. See Installing the Secure Web Browser Images for more information.) If you see an error similar to either of the following, then you have exhausted the available process sections: nsNativeComponentLoader:GetFactory(/dka0/mozilla/components/libnsgif.so)
Load FAILED with error: OpenVMS status is decimal 540
%SYSTEM-F-SECTBLFUL, process or global section table is full
There are three ways to solve this problem, as follows:
The Secure Web Browser is based on SeaMonkey V1.1.12. SeaMonkey has provided release notes for http://www.seamonkey-project.org/releases/seamonkey1.1.12/ The release notes contain sections about SeaMonkey on Windows, Mac, and UNIX. The Secure Web Browser is ported from the UNIX code, so the notes in the UNIX section are applicable to OpenVMS. When reading UNIX documentation, note the following differences between UNIX and OpenVMS:
Installing the Secure Web Browser The Secure Web Browser kit is included with the OpenVMS Integrity servers and OpenVMS Alpha layered product distributions. A compressed, self-extracting file is also available for download from the Secure Web Browser website. Beginning with the Secure Web Browser V1.4, GTK+ for OpenVMS and the OpenVMS Porting Library are included in the Secure Web Browser self-extracting file. See the Release Notes for more information. The size of the compressed Secure Web Browser V1.1-12 kit is 52,385 blocks. The expanded Secure Web Browser kit will occupy 141,648 blocks. The expanded GTK+ for OpenVMS kit will occupy 6768 blocks. The expanded OpenVMS Porting Library kit will occupy 352 blocks. Expand the Secure Web Browser self-extracting file by entering the following command: $ RUN CSWB-OPENVMS-ALPHA-V1112.SFX_AXPEXE The system expands the file and names the decompressed files as follows. Do not rename these files. UnZipSFX 5.41 of 16 February 2006, by Info-ZIP (http://www.info-zip.org). This self-extracting archive file contains PCSI kits for: - Secure Web Browser (CSWB) - GTK+ - OpenVMS Porting Library (OPL) Once the PCSI files are extracted, use the PRODUCT INSTALL command to install SWB. If you don't already have the required versions of GTK+ and OPL installed, they will be automatically installed too. inflating: CPQ-AXPVMS-CSWB-V0101-12-1.PCSI$COMPRESSED inflating: CPQ-AXPVMS-CSWB-V0101-12-1.PCSI$COMPRESSED_ESW inflating: CPQ-AXPVMS-GTK-V0102-10-1.PCSI$COMPRESSED inflating: CPQ-AXPVMS-GTK-V0102-10-1.PCSI$COMPRESSED_ESW inflating: CPQ-AXPVMS-OPL-V0100-0A9-1.PCSI$COMPRESSED inflating: CPQ-AXPVMS-OPL-V0100-0A9-1.PCSI$COMPRESSED_ESW $ After you expand the Secure Web Browser kit, you can delete the .SFX_AXPEXE file. Alternatively, you can first install the Secure Web Browser, then delete the .PCSI files, and keep the smaller .SFX_AXPEXE file in case you need to re-install the kit. Use the following procedure to start the installation. Note: Multiple users can run the Secure Web Browser on the same system. You need to install the Secure Web Browser only once. User specific information is maintained in a user profile, and these are stored in each user's SYS$LOGIN tree. You must install the Secure Web Browser into a top-level directory. If you do not accept the PCSI default destination, make sure that you do not attempt to install the Secure Web Browser into a subdirectory. To install the Secure Web Browser for OpenVMS Alpha kit, enter the following command: $ PRODUCT INSTALL CSWB For a description of the features you can request with the PRODUCT INSTALL command when starting an installation such as running the IVP, purging files, and configuring the installation, see the POLYCENTER Software Installation Utility User's Guide. As the installation procedure progresses, the system displays the following information. Performing product kit validation ...
%PCSI-I-VALPASSED, validation of WATER$DKB100:[000000.CSWB]CPQ-AXPVMSCSWB-
T0101-10-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VALPASSED, validation of WATER$DKB100:[000000.CSWB]CPQ-AXPVMSGTK-
V0102-10-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VALPASSED, validation of WATER$DKB100:[000000.CSWB]CPQ-AXPVMSOPL-
V0100-0A9-1.PCSI$COMPRESSED;1 succeeded
The following product has been selected:
CPQ AXPVMS CSWB V1.1-12 Layered Product
Do you want to continue? [YES]
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
CPQ AXPVMS CSWB V1.1-12
Do you want the defaults for all options? [YES]
Secure Web Browser (SWB) for OpenVMS Alpha
CPQ AXPVMS GTK V1.2-10
GTK+ for OpenVMS Alpha
CPQ AXPVMS OPL V1.0-0A9
OpenVMS Porting Library for OpenVMS Alpha
Do you want to review the options? [NO]
Execution phase starting ...
The following products will be installed to destinations:
CPQ AXPVMS CSWB V1.1-12 DISK$V0732:[VMS$COMMON.]
CPQ AXPVMS GTK V1.2-10 DISK$V0732:[VMS$COMMON.]
CPQ AXPVMS OPL V1.0-0A9 DISK$V0732:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
The following products have been installed:
CPQ AXPVMS CSWB V1.1-12 Layered Product
CPQ AXPVMS GTK V1.2-10 Layered Product
CPQ AXPVMS OPL V1.0-0A9 Layered Product
$
If the product is installed on OpenVMS Alpha V7.3-2 or V8.2, the output looks similar to the following: $ prod install cswb The following product has been selected: CPQ AXPVMS CSWB V1.1-12 Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. CPQ AXPVMS CSWB V1.1-12 Do you want the defaults for all options? [YES] Secure Web Browser (SWB) for OpenVMS Alpha CPQ AXPVMS GTK V1.2-10 GTK+ for OpenVMS Alpha CPQ AXPVMS OPL V1.0-0A9 OpenVMS Porting Library for OpenVMS Alpha Do you want to review the options? [NO] Execution phase starting ... The following products will be installed to destinations: CPQ AXPVMS CSWB V1.1-12 DISK$ALPHA732P5:[VMS$COMMON.] CPQ AXPVMS GTK V1.2-10 DISK$ALPHA732P5:[VMS$COMMON.] CPQ AXPVMS OPL V1.0-0A9 DISK$ALPHA732P5:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...50%...60%...70%...80%...90%...100% The following products have been installed: CPQ AXPVMS CSWB V1.1-12 Layered Product CPQ AXPVMS GTK V1.2-10 Layered Product CPQ AXPVMS OPL V1.0-0A9 Layered Product $Stopping and Restarting the Installation Use the following procedure to stop and restart the installation:
After you install the Secure Web Browser using the PRODUCT INSTALL command, you can also optionally install the Secure Web Browser images. There are two benefits to installing the images:
Approximately 190 global sections and 64,576 global pages are required to install the Secure Web Browser images. To install the Secure Web Browser images, run the command file INSTALL.COM (which resides in the Secure Web Browser root directory). For example: $ SET DEFAULT SYS$COMMON:[CSWB]
$ @INSTALL
You can also use the INSTALL.COM procedure to REPLACE (update) the Secure Web Browser images if they have been previously installed. To re-install the Secure Web Browser images, enter the following commands: $ SET DEFAULT SYS$COMMON:[CSWB]
$ @INSTALL REPLACE
If you want to uninstall the Secure Web Browser images, enter the following: $ SET DEFAULT SYS$COMMON:[CSWB]
$ @INSTALL REMOVE
Running the Secure Web Browser The Secure Web Browser is a full browser with extensions, and closely resembles Netscape 7. The Secure Web Browser contains:
You invoke the Secure Web Browser application through the supplied MOZILLA.COM command file. To invoke the Secure Web Browser, enter the following: $ @SYS$COMMON:[CSWB]MOZILLA This assumes that you installed the kit to the default location. If you directed PCSI to install to a different location, then your command to start the Secure Web Browser will contain a different disk or directory. You can also pass arguments to the application. For example: $ @SYS$COMMON:[CSWB]MOZILLA $ @SYS$COMMON:[CSWB]MOZILLA -edit $ @SYS$COMMON:[CSWB]MOZILLA -ProfileManager When you run the Secure Web Browser, the system must have approximately 336 global pages and one global section available. A check is made when you invoke the Secure Web Browser. If these requirements are not met, a warning is issued and terminating the Secure Web Browser is recommended. The Secure Web Browser requires that local files be in Stream_LF record format. Files of other record formats are not supported and the results of attempting to use any such file are undefined. When running the Secure Web Browser, you will see messages similar to the following appear in the terminal output. $ @SYS$COMMON:[CSWB]MOZILLA Starting seamonkey-bin... Many other messages are displayed when using the Navigator, Mail/News and Composer components of the Secure Web Browser. This is normal behavior. Release Notes This section contains notes on the current release of the Secure Web Browser.
Known Problems and Restrictions
Frequently Asked Questions (FAQs) This section contains frequently asked questions about the Secure Web Browser for OpenVMS Alpha. Differences between Secure Web Browser and Netscape Q: What are the differences between the Secure Web Browser and Netscape? A: There are very few differences. The Secure Web Browser and Netscape 7 are both based on Mozilla code. Differences between Secure Web Browser and Mozilla Q: What are the differences between the Secure Web Browser and Mozilla for OpenVMS? A: The Secure Web Browser is supported by Hewlett-Packard, but Mozilla for OpenVMS Alpha is not supported. You can download Mozilla for OpenVMS Alpha from the OpenVMS web site. Java Support in the Secure Web Browser Q: Is there support for Java in the Secure Web Browser for OpenVMS? A: Yes. See Support for the Java™ Platform in the Secure Web Browser for OpenVMS. Secure Web Browser on OpenVMS VAX Q: Will a version of the Secure Web Browser be available on VAX systems? A: There are currently no plans to port the Secure Web Browser to the VAX platform. Installing the Secure Web Browser and Mozilla on the same system Q: Can I install Mozilla on the same system as the Secure Web Browser? A: Yes. Both the Secure Web Browser and Mozilla can coexist on the same system. User profiles are common to the Secure Web Browser and Mozilla so your mail, bookmarks, and so on that you have on the Secure Web Browser will be available on Mozilla. The reverse is also true: mail and bookmarks on Mozilla are available on the Secure Web Browser. Changing the date format Q: A date field in the Secure Web Browser is always displayed in MM/DD/YY format. Can I change it? A: Yes. The format that the Secure Web Browser uses to display the date is determined by the locale, which you can change. For example, to set the locale to French, which causes dates to be displayed in DD.MM.YY format, define LC_ALL before running the Secure Web Browser. For example: $ DEFINE LC_ALL FR_FR_ISO8859-1 To list all the locales available on your system, enter the following: $ LOCALE SHOW PUBLIC PAGE UP key doesn't work Q: Why doesn't the PAGE UP key work as expected? A: The key bindings for the six keys in the middle of the keyboard (which include PAGE UP or REMOVE) assume that you have an LK style keyboard. If you have a PC style keyboard, you should define the logical GTK_KEY_MAPPING_MODE to 2 before running Mozilla. For example:
$ DEFINE GTK_KEY_MAPPING_MODE 2 Valid values for GTK_KEY_MAPPING_MODE are:
0 - No mapping GENERIC_POLL: unknown condition, errno=4 vaxc$errno=2096 Q: From time to time I see the GENERIC_POLL message above. What's the problem? A: There is no problem. The message, which typically appears when a java applet starts up, is purely informational and can be ignored. Secure Web Browser terminates with Gdk-ERROR **: BadAlloc (insufficient resources for operation) Q: Why am I getting an insufficient resources for operation error, which causes the Secure Web Browser to terminate? A: If the Secure Web Browser terminates with an error similar to the following: It is likely that you need to increase the amount of virtual memory available to your DECwindows X server process. The default is 100,000 pages. recommends that you set the value of virtual memory to 200,000 pages.Gdk-ERROR **: BadAlloc (insufficient resources for operation) serial 3993912 error_code 11 request_code 53 minor_code 0 Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter) serial 3993915 error_code 9 request_code 70 minor_code 0 To change this number, edit the file SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM and add a line similar to the following:
If the file SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM does not already exist, create it and add the preceding line.$ decw$server_page_file == 200000 The amount of virtual memory required depends on many factors. In general, the higher the resolution of your display and the higher the number of planes used for color (8, 16, or 24), the more virtual memory the X server needs.
After saving the file, restart your X server for the change to take effect. To restart your X server, enter the following command:
Note: Restarting the X server will terminate all of your running DECwindows programs.$ @sys$startup:decw$startup restart Secure Web Browser fails to load the Java plug-in at startup Q: Why can't the browser load the Java plug-in after I installed Java and copied the OJI plug-in file? I get this error: $ @mozilla Starting SEAMONKEY-BIN... LoadPlugin: failed to initialize shared library /dkb300/vms$common/mozilla/plugins/libjavaplugin_oji.so [OpenVMS status is decimal 98962] A: You need to set up Java before starting the Secure Web Browser. For Java v 5.0-5, enter the following command: $ @sys$startup:java$150_setup Secure Web Browser doesn't start up - decimal error Q: The Secure Web Browser fails to start up. I see errors similar to this displayed: nsNativeComponentLoader: SelfRegisterDll(/dka0/mozilla/components/libvcard.so) Load FAILED with error: OpenVMS status is decimal 114690 A: One of the account quotas may be too low. See Account Quotas and System Parameters, in particular the discussion about the FILLM quota. Secure Web Browser doesn't start up - process or global section error Q: The Secure Web Browser fails to start up. I see errors similar to this displayed: nsNativeComponentLoader: GetFactory(/dka0/mozilla/components/libnsgif.so) Load FAILED with error: OpenVMS status is decimal 540 %SYSTEM-F-SECTBLFUL, process or global section table is full A: You have a shortage of process sections. See Account Quotas and System Parameters for information about how to solve this problem. Can't open new DECterms Q: After running the Secure Web Browser, I can't open any new DECterms. Normal terminal sessions (for example, telnet) still work properly. Only a reboot seems to fix the problem -- removing the installed components from memory (INSTALL.COM REMOVE), or restarting X-Windows does not help. Other X-Windows applications do not seem to be affected. What's going on? A: You are probably out of buffer object space. Try increasing the SYSGEN parameter MAXBOBMEM. Unable to open the temporary file Q: I can't send mail or create a page using Composer. I see a message similar to "Unable to open the temporary file." What's wrong? A: Make sure that you do not have any logical name or symbol definitions for tmp or tmpdir. If you do, remove them. Support V1.1-12 Release Version Support for the HP Secure Web Browser Version 1.1-12 for OpenVMS Alpha is
provided under existing OpenVMS service agreements through standard support
channels.
$! Command file to run Mozilla/CSWB and accept a VMS filespec as P1.
$! This command file must exist in the root Mozilla/CSWB directory
$! (where MOZILLA.COM resides).
$!
$ moz_self = f$envir("procedure")
$ moz_dir = f$parse(moz_self,,,"device") + f$parse(moz_self,,,"directory")
$!
$ if p1 .eqs. ""
$ then
$ write sys$output "No argument passed in"
$ @'moz_dir'mozilla
$ else
$ fs_vms = p1
$ fs_unix = "/" + f$parse(fs_vms,,,"device") - ":"
$ fs_vms_dir = f$parse(fs_vms,,,"directory") - "[" - "]" - "<" - ">"
$ i=0
$uloop:
$ e=f$element(i,".",fs_vms_dir)
$ if e .nes. "."
$ then
$ fs_unix = fs_unix + "/" + e
$ i=i+1
$ goto uloop
$ endif
$ fs_unix = fs_unix + "/" +-
f$parse(fs_vms,,,"name") + f$parse(fs_vms,,,"type")
$ fs_unix = f$edit(fs_unix,"lowercase")
$ write sys$output "VMS: ", fs_vms
$ write sys$output "UNIX: ", fs_unix
$ @'moz_dir'mozilla file://'fs_unix'
$ endif
$ exit
|
| ** About PDF files: The PDF files on this Web site can be read online or printed using Adobe® Acrobat® Reader. If you do not have this software installed on your system, you may download it from the Adobe Web site. | ||
|
|
|
|||||||||||||||
|
|||||||||||||||
