test

Sun Java System Portal Server 7.2 Installation and Configuration Guide

Creating a New Portal Using the CLI

After creating a Portal Server installation on a node, you can create another Portal Server installation on the same node or different nodes using the same Access Manager and Directory Server. This new Portal Server installation is empty. You can use the sample portals provided to customize the portal for your specific needs. For example, you could create portals for different departments of an organization but still use the same Access Manager and Directory Server.

This section explains about creating a new portal installation on the same node or different node depending on your first Portal Server installation.

Creating a New Portal on the Same Node

When you create a new portal on the same node where you have the first Portal Server installation, you need to create a web container instance. Then, you need to duplicate the Webcontainer.properties file that is available in the Portal Server installation directory and modify the Webcontainer.properties file to direct to the new web container instance. Finally, you can run the psadmin create-portal sub command to create the new portal.

ProcedureTo Create a New Portal on a New Domain of Application Server 9.1

  1. Create a new domain, seconddomain, on port 8100.

    /ApplicationServer_base/appserver/bin/asadmin create-domain --adminport 4850 --adminuser admin --instanceport 8100 seconddomain

  2. Start the new domain.

    /ApplicationServer_base/appserver/bin/asadmin start-domain --user admin seconddomain

  3. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS91 file to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

  4. Edit the following properties in the secondportal.properties file.

    • Host=myhostname.mydomain

    • Port=8080

    • Scheme=http

    • WebContainerType=SJSAS91

    • WebContainerInstallDir=/opt/SUNWappserver/appserver

    • WebContainerInstanceName=server

    • WebContainerDomainName=seconddomain

    • WebContainerInstanceDir=/opt/SUNWappserver/appserver/domains/seconddomain

    • WebContainerDocRoot=/opt/SUNWappserver/appserver/domains/seconddomain/docroot

    • WebContainerAdminHost=myhostname.mydomain

    • WebContainerAdminPort=4850

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=admin

    • WebContainerAdminPassword=Application Server admin password

    • WebContainerMasterPassword=Application Server master password

    • ClusterID=cluster id

  5. Create the new portal.

    PortalServer_base/SUNWportal/bin/psadmin create-portal -u amadmin -f ps_password -p -secondportal --uri /portal -w secondportal.properties

  6. Restart the web container.

  7. Verify that the new portal has been created.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

Creating a New Portal on a Remote Node

This section explains how to create a new portal on a remote node. When you create a new portal on a remote node, you should install Access Manager SDK (AMSDK) and a compatible web container. When you install AMSDK, you need to provide the details of Access Manager and Identity Server that you installed for the Portal Server installation. You need to install Portal Server in the Configure Now or Configure Later mode. All the procedures that are explained in this section use the web container of the first portal installation for the second portal installation on a remote node.

Note –

When you install AMSDK, provide the same encryption key, am password, and LDAP password that are used for Access Manager on Node 1.

After you install AMSDK and the web container, you can use any one of the following options to create a new portal:

ProcedureTo Create a New Portal on Application Server 9.1 in the Configure Now Mode

Before You Begin

Ensure the following:

  1. Invoke the Portal Server 7.2 GUI installer and select Application Server 9.1, Access Manager SDK, and Portal Server and install them in the Configure Now mode.

  2. Provide the Access Manager host and the Directory Server host information.

  3. Change the name of the portal.

    For example, first portal will be portal1. Change the second portal name to portal2.

ProcedureTo Create a New Portal on Application Server 9.1 in the Configure Later Mode

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Application Server 9.1 in the Configure Now mode using the Java ES installer.

  2. Start the Application Server 9.1 Administration Server.

    ApplicationServer_base/appserver/bin/asadmin start-domain --user admin_user --password admin_password domain-name

  3. Install Portal Server in the Configure Later mode using the Portal Server 7.2 GUI installer.

  4. Complete the Portal Server installation.

    PortalServer_base/bin/psconfig --config example7.xml

To Configure Common Agent Container When Running as Root and Portal Running as Non-root

Follow these steps when the Common Agent Container process is running as root and Portal Server is running as non-root. If the Common Agent Container process is running as the same non-root user as Portal Server, skip the following steps.

