R12.2 DMZ issue unable to login and Solution

Issue-1 
DMZ RUN file system config file having Patch file system entry which may be happened because of copy of patch file system config file to RUN fs config file.
Solution: Manually edited and modified RUN fs config file and made changes according to RUN fs
(For More clarification manually compared config file and setups to APDBAPROD DMZ setup config files)
Issue-2 
In CONTEXT_FILE of RUN fs webPort was set to 8002
Solution: corrected web port to 8001
Issue-3 
In CONTEXT_FILE of RUN fs httplistenparameter was set to 8002
Solution: corrected httplistenparameter to 8001
Issue-4
http port was reflecting wrong in http config file
Solution: corrected http port to 8001
Processes in Instance: EBS_web_APDBATST_OHS6
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component                    | process-type       |     pid | status   |        uid |  memused |    uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
EBS_web_APDBATST                   | OHS                |   20517 | Alive    | 1843739326 |  1805484 |   0:34:30 | https:4445,https:10001,http:8001
Issue-5-
mod_wl_ohs.conf file  having Patch fs entry which corrected as below according to correct RUN file setup for DMZ.
Solution:
Setup WebLogicCluster entry for DMZ
Issue-6-
In apps.conf file of RUN fs having Patch fs entry of apps.conf. oacorecluster URL was reflecting patch file entry
Solution:
Manually modified apps.config of RUN fs and added below entry
(Compared apps.config entry of APDBAPROD with current RUN fs apps.config for corrected modification and entry)
http://apdbadmz01.APDBA.com:7203/OA_HTML/media
http://apdbasrv02.APDBA.com:7201/OA_HTML/media
Note: Run autoconfig to reflect changes all changes