Oracle Applications DBA Blog

Managing Your 10g Application Server

After having discussed about installation and configuration of Oracle Applications Server, in today’s post I will talk about managing the application server primarily the startup and shutdown procedures. I am sure this would have been already well  documented by oracle but the post aims summing up the process. I will discuss the opmn tool by Oracle and also the Enterprise Manager

The process described here also holds good for other Oracle products like Oracle Collaboration suite and Oracle SOA suite.

Any application server would necessarily consist of a infrastructure Tier, it may or may not have a middle tier associated.

Starting Application Server Services

Order of Startup
As the middle tier is dependent on your infrastructure it is important that the infrastructure should be up and running  before you proceed with the middle tier services.

Using runstartupconsole.sh
You can start up the infrastructure tier services using the runstartupconsole.sh script located at your $ORACLE_HOME/bin/ on  the machine which contains your infrastructure.

# su - saminf
$ cd $ORACLE_HOME/bin
$runstartupconsole.sh start

This command will startup

The AS Meta Data Repository Instance
The Listener
The Enterprise Manager Console
Infrastructure Process Such as OID,OC4J_security,SSO etc.

To startup the middle Tier Services you log in to your middle tier OS user and run the the runstartupconsole.sh from the  middle tier ORACLE_HOME.

# su - sammid
$ cd $ORACLE_HOME/bin
$runstartupconsole.sh start

This Command will start up

The 10g Enterprise Manager
All OPMN managed process for the middle tier like portal

Using Enterprise Manager Console
You can also use the 10g Enterprise Manager console to start up the infrastructure tier and middle tier services, however you  must start up the enterprise manager explicitly before you can use it. The emctl command is used to startup the enterprise manager. The location is $ORACLE_HOME/bin

#su - saminf
$emctl start iasconsole

You can logon top the enterprise manager using the ias_admin username and password given at the time of installatiuon. You  can get the URL of the EM from the setupinfo.txt file located at the $ORACLE_HOME/install directory location.

Similarly you can start the EM of the middle Tier using the emctl command and start the middle tier services using the EM  console.

However you must start your Meta Data Repository instance and Listener manually before starting and using the EM console.

Using OPMN

OPMN stands for the Oracle Process Manager and Notification, is a tool with you can manage the OPMN managed Infrastructure  and Middle Tier Porcess. The opmnctl executable is located at the $ORACLE_HOME/opmn/bin.

opmnctl start
This command will start up your opmn process

opmnctl startall
This will start up the opmn process and all process managed by opmn

opmnctl startporc ias-component=component
This will start a specific opmn managed process like SSO
You can also start using the sub-porcess of a component using
opmnctl startproc process-type=process

You could also restart the processs using
opmnctl restartproc ias-component=component
opmnctl restartproc process-type=process

However before using OPMNCTL you must have started your Metadata Respositery Database Instance and the Listener manually.

Shutdown of Application Tier Services

Order Of Shutdown
Your Middle tier Services must be shutdown before you shutdown your infrastructure services.

Using runstartupconsole.sh
You can shutdown the infrastructure tier services using the runstartupconsole.sh script located at your $ORACLE_HOME/bin/ on the machine which contains your infrastructure.

# su - saminf
$ cd $ORACLE_HOME/bin
$runstartupconsole.sh stop

This command will stop
All infrastructure tier services
The 10g EM console
The meta data repository instance
The listener

For middle Tier services you must run this command for the middle tier ORACLE_HOME.

Using Enterprise Manager Console
You can also use the 10g EM console to shutdown your middle tier and infrastructure services.
After that you must shutdown your EM console manually using the emctl command

emctl stop iasconsole

You can also shutdown the Infrastructure services using the EM Console of the infrastructure tier after which you must manually shutdown the EM console manually using emctl at the infrastructure tier.

You must also remember to bring down your Meta Data Repository and Listener manually from the infrastructure home after all  the services are brought down.