ProcedureTo Create a New Portal on Application Server 9.1 Using the psadmin Command

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Application Server 9.1 in the Configure Now mode using the Java ES installer.

  2. Start the Application Server 9.1.

    ApplicationServer_base/appserver/bin/asadmin start-domain --user admin_user --password admin_password domain-name

  3. Run the installer and install Portal Server software in the Configure Later mode.

  4. Configure Common Agent Container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  5. Verify that the Common Agent Container is working properly.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

  6. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS91 file to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

  7. Edit the following properties in the secondportal.properties file.

    • Host=hostname.domain

    • Port=8080

    • Scheme=http

    • WebContainerType=SJSAS91

    • WebContainerInstallDir=/opt/SUNWappserver/appserver

    • WebContainerInstanceName=server

    • WebContainerDomainName=domain1

    • WebContainerInstanceDir=/opt/SUNWappserver/appserver/domains/domain1

    • WebContainerDocRoot=/opt/SUNWappserver/appserver/domains/domain1/docroot

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=4848

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=admin id

    • WebContainerAdminPassword=ApplicationServer admin password

    • WebContainerMasterPassword=ApplicationServer master password

    • ClusterID=cluster id

  8. Create the new portal.

    PortalServer_base/SUNWportal/bin/psadmin create-portal -u amadmin -f ps_password -p secondportal --uri /portal -w secondportal.properties

  9. Restart the web container.

  10. Verify that the new portal has been created.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

Deploying Sample Content to a New Portal

When you create a new portal, it does not have any sample portal deployed in it. However, you can deploy sample portals such as community sample, enterprise sample, and developer sample to the new portal.

ProcedureTo Deploy a Sample Content to a New Portal

  1. Copy the /PortalServer-base/SUNWportal/samples/portals/shared/input.properties.template file to the /var/opt/SUNWportal/tmp/input.properties file.

    In the Linux platform, copy to the /var/opt/sun/portal/tmp/input.properties file.

  2. Edit the input.properties file that you created in the /var/opt/SUNWportal/tmp directory with the following values.

    • ps.config.location=%PS_CONFIG_LOCATION%

    • ps.portal.id=%PORTAL_ID%

    • ps.access.url=%PORTAL_ACCESS_URL%

    • ps.webapp.uri=%PORTAL_WEBAPP_URI%

    • search.access.url=%SEARCH_ACCESS_URL%

    • search.id=%SEARCH_ID%

    • am.admin.dn=%AM_ADMIN_DN%

    • default.org.dn=%DEFAULT_ORG_DN%

    • portlet.dn=%PORTLET_DN%

    • ps.profiler.email=%PROFILER_EMAIL%

    • ps.profiler.smtp.host=%PROFILER_SMTP_HOST%

  3. Copy the /PortalServer-base/SUNWportal/samples/portals/shared/password.properties.template file to the /var/opt/SUNWportal/tmp/password.properties file.

    In the Linux platform copy the file to the /var/opt/sun/portal/tmp/password.properties directory.

  4. Edit the /var/opt/SUNWportal/tmp/password.properties file and set proper passwords.

    • amadminPassword=%AMADMIN_PASSWORD%

    • amldapuserPassword=%AMLDAPUSER_PASSWORD%

    • userManagementPassword=%USER_MANAGEMENT_PASSWORD%

      You can ignore this value if you are not setting up Communication channels.

  5. Run the following command.

    export JAVA_HOME=/usr/jdk/entsys-j2se

  6. Run the following command to deploy all the portals.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location=/var/opt/SUNWportal/tmp/ -logfile /var/opt/SUNWportal/tmp/log-file.txt

  7. (Optional) Run the following command if you wish to deploy only the enterprise portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location=/var/opt/SUNWportal/tmp/ enterprise -logfile /var/opt/SUNWportal/tmp/log-file.txt

  8. (Optional) Run the following command if you wish to deploy only the sand box portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location=/var/opt/SUNWportal/tmp/ sandbox -logfile /var/opt/SUNWportal/tmp/log-file.txt

  9. Restart the web container.