Professional Documents
Culture Documents
Configuring
WebLogic 12c
(v12.1.3)
Hands-On Workshop
Guide
Copyright 2014, Oracle. All rights
Reserved
Table of Contents
Lab 1: Installing Oracle WebLogic Server 12c (v12.1.3).............................................3
1.1)
2.2)
2.2.1)
2.2.2)
Revision History........................................................................................................ 24
Activity Steps:
Manager, Java Required Files (JRF) for Async Web Services, SOAP over JMS,
and the ADF application libraries.
1.2.1)
oepe-12.1.3.1-kepler-installer-win32
1.1.3)
1.1.4)
On the Welcome Screen, click Next
Note the new left-hand navigation to show progress through the installation
steps.
1.2.5)
On the Installation Location screen:
Enter the location for the new Oracle Home:
Recommended value for this lab: C:\Oracle\WLS_12.1.3_oepe
Click Next
By default, this installer will install both WebLogic Server and Coherence. The
generic installer found in the downloads directory behaves a little differently in
the fact that it allows you to choose whether or not you want to install
Coherence and the WebLogic samples.
1.2.6)
On the Installation Summary screen, click the Install button to
begin the installation process:
1.2.7)
completed
Note that during the Generating Libraries step, the installer generates
some libraries that helps server startup times it also generates client
libraries.
Select Next when the installation is complete
1.2.8)
On the Installation Complete screen, select Finish
Note that there is no longer any checkbox to Run QuickStart in this installer
- this is provided as a separate executable to be launched independently if
desired. If you are using the generic installer, there is a quickstart checkbox
used to configure the sample domains.
1.2.9)
Look at the directory structure that was laid-down for WebLogic 12.1.3
When you compare this to a WLS 10.3.6 installation, youll notice that there are 4
new directories:
inventory, install and oui are for the Oracle Universal Installer
OPatch for patching
The old modules directory has been nested under oracle_common
Heres a screenshot of a WLS 10.3.6 directory structure for comparison purposes:
Notice the patch directories as well as the version numbers of the specific products
on the directory names these were eliminated in WebLogic 12c.
1.2)
1.2.1)
Before you can install any Oracle Fusion Middleware product using a
generic installer, you must download and install a supported JDK on your
system before attempting to run the installer.
WebLogic 12.1.3 is supported with the Java 8 JDK v1.8.0_20 and above.
For more information about supported JDKs with WebLogic 12.1.3, see the
following spreadsheet: System Requirements and Supported Platforms for
Oracle Fusion Middleware 12c (12.1.3):
1.2.3)
Launch the Oracle WebLogic 12.1.3 installer by opening an
Administrator command-window in the directory where the generic download
was saved to.
Either full-path the java command-line or set the JAVA_HOME and PATH
environment variables to reflect the Java JDK. In this example, the v1.8.0_20
JDK is being used.
set JAVA_HOME=C:\PROGRA~1\Java\jdk_1.8.0_20
set PATH=%JAVA_HOME%\bin;%PATH%
Run the command: java jar fmw_12.1.3.0.0_wls.jar and wait for the
1.2.4)
1.2.5)
On the Welcome Screen, click Next
Note the new left-hand navigation to show progress through the installation
steps.
1.2.7) On the Installation Type screen, select Complete with Examples to install
WebLogic, Coherence, and the examples for each.
Select Next to continue:
1.2.8) Select Next on the Prerequisite Checks screen if all checks are successful,
otherwise correct and re-launch the installer. A supported Java7 or Java8 JDK is
required (ie: JDK 1.7.0_15+, or JDK 1.8.0_20+)
If you de-select the checkbox, select Yes button in the My Oracle Support
Username/Email Address Not Specified dialog that pops up:
1.2.10)
1.2.11)
1.2.12)
completed
Note that during the Generating Libraries step, the installer generates
some libraries that helps server startup times it also generates client
libraries.
1.2.13)
Select Finish when the installation is complete to dismiss the
installation wizard. WebLogic 12.1.3 is now installed.
1.2.14)
installer for WebLogic 12.1.3 in your file explorer. Note how this is different from
the directory that was installed by the OEPE installer as well as that of a WLS
10.3.6 install:
OEPE Installer
WLS 10.3.6
Installer Directories
Directories
Directories
2.1)
Run the config wizard this can be started by running the config.cmd program in
the directory: C:\Oracle\WLS_12.1.3\oracle_common\common\bin
Note that just like the new installer, the configuration wizard now also uses the
Oracle Universal Installer so has the same look-and-feel as other Oracle products
like SOA Suite.
Select the option to Create a new domain and override the base domain directory to
something like WLS_12.1.3_DevDomain in the default directory - Then select Next.
You dont need to select any additional Templates for a plain old WebLogic
development domain - just select Next.
For more information on the use of Templates, look here.
You may use the default Java JDK that was used when WebLogic 12.1.3 was installed
or select Other JDK Location and select a 64-bit JVM for the domain. In the future,
if this WebLogic domain is extended for use with SOA, OSB, and/or BPM, a 64-bit JVM
will be needed because the heapsize for all those applications together is larger
than the max for a 32-bit JVM.
Ensure that the Development Domain Mode is selected so the domain is easier to
start/stop without having to provide user/password each time. Development mode
is also easier to deploy applications to because WebLogic will poll an application
directory for new artifacts to deploy.
The default domain is set to listen on port 7001 if you want to override that port
number you can modify the administration server settings or modify it after the
domain is created by editing the configuration files or changing the port number in
the WebLogic administration console. These steps arent covered in this workshop
so select the Next button:
Monitor the configuration progress until the domain is created then select Next.
After the domain is created, take note of the domain location and admin server URL
then select Finish (dont select the Start Admin Server checkbox as well start
the server manually in the smoke-test next).
2.2.2)
Checking WebLogic Server:
You can test to be sure that WebLogic is up by going to the administration console
at: http://localhost:7001/console
The first time this URL is hit, the console application will be deployed onto the new
WebLogic domain. In any subsequent console access, the console app will already
be there so this delay only happens once.
login as weblogic/welcome1 (or whatever you set the weblogic password to be).
Copyright 2014, Oracle. All rights reserved.
P a g e | 21
Open the Environment -> Servers -> AdminServer and browse through this
WebLogic managed server configuration.
Revision History
File Name
WebLogic_12.1.3_Install_and_Config_Workshop_v1.0.doc
Original Author(s)
John VanSant
Date
Author(s)
Revision Notes
1.0
January 5, 2015
John VanSant
Original