The GroundBlog By Duncan Mills
Duncan Mills's WebLog from GroundSide

Installing and Setting up WebLogic 10.3 Production for Running ADF Applications

The process of setting up and running WebLogic Server to handle ADF 11g applications appears to be causing some confusion so this blog entry documents the basic steps required to setup and configure WebLogic (both and Admin server and a Managed server) for ADF Applications.
This is not the official documentation, but rather it's the basic steps I followed this evening to set up a configuration from scratch. So it's rough but it does work.

1. As prerequisites I’m using WebLogic 10.3 downloaded from OTN and the latest version of JDeveloper (11.1.1.0.1 build 5188)
2. Install WebLogic into a new BEA home. I’m doing this on M/S Windows and my home directory will be C:\builds\WLS10_3
3. While installing you can go for a custom install and deselect the following which you won’t need:
   • Workshop
   • Web 2.0 http pub-sub server
   • Weblogic Web Server Plugins
   • UDDI and Xquery Support
   • Server Examples
4. Select the JVM that you want to use. Here I’m just using JRockit
5. Don’t bother to install the node manager service. If you use it to start a managed server then ADF apps will not run because the classpath is somehow not set up correctly - so you need to start the admin server and managed servers from the command line.
6. Complete the install sticking to the defaults, but uncheck the Quickstart option on the last screen
7. Now run the JDeveloper install on the target machine
8. Choose existing middleware home in the home type and select the home that you just created for the server install (e.g. C:\builds\WLS10_3 in my case)
9. On the product selection screen make sure that both JDeveloper Studio and ADF Runtime are installed.
10. Run the install.
11. Now run the Configuration Wizard from the start menu
12. Create a new WebLogic domain
13. Choose the first option on the next screen to pre-configure the domain with both WebLogic Server and ADF
14. Create the admin user as weblogic / weblogic (or whatever). As we’re trying to emulate a production instance here choose production mode and JRockit as the VM
15. On the next screen you can choose to customize things like the ports - so choose yes there so we can reassign out server to use ports 80 and 81
16. Just choose next on the RDBMS security store page
17. On the configure the Admin Server page set the port to 81
18. On the next page Add one managed server called ManagedServer and set the port to 80
19. No need for clustering in this simple case so next through the cluster page
20. Create a machine on the next screen. If you are using a machine with a known DNS name and fixed IP address use that. or just create a arbitrary name such as LocalMachine if this is all for local testing
21. Next through to the summary screen
22. In the Create WebLogic Domain screen change the name of the domain to ADFDomain and press create.
23. Finish the wizard.
24. Now from the command line start the AdminServer with the script (in my case): C:\builds\WLS10_3\user_projects\domains\ADFDomain\bin\startWeblogic.cmd
25. You need to specify the username and password if you defined the Domain in production mode.
26. Once the AdminServer is started run the console at http://localhost:81/console
27. Log in.
28. In the console, click deployments in the Domain Structure tree You should see the following Deployments:
    • adf.oracle.domain(1.0,11.1.1.0.0)
    • jsf(1.2,1.2.7.1)
    • jstl(1.2,1.2.0.1)
29. Press Lock and edit in the change center box at the top left of the screen.
30. Drill down through each of the Deployments and select the Targets tab. For each one check the checkbox for both the ManagedServer and the AdminServer
31. Save each deployment change as you make it
32. Finally press the Activate Changes button when they are all done.
33. Now to start the ManagedServer - use the command line for this: “C:\builds\WLS10_3\user_projects\domains\ADFDomain\bin\startManagedWeblogic.cmd ManagedServer http://localhost:80”
34. Now we can run ADF applications on both servers
35. Now from JDeveloper you will be able to create a Server connection when you deploy the application using port 81 (the AdminServer) and the domain name of ADFDomain.
36. When you deploy an app it should prompt to deploy to either the AdminServer or the managed server.