Introduction
If you apply the April 2019 Critical Patch Update or the Oracle E-Business Suite Technology Stack Delta 11 release update pack (R12.TXK.C.Delta.11), you will see a change in how you access the Oracle WebLogic Server Administration Console. To enhance security all access to the Console is configured to be denied by default. As a result, you can only connect to the Console from the application tier server. For example, if your Console is running on the “beeapps” server, you must log in to the “beeapps” server first and connect using a browser on that server.
Oracle does provide alternative methods of connecting to the Console from your desktop if you prefer. One alternative is using SSH tunneling and is discussed below.
In this example, we will be connecting to the Console running on our “beeapps” application server. Note, this example is assuming the run file system is fs1 and the Console is listening on port 7001. When the run file system is fs2, the Console is listening on port 7002.
Connect to the Console
Step 1: Establish an SSH Tunnel
In your Windows PC
Right-Click on the Start button
Choose the Run menu item
In the Run box, type cmd
Click the OK button
The command window will appear. Enter the following at the prompt to login to the “beeapps” server as the “applmgr” user:
C:\>sshapplmgr@beeapps -L localhost:7001:beeapps:7001
When prompted, enter the password for the APPLMGR user
You should see the following if you login successfully:
E-Business Suite Environment Information
—————————————-
C:\>RUN File System : /opt/app/oracle/apps/fs1/EBSapps/appl
PATCH File System : /opt/app/oracle/apps/fs2/EBSapps/appl
Non-Editioned File System : /opt/app/oracle/apps/fs_ne
DB Host: beedb.beejartha.com Service/SID: PROD
Sourcing the RUN File System ...
[applmgr@beeapps~]$
Step 2: Log in to the Console
Now you can connect to the Console from your desktop. Open a browser and go to http://localhost:7001/console and you will see the login page:
Step 3: Log off and stop SSH Tunnel
When you are done using the Console do not forget to close the SSH Tunnel you created in the CMD window.
Credits
- This tutorial is independently created and is not official Oracle Corporation documentation.
- The content of this tutorial has been enriched by leveraging the insights and documentation available from Oracle Corporation. We extend our thanks to Oracle for their dedication to knowledge sharing. For official Oracle resources and additional information, please refer to www.oracle.com.