Post-Upgrade Procedures
This guide provides instructions on important procedures that you should accomplish after a successful software upgrade. Follow the sequence of procedures to properly apply the updates in the Core Server setup.
After verifying the files, directories, and running processes, you may proceed with verifying the Open iT Core Server web interface.
After upgrading, some existing users may be unable to sign in because their passwords use an older format. If this occurs, an Administrator must reset the user's password.
A password reset is required only if the account:
- was created in a version earlier than 9.8.13;
- has not had its password migrated; and
- is accessed again after upgrading to 9.8.13 or later.
After completing any required password resets, verify that the existing Core Server configurations are retained.
Reapplying Core Server Web Interface Settings/Customizations
-
In the Core Server web interface, go to Administration > Settings > Registry.
-
Using the screenshot of the Registry page as reference, reapply the page settings.
-
Click the Save Changes button.
-
Using the screenshots of the other pages as reference, verify whether the previous customizations are still in place on the following pages after the upgrade.
-
Reapply any missing customizations as needed.
Reapplying Core Server Configurations
- Windows
- Unix
-
Check for the custom file configurations from the
C:\Program Files\OpeniT\Core\Configurationbackup. -
Apply the custom file configurations if the previous configuration settings are not retained after the upgrade.
-
Save the changes.
-
Check for the custom file configurations from the
/var/opt/openit/etcbackup. -
Apply the custom file configurations if the previous configuration settings are not retained after the upgrade.
-
Save the changes.
-
Check for the custom configurations in the
openit.cfgfile from the/etc/opt/openitbackup. -
Apply the old custom configurations in the upgraded
openit.cfgfile.warningAvoid deleting directives that did not exist in the previous configuration file.
-
Save the changes.
For any other custom configurations, scripts, or binaries deployed within your setup, feel free to reach out to the Open iT Support Team at support@openit.com for assistance in integrating the changes into your upgraded software.
Correcting IdP Signin Events Mapping After Upgrading from 10.2.600 to 10.2.630 (Optional)
If you upgraded Core Server directly from version 10.2.600 to 10.2.630, the IdP Signin Events data type may be assigned an incorrect data type ID in the acc_types configuration. This may also affect the generated classvar_mapping_config.
Complete the following steps to correct the configuration.
- Windows
- Unix
-
Go to the Configuration directory, which is by default in
C:\Program Files\OpeniT\Core\Configuration, and open theacc_typesconfiguration file. -
Locate the
IdP^Signin^Eventsblock:acc_types(IdP^Signin^Events,
(
(Count,Number^of^Authentication,x,SUM),
(Events,Number^of^Events,x,SUM)
)
(User,
Mail,
Status,
Application,
Authentication,
Product)
), -
Move the entire
IdP^Signin^Eventsblock so that it appears immediately before theAzure^Resource^Usage^Costblock. -
Save the changes.
-
Open a command prompt with Administrator level privileges.
-
Go to the bin directory, which is by default in
C:\Program Files\OpeniT\Core\bin, run the command:Command Syntaxcd <bin_dir>Examplecd C:\Program Files\OpeniT\Core\bin -
Once in the directory, run the following commands:
Command Syntaxgenerate_classvar_mappingCommand Syntaxrefresh_webgui -
Verify that IdP Signin Events is assigned to the correct data type ID and that the other data types remain correctly mapped.
-
Go to the etc directory, which is by default in
/var/opt/openit/etc/, and open theacc_typesconfiguration file. -
Locate the
IdP^Signin^Eventsblock:acc_types(IdP^Signin^Events,
(
(Count,Number^of^Authentication,x,SUM),
(Events,Number^of^Events,x,SUM)
)
(User,
Mail,
Status,
Application,
Authentication,
Product)
), -
Move the entire
IdP^Signin^Eventsblock so that it appears immediately before theAzure^Resource^Usage^Costblock. -
Save the changes.
-
Go to the bin directory, which is by default in
/opt/openit/bin, run the command:Command Syntaxcd <bin_dir>Examplecd /opt/openit/bin -
Once in the directory, run the following commands:
Command Syntax./generate_classvar_mappingCommand Syntax./refresh_webgui -
Verify that IdP Signin Events is assigned to the correct data type ID and that the other data types remain correctly mapped.
Next Steps?
If you have upgraded from Core Server version 9 to version 10, you can now proceed with Ingress installation.