test

Sun Java System Portal Server 7.1 Configuration Guide

Installing Portal Server 7.1 on a BEA WebLogic 8.1 Managed Server

You can create a managed server in WebLogic and use the managed server as the web container of Portal Server. You can install Access Manager on a managed server or administrator server of WebLogic.

To install Portal Server on a managed server of WebLogic, you need to:

ProcedureTo Install Portal Server on a WebLogic Managed Server

Before You Begin

Install Access Manager on the administrator server of WebLogic 8.1.

  1. Start the WebLogic administrator server.

  2. Add the IP address of the machine, which has the administrator server of the domain in the BEAWebLogic_base/weblogic81/common/nodemanager/nodemanager.hosts file.

    By default, the nodemanager.hosts file is located at the WebLogic_base/usr/local/bea directory.

  3. Start the WebLogic node manager with the IP address of the host as the first argument and the port number on which you want the node manager to run as the second argument.

    For example, WebLogic_base/weblogic81/server/bin/startNodeManager.sh 192.192.10.12 7878

  4. Log in to the WebLogic administrator console.

  5. Select Machines.

  6. Select Configure a New Machine.

  7. Type a machine name and click Create.

  8. Select the Node Manager tab.

  9. Specify the IP address of the host in the listen address and specify the port on which the Node Manager is running.

  10. Select Servers in the left pane to create a new managed server.

  11. Select Configure a New Server.

  12. Specify the server name and machine name and specify the listen port of the managed server.

  13. Start the managed server from the WebLogic administration console.

ProcedureTo Install Portal Server on a Managed Server in the Configure Now Mode

Before You Begin

  1. Install Portal Server in the Configure Now mode using the Java ES installer.

  2. Select the WebLogic container in the WebLogic container panel.

  3. Specify the administrator port as 7001 and the server port as the port of the managed server instance.

  4. Select Managed Server option.

  5. Restart WebLogic server after the successful installation of Portal Server.

ProcedureTo Install Portal Server on a Managed Server in the Configure Later Mode

Before You Begin

  1. Install Portal Server in the Configure Later mode using the Java ES installer.

  2. Complete the Portal Server installation.

  3. Change the example files depending on your requirements.

    For WebLogic, you can use the example15.xml file to configure Portal Server and Search Server. In the example15.xml file, ensure that the Port is set to port of the managed server, web container administrator port is set to 7001, and web container managed server is set to true.

  4. Configure the common agent container.

    PortalServer_base/bin/psconfig --config example15.xml

    The psconfig utility is located in the PortalServer_base/bin directory. It is located in the PortalServer_base/SUNWportal directory. For Linux, this utility is located in the PortalServer_base/sun/portal directory. It is located in the PortalServer_base/samples/psconfig directory for Solaris. It is located in the PortalServer_base/samples/psconfig directory for Linux.

    Note –

    For more information on the appropriate sample, see the PortalServer_base/samples/psconfig/README.txt file.

  5. Restart WebLogic server after the successful installation of Portal Server.

ProcedureTo Install Access Manager on a BEA WebLogic Managed Server

