Application Launcher can use the HTTP or HTTPS protocol to send event information as XML data to the Desktop Management Application Reporting servlet (zfdamrServlet). The servlet processes the messages and adds them to a database compliant with JDBC, such as the Sybase database included with ZENworks.
To set up XML reporting, you need to complete the following tasks:
The Reporting servlet requires one of the following server environments. The version numbers listed are minimum version requirements.
|Server||Java Servlet Engine||JVM|
NetWare 6.5 (Support Pack 1 or later)
Novell JVM* for NetWare 1.4.2
NetWare 6 (Support Pack 2 or later) 1
Novell JVM* for NetWare 1.3.1
Windows 2000 (with latest service pack)
Sun JDK 1.3.1_01
1 Support Pack 2 or later is required. Without Support Pack 2 or later, the Reporting servlet causes server utilization to jump to 100% and remain there.
For information about installing Tomcat on NetWare 6.5, see the NetWare 6.5 documentation.
For information about installing Tomcat on NetWare 6, see the NetWare 6 documentation.
For information about installing Tomcat on Windows 2000, see the Apache Tomcat Web site.
Make sure the server environment where you are installing the Reporting servlet meets the software requirements listed in the previous section, Meeting the Reporting Servlet Requirements.
Copy the zfdamrServlet.war file from the Desktop Management server's sys:\public\reporting\canned\nal reports directory to the Tomcat webapps directory.
Restart Tomcat to expand the zfdamrServlet.war file.
If you don't want to restart Tomcat, use the tools provided with Tomcat to expand the file.
The Reporting servlet needs to know information about the database to which it will write the reporting events. To provide this information:
Open the web.xml file. The file is located in the Tomcat webapps\zfdamrservlet\web-inf directory
If you are using a Sybase database, locate the dbip parameter, then change the parameter value to the IP address of the database server. The IP address is the only parameter you need to modify for a Sybase database.
If you are using a database other than Sybase, modify the parameters, described below, as required by your database. If you are using a Microsoft SQL database, follow the directions in TID 10094306.
dbuser: Specify a user name that has Write access to the database. Read access is not required. The preconfigured user name (MW_DBA) is the default Read-Write user name for a Sybase database created by the Desktop Management Server installation program. If you are using a ZENworks Sybase database and have not changed the default Read-Write user name, you do not need to modify this parameter.
dbpasswd: Specify the password for the user name specified in the dbuser parameter. The preconfigured password (novell) is the default Read-Write user's password for a Sybase database created by the Desktop Management Server installation program. If you are using a ZENworks Sybase database and have not changed the default Read-Write user's password, you do not need to modify this parameter.
dbport: Specify the port where the database is listening. The preconfigured port (2638) is the default NetWare server port for a Sybase database created by the Desktop Management Server installation program. If you are using a ZENworks Sybase database installed on NetWare and have not changed the default port, you do not need to modify this parameter.
dbdriver: Specify the full class of the driver to use when accessing the database. The drive must support the protocol listed in the dbprotocol parameter. For Sybase, this is com.sybase.jdbc2.jdbc.SybDriver (the preconfigured value).
Save the file.
Before Application Launcher can report application events through XML, you need to:
To activate an XML Targets policy and associate containers with it:
In ConsoleOne, right-click the Service Location Package you want to use, then click Properties.
If you do not have a Service Location Package, right-click the container where you want to create one, click New, then click Policy Package. Follow the instructions provided in the Policy Package Wizard to create a Service Location Package.
On the General page, check the box in the Enabled column to enable the XML Targets policy.
Select the XML Targets policy in the list, then click Properties to display the XML Targets properties page.
Click Add to display the XML URL dialog box, enter the URL where you want the XML data sent, then click OK to add the URL to the list.
The URL needs to include the port number, which by default is port 8080 on Windows or on NetWare, and 8180 on OES Linux and SLES. This port is the default Tomcat port in these environments, and is necessary for the Service Location Policy for XML reporting to find the zfdamrServlet running on Tomcat.
The URL for the Reporting servlet on Windows or NetWare would be:
and the URL for the Reporting servlet on Linux (OES Linux or SLES) would be:
where ip_address is the IP address or DNS host name of the server where the Reporting servlet is running.
Repeat Step 4 to add additional URLs.
When you are finished adding URLs, click OK to return to the General page.
Click Associations to display the Associations page.
You use this page to associate the Service Location Package with the containers where the users or workstations reside whose XML reports you want sent to the Web URL. If a parent container includes several containers where User and Workstation objects reside, you can select the parent container rather than each individual container.
Click Add, browse for and select the container you want to add, then click OK to add it to the list.
Repeat Step 8 to add additional containers.
When you've finished adding containers, click OK to save the information.
After you've enabled the XML Targets policy, you can start configuring Application objects to use XML reporting. Because event reporting is configured on a per-application basis, you can choose which applications you want to collect event reports for and which ones you don't.
For detailed instructions about configuring an application to use XML reporting, see Configuring Applications to Use Reporting.