How to change OAS port to 80???

If you are on a UNIX system and you are changing the Listen port to a number less than 1024, perform these steps before you change the Oracle HTTP Server Listen port.

By default, Oracle HTTP Server runs as a non-root user (the user that installed Oracle Application Server). On UNIX systems, if you change the Oracle HTTP Server Listen port number to a value less than 1024, you must enable Oracle HTTP Server to run as root, as follows:



execute the below command as root

cd ORACLE_HOME/Apache/Apache/bin
chown root .apachectl
chmod 6750 .apachectl

change the value of port and Listen in httpd.conf to 80 and restart the OAS as Oracle user.

For more information refer to the below link.http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/ports.htm#CIHJEEJH

How to assign 2 ports to the same website on the same server (OAS)

I recently have to assign 2 ports to same portal on the same OAS server.

Below is the example to do the same.

add the below entries according to ur requirement in httpd.conf

Listen 80
Listen 8080

NameVirtualHost 172.20.30.40:80
NameVirtualHost 172.20.30.40:8080


<VirtualHost 172.20.30.40:80>
ServerName www.example1.com
DocumentRoot /www/domain-80
</VirtualHost>

<VirtualHost 172.20.30.40:8080>
ServerName www.example1.com
DocumentRoot /www/domain-8080
</VirtualHost>

<VirtualHost 172.20.30.40:80>
ServerName www.example2.org
DocumentRoot /www/otherdomain-80
</VirtualHost>

<VirtualHost 172.20.30.40:8080>
ServerName www.example2.org
DocumentRoot /www/otherdomain-8080
</VirtualHost>

The above information have been collected from the below link
http://httpd.apache.org/docs/2.0/vhosts/examples.html

orcladmin password expired???

Beginning with OID version 9.0.4, the default value for Password Expiry Time is set to 5184000 (60 days). Unless you have changed the default password policies from the installation defaults, exactly 60 days from the date of installation all passwords will automatically expire. Furthermore, if you keep trying to login using the old password, there exists the possibility that you will exceed the max grace logins exceeded, and consequently the account becomes locked.

To clarify the fact that the superuser, cn=orcladmin ldapbind succeeds you need to understand the following:

1. There are 2 orcladmin accounts, the superuser account, cn=orcladmin and the REALM administrator cn=orcladmin. For example cn=orcladmin,cn=users,dc=oracle,dc-com.

2. The superuser account is hard coded and you cannot see it in the Oracle Directory Manager nor the Oracle Directory Services Manager in 11g.

3. When you login to OIDDAS the REALM administrator account is the one that is being used. Since this user account exists within the REALM it is also under control of the default password policies.

Solution:

Step 1. If the superuser, cn=orcladmin account is locked, use the oidpasswd utility to unlock the super user orcladmin account, for example:
$ oidpasswd connect=asdb unlock_su_acct=true

This unlocks the OID Super User account, cn=orcladmin ONLY. Do not confuse this account with the default realm cn=orcladmin,cn=users,dc=xxxxx,dc=yyyyy. Again, they are two separate accounts. After resetting the orcladmin super user account, you will still not be able to login to SSO using the orcladmin account until you complete all steps in this document. Do not reset any other account passwords at this time (on this step).

Step 2. Launch the Oracle Directory Manager Console (or the ODSM for 11g).

Pre-11g:
on Unix, type oidadmin at the unix prompt
on Windows, Start->Programs->Oracle - SID->Integrated Management Tools/Oracle Internet Directory

11g:
Open a browser to the Oracle Fusion Middleware Enterprise Manager.
Select the OID instance
Click the OID dropdown list in the right frame
Select Oracle Directory Services Manager

Step 3. Login as "cn=orcladmin" and navigate to Password Policy Management area.
Edit each of these and change the pwdmaxage to an appropriate value:
5184000 = 60 days (default)
7776000 = 90 days
10368000 = 120 days
15552000 = 180 days
31536000 = 1 year
999999999 = never expire

Note: Realm policies can be different than the root policy, so if in doubt change both policies the first time, then change the realm policy one to different values as desired.

Step 4. Launch Oracle Directory Manager (or ODSM if 11g as previously described) and navigate to Entry Management and the Users container under your default realm (for example:
cn=orcladmin,cn=users,dc=oracle,dc=com)
Reset the UserPassword field by entering a new value.

After you have changed the cn=orcladmin for the REALM, you should be able to login to SSO/OIDDAS and reset/change any user passwords that have expired or are locked.

Note: at 11g there is not SSO nor OIDDAS, but you can still use the ODSM to reset user passwords.

Pre-11g Only
Rerun the odisrvreg utility to reset the DIP randomly generated password, for example:
odisrvreg -D cn=orcladmin -w -p 3060
Already Registered...Updating DIS password...
DIS registration successful

