Dashboard Change Management in Release 5

By Emma Schwarz

Change Management is the process of moving components from one installation to another – for example, to accommodate test and production systems. The test system is developed, and when it’s ready to be rolled out, the production system is upgraded with the components from the test system.

Dashboard administrators can perform simple Change Management in the 5.2 release of Dashboard. Customizations developed on one Dashboard installation can be moved to other installations so that there is an identical configuration of the Dashboard on more than one system.

The Change Management described in this article assumes that the entire Dashboard system is moved from the test environment to the production environment, replacing any previous Dashboard customizations or personalizations in the move. Both installations must be at the 5.2 level, but can be either 5.2 or 5.2.1. The steps for moving customizations in 5.2 follow.

Migrating to a New Installation of the Dashboard

You must copy the following directories from the customized system to the new system, replacing the corresponding folders and files on the new system. All of the directories are located in ibi\WebFOCUS52\worp.

	Worp_custom: This folder contains the customized public and group views. The folder names under worp_custom correspond to the view link URL assigned when the view is created in the View Builder. You should copy the entire directory.
	Worp_users: This folder contains additional folders used for customized public and group views. The folder names are identical to the ones in the worp_custom directory. In addition, each Dashboard user will have a folder in this directory. Copy the entire directory.
	Conf: This folder contains additional configuration files. Instead of moving the entire folder, you need only copy the files listed below. Other files in the directory are static ones that should not be moved.
	Worp_mre.epd: This contains the password entered in the public user screen in the View Builder. If the public user password is the same on both systems, you should copy this file. If the passwords differ, the administrator will update the file when saving the password in the public user section of the View Builder. If the public user password is blank, this file will not exist.
	Worp_eda.epd: This file contains the user ID and password entered in the server screen in the View Builder. If the WebFOCUS server user ID and password for the public user are the same on both systems, you should copy this file. Otherwise, the administrator can update this file in the server section of the View Builder. If the WebFOCUS server is running without security, this file will not exist.
	*.tbx: These files contain toolbox information, and you should copy the files.
	Mpv.xml: This contains the list of the views that have been created and information about each user’s view inheritance. The file should be copied.
	Roletree.xml: This file, which you should copy, contains role tree information.
	Worp_html: If you are an advanced Dashboard administrator, you may have created your own "customized" Dashboard view by copying one of the directories that is distributed with the product to a new directory and making changes to fit the needs of your Dashboard. Remember that you need to copy the new directories, although the distribute directories should not be copied.

After copying or editing the directories described in this article, you must reload the WebFOCUS Web application or recycle your Web server to load the updated files into the servlet.