ORACLE - DBA Tips Corner

DBA Tips Archive for Oracle

Installing Oracle9iAS Release 2 - (Linux)

by Jeff Hunter, Sr. Database Administrator

Introduction

Oracle9i Application Server (Oracle9iAS) offers the industry's fastest most complete and integrated J2EE-certified application server. Oracle9iAS has revolutionized the application server market by being the first to integrate all the technology required to develop and deploy e-business portals, transactional applications, and Web services into a single product.
Oracle9iAS provides the most productive development environment for developers to create Internet Applications including J2EE Applications, Web Services, Enterprise Portals, Wireless and Business Intelligence Applications. Its open and integration-ready architecture and standards compliance ensures that your Web applications can integrate with your IT environment, including legacy systems, the applications of your suppliers and partners, and Oracle and non-Oracle databases.
Oracle9iAS provides the most reliable platform to deploy Internet Applications including the fastest J2EE and Web Services environment, High Availability and Clustering Support, and complete, centralized Management and Security of all Oracle9iAS components.
Finally, Oracle9iAS Release 2 offers tight integration across the entire product, further lowering the total cost of ownership - the cost to purchase, operate, and manage the product - a distinct advantage over the major competitors, BEA and IBM.

Downloading Oracle9iAS

There are four types of Oracle9iAS installations, each providing a set of components. The install types are ordered; in that each contains Application Server Installations all of the components in the previous install type, plus additional components. The install types are:

J2EE and Web Cache
Provides a basic Web server that enables you to develop and deploy Java 2 Enterprise Edition (J2EE) applications, use J2EE and Simple Object Access Protocol (SOAP) based Web services, accelerate Web site performance, and manage your application server with a Web-based tool.

Portal and Wireless
Enables you to deploy enterprise portals and wireless applications. Includes all components available in the J2EE and Web Cache install type.

Business Intelligence and Forms
Enables you to analyze clickstream data, personalize applications, perform data analysis, generate Web-based reports, create Discoverer public connections, configure Discoverer viewer and Discoverer Portlet Provider, and use Forms-based applications. Includes all components available in the Portal and Wireless install type.

Unified Messaging
Enables you to integrate different types of messages into a single framework. Includes all of the components available in the Business Intelligence and Forms install type.

Component J2EE and Web
Cache Portal and
Wireless Business
Intelligence
and Forms Unified
Messaging

Oracle HTTP Server YES YES YES YES

Oracle9iAS Containers for J2EE YES YES YES YES

Oracle9iAS Web Cache YES YES YES YES

Oracle Enterprise Manager Web site YES YES YES YES

Oracle9iAS Portal no YES YES YES

Oracle9iAS Wireless no YES YES YES

Oracle9iAS Discoverer no no YES YES

Oracle9iAS Reports Services no no YES YES

Oracle9iAS Clickstream Intelligence no no YES YES

Oracle9iAS Forms Services no no YES YES

Oracle9iAS Personalization no no YES YES

Oracle9iAS Unified Messaging no no no YES

Infrastructure

Overview
An Oracle9iAS Infrastructure is a type of installation that provides centralized security and management services, configuration information, and data repositories for application server installations.
An infrastructure is installed into its own Oracle home and contains the following pieces:

Oracle9iAS Single Sign-On
This feature enables users to access multiple accounts and applications with a single username and password, and provides single sign-on service across your entire application server enterprise.

Oracle Internet Directory
This is an LDAP-compliant directory service that provides centralized storage of information about users, applications, and resources in your enterprise.

Metadata Repository
This is an Oracle9i Enterprise Edition database that contains schemas and business logic used by application server components and other pieces of the infrastructure.

Oracle Management Server (optional)
This is required if you would like to use Oracle Enterprise Manager Console, a Java-based interface for managing the application server instances, databases, and applications in your enterprise.

When is an Infrastructure Required?
An infrastructure is required for most install types. The one exception is a J2EE and Web Cache installation that is not intended to use Single Sign-On or clustering. Clustering is an operation that involves joining application server installations together to share configuration parameters and application deployment.
The following table summarizes the infrastructure requirements for application server install types. The infrastructure must be installed BEFORE any middle-tier application server installations that are going to use it.

Application Server Install Type Infrastructure Required?

J2EE and Web Cache (not using Oracle9iAS Single Sign-On or clustering) No

J2EE and Web Cache (using Oracle9iAS Single Sign-On or clustering) Yes

Portal and Wireless Yes

Business Intelligence and Forms Yes

Unified Messaging Yes

Infrastructure Requirements for Application Server Install Types
How Infrastructure Pieces Work Together
The pieces of an infrastructure work together as follows:

Oracle9iAS Single Sign-On stores user information in Oracle Internet Directory.
Oracle Internet Directory uses the metadata repository as its back-end database.
Oracle Management Server uses the metadata repository to store information

How Application Server Installations use an Infrastructure
Application server installations and their components use an infrastructure in the following ways:

Components and applications use the Single Sign-on service provided by Oracle9iAS Single Sign-On.
Application server installations and components store configuration information and user and group privileges in Oracle Internet Directory.
Components use schemas that reside in the metadata repository.

