Use complex Oracle connection descriptors

For some topologies of the Oracle DBMS, for example Oracle Real Application Clusters (RAC), you might have to use complex Oracle Net connection descriptors. In that case, review the following steps.

1. Create the databases manually for the Application Center, the MobileFirst Server administration, and the MobileFirst project WAR file. This step is mandatory and cannot be performed with the Ant tasks or Server Configuration Tool. See the following links for instructions on how to create these databases.

   • For installing the Application Center, see Create the Oracle database for Application Center.

   • For installing the MobileFirst Server administration, see Create the Oracle database for MobileFirst Server administration.

   • For deploying the MobileFirst project WAR file, see Create the Oracle databases.

2. In IBM Installation Manager, or in the Server Configuration Tool, use a generic Oracle JDBC URL instead of the host name and port.

   Figure 1. Oracle Database Settings window

3. For Ant tasks, use the alternative attributes for the <oracle> element. See configuredatabase Ant task, table 19.

   The example files in Sample configuration files do not use the alternative attributes for the <oracle> element. If we use an example file, we modify the <oracle> elements in the file so they use the alternative attributes.

4. URL must be a URL for the Oracle thin driver. It must not include the user name and password, for example: jdbc:oracle:thin:@(DESCRIPTION= [Oracle Net connection descriptor]).

Parent topic: MobileFirst databases