test

Sun Java System Portal Server 7.2 Installation and Configuration Guide

Setting Up Portals Using the Administration Console

A portal consists of one or more portal server instances that deliver the same content and are mapped to a single Uniform Resource Locator (URL). The content and services delivered by a portal are common to all its instances.

Multiple portals share the same user set. These portals can be deployed on one or more hosts, but they all share the same user repository — the same Access Manager and the Directory server.

Note –

Portals that use different Access Managers are not multiple portals. They are independent and unrelated portals, each with its own set of users.

Access Manger can be a collection of its own instances, all using the same set of Directory Server instances. Different Access Managers are two unrelated Access Managers, not different instances of the same Access Manager.

This section explains how to complete the following tasks:

ProcedureTo List Portals

You can view a list of Portal Servers that are already set up.

  1. Login to the Portal Server Management Console by using http://hostname.domainname:port/psconsole.

  2. Select the Portals tab.

Equivalent psadmin Command

The equivalent Portal Server administration command to list portals is psadmin list-portals -u amadmin -f ./ps_password_file. The ps_password_file file contains the amadmin password.

For more information on the psadmin list-portals subcommand, refer the psadmin list-portals in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

ProcedureTo Create a Portal

During Portal Server installation, a default portal named portal1 is created. You can also create a new portal server using the Create Portal wizard.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Click the New Portal button to launch the wizard.

  4. Provide a unique name for the Portal Server, for example, portal5.

  5. Type a URI that enables end users to access the Portal Server, for example, /portal.

  6. (Optional) Change the default web container instance properties.

    For information, see Creating a New Portal Using the CLI section in the Sun Java System Portal Server 7.2 Installation and Configuration Guide.

  7. Verify the information you supplied.

  8. Click Finish to create the new portal.

  9. (Optional) View the log file to monitor the process.

    1. Login to the machine where portal is to be created.

    2. Run the psdadmin set-logger command.

      ./psadmin set-logger -u uid -f password -m component-type -O logger-name -L log-level

Equivalent psadmin Command

For more information on the psadmin create-portal subcommand, refer the psadmin create-portal in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

Templates for webcontainer.properties for supported web containers are in the portal-install-dir/template directory.

ProcedureTo Delete a Portal

You can delete all existing instances of a portal on all hosts and clean up the portal's data in the Access Manager LDAP directory.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. From the list of portals, select the portal you want to remove, and click the Delete Portal button.

Equivalent psadmin Command

For more information on the psadmin delete-portal subcommand, refer the psadmin delete-portal in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

ProcedureTo Export Portal Data

You can archive the following portal data in a par file:

After you archive data, you can import the data to the same portal or to a different portal. To export a portal from psconsole:

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Select a portal from the table.

  4. Click the Export button.

  5. Specify the par file location on the Portal Server machine and what you want to export:

    • All Desktop data — the exported par includes file system data and display profile data

    • File system data only — the exported par file includes only the desktop file system data, which is data deployed into the portal desktop and portal web-src

    • Display profile data only — the exported par includes only display profile data

Equivalent psadmin Command

For more information on the psadmin export subcommand, refer the psadmin export in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

Note –

This command does not support user data in the Directory Server.

ProcedureTo Import Portal Data to a Portal

You can import into any portal any portal data that you previously exported.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Select a portal from the table.

    The Import Desktop Data page appears.

  4. Click the Import button and specify the following:

    • The par file path for the imported data. The par file must be located on the Portal Server system.

    • Whether to continue if the storage structure of the portal does not match the archived file you want to import.

  5. Redeploy the portal web applications.

    1. Schedule a time to run the psadmin redeploy command.

      Plan to do this step off hours or in system maintenance mode, when your system is not in production. This action redeploys the portal war file, and it logs out users who are running a Desktop, causing them to lose their work.

    2. Run the psadmin redeploy command.

      psadmin redeploy -u amadmin -f passwordfile -p portalID --allwebapps

Equivalent psadmin Command

For more information on the psadmin import subcommand, refer the psadmin import in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

Note –

This command does not support user data in the Directory Server.