Adding Customizations
This chapter offers some general guidelines regarding customizations.
Key Concepts
This chapter describes a few customizations that you might want to make. It is not intended to be a comprehensive list, but it includes likely candidates for customization and a few general guidelines for making changes.
Note that generally, customizations should be made in the following places:
The Portal design themes screen in Site Manager
The ClientConfig folder
The Web.config file
Customizations made in other locations are not guaranteed to be preserved during upgrades.
The Portal Design Screen
The Portal design themes screen in Site Manager provides tools that allow you to:
Upload a logo to serve as the masthead image for the portal.
Customize the color scheme of the portal.
Add additional customizations to the custom.CSS file.
For more details, see the sections that follow in this chapter.
The ClientConfig Folder
The ClientConfig directory exists specifically to hold customizations, so this is an ideal place in which to store files and make modifications. By default, the ClientConfig directory is at the following location:
Drive:\Program Files\Jenzabar\ICS.NET\Portal\ClientConfig
In general, in order for the system to begin honoring changes made in the ClientConfig directory, you will have to do an iisreset after making the change.
The Web.config File
You may also want to modify the Web.config file. For more details, see Modifying the Web.config File.
The Web.config file includes a number of settings that you can use to fine-tune the behavior of the portal. This section highlights a few specific areas you may want to review.
Note that during upgrades, the JICS installer should preserve any modifications you have made to Web.config. Still, you should always back it up prior to an upgrade.
If You Want to Increase the Maximum File Upload Size
Before going live with your JICS installation, you should be aware of the maximum file upload standards that are set up for your system. If a user tries to upload a file greater than the maximum, the system will display a 413 “entity too large” error. Some common large-upload scenarios include the following:
You transfer data from your ERP system to JICS using Jenzabar’s Data Import Service (DIS). This process is described in your ERP system’s documentation. The initial upload will be large, as might others in the future, depending on the strategy you establish for using the DIS.
Users may at times upload large files, in particular via the Course Content Import feature, which is part of e-Racer.
By default, the limit set by JICS is 1GB. If want to modify this, you do so in the Web.config file. In both Server 2008 and 2012 environments, the maximum file upload size is set by the maxAllowedContentLength parameter, which is measured in bytes. (JICS sets this value to 1073741824.)
If the Windows Folder Is Not Located on the C Drive
If the WINDOWS folder is not located on the C drive, you will have to change the value of the ChartImageHandler parameter. This key establishes a temporary storage location for chart images used by the system. The default value of this parameter is one of the following:
On 32-bit systems,
storage=file;timeout=20;dir=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files;
On 64-bit systems,
storage=file;timeout=20;dir=C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files;
If you need to change the value of this parameter, make sure the new target is configured to give “Full Control” to the Network Services user account.
If You Want to Use SSL
If you’re using SSL, you will need to modify the PageBaseProtocol parameter.