The Application Server installation methods are as follows:

• New installation
  With this method, you install Application Server in an environment where Application Server is installed. You can choose the component software you want to install from "Standard" and "Custom". If you choose "Standard", all the component software recommended for Application Server will be installed. If you choose "Custom", the component software selected from among the component software supporting Application Server will be installed. For details, see 2.2.2 Installing new Application Server (In Windows), 2.2.3 Installing new Application Server (In AIX, HP-UX), or 2.2.4 Installing new Application Server (In Linux).
  
• Update installation
  With this method, you install Application Server (same product) in an environment where Application Server is already installed. You can choose the component software you want to install from "Standard" and "Custom". If you choose "Standard", all the component software recommended for Application Server will be re-installed. If you choose "Custom", the component software selected from among the component software supporting Application Server will be re-installed. For details, see Appendix F Update installation of Application Server.
  

The other installation methods are as follows:

• Installation by using JP1/SC/DPM to replicate the disk
  With this method, you use JP1/SC/DPM to install a replication of the created disk image. For details, see Appendix G Installation by using JP1/SC/DPM to replicate the disk.
  
• Remote installation
  With this installation method, you use JP1/NETM/DM and Groupmax Remote Installation to distribute the software to the client via the network. For details, see Appendix H Remote installation.
  

Note that the Application Server installation method described in this example is the new installation method.

When you install Component Container, which is one of the component software included in the Application Server products, the user environment is handled differently for each type of installation. The following table describes the handling of the user environment for each installation type.

Table 2-1 Handling of the user environment for each installation type

Installation type		User definition of the J2EE server or batch server	User definition of the server management commands	Work directory of the server#
New installation		The installer sets up the default J2EE server or batch server, and creates the user definition.	The installer creates the default user definition.	The work directory is created when the J2EE server or batch server starts for the first time.
Update installation	Updating the same versions (overwrite)	The previous settings are inherited. If the definition directory (Application-Server-installation-directory\CC\server\usrconf\ejb\host-name, or /opt/Cosminexus/CC/server/usrconf/ejb/host-name) of the default server (server of the specified host name) does not exist, the definition file is automatically set up.	The previous settings are inherited.	The previous settings are inherited.
	Updating different versions (upgrading the version)	The previous settings are inherited.	The previous settings are inherited.	After installation, execute the cjenvupdate command (migration command for J2EE servers or batch servers) to migrate the work directory. The migration information is stored in the existing directory, and is used as is. For details, see 10.3 Procedure for migrating Application Server (for update installation) in the uCosminexus Application Server Maintenance and Migration Guide.

#:

The work directory of the server varies for the J2EE servers and batch servers. For details on the J2EE server work directory, see Appendix C.1 Work directory of the J2EE server. For details on the batch server work directory, see Appendix C.2 Work directory of the batch server.

The component software included in each product supports the Application Server and BPM/ESB platform functionality. The functionality you can implement varies in accordance with the type of component software included in the product. The following table describes the mapping of the products and the component software. For details on the component software, see 2.2.2 Overview of the component software functionality in the uCosminexus Application Server Overview.

Table 2-2 Mapping of the products and the component software

Component software name	Application Server		BPM/ESB platform		Optional products
	Application Server	Developer	Service Platform	Service Architect	Client
Application Development Plug-in	N	Y	N	Y	N
Component Container	Y	Y	Y	Y	N
Component Container - Client	N	N	N	N	Y
Component Container - Redirector	Y	Y	Y	Y	N
Component Transaction Monitor	Y	Y	Y	Y	N
Developer's Kit for Java	Y	Y	Y	Y	Y
HTTP Server	Y	Y	Y	Y	N
Performance Tracer	Y	Y	Y	Y	Y
Reliable Messaging	Y	Y	Y	Y	N
Service Coordinator	N	N	Y	Y	N
Service Development Plug-in	N	N	N	Y	N
TPBroker	Y	Y	Y	Y	Y
Web Services - Security	Y	Y	Y	Y	N
XML Processor	Y	Y	Y	Y	Y
HiRDB Embedded Server Version 8	N	Y	N	Y	N

Legend:

Y: Included.

N: Not included.

Also, the component software has the dependence relationship described in the following table. Note this relationship when you install and un-install the software.

Table 2-3 Dependence relationship between component software

Component software subject to operations	Prerequisite component software
Application Development Plug-in	Component Container Developer's Kit for Java XML Processor
Component Container	Developer's Kit for Java Performance Tracer TPBroker XML Processor
Component Container - Client	Developer's Kit for Java Performance Tracer TPBroker
Component Container - Redirector	Performance Tracer
Component Transaction Monitor	Performance Tracer
Developer's Kit for Java	--
HTTP Server	--
Performance Tracer	--
Reliable Messaging	Component Container
Service Coordinator	Component Container Component Transaction Monitor Developer's Kit for Java HTTP Server Performance Tracer Reliable Messaging TPBroker XML Processor DABroker Library#1
Service Development Plug-in	Component Container Developer's Kit for Java Service Coordinator XML Processor
TPBroker	Developer's Kit for Java
Web Services - Security	Component Container Developer's Kit for Java XML Processor
XML Processor	Component Container#2 Developer's Kit for Java
HiRDB Embedded Server Version 8	--

Legend:

--: Indicates that this software does not have prerequisite component software.

#1: Required only in Windows x86 and HP-UX (IPF).

#2: Required for using the schema cache functionality in software other than Client. Not required for Client.

The product media describes the procedure for a CD-ROM. If the product media is a DVD-ROM, replace CD-ROM with DVD-ROM.