Using OPMN
Using opmnctl you can shutdown your middle tier services and infrastructure services.

opmnctl shutdown
This shutdown the opmn process and along with it all the managed opmn processes

opmnctl stopall
This command stops all opmn managed process for a particular tier.

You can also stop a specify OPMN managed component using
opmnctl stopproc ias-component=component
or
opmnctl stopproc process-type=process

The EM console on the middle tier and the infrastructure tier needs to be brought down manually using emctl stop iasconsole.
Also the Meta Data Repository Instance and Listener need to be brought down manually.

Posted by Sam at 05:46 PM | Permalink | Comments (7) | TrackBacks (0)

Auditing In Oracle Applications

Auditing in any production application is required due to various statutory or security obligations. Oracle Applications, an ERP which is backbone of the Organization implementing  it, it becomes all the more indispensable. Auditing aims at detection, prevention as well as track down any change which requires further investigation.

In Oracle Applications auditing can be done at two levels

• Oracle Applications Users Level.
• Oracle Applications Database/Schema Level.

In addition to the above you could also enable the standard Oracle RDBMS audit feature using 
the SYS.AUD$ table. In the current post however we will talk about only the auting 
capabilities of Oracle Applications.

Oracle Applications User Auditing

Sign On Audit
In Oracle Applications user level auditing can be done by enabling the Sign Audit profile option. This option can either be set at the user level, responsibility level or the Form level. To enable this kind of auditing you must set a value for the system profile option Sign-On: Audit Level.



Based upon the level of Sign Auditing selected the System capture all or some of the 
following information.

• The users who sign on to the system
• The Sign in and Sign Out times
• Responsiblities they choose
• The forms they use
• Duration of using the form or responsibility
• Terminals used for sign on.

You can get this information from the system by running one of the standard Oracle  Applications reports which are

• Signon Audit Users
• Signon Audit Responsibilities
• Signon Audit Forms
• Signon Audit Concurrent Requests
• Signon Audit Unsuccessful Logins

Additionally you could also setup notifications for unsuccessful logins by setting the  Sign-On: Notification system profile option to YES.



You can also use the monitor users window to have a user level auditing. However you can view the information only of those users for whom sign on auditing has been enabled.



Oracle Applications Database/Schema Level

Oracle Applications also allows to track down changes made to the data in oracle applications. For this purpose Audit Trails are setup and used. The trails track the audited  table by creating a shadow table for each of the audited table. Internally this mechanism uses database triggers to populate the shadow tables. The Following steps are involved for  setting up a audit trail in oracle applications.

Define Audit Groups
The first step involves defining your audit group. An audit group is a set of tables and  columns that you wish to audit. You can choose either to enable auditing of all or some of the  columns of a table except LONG,RAW and LONG RAW. You could have multiple audit groups and a  same object can also be a part of different audit groups.

Define Audit Installations
In this stage you choose the registered ORACLE IDs that you wish to audit. Before you can 
define your audit installation you must have denied your audit groups.

Define Audit Table and Columns
After defining the audit groups and audit installations you can choose the tables and columns 
for which you wish to enable auditing. You can use the audit tables to do this.



Run the Audit Trail Update Tables Report
You must run a concurrent request Audit Trail Update Tables Report so that your audit trail  definitions and the required shadow tables are created. This report is also responsible for building database triggers for your audit installations.



Disabling Auditing
You can disable auditing at anytime by changing the audit group state through the Audit Groups 
window to either Disable - Interrupt Audit, Disable -  Prepare for Archive or Disable - Purge Table. You must run the Audit Trail Update Tables Report after making the selection.

Posted by Sam at 12:43 PM | Permalink | Comments (6) | TrackBacks (0)

Top 50 RAC-Related Acronyms

