iSelfSchooling.com  Since 1999     References  |  Search more  | Oracle Syntax  | Free Online Oracle Training

    Home      .Services     Login       Start Learning     Certification      .                 .Share your BELIEF(s)...

 

. Online Accounting        .Copyright & User Agreement   |
    .Vision      .Biography     .Acknowledgement

.Contact Us      .Comments/Suggestions       Email2aFriend    |

 

Online Oracle Training for beginners and advanced - The most comprehensive Oracle tutorial

The authors do not guarantee or take any responsibility for the accuracy, or completeness of the information.

Advanced - Application Server

 

 

 

 

 

 

 

 

Lesson 03

"Heaven will be inherited by every man who has heaven in his soul."

-Henry Ward Beecher (1813-1887)

What are the OracleAS infrastructure components?

The OracleAS infrastructure components are grouped into two categories:

Identity Management components: it contains schemas for components such as Portal and Wireless

 

OracleAS Metadata Repository components: It is a consistent security model for all applications. It contains: 

a) Oracle Internet Directory 

b) OracleAS Delegated Administration Services 

c) Oracle Directory Integration and Provisioning 

d) OracleAS Certificate authority.

 

Oracle Application Server Topology

Client tier: PC, Cell phone, or PDA

Middle tier: HOST1- J2EE and WebCache, HOST2- Portal and wireless, HOST3- Portal and wireless, HOST4- BI Business Intelligence and forms, HOST5- etc.

Infrastructure: HOSTn- Single Sign On and OID, HOSTm- Metadata repository.

 

What is Oracle HTTP Server?

Oracle HTTP Server or OHS is an extension of the standard Apache distribution. It provides a robust and reliable Web server. You can access to FORMS, REPORTS, Discoverer, and Portal via the Web. You can access to Oracle stored procedures with a PL/SQL engine. It provides failover and supports J2EE (OC4J).

 

How to start and stop the HTTP Server manually:

The Oracle HTTP Server –OHS- is managed by the OPMN utility.

# cd $ORACLE_HOME/opmn/bin

# ./opmnctl startproc process-type=HTTP_Server -- starts the process

# ./opmnctl stopproc process-type=HTTP_Server -- stops the process

# ./opmnctl status – gives status information

 

List the name of all Oracle HTTP Server configuration files.

  • httpd.conf

  • mod_oc4j.conf

  • mime.types jsev.conf

  • oracle_appache.conf

  • aqxml.conf

  • moddav.conf

  • plsql.conf

  • ojsp.conf

  • xml.conf

How do you allow access from specific IP addresses or machine name?

Change your httpd.conf file to add the following lines:

<Location /server-status>

SetHandler server-status

Order deny,allow

Deny from all

Allow from xxx.xxx.xxx.xxx

</Location>

Configuring Directives and Virtual Hosts

 

What is directive?

Directives are files to use for configuring the server. For example, the web master of an Oracle HTTP Server contains more than 120 directives at his or her disposal for configuring the server. It contains container directives. The containers have opening and closing tag. Any directive that doesn’t appear within a container applies to the entire serve.

 

What is the <Directory> directive and how do you maintain it?

It is a group of directives that apply to the named directory and subdirectories.

Examples of how to maintain the <Directory> directive:

<Directory /> -- refers to the whole file system.

Options none

AllowOverride none

</Directory>

<Directory /home/myfiles/*> --refers to the myfiles subdirectory under home.

AllowOverride none

</Directory>

<DirectoryMatch “/u0[1-6]/”> --refers to directories that start with u0 and end with a number from 1 to 6

AllowOverride none

</Directory>

 

How to use IP-Based or Name-Based Virtual Hosts?

<VirtualHost 200.200.200.2 200.200.200.3>

DocumentRoot /usr/virtual/htdocs/home

ServerName www.iselfschooling.com </>

ErrorLog /usr/virtual/logs/error_log

</VirtualHost>

<VirtualHost www.iselfschooling.com>

DocumentRoot /usr/virtual/htdocs/home

ServerName www.iselfschooling.com </>

ErrorLog /usr/virtual/logs/error_log

</VirtualHost>