3 Replies Latest reply on Dec 6, 2017 10:43 AM by simplyDeveloper

    change listening port for ORDS 3.0.9 deployed on weblogic

    simplyDeveloper

      Hi ! I have ords 3.0.9 deployed on weblogic 10.3.6.0

       

      If i look in :

      AdminConsole--->Server--> AdminServer --->Configuration--->ListenPort = 7001

      AdminConsole--->Server--> WLS_APEX --->Configuration--->ListenPort = 9003

       

      But ORDS actually is running on different port 8888

       

       

      Where this is configured and how to change it ?

        • 1. Re: change listening port for ORDS 3.0.9 deployed on weblogic
          thatJeffSmith-Oracle

          it's not possible to deploy ORDS to WLS AND have it run in standalone mode - it shouldn't be listening on any port - all of it's traffic is being handled a layer above it via WLS

           

          it's much more likely that you have managed to get 2 copies of ORDS running on that server, and one of them is in standalone mode and listening on 8888.

           

          how many ords.war processes do you have going?

          • 2. Re: change listening port for ORDS 3.0.9 deployed on weblogic
            Kiran Pawar

            Hi Buzis,

            Buzis wrote:

             

            Hi ! I have ords 3.0.9 deployed on weblogic 10.3.6.0

            If i look in :

            AdminConsole--->Server--> AdminServer --->Configuration--->ListenPort = 7001

            AdminConsole--->Server--> WLS_APEX --->Configuration--->ListenPort = 9003

             

            But ORDS actually is running on different port 8888

            Where this is configured and how to change it ?

            What do you mean by "ORDS actually is running on different port 8888"? Is it running in Standalone Mode?

            NOTE:

            • Standalone Mode has nothing to do with ORDS deployed on Oracle Weblogic Server (both configurations are different)
            • Standalone Mode internally runs a bundled HTTP Server (jetty) and does not need Oracle Weblogic Server to run.
            • But Oracle recommended practice is to deploy ORDS to one of the Supported Java EE Application Servers (here ORDS is the Java application which we are deploying)

             

            Now, if we see the deployments in Oracle Weblogic Server, we can choose the Target Server (Admin or Managed Servers) during deployment and the (java) application uses the port of the Admin/Managed Server on which it is deployed.

            Refer: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/10g/r3/appdeploy/deploy/deploy_apps/deploy_apps.htm

            You can delve more deeper or consult your Oracle Weblogic Administrator as to how Managed Servers are created/maintained/configured and how to change the port on which those servers run.

            Then you can use the appropriate Managed Server to deploy ORDS on the port on which you want it to run.

            NOTE: This applies only for Oracle Weblogic Server, changing port is different case when you deploy ORDS on Apache Tomcat or Glassfish Server.

             

            Hope this helps!

             

            Regards,

            Kiran

            • 3. Re: change listening port for ORDS 3.0.9 deployed on weblogic
              simplyDeveloper

              Ah, there is Oracle HTTP server running on that server and when i check port usage , i see :

              Port in Use

              IP Address

              Component

              Protocol

              8889ALLohs1https
              8890ALLohs1https
              8888ALLohs1http

               

              That's where this 8888 comes from.

              Sorry guys if misleading you some way.

               

              i see no ords.war processes running at system level and in console under deployments only one ords.war.

               

              Thanks anyway!