Set up an Oracle Database Server

After completing the installation of the Application Server and Web Server, you will need to set up the Oracle Database Server. The steps mentioned in this section must be performed on the Oracle Server host and the Application Server host. 

To set up an Oracle database server: 

1. Provide all of the scripts in the %AGILIANCE_HOME%\Oracle directory on the application server to the Oracle database administrator.
2. Open your Oracle Server host. 
3. Open the command window and navigate to the ~\Database\Oracle directory. Run the following command:

   sqlplus system@<service_name> @agl_master.sql

   Stop the RV Tomcat, Connector Manager Tomcat, and Jasper Tomcat services before running the command or it will return an error.

4. Enter the Schema Owner name, Report User password, Schema User name, and Schema User password that appear in the command window upon executing the command above. If you don't own the responsibility of managing the Oracle Server, ask your organization's Oracle database administrator to run the command mentioned above.

5. Open your application server host. 

6. Go to the %AGILIANCE_HOME%\config directory, then open the agiliance.properties file using a text editor. 

7. Ensure the following properties are available for the Schema User and Schema owner:
   
   database.oracle.schema=<SCHEMA_USER> database.
oracle.username.encrypted=SchemaUserinEncryptedStringdata- base.oracle.
password.encrypted=SchemaUserPasswordinEncryptedString
   
   Uncomment the Schema User and comment the Schema Owner. Save the file.

8. Restart the Tomcat service. 

During the upgrade, the database points to the schema owner, so the SCHEMA_USER needs to be commented.

When setting up the Oracle Database, note the following points:

1. Schema Owner name cannot be blank.
2. Schema Owner name cannot be SYS or SYSTEM.
3. Schema Owner name is valid i.e. Schema owner exists.
4. Report User password cannot be blank.
5. Schema User name cannot be blank.
6. Schema User name cannot be same as Schema Owner.
7. Schema User name cannot be SYS or SYSTEM.
8. Schema User password cannot be blank.
9. Schema User is not already connected.
10. Report User is not already connected.