Management of all changes to the system are recommended to follow best practice procedures. Whether the changes derive from a OneStream software upgrade, or through regular application maintenance, all changes are recommended to be first deployed and tested in a development environment. There are additional benefits of making a recent copy of the production Application database, renaming it and using this as a base for these changes. Search for “Rename Application” in the Installation and Configuration Guide.
Prior to being deployed to a production environment, it is recommended to extract changes from the development environment and assess this deployment of changes in a separate test environment.
Deploying changes to a production environment should avoid times during high load and high application activity. Changes to these types of application artifacts especially should not be performed against a production environment experiencing heavy activity:
-
Business Rules, whether they contain Global functions or not
-
Confirmation Rules
-
Metadata, especially when using member formulas
Applying changes like this while the production system is under a high level of activity may have a negative impact on servers and have the potential to cause running processes to produce an error.
Standard environments are recommended to schedule production changes during slow periods or non-work hours. Large environments should consider using the Pause functionality within the Environment tab to allow activity to wind down. These large environment managers should also consider the Marketplace solution, Process Blocker, which allows a pause of critical processes to perform maintenance on the system, without having to shut down the entire application. Process Blocker allows current tasks to be completed, while any new requests are queued, allowing the changes to be applied safely and effectively. Once these changes are in place, it is recommended to significantly limit the ability for users to make such changes during high volume.
It is key that servers get a chance to recycle for good system memory health. IIS also has an Idle Time-Out setting for our OneStreamAppAppPool. This setting should be set to 0 since OneStream has other settings to recycle IIS. For active, global environments with Data Management Sequences regularly being executed, a recycle of IIS is recommended every 24 hours for these OneStream App Servers. Please discuss this situation with OneStream Support to find what is recommended, as each situation may vary.
