Critical PropertyTable and AgileUser Entries

In order for Agile 9.3.2 to work properly, there are some critical accounts such as superadmin, admin, ifsuser, and a couple of others.  In addition, a keystore value has also been added in the database.  For things to work properly, after a dump file from another environment is loaded, the original values must be restored.  This means that they must be obtained from the system after installation.  If you fail to save them, then you will need to reinstall Agile!
Here are the steps to save out the necessary values and create a SQL file to add to the import script(s)

1. Execute the following SQL:
   1. select * from propertytable WHERE parentid=5004 AND propertyid=1008;
   2. select loginid, login_pwd from agileuser where loginid in (‘admin’,’superadmin’,’ifsuser’,’agileuser’);
2. Create a file called set_agile_pwds.sql and store it in the same path as agile9imp.bat add the following lines to it using the passwords from the step above:

UPDATE propertytable SET value='' WHERE parentid=5004 AND propertyid=1008;
commit;

UPDATE agileuser SET login_pwd ='' WHERE loginid = 'admin';
UPDATE agileuser SET login_pwd ='' WHERE loginid = 'superadmin';
UPDATE agileuser SET login_pwd ='' WHERE loginid = 'ifsuser';
UPDATE agileuser SET login_pwd ='' WHERE loginid = 'agileuser';
commit;
exit;

Chances are you could use the same password for admin, superadmin, ifsuser and agileuser if you opted to use the same password for all accounts during installation but I did not test that.

Modifying the Import Scripts

Now that your password script is set up, all that is left is to add it to the import script.  Add the following line to agile9imp or agile9impdp before the :end label

%ORACLE_HOME%binsqlplus agile/%PW_AGILE% @set_agile_pwds.sql

Installation Process Changes

If you have a checklist you use for installations, make sure you add the following

After the installation is complete, save out the original dump file so you can retrieve these settings if required

1. Create a new SQL file to reset the password
2. Modify the import script(s) to call the password reset SQL file
3. TEST IT!