 Print-friendly Version
Post-Installation Configuration for Sun Java System Portal Server Secure Remote Access 7Hemdari Duraiswami, June 2007 This technical note addresses post-installation configuration issues for Sun Java System Portal Server Secure Remote Access (SRA) 7. The document contains a list of common issues that occur during and after the configuration of Sun Java System Portal Server SRA 7 and the solutions to address them. This article addresses issues in the following products:
Contents
Post-Installation Configuration Issues and SolutionsSome error messages displayed during the installation and configuration of Portal Server SRA 7 might not allow you to install and configure the product properly. The following are some of the configuration and installation issues:
Sun Java System Displays Incorrect Error Messages After Installation 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 Note - This incorrect displaying of an error message is fixed in the Sun Java Enterprise System 5 Portal Server SRA 7.1 release. Does Cacao Require a Local Directory Server for Installation? Portal Server 7 uses Java Management Extensions (JMX) 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 a Lightweight Directory Access Protocol (LDAP) server and needs access to the LDAP server for starting. The gateway is deployed in the Demilitarized Zone (DMZ), 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:
Note - Sun Java Enterprise System 5 Portal Server SRA 7.1 release does not require a local directory server in the DMZ for Cacao to start. How Do I Validate Whether Trust Has Been Established Between Two Servers During the Cacao Server Certificate Exchange? 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 installation on the portal node to the security folder on the Cacao installation on the gateway node. Note - The manual step to establish trust between two nodes is automated in the Sun Java Enterprise System 5 Portal Server SRA 7.1 release. Do I Need Both Sun Java System Access Manager and Sun Java System Directory Server for Portal Server 7 Installation? Yes. Both Sun Java System 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 Sun Java System Access Manager and Directory Server reside on the same node. What Is the Difference Between the Profile and Instance Mentioned in the Configuration File Tokens? A profile is created in the PSConsole and includes SRA proxy server configuration information. An instance is a combination of a host name and a profile. Example 1 Profile and Instance For example, create a profile named In the previous scenario, it is possible to use the same profile for multiple instances of SRA proxy servers on multiple hosts. Reference Information for Instance Names Required During Sun Java Enterprise System Installation Use the Should Both Netlet and Rewriter Proxies Be Enabled After Installing Sun Java Enterprise System? Netlet and Rewriter proxies need to be enabled with the help of PSConsole after the installation. Successful installation and configuration of Portal Server SRA 7 does not mean that the gateway uses the Netlet and Rewriter proxies. Manually configure the specific gateways to use the required proxies. How Do I Access PSConsole Through the Gateway? What Are the Requirements for Proper Working of Gateway, Netlet, and Proxylet? To access PSConsole through the gateway:
For gateway, netlet, and proxylet to work properly:
Known Issues and LimitationsSee the Sun Java System Portal Server 7 Release Notes on docs.sun.com to find out about other known problems. How to Report Problems and Provide FeedbackIf you have problems with Portal Server SRA 7, contact Sun customer support using one of the following mechanisms:
So that we can best assist you in resolving problems, please have the following information available when you contact support:
Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions. For documentation feedback, use this form. Accessing Sun Resources OnlineThe docs.sun.com web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities. For More InformationFor more resources, see the Sun Java Enterprise System hub on the BigAdmin portal for systems administrators: http://www.sun.com/bigadmin/hubs/javaes/.
Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License. |
 |
 | |