NetView^(R) Web Application

This readme file contains information about the NetView Web application component of Tivoli^(R) NetView for z/OS^(R) version 6 release 2.

This file is divided into the following categories:

• Installation Planning for NetView Web Application
• Prerequisites
• Selecting the Correct Files
• Installing/Uninstalling the NetView Web Application
• Post-Installation Customizations
• Security Enhancements
• Starting/Stopping the NetView Web Application
• Special Considerations for DBCS Japanese environment
• Late-Breaking News
• Getting Help
• Trademarks and Copyrights

Installation Planning for NetView Web Application

The NetView Web application is available on the following platforms:

• Windows^(R)
• AIX^(R)
• Linux^(R) on System z^(R)
• Linux on x86-32/x86-64

The NetView Web application consists of the following 4 components:

• WebSphere^(R) Enterprise Archive (EAR) file
• Web XML Editor Utility
• Readme Documentation (this file)
• Embedded version of the IBM^(R) WebSphere Application Server v8

Before installing the NetView Web application, you must decide if you want to use the Embedded version of the IBM WebSphere Application Server v8 or the IBM WebSphere Application Server as your web server. The Embedded version of the IBM WebSphere Application Server v8 image is installed as a 32-bit configuration. This embedded version of the WebSphere is integrated within the installation/package self-extracting image of NetView Web Application. The machine where the Embedded version of the IBM WebSphere Application Server v8 or IBM WebSphere Application Server is installed is referred to as the Web Application Server.

During the installation process, the InstallShield InstallAnywhere wizard will guide you through a series of short steps to determine your setup preferences. If you select "Yes, install embedded version of WebSphere", then all components (4) of the NetView Web app will be installed and configured. If you select "No, I already have WebSphere installed", then only 3 components will be be installed (installation and configuration of the Embedded version of the IBM WebSphere Application Server will not take place).

The specific level of the Embedded version of the IBM WebSphere Application Server v8 component which is shipped as part of the install image is V8.0.0.12.
Detailed version information is as follows:

Name:               IBM Embeddable WebSphere Application Server
Version:           8.0.0.12
ID:                    embeddedEXPRESS

Refer to the IBM Tivoli NetView for z/OS Installation: Configuring Additional Components manual for more information.

Prerequisites

Software Requirements

If you are using WebSphere as your web server, IBM WebSphere Application Server, v8 or higher level is required.
Also supported editions are WebSphere v8.5 and v8.5.5.

If you decided to use the Embedded version of the IBM WebSphere Application Server v8 (which is an installable component of NetView Web application) as your web server, then there is no need for another or separate WebSphere Application Server.

The NetView Web application Japanese version is only supported when connected to the NetView for z/OS Japanese version. The NetView Web application English version is only supported when connected to the NetView for z/OS English version.

The final install footprint is about 800 MB of fixed disk space for Windows and 950 MB for UNIX systems.
Important Note: During installation and deployment of the NetView Web application, system temp (%TEMP%) space on Windows and /tmp filesystem on UNIX will increase the total disk space requirements. Also, the target installation directory will require more disk space during the deployment phase than what is noted for the final install footprint. Based on this, it is recommended that your system have at least 1.5 GB for temp space and an additional 1.5 GB for the target installation directory.

It is recommended for your Windows or UNIX system to have at least 2 GB of memory. It is very important to have at least 2 GB of virtual memory available for the NetView Web application when installing on the platform Linux on System z.

The NetView Web application is supported on the following operating systems:

• Windows:
  Hardware:
  • Intel^(R) Pentium^(R) processor; Intel EM64T or AMD Opteron

  Operating System:

  • Microsoft Windows Server 2008 R2 (Enterprise/Standard/Datacenter) (x64)
  • Microsoft Windows Server 2012 (Datacenter, Standard, Essentials, Foundation) (x64)
  • For the NetView Web application Japanese version, the locale supported is Shift-JIS (codepage 932).

• AIX:
  Hardware:
  • IBM POWER^(R) family of 64-bit processors

  Operating System:

  • IBM AIX Version 6.1 (POWER systems) TL4 (6100-00-04) or later
  • IBM AIX Version 7.1 (POWER systems) TL2 SP1 (7100-02-01) or APAR IV09585 applied or later

    Note: For AIX 7.1, APAR IV09585 patch is needed to resolve JDK 1.6 error during WebSphere runtime.
              See http://www-01.ibm.com/support/docview.wss?uid=swg21575120 for more details.
    

    This error can also potentially occur when launching the znetview_webapp_aix.bin installer on AIX 7.1. The error would be indicated by the following message on the terminal:
    

    Error: Port Library failed to initialize: -125
    Error: Could not create the Java Virtual Machine.
    Error: A fatal exception has occurred. Program will exit.
    

    This error does not occur on AIX 6.1

  • For the NetView Web application Japanese version, the locale supported is ja_JP (EUC).

• Linux on System z:
  Hardware:
  • System z processors

  Operating System:

  • SUSE LINUX Enterprise Server (SLES) 10 (System z)
  • SUSE LINUX Enterprise Server (SLES) 11 (System z)
  • Red Hat Enterprise Linux (RHEL) 5.0 (System z)
  • Red Hat Enterprise Linux (RHEL) 6.0 (System z)

  For z/OS x390 64-bit platforms, this architecture requires the installation of compatibility libs for 32-bit apps to run in "compatibility mode" or "tolerance mode".

  NetView Web application runs on the 64-bit Linux on System z distributions in compatibility mode does not contain any native 64-bit compiled code.

• Linux on x86-32/x86-64:
  (Note concerning x86-64 platform: 64-bit is tolerated, not exploited, because the NetView Web application for Linux is a 32-bit application)
  Hardware:
  • Intel IA 32-bit Pentium processors (x86-32); Intel EM64T or AMD Opteron (designated as x86-64 or x64)

  Operating System:

  • SUSE Linux Enterprise Server 10 (x86-32/x86-64)
  • SUSE Linux Enterprise Server 11 (x86-32/x86-64)
  • Red Hat Enterprise Linux (RHEL) 5.0 (x86-32/x86-64)
  • Red Hat Enterprise Linux (RHEL) 6.0 (x86-32/x86-64)

Supported web browsers

