Clarification
I need to clarify a few points to guide you to the correct answer.
- Are you sure this is a separate Weblogic server running on localhost, not the Integrated Weblogic Server?
- Are you sure the Integrated Weblogic server is not running?
- Are you sure the Weblogic server you are attempting to connect to is running?
Troubleshooting
General Recommendations
- Always run JDeveloper as Administrator
- Located an utilize the *-diagnostic.log file and the standard out file
- Utilize the JPS utility to see if the WLS process is running
- Utilize the EM console to see what interface your server is listening on
Integrated Weblogic or Standalone Weblogic
Firstly, because you are new to Oracle SOA I need you to clarify if you have a Weblogic server installed locally separate from your Oracle BPM Studio ( JDeveloper ) IDE.
When creating a local SOA environment, JDeveloper comes with an Integrated Weblogic Server pre-installed. You don't need to install the Weblogic server separately.
To determine if you have a standalone Weblogic server installed on your local machine you could do a few things.
- Do a search for
startWebLogic.cmd
. If that file is somewhere other than beneath %APPDATA% you likely have a standalone server
- Secondly, with 11g ( maybe 12c ) you can check Add or Remove Programs to see if the installation is listed
- You could also check to see if it's running by running a
jps
command in command prompt. This shows all Java processes currently running, and your Weblogic server runs as as a Java process. It will look something like the following

- If you see a suspicious process you can run a
jinfo <pid>
to get more information about the process
- You can also check Windows Services to see if you have a Weblogic service.
Most likely you don't even have a local Weblogic installed separate from JDeveloper's Integrated Server. In that case, please read the following section.
Integrated Weblogic Server
As stated before when you download Oracle BPM Studio ( JDeveloper with all the SOA plugins ) it comes with an Integrated server.
You first need to create a default domain and connection to this server.
First, open the Application Server panel.

You should now see the Application Server panel to the left side of your IDE

Remember, generally you are not installing the server here, you are just connecting to a server that is already installed from your IDE. The purpose being that you can deploy composites directly to the server from JDeveloper. Configuring the Integrated Server is a bit different, but the difference doesn't need to be explained here.
- Right click on "Application Servers" and click New Application Server. This will display the following popup

Now walk through the steps of creating the default domain and server connection

Then test and finish. You should not have an integrated weblogic server running. To start the server you simply run -> Start Integrated Weblogic Server

If you Windows -> log
you can see the server stdout and stderr rolling.
On windows you can also find these logs on Windows 10 by navigating to %APPDATA%\Roaming\JDeveloper\system12.2.1.3.42.170820.0914\DefaultDomain\servers\DefaultServer\logs
in your system's file explorer.
Standalone Server
If for whatever reason you aren't using the Integrated Weblogic Server and instead have a standalone installation of Weblogic on your local machine you would first need to find where your Middleware Home directory is.
The environment variable is MW_HOME or ORACLE_HOME
Navigate to that directory and run startWeblogic.cmd
. Then tail the out file to see if if it starts successful. From there, the process of creating a connection to the server in JDeveloper is no different than the steps listed above, except that you want to select "standalone" not "integrated".
Final Thoughts
If you want to create the Integrated Server and have already failed several times I would try the following
- Stop the Integrated Server (if its running) and delete the default domain
Starting the server again (see above) will recreate the domain.
- If that doesn't work delete the entire server connection and recreate. You may also want to delete the DefaultDomain folder in your
%APPDATA%\JDeveloper
folder