Configure InfoGo for Developers
InfoGo is a complete Logi application distributed with the Self-Service Reporting Module. It provides a complete self-service reporting experience for users.
The following topics discuss how to configure the application after it's been installed:
- Upgrade Considerations
- Completing the Installation
- Integrating the Discovery Module
- Specifying Application Metadata
- Configuring Scheduler and SMTP Services
- Managing Scheduled Reports
- Configuring Security
- Configuring InfoGo Constants
- Enabling Panel Content Editing
- Setting Up Sharing
- Designating a Global Main Page
- Creating a Global Menu
- Working with Gallery Files
- Customizing Appearance
- Customizing InfoGo Files
- Embedding InfoGo
About the InfoGo Application
Introductory information about the Self-Service Reporting Module (SSRM) and directions for installing it can be found in Install the Self-Service Reporting Module. If you haven't read it already, we recommend you do so before proceeding.
The SSRM includes a complete Logi application, InfoGo. It allows users to create and share visualizations, dashboards, and reports at runtime, and can be used as is or as a template for your own applications.
Unlike the Sample Applications on DevNet, InfoGo is distributed complete with Logi Engine files - these include required code and you should not downgrade this application to an earlier engine version or it may cease to work.
InfoGo is an extremely advanced example of Logi Info programming. It uses highly customized code and specialized techniques that may not work if copied into other Logi applications. While you can customize some portions of it, pulling it apart and reusing code in other applications, as you might with a regular Logi Sample Application, may not work well.
You can use the InfoGo application right where it was installed, configuring and modifying it right in its installation location. The default installation location is C:\Program Files\Logi Analytics\InfoGo. However, this approach requires extreme vigilance when applying Logi upgrades and is therefore dangerous.
Our Best Practices recommendation is that you not run the program from there. Instead, leave those files untouched and use them as your "reference model", a pristine set of files that can be copied whenever needed to new applications in other locations (such as C:\inetpub\wwwroot) for customization, registration, and use with your web server. As with any Logi app, you can deploy instances using the Application Deployment tool in Logi Studio.
For example, if you want to deploy InfoGo as a Java-based application:
- Install the SSRM, including the InfoGo application, as usual.
- Use Logi Studio to create a new Java application.
- Copy all the folders and their contents from the installed InfoGo application root folder to the new Java application root folder, except bin and rdTemplate.
- Copy InfoGoReportManagementPlugin.jar from the applications _SupportFile folder to the new Java application's WEB-INF\lib folder.
- Ensure that the copied folders have inherited the file access permissions of the Java application root folder.
Configure the Java application as described in this topic, and make any customizations you desire.
If you want to deploy InfoGo as a.NET-based application:
Install the SSRM, including the InfoGo application, as usual.
Use Logi Studio to create a new .NET application.
Copy all the folders and their contents from the installed InfoGo application root folder to the new .NET application root folder, except bin and rdTemplate.
Give full control to IIS_IUSRS on the .NET application root web folder (and its subfolders).
Ensure that the copied folders have inherited the file access permissions of the .NET application root folder.
Configure the .NET application as described in this topic, and make any customizations you desire.