In this section, you install Access Manager on a managed server of BEA WebLogic.

  1. Install BEA WebLogic 8.1 using the installer.

  2. Create WebLogic domain and start administrator server.

    /usr/local/bea/user_projects/domains/domain1/startWebLogic.sh

  3. Access the administrator server of BEA WebLogic.

    http://host.domain-name:7001

  4. Create a managed server.

  5. Start the Java ES installer. Install Directory Server, Java DB 10. 2 and Web Server in the Configure Now mode.

  6. Start the Directory Server instance.

  7. Install Access Manager in the Configure Later mode.

  8. Customize the amsamplesilent file.

    The amsamplesilent file is located in the following directories:

    • Solaris platform: /AccessManager_base/SUNWam

    • Linux platform: /AccessManager_base/sun/identity

    Set the values in the amasamplesilent file as follows:

    • DEPLOY_LEVEL = 1

    • SERVER_NAME =AM_HOSTNAME without FQDN

    • SERVER_HOST = $SERVER_NAME.domain-name

    • SERVER_PORT =MANAGED_SERVER_INSTANCE_PORT

    • ADMIN_PORT = 7001

    • DS_HOST =DS_HOSTNAME with FQDN

    • DS_DIRMGRPASSWD =Directory Manager Password

    • ROOT_SUFFIX = root suffix of Access Manager

    • ADMINPASSWD =AM_PASSWORD

    • AMLDAPUSERPASSWD =LDAP_PASSWORD

    • COOKIE_DOMAIN = .domain-name

    • AM_ENC_PWD =any string of 12 characters

    • NEW_OWNER = root

    • NEW_GROUP = other (root for the Solaris 10 release and Linux and other for the Solaris 9 release)

    • PAM_SERVICE_NAME = other

    • WEB_CONTAINER = WL8

    • BASEDIR = Access Manager install directory., for example, /opt

    • AM_REALM = disabled

    • WL8_HOME =WebLogic install directory., for example, /usr/local/bea)

    • WL8_PROJECT_DIR = user_projects

    • WL8_DOMAIN = Domain name., for example, mydomain

    • WL8_CONFIG_LOCATION = $WL8_HOME/$WL8_PROJECT_DIR/domains

    • WL8_SERVER = Instance name., for example, myserver

    • WL8_PROTOCOL = $SERVER_PROTOCOL

    • WL8_HOST = $SERVER_HOST

    • WL8_PORT = $SERVER_PORT

    • WL8_SSLPORT = $ADMIN_PORT

    • WL8_ADMIN = Administrator name of WebLogic., for example, weblogic

    • WL8_PASSWORD = WebLogic administrator password

    • WL8_JDK_HOME = $WL8_HOME/jdk142_05 for WebLogic 8.1 service pack 4 or $WL8_HOME/jdk/142_08 for WebLogic 8.1 service pack 5

  9. Run the following command.

    AccessManager_base/bin/amconfig -s amsamplesilent

  10. Log in to the WebLogic administrator console.

  11. Deploy the Access Manager war files, such as amserver.war, ampassword.war, amconsole.war, and amcommon.war available in the AccessManager_base directory.

    1. In the scripts, remove the following classpaths: AccessManager_base/SUNWam/lib/jaxrpc_1.0/jaxrpc-api.jar and AccessManager_base/SUNWam/lib/jaxrpc_1.0/jarpc-ri.jar.

    2. In the scripts, add the following classpaths: AccessManager_base/SUNWam/lib/jaxrpc-api.jar, AccessManager_base/SUNWam/lib/jaxrpc-impl.jar, and AccessManager_base/SUNWam/lib/jaxrpc-spi.jar.

    3. (Optional) For Linux, remove the following classpaths: AccessManager_base/identity/lib/jaxrpc_1.0/jaxrpc-api.jar and AccessManager_base/identity/lib/jaxrpc_1.0/jarpc-ri.jar from the startweblogic.sh and startManagedweblogic.sh scripts.

    4. (Optional) Add the following classpaths: AccessManager_base/identity/lib/jaxrpc-api.jar, AccessManager_base/identity/lib/jaxrpc-impl.jar, and AccessManager_base/identity/lib/jaxrpc-spi.jar

  12. Restart WebLogic server and access the administrator console.

    http://host.domain-name:managed-server-port/amconsole

ProcedureTo Install Portal Server in the Configure Now Mode on a WebLogic Managed Server Where Access Manager is Installed on a Managed Server

  1. Create a managed server.

  2. Install Access Manager on the managed server.

  3. Set -Dcom.iplanet.am.serverMode=false in the startManagedWebLogic.sh script if the managed server instance Portal Server is different from the managed server instance of Access Manager. Otherwise, set -Dcom.iplanet.am.serverMode=true.

  4. Run the /usr/local/bea/domains/mydomain/startManagedWeblogic.sh script.

  5. Start the Java ES installer and install Portal Server in the Configure Now mode.

  6. Choose WebLogic container in the WebLogic container panel.

  7. Specify the administrator port as 7001 and the server port as the port of the managed server instance.

  8. Select Managed Server option.

  9. Restart WebLogic server after the installation of Portal Server.

ProcedureTo Install Portal Server in the Configure Later Mode on a WebLogic Managed Server Where Access Manager is Installed on a Managed Server

  1. Create a managed server.

  2. Install Access Manager on the managed server.

  3. Install Portal Server in the Configure Later mode using the Java ES installer.

  4. Change the example files based on your requirements.

    For WebLogic, you can use the example15.xml file to configure Portal Server and search server. In the example15.xml file, ensure that the Port is set to the port of the managed server, the web container administrator port is set to 7001, and the web container managed server is set to true.

  5. Configure the common agent container.

    PortalServer_base/bin/psconfig --config example15.xml

    Note –

    For more information on the required sample, see the PortalServer_base/samples/psconfig/README.txt file.

  6. Restart WebLogic server after the successful installation of Portal Server.

ProcedureTo Install psconsole on Web Server 7.0

The psconsole of Portal Server can be installed only on Web Server or Application server. If you install Portal Server on any of the compatible web containers, such as BEA WebLogic or IBM WebSphere, you need to install psconsole on Web Server or Application Server.

  1. Start the Web Server 7.0 administrator server and instance.


    WebServer_base/admin-server/bin/startserver
WebServer_base/https-host.domain-name:80/bin/startserv

  2. Deploy the PortalServer_base/SUNWportal/admin/psconsole.war file on the Web Server 7.0 using the administrator console.

    1. Log in to the administrator console.

    2. Click the Deployment Pending link.

    3. Select Deploy.

    4. Select Configurations.

    5. Select the configuration in which the psconsole.war file is to be deployed.

    6. Click the java tab.

    7. Type /usr/lib/cacao/lib/cacao_cacao.jar to the Class Path Suffix text box and click Save.

  3. Access psconsole.

    http://host.domain-name:80/psconsole