|
Sun Java Enterprise System Release Notes for HP-UX |
Sun Java™ Enterprise System Release Notes for HP-UX
Version 2005Q4
Part Number 819-8007-10
This document contains important information available at the time of release of Sun Java Enterprise System 2005Q4 for HP-UX. Known limitations and problems, installation notes, and other information are addressed here. Read this document before installing the Sun Java Enterprise System software.
These release notes can be found at the Sun Java Enterprise System documentation web site at http://docs.sun.com/app/docs/prod/entsys.05q4. Check the web site before installing and setting up your software and then periodically thereafter to view the up-to-date release notes and product documentation.
This document contains the following sections:
Third-party URLs are referenced in this document and provide additional, related information.
Release Notes Revision History
Table 1 Revision History
Date
Description
February 2006
Revenue release.
November 2005
Beta release.
About Sun Java Enterprise System 2005Q4 for HP-UXThis section contains the information you need to install the Sun Java Enterprise System software in a HP-UX operating environment. This section covers the following topics:
What’s New in This ReleaseThis section lists the new features for Java ES 2005Q4. To continue adding value for Sun customers, Sun has added enhancements to the existing products. The following fully supported products have been added to the Java Enterprise System license and are maintained by the same systematic features as the rest of the Java Enterprise System portfolio:
Platform support for system level:This section describes the current OS and browser support for Java ES 2005Q4.
Operating System:
Supported Browsers:
For detailed information on the following, refer to the respective Release Notes, all of which can be found at: http://docs.sun.com/app/docs/coll/1258.2.
Table 2 New Features in Java Enterprise System Components
Component
Product
Access Manager
- New delegated administration model
- Improved log files
- Personalization attributes
- Policy status (active / inactive)
- Bulk federation
- Authentication named configuration or chaining name space
- Multiple Authentication instances support
- Refer to the Access Manager Release Notes for new feature content: (http://docs.sun.com/doc/819-8002)
Service Registry
New product in this release
Web Proxy Server
New product in this release
Sun Java Enterprise System Components for HP-UX
The following components are supported in the HP-UX version of Sun Java Enterprise System:
- Sun Java System Access Manager 7 2005Q4
- Sun Java System Administration Server 5 2005Q4
- Sun Java System Application Server 8.1 2005Q4
- Sun Java System Calendar Server 6 2005Q4
- Sun Java System Directory Proxy Server 5 2005Q4
- Sun Java System Directory Server 5 2005Q4
- Sun Java System Instant Messaging 7 2005Q4
- Sun Java System Message Queue 3 2005Q4, Enterprise Edition
- Sun Java System Messaging Server 6.2 2005Q4
- Sun Java System Portal Server 6 2005Q4
- Sun Java System Web Server 6.1 2005Q4
- Service Registry 2005Q4
- Sun Java System Web Poxy Server 4.0.1 2005Q4
Unsupported Components on HP-UX
Sun Java Enterprise System on HP-UX does not support the following components and features:
- Web container support for BEA WebLogic and IBM WebSphere
- HADB Server. HADB Server for Solaris can be downloaded from: http://www.sun.com/download/sdl.jsp?2a1c7bbd=1
- Load Balancer support for Apache and IIS web servers
Hardware and Software Requirements
This HP-UX release of Sun Java Enterprise System is supported only on HP-UX 11i (11.11) PA-RISC platforms. The following table lists the hardware and software Requirements for the complete installation of Java ES requirements:
RAM And HDD Requirements
For Sun Java Enterprise System to be installed on an HP-UX system, the following criteria should be met:
Space and Memory Requirements
Sun Java Enterprise System and its associated components requires a minimum of 2 Gbytes of disk space. The following table lists the space and memory requirements for the various components.
For more information on disk space and RAM requirements, refer to the respective release notes listed in Bugs Fixed in This Release.
Software Requirements
HP-UX Software Group Requirement
This HP-UX release of Sun Java Enterprise System requires the following Perl programming language packages:
Perl (B.5.6.1.F) HP-UX11i
Java 2 Standard Edition Requirement
This HP-UX release of Sun Java Enterprise System is certified with Java 2 Standard Edition (J2SE) 1.5.0.01.00 from Hewlett Packard.
Install Java 2 Standard Edition (J2SE) 1.5.0 (JDK and JRE) before running Sun Java Enterprise System 2005Q4 installer or installing any of its components.
If your system already has J2SE 1.5.0.01.00 runtime environment package Jrel5, installed without the J2SE 1.5.0.01.00 development tools package, Jdk15, install the development tools package prior to installing the Java Enterprise System. This package contains several facilities required by the Java Enterprise System. See the Java Enterprise System Installation Guide at http://docs.sun.com/doc/819-2328 for details on how to determine the version of J2SE installed on your system and how to prepare your system prior to installing Java Enterprise System.
To Gather Information About the J2SE Installation
- Inspect the symbolic link /usr/jdk/entsys-j2se to determine the location of the J2SE installation used by Java Enterprise System:
# ls -l /usr/jdk/entsys-j2se
- Note the location the link points to /opt/java1.5 for example.
- Note down the version number.
- Determine the version of the J2SE installation used by Java Enterprise System:
/opt/java1.5/bin/java -fullversion
For each of the required packages do the following:
Display information about all instances of the package:
swlist -l product Jre15
swlist -l product Jdk15
Bugs Fixed in This ReleaseThe table below describes the bugs fixed in Java Enterprise System 2005Q4. If a component is not listed, no bugs were fixed for 2005Q4.
Compatibility Issues
When you run the Java ES installer, Access Manager 7 2005Q4 has two installation types (or modes):
Portal Server, Messaging Server, Calendar Server, Instant Messaging, and Delegated Administrator are not compatible with the Access Manager 7 2005Q4 enhanced (7.x) installation type. If you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Instant Messaging, or Delegated Administrator, you must select the Access Manager compatible (6.x) installation type (which is the default value).
For more information, see the Access Manager Release Notes:
http://docs.sun.com/doc/819-8002.
Compatibility Issues Between Components
The table below highlights some of the compatibility issues in Java ES 2005Q4 components. For specific information, use the links above to access the appropriate component-level release note.
Important InformationThis section covers the following topics:
Component Release Notes
All information on specific Sun Java Enterprise System components appears in the respective component release notes. Release notes for the components can be found at:
HP-UX Patch Requirements
This section covers the following topics:
Getting HP-UX Patch Updates for Sun Java Enterprise System
To find the patch requirements for a particular Sun Java Enterprise System component, refer to the respective release notes listed in Component Release Notes.
To get HP-UX 11.11i Patches
- Go to http://www.itrc.hp.com
- Click Login in the IT Resource panel.
The Login/Register page appears.
If you do not have a login, you need to create one:
- Enter your User ID and password and click Login.
The IT Resource page appears.
- Click Patch/firmware database under the Maintenance and support (HP products) section.
The patch/firmware database page appears.
- Enter the patch name that you need to download under the Find a specific patch section.
For example: Access Manager needs PHSS_30966 to be installed. When you do a search for this patch, the following results are displayed:
- Select the version of the patch you want to download.
- Click Add to the selected patch list.
The Download option for that patch is displayed.
- Follow the instructions given in the download option to install the required patch.
HP-UX Packages Required to Run Java Enterprise System Components
The following system packages also need to be installed for some of the Java Enterprise System components to be run on HP-UX:
Patch Information
For more information on patches for a given component, refer to the Component Release Notes.
In addition, go to SunSolve at http://sunsolve.sun.com.. Navigate to the Patch Portal. Click “Recommended Patch Clusters” and choose “Java Enterprise System Component Patches”. You can find the product in which they are looking for patches and click on that product link.
For detailed information about Upgrade procedure for any product component from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for HP-UX located at http://docs.sun.com/app/docs/doc/819-4460.
Support for Netscape Security Services 3.9.5
Version 3.9.5 of the Netscape security libraries are included in Java Enterprise System. Directory Server, Directory Proxy and Administration Server may depend on the older version (3.3.x) of these libraries also installed under /opt/sun/private/lib while all other component products that depend on these libraries depend on the newer version (3.9.5) installed under /opt/sun/private/lib.
Version 3.9.5 of the Netscape security libraries is included in Sun Java Enterprise System. Directory Server, Directory Proxy Server, and Administration Server depend on the version of the libraries installed under /opt/sun/private/lib.
Accessibility Features for People With Disabilities
To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at http://sun.com/software/javaenterprisesystem/get.html.
For information on Sun’s commitment to accessibility, visit http://sun.com/access.
HP-UX Installation NotesThe procedures and tasks of installing Sun Java Enterprise System in the HP-UX environment are quite similar to the instructions for installing in the Solaris environment. For all basic Sun Java Enterprise System installation instructions, refer to the Sun Java Enterprise System Installation Guide for Unix http://docs.sun.com/app/docs/doc/819-2328
However, there are some installation differences for HP-UX. The following sections describe issues and tasks that are specific to HP-UX:
Features That Are Not Supported
Java Enterprise System on HP-UX does not support Sun Cluster, Sun Remote Services Net Connect, third party web containers (BEA WebLogic or IBM WebSphere), or Apache and IIS web servers.
Getting the Sun Java Enterprise System Software
- Go to:
http://www.sun.com/software/javaenterprisesystem/index.xml
- Download the HP-UX zip file.
- Unzip the file:
unzip java_es_05q4-hpux-parisc.zip
The directory folder will be HPUX_PA-RISC.
Note
Before you install Java ES on HP-UX read “Preparing for Installation” in the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX at
The following table lists the items in a Sun Java Enterprise System HP-UX distribution.
Installing Sun Java Enterprise System Software From a DVD
The following are the steps for installing Sun Java Enterprise System Software from a DVD:
Directory, Command, and Path Equivalencies
The following tables list the HP-UX directories, commands and paths equivalent to Solaris.
Default Installation Directories for Sun Java Enterprise System Components
The Sun Java™ Enterprise System installer automatically installs components in default directories unless you specify otherwise. In most cases, you can specify a custom location to override a default location when you are using the Configure Now option.
Installation directories for the following components have restrictions:
- Directory Server. You cannot specify the installation location for Directory Server. However, you can specify the location for Directory Server runtime configuration data.
- Portal Server Secure Remote Access. Portal Server Secure Remote Access Core must be installed into the same location as Portal Server.
- Message Queue. You cannot change the location of the installation directories.
The following table lists the default installation directories for the Sun Java Enterprise System components.
Installable Packages
The following sections list the HP-UX 11.11i packages installed by the Sun Java Enterprise System installer:
Uninstall Packages for Java Enterprise System on HP-UX
The following table lists the uninstall packages for Sun Java Enterprise System.
Table 11 Uninstall Packages for Java Enterprise System on HP-UX
Component
Packages
Uninstall program
sun-entsys-uninstall
sun-entsys-uninstall-l10n
Java Enterprise System Packages on HP-UX Installed for Components
This section lists installed Java Enterprise System packages on HP-UX for each Sun Java Enterprise System component.
Access Manager HP-UX Packages
Administration Server HP-UX Packages
Application Server HP-UX Packages
Calendar Server HP-UX Packages
Communications Express HP-UX Packages
Table 16 Communications Express Packages for HP-UX
Component
Packages
Communications Express
sun-uwc
Locale packages
sun-uwc-de
sun-uwc-es
sun-uwc-fr
sun-uwc-ja
sun-uwc-ko
sun-uwc-zh_CN
sun-uwc-zh_TW
Directory Server HP-UX Packages
Directory Proxy Server HP-UX Packages
Instant Messaging HP-UX Packages
Message Queue HP-UX Packages
Messaging Server HP-UX Packages
Portal Server HP-UX Packages
Web Server HP-UX Packages
Web Proxy Server HP-UX Packages
Service Registry HP-UX Packages
Table 26 Service Registry Packages for HP-UX
Component
Packages
Service Registry
sun-soar-sdk
sun-soar-server
Java Enterprise System Packages on HP-UX Installed for Shared Components
The following table lists the names of the HP-UX packages distributed for each shared component.
Post-installation Configuration
When the Sun Java™ Enterprise System installer finishes installation, most components require that you perform additional configuration tasks before the Sun Java Enterprise System environment is operational. The extent of the tasks depends on the configuration type you selected (Configure Now or Configure Later), and whether or not your components will be configured with the Sun Cluster software.
This section contains the differences between HP-UX and Solaris as in the Sun Java Enterprise System Installation Guide (http:/docs.sun.com/doc/819-2328):
Installed Packages
Before acting on the information in this chapter, you should have completed the installation of the Sun Java Enterprise System components. You can use the swlist command to verify that the component packages have been installed. A list of packages associated with the components is contained Installable Packages
MANPATH Setup
If your components have man pages, you will need to verify that your MANPATH environmental variable is set correctly. After installation, the man pages for the Sun Java Enterprise System components are located in default directories. In some cases, the correct location for the component man pages is already set in your MANPATH environment variable. If the location of your man pages is present, you do not need to take any action. If the location of your man pages is not present, you need to add it to your MANPATH environment variable.
The following table indicates the default locations for the man pages of the Sun Java Enterprise System components. If a component is not listed, the component does not have man pages.
To Update Your MANPATH Variable
The following example shows how to verify that the man pages are available in the C shell:
- On the command line, check your MANPATH environment variable to see if the correct path is already there.
env
- If the correct path is not there, add the location of your Sun Java Enterprise System component man pages to your MANPATH environment variable.
Update the /etc/MANPATH file with the required MANPATH. For example, add this line to the /etc/MANPATH file:
/opt/sun/man
The new man pages will be fully accessible, regardless of path.
- Verify that the man pages are accessible. For example, the following commands should display the asadmin man page for Application Server:
man asadmin
Configure Now Option: Procedures
If you selected the Configure Now option during installation, you were asked to specify configuration values during the installation session. Some of the components that were configured during installation require additional configuring as described in this section. A summary report containing the values that were set during installation is available:
/var/opt/sun/install/logs
The following sections detail the configurations necessary for the particular Sun Java Enterprise System components. If your component does not require additional configuration after a Configure Now installation, proceed to Starting and Stopping Components to verify configuration.
The following sections contain postinstallation configuration information for the Configure Now option:
Configuring Access Manager After a Configure Now Installation
Although you can start Sun Java System Access Manager and log into the Access Manager console immediately after running the Sun Java Enterprise System installer, you cannot perform basic user management operations until you complete some final configuration steps. These steps differ depending on whether or not Access Manager is using a Sun Java System Directory Server instance that is already provisioned with user data.
The next sections explain what to do in the following cases:
When Directory Server is Provisioned With User Data
When Directory Server is already provisioned with user data, refer to “Configuring Access Manager with a Provisioned Directory Server” in the Sun Java System Access Manager Migration Guide, http://docs.sun.com/doc/817-5708, for a description of the final configuration steps.
When Directory Server is Not Yet Provisioned With User Data
When Directory Server is not provisioned with user data, perform the steps in the following sections:
Caution
Before performing the tasks in this section, ensure that Directory Server is configured and running.
Enabling the Referential Integrity Plug-in
When the referential integrity plug-in is enabled, it performs integrity updates on specified attributes immediately after a delete or rename operation. This ensures that relationships between related entries are maintained throughout the database.
To Enable the Referential Integrity Plug-in
- In Directory Server console, click Configuration.
- In the navigation tree, double-click Plug-ins to expand the list of Plug-ins.
- In the Plug-ins list, click Referential integrity postoperation.
- In the properties area, check the Enable plug-in box.
- Click Save.
- Restart Directory Server to enable the plug-in.
Database indexes enhance the search performance in Directory Server.
To Add Access Manager Indexes
- In Directory Server console, click Configuration.
- Add the nsroledn index.
- In the navigation tree, double-click the Data icon, then click the root suffix that contains the directory entries you want to use in Access Manager.
- Click the Indexes tab.
- Under Additional Indexes, for the nsroledn attribute, check the following checkboxes: Equality, Presence, and Substring.
- Click Save.
- In the Indexes window, after the index is successfully created, click Close.
- Add the memberof index.
- In the Indexes tab, click Add attribute.
- In the Select Attributes window, select the attribute memberof, then click OK.
- In the Indexes tab, for the memberof attribute, check the following checkboxes: Equality and Presence.
- Click Save.
- In the Indexes window, after the index is successfully created, click Close.
- Add the iplanet-am-static-group index.
- In the Indexes tab, click Add attribute.
- In the Select Attributes window, select the attribute iplanet-am-static-group, and then click OK.
- In the Indexes tab, for the iplanet-am-static-group attribute, check the following checkbox: Equality.
- Click Save.
- In the Indexes window, after the index is successfully created, click Close.
- Add the iplanet-am-modifiable-by index.
- In the Indexes tab, click Add attribute.
- In the Select Attributes window, select the attribute iplanet-am-modifiable-by, and then click OK.
- In the Indexes tab, for the iplanet-am-modifiable-by attribute, select the Equality checkbox.
- Click Save.
- In the Indexes window, after the index is successfully created, click Close.
- Add the iplanet-am-user-federation-info-key index.
- In the Indexes tab, click Add attribute...
- In the Select Attributes window, select the attribute iplanet-am-user-federation-info-key, then click OK.
- In the Indexes tab, for the iplanet-am-user-federation-info-key attribute, check the following checkbox: Equality.
- Click Save.
- After the index is successfully created, click Close in the Indexes window.
- Restart Directory Server.
Configuring Message Queue After a Configure Now Installation
Message Queue requires no additional configuration. However, a common optional task is to configure Message Queue for automatic startup. To perform this task, become superuser and edit properties in the imqbrokerd.conf configuration file (in /etc/opt/sun/mq). The properties to edit are:
- AUTOSTART, which specifies (YES or NO) if the broker is automatically started at boot time. The default value is NO.
- ARGS, which specifies command line options and arguments to pass to the broker startup command. See the Sun Java System Message Queue Administration Guide (http://docs.sun.com/doc/819-2571) for a listing and description of imqbrokerd command line options. (For example -name instanceName)
- RESTART, which specifies (YES or NO) if the broker is automatically restarted if it abnormally exits. The default value is YES.
Additional configuration for Message Queue is discussed in the Sun Java System Message Queue Administration Guide (http://docs.sun.com/doc/819-2571). For example, you might want to change the default administration password.
Configuring Portal Server After a Configure Now Installation
Final configuration steps for Portal Server depends on the Sun web container it is deployed.
If you are using Application Server or Web Server as the web container for Portal Server, you must apply changes to the instance. Use the instructions in Chapter 2, “Post Installation Configuration” of the Sun Java System Portal Server Administration Guide (http://docs.sun.com/app/docs/doc/819-4154).
Configure Later Option: Procedures
If you selected the Configure Later option during installation, the Sun Java Enterprise System installer placed the component package files in their respective directories. No parameter setting was done, and most components are not operational because runtime services are not available.
A number of the components include configuration tools for completing a Configure Later installation. After running the configuration tools, you can make any additional changes by following the instructions in this guide and in the product documentation for each component.
The following sections contain postinstallation configuration information for the Configure Later option:
Configuring Access Manager After a Configure Later Installation
After a Configure Later installation, the packages are installed and you are ready to configure Access Manager using the Access Manager configuration script, identity_svr_base/bin/amconfig. Instructions for using this program are contained in the Sun Java System Access Manager Administration Guide, http://docs.sun.com/app/docs/doc/819-2137
Configuring Administration Server After a Configure Later Installation
After a Configure Later installation, packages are installed and you are ready to begin Administration Server configuration.
To Configure Administration Server After a Configure Later Installation
- Start the configuration utility. For example,
/opt/sun/sbin/mpsadmserver configure
Follow the instructions on each screen.
- Ensure that access permissions for the files under <server root>/alias have been set to prevent access by all user accounts other than those of the servers installed there.
- Verify the common server settings and the Administration Server settings.
Update the settings as needed. Information on these setting can be found in the Sun Java System Administration Server Administration Guide (http://docs.sun.com/app/docs/doc/817-7612).
Note
If Administration Server was installed with Access Manager, most of the configuration in Step 3 was completed during installation.
Configuring Application Server After a Configure Later Installation
After a Configure Later installation, packages are installed and you are ready to begin Application Server configuration.
To Configure Application Server After a Configure Later Installation
Configuring Calendar Server After a Configure Later Installation
Calendar Server cannot be configured by the Sun Java Enterprise System installer.
To Configure Calendar Server After a Configure Later Installation
- Configure Directory Server for communications services (Calendar Server, Messaging Server and the Delegated Administrator Utility) by running the Directory Preparation Script (comm_dssetup.pl).
Note
Skip this step if you have already run the Directory Preparation Script on the same Directory Server during configuration of another communications component.
- Verify that Directory Server is running.
- On the machine where Directory Server is installed, run the Directory Preparation Script:
perl /opt/sun/comms/dssetup/sbin/ comm_dssetup.pl
- When prompted by the script, select Schema 2 Native Mode as the schema type unless you need to retain compatibility with previous versions of Calendar Server, Messaging Server, or custom applications. For more information about making the appropriate choice, see Chapter 2, “Configuring Your LDAP Directory,” in the Sun Java System Communications Services Delegated Administrator Guide (http://docs.sun.com/app/docs/doc/819-2658).
- Verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name. For example:
192.18.99.999 mycomputer.company.com loghost
- If you intend to use Delegated Administrator to provision users for Calendar Server, you must perform additional steps to configure Delegated Administrator. Instructions for configuring the utility and provisioning users are contained in the Sun Java System Communications Services Delegated Administrator Guide (http://docs.sun.com/app/docs/doc/819-2658).
Caution
Consider this step only if your installation includes Access Manager and LDAP Schema 2, and if this step was not done during configuration of another communications component.
- Configure Calendar Server by running the Calendar Server configuration program,
cal_svr_base/calendar/sbin/csconfigurator.sh.For information on configuring Calendar Server, refer to the Sun Java System Calendar Server Administration Guide, http://docs.sun.com/app/docs/doc/819-2433.
Configuring Communications Express After a Configure Later Installation
Communications Express cannot be configured by the Sun Java Enterprise System installer.
To Configure Communications Express After a Configure Later Installation
- Configure Communications Express for communications services (Calendar Server, Messaging Server and the Delegated Administrator Utility) by running the Directory Preparation Script (comm_dssetup.pl).
Note
Skip this step if you have already run the Directory Preparation Script on the same Directory Server during configuration of another communications component.
- Complete configuration using the Communication Express configuration program, uwc_base/sbin/config-uwc. Instructions are in Chapter 2, “Installing and Configuring Communications Express” in the Sun Java System Communications Express Administration Guide ((http://docs.sun.com/app/docs/doc/819-2658).
Configuring Directory Server After a Configure Later Installation
After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Directory Server.
To Configure Directory Server After a Configure Later Installation
- Start the configuration utility. For example:
/opt/sun/sbin/directoryserver -u 5.2 configure
Follow the instructions on each screen.
- (Optional) Many command-line scripts written in Perl can read the bind password interactively (-w option). To enable this functionality, do the following:
- Install the Term::ReadKey Perl module, available separately from CPAN (http://cpan.org).
- Edit each Perl script to read the bind password interactively by uncommenting the appropriate lines.
All other Perl script functionality remains available without the Term::ReadKey module.
- Verify the common server settings and the Directory Server settings.
Update the settings as needed.
Configuring Directory Proxy Server After a Configure Later Installation
After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Directory Proxy Server.
To Configure Directory Proxy Server After a Configure Later Installation
- Configure the Directory Proxy Server instance using the quickstart.tcl script. For example:
# /opt/sun/directory-proxy-server/5.2/bin/tcl8.2/tclsh /opt/sun/directory-proxy-server/5.2/bin/dps/install/script/quickstart.tcl -cid <cid_path> -serverroot <serverroot_path> -listen <DPS port number> -password <password> -userID <admin user id>
The arguments of the quickstart.tcl script are described in the following table.
- Verify the common server settings.
- Update the common server settings for Directory Proxy Server.
- Verify the Directory Proxy Server configuration.
- Start the Directory Proxy Server.
Configuring Instant Messaging After a Configure Later Installation
Instant Messaging cannot be configured by the Sun Java Enterprise System installer. When you install the server, the multiplexor is also installed and enabled. If you want to support only a multiplexor on a host, you must disable the server installed on that host. For instructions, refer to the Sun Java System Instant Messaging Administration Guide (http://docs.sun.com/app/docs/doc/819-0430).
Instructions for using the Instant Messaging configure utility, im_svr_base/configure, are contained in Chapter 1, “Configuring Instant Messenger After Installation” in the Sun Java System Instant Messaging Administration Guide (http://docs.sun.com/app/docs/doc/819-0430).
Configuring Message Queue After a Configure Later Installation
The Message Queue component requires no additional configuration. However, a common optional task is to configure Message Queue for automatic startup. For instructions on performing this task, refer to Configuring Message Queue After a Configure Now Installation.
Configuring Messaging Server After a Configure Later Installation
Messaging Server cannot be configured by the Sun Java Enterprise System installer.
To Configure Messaging Server After a Configure Later Installation
- Configure Directory Server for communications services (Calendar Server, Messaging Server and the Delegated Administrator Utility) by running the comm_dssetup.pl script.
Note
Skip this step if you have already run the Directory Preparation Script on the same Directory Server during configuration of another communications component.
- Verify that Directory Server is running.
- On the machine where Directory Server is installed, run the Directory Preparation Script:
perl /opt/sun/comms/dssetup/sbin/comm_dssetup.pl
- When prompted by the script, select Schema 2 Native Mode as the schema type unless you need to retain compatibility with previous versions of Calendar Server, Messaging Server, or custom applications. For more information about making the appropriate choice, see Chapter 7, “Understanding Messaging Server Schema and Provisioning Options,” in the Sun Java System Communications Services Deployment Planning Guide (http://docs.sun.com/app/docs/doc/819-2660).
- Verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name. For example:
192.18.99.1 mycomputer.company.com loghost
- If you intend to use Delegated Administrator to provision users for Messaging Server, you must perform additional steps to configure Delegated Administrator. Instructions for configuring the utility and provisioning users are contained in the Sun Java System Communications Services Delegated Administrator Guide (http://docs.sun.com/app/docs/doc/819-2658).
Caution
Consider this step only if your installation includes Access Manager and LDAP Schema 2, and if this step was not done during configuration of another communications component.
- Configure Messaging Server by running the initial runtime configuration program for Messaging Server, msg_svr_base/sbin/configure.
For information on configuring Messaging Server, refer to the Sun Java System Messaging Server Administration Guide (http://docs.sun.com/app/docs/doc/819-2650).
Configuring Portal Server After a Configure Later Installation
Final configuration steps for Portal Server depends on the Sun web container it is deployed.
Configuring Portal Server After a Configure Later Installation on Application Server or Web Server
Portal Server provides a common configurator that can be used to configure all Portal Server subcomponents as well as Portal Server Secure Remote Access.
To Configure Portal Server After a Configure Later Installation on Application Server or Web Server
- Create a runtime configuration for Portal Server by running the Portal Server configurator, portal_svr_base/lib/configurator.
Instructions for running the configurator as well as descriptions of the settings used by the configurator are contained in the “Minimal Installation Configuration” section in Chapter 2 of the Sun Java System Portal Server Administration Guide (http://docs.sun.com/app/docs/doc/819-4154).
- Apply changes to the instance. Use the instructions in the “Portal Server Post-Installation Tasks” section in Chapter 2 of the Sun Java System Portal Server Administration Guide (http://docs.sun.com/app/docs/doc/819-4154).
Configuring Web Server After a Configure Later Installation
After a Configure Later configuration installation, the packages are installed and you are ready to configure Web Server.
To Configure Web Server After a Configure Later Installation
Configuring Web Proxy Server After a Configure Later Installation
After a Configure Later configuration installation, the packages are installed and you are ready to configure Web Proxy Server.
To Configure Web Proxy Server After a Configure Later Installation
- Configure Web Proxy Server by running the Web Proxy Server configuration program,
web_proxy_svr_base/bin/proxy/bin/configureServer -f <propfile> -l <logfile>
The configuration program creates a runtime configuration, including an admin server and a default instance.
- Verify the common server settings and the Web Proxy Server settings.
Update the settings as needed. Additional information on these settings can be found in the Sun ONE Web Server Installation and Migration Guide (http://docs.sun.com/app/docs/doc/819-0131)
Configuring Service Registry After a Configure Later Installation
Service Registry cannot be configured by the Sun Java Enterprise System installer. After a Configure Later installation, packages are installed and you are ready to begin Service Registry configuration.
To configure Service Registry After a Configuration Later Installation
Before you begin the configuration later installation, Login as root or become superuser
- Change to the ServiceRegistry-base/install directory.
cd /opt/sun/SUNWsoar/install
- Edit the modifiable properties in the file install.properties. For security reasons, it is recommended that you not edit this file to change the password values. Instead, specify these values on the command line.
- Verify that the JAVA_HOME environment variable is set.
The ant command requires the JAVA_HOME environment variable to be set.
- Export the SHLIB_PATH variable as indicated below:
export SHLIB_PATH=$SHLIB_PATH:/opt/sun/private/lib
where /opt/sun is the default installation directory.
Note
Exporting SHLIB_PATH is done as a workaround for Revenue release. For more information refer to the Service Registry Release Notes.
- After editing the install.properties file, run the following command (all on one line):
/opt/sun/share/lib/ant/bin/ant –f build-install.xml install
To specify changed passwords on the command line, specify the following options to the command (all on one line):
/opt/sun/share/lib/ant/bin/ant -f build-install.xml -Dregistry.install.RegistryServerKeystorePassword=passwd1 -Dregistry.install.AdministratorPassword=passwd2-Dregistry.install.ApplicationServerKeystorePassword=passwd3 install
The Registry configuration process creates an Application Server domain at RegistryDomain-base/domains/${registry.install.DomainName}. The default domain name is registry. The configuration process then starts the domain, deploys the Registry, and leaves the domain running.
The Registry configuration process installs the Registry database and server keystore in the directory RegistryDomain-base/3.0. This directory is not removed when the Registry is uninstalled, so that the database can be preserved for use in a future release. The administrator has control over when and whether to remove this directory.
The RegistryDomain-base location is /var/opt/sun/SUNWsoar
- Review the output of the ant install command for any errors. If there are no errors, you can now begin using the Web Console or the Admin Tool.
Starting and Stopping Components
This chapter provides instructions for starting and stopping Sun Java™ Enterprise System components that have been installed and configured. You can use the procedures in this section to verify that components are operational.
This chapter includes the following sections:
Prerequisites
Before using the procedures in this chapter, you should have completed all the post-installation configuration tasks specified in Troubleshooting Installation Problems.
Startup Sequence for Sun Java Enterprise System
To start Sun Java Enterprise System, you start the components one after another, in a specific sequence. You start with the basic services provided by Directory Server and your web container (Web Server or an application server). Sun Java Enterprise System creates runnable instances of these services during installation. Since Portal Server and Access Manager run inside the web container, they start when you start the web container.
The general sequence for bringing up the entire Sun Java Enterprise System component set is shown in the following table. The left column lists the order in which you should perform the startup, the middle column describes the task, and the right column lists the location of the instructions for performing the task.
Table 30 Preferred Startup Sequence for Sun Java Enterprise System
Order
Task
Location of Instructions
1
Start your directory server.
A. Start Directory Server.
B. Start Administration Server.
C. Start Server Console.
2
Start your chosen web container. Access Manager and Portal Server are started if they are installed.
Start Application Server (also starts Message Queue).
To Verify Access Manager and Portal Server on Application Server
Start Web Server.
3
Start Portal Server Secure Remote Access.
4
Start Instant Messaging.
5
Start Messaging Server.
6
Start Calendar Server.
7
Start Directory Proxy Server.
To shut down the entire Sun Java Enterprise System component set, reverse the sequence.
Starting and Stopping Access Manager
Access Manager depends on Directory Server and a web container. To verify Access Manager, you access your specific deployment configurations of Access Manager on the web containers:
This section contains the following procedures:
To Start Access Manager
To Verify Access Manager and Portal Server on Application Server
- Use the following URL to access the default page:
http://appserver-host:port/amconsole
The Access Manager login page appears.
- Log in.
Your login to Access Manager confirms successful deployment of Access Manager on Application Server. The default administrator account is amadmin. a new browser, use the following URL to display the sample Desktop:
http://server:port/portal
Display of the sample Desktop confirms successful deployment of Portal Server on Application Server.
For a mobile device:
http://server:port/portal/dt
To Verify Access Manager and Portal Server on Web Server
- Use the following URL to access the default page:
http://webserver-host:port/amconsole
The Access Manager login page appears.
- Log in.
Your login to Access Manager confirms successful deployment of Access Manager on Web Server.
- In a new browser, use the following URL to display the sample Desktop:
http://server:port/portal
Display of the sample Desktop confirms successful deployment of Portal Server on Web Server.
For a mobile device:
http://server:port/portal/dt
To Stop Access Manager
Starting and Stopping Administration Server
To verify Administration Server, start the Administration Server and the Console Server. Administration Server depends on Directory Server.
To Start Administration Server
To Stop Administration Server
To Start Server Console
- If necessary, configure the $DISPLAY variable to display the Console Server on your machine.
- Verify that the Administration Server processes are running. For example:
/usr/bin/ps -ef | grep admin-serv/config
- Enter the following:
/opt/sun/mps/serverroot/startconsole
- Verify that the Server Console process is running. For example:
/usr/bin/ps -ef | grep console
To Stop Server Console
Starting and Stopping Application Server
To verify Application Server, you need to start the Application Server instance, then start the graphical Administration interface and log in. Application Server depends on Message Queue.
To Start Application Server
- Navigate to application_svr_base/bin and enter this command:
% asadmin start-domain --user admin-id --passwordfile <location _of_passwordfile>/passwordfile-name --domain domain-name
where content of password file should be in the following format
AS_ADMIN_PASSWORD=<PASSWORD>
or
% asadmin start-domain --user admin-id domain-name
Give the password when prompted.
- Enter the values that you provided during installation.
A message is displayed telling you that the server is starting:
Starting Domain domain1, please wait. Log redirected to install_dir...
When the startup process has completed, an additional message is displayed:
Domain domain1 started
- Start individual Application Server instances. For example:
./asadmin start-domain domain1
Note
If you receive a message indicating failure to start, configuration changes might not be applied yet. In this case, run the asadmin reconfig command. For example:
asadmin reconfig --user admin --password adminadmin --host\ localhost --port 4849 server
- Verify that the Application Server processes are running. For example:
/usr/bin/ps -ef | grep appserv
root 9888 9886 0 12:55:46 pts/tc 0:00 /bin/sh/var/opt/sun/appserver/nodeagents/sqe-agent/sqe-server/
root 9886 1 0 12:55:38 pts/tc 0:11 /opt/sun/appserver/lib/appservAgent sqe-agent
root 9898 9890 0 12:55:53 pts/tc 0:31 /opt/sun/appserver/lib/appserv sqe-server
root 9890 9888 0 12:55:46 pts/tc 0:00 /opt/sun/appserver/lib/appservLauncher/opt/sun/appserver/lib/a
root 9869 1 0 12:54:28 pts/tc 1:03 /opt/sun/appserver/lib/appservDAS sqe-domain
To Access the Application Server Graphical Interface
To verify that the server is running on your system, use the following URL format in your browser: https://localhost:port
Replace the localhost variable with the name of the system that the browser is currently running on. If Application Server software is running on another system, substitute the name of that system for localhost. Replace the port variable with the Domain Administration Server’s port number assigned during installation. The default port number is 8080. If you changed the port number during the installation, use that number instead. For example:
https://mycomputer.example.com:4849
You should see the Application Server Welcome page if the Domain Administration Server is running.
To Stop Application Server
Starting and Stopping Calendar Server
Calendar Server depends on Directory Server.
To Start Calendar Server
To Access the Calendar Server Graphical Interface
If you are already provisioned in the LDAP directory that Calendar Server points to, you can log into Calendar Server. In your browser, use the http://hostname.domain[:port] format to access Calendar Server. For example:
http://mycomputer.example.com:8000
At initial login, Calendar Server creates a default calendar for you. Your login to Calendar Server confirms successful installation.
To Stop Calendar Server
Starting and Stopping Communication Server
Unified Web Client depends on webcontainer (WebServer/Application Server). It is an integration application for Calendar Server, Messaging Server And Address Book. As it is a client Program, there is nothing to start and stop.
To Access the Unified Web Client Graphical interface
- Navigate to uwc_svr_base/uwc/sbin
- Configure Unified Web Client
./config-uwc (Refer to the Administration Document of UWC)
- Restart webserver for deployment to take place.
- In your browser, use the
http://hostname.domain[:webport]/deployed-uri format to access UWC.
For example: http://mycomputer.example.com:80/uwcStarting and Stopping Directory Server
If Directory Server is part of a cluster, verify that you are working on the active node for the logical host. Directory Server has no dependencies.
To Start Directory Server
To Stop Directory Server
Starting and Stopping Directory Proxy Server
Log in as root if the server runs on ports less than 1024. On ports greater than 1024, log in either as root or with the server's administrator account. Directory Proxy Server depends on Administration Server.
To Start Directory Proxy Server
- Navigate to <DPS Server root>/dps-instance-name (instance-name is usually machine name). For example, the default is:
/opt/sun/mps/serverroot/dps-host1
- Start the Directory Proxy Server process.
./start-dps
- Verify that the Directory Proxy Server process is running. For example:
/usr/bin/ps -ef | grep dps
To Stop Directory Proxy Server
Starting and Stopping Instant Messaging
Instant Messaging depends on Directory Server and Web Server.
To Start Instant Messaging
Note
There are many ways to start the Instant Messaging client. For information, refer to the Sun Java System Instant Messaging Administration Guide (http://docs.sun.com/app/docs/doc/819-0430).
To Stop Instant Messaging
Starting Message Queue
To Start Message Queue
Starting and Stopping Messaging Server
Messaging Server depends on Directory Server and Administration Server.
To Start Messaging Server
- Navigate to msg_svr_base/sbin.
- Start the Messaging Server processes.
./start-msg
- Verify that the Messaging Server processes are running. For example.
/usr/bin/ps -ef | grep messaging
/opt/sun/messaging/lib/enpd
/opt/sun/messaging/lib/stored -d
/opt/sun/messaging/lib/popd -d 5
/opt/sun/messaging/lib/imapd -d 5 -D 6
/opt/sun/messaging/lib/mshttpd -d 5 -D 6
/opt/sun/messaging/lib/dispatcher
/opt/sun/messaging/lib/job_controller
/opt/sun/messaging/lib/tcp_lmtp_server
/opt/sun/messaging/lib/tcp_smtp_server
/opt/sun/messaging/lib/tcp_smtp_server
/opt/sun/messaging/lib/imsched
/opt/sun/messaging/lib/watcher
Note that the list of processes varies according to the Messaging Server features you have configured use.
To Access Messenger Express
If you are already provisioned in the LDAP directory that Messaging Server points to, you can log into Messaging Server. In your browser, use the http://hostname.domain[:port] format to access Messenger Express.
For example:
http://mycomputer.example.com:8080
To Stop Messaging Server
Some Messaging Server processes might take several minutes to stop because they wait for their current transactions to complete.
Starting and Stopping Portal Server
The Portal Server startup and shutdown mechanisms are part of the startup and shutdown mechanisms for the web container (either Web Server or an application server). Portal Server depends on Directory Server, Access Manager or the Access Manager SDK, and a web container.
To verify Portal Server, go to the following sections:
Starting and Stopping Portal Server Secure Remote Access
Portal Server Secure Remote Access depends on Portal Server and Access Manager or the Access Manager SDK.
To Start Portal Server Secure Remote Access
- After installing the Gateway and creating the required profile, run the following command to start the Gateway:
/opt/sun/portal_svr/bin/gateway -n default start
The default is the default gateway profile that is created during installation.
You can create your own profiles later, and restart the Gateway with the new profile.
- Run the following command to check if the Gateway is running on the specified port:
netstat -a | grep port-number
The default Gateway port is 443.
To Stop Portal Server Secure Remote Access
Starting and Stopping Web Server
Web Server has no dependencies.
To Start Web Server
- Navigate to web_svr_base/https-admserv.
- Start the Web Server administration process.
./start
- Navigate to web_svr_base/https-hostname.domain.
- Start the Web Server instance.
./start
- Verify that the Web Server processes are running. For example:
/usr/bin/ps -ef | grep webservd
./webservd-wdog -r /opt/sun/webserver-d /opt/sun/webserver/https-admserv/config -n http
./webservd-wdog -r /opt/sun/webserver -d /opt/sun/webserver/https-host1.example.com
webservd -r /opt/sun/webserver -d /opt/sun/webserver/https-admserv/config -n https-admserv
webservd -r /opt/sun/webserver -d /opt/sun/webserver/https-admserv/config -n https-admserv
webservd -r /opt/sun/webserver -d /opt/sun/webserver/https-host1.example.com/config
webservd -r /opt/sun/webserver -d /opt/sun/webserver/https-host1.example.com/config
To Access the Web Server Graphical Interface
- In your browser, use the http://hostname.domain:port format to access the Web Server interface. For example:
http://host1.example.com:80
- Use the http://hostname.domain:adminport format to access the administration server. For example:
http://host1.example.com:8888
Your login to Web Server confirms successful installation.
To Stop Web Server
Starting and Stopping Web Proxy Server
To start Web Proxy Server
To start Socks Server
To access Web Proxy Server admin Graphical Interface
To stop Web Proxy Server
To stop Socks Server
Starting and Stopping Service Registry
The configuration process for the Registry starts the Application Server domain in which the registry is deployed. After you perform certain administrative tasks, you need to stop and restart the domain.
The Admin Console informs you if you need to restart the domain. You can use the Admin Console to perform this task. If you are using the asadmin command, you can use Ant tasks to stop and start the domain.
To Start Service Registry
To Stop Service Registry
To Restart Service Registry
To access the Web Console
Troubleshooting Installation Problems
The following sections provide suggestions on how to resolve Sun Java™ Enterprise System installation and uninstallation problems:
General Troubleshooting Methods
This section provides general guidelines for tracking down the source of a problem. The following topics are addressed:
Examine Installation Log Files
If a problem occurs during installation or uninstallation, check the following log for problems relating to Sun Java Enterprise System Installer
For system related problems check the appropriate log files in the logs directory:
Most logs have two versions:
The following table lists the formats of the log files.
Table 31 Sun Java Enterprise System Log File Name Formats
Logged Entity
Log File Name Format
Installer: components
Java_Enterprise_System_install.Atimestamp
Java_Enterprise_System_install.Btimestamp
Java_Enterprise_System_Config_Log.id
Installer: shared components
JES_V4_OrionConfig_log.timestamp
JES_V4_OrionPanelFlow_log.timestamp
Uninstall program
Java_Enterprise_System_uninstall.Atimestamp
Java_Enterprise_System_uninstall.Btimestamp
Java_Enterprise_System_Config_Log.id
Installation summary
Java_Enterprise_System_Summary_Report_install.timestamp
Java_Enterprise_System_Summary_Report_ uninstall.timestamp
JES_V4_MasterLog_log.timestamp
Dependencies
Java_Enterprise_System_Dependency_Check_install.timestamp
Examining the uninstall and installer log files, along with the Sun Java Enterprise System configuration log and component logs, can help locate the source of uninstallation problems. For example, you can compare the packages listed in the installation log to the packages listed in the uninstallation log.
Many components write installation log files to the same directory. For more information about component log files, refer to Component Troubleshooting Information.
To use the log files for troubleshooting, attempt to isolate the first problem that occurred. Often, the first problem leads to successive problems. Use the following sequence:
The log files can give you clues that determine your next steps, such as these:
Examine Component Log Files
If a problem occurs starting a component, examine its log files. Many component log files are listed under Component Troubleshooting Information.
Verify Product Dependencies
A number of components have installation-time interdependencies. Problems that affect one component can affect other components. To check for unmet interdependencies, familiarize yourself with the information in Sun Java Enterprise System Installation Guide (http://docs.sun.com/app/docs/doc/819-2328) How Do Component Interdependencies Affect My Installation? Next, check the following:
- Review the summary file and log files to see whether related products have failed. These might provide a clue as to what to fix first.
- Check that you have specified correct connection information. For example:
- Does the information that you provided when configuring Directory Server match the directory information you provided for components that use Directory Server?
- Does the Access Manager information that you provided for Portal Server or Portal Server SRA match the information you provided for Access Manager?
Check Resources and Settings
The following host-level issues can cause installation problems.
- Updates. Have you applied the recommended updates (patches)?
- Disk space. How is the disk partitioned, and to what partitions do installation directories point? The installation directories /var/opt and /etc/opt, /opt, /, /tmp or the non-default directories that you specify, need sufficient disk space.
- Network ports. During configuration, you supply port numbers for Sun Java Enterprise System components. Check the following:
- Examine the standard port numbers in the file /etc/services.
- Look at the summary log file to compare your settings with the standards. Did you mistype a port number or set one server to the port that is typically used for another?
- Use the command netstat -a to view current port use on the system. Did you assign a port number that was already in use?
- IP addresses. During configuration, you specify IP addresses. Check that you entered the correct IP addresses. These are some questions to resolve:
Run Verification Procedures
If you are having problems starting components, verify that component processes are running, then perform the verification procedures in Troubleshooting Installation Problems.
Check Directory Server Connectivity
If you are installing a component that relies on Directory Server, problems can be caused by one of these problems:
The interactive modes of the installer check for Directory Server connectivity during installation, but silent mode does not do so. If you perform a silent installation when Directory Server is not available, Access Manager or Portal Server could fail during installation.
Remove Web Server Files and Directory
To prevent the overwriting of customized files, such as edited configuration files, Web Server cannot be installed into a directory that contains files.
If you are reinstalling Web Server, check the installation directories to ensure that they are empty. If they are not empty, archive the files elsewhere and retry the installation.
Verify Passwords
The installer requires that you enter a number of passwords for components. If you are installing different components on different machines, it is important to ensure that you supply matching passwords on each machine.
To resolve password problems, you might need to uninstall and then reinstall. If the uninstall fails, refer to Installation Fails Due to Leftover Files During Uninstallation.
Examine the Installed or Uninstalled Components
If you have installed components but are having problems and cannot reinstall or uninstall, check the packages installed using HP-UX swlist command.
Verify Administrator Access
During uninstallation, you might need to grant administrator access to the uninstall program, as described in Sun Java Enterprise System Installation Guide (http://docs.sun.com/app/docs/doc/819-2328) Administrator Access for the Uninstall Program. Make sure you provide the correct user IDs and passwords during uninstallation.
Installation Problems
This section addresses the following problems you might encounter during installation:
Installation Fails Due to Leftover Files During Uninstallation
If an uninstallation fails, it can leave behind components or packages. In such a case, you must manually remove the components or packages before you reinstall Sun Java Enterprise System. You might discover this problem in the following ways:
If you have removed all the product and shared components related directories and have not uninstalled the products then you need to uninstall all the products before proceeding to the installation again.
Installer Completes Installation but Product(s) Not Installed on Machine
The installer completes the installation according to the process but the products are not installed on your machine.This could probably be because of the product or products being uninstalled by user manually with swremove without using uninstaller.
Suggestion. You need to run the uninstaller and select the products you wanted to reinstall. It will clear the registry entries. Take the backup of the present productregistry and start installation once again
Installer/Uninstaller Hangs at Some Panel Without Any Exceptions
If the installer is abnormally terminated by the user during the installation process, it would create a lock file:
viz.
productregistry.access.lock
productregistry.access.tmp.This induces the installer/uninstaller to hang.
Suggestion. You need to remove both the files from the following location: /var/adm/sw
Installation Fails Due to Dependencies
If some of the dependencies are not met, the installation fails. Refer to the following log to see the details of the failure
Suggestion. You need to ensure that all dependent products which are previously installed are not uninstalled manually.
Installation Fails When swagent is Busy
If swinstall or swremove commands run in parallel then installation fails.
Suggestion. You need to ensure that the swinstall and swremove commands are not used during the installation and uninstallation.
Unexpected External Error Occurs
A power failure or system failure might have occurred, or you might have entered CTRL/C to stop the installer process.
Suggestion. If the failure occurred during the installation or configuration process, you are probably left with a partial installation. Run the uninstall program. If the uninstall program fails, follow the instructions under Uninstallation Fails, Leaving Behind Files.
Graphical Installer Seems Unresponsive
The installer sometimes creates an image on the screen before the image is ready for input. You cannot repeatedly click Next in the installation wizard without waiting.
Suggestion. The button that represents the default choice includes a blue rectangle. This rectangle sometimes appears after the button itself appears. Wait until you see the blue rectangle before clicking a button.
Silent Installation Fails: “State File is Incompatible or Corrupted”
If you are using a state file that was created on the same platform on which you are using it, the problem might be due to an unknown file corruption error.
Suggestion. If you created the state file on the same platform on which you are running the silent installation, generate a new state file and reinstall.
Silent Installation Fails
If you edited the state file, you might have introduced errors. For example:, check the following:
Suggestion. Resolve the problem and regenerate the state file.
Terminal Echo Goes Off
When a user exits at password request timed out during Silent mode installation the Terminal Echo goes off.
Suggestion. You need to run the command stty echo to make echo on.
Man Pages Do Not Display
The most likely reason for man pages not displaying is that your MANPATH environment variable is not set correctly for the components you installed.
Suggestion. Update /etc/MANPATH to point to the new Man Page directory.
Uninstallation Problems
This section discusses causes and solutions to the following uninstallation problems:
You Cannot Find the Uninstall Program
The Sun Java Enterprise System installation program places the uninstall program on your system at the following location:
If the uninstall program is not at that location, one of the following might have occurred:
Suggestion. Manually clean up your system as described in Uninstallation Fails, Leaving Behind Files.
Uninstallation Fails, Leaving Behind Files
If manual cleanup is necessary because the uninstall program left behind files or processes, perform the following procedure to remove packages from your system.
To Manually Clean Up Packages
- Determine which packages you want to remove.
Compare the packages on your system with the Sun Java Enterprise System packages listed in Installable Packages. You can use the swlist command to determine which packages are installed.
- Stop all running processes for Sun Java Enterprise System components.
Brief instructions for stopping processes are contained in Starting and Stopping Components. The section on Component Troubleshooting Information provides some information on each component, with links to component documentation.
- Back up all custom configuration and user data if you plan to use in subsequent installations.
Chapter on Uninstallation Behavior for Sun Java Enterprise System Components in Sun Java Enterprise System Installation Guide (http://docs.sun.com/apps/doc/apps/docs/819-2328) provides some information on configuration and user data that should be backed up. For more information, refer to the component documentation for each component.
- Use the swremove command to remove Sun Java Enterprise System component packages.
- Remove any remaining component directories and their content that you do not plan to use in subsequent installations. If you do plan to use these directories later, move them elsewhere.
- Update the product registry file, which is located here:
/var/adm/sw/productregistry
The uninstall program uses this registry to determine which components are installed on a host. Both the installer and uninstall program update the product registry upon completion of an installation or uninstallation.
Note
If you manually remove packages rather than using the uninstall program, then you must edit the product registry so it correctly reflects the software installed on your system.
- Clean up the log files for your system, which are located here:
/var/opt/sun/install/logs
The log files might not correctly reflect the state of your system after you manually remove packages.
Product Registry is Corrupted
During uninstallation, the uninstall program uses the product registry file to determine what needs to be uninstalled:
- If the uninstall program fails, you might need to retry after you restore the product registry from your backup copy.
- If you manually remove packages, the product registry is not automatically updated. When you subsequently run the uninstall program, you might encounter problems because the product registry does not correctly reflect your system. In this case, you can try to reinstall and then run the uninstall program again.
Uninstaller Cannot Connect to Configuration Directory Server
When uninstalling either the Administration Server or Directory Server, the uninstall program attempts to connect to the Configuration Directory Server using the administrator user ID and password supplied earlier when running the uninstall program. If the uninstall program cannot connect to the Configuration Directory Server, or if the administrator user ID and password are not valid, the uninstall program indicates that it cannot proceed by displaying an error message.
Suggestion. Perform the procedure in this section to resolve the problem, then complete the uninstallation. You do not have to exit the Sun Java Enterprise System uninstall program to complete this procedure.
Note
The following procedure assumes you have configured a Directory Server instance at the following location:
/opt/sun/mps/serverroot/slapd-Dir_Svr_Instance_Name
If you specified a different location, modify the instructions in the procedure accordingly.
To Troubleshoot and Complete Administration Server or Directory Server Uninstallation
- Make sure the Directory Server instance hosting the configuration directory is running. For example, search for the slapd process as follows:
/usr/bin/ps -ef | grep slapd
- If the Configuration Directory Server is not running, do the following:
- When the Configuration Directory Server is running, verify that you have a valid administrator user ID and password and proceed with the uninstallation.
- If you do not have a valid administrator user ID and password, the uninstall program stops and displays the following error:
Could not connect to Configuration Directory Server with administrator identity and password supplied
To continue with the uninstallation, manually unconfigure the Directory Server and/or Administration Server:
- Stop the Directory Server instance that is hosting the configuration directory. For example, with root privileges do the following:
/opt/sun/mps/serverroot/slapd-Dir_Svr_Instance_Name
./stop-slapd
- Run the following unconfiguration programs for Administration Server and Directory Server respectively:
/opt/sun/sbin/mpsadmserver unconfigure
/opt/sun/sbin/directoryserver -u 5.2 unconfigure
During unconfiguration, a notice appears informing you that the Configuration Directory Server cannot be contacted.
- Click Continue to continue with unconfiguration.
- After running the unconfiguration programs, proceed with uninstallation.
- You will be prompted for the administrator user ID and password.
- Supply any arbitrary value. These values will be ignored during uninstallation.
- Continue with the uninstallation until it is complete.
Common Agent Container Problems
This section addresses problems that might arise in relation to the common agent container shared component:
Port Number Conflicts
The common agent container inside Sun Java Enterprise System occupies the following port numbers by default:
Compromised Security Around the Root Password
It might be necessary to regenerate security keys on a machine running Sun Java Enterprise System. For example, if there is a risk that a root password has been exposed or compromised, you should regenerate security keys. The keys used by the common agent container services are stored in the following locations:
Under normal operation, these keys can be left in their default configuration. If you need to regenerate the keys due to a possible key compromise, you can regenerate the security keys using the following procedure.
Error Notification About Lock File
When you issue a cacaoadm subcommand, it is possible that another user issued a command at exactly the same time. However, only one cacaoadm subcommand can be run at a time.
The following error message is generated:
If cacaoadm daemon is running, it is busy executing another command.
Otherwise remove lock file /var/opt/sun/cacao/run/lock.The first recommended action when you receive this notification message is to wait a few moments and retry.
If you receive the same notification message when you retry, then it is possible that a lock file has not been removed by the common agent container management daemon. This can happen in the case of a crash. The lock file prevents further cacaoadm subcommands from being run.
Remove the lock file from the location indicated in the error message.
Component Troubleshooting Information
This section provides various quick tips on components, with references to useful documentation.
The following additional information in this guide is useful for troubleshooting:
- Developing Your Installation Sequence in Sun Java Enterprise System Installation Guide (http://docs.sun.com/app/docs/doc/819-2328) contains information on component interdependencies.
- Refer to the sections Troubleshooting Installation Problems and Starting and Stopping Components for instructions.
Access Manager Troubleshooting Tools
Table 32 Access Manager Troubleshooting Tools
Topic
Details
Log Files
Location of AM debug logs
/var/opt/sun/identity/logs
/var/opt/sun/identity/debug
Configuration File
AMConfig.properties
/etc/opt/sun/identity/config
Debug Mode
Refer to the Sun Java System Access Manager Developer’s Guide (http://docs.sun.com/app/docs/doc/819-2139)
Administration Server Troubleshooting Tools
Table 33 Administration Server Troubleshooting Tools
Topic
Details
Log Files
Installation log directory:
/var/opt/sun/install/logs
Configuration log files:
Administration_Server_install.Atimestamp
Administration_Server_install.BtimestampFor more information on logging options, refer to the Sun Java System Administration Server Administration Guide (http://docs.sun.com/app/docs/doc/817-7612).
Troubleshooting
Refer to the Sun Java System Administration Server Administration Guide (http://docs.sun.com/app/docs/doc/817-7612).
Application Server Troubleshooting Tools
Table 34 Application Server Troubleshooting Tools
Topic
Details
Log Files
Log file directory:
/var/opt/sun/install/logs/
Application Server instance log directory (default location for the initially created instance):
/var/opt/sun/appserver/domains/domain1/logs
Message log file name:
Configuration Files
Configuration file directory: /var
Troubleshooting
Refer to the Sun Java System Application Server Enterprise Edition Troubleshooting Guide (http://docs.sun.com/app/docs/doc/819-2562).
Calendar Server Troubleshooting Tools
Table 35 Calendar Server Troubleshooting Tools
Topic
Details
Log Files
Administration Service (csadmind): admin.log
Distributed Database Service (csdwpd): dwp.log
HTTP Service (cshttpd): http.log
Notification Service (csnotifyd): notify.logDefault log directory: /var/opt/sun/calendar/logs
For more information, refer to Sun Java System Calendar Server Administration Guide (http://docs.sun.com/app/docs/doc/819-2433)
Configuration File
/opt/sun/calendar/config/ics.conf
Debug Mode
To use debug mode, a Calendar Server administrator sets the logfile.loglevel configuration parameter in the ics.conf file. For example:
logfile.loglevel = "debug"
For more information, refer to Sun Java System Calendar Server Administration Guide (http://docs.sun.com/app/docs/doc/819-2433).
Troubleshooting
Refer to Sun Java System Calendar Server Administration Guide (http://docs.sun.com/app/docs/doc/819-2433).
Communications Express Troubleshooting Tools
For information on troubleshooting Communications Express, refer to the Troubleshooting chapter in the Sun Java System Communications Express Administration Guide, http://docs.sun.com/doc/819-0115
Directory Proxy Server Troubleshooting Tools
Table 36 Directory Proxy Server Troubleshooting Tools
Topic
Details
Log Files
Default log file: <DPS Server root>/dps-hostname/logs/fwd.log
For more information, refer to the Sun Java System Directory Proxy Server Administration Guide (http://docs.sun.com/doc/817-7615).
Troubleshooting
Refer to the Sun Java System Directory Proxy Server Administration Guide (http://docs.sun.com/doc/817-7615).
Directory Server Troubleshooting Tools
Table 37 Directory Server Troubleshooting Tools
Topic
Details
Log Files
Installation log file:
/var/opt/sun/install/logs
Configuration log files:
For information on managing log files, refer to the Sun Java System Directory Server Administration Guide (http://docs.sun.com/doc/817-7613).
Troubleshooting
Refer to the Sun Java System Directory Server Administration Guide (http://docs.sun.com/doc/817-7613).
Instant Messaging Troubleshooting Tools
Table 38 Instant Messaging Troubleshooting Tools
Topic
Details
Log Files
Server log: xmppd.log
Agent calendar log: agent-calendar.log
WatchDog log: iim_wd.log
Multiplexor log: mux.log
Default log directory: /var/opt/sun/im/log
For more information, refer to Sun Java System Instant messaging Server Administration Guide (http://docs.sun.com/app/docs/doc/819-0430).
Configuration File
/opt/sun/im/config/iim.conf
Debug Mode
To use debug mode, a Instant Messaging Server administrator sets the iim.log.iim_server.severity configuration parameter in the iim.conf file. For example:
For more information, refer to Sun Java System Instant Messaging Server Administration Guide (http://docs.sun.com/doc/ <doc no:>).
Troubleshooting
Refer to Sun Java System Instant Messaging Server Administration Guide (http://docs.sun.com/app/docs/doc/819-0430)
Helpful Documentation
Refer client online help and the Sun Java System Instant Messaging Administration Guide (http://docs.sun.com/doc/819-0430).
Message Queue Troubleshooting Tools
Table 39 Message Queue Troubleshooting Tools
Topic
Details
Log Files
Installation Log file:
/var/opt/sun/mq/instances/<instance name>/log
Refer to the Sun Java System Message Queue Administration Guide (http://docs.sun.com/app/docs/doc/819-2571).
Troubleshooting
For performance problems, refer to Analyzing and Tuning a Message Service chapter in the Sun Java System Message Queue Administration Guide (http://docs.sun.com/app/docs/doc/819-2571).
Message Queue troubleshooting is discussed in the Troubleshooting Problems chapter of the Sun Java System Message Queue Administration Guide and the MQ Forum, at: (http://docs.sun.com/app/docs/doc/819-2571).
Additional articles are available in Knowledge Base, at http://developers.sun.com/prodtech/msgqueue/reference/techart/index.html
Messaging Server Troubleshooting Tools
Table 40 Messaging Server Troubleshooting Tools
Topic
Details
Executable Location
/opt/sun/messaging/sbin
Log Files
/opt/sun/messaging/log
Troubleshooting
Refer to the Sun Java System Messaging Server Administration Guide (http://docs.sun.com/app/docs/doc/819-2661).
Portal Server Troubleshooting Tools
Table 41 Portal Server Troubleshooting Tools
Topic
Details
Log Files and Debug Files
Portal Server uses the same log files and debug files as Access Manager. Their directories are as follows:
Log file: /var/opt/sun/identity/logs
Debug file: /var/opt/sun/identity/debug
For information on managing Portal Server log files and debug files, refer to the Sun Java System Portal Server Administration Guide, (http://docs.sun.com/app/docs/doc/819-4154).
For Portal Server Desktop, the debug files are:
/var/opt/sun/identity/debug/desktop/debug
/var/opt/sun/identity/debug/desktop.dpadmin.debug
For information on managing these files, refer to the Sun Java System Portal Server Administration Guide, (http://docs.sun.com/app/docs/doc/819-4154).
The dpadmin, par, rdmgr, and sendrdm Portal Server command line utilities have options to generate debugging messages. Options are described in the Portal Server Administrator’s Guide.
Portal Server Secure Remote Access Troubleshooting Tools
Table 42 Portal Server Secure Remote Access Troubleshooting Tools
Topic
Details
Debug Logs
Portal gateway debug logs are located in this directory:
/var/opt/sun/identity/debug/desktop/debug
Web Server Troubleshooting Tools
Table 43 Web Server Troubleshooting Tools
Topic
Details
Log Files
There are two types of Web Server log files: the errors log file and the access log file, both located in the directory /opt/sun/webserver/https-instance_name/logs.
The errors log file lists all the errors the server has encountered. The access log records information about requests to the server and the responses from the server. For more information, refer to the Sun One Web Server 6.1 Administrator’s Guide (http://docs.sun.com/app/docs/doc/819-0130).
Troubleshooting
Refer to the Sun One Web Server 6.1 Installation and Migration Guide (http://docs.sun.com/app/docs/doc/819-0131).
Configuration File Directory
/opt/sun/webserver/https-instance-name/config
Debug Mode
The following options are available:
Log output might be used for diagnostics and debugging. You can set the value of the loglevel attribute of the LOG element in the /server_root/https-instance_name/config/server.xml file to the following values: info, fine, finer or finest. These values indicate the verbosity of debug messages, with finest giving maximum verbosity. For more information about the LOG element, refer to the Sun ONE Web Server Administrator’s Configuration File Reference (http://docs.sun.com/doc/817-6248-10).
A debug flag might be enabled to start the server web container in debug mode ready for attachment with a Java Platform Debugger Architecture (JPDA debugger. To do this, set the value of the jvm.debug flag of the JAVA attribute in the /instance_root/https-server_name/config/server.xml file to true. For more information, refer to the Sun ONE Web Server Administrator’s Configuration File Reference (http://docs.sun.com/doc/817-6248-10).
The Sun Java System Studio 5, Standard Edition, plugin enables the debugging of web applications. For more information, refer to the Sun ONE Web Server Programmer's Guide to Web Applications (http://docs.sun.com/doc/817-6251-10).
Web Proxy Server Troubleshooting Tools
Table 44 Web Proxy Server Troubleshooting Tools
Topic
Details
Log Files
There are two types of Web Server log files: the errors log file and the access log file, both located in the directory /opt/sun/webproxyserver/https-instance_name/logs.
The errors log file lists all the errors the server has encountered. The access log records information about requests to the server and the responses from the server. For more information, refer to the Sun One Web Server 6.1 Administrator’s Guide (http://docs.sun.com/doc/817-6247-10).
Troubleshooting
Refer to the Sun One Web Server 6.1 Installation (http://docs.sun.com/doc/817-6245-10).
Configuration File Directory
/opt/sun/webserver/https-instance-name/config
Debug Mode
The following options are available:
Log output might be used for diagnostics and debugging. You can set the value of the loglevel attribute of the LOG element in the /server_root/https-instance_name/config/server.xml file to the following values: info, fine, finer or finest. These values indicate the verbosity of debug messages, with finest giving maximum verbosity. For more information about the LOG element, refer to the Sun ONE Web Proxy Server Administrator’s Configuration File Reference (http://docs.sun.com/app/docs/doc/819-3651).
A debug flag might be enabled to start the server web container in debug mode ready for attachment with a Java Platform Debugger Architecture (JPDA debugger. To do this, set the value of the jvm.debug flag of the JAVA attribute in the /instance_root/https-server_name/config/server.xml file to true. For more information, refer to the Sun ONE Web Proxy Server Administrator’s Configuration File Reference (http://docs.sun.com/app/docs/doc/819-3651).
The Sun Java System Studio 5, Standard Edition, plugin enables the debugging of web applications. For more information, refer to the Sun ONE Web Server Programmer's Guide to Web Applications (http://docs.sun.com/doc/817-6251-10).
Service Registry Troubleshooting Tools
Table 45 Service Registry Troubleshooting Tools
Topic
Details
Log Files
Log file directory:/var/opt/sun/install/logs/
Service Registry instance log directory: /var/opt/sun/SUNWsoar/domains/registry/logs
Message log file name: server.log, for each server instance
Configuration File Directory
Configuration file directory: /var
Troubleshooting
Refer to the Sun Java System Service Registry 3 2005Q Administration Guide (http://docs.sun.com/app/docs/doc/819-2684).
Known Issues and LimitationsThis section describes the known issues and limitations of Sun Java Enterprise System 6 for HP-UX. For a list of the known issues and limitations in this component, refer to the following Release Notes:
Known problems that are associated with the Sun Java Enterprise System components are documented in the respective component release notes on HP-UX. Refer to Bugs Fixed in This Release.
The following topics are the known issues:
Installation
Miscellaneous Installation Issues
In CLI Mode, the Installer does not let you install Portal Server Gateway Alone (6279513)
A key issue is that the installer does not allow you to perform a deployment in the CLI mode because the installer does not allow you to select only the Gateway sub-components.
Solution Use the installer in the GUI mode.
Java ES 2005Q4 Installer needs a mechanism to query if a product license is of type evaluation (6265136)
The installer should check if shared components is an evaluation component and replace it if in fact it is an evaluation component.
Solution Ensure that the workstation does not have an evaluation component installed before beginning an installation.
Problem with IP Address validation for Netlet Proxy (6317592)
In the Netlet proxy panel, the installer does not accept the valid IP address and asks to enter the valid IP address. This problem also occurs in the GUI mode.
Solution Ensure that the /etc/hosts file contains the correct information.
The JES4 installation on HP-UX platform takes a more time when installed under the following scenarios as compared with Solaris, Linux and Windows platforms: (6291473)
- Directory Server, Administration Server and all language packs with Configure Now option
- Directory Server, Web Server, Access Manager, Portal Server and all language packs with Configure Later option
- Directory Server, Application Server, Access Manager, Portal Server and all language packs with Configure Now option
Solution: Install the product components only with the required languages on the system.
When JES installer CD/DVD is mounted directory and file names appear in Upper case letters with semicolon in file names.
Solution: - This problem is know as rock ridge problem, if mount command is not supporting rock ridge options like cdcase and rr then file names appear in upper case letters. The following patches needs to be installed to support rock ridge options with mount command:
JES INSTALLER shows Apache webserver in AS Load balancing plugin panel (6367708)
Solution Sun Java System does not support Third party web containers on HPUX, select Sun Java System Webserver for configuring loadbalancer plugin. The consequences of selecting Apache webserver is unknown.
Delegated Administration configurator asks for Web Server information while Access Server is the web container (6270890)
The Delegated Administration server is deployed to the same web container as Access Manager.
Solution The dependency of Delegated Administrator on Access Manager can be temporarily achieved by manually selecting Access Manager while installing Delegated Administrator.
Multiple versions of comm_dsetup.pl exist (6226161)
Solution Only use the version of comm_dssetup.pl found in /opt/sun/comms/dssetup/sbin. Ignore all other versions.
Cannot deploy Portal Server using SSL encryption if Access Manager is using SSL (6211026)
Solution Install portal server using the “Configure Later” option Hack the dpadmin and pdeploy scripts in /opt/sun/portal_svr and add the option to the java command lines: -D”java.protocol.handler.pkgs=com.iplanet.services.comm”
Edit the /etc/opt/sun/identitiy/config/AMConfig.properties and change the certdb settings to:
com.iplanet.am.admin.cli.certdb.dir=/opt/sun/webserver/alias
com.iplanet.am.admin.cli.certdb.prefix=https-<HOSTNAME><DOMAINNAME><HOSTNAME>
com.iplanet.am.admin.cli.certdb.passfile=/opt/sun/webserver/alias/.wtpass
(based on what the web server is using).
Create the file /opt/sun/webserver/alias/.wtpass containing (only) the password for the certdb. Note that this is a different format to the password.conf file that the web server itself uses:
cd /opt/sun/Portal_svr/lib;
JAVA_HOME=/usr/jdk/entsys-j2se ./psconfig
The uninstaller does not validate passwords for Portal Server uninstallation(6263414)
Proper validation is required before beginning the Portal Server uninstallation process can begin.
Solution In order to complete the uninstallation process, enter any value in the Portal Uninstall screen.
Installation log messages are not always valid (no specific ID)
Please note that log messages are not always valid. For example, the “no software was installed” message appears even if some (but not all) component products are installed after an error of some sort.
Mentions of “Sun ONE” in data services should be “Sun Java System” (no specific ID)
All occurrences of Sun ONE in the names and descriptions of the data services for Java ES applications should read “Sun Java System”. For example, “Sun Cluster data service for Sun ONE Application Server” should read “...for Sun Java System Application Server”.
Auto-selection of components in component selection page confusing (4957873)
When a component product is selected, the installer automatically selects to install any dependent component products. The component product selection page does not indicate that the dependencies have been selected along with the original component product.
Solution None.
Selected component notation inconsistent from page to page (5033467)
The “**” to indicate a disabled selection is not implemented globally.
Solution None.
Access Manager Installation
Amconsole home page is not coming up in multinode installations (6291099)
In multinode installations you may find that the Amconsole home page fails to appear. Refer to the solution listed below:
- Login to the realm console of the first instance (for example: <first-node-protocol>://<first-node-fqdn>:<first-node-port>/amserver)
- Click on the link corresponding to the default realm.
- In the text field for “Realm/DNS Aliases”, enter “<node2–fqdn>” and click Add.
- Click Save.
- Click on the “Realms” link in the bread crumb above the tabs.
- Click on the “Configuration” tab.
- Click on the “System Properties” tab
- Click on the “Platform” service tab.
- Under “Instance Name”, click the “New...” button.
- In the “Server” field, enter “<node2–protocol://<node2–fqdn>:<node2–port>”.
- In the “Instance Name” field, enter an unused number (for example, the number
- Click “OK”.
- Click “Save”.
Access Manager SDK configuration causes web server startup failure errors (6293225)
The problem of web server startup failures can be attributed to the Access Manager’s SDK configuration. In the current scenario, the AMConfig.properties file contains the wrong information and causes a series a web server startup failures. The following variables do not have the correct information:
Solution On your node B, where Access Manager SDK is installed with Web Server, modify the <Web_Server_Instance_dir>/config/server.xml file and add the required Access Manager JAR files to the classpath.
Console-only install configuration fails (5047119)
The installer does not configure the web container for a console-only installation on a local server.
Solution Perform a console only installation in two separate installation sessions:
- In the first installation session, perform a “Configure Now” install of the web container (Application Server or Web Server).
- In the second installation session, perform a “Configure Later” install of Access Manager Administration Console.
- After the second session is finished, change to the Access Manager utilities directory. For example, on Solaris systems:
# cd AccessManager-base/SUNWam/bin/
where AccessManager-base is the Access Manager base installation directory.
- Copy the amsamplesilent file and specify a new file name.
- Edit the copy of the amsamplesilent file to specific the configuration information, including DEPLOY_LEVEL (2 for console only) CONSOLE_HOST, CONSOLE_PORT, and SERVER_PORT variables.
- Run the amconfig script with the edited amsamplesilent file.
# ./amconfig -s copy-of-amsamplesilent
where copy-of-amsamplesilent is the name of the copy of the amsamplesilent file. For more information about the amsamplesilent file and amconfig script, see the Access Manager 2005Q4 Administration Guide.
Single Quote Not Allowed in Passwords and Root Suffix (no issue ID)
In passwords (such as for amadmin) and the Directory Server root suffix, Access Manager does not support a single quote (\q). The back-slash (\\), however, is supported.
Installer doesn’t add platform entry for existing directory install (6202902)
The Java ES Installer does not add a platform entry for an existing directory server installation (DIRECTORY_MODE=2).
Solution Edit the platform service Server List attribute to add the second instance. For example. if the first instance is host1.example.com, it will have an entry such as http://host1.example.com:port|01. If the second instance is on host2 and uses the same Directory Server as host1, use the Access Manager administrator console to add an entry such as http://host2.example.com:port|02
Installing Access Manager on an existing DIT requires rebuilding Directory Server indexes (6268096)
To improve the search performance, Directory Server has several new indexes. Therefore, after you install Access Manager with an existing directory information tree (DIT), rebuild the Directory Server indexes by running the db2index.pl script. For example: #./db2index.pl -D "cn=Directory Manager" -w password -n userRoot
The db2index.pl script is available in the DS-install-directory/slapd-hostname/ directory.
Access Manager registered portal services are not added to user when created through the Access Manager SDK (6280171)
Solution For every user created through the use of the commadmin command line interface, you will need to register all of the missing services with the Access Manager admin console.
Big regression in using the Access Manager amadmin CLI (6267167)
When using the amadmin command line interface, you need to provide the full dn of an amAdmin user. An example is shown below:
amadmin -u uid=amadmin,ou=people,o=isp -w
Sub-org creation not possible from one Identity Server by using Identity Server amadmin CLI (5001850)
Solution In both Directory Server, make sure to have inside cn=config, cn=ldbm database,cn=plugins, cn=config, nsslapd-lookthroughlimit set to -1.
Console-only install configuration fails (5047119)
The installer does not configure the web container for a console-only installation on a local server.
- In the first installation session, perform a “Configure Now” install of the webcontainer (Application Server or Web Server).
- In the second installation session, perform a “Configure Later” install of Access Manager Administration Console.
- After the second session is finished, change to the Access Manager utilities directory. For example, on Solaris systems:
# cd Access Manager-base/identity/bin
where AccessManager-base is the Access Manager base installation directory.
- Copy the amsamplesilent file and specify a new file name.
- Edit the copy of the amsamplesilent file to specific the configuration information, including DEPLOY_LEVEL (2 for console only) CONSOLE_HOST, CONSOLE_PORT, and SERVER_PORT variables.
- Run the amconfig script with the edited amsamplesilent file. For example:
# ./amconfig -s copy-of-amsamplesilent
where copy-of-amsamplesilent is the name of the copy of the amsamplesilent file.
For more information about the amsamplesilent file and amconfig script, see the Access Manager 2005Q4 Administration Guide
Installing Access Manager 2005Q1 With SSL Enabled Directory Server (no Issue ID)
If Directory Server is already installed and has SSL enabled, the installation of Access Manager 2005Q1 will fail. To install Access Manager 2005Q1, first disable SSL for Directory Server. After the Access Manager installation is finished, then re-enable SSL for Directory Server.
Administration Server Installation
Administration Server patch fails to apply when server is stopped (6273652)
When stopping the Administration Server and using patchadd to apply a patch the process fails.
Solution You must start the Administration Server before applying the patch.
Cannot install Directory Server and Administration Server in separate sessions (5096114)
If you install Directory Server in one session and then try to install Administration Server in a second session, the box for Administration Server is already checked even though it is not installed and configured. You therefore cannot install and configure Administration Server.
Solution Install Directory Server and Administration Server in the same session. Or, refer to the Directory Server Administration documentation to learn how to manually configure Administration Server.
Deployment on Administration Server 8.1 with non-default URIs is inaccessible (6308426)
If you install Access Manager 7.0 on Application Server 8.1 and choose non-default URIs for Access Manager (for example, idserver instead of amconsole and idconsole instead of amconsole). Specifically, in the amas81configfile, the configureServerPolicy() does not account for the use case in which Access Manager is being configured with default URIs. Instead it assumes that the Access Manager war files will be deployed with the default URIs and grant permissions to amserver.war, amconsole.war, and ampassword.war.
Solution Perform the following procedure:
"file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/amserver/-" { permission java.net.SocketPermission "*", "connect,accept,resolve"; permission java.util.PropertyPermission "*", "read, write"; }; grant codeBase "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/amconsole/-" { permission java.net.SocketPermission "*", "connect,accept,resolve"; permission java.util.PropertyPermission "*", "read, write"; }; grant codeBase "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/ampassword/-" { permission java.net.SocketPermission "*", "connect,accept,resolve"; permission java.util.PropertyPermission "*", "read, write"; };
Application Server Installation
If a port which is already in use is chosen installation fails (4922417)
Solution None.
Installer does not recognize host name user enters in configuration page (4931514)
The installer prompts you for the “server name” for the Application Server. However, the installer uses the actual host name of the machine regardless of what you input in the text field.
Solution If the server name is different from the server’s host name, become superuser and type the following in the domain directory of interest (the “server root” directory):
# find . -type f -exec grep -l $HOSTNAME {} \\ ;
Then, change the file contents appropriately.
Java ES 2005Q4 Promoted build 08 shows incorrect Application Server Name (6297837)
Sun Java™ System Application Server Enterprise Edition 8.1 2005Q2 Update 2 is the correct notation. The notation Sun Java™System Application Server Enterprise Edition 8.1 2005Q4 was in error.
Directory Server Installation
Slow DPS response causing exceptions in web server and system instability
When too many connections are established to the DPS server from a remote node, the
DPS response is slow and exceptions are thrown.
Solution None
Directory Server configuration output splits the progress bar on silent mode (4928102)
When components are configured the corresponding output is sent to the installer’sstdout instead of the log. This action places the CLI progress bar on multiple lines in the installer output.
Solution None
Incorrect Version of Directory Server is displayed after upgrade from Directory Server 5 2005Q1 to Directory Server 2005Q4 (269446)
Solution You can ignore the version displayed in the console. Type the following in order to get the proper version information.
$SERVERROOT/bin/slapd/server/ns-slapd —v
Directory Server instance were not created because of /etc/ds and /etc/mps (5094994)
Remove the remaining link /etc/ds/v5.2/shared/config/certmap.conf before re-configuring servers.
Cannot configure Directory Server if you reinstall after uninstalling (6223527)
You cannot configure Directory Server if you are reinstalling after having uninstalled. During the uninstall, /var/opt/sun is not removed. As a result, the Directory slapd is not found and there are errors logged when you try to start Directory Server.
Solution After uninstalling Directory Server, remove /var/opt/sun before you reinstall.
Cannot install Directory Server and Administration Server in separate sessions (5096114)
If you install Directory Server in one session and then try to install Administration Server in a second session, the box for Administration Server is already checked even though it is not installed and configured. You therefore cannot install and configure Administration Server.
Solution Install Directory Server and Administration Server in the same session. Or, refer to the Directory Server Administration documentation to learn how to manually configure Administration Server.install.
Message Queue Installation
If Message Queue is installed with Java ES installer you must use uninstaller to uninstall (no issue ID)
If you remove the depot packages directly, the next time the installer is run, it may see Message Queue as still being installed and not behave correctly.
Solution If you have already removed the Message Queue packages manually, you must uninstall Message Queue using the uninstaller. Run the uninstaller and select Message Queue components for removal.
Portal Server Installation
Unable to stop Gateway in two host scenario (6283068)
Solution To start the gateway type ./gateway start -n default. In order to stop the gateway type /gateway stop -n default.
Portal Server Gateway login after Porter Server restart (6191449)
Solution Each time the Portal Server, Administration Server or Web Server is restarted, the gateway must also be restarted.
Login page is not downloaded through proxylet (6216514)
When the proxylet is enabled, SRA still uses the rewriter technology to fetch the login pages and a part of the desktop page before the proxylet starts.
Solution None
Exception thrown after reloading Portal Desktop (218871)
Launching the instant messaging link and refreshing the portal desktop causes the “ERROR: content is not available” to appear. Also, an exception is thrown in this file:
/var/opt/sun/identity/debug.
Solution Edit the domain.xml file (located in /var/opt/sun/appserver/domain1/config and perform the following
Modify the java configuration classpath-prefix with /opt/sun/share/lib/jaxen-core.jar
Type stop-domain domain1
Type asadmin start-domain
Enter your user name and password.
Netlet crashes after making connection (approximately 10 to 15 seconds) with remote server (6186633)
This problem occurs if you are using applications such as Citrix Metaframe, PC Anywhere, Remotely Anywhere, Tarentella and similar applications.
Solution None
Informative and useless page provided to the user when logging into Portal Server (6267783)
When you log into Portal Server, you are presented with an informative page that
states you have been authenticated, but you cannot exit this page.
Solution Use the administration console and click on the Identity Management tab, select Services view and change the value of “Default Success Login URL” with your portal URL (for example, http://<fqdn>:<port>/portal).
Installation and uninstallation of Portal Server appears to hang (5106639)
During installation and uninstallation of Portal Server, the installer and uninstaller appear to hang. The delay can be up to 30 minutes before installation/uninstallation finishes successfully
Gateway redirection not happening in any multi-session installation (4971011)
Regardless of the installation mode, gateway redirection does not occur during a multi-session installation.
Solution
To enable gateway redirection
- Launch a Portal Server browser and access the amconsole.
- Under “Service Configuration” tab, select “gateway”.
- In the lower right corner of the window, click “default” and “security” tab as well.
- Then, add a URL like “http://IS_HOST:PORT/amserver/UI/Login” into “Non-authenticated URLs:” field.
An example URL is http://boa.prc.sun.com:80/amserver/UI/Login.
- Finally, restart the Portal gateway by doing the following as superuser:
# /sbin/init.d/gateway -n default start debug
Web Server Installation
Web Server installation fails if install directory is populated with files from a previously installed version (no issue ID)
Solution Back-up all your configuration files. Then, remove the install directory before installing Web Server using the Java Enterprise System installer.
Localization Issues
Custom Configuration installer screen sometimes displays with crippled text layout (#6210498)
Solution Resize the window. Then, click Back and Next. The window will display correctly.
Single Quote Not Allowed in Passwords and Root Suffix (no issue ID)
In passwords (such as for amadmin) and the Directory Server root suffix, Access Manager does not support a single quote (\q). The back-slash (\\), however, is supported.
Installation of Access Manager fails if Directory Server 5.1 sp2 implements the Reset Password (4992507)
When you run the Java Enterprise System installer, the installation of Access Manager 2005Q1 fails if Directory Server 5.1 SP2 is configured to require users to change their passwords the first time they log in.
Solution Set the Directory Server password reset policy to “off”.
Uninstallation
During uninstallation, the Application Server directory is not removed (6229908).
The Application Server directory is not automatically removed when uninstalling all components of Sun Java Enterprise System.
Solution
Manually remove the Application Server directory after uninstallation, provided there is no node agent or instance-related data in this directory.
Redistributable FilesSun Sun Java Enterprise System 2005Q4 does not contain any files which you can redistribute.
How to Report Problems and Provide FeedbackIf you experience problems with Sun Java Enterprise System, contact Sun customer support using one of the following mechanisms:
- Sun Software Support services online at
http://www.sun.com/service/sunone/softwareTo assist you in resolving problems, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the guide or at the top of the document.
Additional Sun ResourcesUseful Sun information can be found at the following Internet locations:
- Sun Documentation
http://docs.sun.com/prod/java.sys- Sun Professional Services
http://www.sun.com/service/sunps/sunone- Sun Software Products and Service
http://www.sun.com/software- Sun Software Support Services
http://www.sun.com/service/sunone/software- Sun Support and Knowledge Base
http://www.sun.com/service/support/software- Sun Support and Training Services
http://training.sun.com- Sun Consulting and Professional Services
http://www.sun.com/service/sunps/sunone- Sun Developer Information
http://developers.sun.com- Sun Developer Support Services
http://www.sun.com/developers/support- Sun Software Training
http://www.sun.com/software/training- Sun Software Data Sheets
http://wwws.sun.com/software
Copyright � 2006 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright � 2006 Sun Microsystems, Inc. Tous droits r�serv�s.
Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plusieurs des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou des brevets suppl�mentaires ou des applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propri�t� de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.
Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.