Converting the Local Database Encryption with ReconfigureDB.exe

Deployment Servers and Development Clients (Prior to Tools Release 9.2.5.0) connects to the local Oracle database known as E1Local using the “SYSTEM” and “SYS” database accounts. EnterpriseOne generates and then encrypts a password each time it initializes a connection to this database. In Tools Release 9.2.0.0, the algorithm used to generate and encrypt the password was changed. Therefore, if you are upgrading from a Tools Release prior to 9.2.0.0, you need to reset the database password using the following steps.

Note: Starting with Tools Release 9.2.5.0, Development Clients do not use E1Local; however, Deployment Servers continue to use it.

Note: The procedure in this section applies only to the Oracle database called E1Local (also known as Oracle Enterprise Edition or OEE) installed on the Deployment Server and each of the Development Clients.

The encryption used prior to Tools Release 9.2.0.0 is known as “Legacy” encryption. The new encryption introduced with Tools Release 9.2.0.0 is termed “Enhanced” encryption.

The program ReconfigureDB.exe can change the EnterpriseOne local database between the two types of encryption and a plain-text string. Setting the password to a plain-text string allows an EnterpriseOne administrator to perform any required actions on the local database.

Note: For Tools Release 9.2.0.0 and later, the password must be set to Enhanced Encryption. If it is not set, any attempts to log into EnterpriseOne running on the Deployment Server or Development Client will fail. If you change it from Enhanced Encryption to any other password (either a text string or Legacy Encryption), be sure to change it to Enhanced Encryption before trying to run EnterpriseOne.

1. Run ReconfigureDB.Exe

   

2. In the Change from password... area, select Legacy Encryption.

3. In the To password area, select Enhanced Encryption.

4. Click OK

5. Confirm the password change.
6. Click Cancel to exit.