Reverse Proxy

Reverse proxy is an intermediate server that sits between a client and the actual web server and makes requests to the web server on behalf of the client.
It is generally used when configuring DMZ with Oracle applications. If it is properly configured it enhances the security level.

More post on this is on the way....

Implementing HRMS in 11i

To implement HRMS apply patch HR_PF.K Rup 1 (patch 5055050).
Now you can follow the following patch sets to implement HRMS with india legislation :

1. 6196112 Global HR patch
2. 6339534 Global HR patch
3. 6348219 Global HR patch
4. 5853811 India Legislation Patch

Apply additional payroll updates also :

1. 5972562 END OF YEAR 2006-2007 CHANGES AND NEW YEAR STATUARY UPDATE

2. 6021023 FORM 16/16AA - AMENDMENTS


Refer to these metalink documents for more details :


NOTE. 375001.1 IN Legislation : Mandatory installation and Patch list.
NOTE. 297146.1 Oracle HRMS for India Supplement
NOTE. 283267.1 APAC HRMS Mandatory Patches
NOTE. 369718.1 India Income Tax Reports

Change IP address of an existing Apps server

This scenario solely depends on how you have carried out Installations. While installations if you have used only hostname of servers instead of IP address then the activity becomes very simple.

Otherwise you can check fnd_profile_option_values where profile_option_value has an ip style number in it. Check icx_parameters so see whether an vals in there are IP numbers, check the tnsnames and listener.ora files in the oracle homes to see if they have ips or names and a quick check, if someone has not manually updated it ... if you are autoconfig enabled, check the context file ( $APPL_TOP/admin/.xml ) to see whether it has IPs or names in it.



Steps :

1. Shut down the Application as well as database.

2. Change the IP address at OS level and restart the Network daemon.

3. Bring up the database listener.

4. Startup the databse.

5. run auto config at databse then at all middle tier starting from admin node. It should complete successfully.

6. Bring up the middle Tier. They should come up without any error.

Chaging port of Web listener after installation

This note applies to Oracle Applications 11.5.10.2
I have implemented this in one of my project at client location.

Follow these easy steps to change the port of web listener of your live system.

Assumptions:

1. Current port is 8080 and need to be changed to 8000.


Steps :

1. Logon to middle Tier and open the confiduration .xml file (resides in $APPL_TOP/admin) with editor. I have used vi as my editor.

2. Replace any occurrance of 8080 with 8000. You can use this command in vi to replace the string 8080
:%s/8080/8000/g


3. Save the file and exit.

4. Now run the autoconfig on the middle Tier. And Restart all the middle tier services.

5. Now try to open the instance login page with new port.


If you are using multi-Node system. The you have to edit every node's xml file and run autoconfig on each node seperately.

Cloning (multi node to single node) oracle Shared Application file system

I didn't find any clear note on cloning of shared application tier file system. I have implemented this for one of our client. Hence, I am posting. Hope it help you out.

Source server Specifications :

Number of Nodes : 3
Node1 : Database
Node2 : Admin & Concurrent server (NFS Share)
Node3 : Forms $ web (NFS mount)


Target server Specification :

Node 1 : All services

Operating System : Solaris 10

Application Version : 11.5.10.2

Steps :

note : While cloning assume the shared file system server as single node server.

1. Run adpreclone.pl at node on which admin server is installed.

$perl adpreclone.pl appsTier

In shared application file system you need NOT use "merge" option with adpreclone.

If you are using solaris you will have to define env varaiable PATH and PERL5LIB to successfully run this command.

2. Run adpreclone.pl at database tier.

$perl adpreclone.pl dbTier


3. Copy all the file system from source node to target node. You can use tar and gzip command to create file for transfer.

Copy the following application tier directories from the primary node of your source system to the target application tier node, retaining the original directory structure:

– [APPL_TOP]
– [OA_HTML]
– [OA_JAVA]
– [COMMON_TOP]
– [806 ORACLE_HOME]
– [iAS ORACLE_HOME]

4. At target node uncompress the files.

5. Run the adcfgclone.pl at database end first then at appsTier.

perl adcfgclone.pl dbTier (DBTier)
perl adcfgclone.pl appsTier (appsTier)


6. run autoconfig on database end first then on apps tier.

7. Post Clone Tasks

Log in to the target system application tier node as the APPLMGR user.
Run the following tasks in adadmin for all products:
o generate JAR files
o generate message files
o relink executables
o copy files to destination

Installing Oracle Application with shared File system

This activity I carried out in one of my Project for setting up a production. I am putting exact steps.

Installation Specifications :

Number of Nodes : 3
Node1 : Database
Node2 : Admin & Concurrent server (NFS Share)
Node3 : Forms $ web (NFS mount)

Operating System : Solaris 10

Application Version : 11.5.10.2

Steps :


1. create nfs share on node2 say /prodxyz. share /prodxyz.
2. create same directory /prodxyz in node3 also. Be sure when you do pwd in node2 or node3 this should exact same directory structure.
3. share (by nfs) /prodxyz in node2.
4. mount node2 /prodxyz on node3 /prodxyz.
5. check /prodxyz should have sufficient space for installation.

6. create database user in node1 say oraprod with home directory /prodxyz/oraprod. Note that there is no nfs mount from node2 on this node1. we are just following uniformity.

7. create apps user in node2 and node3. take care that they should have same userid and group(generally dba) id. Also the oraprod should also have same group and group id as apps user. say apps user is appsprod.

8. Home directory of appsprod is /prodxyz/appsprod (which is shared).

9. Now begin the installation from database end (node1)

10. select multi node installation. It will ask you at some stage for node information. on that stage click on details tab. select node2 "INSTALL" and for node3 "share existing".

11. rest follow the screen as normal installation.

12. after installation on node1. begin installation on node2 sourcing the context file from node1.

13. after installation on node2 begin on node3 sourcing the same context file. Note that begin installation at node3 with appsprod user. otherwise installation will error out.

now leave rest on installer.

wow you have implemented applications shared file system !!