FIGURE: Relationship between pieces of the Infrastructure

Configuring an Application Server to use an Infrastructure
You can configure an application server installation to use an infrastructure at the following times:

During the installation of any application server install type. The Oracle Universal Installer guides you through this and it is required for all install types except J2EE and Web Cache.

After the installation of a J2EE and Web Cache install type. You can associate a J2EE and Web Cache install type with an infrastructure at any time if you want to use Single Sign-On or clustering.

The figure (above) shows the convention used throughout this book to depict an application server installation using an infrastructure. Note that the application server installation and the infrastructure are each installed into their own Oracle home and may reside on a single host or on separate hosts.

Order of Installation Components

When required to use an Infrastructure, ensure that it is installed and configured BEFORE installing the application server instance. In many cases, we will install the pieces of the infrastructure on a separate machine (Oracle Management Server, Oracle Internet Directory). Within the installer for the Infrastructure, there is an option to configure these pieces on a different server than you are installing the Infrastructure on.

Installing 9iAS Infrastructure

Pre Installation Tasks
Linux Distribution / Version
I was able to get Oracle9iAS installed on both RedHat 7.3 and RedHat 8.0. While the installation and link phase seemed to work properly with RedHat 8.0, the installation dialog boxes where having problems with the new windows manager to RedHat 8.0.
When installing RedHat Linux, ensure to install ALL components under the "Custom" menu of the installer.
Already Installed Oracle Internet Directory or Oracle Management Server?
The first thing to decide is weather you want to configure the Oracle Internet Directory (OID) and/or the Oracle Management Server (OMS) that is installed by default with 9iAS Infrastructure. In some cases, the company may already have an OID or OMS installation and will want to leverage that. This is possible when installing 9iAS Infrastructure.
Set environment variable LD_ASSUME_KERNEL "before" running the Oracle Universal Installer
Ensure that LD_ASSUME_KERNEL is set as follows in the environment for the user (i.e. oracle) performing the install of 9iAS:
LD_ASSUME_KERNEL=2.2.5
export LD_ASSUME_KERNEL
Swap Space
Ensure that you have at least 1G of swap configured before running the installer.
Network / Hostname Settings
You MUST have a fully qualified domain name (FQDN) specified for the installation to be successfully run. A typical example is as follows:
  IP_ADDRESS   FULLY_QUALIFIED_HOSTNAME   SHORT_NAME   ALIAS
i.e.
  192.168.1.100  cartman.iDevelopment.info  cartman  oracleinstall
If your hostname is not registered with a DNS, you can define them locally in the following file:
  /etc/hosts
You hostname must meet RFC compliancy (no special characters). Your machine must also have a static IP address. (Do not use DHCP). You hostname and IP address also CANNOT be changed after installation in 9iAS Release 2 (9.0.2).
Make note of the values you will be using for the installation of Oracle Infrastructure
The following values will be used for installing the Infrastructure.

Information My Default Values

ORACLE_HOME Name Ora9iASInfHome

ORACLE_HOME Path /u01/app/oracle/product/9IASINF

Available Products [x] Oracle9iAS Infrastructure 9.0.2.0.1

Create Instance Name Instance Name: InfrastructureInstance
ias_admin Password: manag3r

Oracle 9iAS Single Sign-On Server Host Name <machine_name>.<domain_name>
(i.e. cartman.iDevelopment.info)

Oracle 9iAS Single Sign-On Port Number 7777

Oracle Internet Directory Host Name <machine_name>.<domain_name>
(i.e. cartman.iDevelopment.info)

Oracle Internet Directory Port Number 389

Oracle Internet Directory Username orcladmin

Oracle Internet Directory Password welcome

Database Character Set [x] WE8ISO8859P1
Installing the Infrastructure
Installing the Infrastructure is nothing more than running the Oracle Universal Installer and answering several screens.
When installing the Infrastructure on RedHat Linux, here are some of the errors I encountered and how to resolve them:
Error Dialog early in Install Processes indicating "Cannot determine current process" !!!
This generally occurs when trying to re-install Oracle 9iAS on a UNIX system that has not been fully cleaned. The key file (emtab) that needs to be delete before attempting the install is:
/etc/emtab
LINKING FAILURE !!!
The Oracle9iAS installer will fail 64% into the link phase with the following error:

This is expected behavior on RedHat 7.2, 7.3 and 8.0. Leave the error dialog up (DO NOT "Ignore" this message) and perform the following tasks:
Open a console window to the server, and "cd" to the Oracle Home installation target location.

Ensure that the Oracle environment variable ORACLE_HOME is set to the proper directory for the 9iAS Infrastructure.

Use an editor to modify the file: $ORACLE_HOME/bin/genclntsh.
In this file, you will need to remove "-z defs" from the LD_SELF_CONTAINED assignment. This definition should be on or near line 147. Do this by commenting out the line as follows:
# LD_SELF_CONTAINED="-z defs"
After making this change, save and run the script $ORACLE_HOME/bin/genclntsh to create the required Oracle libraries.

