Stat 6.1 - System Administration Guide


	NOTE: For any service domain in which you want to use customer priorities, be sure to select Use Cust Prio in the service domain maintenance table. Otherwise, the Customer Priority field will be grayed out on CSRs opened in that service domain. For more information, see Service Domain Maintenance .


Value	Description
Active	If selected, activates the priority definition in Stat
Prio Cd (Key Value)	1-4 character code that uniquely identifies the priority
Description (Required Value)	1-35 character description of the priority
Prio Order	The position of the priority in the Customer Priority field
Last Update (Read Only)	The date and time that this record was last updated
Update By (Read Only)	The user that last updated this record

Generic Application Migration Path Maintenance

The Generic Application Migration Path Maintenance table defines migration paths used in Stat’s generic application change management module. Migration paths define the progression of objects from one environment to another. When a user associates objects with a CSR, they must first select a migration path.

For more detailed information on migration paths, see the book, Change Management for Generic Applications, Chapter 1, “Object Management.”

When defining migration paths, keep in mind the following considerations:

•

Environments cannot be listed on the path more than once

•

The environments defined as Base, Development, and Distribution must also appear on the path. It is not required that they appear as environment 1, 2, and 3, but they must appear somewhere.

•

Environments connected to a distribution environment (i.e., the distributed environments) should not appear in any other migration path. This is because objects are not locked in the connected environments and overwrites could occur if the same objects exist in other environments.

•

Environments cannot exist on migration paths of different service domains. An environment cannot be shared by multiple service domains.

•

An environment can exist in multiple migration paths in a service domain

•

If you attempt to remove from a migration path an environment that is used in a workflow transfer rule, Stat displays a warning message. If you proceed in removing the environment, Stat automatically deletes the transfer rules from any workflow in which the environment is used.

•

Service domains and environments have a one-to-many correlation

Generic application migration path security is controlled by the following user class rights:

•

Generic Application Migration Paths - Add

•

Generic Application Migration Paths - Edit

The Generic Application Migration Path Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Generic Application Migration Paths.

The following table defines the fields (columns) in the Generic Application Migration Path Maintenance window.


Value	Description
Active	If selected, activates the value in stat
Migration Cd (Key Value)	A 1-10 character code that uniquely identifies this migration path NOTE: Special characters are not allowed, including: ~ ‘ “ * % ( ) ,
Description (Required Value)	A 1-35 character description of the path
Base Object Source (Required Value)	The Base environment from where the base archive set is created
Development Environment (Required Value)	The environment where development takes place
Last Update (Read Only)	The date and time that this record was last updated
Update By (Read Only)	The user who last updated this record

Migration Path Diagram

After you have specified the migration code and description, click Apply to save your work. Then select the migration path and click Template.... This opens the Migration Path Definition window. The left section of the window displays a list of each environment that can be added to the new migration path (environments previously applied to a migration path in a different service domain will not be displayed). The right section of the window is where you arrange the icons to create a graphical diagram representing the sequence of the migration.


	NOTE: It is recommended that you have the basic design of your migration path diagram in place before you build it in the Migration Path Definition window. This avoids the time-consuming process of rebuilding a diagram if mistakes or oversights occur.

To create a migration path:

In the left section of the window, click and hold on the first environment of the migration path. Then drag into the right section of the window to where you want to place the graphic and release the mouse button.

Following the sequence of the migration path, place the other environments in the migration path in the diagram.

Environments are labeled according to the order in which they are placed in the diagram. The first environment you place in the diagram is labeled “1”, the second “2” and so on.

Right-click on the graphic representing the base environment in the migration path. Then in the pop-up menu, select Set base environment.

Right-click on the graphic representing the development environment in the migration path. Then in the pop-menu, select Set dev environment.

(Optional) If you want to designate a distribution database, right-click on the graphic representing the distribution environment in the migration path. Then in the pop-up menu, select Enable distribution environment.

For more information, see Defining Distribution Environments .

(Optional) If you want to modify the migration path, right-click the graphic representing the environment you want to change and do any of the following:

•

To designate the environment as the new base environment in the migration path, select Set base environment.

•

To designate the environment as the new development environment in the migration path, select Set dev environment.

•

To switch the environment’s place in the migration path with another environment, select Swap environment number. Then in the prompt select the number of the environment you want to switch and click OK.

•

To remove the environment from the diagram, select Delete environment.


	NOTE: After deleting an environment, you may need to adjust the order numbers of the remaining environments in the diagram to make them consecutive. Stat does this for you automatically when you save.

Defining Distribution Environments

Distribution environments allow users to migrate objects to multiple environments distributed over a network at one time. When a user migrates an archive set to a distribution environment, Stat automatically migrates the archive set to a list of connected environments.

You define distribution environments at the migration path level. The first step is to designate certain environments in a migration path as distribution environments. Then you determine which environments you want to connect to them. For example, let’s say you have ten production environments. All of your development work is done centrally, and when ready, changes are migrated out to all the production environments at the same time. Most likely you would define the local or ‘in-house’ production environment as the distribution environment on the migration path and connect it to the nine other production environments.

Although connected to the distribution environment, the other environments are not represented graphically and are not technically part of the migration path. This means that objects cannot be locked in the environments connected to a distribution environment. Likewise, objects can only be migrated to them; you cannot archive objects from these environments.

For more information on distribution environments, see the book, Change Management for Generic Applications, Chapter 3, “Object Migrations.”


	CAUTION: Because objects are not locked when migrated to the environments connected to a distribution environment, it is recommended that you do not include these environments in any other migration path. This eliminates the possibility of two developers accidently overwriting each other’s work.