Using the JICS Reporting Services Reports
If you have activated usage statistics logging, you may want to download and use a series of prepackaged reports that can be used in conjunction with Reporting Services, an optional component of SQL Server.
These reports will tell you the average duration of user sessions, the average page loads per session, and other statistics. If appropriate, you can provide easy access to the reports by adding the Reporting feature to your site.
For more on what exactly the reports show, see the Reporting section. In general, to use these reports, you complete the following tasks:
Checking Reporting Services requirements
Obtaining and importing the reports
Managing permissions
Configuring the URL used by the Reporting feature
Adding the Reporting feature to a page
Background
JICS uses a system of logging that was introduced in version 7.1.0 and significantly updated in 7.4.0. So if you have recently upgraded from a pre-7.1.0 version of JICS, you will notice many differences. If you are upgrading from 7.1.0 or later, you will notice some differences, though perhaps not as many.
Checking Reporting Services Requirements
Review this section to make sure your Reporting Services setup meets the requirements for the reports provided by Jenzabar.
Making Sure the Needed Services are Enabled
To use the JICS reports, you need to make sure the following two Reporting Service features are enabled:
Scheduled Events and Report Delivery
Web Service and HTTP Access
The way you do this may vary depending on your version of SQL Server. For example, in SQL Server 2008 R2, you can either edit the rsreportserver.config file, or you can connect to the Reporting Server using SQL Server Management Studio and use the View Facets feature.
For further help managing these settings, refer to Microsoft’s msdn web site (http://msdn.microsoft.com/library/default.aspx).
Meeting Installation Requirements
In both SQL Server 2008 R2 and 2012, note that Reporting Services must have been installed in either “default configuration (native mode)” or “files-only mode”—not in “default configuration (SharePoint integrated mode).”
Further, if you installed in files-only mode, make sure you review Meeting the Configuration Requirements.
Meeting the Configuration Requirements
If you installed SQL Server 2008 R2 or 2012 in “default configuration (native mode),” then the minimum configuration was completed for you automatically as part of the installation.
If you installed in files-only mode, then you have to complete a few extra steps. Specifically, make sure you have done each of the following:
Configure the web service URL
Configure the report server database
Configure the Report Manager URL
You can do this using the Reporting Services Configuration Manager (Start > All Programs > Microsoft SQL Server 2008 R2 or 2012 > Configuration Tools > Reporting Services Configuration Manager). Once you open the tool, you will see icons on the left side of the screen that correspond with each of these tasks. For help with any of this configuration, refer to Microsoft’s msdn web site (http://msdn.microsoft.com/library/default.aspx). As you go through the process, note that the default values suggested by the application should be acceptable for use with JICS.
Verifying that Report Manager is Available
Before proceeding, make sure that Report Manager is configured properly by opening a browser on the database server and navigating to one of the following URLs:
http:Name of the server hosting Reporting Services/Reports
http:Name of the server hosting Reporting Services/Reports_InstanceName)
Verifying that Reporting Services Service is Running
Before you can use Reporting Services in conjunction with JICS, you should make sure the Reporting Services service is running, using the Start > Administrative Tools > Services screen. The Reporting Services service will be listed as SQL Server Reporting Services (instance name).
Obtaining and Importing the Reports
To use the JICS reports, you need to transfer them to your system and import them into Reporting Services.
You obtain the reports from MyJenzabar, Jenzabar’s support site.
To obtain the reports:
Log in to MyJenzabar (https://www.myjenzabar.net/ICS/).
Choose Support > JICS – CRMs > JICS Downloads for your ERP system > JICS V9.3.x Framework Installers and Documentation.
The archive containing the reports, SST_ReportingServicesReports.zip, should be located on this page.
Download SST_ReportingServicesReports.zip and copy it to the web server (or the server of your choice).
Extract the file into a new directory called SST_ReportingServicesReports. Note that the directory should contain eight .rdl files.
This section explains how to create a data source for JICS and import the reports.
To import the JICS reports:
Log in as someone with administrative privileges to the server where you saved the reports.
Open a browser and navigate to one of the following URLs as appropriate:
http:Name of the server hosting Reporting Services/Reports
http:Name of the server hosting Reporting Services/Reports_InstanceName)
Create a folder named Jenzabar:
Click the New Folder icon.
In the New Folder dialog box, enter Jenzabar.
Click OK.
Open the Jenzabar folder link and, within it, create a folder named Site Stats:
Click the New Folder icon.
In the Site Stats dialog box, enter the name New Folder.
Click OK.
Open the Site Stats folder.
While in the Site Stats folder, click New Data Source.
The system displays the New Data Source screen.
In the screen displayed, set the following values:
Name: Enter the name of your logging database (by default, this was ICS_NET_STAT).
Hide in list view: Select or deselect this as appropriate for your site.
Enable this data source: Make sure this field is checked.
Connection Type: Set the drop-down list to Microsoft SQL Server.
Connection String: Enter the connection string for the logging database. You can find this by logging in to JICS and choosing Site Manager > Framework settings > Site Stats. Copy the value displayed after the Logging connection string area.
An alternate way of getting this data is to query the main JICS database. This value is stored in the FWK_ConfigSettings table, with the key LoggingConnectionString.
Connect using: Make sure that Credentials stored securely in the report server is checked.
User name: RSReporter
Password: The default password is RSReporter. If you change this, make sure you also change it in SQL Server.
Click the Test Connection button to verify that a connection can be made with the details you entered. If the system returns an error, make changes and try again.
Click OK.
The system again displays the Site Stats folder, this time with one item—your new data source.
While still in the Site Stats folder, upload the needed files:
Click Upload File.
On the Upload File screen, click the Browse button.
In the Open File dialog, browse to the SST_ReportingServicesReports folder (to which you extracted the eight .rdl files).
Upload each report by selecting and clicking Open. Then, on the Upload File screen, select OK. Continue until you have uploaded all the reports.
Managing Permissions in the Usage Statistics Feature
To make sure the appropriate users can access the JICS reports, complete the tasks described in this section.
Log in to the web server as a user with administrative access to the Reporting Tool.
Open a browser and navigate to one of the following URLs:
http:Name of the server hosting Reporting Services/Reports
http:Name of the server hosting Reporting Services/Reports_InstanceName)
Within the browser, the Report Manager interface displays.
In the upper-right corner of the screen, click Site Settings.
The system displays the Site Settings screen.
In the area of the screen labeled Security, click Configure site-wide security.
Click New Role Assignment.
The system displays the New System Role Assignment screen.
In the Group or user name field, enter ReportsUsers.
Select the System User checkbox.
Click OK.
The system again displays the System Role Assignments screen, this time with the ReportsUsers group listed.
Click on the Home link in the top right of the page.
The system displays the main view.
Click the Properties tab.
Click the New Role Assignment button.
The system displays the New Role Assignment screen.
In the Group or user name field, enter “ReportsUsers” (without quotation marks).
Select the checkbox that corresponds with the Browser role.
Click OK.
All users in the ReportsUsers group should now be able to navigate and view report data.
Before proceeding, you must create a Windows group for Reporting Services and add the appropriate users to it.
To create a Reporting group:
Log in to the server where Reporting Services is installed as someone with administrative privileges.
Choose Start > Control Panel > Administrative Tools > Computer Management.
The system displays the Computer Management screen.
In the left-hand pane, select Local Users and Groups.
In the right pane, select Groups.
Choose Action > New Group.
The system displays the New Group dialog box:
In the Group name field, enter ReportsUsers.
Use the Members field to identify people who should be allowed to view report data.
Click Create.
Close the New Group screen.
Close the Computer Management screen.
Configuring the URL Used by the Reporting Feature
If desired, you can add the Reporting feature to JICS so that authorized users can easily navigate the reports from within the portal. If you plan to do this, you should make sure that the Reporting feature is configured to use the right URL, as described below.
To configure the URL used by the Reporting feature:
Log in to JICS as someone with administrative privileges.
Click the user icon and select Site Manager from the drop-down menu.
The system displays the Site Manager screen, with the Site settings tab selected.
Click the Framework settings tab.
Select Location from the drop-down list at the top of the screen.
Check the Reporting tool field. The value in this field should match the name of the virtual directory for Report Manager. By default, the value of this field is /Reports. However, if the name of your virtual directory uses the Reporting Services instance name—for example Reports_SQLSERVERR2—you will need to change the value to /Reports_SQLSERVERR2.
Make any changes necessary and click Save.
Adding the Reporting Feature to a Page
When you place the Reporting feature on a page, note that there are no there are no permissions settings for this feature—so you should be careful to place the feature on a page that only authorized users can see.
Regardless of where the feature is placed, unauthorized users will be unable to view report data (because the system looks at the user’s Windows credentials, which you set up in Managing Permissions in the Usage Statistics Feature).
For help adding a feature to a page, see Working with Features. For details about the content of the reports, see the Reporting section.