Couple of days ago i read Eddie Award’s Post on Top 50 SOA-Related Acronyms and found it very interesting. Lately i have been working on Oracle Applications RAC environments and realized that RAC had its own set of frequently used Acronyms. In this post I have put together my 'Top 50' of the RAC Acronyms. Some of these might be related to other technologies also but they find a place in this list as they also relate RAC and Oracle Applications.

• RAC (Real Application Clusters) Is Oracle Implementation of Clustered Database Instances.
• CRS (Cluster Ready Services) Oracle's own clusterware tightly coupled with Oracle Real Application Clusters (RAC).
• OCSF (Oracle Cluster File System) Oracle File system Implementation For Linux.
• PCP (Parallel Concurrent Processing) PCP allows concurrent processing activities to be distributed across multiple nodes in an RAC environment, maximizing throughput and providing resilience to node failure.
• OCR (Oracle Cluster Registry) The OCR contains cluster and database configuration information for RAC and Cluster Ready Services (CRS).
• ASM (Automatic Storage Management) Simplifies database administration by enabling you to create disk groups and manage them instead of individual datafiles.
• SSH (Secure Shell) SSH is a set of standards and an associated network protocol that allows establishing a secure channel between a local and a remote computer.
• RSH (Remote Shell) rsh (remote shell) is a command line computer program which can execute shell commands as another user, and on another computer across a computer network.
• DSA (Digital Signature Algorithm) The Digital Signature Algorithm (DSA) is a United States Federal Government standard or FIPS for digital signatures.
• SCSI (Small Computer System Interface) standard interface and command set for transferring data between devices commonly used for interfaces for hard disks, and USB and FireWire connections for external devices.
• NAS (Network-attached storage) Is a dedicated data storage technology that can be connected directly to a computer network to provide centralized data access and storage to heterogeneous network clients.
• NFS (Network Filesystem) is a protocol allows a user on a client computer to access files over a network as easily as if attached to its local disks.
• OSCP (Oracle Storage Compatibility Program) An Oracle Programe To assist third-parties with their Oracle compatibility with respect to storage devices.
• DTP (Distributed Transaction Processing) DTP model is the synchronization of any commits and rollbacks that are required to complete a distributed transaction request.
• VIP (virtual IP Address) is an IP address that is not connected to a specific computer or network interface card (NIC) on a computer.
• TCP/IP ( Transmission Control Protocol (TCP) and the Internet Protocol (IP)
• DNS (Domain Name Server) The domain name system is responsible for translating  it translates domain names (computer hostnames) to IP addresses.
• MAC (Media Access Control) Media Access Control address (MAC address) is a unique identifier attached to most network adapters.
• JDBC (Java Database Connectivity) A Java API that allows independent connectivity between the Java programming language and a wide range of databases.
• LB (Load Balancing) Is a technique to balance the load between configured servers.
• FAN (Fast Application Notification) enables end-to-end, lights-out recovery of applications and load balancing when a cluster configuration changes.
• FCF (Fast Connection Failover) Fast Connection Failover provides the ability to failover connections in the connection cache as quickly and efficiently as the database itself.
• TAF (Transparent Application Failover) Using transparent application recovery (TAF), Oracle can automatically reconnect users to the database in the case of instance or node failure.
• OCI (Oracle Call Interface) OCI allows you to develop applications that take advantage of the capabilites of SQL from within the application.
• ODP (Oracle Data Provider) ODP.NET features optimized data access to the Oracle database from a .NET environment.
• ONS (Oracle Names Server) Oracle Names makes network address and database link information available to all nodes throughout the network.
• ORION (Oracle I/O) ORION is a test tool freely available tool which simulates Oracle I/O.
• GSD (Global Services Daemon) The Global Services Daemon (GSD) background process allows usage of Oracle Enterprise Manager or the SRVCTL utility to perform system management tasks.
• NTP (Network Time Protocol) The Network Time Protocol (NTP) is a protocol for synchronizing the clocks of computer.
• CVU (Cluster Verification Utility) CVU is used to verify all the important components that need to be verified at different stages in a RAC environment.
• VSD (Virtual Shared Disk) A Virtual Shared Disk (VSD) facility is a layer of software that allows a processing node to access disk devices physically attached to a remote node as if those devices were attached locally.
• LPARs (Logical Partitions) a Logical Partition, commonly called an LPAR, is a virtualized computing environment abstracted from all physical devices.
• DBCA (Oracle Database Configuration Assistant) An Oracle utility that facilitates the creation and configuration of a database.
• ORACM (Oracle Cluster Manager) allows to add new nodes to an existing cluster without having to stop/start the whole cluster.
• RDA (Remote Diagnostic Agent) An Oracle Diagnostic Tool used in troubleshooting.
• GFS (Global Filesystem) GFS allows a cluster of Linux servers to share data in a common pool of storage.
• NIC (Network Interface Controller) is a piece of computer hardware designed to allow computers to communicate over a computer network.
• LVM (Logical Volume Manager)
• GPFS (General Parrel File System) GPFS is IBM’s high-performance parallel, scalable file system for IBM UNIX clusters.
• HA (High Avaliblity)
• MAA (Maximum Availability Architecture)
• RACDDT (RAC Data Collection Tool) is a data collection tool designed and configured specifically for gathering diagnostic data related to Oracle's Real Application Cluster (RAC) technology.
• OSW (OSWatcher) is an operating system diagnostic utility tool that gathers archival performance data using various native Unix utilities, such as vmstat, iostat and top.
• OLS (Oracle Label Security) Oracle Label Security is developed based on virtual private database (VPD) technology and provides a flexible, fine-grained access control functionality that is achieved by comparing a sensitive label assigned to a piece of data with label authorizations assigned to an application user.
• RSM (Remote Shared Memory) is a feature that bypasses the UDP/IP communication in Solaris.
• UDP/IP (User Datagram Protocol) can send short messages sometimes known as datagrams to one another.
• TNS (Transparent Network Substrate) Allows peer-to-peer connectivity where no machine-level connectivity can occur.
• EMCA (Enterprise Manager Configuration Assistant) An Oracle tool to set up the Enterprise Manager.
• OPS (Oracle Parallel Server) The OPS option allows multiple instances on different computer systems (nodes) can access the same database files simultaneously.
• SRVCTL (Server Control) A utility to assist in administration and maintenance of RAC databases.

Hope you enjoyed reading them as much as I did compiling them ;)

