Previous Topic: Installation DialogsNext Topic: Install Adapter Listeners


Install Additional Application Servers

To optimize performance for multi-tier environments, divide services onto several application servers.

Note: To ensure optimal performance with additional application servers, open the operating system Services dialogs, and clear or stop unnecessary components.

Component

Description

Adapter

Installs the Adapter services options (Text File, SQL, Manager, Expression Checker).

Adapter Listener

Installs the Adapter Listener.

Note: The Adapter Listener can be installed only once.

Alerts

Installs the Alert service.

Note: Do not install the Alert more than once.

Dashboard Engine

Installs the Dashboard Engine service.

Note: The Dashboard Engine service can be installed only once.

Log Server

Installs the Log Server service.

Penalty Writer

Installs the Penalty service.

PSL Writer

Installs one instance of the Calculation Engine service.

Report Scheduler

Installs the Report Scheduler service.

ACE Engine on JBoss Application Server

The JEE Application Server that runs the ACE2 Manager.

Tomcat 6

Apache Tomcat 6.0.32 Server

For more information, see http://tomcat.apache.org.

Oblisync on JBoss Application Server

Enables the Content Transfer feature to run.

ScriptHost

Installs the Script Host service.

Note: The Script Host can be installed only once.

Tasks Host

Installs the Task Host service.

Note: The Task Host can be installed only once.

Windows Server 2008 R2 Server Configuration

To configure installations on Windows Server 2008 R2, perform the following tasks on all servers that include an Application server or Web server component.

Follow these steps:

  1. When the installation wizard prompts you to restart, open a command prompt:
    1. Click Start, Run.
    2. Enter the following command in the Run window:
      C:\Windows\SysWOW64\cmd.exe
      

      The command prompt opens.

  2. Execute one of the following commands:
  3. Restart the server.

Configure a Multi-tier Environment

To use a multi-tier topology, configure the servers.

Follow these steps:

Application server and Web server

  1. verify that the local naming configuration file contains the service alias with the correct host name and port.

    Filename: $ORACLE_HOME\network\admin\TNSNAMES.ORA

    Default Port: 1521

    Example:

    OBLICORE =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = server12.ca.com)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = oblicore)
        )
      )
    

Web Server

  1. Start the Distributed Transaction Coordinator service.
  2. Start the World Wide Web Publishing service.
  3. Install and configure the Oracle client and the database connection configuration components correctly to establish a connection to the database through OLEDB.
    1. Install and configure TNSnames.ora on all servers.
    2. Install and configure Listener.ora on the Database server.

Database Server

  1. Verify that the listener configuration file is configured correctly and that the file recognizes the instance to be created.

    Filename: $ORACLE_HOME\network\admin\LISTENER.ORA

    Example:

    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = OBLICORE)
          (ORACLE_HOME = C:\app\Administrator\product\11.2.0\dbhome_1)
          (SID_NAME = oblicore)
        )
      )
    
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = server12.ca.com)(PORT = 1521))
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
        )
      )
    
  2. Open a command-prompt window, and run the following command:
    lsnrctl status 
    

    A list of services summary appears.

    Note: If the list does not appear, run the following command:

    lsnrctl start 
    

    A confirmation message appears.

  3. Verify that $ORACLE_HOME\network\admin\SQLNET.ORA contains the following line:
    SQLNET.AUTHENTICATION_SERVICES = (NTS)
    
  4. To test communication between the Oracle client and the Listener, rune the following command:
    Tnsping  <tns_entry_name>
    

    The system responds with "OK" followed by the response time.