Note:
When you invoke zNetViewWebAppzLinux_en.bin, Linux will display the following status messages:
Initializing InstallShield Wizard Installer...
Preparing Java(tm) Virtual Machine...
...................................
...................................
.........................
Running InstallShield Wizard Installer...
The InstallShield panels that follow with this installation are
similar to the Window's version.
It is recommended, but not required, to use the default directory name of the target folder. The default path is "/usr/lpp/netview/v5r1".
Uninstalling the NetView Web Application from zLinux
-
Following these procedures if you previously installed using zNetViewWebAppzSeries.tgz (gzip file for RPM install):
- At the host, issue the following commands from a terminal session:
"cd /NVtemp" (assuming zNetViewWebAppzSeries.tgz was unzipped & untar'ed here)
"uninstall.sh" - The "uninstall.sh" shell script will let you select the features of NetView Web application
that you want to uninstall.
Note:
During the uninstall process, you may notice several messages similar to:
"cannot remove /usr/lpp/netview/v5r1/log - directory not empty"This is not a problem since the post-uninstall processing within RedHat Package
Manager will complete the removal of all NetView Web application files and subdirectories.
To uninstall the NetView Web application on from your Linux system follow the these steps:
-
Following these procedures if you previously installed using zNetViewWebAppzLinux_en.bin (InstallShield image):
- To uninstall the NetView Web application, you can run zNetViewWebAppUninstall.bin file that resides in
the /uninst subdirectory below your target installation path (this is the NETVIEW_HOME path).
Better yet, you can copy zNetViewWebAppUninstall.bin to another directory and run it there.
That will ensure that the /uninst subdirectory itself is removed as well. This is the recommended
procedure.
InstallShield will run the uninstall program which will present you with panel information that will let you select the feature(s) that you want uninstalled.
- After finishing the uninstallation process, be sure that all subdirectories and files
have been removed from the target folder. InstallShield will not remove files that have been
created dynamically. For example, if you used the default path, "/usr/lpp/netview/v5r1" as
the product installation path, then it would be sufficient to remove the "v5r1" subdirectory
or folder under "/usr/lpp/netview/".
Note:
DO NOT remove any installed files or subdirectories without first running the InstallShield's uninstaller file zNetViewWebAppUninstall.bin as described in step #1 above.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 Customization for NetView Web Application
Using the Web XML Editor Utility to edit the web.xml file
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.Modify the web.xml File
- 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. Note: If you are not using the Web XML
Editor Utility, the url-pattern is part of the servlet-mapping element.
- Modify the value of the HOST parameter to be the fully qualified hostname of your NetView
for z/OS domain (for example, nmp190.raleigh.ibm.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.
- In the web.xml file, the default value 'localhost' is specified as the IP address of the machine where the SNMP Server is running. If you are running the SNMP Server on a different machine than the Application Server, you will have to modify the web.xml file to specify the IP address of the machine where the SNMP Server is running. There are four places in the web.xml file (one for each SNMP servlet) where this needs to be specified. Change the value of the init-param SnmpServerHost for the MibServiceServlet, SnmpServiceServlet, DmpServiceServlet, and InstanceServiceServlet.
Post-Installation Customizations for Jetty
It is recommended that you use the Web XML Editor Utility to modify your web.xml file. See "Modify the web.xml File" under the section Using the Web XML Editor Utility to edit the web.xml file for information regarding this utility.If you are using the Jetty Web Server, it will be necessary to modify the web.xml file in the WEB-INF directory before starting Jetty. If you have chosen the default target directory during installation, the full path to this file will be usr\lpp\netview\v5r1\www\webapps\netview\WEB-INF. Although it is recommended to use the Web XML Editor Utility, you can use any ASCII editor to modify the web.xml file. Sections that need to be modified have been preceded with comments so they can be located easily.
Post-Installation Customizations for WebSphere
It is recommended that you use the Web XML Editor Utility to modify your web.xml file. See "Modify the web.xml File" under the section Using the Web XML Editor Utility to edit the web.xml file for information regarding this utility.
If you are using WebSphere, it will be necessary to modify the web.xml file that is imbedded in the zNetViewWebApp.ear file. If you have chosen the default target directory during installation, the full path to this file will be usr\lpp\netview\v5r1\ears. Although it is recommended to used Web XML Editor Utility, you can use the WebSphere Application Assembly Tool to modify the web.xml file for use with WebSphere. If you plan to use the Web XML Editor Utility, skip to the section titled Installing the Enterprise Application (.ear file) with the WebSphere Enterprise Application Wizard. Otherwise, continue to the next section.
- Start the WebSphere Application Assembly Tool:
Windows environment:
Start -> Programs -> IBM WebSphere -> Application Server V4.0 AE -> Application Assembly Tool
Unix environment:
Issue the following command from the /opt/WebSphere/AppServer/bin directory
./assembly.sh & - Click Cancel on the "Welcome to the Application Assembly Tool" window
- Click on File, then Open and navigate to the ears folder (usr\lpp\netview\v5r1\ears)
- Highlight the zNetViewWebApp.ear file and click OK
- On the left side of the Application Assembly Tool window
- Expand Web Modules
- Expand zNetView Web Application
- Expand Web Components
- Expand z/NetView Host Access Servlet
- Double click on Initialization Parameters
- On the right side of the window change the value of the HOST parameter to the fully qualified hostname of your host NetView (for example, nmp190.raleigh.ibm.com)
- Click Apply
- On the right side of the window change the value of the ZNV_DOMAIN parameter to the NetView for z/OS domain (for example, NTV74)
- Click Apply
- Verify that the values for the INKEY, OUTKEY and PORT parameters are correct and valid for your NetView host system.
- On the left side of the Application Assembly Tool window
- Double click on Servlet Mapping
- On the right side of the window change the value of the URL pattern for the accessServlet to the same value you assigned to ZNV_DOMAIN parameter (for example, ntv74).
- Be sure to keep the slashes and the asterisk intact.
- Click Apply
- On the left side of the Application Assembly Tool window
- Expand Mib Service Servlet
- Double click on Initialization Parms
- On the right side of the window change the value of SnmpServerHost to the IP address of the machine where SNMP Server is running.
- Click Apply
- On the left side of the Application Assembly Tool window
- Expand Snmp Service Servlet
- Double click on Initialization Parms
- On the right side of the window change the value of SnmpServerHost to the IP address of the machine where SNMP Server is running.
- Click Apply
- On the left side of the Application Assembly Tool window
- Expand Dpm Service Servlet
- Double click on Initialization Parms
- On the right side of the window change the value of SnmpServerHost to the IP address of the machine where SNMP Server is running.
- Click Apply
- On the left side of the Application Assembly Tool window
- Expand Instance Service Servlet
- Double click on Initialization Parms
- On the right side of the window change the value of SnmpServerHost to the IP address of the machine where SNMP Server is running.
- Click Apply
- Click File
- Click Save
- Click Cancel on the "Welcome to the Application Assembly Tool" window
- Click on File, then Open and navigate to the ears folder (usr\lpp\netview\v5r1\ears)
- Highlight the zNetViewWebApp.ear file and click OK
- On the left side of the Application Assembly Tool window
- Expand Web Modules
- Expand zNetView Web Application
- Expand Web Components
- Right click on Web Components
- Click New:
-
Assign a name and display name (your choice)
Keep component type as servlet. For class name, enter com.tivoli.nv390.webacc.servlets.FLB_NvServ
Select Load on Startup, and enter a priority value of 2.
Click OK
- You now see a list of the web components. You will need to add initialization parameters to your new
component. The easiest way is to copy an existing set and modify it. Use the set from the z/NetView
Host Access Servlet:
-
Double-click on the z/NetView Host Access Servlet
Double-click on initialization parameters
Using the mouse and the ctrl key, select all the parameters, then right-click and click Copy. - Now click on Web Components on the left:
-
Now double-click the new component you created and double-click Initialization Parameters.
On the right, right click and select Paste. - You have now copied the parameters. On the right side of the window change the value of the HOST parameter to the fully qualified hostname of your host NetView (for example, nmp190.raleigh.ibm.com).
- Click Apply.
- On the right side of the window change the value of the ZNV_DOMAIN parameter to the NetView for z/OS domain (for example, NTV74).
- Click Apply.
- On the left side of the Application Assembly Tool window
- Double click on Servlet Mapping
- Right click and select New
- Fill in a new URL pattern it should start with "/" and end with "/*"
- Using the drop down box, select your new servlet
- Click OK
- Click File
- Click Save
Using the WebSphere Application Assembly Tool to edit the web.xml file
If you need to have access to more than one NetView host, you will need to add additional access servlet definitions under the Web Components portion of the tree on the left in the Application Assembly tool. Only create a single servlet definition for each NetView domain; however, you can define multiple servlet-mappings that point to each servlet. Following are instructions for doing so after starting the Application Assembly Tool.
Installing the Enterprise Application (.ear file) with the WebSphere Enterprise Application Wizard
To install the Enterprise Application:- Start the WebSphere Application Server
Windows environment:
Start -> Programs -> IBM WebSphere -> Application Server V4.0 AE -> Start Admin Server
Unix environment:
Issue the following command from the /opt/WebSphere/AppServer/bin directory
./startupServer.sh & - Start the WebSphere Administrator's Console
Windows environment:
Start -> Programs -> IBM WebSphere -> Application Server V4.0 AE -> Administrator's Console
Unix environment:
Issue the following command from the /opt/WebSphere/AppServer/bin directory
./adminclient.sh & - Click on the Wizards button on the toolbar and choose Install Enterprise Application.
- Provide the node name of the machine where the zNetViewWebApp.ear file resides.
- Select the Install Application (*.ear) radio button.
- 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\v5r1\ears.
- Enter the Application Name (for example, 'NetView for z/OS Web Access')
- Click Next
- Click Next on the Mapping Users to Roles window
- Click Next on the Mapping EJB Run as Role to User Mapping window
- Click Next on the Bind EJB to JNDI Name Mapping window
- Click Next on the Mapping EJB References to EJBs window
- Click Next on the Mapping Resource References to Resources window
- Click Next on the Specifying the Default Datasource for EJB Module window
- Click Next on the Specifying Datasource for Individual CMP Beans window
- Click the Select Virtual Host button on the Selecting the Virtual Host for Web Modules window and choose the virtual host
- Click Next
- Click the Select Server button on the Selecting the Application Server window and choose the application server
- Click Next
- Click Finish
- Expand Nodes, right-click your node. Select "Regen Webserver Plugin'.
- Expand Nodes
- Expand the hostname directory (this is the hostname of your machine)
- Expand Application Servers
- Click on the server where you have chosen to run the zNetView Web application (for example, you can use the Default Server)
- On the right side of the window, click on Session Manager Service
- Click on the Edit Properties button
- In the General section, check the appropriate box for your operating environment.
- For these changes to take effect, stop the WebSphere Application Server by right-clicking your node and selecting Stop
- At the next panel, click Yes.
- Then restart the WebSphere Application Server
Windows environment:
Start -> Programs -> IBM WebSphere -> Application Server V4.0 AE -> Start Admin Server
Unix environment:
Issue the following command from the /opt/WebSphere/AppServer/bin directory
./startupServer.sh & - Restart the WebSphere Advanced Administrative Console, navigate to the Enterprise Applications and select the application name that you provided above for the NetView Web application (for example, "NetView for z/OS Web Access").
- Click the Start button in the toolbar.
Starting/Stopping the NetView Web Application
The nvsrvc Command
The nvsrvc command is used to start the Jetty Web Server and the SNMP Server. In the AIX environment, you must include the .sh extension when issuing the nvsrvc command (nvsrvc.sh).-
nvsrvc start webserver
-
This will start the Jetty Web Server. The Jetty window will contain several messages
including a message stating that the SocketListener has been started on port 8080.
Three log files will be created in usr\lpp\netview\v5r1\www\logs when the Jetty Web Server is started:
jetty.out - This log is written to each time the Jetty Web Server is started.
netviewservlets.log - This log contains information, warning and error messages generated during Jetty initialization or servlet processing.
year_month_day.requestlog - This log contains the requests made to the Jetty Web Server. The filename of this log is in the format of year_month_day.
-
nvsrvc start snmpserver
-
This will start the SNMP Server. The SNMP Server window will contain
"Processing file .." messages.
Any information, warning or error messages related to SNMP Server initialization will be written to the snmpserver.log file in usr\lpp\netview\v5r1\jars\logs. You may notice the following warning messages in the snmpserver.log file. These messages can be ignored.
WARN com.tivoli.netview.util.InetService - Unable to load 'utiljni':java.lang.UnsatisfiedLinkError: no utiljni (utiljni.dll) in java.library.path
-
nvsrvc start
This will start the Jetty Web Server and the SNMP Server.
To display help for this command, issue the nvsrvc command without any parameters.
Starting Jetty Web Server
Use the following command to start Jetty on your Web application Server.Note: D: drive is used as an example drive in the command below.
Windows Environment - execute the following:
D:\usr\lpp\netview\v5r1\bin\nvsrvc start
-- OR --
cd D:\usr\lpp\netview\v5r1\bin
nvsrvc start webserver
UNIX Environment - execute the following:
/usr/lpp/netview/v5r1/bin/nvsrvc.sh start
-- OR --
cd /usr/lpp/netview/v5r1/bin
nvsrvc.sh start webserver
Starting SNMP Server
If you plan to use the SNMP services provided by NetView Web application, you must start the SNMP Server. Use the following command to start the SNMP Server.Note: D: drive is used as an example drive in the command below.
-
Windows Environment - execute the following:
-
D:\usr\lpp\netview\v5r1\bin\nvsrvc start
-- OR --
cd D:\usr\lpp\netview\v5r1\bin
nvsrvc start snmpserver
UNIX Environment - execute the following:
/usr/lpp/netview/v5r1/bin\nvsrvc.sh start
-- OR --
cd /usr/lpp/netview/v5r1/bin
nvsrvc.sh start snmpserver
Starting the Web XML Editor Utility
This utility enables you to edit the web.xml file that is used by the WebSphere and Jetty web servers. Consult the online help available with this feature for detailed information.
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\v5r1\wxe\bin
WxeEditor.bat
UNIX Environment - execute the following:
cd /usr/lpp/netview/v5r1/wxe/bin
WxeEditor.sh
Starting your Internet Browser
To display the 'Welcome to NetView' screen from your Internet Browser (Netscape or Internet Explorer), task DSIWBTSK must be ACTIVE on the NetView for z/OS system.
If you are using Jetty, point your web browser to http://hostname:8080/netview/servletMappingName/
Note that port 8080 is the default port specified in the jetty.xml file. If you have modified this file to use
a different port you must specify that port in the URL.
If you are using WebSphere, point your web browser to http://hostname/netview/servletMappingName/
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.
servletMappingName is the name that you specified in the servlet-mapping definition in the web.xml file (if you are using Jetty) 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. NOTE that the SLASH ('/') at the end of the URL is REQUIRED.
Sign on to NetView using a valid user name (NetView operator ID) and password.
Modifying the Default MIB Definitions
The NetView Web application is shipped with a default set of MIB definitions which are included when you start the SNMP Server. MIB definitions are specified in a file named mibserver.def which resides in the usr\lpp\netview\v5r1\mibs directory. The mibserver.def file can be modified to include additional MIB definitions or exclude existing MIB definitions. Refer to the mibserver.def file for the complete list of MIBs shipped with the NetView Web Application.
Hints and Tips for the NetView Web Application
- How to enable debugging for servlets
The log file for servlet processing is named netviewservlets.log and it resides in /usr/lpp/netview/v5r1/www/logs. If you wish to enable debugging for classes under com.tivoli.netview.snmp you need to change the word 'INFO' to 'DEBUG' in the following line in the log4j.properties file in /usr/lpp/netview/v5r1/www/classes.
log4j.category.com.tivoli.netview.snmp=INFO
- How to enable debugging for SNMP Server
The log file for the SNMP Server is named snmpserver.log and it resides in /usr/lpp/netview/v5r1/jars/logs. If you wish to enable debugging for classes under com.tivoli.netview.snmp and under ibm.nways.jdm you need to change the word 'INFO' to 'DEBUG' in the following two lines in the snmpserver-log4j.properties file in /usr/lpp/netview/v5r1/jars/logs.
log4j.category.com.tivoli.netview.snmp=INFO
log4j.category.ibm.nways.jdm=INFO
- How to modify the log settings
The default size for netviewservlets.log and snmpserver.log is 100KB. Once a log is full, it is renamed with a '.1' suffix and a new '.log' file is created.
The log4j.properties file in /usr/lpp/netview/v5r1/www/classes and the snmpserver-log4j.properties file in /usr/lpp/netview/v5r1/jars/logs can be modified to change the maximum size of these logs. Modify the value specified on the MaxFileSize statement in the properties file if you want to change the log size.
If you want to increase the number of saved log files, modify the value specified on the MaxBackupIndex statement.
- How to activate the 3270 web application
NetView includes a non-supported application that translates native 3270 panels into HTML and displays them in the web browser. You can enable this application by adding it to the web portfolio. For details and help for the application, see the online help file FKXY3270.HTML. This file can be found in the usr/lpp/netview/v5r1/www/webapps/netview directory.
- NetView Web Application and Integrated TCP/IP Services Component
The NetView Web application and the Integrated TCP/IP Services Component utilize certain similar components. If both the NetView Web application services and the Integrated TCP/IP Services Component are to be active on the same Linux for zSeries LPAR, the jetty component of one of these must be configured to use a unique port number.
If the NetView Web application is to be modified, edit the file /usr/lpp/netview/v5r1/www/conf/jetty.xml.
If the Integrated TCP/IP Services Component is to be modified, edit the file /usr/OV/www/conf/jetty.xml.
In either file, look for the line:
<Set name="Port">8080</Set>
And change the port number from 8080 to a unique number (for example 8081) for that machine.
Operating System Environment Information
AIX environment
For AIX 4.3.3, the Recommended Maintenance Level is 09. This maintenance package is intended for customers who already have AIX 4.3.3 installed. The AIX 4330-09 maintenance package can be downloaded from http://techsupport.services.ibm.com/rs6000/fixes/, using APAR number IY22024. If you are a licensee of AIX 4.3.3, you can obtain an Update CD by contacting your point of sale and requesting feature code 0838.
For AIX 5.1, the Recommended Maintenance Level is 01. This maintenance package is intended for customers who already have AIX 5.1.0 installed. The AIX 5100-01 maintenance package can be downloaded from http://techsupport.services.ibm.com/rs6000/fixes/, using APAR number IY21957. If you are a licensee of AIX 5.1, you can obtain an Update CD by contacting your point of sale.
Note: Before updating your AIX 5.1.0 system to the AIX 5100-01 maintenance level, you must first apply and commit APAR IY19375 (which includes bos.mp64 5.1.0.1, bos.mp 5.1.0.1, and bos.up 5.1.0.1). Run smitty update and pick IY19375 to install. When the installation completes you must reboot your system. After the system has rebooted, you can then install the AIX 5100-01 maintenance level. After the maintenance level has been installed, you must again reboot. See the AIX 5L for POWER Version 5.1 Release Notes for more information. APAR IY19375 can be obtained from the AIX Electronic Fix Distribution site: http://techsupport.services.ibm.com/rs6000/fixes/.
If you are using one of the supported non-UTF8 CKJ locales, the following fileset (available on both AIX 4.3.3 and AIX 5.1 base CDs) is required:
For Japanese users, if you are using Japanese Input Method, you may apply the following PTFs to avoid some Input Method related problems.
zLinux environment
We refer to Linux on zSeries as zLinux. In the context of NetView Web application product, zLinux can generically refer to either SuSE Linux Enterprise Server for S/390 version 7.0 which is a SuSE 7.0 source base or SuSE Linux Enterprise Server 7 for S/390 and zSeries which is a 7.2 source base. Specifically, the formers abbreviated title is 31-bit SLES 7.0 or just SLES 7.0 while the latter is referred to as 31-bit SLES 7 or just SLES 7.
New enhancements
- None
Known defects
- AIX Netscape browser and getting a message about not being authenticated.
If you are using the Netscape browser on the AIX platform, and you launch the MIB Browser or Real Time Poller applet, a message is displayed stating that you are not authenticated. This problem occurs when using cookies to manage session tracking. The problem exists in the Java plugin, and a permanent fix will be available in the near future. A temporary workaround is to use URL re-writing for session tracking. See the NetView for z/OS Security Reference for more information on authenticating access to NetView by a web browser and session tracking.
- Problems with "Save as" in Web XML Editor Utility
When using the "Save as" feature with the utility, there are some problems that are 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.
- Scroll Bar Warning Messages during the AIX installation of NetView Web Application
This problem occurs during both English and Japanese installs on AIX 5.1 and 4.3.3.
As you move forward during install, selecting each InstallShield panel, a warning message is displayed on the terminal session:
-
Warning: 2054-901
Name: scrollbar
Class: XmScrollBar
2054-448 The scrollbar page increment is less than 1.
This anomaly will not affect the installation of any of the features you select to install. You can ignore these warning messages.
- Blank Splash panel during AIX installation for Japanese ja_JP locale
The initial InstallShield panel (Splash panel) that displays the product title will appear blank when attempting to install on AIX with Japanese locale ja_JP. This problem does not affect the rest of the installation. All of the subsequent panels will be displayed correctly.
- Garbage characters are displayed at the beginning of the install for AIX ja_JP locale
English characters are being displayed at the terminal session during the beginning of the AIX install for locale ja_JP only. These characters can be ignored. The installation process is not affected.
- During the Japanese installation, the first InstallShield panel after the initial Splash panel displays
"Back/Next/Cancel" pushbuttons truncated.
During AIX Japanese installation, one of the InstallShield panels displays only part of each pushbutton. Resizing the panel will properly display these pushbuttons so you can continue with the installation process. This occurs with ja_JP and Ja_JP locales.
- 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.
- Text in titles on the Netscape browser are truncated for Japanese AIX
Text in the title field of the Netscape browser may be truncated horizontally using the Japanese version of NetView Web application on AIX. A display resolution of 1024x768 is recommended.
- 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
- This is NetView Web Application fixlevel 5.1.0.2
- APAR OA01833
- APAR OA04937
- This is NetView Web Application fixlevel 5.1.0.3
- APAR 0A19486
- Further information regarding the NetView Web Application build level is contained in the file zNetViewWebApp_en.gen under the /doc subdirectory.
Documentation Changes
- Service Level: 5.1.0.3
- Updated information in this file for "Service History".
- Additional information added concerning install and uninstall of Web Application on zLinux platform.
- New installation filenames.
- JRE runtime levels remain the same. Patch info about DST fix support as been included.
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 one of the following ways:
- Submit a problem management record (PMR) electronically from IBMSERV/IBMLINK
- Submit a problem management record (PMR) electronically from our Web site at http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliNetViewforzOS.html
Customers in the United States can also call 1-800-237-5511. International customers should consult the Customer Support Handbook, which is available on our Web site at 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 an IBM supported external NetView newsgroup or 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.
- To access the external NetView newsgroup through your browser use the URL: news://news.software.ibm.com/ibm.software.netview
- For information about IBMLINK registration and access, look on the IBM Web page:
http://www.ibmlink.ibm.com - For information about NetView group on Yahoo! registration and access, look on the Web page:
http://groups.yahoo.com/group/NetView
To find documentation online, point your web browser at http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliNetViewforzOS.html and click on "Library" under "Related Links".
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
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 edit or type the file named zNetViewWebApp_en.gen (in the product "\doc" subdirectory) which lists the level of maintenance of the NetView Web application.
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, APPN, BookManager, DB2, MVS/ESA, NetView,
OS/390, TME, VisualAge, 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.
- Sun, SPARC, SunOS, and Solaris, java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
- HP-UX and Hewlett-Packard are trademarks of Hewlett-Packard Company.
- Microsoft, Windows, Windows NT, Windows 2000, 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 SuSE 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. - Yahoo!, the Yahoo! logo, and product and service names are trademarks of Yahoo! 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" file on the \readme\enu directory (in Unix, the /readme/enu directory) of the first installation CD-ROM for this product. The "LICENSE.TXT" file is also installed into the "doc" product installation subdirectory 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.
Product Number 5697-ENV
(C) Copyright IBM Corp. 2002. All rights reserved.
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.
Last Updated: January 31, 2007