Posted by Sam at 04:03 PM | Permalink | Comments (2) | TrackBacks (0)

Oracle SOA Suite

SOA or Service Oriented Architecture allows organizations to reduce the complexity within there IT Architecture by adopting modular standards such as web services that are adaptable and flexible. The Service Oriented Architecture aims at achieving interoperability between various prosperity software that the organization might use. The SOA makes use of web service standards like Web Services Description Language (WSDL), extensible markup language (XML), and Simple Object Access Protocol (SOAP).

Oracle provides an SOA Suite provides the necessary infrastructure that enables you to create, deploy and managed these SOA complaint Web services.

The main components of the Oracle SOA Suite are

• Integrated Service Environment which includes Oracle JDeveloper,Oracle Application Framework and Oracle Toplink.
• Oracle BPEL Process Manager
• Oracle Enterprise Service Bus
• Oracle Business Rules
• Oracle Business Monitoring
• Oracle Web Services Manager
• Oracle Application Server 10g Rel 3

Installing SOA Suite

The Oracle SOA suite needs an 10g infrastructure to which it can be integrated and installed. This can either be the  infrastructure that come with the 10g Application Server or the Oracle Collaboration Suite infrastructure.However to install SOA suite the database of the infrastructure must be at 10.1.5 or higher.

Pre Requisites

A 10g Application Server infrastructure installed

As mentioned earlier the SOA suite will be installed on a existing infrastructure, you must install a 10g infrastructure of  you already do not have one.