• Windows:
  • Internet Explorer 8, 9, 10 or later with Java Plug-in v6.0 or v7.0
  • Firefox 17 (ESR) or later with Java Plug-in v6.0 or v7.0
  • Google Chrome 24 or later with Java Plug-in v6.0 or v7.0

• SUSE Linux:
  • Mozilla Firefox 17 (ESR) or later with Java Plug-in v6.0 or v7.0

• Red Hat Linux:
  • Mozilla Firefox 17 (ESR) or later with Java Plug-in v6.0 or v7.0

Hardware Requirements

For additional hardware requirements for IBM Websphere Application Server v8, Advanced Edition, see the WebSphere documentation for the applicable platform.

Selecting the Correct files

The files to install are located in the Tivoli NetView for z/OS DVD distribution media under the directory "webapp".

The following files are distributed as part of the NetView Web application:

Installing/Uninstalling the NetView Web Application

General information concerning Installing and Uninstalling the NetView Web Application

• The wizard for the uninstall process will guide you through the uninstall by prompting you to provide information in each wizard panel.
• During uninstall processing, the InstallAnywhere wizard does not remove files that were not originally installed by InstallAnywhere.
• Before attempting the uninstall, make sure you save any customized files that you may want to keep (e.g., the web.xml file that you modified for your environment).
• If you have previously installed the Embedded version of the IBM WebSphere Application Server v8 component, you must first end the web application server (server1) if it is still active before continuing with the uninstall.

• For instructions to run the NetView Web application web server as a Windows service, see section below under "Hints and Tips" called Setting up Web Application webserver to run as a Windows service.
• For silent or unattended installation of NetView Web application component, see InstallAnywhere template file in the "doc" subdirectory under your installation location. The file is called "znetview_webapp_silent_install.rsp" and contains all the necessary instructions and information about running a silent install on any supported platform. This file is also available on the DVD media under "webapp" subdirectory.
• For console mode (non-GUI interface) installations, invoke the installer with "-i console" option. Example below is for AIX platform:

  ./znetview_webapp_aix.bin -i console
  

  (console mode invocation with "-i console" option can also be used with the uninstall launcher as well)

• The installation wizard, InstallShield InstallAnywhere will guide you through the install process by prompting you to provide information in each wizard panel.
• Notes concerning SECURE and NON-SECURE selections for configuring your CONNECTION:

The default choice for the installation wizard is SECURE CONNECTION when running the NetView Web application with the Embedded version of the IBM WebSphere Application Server v8.

• If SECURE CONNECTION is configured, then the HTTPS Transport Port value (specified in the previous panel: default is 9943) is the port number for the URL to run the Web application. See the section below entitled "Starting your Internet Browser" for details. Selecting SECURE CONNECTION will only allow HTTPS access since HTTP transport will be disabled.

  Sample URL   (notice the "s" with this protocol https !):
  https://hostname:9943/netview/NetView4zosDomain/      (secure connection)

• If NON-SECURE CONNECTION is configured, then both HTTP and HTTPS transports are enabled. This means that you can run the Web application using either HTTPS Transport Port value (default is 9943) or HTTP Transport Port value (default is 9980).

  Sample URL   (either one will provide access):
  http://hostname:9980/netview/NetView4zosDomain/        (non-secure connection) https://hostname:9943/netview/NetView4zosDomain/      (secure connection)

Note: If after installation of the Embedded version of the IBM WebSphere Application Server v8 component, you then decide that you want to change your CONNECTION from SECURE to NON-SECURE or NON-SECURE to SECURE, then use the "secure script" to make this change. See the section below labeled "Using the secure script:" under Configuring the Embedded version of the IBM WebSphere Application Server v8 for details.

• As a general rule for each of the installation sections below, uninstall the product before attempting any new installation.
• For installation debug purposes, there is a log file in the installation home directory named NetView_Web_Application_InstallLog.log.
  Also, an additional accumulative log file named webapp_installer.log can be located in c:\tmp for Windows and /tmp for UNIX.

  It is possible that these files may need to be examined by the NetView service support team if any installation errors occur.

Installing the NetView Web Application on Windows

To install the NetView Web application on a supported Windows platform, follow these steps:

Installation Tips:

• How much extra disk space will I need to complete my installation of all components?
  When you see the first InstallAnywhere panel displaying the title "IBM NetView Web Application", at least 850 MB of temporary disk space will be required on the C: drive. When you complete the installation, the temporary space will be released. As for your target directory or folder, you will need at least 850 MB of space to install all components.

To install the NetView Web application from DVD:

• Insert the Tivoli NetView for z/OS DVD distribution media into the DVD drive of your workstation.

• Find the drive and directory where the NetView Web application for Windows resides. The directory is "webapp" and the file name is znetview_webapp_win.exe.

               ---- or ----

To install the NetView Web application by HTTP download, follow these instructions:

• Point your web browser to the following URL: http://www.ibm.com
• Select from the drop down menu list "Support and downloads"- "Download" - "fixes, updates and drivers"
• Enter "NetView Web Application" in the "Search within Download" field and select "Search"
• In the resulting list, click on the link for the "NetView Web Application"
• You will now be on the support and downloads page for NetView Web Application.
• Select the download package for Windows version 6.2 and download it into a temporary directory as znetview_webapp_win.exe.

Running the znetview_webapp_win.exe file will invoke the InstallShield InstallAnywhere setup wizard.

Note:
When you run znetview_webapp_win.exe for Windows, you get an initial InstallAnywhere panel that prepares a JVM (Java Virtual Machine) to be used for the installation.

Next you should see the display of a NetView for z/OS 6.2 "splash screen". The initial panel to start the InstallAnywhere Wizard should appear shortly thereafter.

It is recommended, but not necessary, to use the default directory name of the target folder. The default path is "c:\usr\lpp\netview\v6r2". It is important not to use special characters like &, *, or # as part of the target folder path name.

Uninstalling the NetView Web Application from Windows

To uninstall the NetView Web application on a supported Windows platform, follow these steps:

• To Uninstall the NetView Web application, use the "Add or Remove Program" available on Windows. (On Windows editions of Server 2008, "Programs and Features" replaces "Add or Remove Programs"). If you select "NetView Web Application" in the list and start the uninstall process, InstallAnywhere will run an uninstall program which will uninstall all NetView Web app components.

