X

EMEA A&C CCOE Partner Technology Cloud Engineering

The Specifics of ADF 12c Production Domain Deployment

Guest Author

Next
to the recent release of Oracle JDeveloper 12c and ADF 12c, many  developers
and ISVs would want to migrate to the new version. Therefore let’s take a look
on the deployment of ADF 12c in production domain.

In this post I
would like to cover simple use case of deployment sample ADF 12c
production domain. In order to do this it is necessary to have the following
components: Application Development Runtime (12.1.2), Oracle Database 11g Express Edition (NOT CERTIFIED, but
suitable for our sample, for enterprise production or development environments
it will be needed Oracle DB SE OneSE or EE)
and JDK 7.

All
links for products distributives you could find bellow:

In
our example we will demonstrate deployment process in MS Windows OS environment.

There
are also some useful links bellow, which could be interesting:

I
would like to pay attention to the following important facts: 

  1. The
    available Oracle WebLogic (12.1.2) installer
    is generic and can
    be used on any supported platform. Platform-specific WebLogic Server
    installers are no longer provided. Also installation program no longer
    includes a JDK.
  2. ADR already contains WebLogic
    12
    с components. So there
    are two ways of infrastructure deployment:
                              2.1. The first approach involves the
use of 
Oracle WebLogic 12c installers, and after
this it is necessary to install
ADR.
                              2.2. The second approach use only ADR
installer
, which installs Oracle WebLogic and
ADF runtime components (except 
JDK).

The
following self-extracting installer JARs are available:

  • wls_121200.jar - Installs WebLogic Server
    and Coherence
  • fmw_infra_121200.jar - Installs WebLogic Server,Coherence, and infrastructure components for Fusion Middleware
    product platforms.

In
our case we will go through shortest way using only ADR installer.

Let’s
consider the whole process step by step:

Stage 1: JDK installation.

In
our case we use Java SE version 7u25. But it is possible to use
also Oracle JRockit JVM.

Stage 2: Oracle Database XE
installation.

RDBMS
installation is necessary stage, as in addition to application specific data, you
should install the metadata schemas on a database which certified for this
release of Oracle Fusion Middleware.

NOTE: It is important to
know that Oracle Database XE 11g is NOT certified for
FMW 12c infrastructure. In this case it will
be used for sample purposes. For FMW 12c certified the following
versions of Oracle Database: 12.1.0.1+; 11.1.0.7+; 11.2.0.3+. Please, be
familiar with Oracle
Fusion Middleware 12c (12.1.2.0.0) Certification Matrix
.

Stage 3:  Fusion Middleware
components installation.

On
the command prompt use the following command:

<JDK_path>\bin\java
-jar fmw_infra_121200.jar  

Example:

C:\Java\jdk1.7.0_25\bin\java
-jar fmw_infra_121200.jar

NOTE: For Mac OS X environment use the following command:

/usr/libexec/java_home --version 1.7.0 --exec java -jar ./fmw_infra_121200.jar

Let’s
look at the key aspects of installation process:

1) On  the 2nd step of installation wizard you should specify Oracle
Home
directory:

2) On 4th
step
of installation wizard be aware, that all prerequisite checks
have been completed successfully. 

3) Finish the installation process.


Stage
4:
 DB
schemas creation by RCU utility.

You
should start RCU with the following command:

<MW_HOME_path>\oracle_common\bin\rcu 

Example:

C:\Oracle\Middleware\FMW12c\oracle_common\bin\rcu 

NOTE: For Mac OS X environment before running RCU use the following commands:

bin $ export DISPLAY=:0
bin $ export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home
bin $ ./rcu

You
could get more information about RCU utility in the «Creating
Schemas with the Repository Creation Utility
» guide:

During
launching RCU utility you might get an error that OS cannot found JRE
location directory. You could fix this issue by the following way:

  • Open rcu.bat batch file
    in a text editor
    .
  • Find lines
    where parameter JRE_DIR was
    defined, and edit it, adding path to JRE location:

  • Save the
    file and launch it again.

Let’s
look at the key points of this stage:

1) On the 2nd
step
 of configuration wizard you should specify Database Connection
Details
:

After
this, click Next button and the utility will make all the necessary
checks and report about database incompatibility. Click Ignore here
to continue process.

2) On the 3rd
step
of configuration wizard, you should specify schemas prefix and
check AS Common Schemas in the components tree:

3) On the 4th
step
of configuration wizard, you should specify passwords for schemas:

4) On the 5th
step
of configuration wizard
, RCU makes tablespaces
configurations. You could change default values here:

5) After the
completion of the 6th step of configuration wizard, click the
Close button.

Stage 5: Domain deployment and
configuration.

In
order to configure domain we will use Configuration Wizard utility:

In
order to start wizard you should execute the following command:

<MW_HOME_path>\oracle_common\common\bin\config.cmd

Example:

C:\Oracle\Middleware\WebLogic1212\oracle_common\common\bin\config.cmd

Let’s
look at the key points of this stage:

1) On the 2nd
step
of configuration wizard, check the following options in Available Templates
list: 

  • Oracle
    Enterprise Manager - 12.1.2.0 [em]
  • Oracle JRF
    - 12.1.2.0 [oracle_common]
  • Weblogic
    Coherence Cluster Extension - 12.1.2.0 [wlserver]

