Sun JavaTM System Portal Server 7.1 can be installed using the Installer in two modes: Configure Now mode or Configure Later mode. If you install in the Configure Now mode, the installation and configuration take place simultaneously.
For the default installation of Portal Server, the user should be the root user. A non-root user can install Portal Server in the Configure Later mode.
This chapter contains information about installing Sun Java System Portal Server 7.1 in the Configure Now mode.
This chapter contains the following topics:
This section contains the requirements for installing Sun Java System Portal Server 7.1.
The installation instructions are specific to the Solaris platform. Refer to the Installation guide for Windows if you are installing Portal Server on the Windows.
The following table lists hardware and operating system requirements:
Table 1–1 Hardware and Operating System Requirements
Component |
Platform Requirement |
---|---|
Supported platforms |
Sun BladeTM or comparable workstation or server |
Operating system |
SolarisTM 9 or Solaris 10 on SPARC Solaris 9 or Solaris 10 on x86 Red Hat Enterprise Linux 3.0 Update 3 or 4.0 on x86 Windows Note: Portal Server 7.1 on Windows can only be used as a developer platform or an evaluation platform. It can not be used as a deployment platform. |
RAM |
1.5 Gbytes for regular deployment on Sun Java System Web Server 2.0 Gbytes for regular deployment on Sun Java System Application Server |
Disk space |
1 Gbyte for Portal Server and associated applications |
Swap space |
Twice the amount of physical memory, for example, 2.0 Gbytes RAM and 4.0 Gbytes swap space. |
Remove the link /usr/share/bdb/db.jar before installation, if it exists.
Check ant already exists on the system by running the following command:
rpm -qa | grep ant
If a version of ant below 1.6 is installed, remove it by running the following command:
rpm -e ant-older-version ant-libs-older-version
You need to use the version of ant sun-ant-1.6.5-2 to install or deploy Portal Server. When you run the installer, it is automatically installed at /opt/sun/bin/ant.
Portal Server requires the following stack components:
Sun Java System Directory Server 6
Sun Java System Access Manager 7 installed in legacy mode not in realm mode.
Portal Server requires Access Manager, Directory Server, and a web container for its installation and configuration. If you are performing a fresh install, Access Manager and Directory Server do not have to be installed before Portal Server is installed. Access Manager, Directory Server, and Portal Server can be installed at the same time. If Access Manager and Directory Server are installed already, point the Portal Server installation and configuration to the existing Directory Server and Access Manager servers.
Sun Java System Web Server 6.x or Sun Java System Application Server 8.x.
Access Manager must be installed in legacy mode before installing Portal Server 7.1.
For detailed instructions for installing the stack components, see the Sun Java Enterprise System 5 Installation Reference for UNIX.
If the system on which you installed Portal Server does not have direct connectivity to the internet, an HTTP proxy needs to be specified. For example, for Sun Java System Application Server, specify the following in the domain.xml file:
<jvm-options>-Dhttp.proxyHost=proxy-host</jvm-options> <jvm-options>-Dhttp.proxyPort=proxy-port</jvm-options> <jvm-options>-Dhttp.nonProxyHosts="portalserver-host"</jvm-options>
For Web Server 7.0, add this options to server.xml of the configuration in which portal is deployed. For IBM WebSphere, add this to the server.xml of the node in which portal is deployed. For WebLogic, add this to startWeblogic.sh/startManagedWeblogic.sh depending on whether the portal is to be installed on administrator server or managed server.
Where, proxy-host is the fully qualified domain name of the proxy host, proxy-port is the port on which the proxy is run, and portalserver-host is the fully qualified domain name of the Portal Server software host.
Execute the command prtconf | grep Memory to check RAM.
Use the command swap -l to see how much swap space your machine has. To temporarily increase your swap space by 4 Gbytes, you can use the following instructions:
mkfile 4g /swap-filename swap -a /swap-filename
where swap-filename is an empty file to be used as a swap area.
Some post installation configuration tasks require you to use values that you entered during the installation. Keep these values available for configuration.
If you install Portal Server on a root local zone, install shared components in global zone.
If you install Portal Server on Sparse local zone, install shared components and Message Queue in global zone if you use Application Server as a web container. If you use Web Server as the web container, install only shared components in global zone.
From the installation location, go to the OS-arch directory, where OS-arch can be Solaris_sparc, Solaris_x86, or Linux_x86.
Run ./installer to invoke the wizard to install the software.
In the Welcome screen, click Next.
In the Software License Agreement screen, read the agreement and click Yes, Accept License.
The Choose Software Components screen appears. Select Portal Server 7.1.
When this option this selected, the following components are selected by default:
The Directory Preparation Tool
Service Registry 3.1
Access Manager 7.1 and related sub components of Identity Management and Policy Services
Directory Server Enterprise Edition 6.0 including the Directory Server Core
Java DB 10.2
Select the other software components that you want to install.
To install Secure Remote Access (SRA) services, select Portal Server Secure Remote Access 7.1. When you select this option, the Gateway, Netlet Proxy, and the Rewriter Proxy are selected by default.
To install Application Server, select Application Server Enterprise Edition 8.2 . When you select this option, the Domain Administration Server, Command Line Administration Tool, and Sample Applications for the Application Server are selected by default. The Application Server High Availability Session Store 4.4 and Sun Java System Message Queue 3.7 UR1 are also selected by default.
Select this option if you need EJB container for portal.
To install Web Server, select the Sun Java System Web Server 7.0. When you select this option, the Web Server CLI, Web Server Core, and Web Server Samples are selected by default.
Select this option if you require only Web Applications.
To install multilingual support for the selected Java ES components, select Install Multilingual Packages for Selected Component(s).
If J2SE-SDK or any shared components require upgrade, the installer displays the corresponding screens. By default, installer upgrade them with the latest version in the installer disk.
The Shared Component Upgrades Requires screen is displayed if any one of the shared components requires upgrading. Click Next to upgrade these shared components.
On the Specify Installation Directories page, specify the installation directory for the software. The following are the default locations. Use the Browse button to change the default location. Click Next.
/opt
/opt/SUNWappserver
/var/opt/SUNWappserver
/opt/SUNWdsee
/opt/SUNWcomds
/opt
/var/opt/SUNWwbsvr7
/opt
/opt
The Verify System Requirements screen is displayed. The installer verifies each of the listed system requirements and displays OK if the requirements are met. If the installer indicates that all the requirements are met, the System Ready for Installation message appears. Click Next to continue with the installation. In case any of the requirements are not met, a text indicating the same appears with the following options: View Reports and Check Again. The View Report option provides the details about the requirements that are not met. It is recommended that you address these issues. After the requirements are met, click the Check Again option to verify whether the requirements are met.
Click Next to continue the installation.
The Choose a Configuration Type screen is displayed.
Select Configure Now, and click Next.
The installer only supports adding one portal and one instance only. For any other configuration, the Configure Later option must be selected. If the Configure Now option is selected, after the packages are installed, the configuration starts immediately.
Select Configure Now, and click Next.
The Custom Configuration screen is displayed.
Service Registry 3.1 and Java DB are not configured during the installation. It can be configured after the installation. Click Next.
The Specify Administrator Account Preferences screen is displayed.
Enter the Administrator ID and password. Type the password, and click Next.
You are also provided with an option to select different administrator accounts for each product.
The Specify Common Server Settings screen is displayed.
Specify the following server settings:
Host name, domain, and IP address of the system. The installer automatically displays these values.
System user name and group ID. For Solaris 10 OS and Linux, the default is root for system user name and root for group ID. For Solaris 9 OS, the default is root for system user name and other for group ID.
Values you enter here appear as default values during the rest of the installation.
If you have selected Web Server as a component to install, the Choose Configuration Type screen is displayed. You have an option to configure administration instance as a server or as a node. By default, configure administration instance as server is selected. Click Next.
If you have selected Web Server as a component to install, the Web Server: Specify Administration Server Settings and Web Server: Specify Instance Settings screens are displayed. Provide the information for Web Server, and click Next.
Specify the Runtime Unix user ID as root.
You need to specify the following details for the Web Server: Specify Administration Server Settings screen:
The default value is automatically created by joining the values that you provided for Host Name and DNS Domain Name under Common Server Settings. The value has the format hostname.domainname.
The default value is 8989.
Port on which Web Server listens for HTTP connections. The default is 8800.
User ID that the default instance of Web Server uses to run on the system. The default is root.
You need to specify the following details for the Web Server: Specify Instance Settings screen:
A host and domain value that resolves to the local host. The value has the format hostname.domainname.
Port on which Web Server listens for HTTP connections. The default value is 80.
An existing non-root user. If you are installing Access Manager or Portal Server, set this value to root and set the Runtime Group to other. You can change these values after installation. For other servers, the Runtime User ID should be a non-root user. The default value is webservd.
Location where Web Server stores content documents. For Solaris OS, the default value is /var/opt/SUNWwbsvr7/docs. For Linux and HP-UX, the default value is /var/opt/sun/webserver7/docs.
The High Availability Session Store (HADB): Specify Configuration Data screen is displayed. The Installer displays the default values. This screen is displayed only if you have selected Application Server as a component to install. Click Next.
Port on which the HADB management listens. The default value is 1862.
Location where HADB stores resource contents. The default value is /var/opt.
The UNIX group (GID) in which the default instance of HADB runs as a user. The default value is other.
Choose this option to direct the installer to configure HADB to start automatically when the system restarts. By default, this is selected.
Choose this option when you want HADB to be managed by the HADB Administration Group. If this parameter is set to yes, all members belonging to the group (HADB_DEFAULT_GROUP) can run and manage HADB. By default, it is set to No.
The Application Server: Domain Administration Server screen is displayed.
Provide or change values in the installer pages as needed and click Next.
The installer displays the default values. This screen is displayed only if you have selected Application Server as a component to install.
Port on which Application Servers administrative server listens for connections. By default, it is 4849.
The default is 8686.
The default value is 8080. If the installer detects that the default port is used, an alternative value is suggested.
The default is 8181.
SSL certificate database password, used for asadmin operations such as Domain Administration Server startup and Node Agent startup. The default value is the Administrator Password you provided under Common Server Settings.
The Application Server: Node Agent screen is displayed.
Specify the details and click Next.
This screen displays only if you have selected Application Server as a component to install.
Host name for administration server which the node agent can connect to.
User ID of the Application Server admin user. The default value is the Administrator User ID you provided under Common Server Settings.
If you chose to use a single administrator account, this field is not present.
Password for the Application Server admin user. There is no default value.
If you chose to use a single administrator account, this field is not present.
SSL certificate database password, used for asadmin operations such as Domain Administration Server startup and Node Agent startup. There is no default value.
Port on which Application Servers node agent listens for connections. Provides access to the administration tools. The default value is 4849.
Name of the local node. The default value is the local host name
The Application Server: Configure Load Balancing Plugin screen is displayed.
Specify the details and click Next.
This screen displays only if you have selected Application Server as a component to install.
You can select either Sun Java System Web Server or Apache Web Server. HP-UX does not support Apache Web Server.
Installation directory for Web Server or Apache HTTP Server.
The default value is:
Solaris OS: /opt/SUNWwbsvr7
Linux and HP-UX: /opt/sun/webserver7
Installation directory for Web Server or Apache HTTP Server.
The default value is:
Solaris OS: /var/opt/SUNWwbsvr7
Linux and HP-UX: /var/opt/sun/webserver7
The Directory Server: Specify Instance Creation Information screen is displayed.
Specify the information for Directory Server instance creation and click Next.
Location of new instance.
The default value is 389.
The default value is 636.
Distinguished Name (DN) of the user who has unrestricted access to Directory Server. The default value is cn=Directory Manager.
The default value is root.
The default value is root.
Password for the directory manager.
Initial directory suffix managed by this instance. The default value is formed by the segments of the fully qualified domain name for the current host. For example, if you install on siroe.sub1.example.com, the default value is dc=sub1,dc=example,dc=com.
For more information, see Directory Server Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX.
The Access Manager: Specify Configuration Information screen is displayed.
Specify the information for the Access Manager configuration and click Next.
Indicates the level of interoperability with other components. You have a choice of Realm mode (version 7 style) or Legacy mode (version 6 style). Default option is Legacy mode. You must use Legacy mode if you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. The default value for Legacy mode is Enabled. The default for Realm mode is Disabled.
Portal Server supports Realm mode only if Sun Java System Directory Server is used as a user repository and Access Manager SDK is configured as the datastore plugin for the Realm mode. If you select the Configure Now option for the Realm mode, the installer does this by default.
Access Manager's top-level administrator. This user has unlimited access to all entries managed by Access Manager. The default name, amadmin, cannot be changed. This ensures that the Access Manager administrator role and its privileges are created and mapped properly in Directory Server, allowing you to log into Access Manager immediately after installation.
Password of the amadmin user. The value must have at least eight characters.
Bind DN user for LDAP, Membership, and Policy services. This user has read and search access to all Directory Server entries. The default user name, amldapuser, cannot be changed.
Password of the amldapuser user. This password must be different from the password of the amadmin user. It can be any valid Directory Service password.
A string that Access Manager uses to encrypt user passwords. For security purposes, it is recommended that the password encryption key be 12 characters or longer.
amAdmin and amldapuser password should be different.
For more information, see the Access Manager Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX.
Portal Server supports installing Access Manager in the Realm mode or in the Legacy mode.
The Access Manager: Choose Deployment Container screen is displayed.
You can select either Sun Java System Web Server or Sun Java System Application Server. Select the option, and click Next.
For more information about configuring Web Server, see the Web Server Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX in Sun Java Enterprise System 5 Installation Reference for UNIX.
For more information about configuring Application Server, see the Sun Java Enterprise System 5 Installation Reference for UNIX
The Access Manager: Specify Sun Java System Application Server screen is displayed.
Specify the details and click Next.
This screen is displayed only if you have selected Sun Java System Application Server as the web container for Access Manager.
Specify whether the value for Instance Port refers to a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP.
Specify whether the value for Administrator Port is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP.
The Access Manager: Specify Web Container for Running Access Manager Services screen is displayed.
Specify the details for Access Manager and click Next.
Fully qualified domain name of the host on which you are installing.
Uniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and Java Archive (JAR) files associated with the Identity Management and Policy Services Core subcomponent. The default value is amserver. Do not enter a leading slash.
URI prefix for accessing the common domain services on the web container. The default value is amcommon. Do not enter a leading slash.
The names of the trusted DNS domains that Access Manager returns to a browser when Access Manager grants a session ID to a user. A leading dot (.) is required for each domain in the list. The default value is the current domain, prefixed by a dot (.).
URI that determines the mapping that the web container running Access Manager will use between a string you specify and a corresponding deployed application. The default value is ampassword. Do not enter a leading slash.
Specify whether the console uses a secure or unsecure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default is HTTP.
The Access Manager: Choose Access Manager Console screen is displayed.
This screen is displayed only if you select the Legacy mode to install Access Manager.
By default, Deploy New Console is selected. Click Next.
Choose Deploy new console to deploy the console into the web container of the host on which Access Manager is being installed. Choose Use existing console to use an existing console that is deployed on a remote host.
URI prefix for accessing the HTML pages, classes, and JAR files associated with the Access Manager Administration Console subcomponent.The default value is amconsole.
Fully qualified domain name for the server hosting the existing console. This value is not needed if you are deploying a new console. You can edit the field only if you are using an existing console.
Port on which the existing console listens for connections. Permitted values are any valid and unused port number, in the range 0 (zero) through 65535.
The Access Manager: Choose Directory Server Instance screen is displayed.
Use the Directory Server Instance that you just created. Click Next.
If you choose to use an existing instance instead of the default, the alternate instance must already be configured.
The Access Manager: Specify Directory Server Data screen is displayed.
You can select Yes or No for the option: Is Directory Server is Provisioned with User Data. By default, No is selected. If you select Yes, you need to provide the related information. Click Next.
If you have selected Application Server as the deployment container for Access Manager, the Specify Sun Java System Application Server Information screen is displayed. Click Next.
This protocol specifies whether the value for Server Instance port refers to a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP.
The Portal Server: Specify Web Container Deployment Information screen is displayed.
Specify the Web Container deployment information and click Next.
The default is host name:port/portal1.
The default is portal1.
The default is search1.
The default is /portal.
The default is hostname-8080.
Select the Enable Secure Remote Access option, if you wish to enable Secure Remote Access. Select Developer Sample, Enterprise Sample, and Community Sample if you wish to configure samples.
The Portal Server: Secure Remote Access screen is displayed. The Portal Server: Secure Remote Access: Configure Gateway screen is displayed.
Enter the following information and click Next.
It is https by default.
Portal Server domain name.
Gateway domain.
It is 443 by default.
It is default by default.
The user password
Specify the details and click Next.
Protocol (HTTP or HTTPS) the gateway uses to communicate. In most cases the gateway should use HTTPS.
The name, subdomain, and domain name of the machine on which the Gateway proxy resides. By default, the system values are used.
The host IP address on which the Gateway Proxy resides. By default, the IP address is the IP address of the system and port is 443.
The gateway profile name. By default, the gateway profile name is default.
The Portal Server: Secure Remote Access: Configure Netlet Proxy screen is displayed.
Specify the following information for the Netlet Proxy.
The name, subdomain, and domain name of the machine on which the Netlet proxy resides. By default, the system values are used.
The host IP address on which the Netlet Proxy resides. By default, the IP address is the IP address of the system and port is 10555.
The gateway profile name. By default, the gateway profile name is default.
Click Next.
The Portal Server: Secure Remote Access: Configure Rewriter Proxy screen is displayed.
Specify the following information to install the Rewriter Proxy.
The host name, subdomain, and domain name of the machine on which the Rewriter Proxy resides. By default, the system values are used.
The Host IP address and access port of the machine on which the Rewriter Proxy resides. By default, the IP address is the IP address of the system and port is 10443.
The gateway profile name. By default, the gateway profile name is default.
Click Next.
The Portal Server: Secure Remote Access: Specify Certificate Information screen is displayed.
Specify the following certificate information for the Secure Remote Access.
The organization name, division, city, and state information.
The country code in two character format.
The certificate database password must be at least eight characters.
Click Next.
The Ready to Install screen is displayed. Specify whether you are ready to install by clicking Install.
Verify the Portal Server installation by doing the following:
Accessing the samples.
Accessing the Portal Server administration console.
Verifying the Gateway port and running the Portal Server in secure mode.
Start Directory Server, web container, and gateway.
Access Portal Server. For example, type the URL in the browser.
http://host.domain-name:port/portal-URI
The welcome page appears. The page displays a short description of Portal server and links to sample portals that you selected for installation. Click on one of the links and access the anonymous portal desktop for the sample portal. If the sample portal desktop displays without exception, your Portal Server installation was successful.
Type http://host.domain-name:port/psconsole.
Verify whether Java DB process is running.
netsatat -an | grep 1527
If Java DB is not running, start Java DB. For more information, refer to To Start and Stop Java DB
Check whether the common agent container is running.
On the Solaris platform, type the following:
/usr/share/bin/cacaoadm status
On the Linux platform, type the following:
/opt/sun/cacao/bin/cacaoadm status
If the common agent container is not running, restart it.
On the Solaris platform, type the following:
/usr/share/bin/cacaoadm stop /usr/share/bin/cacaoadm start |
On the Linux platform, type the following:
/opt/sun/cacao/bin/cacaoadm stop /opt/sun/cacao/bin/cacaoadm start |
By default, common agent container creates a self-signed CA cert and uses it to sign the server cert of the Cacao agent. The subject DN of this server cert is CN=hostname_agent (or CN=hostname_default_agent on MS Windows). When this default server cert is to be replaced by another server cert signed by the CA of the user's choice, the subject DN of the new server cert must be kept the same as the original one for Portal Server administration to continue function without interruption.
Verify whether Directory Server is running using the following commands:
netstat -an | grep 389
If it is not running, start the Directory Server using the following command:
cd /opt/SUNWdsee/ds6/bin ./dsadm start /var/opt/SUNWdsee/dsins1 |
Verify whether the Application Server or Web Server is running using the following command:
For Web Server:
netstat -an | grep 80
For Application Server:
netstat -an | grep 8080
If it is not running, start the server using the following command:
For Application Server:
/ApplicationServer_base/Appserver/bin/asadmin start-domain --user admin domain1 |
For Web Server:
/var/opt/SUNWwbsvr7/https-host.domain-name/bin/startserv |
Run the following command to check if the gateway is running on the specified port (the default port is 443):
netstat -an | grep 443
If the gateway is not running, do the following:
PortalServer-base/bin/psadmin provision-sra -u amadmin -f amadmin-password-file --gateway-profile gateway-profile --enable
PortalServer-base/bin/psadmin start-sra-instance -u amadmin -f amadmin-password-file --instance-type gateway --instance-name gateway-instance-name
Run the Portal Server in secure mode by typing the gateway URL in your browser:
https://gateway-machine-name:443
If you chose a different port number other than the default port (443) during installation, you need not specify that port number.
Use the following procedure to uninstall Portal Server.
As a root user, log in to the machine where you installed Portal Server.
Change directories to:
/var/sadm/prod/SUNWentsys5/ on Solaris.
/var/sadm/prod/sun-entsys5/ on Linux.
Type ./uninstall to uninstall Portal Server.
The Sun Java Enterprise System Uninstall Wizard is displayed.
Select the components to uninstall and select Next.
If you are uninstalling the Secure Remote Access component, you are asked to provide the portal administrator, Access Manager administrator, and LDAP passwords.
Select Uninstall to uninstall the software.
Create a custom directory for the configuration files.
mkdir /tmp/mydir
Copy the sample configuration files, input.properties and password.properties, in PortalServer-base/samples/portals/shared to the directory you created and remove the .template extension.
cp /opt/SUNWportal/samples/portals/shared/input.properties.template /tmp/mydir/input.properties cp /opt/SUNWportal/samples/portals/shared/password.properties.template /tmp/mydir/password.properties |
Edit the input.properties file and replace all the tokens that begin and end with % with the appropriate Portal Server settings.
ps.config.location=/etc/opt/SUNWportal ps.portal.id=portal1 ps.access.url=http://domain-name:80/portal ps.webapp.uri=/portal ps.profiler.email= ps.profiler.smtp.host= search.access.url=http://domain-name:80/search1/search search.id=search1 am.admin.dn=uid=amAdmin,ou=People,dc=sun,dc=com default.org.dn=dc=sun,dc=com |
Edit the password.properties file and replace tokens that begin and end with % with the appropriate administration password value.
amadminPassword=adminpassword amldapuserPassword=amldapuserpassword userManagementPassword=%USER_MANAGEMENT_PASSWORD% |
The userManagementPassword is used for only enterprise sample communications tab setup.
The organization name CommunitySample is hardcoded in the community sample ant configuration file. Edit the /opt/SUNWportal/samples/portals/community/build.xml file and replace CommunitySample in the following line with your organization name:
<property name="orgName" value="CommunitySample"/>
The organization name CommunitySample is hardcoded in the par DPMapping.properties file. Edit the /opt/SUNWportal/par-src/community_sample/dp/DPMapping.properties file and replace CommunitySample in the following line with your organization name:
organization=o=CommunitySample,dpnode
The organization name CommunitySampleis hardcoded in the JSP file. Edit the /opt/SUNWportal/par-src/community_sample/pbfiles/templateBaseDir/community_sample /Login/content.jsp file and replace CommunitySample with your organization name.
The user, test, is hardcoded in the community sample setup files. Edit the following files and replace the user, test, with your user name: /opt/SUNWportal/samples/portals/community/setup/CommunitySampleConfigRequest.xml and /opt/SUNWportal/samples/portals/community/setup/CommunitySampleSRAConfigRequest.xml.
The user, commauthlessanonymous is hardcoded in the community configuration and JSP files. Edit the following files and replace the user commauthlessanonymous with your user name.
/opt/SUNWportal/samples/portals/community/build.xml
/opt/SUNWportal/samples/portals/community/setup/ CommunitySampleConfigRequest.xml
/opt/SUNWportal/samples/portals/community/setup/ CommunitySamplePortalRequest.input
Install the Community Sample by running the following command:
/usr/sfw/bin/ant -buildfile /opt/SUNWportal/samples/portals/community/build.xml -Dconfig.location=/tmp/mydir -logfile /tmp/mydir/community_sample_install.log
The details provided in the Configuration guide, such as default directories and commands are specific to the Solaris platform. You can use the same commands for Solaris, Linux, and HP-UX. If you install Portal Server on the Windows platform, a .bat extension is required with all the commands.
The psconfig command is run as follows on the Solaris platform:
PortalServer-base/SUNWportal/bin/psconfig --config configuration-xml-file
When you run the psconfig command on the Windows platform, use the command as follows:
JES-installer-base/portal/bin/psconfig.bat --config configuration-xml-file
where JES-installer-base is the directory where you installed Java ES components. For example, if C:/PROGRA~1/Sun/JavaES5 is the directory where you installed Java ES components, you need to run the psconfig command as follows:
C:/PROGRA~1/Sun/JavaES5/portal/bin/psconfig.bat --config configuration-xml-file
All the commands of Portal Server are run from the /opt/SUNWportal/bin directory. The /opt/SUNWportal is the default installation directory of Portal Server.
The command to display help on the Solaris platform is run as follows:
/opt/SUNWportal/bin psadmin --help
On the Windows platform, use the command as follows:
PortalServer_base/portal/bin psadmin.bat --help
The command to start common agent container on the Solaris platform is as follows:
/usr/share/bin/cacaoadm start
On the Windows platform, use the command as follows:
JES_installer_base/share/cacao_2/bin/cacaoadm.bat start
The default installation directories of Java ES Components change based on the operating system. While running a command, you need to change the directories. In the Configuration guide, the information provided is specific to the Solaris platform. If you are using Windows, Linux, or HP-UX platform, refer to the following table for the default directories.
Table 1–2 Default Directories on LINUX, HP/UX, and Windows
Product Name |
LINUX / HP-UNIX |
Windows |
Access Manager |
/opt/sun/identity |
JES_installer_base/identity |
Access Manager configuration directory |
/etc/opt/sun/identity/config |
JES_installer_base/identity/config |
Access Manager data directory |
/var/opt/sun/identity |
JES_installer_base/identity/data |
Application Server install directory |
/opt/sun/appserver |
JES_installer_base/appserver |
Application Server instance directory |
/var/opt/sun/appserver/ domains/domain1 |
JES_installer_base/appserver/domains/domain1 |
Application Server docroot |
/var/opt/sun/appserver/ domains/domain1/docroot |
JES_installer_base/appserver/domains/ domain1/ docroot |
WebServer install directory |
/opt/sun/webserver7 |
JES_installer_base/webserver7 |
WebServer docroot |
/var/opt/sun/webserver7/ https-instancename/docs |
JES_installer_base/webserver7/ https-instancename/docs |
Directory Server product directory |
/opt/sun/ds6 |
JES_installer_base/DSEE/ds6 |
Directory Server instance directory |
/var/opt/sun/dsins1 |
JES_installer_base/DSEE/var/DSInstance |
Portal Server product directory |
/opt/sun/portal |
JES_installer_base/portal |
Portal Server configuration directory |
/etc/opt/sun/portal |
JES_installer_base/portal/config |
Portal Server data directory |
/var/opt/sun/portal |
JES_installer_base/portal/data |
Common agent container product directory |
/opt/sun/cacao |
JES_installer_base/share/cacao_2 |
Common agent container configuration directory |
/etc/opt/sun/cacao/instances/default |
JES_installer_base/share/cacao_2/etc/cacao/ instances/default |
Registry lib directory |
/opt/sun/srvc-registry/lib |
JES_installer_base/srvc-registry/lib |
MFWK lib directory |
/opt/sun/mfwk/share/lib |
JES_installer_base/share/mfwk/lib |
MFWK bin directory |
/opt/sun/mfwk/bin |
JES_installer_base/share/mfwk/lib |
Derby lib directory |
/opt/sun/javadb/lib |
JES_installer_base/javadb/lib |
Webnfs lib directory |
/opt/sun/webnfs |
JES_installer_base/share/webnfs |
Ant Home directory |
/opt/sun |
JES_installer_base/share/ant |
Ant lib directory |
/opt/sun/share/lib |
JES_installer_base/share/ant/lib |
Shared lib directory |
/opt/sun/share/lib |
JES_installer_base/share/lib |
Private lib directory |
/opt/sun/private/share/lib |
JES_installer_base/share/lib |
Java home |
/usr/jdk/entsys-j2se |
C:/Java/JDK15~3.0_0 |
JDMK lib directory |
/opt/sun/jdmk/5.1/lib |
JES_installer_base/share/lib |
JAX lib directory |
/opt/sun/share/lib |
JES_installer_base/share/lib |
NSS lib directory |
/opt/sun/private/lib |
JES_installer_base/share/lib |
JSS Jar directory |
/opt/sun/private/lshare/lib |
JES_installer_base/share/lib |