This section describes the Eagle Portal system requirements and provides steps for installing and logging in to the Eagle Portal.
NOTE: This section also includes steps for running a conversion utility as part of upgrading to Eagle Portal V12.X and higher from a pre-V11.0 Eagle Portal installation.
...
System Requirements
Eagle Portal is a standalone install and can be installed independently from other Eagle components. Eagle Portal requires a Windows Server 2008 or later with Microsoft .Net 4.5 installed.
The following browsers are compatible with the Eagle Portal:
Internet Explorer 9.0 or higher on the Web server.
Mozilla Firefox 3.5.1 or higher.
...
...
Run the Install
To install the Eagle Portal:
...
Locate Portal(.NET) in the Modules folder.
Run the setup.exe application on the server where you want to install the Eagle Portal.
You see the Eagle Portal InstallShield wizard.
...
Click Next.
You see the second InstallShield dialog box.
...
Click Next.
You see the Eagle Portal Website Configuration dialog box.
...
Click Communication to set the Application Server and file transfer options.
SOAP is the recommended protocol. Make sure you type the correct value for the SOAP port. The SOAP port was renamed in the Engine Manager to NxG Web Service Port. Make sure to use this port when configuring the Eagle Portal.Click Troubleshooting to set options including whether to use debug logging, debug XM, user error messages, and version information.
Click General to set options for the Eagle Portal session timeout due to inactivity, or Web site ID if using multiple Eagle Portals instead of a default website.
In Viewer URL, use a partial URL or absolute URL to specify the path of the ERX installation file. This is needed if your users do not already have ERX Viewer installed and they need to view ERX format reports in their Reports window. The path can be defined as http://website/location/erxviewersetup.exe.Click Login to set options for security or RSS feeds that are displayed in the Eagle Portal Login window.
If you configure the Eagle Portal website to use integrated security, only the Header Type is supported. Set Delimiter to \, Enabled to True, and enter AUTH_USER for Header. See the Customize the RSS Feed section for details.Click File and select Save & Validate.
Click Finish.
You see the final InstallShield Wizard dialog box.
...
...
Click Finish.
The
...
This section contains steps for running a conversion utility as part of upgrading to Eagle Portal V12.X and higher from a pre-V11.0 Eagle Portal already installed on your system.
If you have a pre-V11.0 Eagle Portal installed on your system and wish to upgrade to V12.X and higher, follow the conversion steps below.
...
Eagle Portal is installed.
The Portal User Store Conversion utility converts the following:
Dashboard charts
Query Views
Dashboard Views
Query Parameters
Query Default Views
Dashboard Parameters
Eagle recommends using this utility for the upgrade.
NOTE: If you decide not to use this utility, you will have to set up query views, dashboard parts, and dashboard views from scratch in the upgraded Eagle Portal environment.
...
The Portal User Store Conversion utility must run on the machine from which you launch the PortalStoreConverter.exe file.
Make sure this machine has access to both the source (Classic Eagle Portal) and destination (Eagle Portal V12.X and higher) environments.
You need access to the following in the source environment:
File location where the Classic Eagle Portal user file store is located. If you enter a network location, your machine must have read access to this folder and its subdirectories.
Network access to the AppServer being used for the Classic Eagle Portal AppServer.
Over the network access to the LOCATION and PORT in the Connection Settings dialog box.
Valid Eagle username and password for the AppServer.
...
Figure 5: Connection Settings Dialog Box
You need access to the following in the destination environment:
Network access to the AppServer being used for the V12.X AppServer.
Over the network access to the LOCATION and PORT in the Connection Settings dialog box.
Valid Eagle username and password for the AppServer.
...
To run the conversion from pre-V11.0 Eagle Portal to V12.X and higher:
Run the PortalStoreConverter.exe file located in the bin folder.
You see the Portal User Store Conversion Utility dialog box.
...
Figure 6: Portal User Store Conversion Utility Dialog Box
Click Browse and locate your existing Eagle Portal's UserFileStore.
Click User Info and enter your Eagle Portal login information, including User name, Password, and AppServer information such as location and port.
Click Verify to validate the information you have entered.
The Same as Source check box is selected by default.
If you want to use a different destination, deselect the Same as Source check box.
The Overwrite Existing Views check box is selected by default.
If you do not want to overwrite any existing views, deselect the Overwrite Existing Views check box
Click Load Views and Charts.
The views, charts, and view parameters are loaded,
Click Start Conversion.
You see the conversion Progress status bar at the bottom of the dialog box.
After the conversation is complete, you see the Conversion Success message.
...
Figure 8: Conversion Success Message
Review the conversion log file, conversion.log, located in the bin directory.
...
If the source AppServer is not communicating properly with the destination AppServer, you can copy your existing Eagle Portal's UserFileStore to another location.
NOTE: Make sure you copy the entire UserFileStore and all of its subdirectories.
This conversion utility expects that the destination database is an upgraded version of the source database and that the queries, dashboards, and parts from the source exist in the destination database.
Conversion may impact several Eagle Portal tables that depend on other Eagle Portal tables.
So, if you have to restore after you have run the conversion, you must either make sure that all Eagle Portal tables are unchanged (Eagle Portal tables start with portal_ and are located in the PACE_MASTERDBO database), or you must rerun the conversion utility.
...
Configure Eagle Portal Website for Integrated Security
If you are using integrated security, you need to complete additional steps.
You can configure the Eagle Portal website by using PortalCofiguration.exe and setting the following options:
Communication. Set Application Server and file transfer options.
Troubleshooting. Set options such as whether to use debug logging,
General. Set options for the Eagle Portal session timeout due to inactivity or Web Site ID if not using the default web site.
Login. Set options for Integrated Security or RSS feeds that display in the Eagle Portal login window.
...
If you are configuring the Eagle Portal website to use integrated security, only Header type is now supported. You need to set Delimiter to \, Enabled to True, and type in AUTH_USER for Header.
To configure for integrated security:
Locate the web.config file in the Web folder and open it using Notepad.
Make a copy of the original web.config file before making any changes.
In web.config, find <authentication mode="Forms"> and replace Forms with Windows if using Windows authentication. If using a third party authentication tool, replace Forms with None.
Save and close the web.config file.
Open IIS Manager.
Open the Properties section of the Eagle Portal website.
Select Directory Security.
Select Edit in the Authentication & Access Control section.
Disable Anonymous Access.
Select Integrated Windows Authentication.
Click OK to close the Properties dialog boxes.
Restart IIS.
Your Eagle Portal website is now configured to use integrated security.
...
...
Customize the RSS Feed
You can customize what your users see on the Eagle Portal Login window. The feed displayed on the Eagle Portal Login window is controlled by an XML file you can edit. RSS feeds require internet access to work correctly.
To customize the RSS feed:
Locate the file common/rss/eagle.xml in the Portal installation directory.
Open the file and enter the location of the RSS feed you want to display in the Eagle Portal Login window.
Save your changes and close the eagle.xml file.
...
...
Remove the RSS Feed
You can choose to display a blank Eagle Portal Login window to your users.
To remove the RSS feed:
Locate the directory where the Eagle Portal is installed.
Locate and run the file portalconfig.exe located in the Bin folder.
Select Login.
You see the Eagle Portal Configuration dialog box.
...
In the RSS Feeds section, remove the common/rss/eagle.xml file from the Top RSS feed URL section.
Once you remove this section, your users see a blank Eagle Portal Login window when they log in.
...
Customize the Look and Feel
You can customize the Eagle Portal look and feel by creating your own theme in the folder:
<Portal install directory>/Web/App_themes/. You can also customize the color palette that is used for charts throughout the Eagle Portal.
To customize the Eagle Portal theme:
Copy the existing Default folder from <Portal install directory>/Web/App_themes/.
Rename the folder to reflect the name of the theme. You will use the name of this folder in Step 5 of this procedure.
...
This folder contains the following types of files:
Images in the Images subfolder
ASP.NET skin files
CSS files
The main CSS for Eagle Portal is site.css, which contains the default settings for fonts, colors and logos in Eagle Portal.
...
Figure 10: Files in Default Folder
...