This chapter contains instructions for completing initial configuration of the product components after installation. If a product component is not listed in this chapter, postinstallation configuration is not required for that component. However, that component might still require postinstallation tasks relating to monitoring or Sun Cluster data service.
This chapter contains the following sections:
When the installer finishes installation, most product components require additional configuration before the Communications Suite environment is operational. The extent of this work depends on the configuration type you selected (Configure Now or Configure Later), and whether or not your product components will be configured for monitoring or Sun Cluster.
If you selected the Configure Later type during installation, the installer placed the product component package files in their respective directories. No parameter setting was done, and most product components are not operational because runtime services are not available. A number of product components include configuration tools for completing a Configure Later installation. When running the configuration tools, you can make any additional changes by following the instructions located in this guide, and in the product documentation for each product component.
Before acting on the information in this chapter, you should have installed the Communications Suite components. You can examine the product registry Solaris OS pkginfo command or the Linux rpm command to verify that the component packages have been installed. A list of packages associated with the components is contained in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX.
A summary report containing the configuration values that were set during installation is available here:
Solaris OS: /var/sadm/install/logs
Linux: /var/opt/sun/install/logs
After completing installation, look through the procedures included in this chapter for the product components you installed. If you determine that no additional configuration is required for your product components, you can start your product components by following the instructions in Chapter 7, Verifying Installed Product Components.
The default installation locations of Communications Suite product components might be different on the various platforms. Due to this, the procedures in this chapter use variables to represent these locations. For example, ApplicationServer-base represents the directory where Application Server is installed, regardless of platform.
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 Communications Suite 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 not present, add this location to your MANPATH environment variable.
The following table indicates the default locations for the man pages of the Communications Suite components. If a component is not listed, the component does not have man pages.
Table 6–1 Man Pages Default Locations
Component |
Location of Man Pages |
---|---|
Solaris OS: /opt/SUNWappserver/share/man Linux: /opt/sun/appserver/share/man |
|
Sun Cluster on Solaris OS: /opt/SUNWcacao/man Linux: /opt/sun/man |
|
Solaris OS: /usr/cluster/man/ |
The following example procedure shows how to ensure that the Application Server man pages are available using the C shell.
Check your MANPATH environment variable to see if the correct path is already there.
env | grep MANPATH
If the correct path is not there, add the location of your Communications Suite component man pages to your MANPATH environment variable.
On Solaris OS, the following example command sets your MANPATH environment variable for the session:
setenv MANPATH {$MANPATH}:/usr/dt/man:/usr/man:/opt/SUNWappserver/share/man |
To configure this environment variable to apply each time you log in, add the setenv command contents to your .login or .cshrc file.
On Linux, update the /etc/man.config file with the required MANPATH. For example, add this line to the /etc/man.config file:
MANPATH /opt/sun/man |
The new man pages will be fully accessible, regardless of path.
For Linux, if users have MANPATH settings in their own shells, the procedure for Solaris OS should be used. This allows their personal settings to override the /etc/man.config file.
Verify that the man pages are accessible.
For example, the following command should display the asadmin man page for Application Server:
man asadmin |
If the product components you have installed will use the Java ES Monitoring Console, you must configure each component to use the monitoring framework. For instructions on installing the Monitoring Console see the Sun Java Enterprise System 5 Installation Guide for UNIX. For configuration instructions, refer to Chapter 2, Enabling and Configuring the Monitoring Framework, in Sun Java Enterprise System 5 Monitoring Guide.
Sun Cluster software provides a high availability platform for managing applications such as databases, application servers and web servers. Before you install or configure Sun Cluster software, ensure that the combination of hardware and software that you choose for your cluster is currently a supported Sun Cluster configuration.
Sun Cluster software can be used to manage the following Communications Suite product components:
Application Server
Application Server EE (HADB)
Calendar Server
Directory Server
Instant Messaging
Messaging Server
Message Queue (requires no additional configuration)
Web Server
If the product components you installed will be included in a Sun Cluster environment, you must first configure the Sun Cluster framework before configuring the product components, then configure the Communications Suite product components you have selected. Finally, depending on the product components installed, you might need to configure Sun Cluster data services.
The installer performs a simple pkgadd installation of the core Sun Cluster packages and sets up the /usr/cluster/bin directory. No configuration is done during installation, so your first postinstallation task is to configure the cluster framework as described in the Sun Cluster Software Installation Guide for Solaris OS.
During this phase, the scinstall utility verifies the Sun Cluster packages. If packages are missing, an error message is displayed. If this happens, you must verify that the correct Sun Cluster packages were installed. Refer to Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX.
After you have installed and configured the Sun Cluster framework and the other Communications Suite components, you are ready to configure the Sun Cluster data services using the Sun Cluster agents software.
To configure Sun Cluster data services, you must have chosen the associated Sun Cluster agents during installation. To see an example Sun Cluster installation sequence, refer to Sun Cluster Software Example.
For guidelines on configuring the Sun Cluster data services, refer to Sun Cluster Data Services Configuration.
Whenever you use the installer to configure Access Manager on Web Server, you will need to perform the following steps:
Start the Web Server administration instance.
Start the Web Server instance.
Select the Web Server instance on which Access Manager was installed.
Click Manage.
For all Access Manager installations, the web container needs to be restarted. If a full installation is being performed on Web Server or Application Server, the installer will stop the web container instance so only the instance needed to be started. For instructions on restarting Access Manager, see Starting and Stopping Access Manager.
Access Manager configuration is described in the following sections:
Configuring Access Manager After a Configure Now Installation
Configuring Access Manager After a Configure Later Installation
Although you can start Access Manager and log into the Access Manager console immediately after running the 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 Directory Server instance that is already provisioned with user data.
The next sections explain what to do in the following cases:
Refer to Sun Java System Access Manager 7.1 Postinstallation Guide for a description of the final configuration steps.
When Directory Server is not yet provisioned with user data, perform the steps in the following sections:
Before performing the tasks in this section, Directory Server must be configured and running. To verify that Directory Server, is running, refer to Starting and Stopping Directory Server.
When the Directory Server 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. If the Referential Integrity Plug-in is not already enabled, perform the following procedure.
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.
Directory Server indexes improve the performance of searches of Directory Server data. The following table lists the recommended attributes that you should consider indexing for Access Manager (if they are not already indexed).
Table 6–2 Suggested Access Manager Indexes for Directory Server
Attribute |
Index Type |
nsroledn |
Equality, Presence, and Substring |
memberof |
Equality and Presence |
iplanet-am-static-group-dn |
Equality |
iplanet-am-modifiable-by |
Equality |
iplanet-am-user-federation-info-key |
Equality |
sunxmlkeyvalue |
Equality and Substring |
o |
Equality |
ou |
Equality, Presence, and Substring |
sunPreferredDomain |
Equality, Presence, and Substring |
associatedDomain |
Equality, Presence, and Substring |
sunOrganizationAlias |
Equality, Presence, and Substring |
Add indexes using either the Directory Server Console or the ldapmodify command-line utility. Use ldapmodify to load the Access Manager index.ldif file, which is available in the following directory:
Solaris OS: /etc/opt/SUNWam/config/ldif
Linux: /etc/opt/sun/identity/config/ldif
For more information about both the Console and ldapmodify, see Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.
After a Configure Later installation, the packages are installed and you are ready to configure Access Manager using the Access Manager configuration script, AccessManager-base/bin/amconfig. Instructions for using this program are contained in the Sun Java System Access Manager 7.1 Postinstallation Guide.
For instructions on configuring Access Manager for a third-party web container on Solaris OS (BEA WebLogic or IBM WebSphere Application Server), refer to Sun Java System Access Manager 7.1 Postinstallation Guide.
For all Access Manager installations, the web container needs to be restarted. If a full installation is being performed on Web Server or Application Server, the installer will stop the web container instance so it need only be started. For instructions on restarting Access Manager, see Starting and Stopping Access Manager.
After a Configure Now installation, Application Server requires no postinstallation configuration.
To configure Application Server for load balancing, refer to the “Configuring Web Servers for HTTP Load Balancing” section in the Chapter 5, Configuring HTTP Load Balancing, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.
If needed, configure Application Server for use with the Sun Cluster software. Refer to Sun Cluster Postinstallation Configuration.
Locate the accessory CD for Application Server.
Accessory contents can also be downloaded from the Sun Download Center at http://www.sun.com/download/index.jsp.
Refer to the README file in the Addon folder on the CD and follow the procedures detailed there.
Modify the ApplicationServer-base/samples/common.properties file.
Modify the following properties in the common.properties file. If you do not know some paths, you can copy them from the ApplicationServer-base /config/asenv.conf file.
Solaris Properties |
---|
com.sun.aas.derbyRoot=/opt/SUNWappserver/appserver/derby |
com.sun.aas.webServicesLib=/opt/SUNWappserver/appserver/lib |
com.sun.aas.imqHome=/var/opt/SUNWappserver/domains/domain1/imq |
com.sun.aas.imqBinDir=/usr/bin |
com.sun.aas.imqUserMgr=/usr/bin/imqusermgr |
com.sun.aas.imqLib=/usr/share/lib |
com.sun.aas.installRoot=/opt/SUNWappserver/appserver |
com.sun.aas.javaRoot=/usr/jdk/entsys5i-j2se |
com.sun.aas.domains.dir=/var/opt/SUNWappserver/domains |
#admin.password= The admin password will not be saved as default. User can enter it and save it manually. |
admin.host=jws-v210-4 |
appserver.instance=server |
appserver.instance.port=8080 |
admin.user=admin |
admin.port=4849 |
derby.port=9092 |
domain.name=domain1 |
server.cert.alias=s1as |
keystore=${com.sun.aas.domains.dir}/${domain.name}/config/keystore.jks |
keystore.password=changeit |
trustStore=${com.sun.aas.domains.dir}/${domain.name}/config/cacerts.jks |
Linux Properties |
---|
#admin.password= The admin password will not be saved as default. User can enter it and save it manually. |
server.cert.alias=s1as |
keystore=${com.sun.aas.domains.dir}/${domain.name}/config/keystore.jks |
domain.name=domain1 |
com.sun.aas.imqHome=/var/opt/sun/appserver/domains/domain1/imq |
com.sun.aas.imqUserMgr=/opt/sun/mq/bin/imqusermgr |
com.sun.aas.domains.dir=/var/opt/sun/appserver/domains |
admin.user=admin |
appserver.instance=server |
com.sun.aas.imqBinDir=/opt/sun/mq/bin |
trustStore=${cbom.sun.aas.domains.dir}/${domain.name}/config/cacerts.jks |
com.sun.aas.imqLib=/opt/sun/mq/share/lib |
keystore.password=changeit |
com.sun.aas.derbyRoot=/opt/sun/appserver/javadb |
admin.port=4849 |
derby.port=9092 |
com.sun.aas.webServicesLib=/opt/sun/appserver/lib |
admin.host=jws-linuxpc-2 |
com.sun.aas.javaRoot=/usr/jdk/entsys5i-j2se |
com.sun.aas.installRoot=/opt/sun/appserver |
appserver.instance.port=8080 |
If needed, configure Application Server for use with the Sun Cluster software.
Calendar Server cannot be configured by the installer (Configure Now). After a Configure Later installation, use the following procedure to configure Calendar Server.
Skip Step 1 if you have already run the Directory Preparation Tool on the same Directory Server during configuration of another communications product component.
Configure Directory Server for communications services (Calendar Server, Messaging Server and Delegated Administrator) by running the Directory Preparation Tool, comm_dssetup.pl.
Verify that Directory Server is running.
Refer to Starting and Stopping Directory Server.
On the host where Directory Server is installed, run the Directory Preparation Tool.
For example:
perl /opt/SUNWcomds/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 the Sun Java System Communications Services 6 2005Q4 Schema Migration Guide.
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 mycomputer 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 Delegated Administrator 6.4 Administration Guide.
This step only applies if your installation uses LDAP Schema 2, and if this step was not done during configuration of another communications product component.
Configure Calendar Server by running the Calendar Server configuration program as follows:
Solaris OS: CalendarServer-base /opt/SUNWics5/cal/sbin/csconfigurator.sh
Linux: /opt/sun/calendar/sbin/csconfigurator.sh
For more information on configuring Calendar Server, refer to the Sun Java System Calendar Server 6.3 Administration Guide.
If needed, configure Calendar Server for use with the Sun Cluster software.
Refer to Sun Cluster Data Services Configuration.
Communications Express cannot be configured during installation (Configure Now). After a Configure Later installation, the packages are installed and you are ready to configure Communications Express.
Skip Step 1 if you have already run the Directory Preparation Tool on the same Directory Server during configuration of another communications product component.
Configure Directory Server for communications services (Calendar Server, Messaging Server and Delegated Administrator) by running the Directory Preparation Tool (comm_dssetup.p1).
Follow instructions in Calendar Server Postinstallation Configuration.
Before proceeding to Step 2, ensure that the product components on which Communications Express is dependent are installed and running. For more information, see “Prerequisites for Configuring Communications Express” in the Sun Java System Communications Express 6.3 Administration Guide.
Configure Communications Express using the configuration program, CommunicationsExpress-base /sbin/config-uwc.
Instructions are in Chapter 2, Installing and Configuring Communications Express, in Sun Java System Communications Express 6.3 Administration Guide.
Compete the additional post configuration tasks needed for Communications Express.
After a Configure Now installation, no additional configuration is necessary. After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for HADB.
Postinstallation configuration instructions for HADB and additional information can be found in the Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.
If needed configure HADB for use with the Sun Cluster software. Refer to Sun Cluster Data Services Configuration.
Instant Messaging cannot be configured during installation (Configure Now). After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Instant Messaging.
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 7.2 Administration Guide.
Instructions for using the Instant Messaging configure utility, InstantMessaging-base/configure, are contained in Chapter 1, Configuring Instant Messaging After Installation in the Sun Java System Instant Messaging 7.2 Administration Guide.
If needed configure Instant Messaging for use with the Sun Cluster software. Refer to Sun Cluster Data Services Configuration.
After installation, Message Queue requires no additional configuration.
If this product component will be included in a Sun Cluster configuration, proceed to Sun Cluster Postinstallation Configuration.
A common optional task is to configure Message Queue for automatic startup. To do this, become superuser and edit the following properties in the imqbrokerd.conf configuration file located in /etc/imq on Solaris OS and in /etc/opt/sun/mq on Linux.
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 3 2005Q4 Administration Guide 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 3 2005Q4 Administration Guide. For example, you might want to change the default administration password.
Messaging Server cannot be configured during installation (Configure Now). After a Configure Later installation, the packages are installed and you are ready to configure Messaging Server using the following procedure.
Skip Step 1 if you have already run the Directory Preparation Tool on the same Directory Server during configuration of another communications product component.
Configure Directory Server for communications services (Calendar Server, Messaging Server and the Delegated Administrator) by running the Directory Preparation Tool, comm_dssetup.pl.
Use the instructions in Chapter 8, Directory Preparation Tool (comm_dssetup.pl).
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 mycomputer loghost
Configure Messaging Server by running the initial runtime configuration program for Messaging Server, MessagingServer-base /sbin/configure.
For information on configuring Messaging Server, refer to Creating the Initial Messaging Server Runtime Configuration in Sun Java System Messaging Server 6.3 Administration Guide.
Set the number of file descriptors to be used by Messaging Server:
ulimit -n 12851 |
Set ulimit to a value no less than 12851.
If you intend to use Delegated Administrator to provision users for Messaging Server, you must perform additional steps to configure it.
Instructions for configuring Delegated Administrator and provisioning users are contained in the Sun Java System Delegated Administrator 6.4 Administration Guide.
This step applies only if your installation uses LDAP Schema 2, and if this step was not done during configuration of another communications product component.
Configure for use with the Sun Cluster software, if applicable. Refer to Sun Cluster Data Services Configuration.
After a Configure Now installation, no additional configuration is needed. After a Configure Later installation, the packages are installed and you are ready to configure Web Proxy Server using the following procedure.
Create a properties file with your settings.
For example, the wps.properties file might contain the following:
WPS_JDK_HOME=/usr/jdk/entsys5i-j2se/jre WPS_SERVER_ROOT=/opt/SUNWproxy WPS_ADMIN_NAME=admin WPS_ADMIN_PWD=admin123 WPS_ADMIN_PORT=8889 WPS_START_ON_BOOT=N WPS_ADMIN_SERVER_USER=root WPS_SERVER_NAME=jws-v60x-4.red.iplanet.com WPS_SERVER_PORT=8081 WPS_SERVER_ID=proxy-server1 WPS_ADMIN_SERVER_ID=proxy-admserv WPS_SERVER_USER=root |
After you have created the file, run the following command:
WebProxyServer-base/bin/proxy/bin/configureServer -l logfile -f \ path /wps.properties |
After a Configure Now installation, no additional configuration is needed unless you are using Sun Cluster or a 64–bit configuration.
Sun Cluster. If this product component will be included in a Sun Cluster configuration, proceed to Sun Cluster Postinstallation Configuration and Sun Cluster Data Services Configuration.
64–Bit Support . If you are enabling 64–bit JVM support for Web Server, refer to 64-bit Support in Sun Java System Web Server 7.0 Installation and Migration Guide.
After a Configure Later installation, the packages are installed and you are ready to configure Web Server using the following procedure.
Create a runtime configuration for Web Server by running the Web Server configurator following instructions in the Configure Later Mode (Java ES Only) in Sun Java System Web Server 7.0 Installation and Migration Guide.
Verify the common server settings and update settings as needed.
Refer to the tables in Web Server Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX.
After the cluster has been established and the product components have been configured, you are ready to configure Sun Cluster data services for the various product components. The installed Sun Cluster agents are software programs that enable applications to take advantage of clusters. Agent software and additional configuration files comprise data services that enable you to run an application (such as Web Server or an Oracle database) on a cluster instead of on a single server. Combined with the Sun Cluster framework software and multihost disks, data services enable applications to become highly available and scalable.
Until you have fully configured the data services and all the supporting layers (volume manager, cluster file system, resource group information), Sun Cluster installation is not complete. More information on data services can be found in the Sun Cluster Overview for Solaris OS .
You can deploy Access Manager in a highly available web container. However, like any web application deployed in a web container, it is subject to failure. In this case, the web container will not fail over.
For Communications Suite product components, run the installer on each node installing the product components, then install the corresponding HA Sun JavaTM System subcomponent of the Sun Cluster Agents for Sun Java System product components. In the installer, select the Configure Later type. When specifying installation directories, use the location on the node's local file system for product component, and use locations on a cluster file system for the component Configuration and Product Location.
If your installation plan calls for high availability for non-Communications Suite products, first install and configure the non-Communications Suite product, then select the agent that supports that product in the installer. Install and configure the agent following the instructions in the appropriate Sun Cluster data service guide.
Solaris SPARC platform data services guides are available here: http://docs.sun.com/app/docs/coll/1124.4
Solaris x86 platform data services guides are available here: http://docs.sun.com/app/docs/coll/1125.4
The following table lists the agents that are provided for the Communications Suite product components in the Sun Cluster Agents product component. Links to the documentation needed for configuring these data services are provided.
Table 6–3 Sun ClusterAgents (Data Services)
Agent Name |
Special Instructions |
Platform |
---|---|---|
HA Sun Java System Application Server |
SPARC, x86 |
|
HA Sun Java System Application Server EE (HADB) |
Sun Cluster Data Service for Sun Java System Application Server EE (HADB) Guide for Solaris OS |
SPARC |
HA Sun Java System Calendar Server |
Use Chapter 6, Configuring Calendar Server 6.3 Software for High Availability (Failover Service), in Sun Java System Calendar Server 6.3 Administration Guide as a guide to installing and configuring for failover. |
SPARC |
HA Sun Java System Directory Server |
SPARC |
|
HA Instant Messaging |
Use the Sun Java System Instant Messaging 7.2 Administration Guide for instructions on installing and configuring for high availability. |
SPARC |
HA Sun Java System Message Queue |
Use Sun Cluster Data Service for Sun Java System Message Queue Guide for Solaris OS as a guide to installing and configuring for failover. |
SPARC, x86 |
HA Sun Java System Messaging Server |
Use Chapter 3, Configuring High Availability, in Sun Java System Messaging Server 6.3 Administration Guide as a guide to installing and configuring for failover |
SPARC |
HA/Scalable Sun Java System Web Server |
Use the Sun Cluster Data Service for Sun Java System Web Server Guide for Solaris OS as a guide to installing and configuring for failover or for scalability. |
SPARC, x86 |
HA Agfa IMPAX |
SPARC |
|
HA Apache Tomcat |
SPARC, x86 |
|
HA Apache |
SPARC |
|
HA Broadvision One-to-One Enterprise |
SPARC |
|
HA DHCP |
SPARC, x86 |
|
HA DNS |
SPARC, x86 |
|
HA MySQL |
SPARC, x86 |
|
HA NetBackup |
SPARC |
|
HA Sun N1 Service Provisioning |
SPARC |
|
HA NFS |
SPARC, x86 |
|
HA Oracle |
SPARC |
|
HA Oracle Application Server |
SPARC |
|
HA Oracle E-Business Suite |
SPARC |
|
HA Oracle Real Application Clusters |
SPARC |
|
HA Samba |
SPARC, x86 |
|
HA SAP |
SPARC |
|
HA SAP DB |
SPARC |
|
HA SAP liveCache |
SPARC |
|
HA Siebel |
SPARC |
|
HA Solaris Containers |
SPARC, x86 |
|
HA Sun N1 Grid Engine |
SPARC |
|
HA Sun N1 Service Provisioning |
SPARC |
|
HA SWIFT Alliance Gateway |
SPARC |
|
HA Sybase ASE |
SPARC |
|
HA WebLogic Server |
SPARC |
|
HA WebSphere MQ |
SPARC |
|
HA WebSphere MQ Integrator |
SPARC |
After you have finished the required post-installation configuration for your Communications Suite product components, some product components might require that you tune the Java Virtual Machine (JVM). The JVM consists of several entities, the most significant being the compiler, which turns Java byte code into machine instructions. In the version of the Java Developer's Kit (JDK) that is included with this Communications Suite release, there are several choices which can be made for the JVM. The best starting option is the –server option. (You can obtain the list of options by using the java –? command.) The –server option is a good tuning option for a JVM running in server mode.
For garbage collection, the default algorithm is a good place to start.
Another significant tuning option that might need to be configured is the Java heap memory. For example:
The following command sets the initial Java heap size: -Xmssize
The following command sets the maximum Java heap size: -Xmxsize
A good starting point for a heavily used system would be to set the maximum heap size to 1.2 GB.
You must be root to run the installer. Because of this, all files placed on the machine by the installer are owned by root. However, when performing configuration after installation, you can assign a non-root runtime user or group to some product components. For example, you might be deploying Access Manager in an instance of Application Server that is not owned by root. For purposes of installation or administration, there are many reasons to configure a product component with a non-root identifier. Generally, the non-root user must already exist on the system, but this can vary by product component.
The following table provide links to information on configuring the applicable product components with non-root identifiers.
Table 6–4 Configuring Non-root Identifiers for Product Components
Product Component |
Where to Find Instructions |
---|---|
Application Server |
Set up an entire administrative domain owned and operated by a non-root user. For instructions, refer to Sun Java System Application Server Enterprise Edition 8.2 Administration Guide. |
Calendar Server |
Use the Calendar Server configurator to configure for non-root. For instructions, refer to the Sun Java System Calendar Server 6.3 Administration Guide. |
Directory Server |
To configure Directory Server with a non-root ID, create the server instance as a regular user, or specify the user when creating the instance. For instructions, refer to the Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide. |
Messaging Server |
To configure Messaging Server with a non-root ID, use the Messaging Server configurator. See the Sun Java System Messaging Server 6.3 Administration Guide for instructions. |
Web Server |
By default, Web Server is configured with webservd as the runtime user. When using the Web Server configurator, you can specify any runtime user ID. For additional information, refer to the Sun Java System Web Server 7.0 Administrator’s Guide. |
After you have completed the configuration tasks in this chapter, verify postinstallation configuration by starting the product components as described in Verifying After Post-Installation Configuration.