Install Weblogic on RHEL 5.5 with ADF

Basic Requirements

·         X-Windows server (e.g. Cygwin, Xming)

·         Ssh client software (e.g. putty)

·         jdk-6u23-linux-x64-rpm.bin

·         wls1034_generic.jar

·         jdevstudio11114install.bin

Install the 64bit JDK

Download jdk-6u23-linux-x64-rpm.bin

Become root by running the su command and entering the root password.

 Extract and install the contents of the downloaded file.

Change directory to where the downloaded file is located and run these commands to first set the executable permissions and then run the binary to extract and run the RPM file:

              

·         chmod a+x jdk-6u23-linux-x64-rpm.bin

·         ./jdk-6u2323-linux-x64-rpm.bin

The script displays a binary license agreement, which you are asked to agree to before installation can proceed. Once you have agreed to the license, the install script creates and runs the file jdk-6u 23-linux-x64.rpm in the current directory.

Install 64bit Weblogic

Installation documentation http://download.oracle.com/docs/cd/E17904_01/doc.1111/e14142/guimode.htm

Download jar file wls1034_generic.jar (from additional platforms column)File may be named .zip, rename the .zip file to be .jar

Navigate to the JDK bin directory

$ ./java -Xmx1024m -jar wls1034_generic.jar -Djava.io.tmpdir=tmpdirpath

1. Use a custom install and deselect the following which are not needed:
• Workshop
• Web 2.0 http pub-sub server
• Weblogic Web Server Plugins
• UDDI and Xquery Support
• Server Examples
2. Select the JVM  
3. Complete the install -sticking to the defaults,
• Uncheck the Quickstart option on the last screen

Install ADF option

Download jdevstudio11114install.bin

$ ./ jdevstudio11114install.bin

1. Choose existing middleware home in the home type and select the home that you just created for the Weblogic server install
2. On the product selection screen select ADF Runtime
3. Run the install.

Configuration

1. Now run the Configuration Wizard (config.sh)
• Optionally select the quickstart option
2. Create a new WebLogic domain
• Choose the first option on the next screen to pre-configure the domain with
1.  WebLogic Server
2. ADF (JSF)
• Create the admin user as weblogic /<<password>>
•   Choose production mode
• On the next screen  customize the ports - choose yes
1. Assign the server to use ports 80 and 81
• Just choose next on the RDBMS security store page
• On the configure the Admin Server page
1. Set the port to 81
• On the next page Add one managed server called <<MyManagedServer>>
1. Set the port to 80
• No need for clustering in this case so next through the cluster page
• Create a machine on the next screen.
1. If you are using a machine with a known DNS name and fixed IP address use that.
• Next through to the summary screen
• In the Create WebLogic Domain screen change the name of the domain to <<your-domain-name>> and press create.
• Finish the wizard.

Start the Admin Server

When installing Weblogic on Red-Hat x86_64 using 32-bits JVM, the Weblogic can't find the performance pack and therefore can't enable native network IO.Copy libmuxer.so into the ORACLE_HOME/wlserver_10.3/server/native/linux/x86_64 from ORACLE_HOME /wlserver_10.3/server/native/linux/server/native/linux/i686

We need a file boot.properties to get the server to start in production mode

o   Create a security directory under the Managed Server Name in Domains etc.

ORACLE_HOME/user_projects/domains/base_domain/servers/AdminServer

§  Create a directory called security

§  Create a file called boot.properties

·         username=Weblogic
password=<password>

Repeat for each managed server

Now from the command line start the Admin Server

$ORACLE_HOME/ wlserver_10.3/server/bin /setWLSEnv.sh

Navigate to $ORACLE_HOME/user_projects/domains/base_domain

/.nohup startWebLogic.sh -Djava.awt.headless=true &

This will start the admin-server in the background; the –Djava.awt.headless=true switch ensures the application displays graphics correctly.

If the boot.properties files is not present the server will fail to start, you will be prompted to enter the Weblogic user but not the password. In order to display the password append
 -Dweblogic.management.allowPasswordEcho=true to the startWebLogic command

Ø  Once the Admin-Server is started run the console

Ø  http://<<servername/IP>>:81/console

Ø  Log in    Weblogic/<<password>>

Ø  In the console, click deployments in the Domain Structure tree

o   adf.oracle.domain(1.0,11.1.1.0.0)

o   jsf(1.2,1.2.7.1)

o   jstl(1.2,1.2.0.1)

Ø  Press Lock and edit in the “change centre” box at the top left of the screen.

Ø  Drill down through each of the Deployments and select the Targets tab. For each one check the checkbox for both the Managed-Server and the Admin-Server

Ø  Save each deployment change as you make it

Ø  Finally press the Activate Changes button

Start the Managed-Server

Navigate to $ORACLE_HOME/user_projects/domains/base_domain/bin

nohup ./startManagedWebLogic.sh "<<MANAGED-SERVER>>" "http://host-name:81" &

Now we can run ADF applications on both servers

When we deploy an app it will prompt to deploy to either the Admin Server or the managed server.

• Deploy to the Admin Server in addition to the Managed Server to ensure the security files are installed