If you are unsure of your OID Port, check $ORACLE_HOME/install/portlist.ini file, which shows the ports at install time.

The above information have been collected from metalink.oracle.com

How to change SSO Login page to Custom Login Page in Oracle Application server (OAS) ?

To change SSO Login page follow the below steps:

1) The Login page is a jsp file "login.jsp" which can be found in $INFRA_HOME/j2ee/OC4J_SECURITY/applications/sso/web/jsp, you can create your own login file say "my_login_page.jsp" and place it into that directory.

2) Then go to $INFRA_HOME/sso/conf and modify "policy.properties" file (backup the original one first). You have to find the line:
loginPageUrl = /sso/jsp/login.jsp

Replace "login.jsp" with your new login file name "my_login_page.jsp"
loginPageUrl = /sso/jsp/my_login_page.jsp

3) Restart OC4J_SECURITY and HTTP_Server

You can however customize more, check [chapter 12|http://download.oracle.com/docs/cd/B14099_19/idmanage.1012/b14078/custom.htm#i1015535] in the SSO Administration Guide (Creating Deployment-Specific Pages) for more options.

How to Change / Reset ias_admin Password???

— ias_admin is user required to use Enterprise Manager Web (aka Application Server Console - iASConsole) Site.

— ias_admin password is set during Installation of Oracle Application Server (902, 904, 10.1.2.X) or Oracle Identity Management (Infra Tier 10.1.4.X)

—ias_admin account is NOT stored in OID (Oracle Internet Directory), It is stored in XML file (JAZN-XML - Java AuthoriZatioN) (More on JAZN-XML & JAZN-LDAP coming soon..)


You can reset/change ias_admin password in following ways

1. Using Enterprise Manager (Application Server Control) Web Site
–Login to Instance Home Page
–Click on Preferences on top right
–In new screen, click on “Change Password” on left menu
–Enter current password and New Password

2. Using Command line tool
emctl set password <old_password> <new_password>
like
emctl set password welcome1 welcome2
(Here welcome1 is current ias_admin password and welcome2 is new password which you
wish to reset)


If you don’t know current ias_admin password then change it in configuration file

3. Change ias_admin password directly in configuration file
–Backup $ORACLE_HOME/sysman/j2ee/config/jazn-data.xml
–Search for entry like below

<user>
<name>ias_admin</name>
<credentials>{903}8QkQ/crno3lX0f3+67dj6WxW9KJMXaCu</credentials>
</user>

and Update new password (welcome1 like )

<user>
<name>ias_admin</name>
<credentials>!welcome1</credentials>
</user>

Note: ! (Exclamation Mark in front of password. This signifies that password is stored in clear text)

Managing Ports in Oracle Application Server (OAS)

The change of ports is required in Oracle Application Sever (OAS) is commonly required when doing any new Installation or reconfiguring the Installation. To change ports in Oracle Application Server (OAS) is a very difficult task and to be done very carefully.

Below is the link that i generally use whenever i require to change any port in Oracle Application Server (OAS).
Note: The below link applies to Oracle Application Server (OAS) 10g.

Managing Ports in Oracle Application Server (OAS)

If you have any queries/doubts, please leave a comment I'll reply ASAP.

Bulk Delete Users From Oracle Internet Directory (OID)

Using ldapsearch and ldapdelete commands to remove OID users

1. First, you need to know what is the directory tree of users that you want to perform the deletion on (s_UserContainerDN), source of subscriber DN.

2. Get all the user entries first using ldapsearch command and spool it to a file

$ ldapsearch -h [oid_hostname] -p [oid_ldap_port] -D "cn=orcladmin" -w [password] -s one -b "cn=Users,[source subscriber DN]" "(objectclass=orcluserv2)" "cn=*" > users.ldif
Example:

$ ldapsearch -h [oid_hostname] -p [oid_ldap_port] -D "cn=orcladmin" -w [password] -s one -b "cn=Users,dc=spain,dc=oracle,dc=com" "(objectclass=orcluserv2)" "cn=*" > users.ldif

3. Edit the spool output ldif file, users.ldif to remove entires which you want to preserve such as orcladmin,Portal and public. You may want to preserve the following seeded users:

cn=orcladmin,cn=Users,[source subscriber DN]
cn=ias_admin,cn=Users,[source subscriber DN]
cn=PUBLIC,cn=Users,[source subscriber DN]
cn=Portal<*>,cn=Users,[source subscriber DN]
cn=sample<*>,cn=Users,[source subscriber DN]
cn=synd<*>,cn=Users,[source subscriber DN]
cn=uddi<*>,cn=Users,[source subscriber DN]

(Note:Example above include users/entries that could be seeded by certain midtier installs, so they may or may not exist in a particular OID)

4. Use the ldapdelete command along with the edited output ldif file to delete all the users:

$ ldapdelete -h [oid_hostname] -p [oid_ldap_port] -D "cn=orcladmin" -w [password] -c -v -f users.ldif

deleting entry cn=UNCLE_SAM,cn=Users,dc=spain,dc=oracle,dc=com
entry removed
deleting entry cn=LARRY_ELISSON,cn=users,dc=spain,dc=oracle,dc=com
entry removed

Note:Before removing users remove the users from the users.ldif which you dont want to delete.

There is one more command which is given below which might be helpful in some cases.
ldapadd -h myhost -p 389 -D "cn=orcladmin" -w welcome -f users.ldif

Changing the ODS schema password in OAS!!!

OID Database Schema Owner

The Oracle Internet Directory runs on an Oracle database

and creates two database users: ODS and ODSCOMMON. ODS

is the schema owner that contains all of the database

objects (tables, views, objects, etc.) used for OID

functionality and directory storage. When the OID needs

to login to the database, it uses the ODS database

account which has a default password of ODS. You should

secure this database user account before putting the

LDAP directory into production.

1. Change the ODS password to the desired value, and

create the new wallet:

oidpasswd connect= change_oiddb_pwd=true

oidpasswd connect= create_wallet=true

2. Restart OID:

opmnctl stopproc process-type=OID

opmnctl status

opmnctl startproc process-type=OID


3. Change the password in Enterprise Manager:

1. Login to EM

2. Click Targets tab > Click All Targets tab

3. Find the Name reported in the emagent.trc file (e.g.,10_1_2_portoidd.libby.oracle.com_LDAP) > click on it

4. Click Monitoring Configuration at the bottom right

5. Enter:

Username = ods

Password =

Using the OID Database Password Utility


The DBA can change this password by using the OID

Database Password Utility (included with the OID

installation). The following example uses this utility

to change the database password for ODS:


# $ORACLE_HOME/bin/oidpasswd

current password: ods

new password: new_secret_password

confirm password: new_secret_password

password set.

How oidpasswd Works

The oidpasswd utility connects as the ODSCOMMON user and

uses the role ODS_SERVER with the original password to

perform the following:

1. Changes the password for the ODS user for the OID

schema database.

2. Updates the SYSTEM.ODSINSTANCES table with the new,

encrypted password for ODS.

3. Changes the password for the ODS_SERVER role to the

new password.

4. Updates the $ORACLE_HOME/ldap/admin/oidpwdr file with

the encrypted password.


NOTE: Some Oracle OID patches and scripts may assume the

user ODS/ODS. It is advised to change the password for

ODS back to its default of ODS during application of

patches or when running OID scripts.


But what about ODSCOMMON?

When connecting to the database schema, the OID

executables, such as oidctl or oidldapd servers connect

as the database user ODSCOMMON. The password for

ODSCOMMON is ODSCOMMON, and that password cannot be

changed. It is hardcoded in the executables and changing

it on the database level will cause an ORA-01017 error.

There is no security risk, however, not being able to

change the ODSCOMMON password, as it has only CONNECT

privilege. Once connected as ODSCOMMON, the executable

will obtain the privileges it needs via the role

ODS_SERVER, which is protected by the ODS password. The

password is obtained by the executable from the

SYSTEM.ODSINSTANCES table. This is the password

encrypted and set by the oidpasswd utility.

How to Unlock/Reset Super User cn=orcladmin When the ODS's Password Has Been Forgotten or is Unknown?

Solution

If the ODS password has been lost then follow steps 1-7:

1. Shutdown the OID processes

% opmnctl stopproc ias-component=OID

2. Verify that there is no OID process running

% ps -ef | grep -i oidmon
% ps -ef | grep -i oidldapd
% ps -ef | grep -i odisrv

3. Go to the $ORACLE_HOME/ldap/admin directory and rename the files oidpwdlldap1 and oidpwdrxxxx

where xxxx is the instance name

4. Login to the OID database via sqlplus as an user with DBA privileges (example. SYS or SYSTEM) and reset the ODS schema password:

SQL> alter user ods identified by password;

Note: replace password for the desirable value.

5. Verify that you are able to login to the database using following command.

% sqlplus ods/password@connect_string

Where connect_string is the alias defined in the tnsnames.ora to connect to the OID database.

6. Execute the oidpasswd command to recreate the files renamed in step 3

%oidpasswd connect=connect_string create_wallet=true

Note: To use in this step the same password defined in step 4.

7. Verify that the files renamed in step 3 have been recreated under $ORACLE_HOME/ldap/admin directory

8. If the orcladmin account is locked then use following command

% oidpasswd connect=connect_string unlock_su_acct=true

9. If the password for orcladmin needs to be changed then use following command

% oidpasswd connect=connect_string reset_su_password=true

10. Start the OID process

% opmnctl startproc ias-component=OID

11. Verify that the account orcladmin has been unlocked or that the password has been changed successfully

% $ORACLE_HOME/bin/ldapbind -p port -D cn=orcladmin -w passwd

For example:

$ORACLE_HOME/bin/ldapbind -p 389 -D cn=orcladmin -w welcome1

Overview of 10g Application Server Installation

– infrastructure & Middle Tier Should (MUST) be installed under separate Oracle Homes. Though they can be on Same Physical Machine or on different Machines
– First you have to install Infrastructure Tier then only you can install Middle Tier
– You can install Portal/Wireless or IM Repository in an existing database (Choose RepCA, Repository Creation Assistance tool for this option. If you are new to 10g AS skip this for time being as this is optional feature)
– Before Installation, Make sure all prereq. are complete (Check installation Document mentioned at bottom of this page)
– You can use eDelivery.oracle.com for software or use link http://www.oracle.com/technology/software/htdocs/devlic.html?=/technology/software/products/ias/htdocs/101202.html
– For Portal 10.1.4 , you need 10.1.2.0.2 & then Upgrade portal to 10.1.4 (P.S. Portal version is different than Application Server Version)

Options in Installation

While Installing Infrastructure Tier, you will get three options
- Identity Management & Metadata Repository
- Identity Management only
- Metadata Repository only
If you are new select option 1 i.e. IM+MR as option 2 & 3 are for advanced configuration like Infrastructure on Multiple Machines

While Installing Middle Tier, you will again get three options
- J2ee & Webcache
- Portal & Wireless
- Business Intelligence & Forms

BI & Form type Installation include first two options so this selection will include all J2ee, Webcache, Portal, Wireless, BI & Forms

Portal & Wireless include first option so this selection will include J2ee, Webcache, Portal, Wireless

J2ee & Webcache will install only j2ee & webcache. So if you are not aware of at this minute what you want better select option three i.e. Business Intelligence & Forms

Installation Document
Installation Document from oracle for Application Server version 10.1.2.0.2 is available at
http://download-uk.oracle.com/docs/cd/B14099_19/getstart.htm . Select as per your Operating System.

Hope this helps.....

Overview of 10g Application Server

Overview of 10g Application Server
10g Application Server Consist of Infrastructure Tier & Middle Tier.

What is Infrastructure Tier ?
Infrastructure Tier provides Infrastructure Services to 10g Application Server & consist of following technical components
- Database : To Store User/Applications Identity Data (Portal,Wireless,OID data)
- OID : Oracle Internet Directory, to store User Credentials, Schema passwords, Application details & lot more ...
- HTTP Server : This Web Server (OHS, Oracle HTTP Server) on Infra Tier is used to access SSO (Single Sign-On Server) & OIDDAS (OID Delegated Administrative Services)
- OC4J : Oracle Container for J2EE (OC4J_Security for SSO), You have additional OC4J_OCA if you have OCA (Oracle Certifying Autority). OCA is Optional component in Infrastructure Tier.

What is Middle Tier ?
Middle Tier is tier where application Server & applications logic resides. It consist of following Technical Components
- HTTP Server : This OHS (Oracle HTTP Server) is separate from above OHS & this is OHS from where users access application Server like portal, wireless, j2ee
- OC4J : These are container which provide place holder for j2ee or web applications . Applications are deployed on OC4J's. 10g AS comes with default OC4J name "home", you create more OC4J depending on your requirement
- Web Cache : Web Cache acts as cache for fast response to web server.

Logical Services for Infrastructure Tier
Above was technical components of Infrastructure Tier , Logically Infrastructure Tier consist of Two main categories which are
1. Identity Management
2.Metadata Repository

What is Metadata Repository?
MR is similar to Database Metadata & MR you can further classify as Metadata repository for Products (Like Portal, Wireless, BI) This MR usually is user data. Lets assume I created some pages, documents in Portal or User entered some data in any application , such data when stored in database is called as Product MR.
MR for OID : Oracle Internet Directory contain some data & data related to this , one can classify as MR for IM (as OID is part of Identity Management - discussed later).
MR for SSO : Oracle Single Sign-On data & schema definitions , one can classify as MR for IM (as SSO is part of IM).

So broadly there are three kind of MR (that's how I classify MR)

What is Identity Management?
Logical Grouping of Services which help in Managing Identity is called as Identity Management.Identity management Consist of following Services like :
- OID: Oracle Internet Directory
- DAS: Delegated Administrative Services
- DIP: Directory Integration & Provisioning Services
- SSO: Single Sign-On Service
- OCA: Oracle Certifying Authority

Installation of 10g Application Server in next post.....