1. Sampling the Horizon Information Portal Administration 4.0 Steven J. Orton Education Services

2. The Upgrade Portal Administration is not managed from a browser (New client provides more tools and greater flexibility New Dynix Client (Horizon 8.0 ‘look and feel’) 7.4 Horizon continues to use the Horizon Client

3. Horizon 4.0 Client

4. Changes that will not port over Tab colors Tabs or sub-tabs that are links Multiple search tabs Style sheet changes Changes to variables Changes to wording Categories Custom changes to languages Library Hours

5. Features that will be coming with 4.1 Kids HIP ADA

6. New “Mind-Set” Design your portal for guests Design your portal for empowering your authenticated users Tabs and Tabs Globes Jboss restarting rarely needed Live examples of HIP 4.0 are now available at : http://library.pittstate.edu/staff/susan/ ipac/chip4.html http://library.pittstate.edu/staff/susan/ ipac/chip4.html

7. Installing the Clients Horizon 7.4 HIP 4.0 Java 1.4.2 (Do NOT install or upgrade Java to 1.5)

8. JBoss Use some type of Remote Access software to connect to the HIP server to access JBoss. Run JBoss (HzAppServer40) as a service or in a window. All 3.0 HIP services are now a component of the one HzAppServer40 service.

9. When You Must Restart JBoss Changing any of the Marc Maps in Horizon (to see the changes in HIP) Changing your Circ Parameters in Horizon Changing Index Servers or Indexer Setup in Keyword Searching Switching portal layouts Creating a ZServer or making any ZServer changes Adding “More by” to the full bib After changing a template guest user in Portal Properties > Branding Setting up browse scoping (for searching) Creating an new Search Group

10. Agency Agency is a unit or a sub-unit of a library. It may be part of consortium, an independent institution, a branch, or any other division. An Agency may have sub-agencies You do NOT need a separate Agency for each location.

11. Target Setup

12. Profile Setup A Profile determines the settings and policies for your Portal. You do NOT need a separate profile for each Portal. A 3.0 Profile is not the same as a 4.0 Profile. 3.0 Profiles = 4.0 Portal Properties. The Upgrade process creates a separate Profile for each 3.0 Profile. Consolidate and organize profiles.

13. Profile Policy

14. Search SubTab HIP 3.0 was designed around the Tabset. HIP 4.0 is designed around channels. The Search SubTab is a channel. The Search SubTab consists of Search Groups. You do NOT need a separate Search SubTab for each Portal. The search tab of the 3.0 Tabset = 4.0 Search SubTab. The Upgrade process creates a separate Search SubTab for each 3.0 Profile. Consolidate and organize Search SubTabs. Eliminate Search Groups that are not being used by a Search SubTab.

15. Portal Property--Profile The Profile setting ties the Property to the Profile Policy and the Search Subtab.

16. Portal Property--General The General tab controls the entry code. Use the Open Portal button to launch a Portal

17. Portal Property--Branding Contains the path to the logo. Contains the link text (Library Name).

18. Portal Properties—Skins (default)

19. Portal Properties—Skins brushed_metal

20. Portal Properties—Skins (bluesky)

21. Portal Properties—Skins (default— dnxuser and dnxguest)

22. Defining the Portal Create an Administrator to setup the portal for guests. Create an Administrator to setup the portal for “logged-in” users. Assign the Guest Administrator and the User Administrator to the branding for the Portal. Login as the User Administrator to make custom changes. Save the user as the template user and save the layout. Restart JBoss. Login as the Guest Administrator to make custom changes. Save the user as the template user and save the layout.