• InstallAnywhere will not remove files that have been created dynamically.

  Note:
  DO NOT remove any installed files or folders (subdirectories) without first completing the "Add or Remove Program" process described above in the first bullet.

  Also, if you have made any important updates to the web.xml file file, you might want to save this file before uninstalling the product.

Installing the NetView Web Application on AIX

To install the NetView Web application from DVD:

• Insert the Tivoli NetView for z/OS DVD distribution media into the DVD drive of your workstation.

• Find the drive and directory where the NetView Web application for AIX resides. The directory is "webapp" and the file name is znetview_webapp_aix.bin.

               ---- or ----

To install the NetView Web application by HTTP download, follow these instructions:

• Point your web browser to the following URL: http://www.ibm.com
• Select from the drop down menu list "Support and downloads"- "Download" - "fixes, updates and drivers"
• Enter "NetView Web Application" in the "Search within Download" field and select "Search"
• In the resulting list, click on the link for the "NetView Web Application"
• You will now be on the support and downloads page for NetView Web Application.
• Select the download package for AIX Version 6.2 and download it into a temporary directory as znetview_webapp_aix.bin.

Running the znetview_webapp_aix.bin file will invoke the InstallShield InstallAnywhere setup wizard.

Note:
When you invoke znetview_webapp_aix.bin, AIX will display the following status messages:

         Initializing InstallAnywhere Wizard Installer...
         Preparing Java(tm) Virtual Machine...
         ...................................
         ...................................
         .........................

         Running InstallAnywhere Wizard Installer...

The InstallAnywhere panels that follow with the AIX installation are similar to the other platform installation sequences.

It is recommended, but not required, to use the default directory name of the target folder. The default path is "/usr/lpp/netview/v6r2".

Uninstalling the NetView Web Application from AIX

To uninstall the NetView Web application from AIX, follow these steps:

• To uninstall the NetView Web application, you can run uninstall_webapp file that resides in the _uninstall subdirectory located in the path selected during the installation.

  InstallAnywhere will run the uninstall program to uninstall all NetView Web application components.

• InstallAnywhere will not remove files that have been created dynamically.

  Note:
  DO NOT remove any installed files or subdirectories without first running the InstallAnywhere's uninstaller file znetview_webapp_aix_uninstall.bin as described above in the first bullet.

  Do not attempt to uninstall the NetView Web application product via "installp -u" or through the SMIT/SMITTY interface.

  Also, if you have made any important updates to the web.xml file, you might want to save this file before uninstalling the product.

Installing the NetView Web Application on Linux on System z

To install the NetView Web application on your Linux system follow these steps:

To install the NetView Web application from DVD:

• Insert the Tivoli NetView for z/OS DVD distribution media into the DVD drive of your workstation.

• Find the drive and directory where the NetView Web application for Linux on System z resides. The directory is "webapp" and the file name is znetview_webapp_zlinux.bin.

               ---- or ----

To install the NetView Web application by HTTP download, follow these instructions:

• Point your web browser to the following URL: http://www.ibm.com
• Select from the drop down menu list "Support and downloads"- "Download" - "fixes, updates and drivers"
• Enter "NetView Web Application" in the "Search within Download" field and select "Search"
• In the resulting list, click on the link for the "NetView Web Application"
• You will now be on the support and downloads page for NetView Web Application.
• Select the download package for Linux on System z Version 6.2 and download it into a temporary directory as znetview_webapp_zlinux.bin.

Running the znetview_webapp_zlinux.bin file will invoke the InstallShield InstallAnywhere setup wizard.

Note:
When you invoke znetview_webapp_zlinux.bin, your Linux system will display the following status messages:

         Initializing InstallAnywhere Wizard Installer...
         Preparing Java(tm) Virtual Machine...
         ...................................
         ...................................
         .........................

         Running InstallAnywhere Wizard Installer...

The InstallAnywhere panels that follow with the Linux on System z installation are similar to the other platform installation sequences.

It is recommended, but not required, to use the default directory name of the target folder. The default path is "/usr/lpp/netview/v6r2".

Uninstalling the NetView Web Application from Linux on System z

To uninstall the NetView Web application from Linux on System z, follow these steps:

• To uninstall the NetView Web application, you can run uninstall_webapp file that resides in the _uninstall subdirectory located in the path selected during the installation.

  InstallAnywhere will run the uninstall program which will remove all NetView Web application components.

• InstallAnywhere will not remove files that have been created dynamically.

  Note:
  DO NOT remove any installed files or subdirectories without first running the InstallAnywhere's uninstaller file znetview_webapp_zlinux_uninstall.bin as described above in the first bullet.

  Do not attempt to uninstall the NetView Web application product via "rpm -e".

  Also, if you have made any important updates to the web.xml file, you might want to save this file before uninstalling the product.

Installing the NetView Web Application on Linux on x86-32/x86-64

To install the NetView Web application on your Linux system follow these steps:

To install the NetView Web application by HTTP download, follow these instructions:

• Point your web browser to the following URL: http://www.ibm.com
• Select from the drop down menu list "Support and downloads"- "Download" - "fixes, updates and drivers"
• Enter "NetView Web Application" in the "Search within Download" field and select "Search"
• In the resulting list, click on the link for the "NetView Web Application"
• You will now be on the support and downloads page for NetView Web Application.
• Select the download package for xLinux Version 6.2 and download it into a temporary directory as znetview_webapp_ia32linux.bin.

Running the znetview_webapp_ia32linux.bin file will invoke the InstallShield InstallAnywhere setup wizard.

Note:
When you invoke znetview_webapp_ia32linux.bin, your Linux system will display the following status messages:

         Initializing InstallAnywhere Wizard Installer...
         Preparing Java(tm) Virtual Machine...
         ...................................
         ...................................
         .........................

         Running InstallAnywhere Wizard Installer...

The InstallAnywhere panels that follow with the Linux installation are similar to the other platform installation sequences.

It is recommended, but not required, to use the default directory name of the target folder. The default path is "/usr/lpp/netview/v6r2".

Uninstalling the NetView Web Application from Linux

To uninstall the NetView Web application from Linux, follow these steps:

• To uninstall the NetView Web application, you can run uninstall_webapp file that resides in the _uninstall subdirectory located in the path selected during the installation.

  InstallAnywhere will run the uninstall program which will remove all NetView Web application components.

