The information in this Readme pertains to the Novell ZENworks Reporting 5.6.1 release.
|
Item |
Requirements |
|---|---|
|
Processor |
Speed:2.0 GHz or faster Multi-core processor 4 to 8 Type: Server-class CPU such as AMD64 dual core or Intel EM64T dual core or faster |
|
RAM |
4 GB minimum; 8 GB and above recommended |
|
Disk Space |
60 GB minimum Additional hard disk 10 GB minimum; 15 GB and above recommended |
|
Supported Hypervisors |
Primary server software can be installed in the following virtual machine environments:
|
|
Web Browser |
The following web browsers are supported:
|
To replace the image in a report manually:
Launch Jaspersoft Studio.
Upload the image in the Repository Explorer as follows:
Right click on the corresponding report unit (folder) in the Repository Explorer.
Select New > Image and then click Next.
Specify Name, ID for the new image and press Next.
Upload the new image and then click Finish.
Open the .jrxml file for the report requiring the new image.
Click on the image (default logo) and go to Properties panel.
Go to Image and change the Expression attribute to "repo:<Name of the new image>"
Save the jrxml file to get these changes published.
To replace the default logo automatically:
Open the Terminal.
Go to /var/adm/reporting.
Type ./change-logo.sh and press Enter. Specify the path of the new image.
Logo is replaced only for ZENworks Reporting predefined reports.
For information about the new features in ZENworks Reporting 5.6.1, see What’s New in ZENworks 11 SP4 .
This section contains information about issues that might occur while you work with ZENworks Reporting 5.6.1:
Section 4.1, ZENworks Reporting Appliance System Requirements
Section 4.2, Problem connecting to Microsoft SQL Server running on a named instance
Section 4.8, In the Audit domain the comparison filters might not work as expected
Section 4.10, The Ad Hoc View might not display as expected if data policies have large datasets
For optimum results we recommend at least a 2.5 GHz multi-core processor.
During ZENworks Reporting configuration, you need to configure a ZENworks database as ZENworks Reporting datasource. If the ZENworks database is Microsoft SQL Server running on a named instance, the associated port is getting picked up incorrectly from the ZENworks configuration. This leads to datasource connectivity problem in ZENworks Reporting server which will then not function as expected.
Workaround: Before configuring ZENworks Reporting perform the following:
Windows:
Go to %zenworks_home%\conf\datamodel
Open the zdm.xml and zenaudit.xml files.
Search for the <entry key="Port"> text and update the value with the correct port number at which the named instance is listening.
Restart ZENworks services.
Linux:
Go to /etc/opt/novell/zenworks/datamodel
Open the zdm.xml and zenaudit.xml files.
Search for the <entry key="Port"> text and update the value with the correct port number at which the named instance is listening.
Restart ZENworks services.
For information, see Restarting the ZENworks Services in the ZENworks 11 Primary Server and Satellite Reference.
If you had been scheduled a report with "input controls" in ZENworks Reporting 5, after migrating to ZENworks Reporting 5.6.1 that scheduled report will display with no data.
Workaround: Reschedule the report after migrating to ZENworks Reporting 5.6.1.
User Source usernames and user-groups named with special characters might not work as expected.
Recommendation: Use alphanumeric characters and underscores for usernames and user-groups.
Rights associated with a particular usergroup will be applicable for all the groups with the same name.
For example, there are two usergroups companyname/companybu1/managers and companyname/companybu2/managers. You have assigned a set of rights to the first group, then the other group will also get these rights.
Workaround: Use unique name for usergroups.
After migrating from ZENworks Reporting 5 to ZENworks Reporting 5.6.1, Distinguished Name format may not be maintained for user-groups from the User Source.
Workaround: Using Groups Configuration delete the migrated groups and reconfigure them.
Double Byte language characters might not appear in report export outputs after migration if the ZENworks-Reporting-5-patch was not applied.
Workaround: Apply the ZENworks Reporting 5 patches before migration.
In the audit domain the string comparison filters such as 'starts with’ might not work as expected.
Recommendation: Use other filters to reduce the report data set.
Using the import option to move ZR resources from ZR 5 to ZR 5.6.1 might not work as expected.
Recommendation: Use the ZENworks Reporting migration utility to migrate ZENworks Reporting resources from ZENworks Reporting 5 to ZENworks Reporting 5.6.1.
When handling large datasets from a Domain source in the Ad Hoc Editor, fields summarized by distinct count are computationally intensive and Ad-hoc view might not display as expected.
Workaround: To design the Ad-hoc view as expected with large data:
Log into the ZENworks Reporting server, as an administrator.
Go to /opt/novell/zenworks-reporting/js/apache-tomcat/webapps/jasperserver-pro/WEB-INF
Open the applicationContext-adhoc-dataStrategy.xml file.
Search for the Bean – CountDistinct and search for tag Property name ="calcMethod"
Change the property to value ="sqlGroupBy"
Restart the ZENworks Reporting server.
Increasing the default value of crosstab.bucket.measure.limit makes the generated report export (pdf and Excel) operation failure.
Workaround: By default, the limit set by ZENworks Reporting measure is 100000. If the number of records exceeds the default limit, then report fails to generate. Increasing the default ZENworks Reporting measure limit might able to generate the report. However, the export operation of the generated report might fail. Hence, it is not recommended to change the default value instead increase the number of filters to reduce the output data.
When you run a large number of reports on a regular basis, based on the configuration, the ZENworks Reporting server might hang.
Workaround: Restart the ZENworks Reporting services.
ZENworks Reporting 5 requires a user source to be configured. Consider a scenario in which a ZENworks Reporting 5 administrator called admin1 exists in the configured user source. During ZENworks Reporting migration, you are prompted to configure a local ZENworks Reporting administrator. If the credentials of this administrator conflict with admin1, then the administrator privileges of both the administrators might get revoked.
Workaround: After migration, reconfigure the local Administrator from the ZENworks Reporting Appliance summary page.
This Readme lists the issues specific to ZENworks Reporting 5.6.1. For all other ZENworks 11 SP4 documentation, see the Novell ZENworks 11 SP4 documentation website.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2015 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.