It's a common practice for a system administrator to implement and test new system functionality, perform system upgrades, apply service packs or change any other system wide parameters. Very often the impact of such changes to a production environment can't be evaluated from the very beginning, and can result in severe problems or even a complete collapse of the system. To avoid such dangerous situations a SunSystems test environment has to be created and maintained on a separate machine. It's the test environment that is used for all testings before they are applied in the production.

In this article you will be demonstrated how you can a SunSystems test environment.
The test environment should be created as follows:
1. Copy the live SunSystems database to another test server. This test server must be separate from the live server to avoid impacting performance of the live system.
2. Install the current version of SunSystems on a test server with the same directory/file structure as the live server. This test server must be eparate from the live server to avoid invalidating registry entries on the live system. The directory/file structure of the test server must be he same as that of the live server to ensure accurate replication of .ini file settings. The installation of the current version of unSystems ensures accurate replication of registry settings and Windows/system files.
3. Copy the entire live SunSystems directory and file structure, including all contents, onto the  installation created in step 2. This ensures ccurate replication of all customization to forms, reports, menus, etc.
4. The test environment must have the same software as the live environment. For example, if MS-SQL Server 2000 SP3 is installed on he live server, it must also exist on the test server.
5. It is advisable to have a client machine in the test environment.
Note: Any system menu (.opx), system form layout (.sfl) files, and system report data source (.srd) files that have been customized are saved under a ifferent name. System menu (.opx), system form layout (.sfl) files, and system report data source (.srd) files that have been customized without hanging the file name are overwritten by the upgrade process.

Only registered users can write comments.
Please login or register.