Upgrade Infrastructure Database

The infrastructure database that comes with Oracle Application Server or Oracle Collaboration Suite might be required to be  upgraded to 10.1.5 at least.

Create the required SOA schemas In The Database

The SOA suite requires the ORABPEL,ORAESB and ORAWSM schemas to be loaded into your  infrastructure database. The irca.sh script will create these schemas for you. You can find this script at install/soa_schemas/irca in your SOA Suite CD.Even if these schemas exist you must overwrite them in order for the SOA Suite to function properly.

Login to your infrastructure tier and execute this script after setting the environment.

$ ./irca.sh
Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
(c) Copyright 2006 Oracle Corporation. All rights reserved.
Enter database "host port serviceName" [localhost 1521 orcl]: samlx.appsdbablog.com 1521 samdb.appsdbablog.com
Enter sys password:
Running IRCA for all product(s):
 connection="samlx.appsdbablog.com 1521 samdb.appsdbablog.com", , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM
Validating database ...
Validating database character set ...
Running prerequisite checks for ORABPEL ...
WARNING: This script will overwrite the existing ORABPEL schema.
Do you wish to continue? (y/n) y
Enter password for ORABPEL:
Loading ORAESB schema (this may take a few minutes) ...
Running prerequisite checks for ORAESB ...
Enter password for ORAESB:
Loading ORAESB schema (this may take a few minutes) ...
Running prerequisite checks for ORAWSM ...
Enter password for ORAWSM:
Loading ORAWSM schema (this may take a few minutes) ...
INFO: ORABPEL schema contains 210 valid objects.
INFO: ORAESB schema contains 175 valid objects.
INFO: ORAWSM schema contains 90 valid objects.
IRCA completed.
Please check for any ERROR message above and also check the log file
irca2006-11-30_07-52-09PM.log for any error or other information.

Create OS User

Create a OS user through will the installation of SOA suite will happen.

$useradd -g dba -d /u02/orasoa orasoa

Starting The Installation

Login to the orasoa user and start the installer using the ./runInstaller command.



The first screen lets us choose between a basic installation and a advanced installation, we choose the advance installation option for more felxiblity.



The next screen presents us with the components of SOA suite which we wish to install, here we choose J2EE Server, Web Server and the SOA Suite option.



A pre installation check of the operating system is now carried out.



You must now provide a user with sys DBA privileges on your infrastructure database and the hostname for your infrastructure.



Now you must give the password for the schemas you created using the irca script.



Specify weather you want manual or automatic port selection.



Enter an instance name and the password for the OC4JADMIN super user.



In case you want this instance to be a part of the existing Application Server cluster, you must specify the details here.



The installer will now display the components that it will install and configure for you.

Posted by Sam at 04:58 PM | Permalink | Comments (1) | TrackBacks (0)

Sneak Preview Release 12

Much speculation about the release dates of Oracle Applications next major release which is Release 12 has been around, However there is still no conformation on the official dates for its release to the users. The beta code version though has been out for some time now.

The current post takes a sneak preview at Release 12 (Beta).
The post just meant to share the new look and feel in Release 12 and is NOT a installation post.

As expected Release 12 was to be real big in terms of disk space at least the vision demo instance.

This is how it ate up disk space on my server

Application Tier Files - 20GB
Database Binaries - 4.5 GB
Vision Demo Data Files - 81GB

The login screen is the one perhaps that has undergone most of the changes. It comes with a fresh cool blue look. Something which you will have to get used with this Release.

The Self Service Home Page does not seem to have changed much expect for the new color scheme and link to Oracle Diagnostics on it.

The Oracle Application Manager console also looked pretty much similar with almost the same links as with 11.5.10.2

Invoking the forms based applications, It prompts you to install the Java 2 Standard Edition on your PC. Yes the Jinitiator is now gone. The installation was quick and over was over in a few clicks.