2) On the 5th
step
of configuration wizard, specify Production Mode and leave and JDK
path the same:

3) On the 6th
step
of configuration wizard, specify DB connection parameters, and RCU
service table (STB) schema credentials. Click Get RCU Configuration
and ensure that Connection Result Log is OK. Click Next.

4) On the 9th
step
of configuration wizard, check Administration ServerManaged
servers, clusters and coherence
options. We will configure its later. Click
Next.

5) On the 11th
step
of configuration wizard, click Add button in order to add managed
server and specify it name as ADFManagedServer. Leave other parameters
with its default values and click Next.

6) On the 14th
step
of configuration wizard, click Add button to add machine as ADFMachine
and then click Next.

7) On the 15th
step
of configuration wizard, target AdminServer and ADFManagedServer
to ADFMachine and click Next.

8) On the 16th
step
of configuration wizard, click Create button and wait until
wizard will create and configure domain. Click Finish after this.

9) Domain creation
now has been completed.

Stage 6: Additional configuration of
the domain and other components.

Execute
command below and run AdminServer:

<MW_HOME_path>\user_projects\domains\<domain_name>\bin\startWebLogic.cmd

Example:

C:\Oracle\Middleware\WebLogic1212\user_projects\domains\ADFDomain\bin\startWebLogic.cmd

During the domain configuration process, we specified Production mode,
so in our case you need to input weblogic account credentials to
run AdminServer. After this wait until AdminServer goes to state RUNNING.

Navigate to WebLogic Administartion Console, on URL:

http://<host_name>:7001/console

Log in using weblogic account.

In our configuration we will not use SSL encryption in the Node
Manager
configuration. So in order to use Plain type let’s
make the following steps:

1) Go in the Domain Structure tree to Machines
node. Click on our ADFMachine and go to the Node Manager
tab. Click Lock & Edit to edit current configuration and select Plain value
of Type parameter. Click Save 
и Activate
Changes
 in order to save current configuration.

2) Open nodemanager.properties file located in the
following path in the text editor:

<MW_HOME_path>\user_projects\domains\<domain_name>\nodemanager\nodemanager.properties


Example:



C:\Oracle\Middleware\WebLogic1212\user_projects\domains\ADFDomain\nodemanager\nodemanager.properties

Edit SecureListener parameter,
and specify it value as
false.

SecureListener=false

3) Run Node Manager service, using the following
command:

<MW_HOME_path>\user_projects\domains\<domain_name>\bin\startNodeManager.cmd

Example:

C:\Oracle\Middleware\WebLogic1212\user_projects\domains\ADFDomain\bin\startNodeManager.cmd

4) Restart AdminServer and ensure that the Node Manager is
available and has Reachable status. You could check it in Monitoring tab
and Node Manager Status tab inside it.

Stage 7: Targeting
JRF libraries on managed servers.

For regular ADF Application with working Enterprise Manager
Fusion Middleware Control
, it is necessary, to target JRF (Java
Required Files) 
libraries on managed servers.

1) Navigate to Enterprise Manager Console, using URL:

http://<host_name>:7001/em

Log
in, using weblogic account.

2) Find out single managed server (in our case) ADFManagedServer
in components tree. Click Apply JRF Templates button. Wait until
the operation is complete. Targeting libraries is complete now.

3) Now it is necessary to run our managed server. Select Control -> Start
Up
in the context menu of managed server. Wait until the process is
complete.

4) Ensure that AdminServer and all managed servers (in our
case it is one server) are running (has RUNNING stage). You could
do this, for example, in the WebLogic Administration Console.

Stage 8: Applications
deployment and domain testing.

So all necessary
procedures are complete and our sample domain is ready for ADF applications
deployment. You could simply deploy your applications using WebLogic
Administration Console
or Enterprise Manager Fusion Middleware Console
and you are ready!

Russian-speaking readers could find this article on Russian language in Middleware Technology blog for Russian developer’s community.

Join the discussion

Comments ( 4 )
  • Chris Muir Sunday, August 4, 2013

    Thanks for the detailed post Emin. Here's some supplemental instructions for running this on OSX that might assist other readers:

    Stage 3: Running the fmw_infra_121200.jar in a terminal window

    /usr/libexec/java_home --version 1.7.0 --exec java -jar ./fmw_infra_121200.jar

    Stage 4: Before running the rcu program

    bin $ export DISPLAY=:0

    bin $ export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home

    bin $ ./rcu


  • Emin Askerov Sunday, August 4, 2013

    Chris, thank you for supplements, I will add it into the post.


  • ovais Wednesday, August 5, 2015

    When i have restart my server weblogic could not start

    >

    <Aug 5, 2015 7:07:31 PM PKT> <Notice> <WebLogicServer> <BEA-000365> <Server stat

    e changed to FAILED.>

    <Aug 5, 2015 7:07:31 PM PKT> <Error> <WebLogicServer> <BEA-000383> <A critical s

    ervice failed. The server will shut itself down.>

    <Aug 5, 2015 7:07:31 PM PKT> <Notice> <WebLogicServer> <BEA-000365> <Server stat

    e changed to FORCE_SHUTTING_DOWN.>

    <Aug 5, 2015 7:07:31 PM PKT> <Info> <WebLogicServer> <BEA-000238> <Shutdown has

    completed.>


  • Emin Askerov Monday, October 26, 2015

    Can you please provide more information from the log?


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.