Configuring iSupplier Node in Oracle R12.2 | Step-by-Step Guide

When exposing iSupplier to external node, Oracle recommends configuring a dedicated DMZ web node. This ensures only the web tier is accessible externally, while the application and database tiers remain secure inside the firewall.

---

Here will use two nodes for internal and external.

Internal Server: - 192.168.11.10

External Server: - 192.168.11.20

Step 2: Configuring NFS for Oracle Applications (iSupplier Node Setup)

Before proceeding with the configuration, ensure that both NFS client and NFS server packages are installed on the respective systems.

Step 1: Install NFS Packages on External node

If NFS is not installed, install it using the following command:

yum install -y nfs-utils

Step 2: Verify NFS Service Status

Check the status of the NFS service:

systemctl status nfs-server

If the service is not running, start and enable it:

systemctl start nfs-server

systemctl enable nfs-server

Step 3: Configure NFS Export on Source Server

Edit the exports file on the source server:

vi /etc/exports

Add the Application tier file system path as shown below:

/oracle/apps/ 192.168.11.10 (rw,sync,no_root_squash)

Explanation:

• rw → Read and write permissions
• sync → Synchronous writing for data integrity
• no_root_squash → Allows root access from client (use cautiously in secure environments)

---

Step 4: Restart NFS Service

Apply the changes by restarting the NFS service:

systemctl restart nfs-server

Also reload exports:

exportfs -ra

Step 2 : Run preclone on the existing node(source node)

$ cd $INST_TOP/admin/scripts

$ perl adpreclone.pl appsTier

Step 3 : Clone Context File

Run the adclonectx.pl script to generate a new context file for the external node:

perl $COMMON_TOP/clone/bin/adclonectx.pl

You’ll be prompted for details such as hostname, SID, domain, base directory, ORACLE_HOME paths, APPL_TOP, COMMON_TOP, and instance home. Example:

• Target Hostname: abctest
• Target SID: UAT
• Target Domain: abc-test.com
• Base Directory: /data01/GSTUAT_8026
• APPL_TOP: /data01/GSTUAT_8026/apps/apps_st/appl
• COMMON_TOP: /data01/GSTUAT_8026/apps/apps_st/comn
• Instance Home: /data01/GSTUAT_8026/apps/inst

At the end, a new context file (e.g., UAT_abctest.xml) will be created.

During context file creation, enable only the services required for iSupplier node:

• Root Service: enabled
• Web Entry Point Services: enabled
• Web Application Services: enabled
• Batch Processing Services: disabled
• Other Services: disabled

This ensures the external node runs only web-related services.

Step 4: Set Port Pool

Choose a unique port pool (e.g., 26) to avoid conflicts with internal nodes. Port details will be logged in portpool.lst.

$perl $AD_TOP/bin/adconfig.pl  contextfile=/oracle/PROD/inst/apps/PROD_isupplier/External.xml

Step 5 : Run the txkChangeProfH.sql under $FND_TOP/patch/115/sql using apps user.

SQL>@txkChangeProfH.sql SERVRESP

After adding and generating the new context file on external node, run AutoConfig on the internal node initially, and then execute AutoConfig on the external node. This sequence is required to synchronize the configuration and ensure that the new node is correctly populated in the FND_NODES table.

 Step 6: Run AutoConfig

Once the context file is ready, run AutoConfig on the external node:

$ADMIN_SCRIPTS_HOME/adautocfg.sh

This applies the configuration and sets up the external web tier.

Step 6: Validate Setup

• Check the CloneContext log for errors:
  /data01/GSTUAT_8026/apps/inst/apps/UAT_aceapps/admin/scripts/CloneContext_0804113428.log
  
  
• Verify that only web services are running on the external node.
• Test iSupplier login externally via the DMZ hostname.
  
  

Step 7 : Set below profile as per configuration.

POS: External URL

POS: Internal URL

Query for %NODE%TRUST%. You will see a profile option named 'Node Trust Level'

Set the value of this profile option to External at the server level to external node only

Once set the profile option . Hope you will able to login in External URL accordingly...

 

 Best Practices

• Always configure SSL for secure supplier communication.
• Keep database and application tiers internal.
• Regularly monitor AutoConfig logs and Apache/OHS logs.
• Follow Oracle’s DMZ best practices (DMZ configuration guide).

---

This process ensures that your iSupplier portal is securely accessible to external suppliers while protecting your internal EBS environment.

Would you like me to extend this into a full-length blog post with troubleshooting tips (e.g., handling login redirection or SSL handshake issues), so it’s ready for publishing?