The forms interface was almost undistinguishable from 11.5.10.2, maybe just the fonts and color again.



Though the User Interface did not undergo any major changes, the Oracle Applications File system has changed quite a bit.

APPSORA.env -> APPS<SID>.env

The APPSORA.env used to setup your E-Business environment has now been replaced by the APPS<SID>.env which in trun calls the
$ORA_CONFIG_HOME/10.1.2/$TWO_TASK.env
$APPL_CONFIG_HOME/$TWO_TASK.env

Instance Top
A new Instance Top has been introduced
INT_TOP=$HOME/inst/apps/<context_name>
One of the main advantages of having this is to get a clear distinction between the shared file system and the file system unique to an instance.

Other Newly Introduced Variables

AF_JLIB - This points to your $COMMON_TOP/java/lib

JAVA_BASE - This points at $COMMON_TOP/java/

Other Environment Variable Changes

JAVA_TOP- The JAVA_TOP now points to $COMMON_TOP/java/classes instead of $COMMON_TOP/java

OA_HTML -  The OA_HTML now points to $COMMOM_TOP/oacore/html instead of $COMMON_TOP/html

FND_SECURE - FND_SECURE now points at $INST_TOP/apps/fnd/12.0.0/secure/ as opposed to $FND_TOP/secure/<SID>/

Apart from this the machine admin scripts are now located at
$INST_TOP/admin/scripts/

Please do note that the official release of R12 is yet to be done and the final product released might be different from what has been talked about in the above post.

Posted by Sam at 02:56 PM | Permalink | Comments (7) | TrackBacks (0)

My Favorite Metalink Notes

I was recently plugged on to one of the podcasts by Steven Chan, in which he described his experiences on running his extremely popular blog on Oracle Applications Technology. An interesting observation pointed out here by Steven was that one of the principle driving object of his blog was that, the metalink which contained a wealth of information was still outside the internet search engine's indexing.

Since metalink does not allow the search engines to index its content due to understandable security concerns, There is a significant percentage of the Oracle Applications Community who Google. Obviously even if the information they are looking out  for is available it gets missed out form there search results.

By creating pointers or references to the metalink notes in his blog. It has enabled this information to have wider exposure  since his blog is obviously indexed by the search engines, so as the information contained within.

The current post is my bit of effort to carry out this task by listing out a few of my favorite Metalink Notes relating to Oracle Applications.

Please do remember you must have a valid metalink account to access these notes. Also the notes are copyrighted by Oracle and a  great amount of time and effort has been put into them, publishing or distributing them is not allowed and more importantly not rite!

Applications FAQ

• Note Id:285267.1 Oracle E-Business Suite 11i and Database FAQ
• Note Id:177610.1 Oracle Forms in Applications FAQ

Cloning

• Note Id:216664.1 FAQ: Cloning Oracle Applications Release 11i
• Note Id:230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
• Note Id:364565.1 Troubleshooting RapidClone issues with Oracle Applications 11i
• Note Id:398619.1 Clone Oracle Applications 11i using Oracle Application Manager (OAM Clone)

Oracle Applications with Oracle Application Server

• Note Id:186981.1 Oracle Application Server with Oracle E-Business Suite Release 11i FAQ
• Note Id:233436.1 Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
• Note Id:295606.1 Oracle Application Server 10g with Oracle E-Business Suite Release 11i Troubleshooting

Autoconfig

• Note Id:218089.1 Autoconfig FAQ
• Note Id:315674.1 How To Verify if Autoconfig is Enabled on 11.5.x
• Note Id:165195.1 Using AutoConfig to Manage System Configurations with Oracle Applications 11i
• Note Id:341322.1 How to change the hostname of an Applications Tier using AutoConfig
• Note Id:270519.1 Customizing an AutoConfig Environment

Oracle Applications and Database

• Note Id:362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)

Oracle Applications And RAC

