Stat 6.3 - User Guide


	NOTE: Unix and Windows-based file servers have different formats for ASCII type file objects. Accordingly, when you migrate an ASCII type file object via SFTP, the Stat Central Agent checks its destination file server. If the server is Unix, the agent converts the file to the Unix ASCII format, which means singly occurring carriage returns followed by linefeed characters are converted to linefeed characters. If the destination server is Windows, the agent converts the file to the Windows ASCII format, which means singly occurring linefeed characters are converted to carriage returns followed by linefeed characters. In either case, the size of the migrated file may be smaller or larger than it was before it was migrated.

Migrating Data Objects

As with file objects, data object definitions are archived in the Stat Repository. When you migrate an archive set that contains data objects, Stat copies the data object definitions from the Stat Repository to the target environment. If the data object already exists in the target environment, Stat replaces that object definition with the archived copy using the delete and insert method.

Migrating to Distributed Environments

When you migrate objects to a distribution environment, by default Stat migrates those objects to all the environments on its distribution list. However, you can opt to exclude certain environments from the migration.

When defining a migration path, system administrators designate distribution environments and add other environments to their distribution lists. For example, let’s say you have ten production environments and each one physically resides in a different location. 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 your system administrator would define the local or ‘in-house’ production environment as the distribution environment 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 on a distribution list. Also, objects can only be migrated to them, not from them.


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

Graphically, distribution environments are designated by a small icon displayed to the left of the environment graphic, as shown below:

To view a listing of the environments connected to the distribution environment, double-click on the distribution icon. Stat opens the Distributed Environments window, which shows a list of all the environments connected to the distribution environment.

In this window, you can deactivate any environment you do not want to include in a migration. This way, when you migrate an archive set to a distribution environment, Stat migrates the objects only to the active environments in the distribution list. To deactivate all the environments, click Set All Inactive. If you want to reactivate an environment, you can do so at any time by selecting the Active check box, or if you want to reactivate all the environments, click Set All Active.

Also, Stat does displays an error message if it successfully completes a migration to a distribution environment but not to one or more of its associated environments (which would be the case if, for example, the password to one of the environments was incorrect). Instead, this information is displayed in the Migration History window. For more information, see Documenting Migrations (Generic Applications) .

Running a Migration (Generic Applications)

To run a migration:

Open the CSR window and do one of the following:

•

In the Migration Path tab, click and hold your cursor over the source environment for the archive set and drag and drop it in the target environment.

•

In the Archive Sets tab, drag and drop the archive set you want from the table to the target environment's tree node.


	IMPORTANT: Before you can migrate an archive set into an environment that requires migration approval, one or more authorized users must approve the migration. For more information, see the section Migration Approvals and Mass Migrations (Generic Applications) .

Stat opens the Migration window.

(Optional) If you want the Stat Central Agent to process the migration job at some later time, enter the date and time in the Migration Date field.

The field defaults to the current date and time. You can schedule the migration up to 90 days in the future.

(Optional) In the Description field, enter a unique description of the migration.

The field defaults to CSR ID+Archive ID.

(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters.

System administrators may set this option to be selected or de-selected by default.

(Optional) De-select the E-mail Notification option if a business rule or personal rule triggered by a migration event has been defined for the service domain and you do not want Stat to send email notifications that may be triggered by the migration.

This option is selected by default and is displayed only if one or more Migration Notification business or personal rules have been defined for the service domain. Fore more information, see Defining Personal Rules .

Select the archive set you want to migrate.

The window displays a list of archive sets that you can migrate from the selected environment. If you initiated the migration from the Archive Sets tab, the list displays only the archive set that you dragged and dropped onto the target environment.

By default, all the objects in the archive set are selected for the migration. However, with the appropriate security rights, you can exclude either all the file objects or all the database objects from the migration. You can also exclude individual objects.

(Optional) De-select the class of objects (file objects or database objects) you do not want to migrate.

(Optional) In the Migrate column, de-select the individual objects you do not want to migrate.

If you are migrating to a distribution environment, the window displays the list of active target environments. By default, each environment in the distribution list is selected as a target. However, with the appropriate security rights, you can exclude certain environments from the migration.

(Optional) If migrating to a distribution environment, de-select any environment in the list of active target environments you want to exclude from the migration.

If the archive set contains file objects and the target environment is Development, select one of the following options in the Migrate file to field:

•

Development Env – Select if you want to place the file objects in the source file locations of the Development environment

•

Working – Select if you want to place the file objects in the developers’ working directories. Only the file objects assigned to each developer get copied into their working directories.

•

Dev & Working – Select if you want to place the file objects in both the source file locations and the working directories. If the archive set does not contain any file objects or the target environment is not Development, this option is dithered with a value of “NA.”

Click Migrate.

At this point, Stat prompts you to perform the pre-migration steps (if any) that have been defined for the target environment or for the objects or object types in the archive set.

Complete any required pre-migration steps.

For more information, see Pre and Post Migration Steps .

After completing the pre-migration steps, Stat opens the CSR Migrations Console, which shows that the migration job has been submitted to the Stat Central Agent. The Agent either begins processing the migration immediately, or if you scheduled the migration, at the date and time you specified. For more information, see Migration Console .

If you are only migrating file objects, Stat copies the file objects into the target environment.