If you want to install Portal Server on BEA WebLogic, you need to install the components in different session.
Install Directory Server and Application Server or Web Server using the Java ES Installer in the Configure Now mode.
Install Access Manager using the Java ES installer in the Configure Later mode.
Install Portal Server using the Java ES installer in the Configure Now or Configure Later mode
Portal Server administration console does not work with WebLogic.
Install BEA WebLogic 8.1.
Create the WebLogic domain and start the administrator server.
/usr/local/bea/user_projects/domains/domain1/startWebLogic.sh
Access the administrator server of BEA WebLogic.
http://host.domain-name:7001
Install Directory Server, Java DB 10. 2 and Web Server using the Java ES installer in the Configure Now mode.
Start Directory Server instance.
Install Access Manager in the Configure Later mode using the Java ES installer.
Customize the amsamplesilent file.
The amsamplesilent file is located in the following directories:
Solaris: /AccessManager_base/SUNWam/bin
Linux: /AccessManager_base/sun/identity/bin
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 = 7001
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
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 8.1 sp4 or $WL8_HOME/jdk/142_08 for 8.1sp5
Run the AccessManager_base/bin/amconfig -s amsamplesilent script.
The amsamplesilent file is located in the following directories:
Solaris: /AccessManager_base/SUNWam/bin
Linux: /AccessManager_base/sun/identity/bin
Edit the startweblogic.sh and startManagedweblogic.sh scripts and add the following to the classpath: /opt/SUNWjavadb/lib/derbyclient.jar.
For Linux, the derbyclient.jar file is located at the /opt/sun/javadb/lib directory.
In the startweblogic.sh and startManagedweblogic.sh 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.
In the startweblogic.sh and startManagedweblogic.sh 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.
(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.
For Linux, 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
Restart WebLogic and access the following URL.
http://host.domain-name:7001/amconsole
Install Portal Server in the Configure Now mode using the Java ES installer.
Choose WebLogic as the web container for Portal Server.
In the Portal Server web container panel, ensure that the Managed Server option is not selected. Also, ensure that both the administrator and server ports are 7001.
Restart WebLogic server after the successful installation of Portal Server.
Access the WebLogic administrator console.
http://hostname.domain-name:7001/console
Deploy the portal web applications.
Deploy the portal.war, communityportlets.war, search.war, and the remaining web applications.
Restart the WebLogic server.
Install Portal Server in the Configure Later mode using the Java ES installer.
Complete the Portal Server installation.
Change the example files based on the requirements.
You can use the example15.xml file to configure Portal Server and search server on WebLogic. In the example15.xml file, make sure both the Port and web container administrator port are set to 7001 and web container managed server is set to false.
Configure the common agent container.
PortalServer_base/bin/psconfig --config example15.xml
The psconfig utility is located in the PortalServer_base/SUNWportal/bin directory on the Solaris platform. For Linux, it is in the /PortalServer_base/sunportal/bin directory.
The example files are located in the PortalServer_base/samples/psconfig directory for the Solaris platform and PortalServer_base/samples/psconfig directory for Linux.
Access the WebLogic administrator console.
http://hostname.domain-name:7001/console
Deploy the portal web applications.
Deploy portal.war, communityportlets.war, search.war, and the remaining web applications.
Restart the WebLogic 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:
Create a managed server.
Install Portal Server on the managed server in the Configure Now or Configure Later mode.
Install Access Manager on the administrator server of WebLogic 8.1.
Start the WebLogic administrator server.
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.
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
Log in to the WebLogic administrator console.
Select Machines.
Select Configure a New Machine.
Type a machine name and click Create.
Select the Node Manager tab.
Specify the IP address of the host in the listen address and specify the port on which the Node Manager is running.
Select Servers in the left pane to create a new managed server.
Select Configure a New Server.
Specify the server name and machine name and specify the listen port of the managed server.
Start the managed server from the WebLogic administration console.
Install Access Manager in the WebLogic administrator server.
Install Directory Server.
Install Portal Server in the Configure Now mode using the Java ES installer.
Select the WebLogic container in the WebLogic container panel.
Specify the administrator port as 7001 and the server port as the port of the managed server instance.
Select Managed Server option.
Restart WebLogic server after the successful installation of Portal Server.
Install Access Manager in the WebLogic administrator server.
Install Directory Server.
Install Portal Server in the Configure Later mode using the Java ES installer.
Complete the Portal Server installation.
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.
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.
For more information on the appropriate sample, see the PortalServer_base/samples/psconfig/README.txt file.
Restart WebLogic server after the successful installation of Portal Server.
In this section, you install Access Manager on a managed server of BEA WebLogic.
Install BEA WebLogic 8.1 using the installer.
Create WebLogic domain and start administrator server.
/usr/local/bea/user_projects/domains/domain1/startWebLogic.sh
Access the administrator server of BEA WebLogic.
http://host.domain-name:7001
Create a managed server.
Start the Java ES installer. Install Directory Server, Java DB 10. 2 and Web Server in the Configure Now mode.
Start the Directory Server instance.
Install Access Manager in the Configure Later mode.
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
Run the following command.
AccessManager_base/bin/amconfig -s amsamplesilent
Log in to the WebLogic administrator console.
Deploy the Access Manager war files, such as amserver.war, ampassword.war, amconsole.war, and amcommon.war available in the AccessManager_base directory.
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.
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.
(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.
(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
Restart WebLogic server and access the administrator console.
http://host.domain-name:managed-server-port/amconsole
Create a managed server.
Install Access Manager on the managed server.
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.
Run the /usr/local/bea/domains/mydomain/startManagedWeblogic.sh script.
Start the Java ES installer and install Portal Server in the Configure Now mode.
Choose WebLogic container in the WebLogic container panel.
Specify the administrator port as 7001 and the server port as the port of the managed server instance.
Select Managed Server option.
Restart WebLogic server after the installation of Portal Server.
Create a managed server.
Install Access Manager on the managed server.
Install Portal Server in the Configure Later mode using the Java ES installer.
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.
Configure the common agent container.
PortalServer_base/bin/psconfig --config example15.xml
For more information on the required sample, see the PortalServer_base/samples/psconfig/README.txt file.
Restart WebLogic server after the successful installation of Portal Server.
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.
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 |
Deploy the PortalServer_base/SUNWportal/admin/psconsole.war file on the Web Server 7.0 using the administrator console.
Access psconsole.
http://host.domain-name:80/psconsole