E.2 Conditions for setting an AJS administrator account
All of the following conditions must be satisfied to set up an AJS administrator account. Make sure beforehand that all of these conditions can be satisfied in the environment where the JP1/AJS3 system is to be created.
-
Initial installation of JP1/AJS3
An AJS administrator account can be set up when JP1/AJS3 is initially installed. No AJS administrator account can be set up in an environment where JP1/AJS3 is already installed.
Note that you cannot set up an AJS administrator account when you perform an upgrade installation. If you want to set up an AJS administrator account when you upgrade JP1/AJS3, back up the definitions of JP1/AJS3 currently in use, uninstall JP1/AJS3, and re-install JP1/AJS3.
-
Operation of JP1/AJS3 by using an AJS administrator account does not violate security policies
An AJS administrator can control JP1/AJS3 processes that are executed with superuser privileges. If there are security policy issues when an ordinary OS user is able to control processes executed with superuser privileges, you must not set an AJS administrator account.
-
A dedicated OS user can be prepared for the AJS administrator account
If you set an OS user as an AJS administrator, you cannot change the setting later. For this reason, prepare a dedicated OS user for the AJS administrator account so that the AJS administrator account does not need to be changed during operation.
If you set an OS user assigned solely to an individual for the AJS administrator account, problems arise if the individual is transferred somewhere else. Do not set an OS user assigned solely to an individual for the AJS administrator account.