Missing .asadmintruststore File Causes Bugs During Upgrade

If the .asadmintruststore file does not exist in the server administrator's home directory, you may experience serious bugs when upgrading certain applications hosted on the server.

Solution

• If possible, the asadmin start-domain domain1 command should be run by user who installed the server.

• If it is not run by that user, the .asadmintruststore file should be moved or copied from the home directory of installing user to the home directory of the running user.

• Note that if the file is moved (not copied) from the installing user's home directory to the running user's home directory, you might experience application upgrade problems, as described in bugs 6315957, 6309079, 6310428 and 6312869, because the upgrade/install user (normally root in Java ES) will no longer have the .asadminstruststore file in his or her home directory.

Restoring a Deleted .asadmintruststore File

There may be instances when the .asadminstrustore file for a domain has been has been deleted. In such cases, you can create a new .asadminstrustore file.

To create a new .asadmintruststore file

1. Use the asadmin start-domain command to start the domain you want to manage.

   Note that this is a local asadmin command, and as such it does not require an ~/.asadmintruststore file to start the domain.

2. Run any remote asadmin command.

   A remote asadmin command is one that requires ---user, ---passwordfile (--password), ---host and ---port options to be specified on the command line, and needs the target domain to be running. A typical remote asadmin command is asadmin list.

3. Accept the new Domain Certificate by pressing “y” when prompted.