vipin's blog

This is the final post in continuation for the creation of the weblogic domain with the SOA support. In last two post I described component required and placement of the each artifact required for the creation of the SOA server. Now everything in place and we can start building a server which will support soa. There are two ways a SOA server can be configured 1. All in one Admin server 2. Soa server as a managed server to Admin server. In weblogic we can create a number of managed server under a admin server each of these managed server are like different serving point. In a cluster environment two or more managed server worked as a single unit, to increase availability. Each managed server can be controlled from Admin server and while startup it takes all the configuration related information from the Admin server. While for the study purpose its better to have a all in one admin server which take less resource to run and require less steps to shutdown or start, which we must have to ...

Now we can start with soa specific installation. There is quite confusion over the oracle soa 11.1.1.3.0 installation. The issue is is a 11.1.1.3.0 patchset rather then a complete installer, hence first 1.1.1.2.0 need to be installed and then we need to install 11.1.1.3.0 at the top of it. So we need both the files, that is the reason I mentioned both the files in the prerequisite. 3. SOA Server Installation. 3.1 Unzip the files ofm_soa_generic_11.1.1.2.0_disk1_1of1.zip and ofm_soa_generic_11.1.1.3.0_disk1_1of1.zip both. 3.2 Start your database if not in the running condition. 3.3 Now go to the directory ofm_soa_generic_11.1.1.2.0_disk1_1of1\Disk1 and then click on setup.exe, it will ask you the location of your JDK. JDK is a part of the standard weblogic installation. So check the directory where you have installed the weblogic in the previous step jdk must be there, for me the location is D:\Oracle\MW_HOME\jdk160_21. Paste this location to the command window and pre...