• InstallAnywhere will not remove files that have been created dynamically.

  Note:
  DO NOT remove any installed files or subdirectories without first running the InstallAnywhere's uninstaller file znetview_webapp_ia32linux_uninstall.bin as described above in the first bullet.

  Do not attempt to uninstall the NetView Web application product via "rpm -e".

  Also, if you have made any important updates to the web.xml file, you might want to save this file before uninstalling the product.

Post-Installation Customizations

If you have installed the NetView Web application component "Embedded version of the IBM WebSphere Application Server v8", then you should skip to the section below called "Post-Installation Customizations for the Embedded version of the IBM WebSphere Application Server v8" to complete necessary customization steps that still need to be taken.

If you have installed the zNetViewWebApp.ear file and only want to run the NetView Web application within the WebSphere Application Server, then you still need to complete the following section herein called "Post-Installation Customizations for WebSphere Application Server".

Post-Installation Customizations for WebSphere Application Server

Installing the Enterprise Application (zNetViewWebApp.ear file) with the WebSphere Enterprise Application Wizard

Note:   The following steps should be used as a guide only since the presentation of panel information is dependant upon your WebSphere configuration. For example, if Global Security is not enabled, you may not see any of the "Security" related panels display during the enumerated steps below. Also, if default binding are pre-configured, then binding information will be filled in automatically with defaults and the Bindings window panel may not be displayed.

To install the Enterprise Application zNetViewWebApp.ear file:

• Start the WebSphere Application Server, if it is not already started.
  
  Windows environment:
  Start -> Programs -> IBM WebSphere -> IBM WebSphere Application Server v8.5 -> Profiles -> profile -> First Steps
  Where: profile is the profile name associated with this instance of the WebSphere Application Server.
  
  Choose "Start the server"
  
  UNIX environment:
  Issue the following command from the WebSphere Application Server's installation location "firststeps" directory in order to start First Steps:
  Note: WebSphere Application Server installation location's firststeps directory is "websphere_installation_path/profiles/profile/firststeps" where:
  websphere_installation_path is the install location of WebSphere Application Server
  profile is the profile name associated with this instance of the WebSphere Application Server.
  
  ./firststeps.sh &
  
  Choose "Start the server"
  

• Start the WebSphere Administrator's Console
  
  Windows environment:
  Start -> Programs -> IBM WebSphere -> IBM WebSphere Application Server V8.5 -> Profiles -> profile -> First Steps
  Note: profile is the profile name associated with this instance of the WebSphere Application Server.
  
  Choose "Administrative console"
  
  UNIX environment:
  Issue the following command from the WebSphere Application Server's installation location "firststeps" directory in order to start First Steps:
  Note: WebSphere Application Server installation location's firststeps directory is "websphere_installation_path/profiles/profile/firststeps" where:
  websphere_installation_path is the install location of WebSphere Application Server
  profile is the profile name associated with this instance of the WebSphere Application Server.
  
  ./firststeps.sh &
  
  Choose "Administrative console"
  

• On the left side of the Administrative Console, expand "Applications".
• Click on "New Application".
• From the list presented, select "New Enterprise Application"
• Provide the path or use the browse key to locate the zNetViewWebApp.ear file.
• By default, the zNetViewWebApp.ear file resides in usr\lpp\netview\v6r2\ears.
• Click Next
• Make sure "Fast Path" is selected. Click Next.
  
  Note: Selecting "Detailed" will show all installation options and parameters (including Map Security Roles to Users or Groups). 12 steps to complete instead of only 4 steps for "Fast Path".
• Step 1: "Select installation options", click Next (note that the application name is already filled in).
• Step 2: "Map modules to servers", select NetView for z/OS Web Application, click Next.
• Step 3: "Map virtual hosts for web modules", select NetView for z/OS Web Application and choose the virtual host. Click Next.
• Step 4: Click Finish on the "Summary" window after verifying the information is correct
• After the NetView Web Application is installed successfully, click "Save directly to the master configuration"

To start the NetView Web Application

• Expand "Applications" on the left side of the Administrative Console and then expand "Application Types".
• Click "WebSphere enterprise applications" and select the application name that you provided above for the NetView Web application
  (for example, "NetView Web Application")
• Click the "Start" button.

Uninstalling the Enterprise Application (zNetViewWebApp.ear file) with the WebSphere Enterprise Application Wizard

To uninstall the NetView Web application from a supported platform, follow these steps:

Note: You might want to first save any customizations made to the web.xml file before proceeding with the rest of these instructions.

• Expand "Applications" on the left side of the Administrative Console and then expand "Application Types".
• Click "WebSphere enterprise applications" and select the application name that you provided above for the NetView Web application
  (for example, "NetView Web Application")
• Click the "Stop" button.
• Once the NetView Web Application has stopped, select it again, and click Uninstall.
• Save the changes.

Note: Uninstalling the zNetViewWebApp.ear file from WebSphere Application Server does not uninstall any of the NetView WebSphere application components previously installed. To uninstall the NetView WebSphere application, see the Installing/Uninstalling the NetView Web Application section for your platform.

• It will be necessary to modify the web.xml file in the WEB-INF directory before starting the NetView Web application. For a deployment within an application server, the full path to this file will be as follows:
  websphere_installation_path/profiles/profile/config/cells/Node/applications/NetView Web Application.ear/deployments/NetView Web Application/zNetViewWebApp.war/WEB-INF
  where:
  websphere_installation_path is the install location of WebSphere Application Server.
  profile is the profile of the WebSphere application server running on Node.
  Node is the Node name where the WebSphere application server resides.

• It is recommended that you use the Web XML Editor Utility to modify your web.xml file. See "Starting the Web XML Editor Utility" under the section Starting/Stopping the NetView Web Application for information regarding this utility.

• You must create a uniquely named servlet definition and url-pattern for each NetView for z/OS domain that you want to communicate with. The default domain used in the web.xml file is cnm01. Using the servlet definition section named cnm01_ZnvAccessServlet as your template, create a uniquely named section for each of your NetView domains. Only create a single servlet definition for each NetView domain; however, you can define multiple url-patterns that point to each servlet. The domain portion of the url-pattern cannot be mixed case. Note: If you are not using the Web XML Editor Utility, the url-pattern is part of the servlet-mapping element. Be sure to provide equivalent url-pattern tags creating the URL with the domain in lowercase and another with the domain in uppercase. The Web XML Editor Utility will automatically do this for you.

