![[Contents]](FIGURE/CONTENT.GIF)
uCosminexus Application Server, System Setup and Operation Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
This subsection separately describes the notes on the installation and un-installation of Application Server for the times at which the operations are performed.
| Classification | Notes | New installation | Update installation | Un-installation |
|---|---|---|---|---|
| Common to OSs | All the directories other than those storing the customized files, such as user-defined files, are deleted. Therefore, do not store required files in the product directory. The directories to be deleted are deleted unconditionally. Therefore, do not store user-specific files in these directories. |
-- | -- | Y |
| If you install and un-install this product version or the evaluation version, and then install an earlier product version, make sure that the environment (Application-Server-installation-directory\CC, or /opt/Cosminexus/CC) created with this version does not remain in the installation destination. If the environment created with this version is retained, the version is not migrated to the earlier version; therefore, the product operations and the update installation performed later might not function properly. If the environment created with this version is retained, change the installation destination, or delete or migrate the environment created with this version, and then install the product. | Y | -- | -- | |
| Common to Windows | This product cannot be installed in an environment where an earlier Application Server product considered as a successor product, is installed. In this case, un-install the installed earlier products and then install this product. | Y | -- | -- |
| Before you install the product, check the disk space at the installation destination, and make sure that the space required for installation is allocated. | Y | -- | -- | |
| For the update installation of the product, make sure that you make a backup for the required files, such as the user-created files, before installation. Also, in the case of an update installation to a different version (the version is upgraded), if you copy and operate the files provided with the product to another directory, copy the newly installed files after update installation and then perform the operations. |
-- | Y | -- | |
| Before you install and un-install the product, terminate the running applications. Terminate the resident programs as well. | Y | Y | Y | |
| If this product is installed or un-installed while the programs and services provided by this product are running, an error might occur. Install or un-install this product after stopping the programs and services provided by this product and the programs and services that are no longer required. | Y | Y | Y | |
| If this product is installed or un-installed while the files provided by this product are in use, an error might occur. Install or un-install this product when the files provided by the product are not in use. | Y | Y | Y | |
| With an environment where the Hitachi Web Server service is registered, stop the Hitachi Web Server service before you perform update installation with the same version (overwrite). | -- | Y | -- | |
| When you start the installation and un-installation of the product and component software, a dialog box indicating the preparation of setup is displayed. Do not click the Cancel button in this dialog box. | Y | Y | Y | |
| Do not perform an update installation that will lead to the installation of an earlier version. | -- | Y | -- | |
| Do not specify accounts other than the default local system account in the logon accounts of the Management Server and Administration Agent services. However, when network resources are accessed from a J2EE application, specify settings so that the logon account of the Administration Agent service belongs to the Administrators group of the local host. | Y | Y | -- | |
| You cannot install HTTP Server in an environment where a stand-alone Web Server is installed. Un-install the stand-alone Web Server and then install HTTP Server. | -- | Y | -- | |
| Before you un-install a stand-alone Web Server, make a backup of the required files. | -- | -- | Y | |
| To install the product in an environment where a stand-alone Web Server is installed, migrate the files (config files such as httpsd.conf, and the user-created contents) used with the stand-alone Web Server, and make the necessary corrections so that the files correspond to the new installation directory. | Y | -- | -- | |
| Windows x64 | Do not specify the files and directories beneath system-drive:\Windows\System32 directory in the installation destination. | Y | -- | -- |
For the following products, the Windows 64-bit products cannot be installed in an environment where the Windows 32-bit products are already installed:
|
-- | Y | -- | |
| Windows x86 | When installing the following products in Windows XP, if the correction program Q328310 is applied in Windows XP, apply the correction program Q329623 before installing the products:
|
Y | -- | -- |
For the following products, the Windows 32-bit products cannot be installed in an environment where the Windows 64-bit products are already installed:
|
-- | Y | -- | |
| Common to UNIX | To use the following products, make sure that the common modules of the products are installed:
|
Y | -- | -- |
| Use the PP installer for installing and un-installing the products. The root permissions are required for installation and un-installation. | Y | Y | Y | |
| Un-install Trace Common Library as and when required, when the component software of the products is un-installed. However, if the un-installation of Trace Common Library fails and a message is displayed, you can also execute a command to un-install Trace Common Library alone. To un-install, execute the following command: /opt/hitachi/HNTRLib2/etc/hntr2setupThe menu is displayed. Select 9 for a normal un-installation and 0 for a forceful un-installation. |
-- | -- | Y | |
| If the installation directory is changed, the installation becomes a new installation. | -- | Y | -- | |
| After OS installation, the host name is set up for the IP address 127.0.0.1 in the /etc/hosts file by default. To use TPBroker for communication, the host name must be set up for the IP address allocated to the network interface. Therefore, specify an appropriate IP address, allocated to the network interface, for the host name in the /etc/hosts file. | Y | -- | -- | |
| After OS installation, the host name is set up for the IP address 127.0.0.1 in the /etc/hosts file by default. To use Performance Tracer, the host name must be set up for the IP address allocated to the network interface. Therefore, specify an appropriate IP address, allocated to the network interface, for the host name in the /etc/hosts file. | Y | -- | -- | |
| For Application Server and Service Platform, check whether disk space is available at the installation destination. For details on the disk occupancy, see the Release Notes. | Y | -- | -- | |
| For Application Server and Service Platform, check whether disk space is available in the temporary directory (/tmp). For details on the disk occupancy, see the Release Notes. If there is no space in /tmp, specify a directory with space in the environment variable TMPDIR and then install the products. | Y | -- | -- |
| Classification | Notes | New installation | Update installation | Un-installation |
|---|---|---|---|---|
| Common to Windows | With an environment where the Hitachi Web Server service is registered, if an error (such as a registry access error) occurs when you perform an update installation with the same version (overwrite), un-install and then re-install the service. | -- | Y | -- |
| When you use an installer for installation, make sure that you do not remove the product media from the CD-ROM drive and that you do not terminate the installer forcefully. If you perform these operations, the installation information might become inconsistent and you might not be able to execute subsequent installation and un-installation. | Y | Y | -- | |
| To complete the installation processing, make sure you restart the OS after the installation is complete. Note that even when you un-install the product after installation, restart the OS to complete installation, and then un-install the product. | Y | Y | Y | |
| When you un-install the product, or un-install the component software included in the product, make sure you restart the OS to complete the un-installation. | -- | -- | Y | |
| With the product and component software included in the product, the installation termination processing might take some time. Wait until installation is complete and the control moves to the next window. | Y | Y | -- | |
| If you cancel a process during installation, the installation processing after the cancelled component software is cancelled. The component software for which processing was completed before the cancelled component software remains installed. Also, even if you cancel a process during un-installation, the un-installation processing after the cancelled component software is cancelled. The component software for which processing was completed before the cancelled component software remains un-installed. |
Y | Y | Y | |
| If you un-install the product after executing update installation with the same version multiple times, without un-installing even once along the way, an error occurs and the operation might fail. In this case, execute un-installation once again. Some of the directories and files might not be deleted, but this does not affect the installation process executed the next time. | -- | -- | Y | |
| During installation, the installation processing sometimes hangs up without terminating the conime.exe process invoked from the installer. If the installation processing hangs up with the conime.exe process still existing, use the task manager (Taskmgr.exe) to terminate the running conime.exe process. | Y | Y | -- |
| Classification | Notes | New installation | Update installation | Un-installation |
|---|---|---|---|---|
| Common to OSs Common to Windows |
If installation fails, check the following points:
|
Y | Y | -- |
| When the environment is migrated by performing an update installation to a different version (version upgrade), the directory that was used in the earlier version is inherited and used as the work directory. Make sure you do not delete the earlier work directory version by mistake. | -- | Y | -- | |
| If an update installation (version upgrade) is performed from version 08-00 or earlier to 08-00 or later, the "management of logical server applications" in the management portal is operated in the V7 compatibility mode. To operate in the V8 mode, specify false in the com.cosminexus.mngsvr.compat.operation_app key of mserver.properties. | -- | Y | -- | |
| The Administration Agent setup file, adminagent.xml, is overwritten during installation, and the existing file is stored as adminagent.xml.bak. If you are editing and operating adminagent.xml, re-edit the previously edited items in the newly installed file. | -- | Y | -- | |
| The list files subject to snapshot log collection, snapshotlog.conf and snapshotlog.2.conf, are overwritten during installation, and the existing files are stored as snapshotlog.conf.bak, and snapshotlog.2.conf.bak. If you are editing and operating the files subject to snapshot log collection, re-edit the previously edited items in the newly installed files. | -- | Y | -- | |
| With an environment where the Hitachi Web Server service is registered, the Hitachi Web Server service remains as is after you perform an update installation with the same version (overwrite). The Cosminexus HTTP Server service is not registered. | -- | Y | -- | |
| With an environment where the Hitachi Web Server service is registered, when you perform an update installation (version upgrade) from a version that is different from the Web Server version, the files, directories, and utilities related to the HTML manuals and GUI server management functionality might remain behind without being deleted. These files cannot be used with the updated version. | -- | Y | -- | |
| Common to UNIX | Only a user who has the root permission can update the installation destination directories and files. Therefore, when Component Container Administrator is set up, specify the Component Container Administrator write permission for the following directories and files:
Note that when you perform an update installation with the same version (overwrite), the directory and file attributes return to the default status. In this case, change the directory and file attributes in accordance with the operations. |
Y | Y | -- |
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.