• Note Id:220970.1 RAC: Frequently Asked Questions
• Note Id:294652.1 E-Business Suite 11i on RAC : Configuring Database Load balancing & Failover
  
• Note Id:312731.1 Configuring Oracle Applications Release 11i with 10g RAC and 10g ASM

DMZ with Oracle Applications

• Note Id:287176.1 DMZ Configuration with Oracle E-Business Suite 11i
• Note Id:377856.1 DMZ Reverse Proxy and Middle Tier In Different Domains

• Note Id:123718.1 11i: A Guide to Understanding and Implementing SSL for Oracle Applications
• Note Id:340178.1 Enabling SSL with Oracle Application Server 10g and the E-Business Suite

• Note Id:243880.1 Shared APPL_TOP FAQ
• Note Id:233428.1 Sharing the Application Tier File System in Oracle Applications 11i

Patching

• Note Id:174436.1 Oracle Applications Patching FAQ
• Note Id:224875.1 Installation, Patching & Upgrade Frequently Asked Questions (FAQ's)
• Note Id:139684.1 Oracle Applications Current Patchset Comparison Utility - patchsets.sh
• Note Id:374915.1 HRMS PATCH INSTALL FAQ
• Note Id:130608.1 ADPATCH BASICS
• Note Id:314540.1 What Log Files are Generated with Adpatch, and Where are They Located?
• Note Id:229423.1 Troubleshooting adpatch complaining of apps.zip existence issues
• Note Id:136342.1 How To Apply a Patch in a Multi-Server Environment

Concurrent Managers

• Note Id:69336.1 Basic information about Concurrent Managers
• Note Id:105133.1 Concurrent Manager Questions and Answers Relating to Generic Platform
• Note Id:241370.1 Concurrent Manager Setup and Configuration Requirements in an 11i RAC Environment
• Note Id:210062.1 Generic Service Management (GSM) in Oracle Applications 11i

• Note Id:189487.1 System Administration FAQ's

Troubleshooting

• Note Id:342332.1 Troubleshooting Login Problems in Oracle Applications 11i (11.5.2 – 11.5.10+)
• Note Id:104531.1 Troubleshooting (Report Review Agent)

Portal with Oracle Applications

• Note Id:305918.1 Using Oracle Portal 10g with Oracle E-Business Suite 11i

Single Sign-On with Oracle Applications

• Note Id:233436.1 Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
  
• Note Id:114534.996 OFA Single Sign-on through Apps 11i
• Note Id:295606.1 Troubleshooting SSO with Oracle Applications

Posted by Sam at 08:16 PM | Permalink | Comments (6) | TrackBacks (0)

Installing Oracle Collaboration Suite

Few post ago i had discussed about the Oracle Collaboration suite, In today’s post i will discuss the installation of Oracle Collaboration Suite and Collaboration Applications.

System Environment
Operation System: Redhat Linux AS 4
Oracle Collaboration Suite Version: 10.1.2

Though we can install the Applications and the infrastructure for Oracle Collaboration Suite together for the ease of  management and understanding i had decided to go in for a separate installation.

Operating System Users
As a first set we will create two users one for holding the Infrastructure of Collaboration Suite and the other for holding  the collaboration suite middle tier applications.

# useradd -g dba -d /u03/ocsin ocsin
# useradd -g dba -d /u03/ocsmi ocsmi

Pre Requisite Checks

Memory requirement
The Oracle Collaboration Suite Both Infrastructure and Application would require a minimum of a 2 GB memory. You must make  sure of this.

grep MemTotal /proc/meminfo
MemTotal:      8312720 kB

Temp Space
Ensure you have at least 250 MB free space in your tmperory directory

# df -k /tmp

Swap Space.
Ensure that at least 1.5 GB of unused swap space is available before proceeding with the installation.

# free -m
             total       used       free     shared    buffers     cached
Mem:          8117       8084         33          0         23       7115
-/+ buffers/cache:        944       7173
Swap:         1601          0       1601

OS packages for Redhat AS 4
The following OS patches a higher version should exist on your Redhat system.

glibc-2.3.4-2.9
glibc-common-2.3.4-2.9
binutils-2.15.92.0.2-13
compat-db-4.1.25-9
compat-glibc-2.3.2-95.30
compat-libstdc++-296-2.96-132.7.2
compat-libstdc++-33-3.2.3-47.3
gcc-3.4.3-22.1
gcc-c++-3.4.3-22.1
libstdc++-3.4.3-22.1
libstdc++-devel-3.4.3-22.1
openmotif21-2.1.30-11.RHEL4.4
pdksh-5.2.14-30
setarch-1.6-1
make-3.80-5
gnome-libs-1.4.1.2.90-44.1
sysstat-5.0.5-1

Staring The Installation
We first start the infrastructure installation as the infrastructure user ocsin

#su - ocsin
$ ./runInstaller

The first screen you see presents you with two choices, a basic installation and an advanced installation, i chose the advanced installation as it gives you more flexibility in terms of your installation and products you choose.




In the next screen you specify the ORACLE_HOME for your OCS infrastructure



The next screen gives an options to install the infrastructure and Application together or Infrastructure Only or Applications only. I choose the infrastructure only option.



This screen allows us to choose the type of Collaboration Suite Infrastructure we want to install. The choices her are IM and OCS DB, just the OCS DB, Just IM and convert an existing DB into an OCS DB. I have selected IM and OCS DB here.



The installer now does a pre requisite check for before proceeding with the installation.



Since OCS can be installed with support for multiple languages, this screen allows us to choose the additional languages which we wish to install with OCS.



The OCS infrastructure like the 10g Application Server infrastructure uses the 1521 port for its listener, it is not allowed to change this at the time of installation. You can however choose to share the listener in case 1521 is used by another listener.



The next screen displays a list of services that the OUI will configure and start for you as a part of the installation.



This screen specifies the namespace that will be used for your Oracle Internet Directory, You can change this if you wish.



Now you can specify whether to have automatic port selection or change it. For static ports you require a staticports.ini file which must be specified at the time of starting your OUI



This screen allows you to create the password for the orclguest user.



In this screen you specify the name for your database and the location you want to place your data files.



Here you specify the password for your other oracle schemas.



In this screen you specify the instance name for you infrastructure database and the passwords for the super user.

This screen displays the components the OUI is going to start the installation with.

After this the installer will start the installation, at the end of the installation it will attempt to configure and start the components it has installed. This will lead to a successful completion of your infrastructure tier installation.

Middle Tier Installation

The middle tier installation will be carried out by the OS user ocsmi



At first screen again we select the advanced installtion option.



Now specify the ORACLE_HOME for your OCS Middle Tier.



Choose that you want to install OCS Application here on this screen.



As usaul the OUI will validate your system before carring out the installation.



Choose the OCS applications you would like to install,i choose evrything other than oracle mail and discussions.



In this screen give the hostname and port of your OID server which you installed as a part of your infrastructure installation.



Give the password for the orcladmin user of your OID.



Here you can specify the components you want to associate with the available OCS databases.



The seelcted OCS Applications require a SMTP server, here you must specify that server and port.



Choose a automatic port selection or a static port selection here.



Specify the instance name for your middle tier and the password for the super user in this screen.



Specify a host name for the calender services here



The OUI now displays a summary of the installation it is going to carry out.



The OUI now start the installation process



You must have root privilages on the system to execute the root.sh as a part of the isntallation.



The installer now starts configuring and starting the products you installed,this really is time consuming and you should take a break here.

If all goes well, you installation would be complete and the access information can be found in the supportinfo.txt file in your ORACLE_HOME/install directory.

Posted by Sam at 04:41 PM | Permalink | Comments (5) | TrackBacks (0)