• Modify the value of the HOST parameter to be the fully qualified hostname of your NetView for z/OS domain (for example, netviewhost.subnet.company.com). Change the value of the ZNV_DOMAIN parameter to be the NetView for z/OS domain name. Modify PORT, INKEY and OUTKEY as appropriate for your installation.

• You must also create a uniquely named url-pattern for each z/NetView. Change the value of the url-pattern for the ZnvAccessServlet to the same value you assigned to ZNV_DOMAIN parameter.

  Important information concerning Japanese environment:

  Edit the web_ja.xml file that resides in the same location as web.xml. It is important to start with the web_ja.xml file since it supports the proper encodings for the Japanese locale. However, after edits are made and saved to web_ja.xml, you must replace the existing web.xml file with the updated web_ja.xml file. The replacement step is important because the Web application processes only the file named web.xml.

For more information, refer to the IBM Tivoli NetView for z/OS Installation: Configuring Additional Components manual.

Post-Installation Customizations for the Embedded version of the IBM WebSphere Application Server v8

• It will be necessary to modify the web.xml file in the WEB-INF directory before starting the Web Application Server. If you have chosen the default target directory during installation, the full path to this file will be as follows:
  \usr\lpp\netview\v6r2\ewas\profiles\profile1\installedApps\DefaultNode\zNetViewWebApp.ear\zNetViewWebApp.war\WEB-INF

• It is recommended that you use the Web XML Editor Utility to modify your web.xml file. See "Starting the Web XML Editor Utility" under the section Starting/Stopping the NetView Web Application for information regarding this utility.

• You must create a uniquely named servlet definition and url-pattern for each NetView for z/OS domain that you want to communicate with. The default domain used in the web.xml file is cnm01. Using the servlet definition section named cnm01_ZnvAccessServlet as your template, create a uniquely named section for each of your NetView domains. Only create a single servlet definition for each NetView domain; however, you can define multiple url-patterns that point to each servlet. The domain portion of the url-pattern cannot be mixed case. Note: If you are not using the Web XML Editor Utility, the url-pattern is part of the servlet-mapping element. Be sure to provide equivalent url-pattern tags creating the URL with the domain in lowercase and another with the domain in uppercase. The Web XML Editor Utility will automatically do this for you.

• Modify the value of the HOST parameter to be the fully qualified hostname of your NetView for z/OS domain (for example, netviewhost.subnet.company.com). Change the value of the ZNV_DOMAIN parameter to be the NetView for z/OS domain name. Modify PORT, INKEY and OUTKEY as appropriate for your installation.

• You must also create a uniquely named url-pattern for each z/NetView. Change the value of the url-pattern for the ZnvAccessServlet to the same value you assigned to ZNV_DOMAIN parameter.

  Important information concerning Japanese environment:

  Edit the web_ja.xml file that resides in the same location as web.xml. It is important to start with the web_ja.xml file since it supports the proper encodings for the Japanese locale. However, after edits are made and saved to web_ja.xml, you must replace the existing web.xml file with the updated web_ja.xml file. The replacement step is important because the Web application processes only the file named web.xml.

For more information, refer to the IBM Tivoli NetView for z/OS Installation: Configuring Additional Components manual.

Security Enhancements

Securing logon to the NetView for z/OS host

The NetView Web application user logon security has been enhanced.

If a user cannot logon to the NetView host from the NetView Web application, it may be that their user ID has been locked out due to five consecutive unsuccessful logon attempts. This would be indicated by the user being redirected to the web site http://www.ibm.com upon attempting to logon to the NetView host. If a user gets locked out, the administrator can locate the following directory:

install_location/ewas/profiles/profile
and delete the file named userid_domain_settings.xml

Do not modify the userid_domain_settings.xml file manually as that can lead to unexpected results.

The browser instance, which was in use when the NetView user ID lock out occurred, must be closed and a new browser instance started.

Try the logon to the NetView host again with a new browser instance.

Securing connection between NetView host and Web application server

To provide enhanced support for cryptographic protocols targeting data flows between the NetView program and the Web application server, the Web application makes use of the Application Transparent Transport Layer Security (AT-TLS) function. At the host end of the connection, z/OS Communication Server provides a configuration option that enables secure connections. For more information, see the z/OS Communications Server library and the CNMSJTLS sample. This AT-TLS supported encryption is enhanced as compared to the current INKEY and OUTKEY initialization and synchronization with DSITCPRF. The IBM Tivoli NetView for z/OS Security Reference has more information; however, first examine the CNMSJTLS sample.

To enable secure connection between the Web application server (where the zNetViewWebApp.ear file has been installed and deployed) and z/OS NetView host, a configuration value in the workstation properties file webapp_security.properties is required to be updated.

webapp_security.properties, file is located here for installations of zNetViewWebApp.ear into base WebSphere Application Server:

websphere_installation_path/profiles/profile/config/cells/Node/applications/NetView Web Application.ear/deployments/NetView Web Application/zNetViewWebApp.war/WEB-INF
where:

websphere_installation_path is the install location of WebSphere Application Server.
profile is the profile of the WebSphere application server running on Node.
Node is the Node name where the WebSphere application server resides.

webapp_security.properties, file is located here for installations into the Embedded version of the IBM WebSphere Application Server v8 (path uses default installation location on Windows platform for the example):

\usr\lpp\netview\v6r2\ewas\profiles\profile1\installedApps\DefaultNode\zNetViewWebApp.ear\zNetViewWebApp.war\WEB-INF

Follow the instructions in the webapp_security.properties file. A value for SECURE_HOST_CONNECTION=TRUE will signal the Web application to enable secure connection to z/OS NetView host. Note: For the Web application to recognize the any change to this SECURE_HOST_CONNECTION setting, the WebSphere application server (where the zNetViewWebApp.ear EAR file has been installed and deployed) will have to be stopped (if running) and started. See section Starting/Stopping the NetView Web Application for details

Supported cryptographic protocols and underlying ciphers will be determined by the z/OS host TTLSEnvironmentAdvancedParms settings (under TTLSEnvironmentAction section) in the AT-TLS rules file. The workstation Web application component will support SSLv3, TLS v1.0, TLS v1.1, and TLS v1.2 protocols. These same protocols can be supported as well (disabled or enabled) via AT-TLS rules settings. The TLS v1.2 protocol is supported on z/OS 2.1. It is additionally supported on z/OS 1.13 with the following patches: z/OS Communications Server toleration APAR PM62905 and System SSL APAR OA39422.

