Logi Ad Hoc v12.1 Overview

The Logi Ad Hoc Management Console is the primary management utility for the centralized administration of all Ad Hoc Reporting instances.

The Logi Ad Hoc v12 Help System provides you with everything you need to know to fully utilize all of the features of Logi Ad Hoc v12. This topic provides a brief explanation of Logi Ad Hoc v12, and you can access other relevant information using the links we have listed in this topic, looking at the Table of Contents, or by using Search.

Do not upgrade to JDK 8 release build 261 (1.8.0_261), or any later build of JDK 8. Doing so affects Logi Info and Logi Ad Hoc running the Java engine. If you perform this upgrade, your web server will stop responding indefinitely the first time it has to process a web request. This issue affects both Oracle JDK 8 and OpenJDK 8. This note will be updated when we have found a resolution.

This product is version specific and enables the System Administrator to:

  • Create and Configure Ad Hoc Reporting instances
  • Upgrade Ad Hoc Reporting instances to the installed version
  • Remove Ad Hoc Reporting instances
  • Exercise various utilities related to an Ad Hoc Reporting instance
  • Review Help information
  • Contact Support

This topic contains the following sections:

General Requirements

Here are the general requirements for the latest release of Logi Ad Hoc: 

Area Requirement


- Internet Explorer: 11 (Certified); see note below about earlier versions.
- Microsoft Edge (Certified)
- Firefox, Chrome: all current public versions (Supported).
- Opera, Safari: all current public versions (Supported). 


- 1.6 GHz or higher processor recommended; 400 MHz minimum required.
- 4 GB or higher RAM recommended; 2 GB of RAM minimum required.
- 1.5 GB of available disk space (with .NET already installed). 

Operating Systems:

- Windows Server 2012 R2, 2008, 2003
- Windows 10 (with Logi Info v12+ only)
- Windows 8 (all editions except RT)
- Windows 7 (all editions)
- SUSE, Red Hat, Ubuntu, CentOS, and most flavors of Linux
- Solaris, HP-UX (Limited support)

- 32-bit and 64-bit Windows OS supported
- 32-bit and 64-bit Linux OS supported 

Web Servers:

- Microsoft Internet Information Server (IIS) 7.x, 8.x
- Apache-Tomcat 6, 7, 8 (without Tomcat FHS)
- JBoss 4, 5, 7, EAP-6.3
- Sun GlassFish (SJSAS) 2.1, 3.0, 3.1
- BEA WebLogic 10
- Oracle WebLogic 12c
- IBM Websphere 7, 8.5 

Metadata Servers:

Logi Ad Hoc builds a metadata repository which can be created on any of the following database servers. All are available for .NET, only those with an asterisk (*) are also available for Java:

- Microsoft SQL Server CE (installed automatically during Logi Ad Hoc installation)
- Microsoft SQL Server
- MySQL *
- Oracle * 

Other Software:

The following components must be installed:

- Microsoft .NET Framework 4.x, or

- Official Sun Java Development Kit (JDK) 1.6, 1.7, 1.8 
(The JRE is not sufficient but OpenJDK 1.7 and JRockit 1.6 or 1.7 may be used)  

Data Sources:

Logi Ad Hoc v12 can retrieve data from any of the following database servers. All are available for .NET, only those with an asterisk (*) are also available for Java:

- DB2
- Informix
- Microsoft SQL Server
- MySQL*
- Oracle*
- PostgreSQL*
- Sybase

  • Microsoft Internet Information Server (IIS) must be installed before installing Logi products. Logi products for the Windows environment, and Logi Studio, require .NET Framework 4.x. If not already in place, with your consent, appropriate versions of the .NET Framework are installed when Logi products are installed. They are also available for free from the Microsoft Download Center.

  • Internet Explorer: While IE 7, 8, 9, and 10 are certified to work with Logi Ad Hoc v12.1, Microsoft ended support for these older IE versions on January 12, 2016 and does not recommend that they be used going forward. Logi Ad Hoc no longer works with IE 5 and 6. We recommend that you use IE 11 or Microsoft Edge for viewing applications built with Logi Ad Hoc v12.1 and later.

  • UN*X/Linux Users: More information about Java is available in Introducing Logi Reporting for Java.

Microsoft ended support for .NET Framework 4.0 and 4.5 on January 12th, 2016. We recommend use of 4.6.

Back to top

How Should Your Server Be Configured?

In a typical scenario with an average data size per report (less 10MB of data per report), you should be able serve 50-100 concurrent users per multi-core CPU on a production server, assuming a good amount of RAM (2GB+) and a fast hard drive (12K RPM+). Here are three representative configuration levels for the web server.

  1. A low-performance hardware configuration: 1 multi-core CPU, 2GB RAM, 12K RPM HD, 64-bit OS
  2. A better performance configuration (for more users or more data): Quad-Core CPU, 4GB+ RAM, 15K RPM HD, 64-bit OS
  3. The best performance configuration begins with the previous configuration and adds:  Additional CPUs (2 or more Quad-Core CPUs), more RAM (8GB+), 64-bit OS, or move to a clustered environment.

Here are a few general "rules of thumb" when considering server configuration options:

  • More Data and Data Complexity = More RAM
  • More Reports, Larger Reports, Complex Reports = Faster hard disk, more available hard disk space
  • More Traffic and Concurrent Visitors = More CPUs/Cores

Back to top

How Many Servers Do You Need?

Your production web server hosts your Logi Ad Hoc instances, which run as extensions to the web server. Ideally, this computer should be dedicated to this task alone.

However, other configurations are possible and feasible, including those in which the web server also serves other functions (i.e. is not dedicated to reporting alone) or the database server is also on the reporting server computer.

Which configuration should you use? We do not have guidelines based on specific numbers of users or reports to share with you; each deployment situation is different.

Whether you choose to combine functions (web server, Logi Ad Hoc instance, and database server) on one computer is, ultimately, your decision. Numerous factors can affect this decision, including the amount of web server traffic, the number of concurrent database users, the size of the databases, the complexity of the database queries, the frequency of report access, and, not least, cost.

You may care to begin with a combined configuration and, as your report usage grows, change to a dedicated configuration. The nature of Logi Ad Hoc allows you to do this easily and often without additional cost (if per-server CPU counts remain constant).

Recent studies concerning server virtualization suggest that database servers are frequently under-utilized. On the other hand, many database vendors recommend that their products be run on a dedicated server. You may wish to check with your database vendor for their recommendations concerning database servers.

Back to top

Server Virtualization

Many organizations are using server virtualization to maximize hardware usage and reduce costs.

Server virtualization products allow the assignment of CPU resources to processes. This may take the form of a maximum percentage of combined CPU utilization, or as specific allocation of logical CPUs, to a virtual machine (VM). The server administrator is responsible for making these configuration decisions. Logi Analytics' product licenses treat a VM just like a regular, non-virtualized server.

In order to ensure good performance in any virtualized server environment, administrators must be careful to allocate appropriate resources to VMs.

It's not uncommon to relocate a VM from one hardware platform to another, for example, for hardware maintenance. The Logi license will "move" with the VM, as long as the machine name remains unchanged.

Back to top

Product Expiration Information

Information about Logi products and versions that have reached the end of their life cycle can be found in Product Life Cycle.

Back to top