Go back to the 9iAS OUI error window, and click on "Retry" button to continue.
Cause: <BUG:1843232>
Versions of ld prior to version 2.11 ignored the "-z defs" flag. ld version 2.11 and later have the ability to use this flag. Because of this the genclntsh script fails to produce the libclntsh.so library on a machine running ld > 2.11.
Oracle Universal Installer HANGS in "Tools Configuration" on "Oracle Net Configuration Assistant"
This indicates that the environment variable LD_ASSUME_KERNEL was not set properly before running the installer. Ensure that LD_ASSUME_KERNEL is set correctly BEFORE starting the Oracle Universal Installer as following:
LD_ASSUME_KERNEL=2.2.5
export LD_ASSUME_KERNEL
ORA-01503: CREATE CONTROLFILE failed Error !!!
During the Configuration Tools, the installer will fail while trying to create the control file in the "Oracle Database Configuration Assistant".

This error is because the orapw file is missing so it can't actually create the control files.
The way to fix it is
cd $ORACLE_HOME/dbs 
orapwd file=orapwiasdb password=change_on_install
I was able to hit the "Ignore" button and successfully complete the Database Configuration Assistant. I have heard from others though that you need to do this before the dbca process starts to create and start the instance.
Oracle Universal Installer FAILS in "Tools Configuration" on "Oracle Internet Directory Configuration Assistant"
You will need to bring up the TNS listener BEFORE this process starts. You should do it when the Database Configuration Assistant is running.
This generally occurs when trying to re-install Oracle 9iAS on a UNIX system that has not been fully cleaned. The key directory (/var/tmp) needs to be clean since Oracle needs to create several pipes for the OID Configuration Assistant:
cd /var/tmp
rm -rf
After installing the Oracle 9iAS Product Set for the 9iAS Infrastructure, the Universal Installer will perform several component configurations as part of it Configuration Tools screen. No user interaction is required here, but closely watch the configuration process for any failures. The following is a list of the components that will be configured.

Applying RDBMS Bundled Patch
Oracle Net Configuration Assistant
HTTP Server Configuration Assistant
Java Security Configuration Assistant
OC4J Configuration Assistant
Clickstream Collector Agent Configuration Assistant
BC4J Configuration Assistant
Oracle Database Configuration Assistant
Internet Directory Configuration Assistant
Infrastructure Schema Configuration Assistant
Infrastructure Instance Configuration Assistant
Oracle9i Application Server randomize Password
Oracle9iAS Instance Configuration Assistant
Single Sign-On Configuration Assistant
Infrastructure mod_osso Configuration Assistant
OC4J Instance Configuration Assistant
OPMN Configuration Assistant - start OPMN
OPMN Configuration Assistant - start HTTP Server
OPMN Configuration Assistant - start DAS Instance
Enterprise Manager Web Site Configuration Assistant
DCM Repository Backup Assistant

End of Installation Phase
After successfully installing 9iAS Infrastructure, the Oracle Universal Installer will present URL and port numbers for accessing the Oracle HTTP Server page and the Oracle Enterprise Manager Web site. The default Oracle HTTP Server page is the Oracle9iAS Welcome page. The Oracle9iAS Welcome page provides links to demonstrations and information about new features.
The following is a sample listing from this screen.
The following information is available in:
  /u01/app/oracle/product/9IASINF/Apache/Apache/setupinfo.txt
  -----------------------------------------
  The HTTP Server can be accessed using the following URLs:

  http://cartman.iDevelopment.info:7777

  https://cartman.iDevelopment.info:4443

  -----------------------------------------
  The Enterprise Manager console can be accessed using the following URL:
  http://cartman.iDevelopment.info:1810
Finding Detailed Error Messages
If there were any failures during the configuration stage, you can view the following log file for installation details:
  /u01/app/oracle/oraInventory/logs/installAction[todays_date_time].log
Testing the Infrastructure
After all installation tasks are complete, you should test the Infrastructure to ensure it is running correctly. To do this, do the following:
Bring up Infrastructure Components
Bring up the components of your Infrastructure installation. The Windows commands are listed in the Oracle9i Application Server Administrator's Guide titled 'Starting an Infrastructure Using Commands in Windows'.
NOTE: The J2EE and Web Cache Instance included in the Infrastructure install is NOT configured for custom applications and there contains components that are not configured to run. When you start an infrastructure, you do not need to start these components:

OC4J_Demos: This OC4J instance is only required if you want to run demos.
OC4J_home: This OC4J instance is not required because customer applications ARE NOT deployed in the Infrastructure install.
BC4J: This component is disabled for use in any Infrastructure instance.
Clickstream Collector: This component is disabled for use in any Infrastructure instance.

Verify accessibility to Websites
Verify accessibility to the EM Website, SSO, OIDDAS. In order to do this, use the following URLs for your Infrastructure machine:
EM Website:
  http://<hostname.domain><:port>  (port 1810 by default)

  Example:
  http://cartman.iDevelopment.info:1810

  Login as:
  ias_admin / <your entered password during install>
9iAS Application Server:
  http://<hostname.domain><:port>  (port 7777 by default)

  Example:
  http://cartman.iDevelopment.info:7777

  Login as:
  No login required.
