Solution:
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
1. Go to Maintenance | General | Generic Application Connects and click on New to define a connection.
You would need to define the environment code, description, DBMS, Database Name, DB User ID, Password, Hostname, service name, and db listener port.
After defining a generic application environment in the maintenance table, you can make sure that you have entered all the information correctly by clicking DB Test Connect.
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 a message stating "Error opening generic environment connection:" followed by a brief explanation of the error it encountered.
Note: The DB Test Connect button 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 SCA will log an error when the user attempts to archive or migrate objects to or from this environment.
2. Go to Maintenance | Domain-Specific | Generic Application Migration Path and click New and define the Migration Cd. You can give it any name. For example, you can call it GA for the Migration Cd. When defining migration paths, keep in mind the following considerations:
• Environments cannot be listed on the path more than once
• Environments cannot be skipped in a path. They must be consecutive.
• The environments defined as Base, Development, and Distribution must also appear on the path. It is not required that they appear in environments 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 overwrite 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 following table defines the fields (columns) in the Generic Application Migration Path Maintenance window.
3. Go to Maintenance | General | Object Types | File Servers tab and define the SFTP Server assuming that you haven’t done this part
4. In the Object Types tab | select Generic File Object from drop down list then click New and define the file type such as EAR, HTML, and JAVA.
5. After defining ex: HTML file type, click on the File Location button on the upper right hand corner
6. Click New and select generic apps from the environment cd drop down list.
7. Select the File server that the HTML file located at and make sure to specify the file path as well as doing the test connection afterward
8. You need to define a file location for all db that exist on your Generic Apps Migration Path. For example, if I have two databases on my generic apps migration path (GA and GO) then I would need to define the file path for both environments.