Note: NetView's rules file is based on z/OS Communications Server's sample pagent_TTLS.conf and, if the sample NetView installation directory structure is used, is found in z/OS UNIX System Services directory /usr/lpp/netview/v6r2/samples/at-tls. Sample job CNMSJTLS will copy rules (or the rules file, whichever you might prefer) from this directory to the /etc/netview/at-tls directory. Your AT-TLS policy for NetView, which can be derived from the examples in the sample rules file, may need to be merged into your existing AT-TLS policy.

To secure the data flow inbound and outbound to the host, the AT-TLS function must be enabled and the z/OS Communications Server Policy Agent (PAGENT) must be configured and active.

Before starting PAGENT (S PAGENT), you have to setup the TCPCONFIG statement with parm TTLS in order to indicate that the AT-TLS function is activated for the TCP/IP stack. This will enable secure data flow on z/OS according to your rules file. Example for this setup would be the invocation of a command as follows (command needs to be run first before attempting to start PAGENT):

vary tcpip,,obeyfile,dsn=USER.PARMLIB(TTLSOBEY)
assuming a USER.PARMLIB(TTLSOBEY) file exists and its contents are: TCPCONFIG TTLS.

OR

you have your TCP/IP profile coded with TCPCONFIG TTLS included in your system startup procedures.

Note: Per z/OS Communications Server: IP Configuration Guide, when a TCPCONFIG TTLS value is specified, the AT-TLS function uses AT-TLS policy information (configured using Policy Agent) to determine how application connections are processed. If the setting is modified using this VARY TCPIP,,OBEYFILE command, only new connections are affected by the change.

Also note, if updates are made to the rules file, then you have to inform z/OS Communications Server Policy Agent that a change was made. Use this command to do so:

F PAGENT,UPDATE


Summary of situations where the Web application will not be able to sign onto the NetView host:

If the value for SECURE_HOST_CONNECTION=FALSE is specified in the webapp_security.properties file, then you must make sure that:

1. the AT-TLS function is not activated for the TCP/IP stack. Command example to de-activate this security is as follows:
   vary tcpip,,obeyfile,dsn=USER.PARMLIB(TTLSOFF)
   assuming a USER.PARMLIB(TTLSOFF) file exists and its contents are: TCPCONFIG NOTTLS
2. and that the Policy Agent is no long active. Stop the Policy Agent with this command:
   F PAGENT

    OR

    z/OS Communications Server Policy Agent is active, but you are not using NetView's AT-TLS rules
    file example that codes for Web application using port 8008 for a secure inbound connection.




If the value for SECURE_HOST_CONNECTION=TRUE is specified in the webapp_security.properties file, then you must make sure that:

1. the AT-TLS function is activated for the TCP/IP stack (TCPCONFIG TTLS statement)
2. and that the Policy Agent is active and is able to read a AT-TLS rules file which configures for Web application secure inbound connection on port 8008.


Information concerning a possible System log message:

A message may be seen in the log after issuing the "S PAGENT" command as follows:

EZD1290I TCPIP ICSF SERVICES ARE CURRENTLY UNAVAILABLE FOR AT-TLS GROUP group_action0

This message indicates that ICSF (z/OS Integrated Cryptographic Services Facility) has not been started. It is important to note that while the AT-TLS function provides invocation of System SSL in the TCP transport layer of the stack, System SSL software algorithms cannot provide the strongest cryptographic support compared to ICSF. For example, FIPS 140-2 mode and any use of elliptical curve ciphers require ICSF to be active when the AT-TLS group starts. One caveat (when defining AT-TLS policy for ICSF usage to further restrict secure data flow) is that stronger ciphers, larger key sizes, and special modes of operation (e.g. Suite B, FIPS 140-2), will normally result in a reduction in performance.

Certificate and Key Management for NetView host and Web application server

The self-signed certificate for the Web application has already been created in the webappkeydb.jks keystore file. The same certificate (webpp.arm) has been added to the host keyring database file (keyring.db). The certificate has the following properties:
• Base64-encoded ASCII data type
• X506 V3 version
• RSA keys with 2048 bits
• Digital signatures with SHA2 encryption algorithm

Important NetView Web application workstation files for consideration:


• webappkeydb.jks    java keystore database file (JKS type) that contains a matching Web Application certificate (webapp.arm)
• webapp.arm    a base64-coded (ASCII data) certificate request file (matches the host file)
• webapp_security.properties    the properties file referenced above to set secure/non-secure host connection

these files are located at in the same subdirectory as the webapp_security.properties file.

To create the public and private keys and certificate requests, you can use one of many key management utilities. One such tool, ikeyman, is available with java 1.7 which is included within the Web application install image (located in directory install_location\_jvm\jre\bin).

Important NetView program host files:

• keyring.db     key ring database file (CMS type) that contains a matching Web Application certificate (webapp.arm)
• keyring.rdb     key ring private key file
• keyring.sth     key ring stash file that contains the key ring password
• readme    instructions for key and certificate management
• webapp.arm    a base64-coded (ASCII data) certificate request file (matches the workstation file)

these files are located on z/OS UNIX System Services at location /etc/netview/at-tls.

To create the public and private keys and certificates or import/export certificates, use the key management utility on z/OS called gskkyman. See the readme in /usr/lpp/netview/v6r2/at-tls directory, if the sample NetView installation directory structure is used on the z/OS system, for instructions in using gskkyman utility or optionally the ikeyman utility for key management of these key ring files.

Starting/Stopping the NetView Web Application

The nvsrvc Command

nvsrvc start webserver OR, simply
nvsrvc start
This will start the Embedded version of the IBM WebSphere Application Server v8. The Web Application server is started when a message stating "Server open for e-business" is issued.
A log file will be created in \usr\lpp\netview\v6r2\ewas\logs when the z/NetView Web Application is accessed:

netviewservlets.log - This log contains information, warning and error messages generated during NetView Web application server initialization or processing.

The Embedded version of the IBM WebSphere Application Server v8 provides log files in the \usr\lpp\netview\v6r2\ewas\profiles\profile1\logs\server1 directory. The SystemOut.log file is the main log file for application server operations.

