Some error messages displayed during the installation and configuration of Portal Server SRA 7 may not allow you to install and configure the product properly.
The following are some of the configuration and installation issues:
When you select the Start Instance After Install check box in any of the SRA screens during installation, the configurator fails to start the portal instance after installation and the Sun Java System installer displays an error message about the configuration failure.
Check the installer logs to verify whether the configuration or the start of the portal instance failed. If the instance failed to start, then the installation and configuration of Sun Java System is correct. Now, use the psadmin command to start the instance manually.
This incorrect display of error message is fixed in the Sun Java System 5 Portal Server SRA 7.1 release.
Sun Java System Portal Server 7 uses JMX (Java Management Extensions) for management of all servers. Since Cacao is an implementation of the JMX API, it requires a Local Directory Server to run Portal Server 7.
The Cacao server stores metadata in an LDAP (Lightweight Directory Access Protocol) server and needs access to the LDAP server for starting. The gateway is deployed in the DMZ (Demilitarized Zone), and the firewall blocks LDAP access to the gateway host. As a workaround, install a local directory server in the DMZ on the gateway node. Note that the LDAP server does not include all the corporate data but only the bootstrap metadata for Cacao to start.
To install the gateway on a standalone node:
Install a local directory server.
Provide information about the local directory server or about the Portal Directory Server on the gateway screens.
Sun Java System 5 Portal server SRA 7.1 release does not require a Local Directory Server in the DMZ for Cacao to start.
When you configure the Portal Server 7 gateway, the configurator tries to record configuration information into the LDAP server on the intranet. For this purpose, the Cacao server on the intranet connects to the Cacao server running on the Portal Server node, which copies data to the LDAP server. For this data transfer to happen, an explicit trust must be established between the Cacao servers on the intranet gateway node and the Portal Server node. Trust can be established by copying the security folder from the Cacao install on the portal node to the security folder on the Cacao install on the gateway node.
The manual step to establish trust between two nodes is automated in the Sun Java System 5 Portal Server SRA 7.1 release.
Yes. Both Access Manager and Directory Server are required for a two session installation of Portal Server 7. However, you can install them in one session if the Access Manager and Directory Server reside on the same node.
A profile is created in the PSConsole and includes SRA proxy server configuration information. An instance is a combination of a hostname and a profile.
For example, create a profile nameddefault. You can create a gateway instance on host A and a netlet proxy instance on host B with the same name, default. Both instances use the configuration information in the profile default, since the name of the instance and the profile are same.
In the above scenario, it is possible to use the same profile for multiple instances of SRA proxy servers on multiple hosts.
Use the psadmin list-sra-instances command to list all the known profiles along with the available instance information.
Netlet and Rewriter proxies need to be enabled with the help of PSConsole after the installation.
Successful installation and configuration of Sun Java System Portal Server SRA 7 does not mean that the gateway uses Netlet and Rewriter proxies. Manually configure the specific gateways to use the required proxies.
To access PSConsole through the gateway:
Tag replace the request file, enablePSConsoleFromGW.xml with appropriate values.
Load the request file into the Directory Server using amadmin —u <adminuser> —w <ampassword> —t enablePSConsoleFromGW.xml command.
For gateway, netlet, and proxylet to work properly:
Tag replace the request file, enableSRAforPortal.xml with appropriate values.
Load the request file into the Directory Server using amadmin —u <adminuser> —w <ampassword> —t enableSRAforPortal.xml command.