Checking Java Installation
The Java version installed in your computer may be different from this example. That is fine as long as it’s version 1.8+.
Open Command Prompt as Administrator.
1. Check if “JAVA_HOME” environment variable is properly set. Type echo %JAVA_HOME% then press Enter.
It should show the JDK installation directory. Mine is C:\Program Files\Java\jdk1.8.0_74. Yours might be slightly different.
2. Check the Java version installed. Type java –version and press Enter.
This is the output in my workstation:
- java version “1.8.0_74”
- Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
- Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)
3. Check if JDK is installed properly. In step 1, we were able to confirm that a JDK installation directory is set in the system environment variable “JAVA_HOME”. To ensure that JDK is installed properly, type javac –version then press Enter.
Mine shows javac 1.8.0_74. This means we’re good to go.
Download SOA Suite Quickstart Installer
Open any Web Browser and search “Oracle SOA Suite Downloads” in google.
Click “Oracle SOA Suite Downloads”.
For a quick reference, this is the link as of the time of this writing:
You will be redirected to this page.
Choose the “Accept License Agreements” radio button.
Expand “Recommended Install Process” section.
Ensure that “Microsoft Windows 64bit JVM” is selected.
If you read the note in Part 1 under Product Installation, notice the last part: “Oracle JDeveloper with SOA IDE extensions and an integrated WebLogic Server…”. That’s what we’re interested in.
Let’s ignore those under the “Additional Components” section as our installation is already rich with features we need.
In my future posts, we will try different features of Service Bus by deploying SB Projects in the WebLogic Server.
Click Download for the Part 1. You will be redirected to the Oracle Single Sign In page. Enter credentials, then download will start.
Once download is complete, simply press the back button of the browser, then download the Part 2. If it prompts to accept the license again, then just click “Accept License Agreements” radio button like you did earlier.
Now we have two zip files:
- fmw_12.2.1.3.0_soaqs_Disk1_1of2.zip
- fmw_12.2.1.3.0_soaqs_Disk1_2of2.zip
Extract each Zip file. Two folders will be extracted, one for each zip file. What we’re interested in are the jar files within those folders, so move those jar files outside. That way, both jar files are within the same directory.
Extract and Run JARs to Start Installer
Run Command Prompt as Administrator then navigate to the location of the installers.
Type java -jar fmw_12.2.1.3.0_soa_quickstart.jar then press Enter.
This could take a couple of minutes. Around 10 minutes in my workstation.
Once extraction and initial checks are complete, the Installation window displays.
Installation Dialog Steps
1. Welcome: Click “Next”.
2. Auto Updates: Leave default (Skip Auto Updates). Click “Next”.
3. Installation Location:
You may set any valid installation directory. In this example, I will just leave the default as it is.
Click “Next”.
4. Prerequisite Checks
Based on experience, you may encounter warnings in this part of the installation. I have encountered warnings on either items shown below but still continued successfully. If it’s a warning, perhaps you could just ignore it and continue. Click “Next”.
5. Installation Summary:
Review the details. Click “Install”.
This may take about 30 minutes. Once done, you’ll see the screen the same as below. Click “Next”.
Take note that by default, “Start JDeveloper” checkbox is checked. Then click “Finish.”
JDeveloper splash screen appears.
“Select Role” dialog box appears. For now, just leave the default as is (Studio Developer (All Features)). Then click “OK”.
We have installed JDeveloper IDE successfully.
Running and Terminating the Integrated WebLogic Server
As mentioned earlier, this installation includes an Integrated WebLogic Server.
So let’s go ahead and try running it!
In the JDeveloper window menu bar, click Window > Application Servers.
Notice the “Application Servers” tab added on the left pane. Expand “Application Servers” and you will see “IntegratedWebLogicServer”. This is the WebLogic Server instance that we will start.
Right click the “IntegratedWebLogicServer” instance > Start Server Instance.
“Create Default Domain” dialog box appears.
| Field | Description | Value |
| Administrator ID | Username for WebLogic admin console and Service Bus console. | Defaulted to “weblogic”. For this installation, we’ll leave it as it is. |
| Password | Password for WebLogic admin console and Service Bus console. | Default is blank. For this installation, let’s set it to “weblogic1” |
| Confirm Password | Repeat for confirmation of password. | Default is blank. For this installation, let’s set it to “weblogic1” |
| Listen Address | IP Address/Domain for the WebLogic Admin and Service Bus consoles. | Default to <All Available Addresses>. For this installation, we’ll leave it as it is. |
| Listen Port | Port for the WebLogic Admin and Service Bus consoles. | Defaulted to 7101. For this installation, we’ll leave it as it is. |
| SSL Listen Port | SSL Port for the WebLogic Admin and Service Bus consoles. | Defaulted to 7102. For this installation, we’ll leave it as it is. |
After the fields are populated, click “OK”.
You should see this in the Log pane:
Creating IntegratedWebLogicServer Domain . . .
It takes about 15 minutes for it to start. You would see the Logs below:
[IntegratedWebLogicServer started.]
Let us now access the WebLogic admin console.
Open the browser and type this:
http://localhost:<listener port>/console
<listener port> was the value set earlier in the “Create Default Domain” dialog box. In this installation, we left the default 7101, so let’s use:
WebLogic Server admin console login screen loads. Login by entering your credentials set earlier in the “Create Default Domain” dialog box. In this installation, the username is “weblogic” and password is “weblogic1”.
Once you login, go to Environment > Servers.
Under Servers, you should see the DefaultServer(admin) in RUNNING state. Health should be OK.
This confirms that our WebLogic installation is successful.
Alright! So for now, let’s shutdown the WebLogic Server.
Back to the JDeveloper window, right-click IntegratedWebLogicServer > Terminate Server Instance.
It will take a few minutes until it is properly terminated. Logs should be like the one below:
After this, you may now safely close the JDeveloper window.
No comments:
Post a Comment