Deploying Newly Created Database User Name Passwords - System Administration - Cloud - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Cloud System Administration

Platform
OnBase
Product
System Administration - Cloud
Release
Foundation 23.1
License
Standard
Essential
Premier
Note:

These steps are assuming that you are continuing from steps in the previous section, which only apply to the OnBase Client and Configuration modules. As of OnBase 18, ADO.NET connection strings are used for connecting to databases except in the OnBase Client and the Configuration module. If you are changing user name or password information for anything outside of OnBase Client or the Configuration module, edit the ADO.NET connection string. For more information on configuring ADO.NET connection strings, see the Application Server module reference guide.

Once you have changed passwords, you must deploy the new OnBase Client and Configuration executables, as well as the Hyland.Core.GrabIcon.dll if you are using the OnBase Application Server. Depending on whether you are using a legacy version of the OnBase Core, you may also need to deploy the dmcore.dll.

Deploying new passwords involves locating the new executables and DLLs created by changing passwords and copying them over to where the old files reside, thereby deleting the old executables and DLLs and replacing them with the new ones. The new files must then be copied to all the workstations that require use of these files.

The new executables and DLLs are stored in a folder named NewKEKExecutables#, where # is the number of times that you have changed the database user name passwords for the selected set of executables. For example, if this is the first time you have changed the database user name passwords for this set of executables, the folder is named NewKEKExecutables1. If this is the fourth time you have changed the passwords for this set of executables, the folder is named NewKEKExecutables4. The NewKEKExecutables# folders are located in the same folder as the current executables (e.g., C:\Program Files\Hyland\ OnBase Client).

If you delete the NewKEKExecutables# folder, OnBase increments the NewKEKExecutables# folder number based on any folders that exist the next time you change the database user name passwords. For example, you change the passwords three times. You delete NewKEKExecutables2 and NewKEKExecutables3. When you change passwords the fourth time, the folder is named NewKEKExecutables2. If you delete all copies of the NewKEKExecutables# folder, such that no NewKEKExecutables# folders exist, the new folder is named NewKEKExecutables1.

Note:

When you upgrade your OnBase executables, any existing NewKEKExecutables# folders are deleted.

To deploy newly created database user name passwords:

  1. Navigate to the file path(s) you specified in the Executable Files field as the locations of your OnBase Client and Configuration executables.
  2. Deploy these new OnBase Client and Configuration executables by copying the executables from the NewKEKExecutables# folder and placing them in the folder where the current executables reside. This will overwrite the current executables.
  3. If you selected the Generate Core dll check box, a new Hyland.Core.GrabIcon.dll is also available in the NewKEKExecutables# folder.

    Copy the new Hyland.Core.GrabIcon.dll from this folder and paste it in the following locations, overwriting the old version of this file:

    • OnBase Core Services: In a default installation, the Core files are located at C:\Program Files\Hyland\Core(32-bit operating systems) or C:\Program Files(x86)\Hyland\Core(64-bit operating systems).

    • OnBase Application Server: In a default installation, this file is located at C:\Inetpub\wwwroot\AppServer\bin.

    • OnBase Studio: In a default installation, this file is located at C:\Program Files(x86)\Hyland\ OnBase Studio (32-bit instances of OnBase Studio) or C:\Program Files\Hyland\ OnBase Studio (64-bit instances of OnBase Studio).

      Tip:

      To ensure that you replace all old versions of Hyland.Core.GrabIcon.dll, perform a Windows search for Hyland.Core.GrabIcon.dll.

  4. Unlock your OnBase database.
  5. Perform an IIS reset on the OnBase Application Server.