Portals

 

Each Arena installation includes three portals. Each portal is a separate set of pages, modules, and security settings. Portals use the primary domain information from your IIS (Internet Information Services) website host headers to direct web traffic from a particular domain to a specific Arena website such as your Arena-managed website. Each portal is designed to have a distinct URL so keep in mind which portal you are accessing within the same browser. Toggling between portals in the same browser session could result in the browser caching to the previously selected portal.

If your organization elected to install two instances of Arena—Production and Sandbox, you have a total of six default portals—the three default listed portals for each instance. The instances are separate and do not have any shared files or data. (Work performed in an Arena Sandbox instance does not convert nor connect with the Arena Production instance. For Hosted clients, you can request a local installation for testing purposes.)

The paths in Arena’s web.config file route users to the specified home page and login. When a user accesses Arena, regardless of the person’s location, the web server consults the web.config file as referenced in IIS. The web.config file has a default portal ID. The web server then queries the Arena database to determine the page to display and if the user is required to login.

•Arena (Portal 1 = Staff) – This is the primary portal designed to be used by staff on a day-to-day basis. This is a default portal.

•Arena Web (Portal 2 = Members) – This is the member portal designed to be used by prospects, guests and members of your organization. This is a default portal.

•Arena Mobile (Portal 3 = Staff) – This is the mobile portal designed for staff and is accessible using any browser-enabled smart phone. This is a default portal.

•Donation Kiosk (Portal 4 = Staff + Members) – This is an optional portal you can install from Arena Hub where staff can process contributions from a browser enabled device using a card reader. (This is not a default portal but is available for download on the Arena Hub page.)

 

Click any portal to display the portal details.

•Portal ID – This is the ID number of the portal. When accessing different portals in the same browser, it is suggested to use the portal ID to point to the specific portal to avoid browser caching to the previous portal such as, http://arena/default.aspx?portal=1&refreshcache=true.

•Portal Name – This is the name of the portal.

•Portal Title – This is the portal title.

•Portal Description – This is the description of the portal.

•Portal Notes – This is an optional field for portal notes.

•Default Page ID – This is the landing page for the portal.

•Portal Style Sheet – This is the default cascading style sheet for the portal. You can set a different CSS for any page in the Page Details.

•Tree Style Sheet – This is the default page tree style sheet. This CSS is used for tree styles unless specified otherwise on the specific page.

•Navigation Style Sheet – This the default navigation style sheet. This CSS is used for tree styles unless specified otherwise on the specific page.

•Login Page ID – This is the page for members to login.

•Not Found Page ID – This is the page to direct users to when a page is not available.

•Person Popup Page ID – This is the page that displays the person pop-up information.

•Default Domain – This is the portal domain.

•Mobile – Check this box if the portal is for mobile devices.

•Authentication – Authentication options are Forms Authentication or Windows Authentication. Hosted clients use Forms Authentication. Self-hosted can select Forms or Windows Authentication.

•JQuery Include – This is the AJAX query to exchange data with the server and update parts of a web page without reloading the whole page.