SSO Login Page:
  http://<hostname.domain><:port>/pls/orasso

  Example:
  http://cartman.iDevelopment.info:7777/pls/orasso

  Login using the orcladmin user and the ias_admin password.
  The port will be the HTTP Server port of your Infrastructure. (i.e. 7777)
OID_DAS Page:
  http://<hostname.domain><:port>/oiddas

  Example:
  http://cartman.iDevelopment.info:7777/oiddas

  Login using the orcladmin user and the ias_admin password.
  The port will be the HTTP Server port of your Infrastructure. (i.e. 7777)
Verify accessibility to Oracle Management Server (optional)
Bring up the Oracle Enterprise Manager Console and login to the Oracle Management Server that was configured (if it was configured at all) on the Infrastructure machine.
Default login information:
  Administrator: sysman
  Password:  oem_temp
NOTE: You will be required to change the default password for sysman before continuing.
Post Installation
Change the SYS and SYSTEM Password
Following installation of Oracle 9iAS Metadata Repository, you should change the SYS and SYSTEM passwords.
Renaming or Relocating the Oracle9iAS Metadata Repository Data Files
You will probably want to rename and relocate the data files created for the Metadata Repository to conform to your OFA standards. (Oracle's typical, DO AS WE SAY, NOT AS WE DO).

Installing 9iAS Application Server

Pre Installation Tasks
Already installed Oracle 9iAS Infrastructure?
A working 9iAS Infrastructure is required to be installed and configured before installing the 9iAS Application Server portion. The 9iAS Infrastructure and 9iAS Application Server can coexist on the same database server provided there are installed in separate ORACLE_HOME directories.
Swap Space
Ensure that you have at least 1G of swap configured before running the installer.
Network / Hostname Settings
You MUST have a fully qualified domain name (FQDN) specified for the installation to be successfully run. A typical example is as follows:
  IP_ADDRESS   FULLY_QUALIFIED_HOSTNAME   SHORT_NAME   ALIAS
i.e.
  192.168.1.100  cartman.iDevelopment.info  cartman  oracleinstall
If your hostname is not registered with a DNS, you can define them locally in the following file:
  /etc/hosts
You hostname must meet RFC compliancy (no special characters). Your machine must also have a static IP address. (Do not use DHCP). You hostname and IP address also CANNOT be changed after installation in 9iAS Release 2 (9.0.2).
Shutdown the Oracle Enterprise Management Website (optional)
If you are installing the Oracle9iAS Application Server on the same machine as the 9iAS Infrastructure, you will need to ensure that the Oracle Enterprise Management Website is shutdown before installing the Application Server. If this is not done, a "Warning" dialog will show during the install, giving you a chance to shut it down.
  % emctl stop
  Enter Management password: manag3r
Make note of the values you will be using for the installation of Oracle9iAS Application Server
The following values will be used for installing the Oracle9iAS Application Server.

Information My Default Values

ORACLE_HOME Name Ora9iASAppsHome

ORACLE_HOME Path /u01/app/oracle/product/9IASAPP

Available Products [x] Oracle9i Application Server 9.0.2.0.1

Installation Types [x] Business Intelligence and Forms (2.74GB)

Component Configuration (I generally select all available components)
[x] Oracle9iAS Portal
[x] Oracle9iAS Wireless
[x] Oracle9iAS Clickstream Intelligence
[x] Oracle9iAS Discoverer
[x] Oracle9iAS Personalization
[x] Oracle9iAS Reports Services
[x] Oracle9iAS Forms Services

Existing Oracle9iAS Single Sign-On (Where you installed the 9iAS Infrastructure)
Host Name: cartman.iDevelopment.info
Port: 7777

Oracle Internet Directory (Where you installed the 9iAS Infrastructure)
Host Name: cartman.iDevelopment.info
Port: 4032
Username: cn=orcladmin
Password: manag3r

Create Instance Name Instance Name: Apps1Instance
ias_admin Password: manag3r

Provide Outgoing Mail Server Information cartman.iDevelopment.info
Installing the Application Server
Installing the Oracle9iAS Application Server is nothing more than running the Oracle Universal Installer and answering several screens. Use the above table for answering the screens.
After installing the Oracle 9iAS Product Set for the Application Server, the Universal Installer will perform several component configurations as part of it Configuration Tools screen. No user interaction is required here, but closely watch the configuration process for any failures. The following is a list of the components that will be configured.

Applying RDBMS Bundled Patch
Java Security Configuration Assistant
Oracle Net Configuration Assistant
HTTP Server Configuration Assistant
Oracle9iAS Web Cache Assistant
Infrastructure Use Configuration Assistant
Clickstream Collector Agent Configuration Assistant
Personalization Configuration Assistant
BC4J Configuration Assistant
OC4J Configuration Assistant
Oracle9iAS Instance Configuration Assistant
Reports Configuration Assistant
Forms Configuration Assistant
Portal Configuration Assistant
Discoverer Configuration Assistant
Clickstream Configuration Assistant
Wireless Configuration Assistant
OC4J Instance Configuration Assistant
OPMN Configuration Assistant

End of Installation Phase
After successfully installing 9iAS Application Server, the Oracle Universal Installer will present URL and port numbers for accessing the Oracle HTTP Server page and the Oracle Enterprise Manager Web site. The default Oracle HTTP Server page is the Oracle9iAS Welcome page. The Oracle9iAS Welcome page provides links to demonstrations and information about new features.
The following is a sample listing from this screen.
  The following information is available in:
  /u01/app/oracle/product/9IASAPP/Apache/Apache/setupinfo.txt

  -----------------------------------------

  The HTTP Server can be accessed using the following URLs:

  http://cartman.iDevelopment.info:7778https://cartman.iDevelopment.info:4444

  -----------------------------------------

  The Enterprise Manager console can be accessed using the following URL:
  http://cartman.iDevelopment.info:1810
Finding Detailed Error Messages
If there were any failures during the configuration stage, you can view the following log file for installation details:
  /u01/app/oracle/oraInventory/logs/installAction[todays_date_time].log
Testing the Application Server
After all installation tasks are complete, you should test the Application Server to ensure it is running correctly. To do this, do the following:
Under Construction
Post Installation
Under Construction

Accessing Enterprise Manager Web Site

The HTTP Server can be accessed using the following URLs:
  http://JeffreyH2.comanage.net:7778
  https://JeffreyH2.comanage.net:4443
The Enterprise Manager console can be accessed using the following URL:
  http://JeffreyH2.comanage.net:1810
User ID: ias_admin
Password: manag3r

Component Port Numbers

Component Port Number

Enterprise Manager Reporting port 3339

Enterprise Manager Repository port 1521

Enterprise Manager Servlet port 1810

Java Object Cache port 7000

Oracle HTTP Server Jserv port 8007

Oracle HTTP Server SSL listen port 4443

Oracle HTTP Server SSL port 4443

Oracle HTTP Server listen port 7777

Oracle HTTP Server port 7777

Oracle Intelligent Agent 1748, 1754, 1808, 1809

Oracle Internet Directory (SSL) 636

Oracle Internet Directory (non-SSL) 389

Oracle Net Listener 1521

Oracle Notification Service local port 6100

Oracle Notification Service remote port 6200

Oracle Notification Service request port 6003

Oracle9iAS Clickstream Collector Agent 6667

Oracle9iAS Web Cache Admin port 4000

Oracle9iAS Web Cache HTTP Listen (SSL) port 4444

Oracle9iAS Web Cache HTTP Listen (non-SSL) port 7778

Oracle9iAS Web Cache Invalidation port 4001

Oracle9iAS Web Cache Statistics port 4002

Configuration Files

There's no single directory with all iAS configuration files. These files are distributed along several directories. This section is a list of all main iAS configuration files and where they are located.

Oracle HTTP Listener related (Apache)

Name Location Purpose

httpds.conf $ORACLE_HOME/Apache/Apache/conf Main Apache configuration file. HTTP listener's settings such as directory mappings, protection, SSL ports, hostnames & domains, etc.

oracle_apache.conf $ORACLE_HOME/Apache/Apache/conf Included in httpds.conf to bind other iAS configuration files. It contains Includes to other configuration files.

mime.types $ORACLE_HOME/Apache/Apache/conf Mapping between MIME types and file extensions. A MIME type instructs clients how to handle data that is sent by the server.

plsql.conf $ORACLE_HOME/Apache/moplsql/cfg Directives for mod_plsql, such as virtual paths handled by mod_plsql. This file is Included by oracle_apache.conf file.

wdbsvr.app $ORACLE_HOME/Apache/moplsql/cfg DAD definitions for mod_plsql.

xml.conf $ORACLE_HOME/Apache/xdk/admin Directives for xml, such as virtual paths pandled by the XSQL servlet. Included in oracle_apache.conf file.

Ojsp.conf $ORACLE_HOME/Apache/Ojsp/conf Directives for Oracle JSP, such as virtual hosts handled by Ojsp. Included in oracle_apache.conf file.

Developer Server related

Name Location Purpose

forms60_server $ORACLE_HOME/6iserver Shell script to start and stop forms server listener. It sets environment variables such as ORACLE_HOME, FORMS60_PATH, etc.

reports60_server $ORACLE_HOME/6iserver Shell script to start and stop reports MTS server. It sets environment variables such as ORACLE_HOME, FORMS60_PATH, etc.

6iserver.conf $ORACLE_HOME/6iserver/conf 6i configuration file for Apache listener. It is read when the Apache listener starts. Included in oracle_apache.conf file.

base.htm $ORACLE_HOME/6iserver/forms60/server Default base HTML file to run a form on the web using APPLET-style tags to include the Forms applet. Do not make changes on this file. Use formsweb.cfg instead.

basejini.htm $ORACLE_HOME/6iserver/forms60/server Default base HTML file to run a form on the web using JInitiator-style tags to include the Forms applet. Do not make changes on this file. Use formsweb.cfg instead.

formsweb.cfg $ORACLE_HOME/6iserver/forms60/server Parameter file used by Forms CGI. These parameters will replace the ones in base.htm or basejini.htm. Modify this file to tailor the html page used to start your forms applicationj.

Jserv related

Name Location Purpose

jserv.conf $ORACLE_HOME/Apache/Jserv/etc Directives for Jserve module. Included by httpds.conf

jserv.properties $ORACLE_HOME/Apache/Jserv/etc Main configuration file for Jserv engine. This file contains properties passed to the JVM and a list of servlet zones and their property files.

zone.properties $ORACLE_HOME/Apache/Jserv/etc Each servlet has his own properties file, known as zone.properties. The zone property file contains settings specific to a single servlet zone.

Starting and Stopping Application Server Components

Overview
The order in which to start the pieces of an application server enterprise is as follows:

Start the infrastructure
If your enterprise contains more than one infrastructure, start the primary infrastructure first.

Start customer database
If your enterprise contains customer databases, you can start them using several methods, including SQL*Plus and Oracle Enterprise Manager Console.

Start application server instances
You can start application server instances in any order. If instances are part of a cluster, start them as part of starting the cluster.

The order in which to stop the pieces of an application server enterprise is as follows:

Stop application server instances
You can stop application server instances in any order. If instances are part of a cluster, stop them as part of stopping the cluster.

Start customer database
If your enterprise contains customer databases, you can stop them using several methods, including SQL*Plus and Oracle Enterprise Manager Console.

Stop the infrastructure
If you enterprise contains more than one infrastructure, stop the primary infrastructure first.

Commands for Starting / Stopping Components

Component Action Command

Oracle HTTP Server Start ORACLE_HOME/dcm/bin/dcmctl start -ct ohs

Stop ORACLE_HOME/dcm/bin/dcmctl stop -ct ohs

Individual OC4J Instances Start ORACLE_HOME/dcm/bin/dcmctl start -co instance_name

Stop ORACLE_HOME/dcm/bin/dcmctl stop -co instance_name

All OC4J Instances Start ORACLE_HOME/dcm/bin/dcmctl start -ct oc4j

Stop ORACLE_HOME/dcm/bin/dcmctl stop -ct oc4j

Web Cache Start ORACLE_HOME/bin/webcachectl start

Stop ORACLE_HOME/bin/webcachectl stop

Discoverer Start ORACLE_HOME/discoverer902/util/startall.sh

Stop ORACLE_HOME/discoverer902/util/stopall.sh

Reports Start ORACLE_HOME/bin/rwserver.sh server=name

Stop ORACLE_HOME/bin/rwserver.sh server=name shutdown=yes

Starting / Stopping an Infrastructure
The following section provides the details and commands for starting and stopping the Oracle 9iAS Infrastructure using commands on UNIX.
An infrastructure contains several component instances that are not required to run an infrastructure and incur unnecessary system overhead if started. When you start an infrastructure, you do not need to start these components.

OC4J_Demos: This OC4J instances is only required if you want to run demos. This is obviously not necessary for an infrastructure install.
OC4J_home: This OC4J instance is not required because applications are not deployed to an infrastructure.
BC4J: This component in only used by OC4J_home and is not required if OC4J_home is not started.
Clickstream Collector: This instance is only required to collect Clickstream data and is not necessary since applications are not deployed to an infrastructure.

The following table shows the component statuses of a properly started infrastructure.

Component Name Status

BC4J

Clickstream Collector

HTTP Server

Internet Directory

OC4J_DAS

OC4J_Demos

OC4J_home

Single Sing-On: orasso:7777

Starting an Infrastructure using UNIX Commands
Make sure the following commands are run in the Oracle home of the infrastructure.
Start the metadata repository
  % ORACLE_SID=iasdb; export ORACLE_SID

  % lsnrctl start

  % sqlplus "/ as sysdba"
  SQL> startup open
  SQL> exit
Start Oracle Internet Directory
  % oidmon start

  % oidctl server=oidldapd configset=0 instance=1 start
Start Oracle HTTP Server
  % ORACLE_HOME/dcm/bin/dcmctl start -ct ohs
NOTE: It is possible for the dcmctl command to fail in starting/stopping the Oracle HTTP Server. The result of the command will be ADMN-100999. If this happens, perform the following:
Backup the file $ORACLE_HOME/config/ias.properties
Run the script in $ORACLE_HOME/bin
% resetiASpasswd.sh "cn=orcladmin" <your orcladminpassword> <OracleHome>
Example:
% resetiASpasswd.sh "cn=orcladmin" manag3r /u01/app/oracle/product/9IASINF
Retry the dcmctl command.
The cause of this problem is that the passwords are out of synch and this is caused by running dcmctl commands while the Enterprise Manager Web site.
Start the OC4J_DAS instance
  % ORACLE_HOME/dcm/bin/dcmctl start -co OC4J_DAS
Start Enterprise Manager Web site
  % emctl status

  % emctl start
Start Web Cache (optional)
  % webcachectl start
Start Oracle Management Server and Intelligent Agent (optional)
  % oemctl start oms

  % agentctl start agent
Stopping an Infrastructure using UNIX Commands
Make sure the following commands are run in the Oracle home of the infrastructure.
Stop all middle-tier application server instances that use the infrastructure
See next section
Stop Oracle Management Server and Intelligent Agent (optional)
  % oemctl stop oms

  % agentctl stop agent
Stop the Enterprise Manager Web site (for system shutdown only)
  % emctl stop
    [enter em password]
Stop Web Cache (optional)
  % webcachectl stop
Stop OC4J instances and Oracle HTTP Server
If you are preparing to shutdown your system, stop all running OC4J instances, Oracle HTTP Server, and OPMN as follows:
  % ORACLE_HOME/dcm/bin/dcmctl shutdown
(This can take some time)
Otherwise, if you are not preparing to shutdown your system, stop all running OC4J instance and Oracle HTTP Server (leaving OPMN running):
  % ORACLE_HOME/dcm/bin/dcmctl stop
Note that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On unavailable.
NOTE: It is possible for the dcmctl command to fail in starting/stopping the Oracle HTTP Server. The result of the command will be ADMN-100999. If this happens, perform the following:
Backup the file $ORACLE_HOME/config/ias.properties
Run the script in $ORACLE_HOME/bin
  % resetiASpasswd.sh "cn=orcladmin" <your orcladminpassword> <OracleHome>
Example:
  % resetiASpasswd.sh "cn=orcladmin" manag3r /u01/app/oracle/product/9IASINF
Retry the dcmctl command.
The cause of this problem is that the passwords are out of synch and this is caused by running dcmctl commands while the Enterprise Manager Web site.
Stop Oracle Internet Directory
  % oidctl server=oidldapd configset=0 instance=1 stop

  % oidmon stop
Stop the metadata repository
  % ORACLE_SID=iasdb; export ORACLE_SID

  % sqlplus "/ as sysdba"
  SQL> shutdown immediate
  SQL> exit

  % lsnrctl stop
Starting / Stopping an Application Server
Under Construction

Troubleshooting

IAS_ADMIN Password Does Not Work 1st Time
After installing Oracle 9iAS, you try to access the Oracle Enterprise Manager Web Site and the password for IAS_ADMIN does not work. You are sure that you are typing the password exactly how you entered it during the Oracle 9iAS installation. This is a known bug and easy to resolve. From the 9iAS ORACLE_HOME, simply run the emctl and supply the password again.
  % emctl
    

All articles, scripts and material located at the Internet address of http://www.idevelopment.info is the copyright of Jeffrey M. Hunter and is protected under copyright laws of the United States. This document may not be hosted on any other site without my express, prior, written permission. Application to host any of the material elsewhere can be made by contacting me at jhunter@idevelopment.info.

I have made every effort and taken great care in making sure that the material included on my web site is technically accurate, but I disclaim any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on it. I will in no case be liable for any monetary damages arising from such loss, damage or destruction.

Last modified on
Monday, 23-Jan-2006 09:02:41 EST
Page Count: 17351

Component	J2EE and Web Cache	Portal and Wireless	Business Intelligence and Forms	Unified Messaging
Oracle HTTP Server	YES	YES	YES	YES
Oracle9iAS Containers for J2EE	YES	YES	YES	YES
Oracle9iAS Web Cache	YES	YES	YES	YES
Oracle Enterprise Manager Web site	YES	YES	YES	YES
Oracle9iAS Portal	no	YES	YES	YES
Oracle9iAS Wireless	no	YES	YES	YES
Oracle9iAS Discoverer	no	no	YES	YES
Oracle9iAS Reports Services	no	no	YES	YES
Oracle9iAS Clickstream Intelligence	no	no	YES	YES
Oracle9iAS Forms Services	no	no	YES	YES
Oracle9iAS Personalization	no	no	YES	YES
Oracle9iAS Unified Messaging	no	no	no	YES

Application Server Install Type	Infrastructure Required?
J2EE and Web Cache (not using Oracle9iAS Single Sign-On or clustering)	No
J2EE and Web Cache (using Oracle9iAS Single Sign-On or clustering)	Yes
Portal and Wireless	Yes
Business Intelligence and Forms	Yes
Unified Messaging	Yes

Information	My Default Values
ORACLE_HOME Name	Ora9iASInfHome
ORACLE_HOME Path	/u01/app/oracle/product/9IASINF
Available Products	[x] Oracle9iAS Infrastructure 9.0.2.0.1
Create Instance Name	Instance Name: InfrastructureInstance ias_admin Password: manag3r
Oracle 9iAS Single Sign-On Server Host Name	<machine_name>.<domain_name> (i.e. cartman.iDevelopment.info)
Oracle 9iAS Single Sign-On Port Number	7777
Oracle Internet Directory Host Name	<machine_name>.<domain_name> (i.e. cartman.iDevelopment.info)
Oracle Internet Directory Port Number	389
Oracle Internet Directory Username	orcladmin
Oracle Internet Directory Password	welcome
Database Character Set	[x] WE8ISO8859P1

Component	Port Number
Enterprise Manager Reporting port	3339
Enterprise Manager Repository port	1521
Enterprise Manager Servlet port	1810
Java Object Cache port	7000
Oracle HTTP Server Jserv port	8007
Oracle HTTP Server SSL listen port	4443
Oracle HTTP Server SSL port	4443
Oracle HTTP Server listen port	7777
Oracle HTTP Server port	7777
Oracle Intelligent Agent	1748, 1754, 1808, 1809
Oracle Internet Directory (SSL)	636
Oracle Internet Directory (non-SSL)	389
Oracle Net Listener	1521
Oracle Notification Service local port	6100
Oracle Notification Service remote port	6200
Oracle Notification Service request port	6003
Oracle9iAS Clickstream Collector Agent	6667
Oracle9iAS Web Cache Admin port	4000
Oracle9iAS Web Cache HTTP Listen (SSL) port	4444
Oracle9iAS Web Cache HTTP Listen (non-SSL) port	7778
Oracle9iAS Web Cache Invalidation port	4001
Oracle9iAS Web Cache Statistics port	4002

Oracle HTTP Listener related (Apache)
Name	Location	Purpose
httpds.conf	$ORACLE_HOME/Apache/Apache/conf	Main Apache configuration file. HTTP listener's settings such as directory mappings, protection, SSL ports, hostnames & domains, etc.
oracle_apache.conf	$ORACLE_HOME/Apache/Apache/conf	Included in httpds.conf to bind other iAS configuration files. It contains Includes to other configuration files.
mime.types	$ORACLE_HOME/Apache/Apache/conf	Mapping between MIME types and file extensions. A MIME type instructs clients how to handle data that is sent by the server.
plsql.conf	$ORACLE_HOME/Apache/moplsql/cfg	Directives for mod_plsql, such as virtual paths handled by mod_plsql. This file is Included by oracle_apache.conf file.
wdbsvr.app	$ORACLE_HOME/Apache/moplsql/cfg	DAD definitions for mod_plsql.
xml.conf	$ORACLE_HOME/Apache/xdk/admin	Directives for xml, such as virtual paths pandled by the XSQL servlet. Included in oracle_apache.conf file.
Ojsp.conf	$ORACLE_HOME/Apache/Ojsp/conf	Directives for Oracle JSP, such as virtual hosts handled by Ojsp. Included in oracle_apache.conf file.
Developer Server related
Name	Location	Purpose
forms60_server	$ORACLE_HOME/6iserver	Shell script to start and stop forms server listener. It sets environment variables such as ORACLE_HOME, FORMS60_PATH, etc.
reports60_server	$ORACLE_HOME/6iserver	Shell script to start and stop reports MTS server. It sets environment variables such as ORACLE_HOME, FORMS60_PATH, etc.
6iserver.conf	$ORACLE_HOME/6iserver/conf	6i configuration file for Apache listener. It is read when the Apache listener starts. Included in oracle_apache.conf file.
base.htm	$ORACLE_HOME/6iserver/forms60/server	Default base HTML file to run a form on the web using APPLET-style tags to include the Forms applet. Do not make changes on this file. Use formsweb.cfg instead.
basejini.htm	$ORACLE_HOME/6iserver/forms60/server	Default base HTML file to run a form on the web using JInitiator-style tags to include the Forms applet. Do not make changes on this file. Use formsweb.cfg instead.
formsweb.cfg	$ORACLE_HOME/6iserver/forms60/server	Parameter file used by Forms CGI. These parameters will replace the ones in base.htm or basejini.htm. Modify this file to tailor the html page used to start your forms applicationj.
Jserv related
Name	Location	Purpose
jserv.conf	$ORACLE_HOME/Apache/Jserv/etc	Directives for Jserve module. Included by httpds.conf
jserv.properties	$ORACLE_HOME/Apache/Jserv/etc	Main configuration file for Jserv engine. This file contains properties passed to the JVM and a list of servlet zones and their property files.
zone.properties	$ORACLE_HOME/Apache/Jserv/etc	Each servlet has his own properties file, known as zone.properties. The zone property file contains settings specific to a single servlet zone.

Component	Action	Command
Oracle HTTP Server	Start	ORACLE_HOME/dcm/bin/dcmctl start -ct ohs
Oracle HTTP Server	Stop	ORACLE_HOME/dcm/bin/dcmctl stop -ct ohs
Individual OC4J Instances	Start	ORACLE_HOME/dcm/bin/dcmctl start -co instance_name
Individual OC4J Instances	Stop	ORACLE_HOME/dcm/bin/dcmctl stop -co instance_name
All OC4J Instances	Start	ORACLE_HOME/dcm/bin/dcmctl start -ct oc4j
All OC4J Instances	Stop	ORACLE_HOME/dcm/bin/dcmctl stop -ct oc4j
Web Cache	Start	ORACLE_HOME/bin/webcachectl start
Web Cache	Stop	ORACLE_HOME/bin/webcachectl stop
Discoverer	Start	ORACLE_HOME/discoverer902/util/startall.sh
Discoverer	Stop	ORACLE_HOME/discoverer902/util/stopall.sh
Reports	Start	ORACLE_HOME/bin/rwserver.sh server=name
Reports	Stop	ORACLE_HOME/bin/rwserver.sh server=name shutdown=yes

Component Name	Status
BC4J
Clickstream Collector
HTTP Server
Internet Directory
OC4J_DAS
OC4J_Demos
OC4J_home
Single Sing-On: orasso:7777