Stat 6.2 - System Administration Guide

Testing Environment Connections

After defining an environment in the maintenance table, you can make sure that you have entered all the information correctly by clicking Test Connection. This makes Stat establish a connection to the newly defined environment. If successful, Stat immediately disconnects from the environment and displays a “Connection Successful” message. If Stat is unable to connect, it displays an error message.

You can also test connections to multiple databases simultaneously. To test multiple connections, hold the <Ctrl> or <Shift> keys and select the databases you want to test. Then click Test Selected. Stat attempts to establish a connection to each database and reports its results in the Database Test Connect window

Note that when you test a single environment, Stat does not validate the values specified in the fields Host Name, Service Name, or DB Listener Port. If any of these fields are not configured properly, the Stat Central Agent will log an error when the user attempts to migrate an object to or from the environment. When you test multiple connections, however, Stat does test both client and agent connections, including Host Name, Service Name, DB Listener Port or (in the case of Oracle-based environments) TNS Entry.


	NOTE: When testing environment connections in the Stat Web Client, Stat Web attempts to connect using the Host, Port, Service Name, and TNS Entry values specified in the Stat maintenance tables for each particular environment. If there is no TNS Entry value specified for an environment, it uses the Host/Port/Service Name values. If a TNS Entry value is specified, it uses that value and disregards the others.

Inactivating Generic Application Environments

To inactivate an environment, de-select Active. Stat displays a warning message if the environment is currently part of a migration path.


	CAUTION: Be careful inactivating environments that are part of migration paths. Objects in inactive environments cannot be archived or migrated.

Managing Source File Locations by Environment

After defining an environment, the next step is to specify the source file locations for the file types defined for that environment. For each file type, you can specify an unlimited number of source file locations. When Stat creates an archive set that includes a file object from that environment, it searches for the file in the first location you specified (Path ID = 1). If the file is not there, Stat searches in the second location, and so on. For each type of file that you plan to archive from or migrate to a particular environment, you must define at least one source file location.

To define source file locations by environment, select the environment in the Generic Application Environment Connection Maintenance window and click File Locations. This opens the Stat File Locations window, which displays a list of all the active generic application file types defined in Stat. For each file type, you can specify as many source file locations as you want. Source files can be located on different servers, or they can be on the same server but in different directories.


	NOTE: You can also specify source file locations by file type. For more information, see Object Type Maintenance .

To define source file locations for an environment:

Click New.

In the File Type field, select the file type for which you want to define a location.

Stat assigns a unique ID number to each file location you define per file type and displays the number in the Path ID field. This number determines the order that the file location is searched during the file archive process. The path with the ID 1 is searched first, and so on.

In the File Server field, select the server that the file directory is on.

In the File Path field enter the path of the file location starting after the predefined server's root or home path.

(Optional) Select Default Path if you want this to be the file type’s default source file location.

This is where Stat will copy file objects of the selected type during a migration. Each file type must have one of its source file locations designated as the default.

Click Test Connections.

See the section, Testing File Locations, Servers, and Default Directory Locations for more information.

Define additional file locations as needed. Then save your changes by clicking either Apply or OK.

Setting Up Migration Approval Lists

If an environment requires the approval of certain users before an archive set can be migrated into it, you can specify who these users are in the Migration Approval List tab. To open this window, select the environment and click App Options in the Generic Application Connection Maintenance table. Stat activates this tab only if the Req. Migr. Approval option has been selected for the environment.

When setting up a migration approval list, you can include different approver groups, including individual users and entire user classes or a combination of the two. The approval of any user or user class that you add to a list can be either required or optional.

Approval requirements that involve multiple approver groups or that can be satisfied in more than one way are defined using AND and OR operators. As you add approver groups using AND and OR operators, Stat displays the list as a tree structure and in the form of a SQL statement at the bottom of the window.

For example, let’s say a migration to a particular environment in the Financial Services service domain can be approved in one of two ways:

•

By a certain user AND at least one user in the Administrator user class

•

By at least two users in the Fin Developer user class

In this case, your approval list would look like this:

To further illustrate, let’s say that the migration must be approved by:

•

Two users, one of whom is required

AND

•

At least one user in the Administrator user class OR at least two users in the Fin Developer user class.

In this case, the approval list would look like this:


	NOTE: Migration approval lists closely resemble status transfer approval lists and the procedures for defining them are much the same. For more information on migration approval lists, see Setting Up Transfer Approval Lists .

To set up a migration approval list:

Do one of the following:

•

Click AND if the approval of one or more approver groups are required

•

Click OR if the approval of one of two or more approver groups are required

The operator icon is added to the approval list diagram.

Click on the AND or OR operator icon you just added.


	TIP: The icon background appears blue when selected and changes to gray when other fields or action buttons are activated. As long as the background of the operator icon is blue or gray, then approver groups and other operators can be attached to the operator.

In the Service Domain field, select the service domain that you plan to associate the environment with in the Generic Application Migration Path Maintenance table.

In the Approver Type field, select the approver group you want to add to the list.

Options include User and User Class.

When adding approvers, be aware of the following:

•

Although you can add any user or class to an approval list, be aware that only users that have access to an environment and the selected service domain (as defined in the User Maintenance table) will be able to approve a migration into that environment or receive email notifications regarding their pending approval. If an approver does not have access to the environment, the migration cannot be approved until either the user is granted access to the environment or the migration’s approval requirements are overridden by another user with proper security rights. For this reason, it is recommended that you first verify users have access to a particular environment and service domain before adding them to an approval list.

•

Adding individual users to approval lists could create problems if those same users are later inactivated or have their service domain and environment access restricted. For this reason, it is recommended that you add user classes to approval lists rather than individual users whenever possible.

•

Users assigned to a migration approval list must have the user class rights to operate in the same change management module in which the migration takes place. Also, you can assign user class rights that enable users to migrate objects regardless of approval status and also to approve migrations on the behalf of other users.

In the Approver Name field, select the name of the user or user class you want to add.

In the Required field, select Required if the approval is required or Optional if it is not required.

The Required option means that the individual user and every member of the user class must approve the migration. Optional means that the individual user’s approval is not required, whereas for user classes, it means that the approval of only a specified minimum number of users within that class is required.

If you selected User Class in the Approver Type field and Optional in the Required field, specify the minimum number of users in that class who must approve the migration in the Number field.

Click Add.

The approver is added to the tree structure under its approver group label and the initial AND or OR operator. Required approvers are displayed in bold.

At this point, how you proceed depends on the different approver groups you want to add to the list and how you want to define the relationships between these groups using AND and OR operators.

(Optional) Do the following to add additional AND or OR operators to your approval list:

Depending on the relationship between approver groups in your list, select the operator icon to which you want to attach additional operators.

Click AND or OR.

Repeat as necessary to add more operator icons to the approval diagram.

(Optional) To add additional user classes, select the appropriate operator icon in the approval diagram and repeat steps 4 through 8.

When you the first add an individual user to an approval list, Stat automatically creates the ad hoc group “users” in the approval diagram and attaches it to the appropriate operator icon. All subsequent users you add to the list must belong to this group.


	TIP: In a scenario in which you want to create approval relationships between multiple user approver groups, you may consider adding users to new user classes or queues created expressly for this purpose.