Sun Java System Portal Server 7.1 can be installed using the Java ES installer in two modes: Configure Now mode or Configure Later mode. If you select the Configure Now option, the installation and configuration take place simultaneously. If you select the Configure Later mode, you need to run the psconfig command to configure Portal Server after installation.
This chapter contains the following topics:
When you run the psconfig command, you specify a configuration XML file. You can customize the configuration XML file based on your requirements. Sample configuration XML files are provided at the PortalServer-base/samples/psconfig directory. To know more about the files that you need to customize, read the PortalServer-base/SUNWportal/samples/psconfig/ReadMe.txt. To customize the files, you modify values and replace the tokens.
The syntax of the psconfig command is as follows:
psconfig --config configuration-xml-file
The location of the psconfig utility is PortalServer-base/SUNWportal/bin.
The subsequent sections in this chapter contain information about customizing a sample configuration XML file if the sample configuration XML files do not meet your requirements.
If a sample configuration file does not suit your desired setup and if a custom configuration XML file must be constructed, follow the instructions in this section. Sample configuration XML files are provided at the PortalServer-base/samples/psconfig directory. In order to set up your custom configuration file, you must follow this process:
Construct the required basic configuration file XML file. For more information, refer to Constructing the Required Basic XML File.
This basic configuration is required to make the portal psadmin command usable.
Construct the <ComponentsToConfigure> element depending on which components are to be configured on this host. See Configuring Portal Server Components for more information.
Construct the following configuration information based on the components to configure on this host:
Run the ./psconfig --config configuration-xml-file command.
This section describes the overall Portal Server, header/footer, shared components, and the Access Manager elements in the configuration file. See the example2.xml file.
Edit the example2.xml file.
In the example2.xml file, replace the following tokens with the actual values.
The host and domain name of the machine on which configuration is occurring
Administrator's password for the Access Manager instance with which Portal Server is to be configured
Internal LDAP user password for the Access Manager instance with which Portal Server is to be configured
Administrator's password of the Directory Server with which Portal Server is to be configured
Modify the following values in the file as needed.
If Portal Server is installed in a non-default location, then change this location to the non-default location.
If Netfile utility is required, install the optional JCIFS package and specify the lib directory path name.
Install the optional JChardet package and specify the lib directory path name.
Specify the installation path name of Access Manager if Access Manager was not installed in the default location.
Specify the installation path name of Portal Server if Portal Server was not installed in the default location.
Portal Server components that can be installed and configured across different nodes include the core Portal Server , Secure Remote Access (SRA), Gateway, Netlet Proxy, and Rewriter Proxy. The <ComponentsToConfigure> element is constructed based on which components are configured on this host.
Include the following in the configuration XML file.
<ComponentsToConfigure> <component>portalserver</component> <component>gateway</component> <component>netletproxy</component> <component>rewriterproxy</component> </ComponentsToConfigure>
To exclude components, remove the corresponding <component> element.
This section explains how to configure a basic Portal Server.
Open the configuration XML file.
Replace the following tokens in the configuration XML file.
The host and domain name of the machine on which Portal Server is to be configured.
Web container port at which Portal Server has to be deployed.
Modify the following values in the configuration XML file.
If the DEPLOY URI is not the default, change /portal to the changed URI value.
If the DEPLOY URI is not the default, change /portal to the changed URI value. Ensure that both PortalAccessURL and PortalWebappURI are specified in the configuration XML file.
Change portal1 to the required portal ID, which should be unique.
Change myInstance to the required instance ID, which should be unique.
Specifies which Search Server this portal samples are configured with. This is needed only if samples are configured.
Portal Server software three types of sample portals: the Developer Sample, Enterprise Sample, and Community Sample. Each sample is created under its own sub-org for ease of management. You can configure any of the samples or all of the samples.
Include the following in the configuration XML file.
<PortalConfiguration> <PortalServer . . . > <SamplePortal> <Sample Name="DeveloperPortal"/> <Sample Name="EnterprisePortal"/> <Sample Name="CommunityPortal"/> </SamplePortal> . . . </PortalServer> </PortalConfiguration>
The Web container configuration varies with the container to be configured. In the configuration XML file, there is one <WebContainerProperties> element specified for the web container under the <PortalServer><Instance> element and one under the <SearchServer> element.
Open the configuration XML file.
For Web Server, open example1.xml, examples 3 to 9, example13.xml, or example17.xml.
For Application Server, open the example14.xml file.
Replace the tokens with actual values.
For Web Server:
The host and domain name of the machine on which the Portal Server instance is to be configured
Web Server port
Web Server instance name
Web Server administration port
Web Server administrator's password
For Application Server:
The host and domain name of the machine on which the Portal Server instance is to be configured
Application Server port
Application Server administration port
Application Server administrator's password
Application Server master password if specified
Modify the following values in the configuration XML file as needed.
For Application Server:
If Application Server is installed at a non-default location insert the installation path name.
If deploying to a non-default Application Server domain insert the appropriate name.
Instance name within the Application Server domain. The server is the name of the first instance which is created by default at the same time the Application Server 8.1 domain is created. This can be changed to the name of any other created instance within that domain.
The Search Server is deployed to a specific web container instance which is defined by a <WebContainerProperties> element. Multiple Search servers can be specified by having multiple <SearchServer> elements within a <PortalConfiguration> section, each with a unique ID. A Portal Server can be associated with a specific search server by specifying the SearchServerID attribute within the <PortalServer> element.
In the configuration XML file, include the SearchServerID attribute within the <PortalServer> element.
<PortalConfiguration> <SearchServer SearchServerID="search1"> <WebContainerProperties . . . /> </SearchServer> <PortalServer SearchServerID="search1"> </PortalServer> </PortalConfiguration>
The SRA core component can only be installed and configured on the same node as the Portal Server component. The Portal Server and SRA core components have to be configured at the same time. So the SRA core component cannot be configured on a host that already has an existing Portal Server.
Add Secure remote access support to Portal Server by adding the <component>sracore</component> to the <ComponentsToConfigure> section.
Add the following section to the <PortalConfiguration> section.
<PortalConfiguration> . . . <SecureRemoteAccessCore GatewayProtocol="https" PortalServerDomain="@DOMAIN@" GatewayPort="@GATEWAY.PORT@" GatewayProfileName="default" LogUserPassword="@SRA.LOGUSER.PASSWORD@"/> </PortalConfiguration>
Replace the tokens with actual values.
Domain name of the machine on which Portal Server is to be configured
Port on which Gateway is to run
SRA log user password
Modify the GatewayProfileName value if the default profile will not be used.
This section explains how to configure Gateway with Portal Server.
Open the example10.xml file.
Replace the following tokens with actual values.
The host and domain name of the machine on which Gateway is to be configured
Port on which Gateway will run
IP address of the machine on which Gateway will run
The host and domain name of the machine on which the Portal Server instance is to be configured
Port on which the Portal Server instance will run
SRA log user password
SRA certificate database password
Modify the following values as needed.
Change if the default profile will not be used
Change if start on installation is not required
Change attributes in this section accordingly
This section explains how to configure the Netlet proxy.
Open the example11.xml file.
Replace the tokens with the actual values.
The host and domain name of the machine on which Netlet Proxy will be configured
Port on which Netlet Proxy will run
IP address of the machine on which Netlet Proxy will run
The host and domain name of the machine on which the Portal Server instance will be configured
Port on which the Portal Server instance will run
SRA log user password
SRA certificate database password
Modify the following values as needed.
Change if the default profile will not be used
Change if start on installation is not required
Change attributes in this section accordingly
This section explains how to configure Rewriter Proxy.
Open the example12.xml file.
Replace the tokens with the actual values.
The host and domain name of the machine on which Rewriter Proxy will be configured
Port on which Rewriter Proxy will run
IP address of the machine on which Rewriter Proxy will run
The host and domain name of the machine on which portal instance will be configured
Port on which Portal Server instance runs
SRA log user password
SRA Certificate database password
Modify the following values as needed.
Change if the default profile is not to be used
Change if start on install is not required
Change attributes in this section accordingly