We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
Ginesys Reports Installation Guide
SUMMARY
Ginesys Reports is a self-service Business Intelligence solution that provides a unique balance of operational and ad-hoc reporting, dashboards and interactive data visualization for non-technical business users. End users can easily build and format analytics report. The Ginesys Reports module has to be configured before it can become operational. Follow the given steps to configure the Reports module in Ginesys.
DEPLOYMENT SCENARIOS
Ginesys Reports can be deployed in two ways. Though there is little difference in installation procedure in either scenarios, the differences are only in pre-requisites installation.
Common Applications Servers + DB server Model:
Ginesys Application and Report Application are installed in a single machine. Database may be installed in same or in another machine.
IMPORTANT
NOTE : If Ginesys Application and Report Application both are running on the same machine, it is recommended to create separate Application Pool (App Pool) for Report Application and assign the newly created App Pool for the virtual directory in which the report application resides.
Ginesys Reports Installation Guide#Individual Server Model:
Ginesys Application and Report Application are installed in separate machines. Database may be installed in Ginesys Application machine or in another machine.
DEPLOYMENT STEPS FOR COMMON APPLICATION SERVER + DB SERVER MODEL
PRE-REQUISITES
OS: Windows Server 2008 R2 or above
IIS Server Role
Framework V 3.5 SP1
Framework V 4.7.2
Oracle Client:
ODAC 12c 64 bit [If Ginesys Database is on Oracle Database 12c]
ODAC 11g 64 bit [If Ginesys Database is on Oracle Database 10g]
In case of single server deployment, all pre-requisites for Ginesys Reports would already be available on the server as those are as same as required for Ginesys Application.
IMPORTANT
Ginesys supports both Oracle Database 10g and 12c. If Oracle Database 10g is in use, then the required client would be ODAC 11g 64 bit and in case of Oracle Database 12c ODAC 12c 64 bit will be required.
STEP BY STEP INSTALLATION
Steps | Related resource | |
---|---|---|
1. | Download and extract Ginesys Report Kit
The adjacent figure shows the folder structure. | |
2. | Create an Application Pool for Ginesys Report Module - name it GinesysReportAppPool.
| Detailed info: How To: Create an application pool on a Web server |
3. | Create three new applications in IIS NOTEIf Ginesys Reports is being configured on same server where Ginesys Application is installed, then Ginesys Web Applications and Ginesys Report Applications will appear under same site, here it will be Default Web Site if the installation as it is done following this guide.
| Detailed Info: How To: Add an application in IIS manager Sample Image of IIS Manager with Report Applications created. |
4. | Add permission on new Applications On all three newly added applications, GINESYSReportUI, GINESYSReportAPI, GINESYSImages 'Full Control' access need to be given to 'IIS User' (IIS_IUSRS). Repeat the above steps for all three applications.
On all three applications, GINESYSReportUI, GINESYSReportAPI, GINESYSImages 'Full Control' access need to be given to 'IIS User' (IIS_IUSRS). To do this, Repeat the above steps for all three applications. | How to provide read and write access to Application Pool Identities |
5. | Modification of GinApps.Config Keys need to be added in its configuration files on GINESYS Application Server (File location:
<add key="ReportURI" value="/GinesysReportUI/" /> | |
6. | Starting up ASP.NET State Service Open Services management console (Go to RUN > Type Services.msc > Enter) Double click on ASP.NET State Service Set Startup Type: Automatic Click on Start button Click on OK button to close the window. Close Services management console. | |
7. | Install the Report Scheduler Windows Service:
cd <GINESYS Installed Drive>\GSL\GINESYS12\GinesysReportInstallReportSchedulerService -install <GINESYS Installed Drive>\GSL\GINESYS12\GinesysReport\ReportScheduler | |
8. | Provide access to Report Module -
| |
9. | Synchronize configuration of Ginesys Reports with Ginesys Application
| |
10. | Grant appropriate Report role to user
| |
11. | Verification for Database Connectivity In the Report Server tab, under | |
12. | Verification for Report Path Access In the same location, under | |
13. | Verification for Schedule Host Connectivity In the same location, under General>Scheduler Settings; Some setting details are shown on the right side (check attached image), click on the icon beside Schedule Remoting Host format - <channel_type>://<machine>or<ipaddress>:<port> (<machine> or <ipaddress> of Report server and scheduler service must be in running state) Sample value - tcp://SERVERNAME:2001 | |
14. | Opening the Report > Home Now the Report Home should open without any issues. | |
15. | Configuring the Repository Tab The report tree structure has to be created by the Admin user in the Repository tab. The report folders can be mapped by drag and drop Report folders from left side (Repository) into right side (Configurable View). IMPORTANT - Report Folder sequence
| |
16. | Configure the Scheduler following the steps given - (Optional) This step is only required if reports need to be scheduled to be send by auto-email. To configure the GINESYS Reports Scheduler Service API, edit the file ‘eWebReportsScheduler.xml’ in the folder where the scheduler service was installed. Location - <GINESYS Installed Drive>\GSL\GINESYS12\GinesysReport\ReportScheduler\eWebReportsScheduler.xml Set the following items - values within the brackets() are random sample values:
|
DEPLOYMENT STEPS FOR INDIVIDUAL SERVER MODEL
Prerequisites
In case of separate servers for the GINESYS Application, GINESYS Reports Application and the Oracle Database, the GINESYS Reports Server needs to have the following prerequisites installed -
ODAC 12c for Oracle 12c database (as mentioned before, if the Database is Oracle 10g then ODAC 11g would be needed)
Step by step installation
Steps |
---|
Need to enable IIS role.
|
Add file read and write access to both folders for Application pool user
|
Ginesys Reports Installation Guide#Modification of GinApps.Config |
Ginesys Reports Installation Guide#Install the Report Scheduler Windows Service: Open Command Prompt in Administration mode <GINESYS Installed Drive>\GSL\GINESYS12\GinesysReport\ InstallReportSchedulerService -install <GINESYS Installed Drive>\GSL\GINESYS12\GinesysReport\ReportScheduler |
Ginesys Reports Installation Guide#Provide access to Report Module |
Ginesys Reports Installation Guide#Verification for Database Connectivity |
Ginesys Reports Installation Guide#Verification for Report Path Access |
Ginesys Reports Installation Guide#Verification for Schedule Host Connectivity Sample value - http://dev-02/GINESYS12/Admin.aspx |
Ginesys Reports Installation Guide#Configuring the Repository Tab Admin user has to create or map the Report-Folder structure in Right Side Configurable View. |
Ginesys Reports Installation Guide#Configure the Scheduler following the steps given - (Optional) To configure the GINESYS Reports Scheduler Service API, edit the file ‘eWebReportsScheduler.xml’ in the folder where the scheduler service was installed. Location - <GINESYS Installed Drive>\GSL\GINESYS12\GinesysReport\ReportScheduler\eWebReportsScheduler.xml Set the following items - values within the brackets() are random sample values:
|