To display help for this command, issue the nvsrvc command without any parameters.

Configuring the Embedded version of the IBM WebSphere Application Server v8

• Using the secure script:

You can set the CONNECTION type to SECURE or NON-SECURE when running the NetView Web application within the Embedded version of the IBM WebSphere Application Server v8 component at any time by using a tool in the "bin" subdirectory of the NetView Web application installed location. For Windows, the script tool is called "secure.bat". For UNIX it is "secure.sh".

Only options for the secure script are "y" or "n". Running the script without any parameters will display the available options with a brief description.

• y  option enables only https access and disables http access for the NetView Web application.
• n  option enables both https and http accesses for the NetView Web application.

For example, if you wanted to set the CONNECTION for the NetView Web application to NON-SECURE on AIX, then you would issue the following command from the ../bin subdirectory:

"./secure.sh  n"

Refer to "Notes concerning SECURE and NON-SECURE selections for configuring your CONNECTION" in the section above under Install - Important Information concerning the details that will affect your URL access (http vs. https) and port number.

• Session Timeout:
To set a new value for session timeout, edit the following file in installation_location\ewas\profiles\profile1\config\cells\DefaultNode\nodes\DefaultNode\servers\server1\server.xml
where installation_location is the install location previously specified (default is c:\usr\lpp\netview\v6r2 for windows and /usr/lpp/netview/v6r2 for UNIX)

In this server.xml file, look for string invalidationTimeout. Default value is 30. Change this value, save the file and then stop/start the web server to enable the change to take place.

(It is recommended that you make a backup of this file before saving any changes)

• Port Values:

Current values of ports values set during the installation can be queried by examining the portdef.props file in the installation_location\properties subdirectory.

Common port values to change are WC_defaulthost (default is 9980) and WC_defaulthost_secure (default is 9943).
You can modify these two values by editing the following three files, searching for their strings, saving your changes, and then stop/start the web server to enable the changes to take place.

The three files are:

installation_location\ewas\profiles\profile1\config\cells\DefaultNode\nodes\DefaultNode\serverindex.xml
installation_location\ewas\profiles\profile1\config\cells\DefaultNode\virtualhosts.xml
installation_location\ewas\profiles\profile1\config\templates\servertypes\APPLICATION_SERVER\serverindex.xml

(It is recommended that you make backups of all three files before saving any changes)

Starting the Embedded version of the IBM WebSphere Application Server v8

Windows Environment - execute the following:

cd D:\usr\lpp\netview\v6r2\bin
nvsrvc start webserver      (or just nvsrvc start)

UNIX Environment - execute the following:

cd /usr/lpp/netview/v6r2/bin
./nvsrvc.sh start webserver      (or just ./nvsrvc.sh start)

Starting the Web XML Editor Utility

Use the following command to start the utility.
   Note: D: drive is used as an example drive in the command below.

Windows Environment - execute the following:
cd D:\usr\lpp\netview\v6r2\wxe\bin
WxeEditor.bat

UNIX Environment - execute the following:

cd /usr/lpp/netview/v6r2/wxe/bin
./WxeEditor.sh

Important note: When running the Web XML Editor Utility (WxeEditor.sh) on UNIX systems, which may not have a common desktop environment (e.g. Linux on System z), it is important that the display be previously configured to handle X-Windows or X11 GUI applications. Any RPM package installations, tools, and configuration needed to export the display properly in this context is beyond the scope of IBM's responsibilities.

Starting your Internet Browser

To display the sign-on panel for the NetView Web application from your Internet Browser (Mozilla or Internet Explorer), task DSIWBTSK must be ACTIVE on the NetView for z/OS system.

If you are using the Embedded version of the IBM WebSphere Application Server v8, point your web browser to:

https://hostname:9943/netview/NetView4zosDomain/

If you are using WebSphere, point your web browser to http://hostname:portnumber/netview/NetView4zosDomain/
If you configure your HTTP web server and WebSphere Application Server to use a port other than the default of 80, then you will need to specify that port in the URL after the hostname. Note that hostname and port must be separated by a colon.

hostname is the hostname of the machine where your Web Application code is installed. If you are running everything locally, you can specify localhost as your hostname.

portnumber is the port number for the application server's internal HTTP or HTTPS transport connection.

NetView4zosDomain is the name that you specified in the servlet-mapping definition in the web.xml file (if you are using the Embedded version of the IBM WebSphere Application Server v8) or the value that you supplied when performing the pre-installation steps for WebSphere. If you have followed the customization steps above, this will be the NetView for z/OS domain name.

Sign on to NetView using a valid user name (NetView operator ID) and password.

Special Considerations for DBCS Japanese environment

The following items describe some situations that need to be considered when operating NetView Web application in a supported Japanese environment:

• Editing the web_ja.xml file (to be saved as web.xml) on a Japanese windows operating system:

Do not use wordpad since some Japanese characters will be incorrectly converted from UTF-8 format when saving the file. It is recommended to use another editor that can handle UTF-8 locale.

Late-Breaking News

New Enhancements

• None.

Hints and Tips

• Setting up Web Application webserver to run as a Windows service.

This section describes the information necessary for installing and starting NetView Web application webserver (WebSphere app server, server1) as a Windows service for the installed component "Embedded version of the IBM WebSphere Application Server v8".

Initial assumptions for the NetViewWebApp Windows service:

This first step is important since you want to make sure that the webserver is functioning properly in normal usage (not as a Windows service):
• It is assumed at this point that "nvsrvc start webserver" successfully starts the WebSphere app server, server1.
• Also, it is assumed that another system can access the webserver remotely and signon to the Web application via its browser. This means that all the setup work for web.xml has been completed correctly.

Installing the NetViewWebApp Windows service:

(Default installation location is used throught for the example. Run all commands from a command prompt windows)
• cd c:\usr\lpp\netview\v6r2\bin
• WASService_wrapper.bat

After running the batch file, you should see a final displayed message:
"IBM WebSphere Application Server v8 - NetViewWebApp service successfully added."

Our webserver is now a windows service called "NetViewWebApp". The name to look for in the windows "Services" panel is the full title:
"IBM WebSphere Application Server v8 - NetViewWebApp".

Starting the NetViewWebApp Windows service:

