Stat 6.1 - System Administration Guide

Generic Application Connection Maintenance

The GenApps Environment Connection Maintenance table defines the generic (non-PeopleSoft and non-Oracle Applications) application environments connected to Stat. The table closely resembles the connection maintenance tables for PeopleSoft and Oracle Applications, and many of the maintenance procedures are the same. Within the definition for each environment is the information Stat needs to connect to it.

Connection security for generic applications is controlled by the following user class rights:

•

Generic App. Connection - Add

•

Generic App. Connection - Edit

The GenApps Environment Connection Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | General | Generic Application Connect.


Value	Description
Active	If selected, indicates that this environment is available for selection
Environment Cd (Key Value)	A 1-10 character code which uniquely identifies the environment
Description (Required Value)	A 1-35 character description of the environment.
Data Obj Version	The version number of the generic application, as defined in the Data Objects Maintenance table. Select a value in this field only if you plan on using Stat to manage data objects within this environment.
Req. Migr. Approval	If selected, indicates that Archive sets cannot be migrated into the environment without migration approval
DBMS	Name of the APPS database account holder
Database Name	The name of the environment (database instance). Options include Oracle, Microsoft SQL Server, and N/A.
DB User ID (SQL Server Only)	The SQL Server user ID for the schema owner. The default is “sysadm.”
DB Password (SQL Server Only)	The password for the DB User ID
Database Server	The name of the database server housing the generic application repository. Format for this entry is DBMS-specific. NOTE: If the database is running on a SQL Server instance, the format must be “host name\instance name”
Srv Logon ID	The login ID used for Stat login to the environment. Not used by ODBC.
Server Password	The password associated with the Srv Logon ID
Host Name	Name of the machine hosting the database NOTE: Required value for the Stat Central Agent.
Service Name	For generic applications running on Oracle, the listener service of the database. Used by the Stat Central Agent to establish JDBC connections to the Oracle database. NOTE: Required value for the Stat Central Agent.
DB Listener Port	Port number for the database listener. NOTE: Required value for the Stat Central Agent.
Use Tns	For RAC Oracle databases, configures Stat to invoke TNS
Tns Entry	The full description as it appears in the tnsnames.ora file with no line breaks or carriage returns
Other Database Parameters	Additional environment-specific parameters, if needed
Unicode DB	If selected, indicates the database is Unicode
Last Update (Read Only)	The date and time this record was last updated
Update By (Read Only)	The user who last updated this record

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.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Stat 6.1 - System Administration Guide

Generic Application Connection Maintenance

Testing Environment Connections

Inactivating Generic Application Environments

Managing Source File Locations by Environment