Pre-requisites for Configuring a Database on an Amazon RDS Instance as the eG Database

The key pre-requisite that you need to fulfill here are outlined below:

1. First, determine the IP address / host name of the Amazon RDS instance that hosts the eG database. This is required because, when setting up the eG manager, you need to specify the Database Server Name / IP and the Database Server Port for the eG manager to communicate with. To figure this out, follow the steps detailed below:

   • Login to the AWS portal.

   • When Figure 2 appears, use the Search text box in it to search for the 'rds' service.

     

     Figure 1 : Searching for the Amazon RDS service

   • Once RDS appears in the search results (see Figure 3), select it by clicking on it.

   • Figure 2 will then appear. Select the Databases option from the left panel of Figure 3.

     

     Figure 2 : Selecting the Databases option from the left panel of the RDS Dashboard

   • Figure 3 will then appear, where you can view the details of the instance that hosts the eG database. Below the Summary section of Figure 3, you will find the Connectivity & security tab page open by default. Click on the Configuration tab page.

     

     Figure 3 : Viewing the details of the Amazon RDS instance that hosts the eG database

   • Figure 4 will then appear displaying the configuration of the Amazon RDS instance. Take a look at the Amazon Resource Name (ARN) of the instance. The text string that precedes the ':' (colon) in the ARN represents the host name of the RDS instance. This is the host name that you should provide when eG manager setup prompts you for a Database Server Name / IP .

     

     Figure 4 : Determining the host name of the Amazon RDS instance from the ARN

   • Now, let us proceed to ascertain the port number of the RDS instance. For that, click on the Connectivity & security tab page in Figure 4. Figure 5 will then appear.

     

     Figure 5 : Determining the port number of the Amazon RDS instance

   • The port number displayed under the Port parameter in Figure 5 should be specified as the Database Server Port during eG manager setup.

2. The eG manager requires a special database user account for storing measures in the eG database. The privileges that such a user account should possess differs according to the type of database on the Amazon RDS instance that is configured as the eG backend. In the case of a Microsoft SQL database on an Amazon RDS instance, refer to the Pre-requisites for Configuring an eG Database on a Microsoft SQL Server topic to know what privileges this user requires and how to configure such a user. In the case of an Oracle database on an Amazon RDS instance, refer to thePre-requisites for Configuring an eG Database on an Oracle Database Server topic to know what privileges this user account requires and how to configure this account.

3. Requirements 2 to 4 described in the thePre-requisites for Configuring an eG Database on an Oracle Database Server topic will apply to an Oracle eG database configured on an Amazon RDS instance as well.

   create tablespace egurkhadata01

   datafile ‘C:\Oracle\ORADATA\egurkha\eGurkhaData01.dbf’ size 10240M

   autoextend off extent management local autoallocate;

   create temporary tablespace egurkhatemp01

   tempfile ‘C:\Oracle\ORADATA\egurkha\eGurkhaTemp01.dbf’ size 512M

   autoextend off extent management local uniform;

4. Create rollback tablespaces and rollback segments as needed when configuring an Oracle database backend for the eG manager.

5. The usage of an Oracle backend for the eG manager also necessitates the resetting of the following Oracle initialization parameters.

   • The processes parameter should be set to a minimum of 100

   • The open_cursors parameter should be set to a minimum of 200.

   These parameters might have to be tuned further based on an increase in server load.