• cd c:\usr\lpp\netview\v6r2\ewas\bin
• WASService -start NetViewWebApp

Now you can start/stop/disable this "NetViewWebApp" service from the Services panel or change directory into C:\usr\lpp\netview\v6r2\ewas\bin and run "WASService.exe" and it'll display other options that can be run from the command prompt (like those in the Service panel).

Using the NetViewWebApp Windows service:

• Reboot, but do not logon to your system:
After reboot, let the system quiesce a bit at Windows logon prompt, but do not logon. Wait for disk activity to level off since the webserver is starting under the Windows service.
• Try accessing the Web App via browser from other system:

Problem Determination for the NetViewWebApp Windows service:

If the Web App fails to display the NetView signon panel in the browser, then
• Possibly give more time for the Windows service to complete the initialization of the webserver.
• Log onto the PC running the NetViewWebApp Windows service and examine the nvsrvc.log file in C:\usr\lpp\netview\v6r2\bin. Nvsrvc.log should show status: Server server1 open for e-business
• See points listed above under subtopic "Initial assumptions for the NetViewWebApp Windows service".

Removing the NetViewWebApp Windows service:

To uninstall this Windows service previously installed, issue the following command from the c:\usr\lpp\netview\v6r2\ewas\bin directory:
WASService -remove NetViewWebApp

Known Defects

• Problems with "Save as" in Web XML Editor Utility

  When using the "Save as" feature with the utility, there are some problems related to the Java runtime. You can only "save as" to the current directory as shown in the open file window or to a file that already exists.

• Hot links not working for Japanese help panel in Japanese web browser

  The resulting data is corrupt when using "Search" against a command in the field "Enter a command or message" in the secondary web browser panel. This panel displays when, from a Japanese web browser, the "NetView Help" option (under the "NetView Support" heading) is selected on the main Tivoli NetView Welcome panel.

  An alternative work-around is to issue this same command (as displayed from the "NetView Help" panel) from NCCF or NetView command line.

• Error message displayed in English language in Japanese web browser

  When using the Japanese web browser, and your credentials are removed (for example, you click on the Sign Off hot link) or expired, and you attempt to display another NetView web page, the error message "CNM1210E No credentials exists to access NetView for z/OS CNM01." will be displayed in English in the browser.

Service History

• Further information regarding the NetView Web Application build level is contained in the file znetview_webapp.gen under the doc subdirectory of the installation location.

• 6.2.0.1:   OA43861
• 6.2.0.2:   OA45267
• 6.2.0.3:   OA45925
• 6.2.0.4:   OA46619
• 6.2.0.5:   OA47547
• 6.2.0.6:   OA48113
• 6.2.0.7:   OA48597
• 6.2.0.8:   OA49388
• 6.2.0.9:   OA49517
• 6.2.0.10:   OA49937
• 6.2.0.11:   OA50310

Documentation Changes

• None (GA version)

Getting Help

For Technical Information

We are ready to help you with your NetView Web application questions. You can contact us through standard problem reporting procedures.

Defect Reporting

For support for this or any Tivoli product, you can contact Tivoli Customer Support in the following way:

• Submit a problem management record (PMR) electronically from our Web site at
  https://www.ibm.com/support/entry/myportal

Customers in the United States can also call 1-800-IBM-Serv, #2. International customers should consult the Customer Support Handbook, which is available on our Web site:

• http://techsupport.services.ibm.com/guides/handbook.html

When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily. Company identification information may also be needed to access various online services available on the Web site.

The Customer Support Web site offers extensive information, including a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including Release Notes, Redbooks, and Whitepapers. The documentation sets for some product releases are available in both PDF and HTML formats. Translated documents are also available for some product releases.

Additional support is also available on the NetView group on Yahoo!. These forums are monitored by NetView developers who answer questions and provide guidance. When it appears that a problem with the code is found, you will be asked to open a PMR to get resolution. For information about registration and access to the NetView group on Yahoo!, look on Web page:

• http://groups.yahoo.com/group/NetView

To find documentation online, point your web browser at the following site and select "Product Documenation and Manuals" in the Learn section:

• http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliNetViewforzOS.html

We are very interested in hearing about your experience with Tivoli products and documentation. We also welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please contact us in one of the following ways:

• Send e-mail to johnlew@us.ibm.com
• Or visit web site: http://www-306.ibm.com/software/tivoli/contact.html

Determining Your Service Level

When reporting defects it will be necessary to provide Tivoli with your service level. You will receive instructions on how to do this when you contact Tivoli. You can view the file named znetview_webapp.gen under the doc subdirectory of the installation location. This file lists the level of maintenance of the NetView Web application.

Also once you are signed onto the NetView Web application, the service level of your application will appear on the About view.

Trademarks and Copyrights

The following terms are trademarks of the respective companies in the United States or other countries or both:

• IBM, the IBM logo, Tivoli, the Tivoli logo, WebSphere, AIX, POWER, APPN, BookManager, DB2, MVS/ESA, NetView, OS/390, VTAM and z/OS are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both.

• Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the United States, other countries, or both.

• Microsoft, Windows, Windows Server 2008, Windows Server 2012, and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

• UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group.

• Linux is a registered trademark of Linus Torvalds.

• SUSE is a trademark of Novell, Inc.

• Red Hat, RPM, and all Red Hat based trademarks and logos are trademarks
  or registered trademarks of Red Hat, Inc. in the United States and other countries.

• AMD, the AMD Arrow logo and combinations thereof are trademarks of Advanced Micro Devices, Inc.

• Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

• Yahoo!, the Yahoo! logo, and product and service names are trademarks of Yahoo! Inc.

• Google and the Google Logo and Google Chrome browser are registered trademarks of Google Inc.

• Other company, product, and service names may be trademarks or service marks of others.

• Third party license terms and conditions, notices and information

  The license agreement for this product refers you to this file, or to a file referenced by this file, for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided in the "LICENSE.TXT" and "NOTICES.TXT" files on the \license directory of the DVD for this product. These files are also installed into the doc product installation directory as part of the installation process. Please note that any non-English version of the information in this file is unofficial and is provided to you for your convenience only. The English version of the file is the official version.

Licensed Materials - Property of IBM
Product Number 5697-NV6
(C) Copyright IBM Corp. 2002, 2013. All rights reserved.


US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.