| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Installing: About the Installation |
|
Planning for Java CAPS Installation
Java CAPS Supported Operating Systems
Java CAPS Components and Supported External Systems
Overview of the Graphical User Interface Installation Process
Overview of the Command-line Interface Installation Process
Repository Names and User Names
Contents of the Java CAPS "installer" and "components" Download Files
Contents of the Installation DVDs
Creating a Windows Service for Sun Java System Application Server
Increasing the NetBeans IDE Heap Size
To Increase the Heap Size in NetBeans IDE
Certified Sun Solaris 9 and 10 Patches
IBM AIX 5L 5.2 and 5.3 Patches
Certified IBM AIX 5L Version 5.2 Patches
Certified IBM AIX 5L Version 5.3 Patches
Certified SUSE Linux Enterprise Server 10 Daylight Savings Time Patch
Using the Java CAPS 6 Installation GUI
Using the Java CAPS 6 Installation CLI
Installing Additional Components for Java CAPS 6
Installing Third-Party JAR Files
This topic provides an overview of the GUI and command-line installations, a list of what Java CAPS product names were in the past and what they are now, and the location of the product SAR files on the DVDs.
Caution - Java CAPS Release 6 does not support spaces in the installation directory path.
The installation process is different from prior installations of Java CAPS, and with Release 6 you can perform a complete or custom installation on any supported platform.
Note - There is one exception to this statement; Release 6 does not support Macintosh installation using the command-line interface.
The installation flexibility of Java CAPS enables you to:
Install more than one Domain on a single system.
Manage multiple Projects on a single environment.
The separation of design from deployment makes it possible to use the same components in more than one Project.
Centralize your software distribution.
After uploading software into “software packages,” Administrators select which physical server or groups of physical servers receive the software.
HTTP connections are used to upload and download the software to and from the Repository.