12.2.2 Notes on installation

(a) About customizable files

JP1/AJS3 files include files that can be customized by users. Because an upgrade installation does not replace existing customizable files, current user-customized settings are retained.

Note that the directory that contains the customized files also contains model files (files ending with .model) from which the customized files were created. These model files are updated in an upgrade installation. After an upgrade installation has been completed, check whether the files in the directories listed below have been customized. For any customized configuration files you find, make the same customization to the copies of the model files you have made. Next, delete all the existing configuration files, and rename the copies of the model files so that they become the new configuration files. If no files have been customized, you need only to delete all the existing configuration files and rename the copies of the model files.

For JP1/AJS3 - Manager:

• /etc/opt/jp1ajs2

• /etc/opt/jp1ajs2/conf

For JP1/AJS3 - Agent:

• /etc/opt/jp1ajs2

• /etc/opt/jp1ajs2/conf

Cautionary notes:

• When JP1/AJS3 is operating in a cluster system, the model files in the conf directory within the jp1ajs2 shared directory are not updated. Therefore, if the files in the shared directory have been customized, perform the same customization for the copies of the model files in the directories described above instead of customizing the model files in the shared directory. If the files have not been customized, you need only to overwrite files of the same name with the copies of the model files.

  Note that the conf files used for logical hosts are stored in the conf directory within the jp1ajs2 shared directory.

• During upgrade installation, both data collection tools and model files are updated. If you need to customize the data collection tool _04 after upgrade installation, back up the tool before performing upgrade installation.

  You cannot customize the data collection tool jajs_log.

If JP1/AJS2 - Manager is upgraded to JP1/AJS3 - Manager, the process management definition files and extended startup process definition files (jp1ajs_xxxd.conf and jp1ajs_xxxx_0700.conf in the directories listed above) are automatically updated for a JP1/AJS3 - Manager process configuration. If linkage with HP NNM or a queueless job execution environment was set up in JP1/AJS2 - Manager, check whether the settings in these files have been inherited after the upgrade installation and setup has been completed. If these settings have not been inherited, re-specify them. If the restart settings were customized (for example, so that abnormally terminated JP1/AJS2 processes are restarted), the restart settings are reset to the defaults. If you want to disable the restart settings or change the maximum number of restart attempts, customize the settings again after the upgrade installation and setup have been completed.

(b) About upgrade installations of JP1/AJS3 - Manager and JP1/AJS3 - Agent

• Stop all of the following services and processes that are running on the host on which you want to install JP1/AJS3, and then perform the installation:

  • JP1/AJS3 or JP1/AJS2

  • Products prerequisite for JP1/AJS3 or JP1/AJS2

  • Products linked with JP1/AJS3 or JP1/AJS2

• Make sure that the following types of processing are not executed until installation is complete:

  • Processing requests for products linked with JP1/AJS3 or JP1/AJS2

  • Processing that executes JP1/AJS3 or JP1/AJS2 functions or commands

• We recommend that you back up necessary definition files before the upgrade installation. For the objects to be backed up, see 5.2.2 Target files and backup timing in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

• Upgrade installation of JP1/AJS3 - Manager or JP1/AJS3 - Agent fails in the following cases:

  • A process of JP1/AJS3 - Manager or JP1/AJS3 - Agent that has already been installed is running.

  • JP1/Base has not been installed or the version of the installed JP1/Base is not appropriate.

  • A product with which JP1/AJS3 - Manager or JP1/AJS3 - Agent is not compatible has been installed.

• To perform an upgrade installation of JP1/AJS3 - Manager version 10-00 or later from a version earlier than 10-00, you need to migrate the embedded database to the format for version 10-00 and later. For details about how to migrate the embedded database, see 13.5.1 Settings for enhancing the embedded database management function.

• To perform an upgrade installation of JP1/AJS3 - Manager or JP1/AJS3 - Agent in a cluster configuration, see 12.2.7 Upgrade installation in a cluster configuration.

• After upgrading JP1/AJS3 - Manager in the standard configuration, check whether the version of the embedded database is the same as the version indicated in Installation Procedures and System Generation Precautions in the Release Notes. If these versions are different, upgrade the embedded database.

(c) About upgrade installations of JP1/AJS3 - Web Console

• Clear your web browser cache. If you do not clear the cache, the web browser will reference the cache of the previous version, and the upgraded content will not be applied.

• Stop all of the following services and processes that are running on the host on which you want to install JP1/AJS3 - Web Console, and then perform the installation:

  • JP1/AJS3

  • Products prerequisite for JP1/AJS3

  • Products linked with JP1/AJS3

• Make sure that the following types of processing are not executed until installation is complete:

  • Processing requests for products linked with JP1/AJS3

  • Processing that executes JP1/AJS3 functions or commands

(d) When IPv6 addresses are being used for communication

To upgrade JP1/Base or JP1/AJS3 to version 10 or later from version 9 or earlier, and to enable communication using IPv6 addresses, you need to specify settings for communicating using IPv6 addresses.

For details, see 13.4.6 Settings for communication using IPv6 addresses.