The CLASSPATH for the Stat® Client must include one of the following directories to compare forms and form libraries:
• |
For Oracle E-Business Suite 11i: $ORACLE_HOME/forms60/java/f60jdapi.jar |
• |
For Oracle E-Business Suite R12: $ORACLE_HOME/forms/java/frmjdapi.jar |
The PATH must include $ORACLE_HOME/bin to compare reports. The version of Oracle Developer should be compatible with the version of objects being compared. For example, with Oracle E-Business Suite, Oracle Developer 6i should be used with at least patchset 15. Please note that the Forms Applet Jar Files component of the Oracle Forms product must be installed. This component is not included with the typical installation.
NOTE: In addition to configuring the Stat Client, Oracle E-Business Suite users must set up the Stat database to support the compare feature for developer objects in patches. For more information, see Oracle Object Compare Support: Stat Database (Oracle E-Business Suite Only). Also, for users who plan to compare form library files that have attached libraries, there are special configuration steps that must be performed. For more information, see Object Compare Support for Form Library Files. |
The new Stat® database needs to be configured with basic data before the installation can be verified. For the purposes of an installation, Stat database configuration includes adding the new databases to the Stat INI file and updating the System table with client specific information including the license code. See Edit the INI file.
The Stat® INI Editor is a GUI application designed to create new INI files and edit existing ones. The INI Editor displays all the database profile records contained in the Stat.ini file in an easy-to-read format. For more detailed instructions, see the Stat System Administration Guide, Chapter 2, Administrative Utilities.
• |
IMPORTANT: The stat.ini file may be hidden depending on the file security settings on your computer. |
The Database tab in the INI Editor lists the database(s) to which Stat can connect. From here you can edit an existing INI file entry or create a new one. The INI Editor helps edit a file by asking for the exact information it needs. For example, if the DSN field is not required for a particular database, that field is grayed out.
1 |
Select File | New. |
2 |
Select Edit | New Record. |
4 |
In the DBMS field, select a DBMS. |
5 |
Enter the STATLOGIN password in the Encrypted Login Password field, either by entering an encrypted password from another stat.ini file or by clicking Change Password and entering the STATLOGIN password. |
7 |
Select File | Save as, and specify a name for the INI file. |
8 |
Click Save. |
The following table contains general database connection settings for the Stat INI Editor. Each record in the Stat INI Editor represents a database in the INI file. For more general information on available DBMS settings, see any of the Environment Connection Maintenance sections in the Stat System Administration Guide, Chapter 4, General Maintenance Tables.
After configuring the Stat® database, the next step is to login to Stat for the first time using the special SYSTEM user account and to update the System Maintenance table. The System Maintenance table is where you define global operating parameters for your installed copy of Stat and verify your license. For more information, see the Stat System Administration Guide, Chapter 4, General Maintenance Tables.
CAUTION: The SYSTEM account is the only way to log into the Stat Client until other users are defined. When prompted for the initial password, enter a password that is easily remembered. A more secure password can be defined later. |
3 |
Select Maintenance | General | System Maintenance. |
4 |
In the General tab, enter the site name, address, phone number, etc. |
5 |
In the License tab, do the following to enter the Stat license key: |
b |
Test the key by clicking Verify. |
6 |
(Optional) Change the default Country on the Other Options tab. The default is USA. |
7 |
© ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center