Installing Oracle SOA Suite 11gR1
From InstallationWiki
| Official Page |
| Project Documentation |
| Download |
|
Contents |
[edit] Checking your installation
If you already have SOA Suite and JDeveloper installed, confirm that you have the correct version and configuration by following the steps in the section below called Testing your installation. In addition, you may want to complete the items in the section called Additional actions. Finally, you must complete the section called Configuration to do the tutorial.
[edit] What you will need and where to get it
Before you can begin, you need to check your machine, download installation files, and check your database, browser, and JDK versions. Follow the instructions in this section carefully for a successful install.
[edit] Memory and Disk Space requirements
This installation requires 3 GB or more available memory. If you have less memory, try separating the installation of the database, the servers, and JDeveloper onto different machines.
The installation process requires about 12 GB of disk space. After installation, you can delete the files used by installation to save about 4 GB.
As you can see, you are installing a lot of software with a large memory and disk footprint. Running your disk defragmentation program now, before you start downloading and installing, can significantly improve install time as well as performance and disk space usage later on.
[edit] Downloading files
Download all the software to get started.
1. In the following steps, save all downloaded files to c:\stageSOA. This document assumes that path. If you save them somewhere else then make sure there are no spaces in your path and adjust accordingly when c:\stageSOA is referenced in this document.
2. Go to: http://www.oracle.com/technology/products/soa/soasuite/ index.html, and download the following from SOA Suite 11g Release 1 (11.1.1.1.0) to c:\stageSOA:
- WebLogic Server:
wls1031_win32.exe
- Repository Creation Utility:
ofm_rcu_win32_11.1.1.1.0_disk1_1of1.zip
- SOA Suite:
ofm_soa_generic_11.1.1.1.0_disk1_1of1.zip
- JDeveloper Studio, base install:
jdevstudio11111install.jar
3. Unzip the SOA Suite ZIP file to c:\stageSOA.
4. Unzip the RCU ZIP file to c:\stageSOA.
5. Additional Files needed:
- Tutorial Files: In Tutorial 3, you were directed to download the files needed for this tutorial. Do that now as some are used during installation. You can download the files from
here: http://www.oracle.com/technology/products/soa/ soasuite/11gthetutorial.html. Unzip the tutorial ZIP file to c:\stageSOA.
- SOA Extension for JDeveloper: You will get this later using the JDeveloper update option.
- Oracle Service Bus: When you are ready to do the Oracle Service Bus (OSB) lab, you will download the install file to install OSB.
[edit] Checking your database
Having your database up and running is the most important pre-requisite for installing SOA Suite.
1. Read the following bulleted requirements carefully to be sure you are ready to begin the SOA Suite installation:
- You need one of:
i. Oracle XE Universal database version 10.2.0.1 ii. Oracle 10g database version 10.2.0.4+ iii. Oracle 11g database version 11.1.0.7+
- You cannot use any other database version in 11gR1 (certification of additional databases is on the roadmap). Specifically, you cannot use XE Standard, it must be Universal.
- We have seen problems with installing XE when a full 10g database is already installed in the environment. The
Windows registry sometimes gets the database file location confused. It is recommended to pick one or the other to avoid such issues.
- If you need to uninstall XE, make sure that you follow the instructions in Oracle Database Express Edition Installation Guide 10g Release 2 (10.2) for Microsoft Windows Part Number B25143-03, Section 7, Deinstalling Oracle Database XE (http://download.oracle.com/docs/cd/B25329_01/doc/ install.102/b25143/toc.htm).
- If you need to uninstall 10.2, be sure to follow the instructions in Oracle Database Installation Guide 10g Release 2 (10.2) for Microsoft Windows (32-Bit) Part Number B14316-04, Section 6, Removing Oracle Database Software (http://download. oracle.com/docs/cd/B19306_01/install.102/b14316/ deinstall.htm).
2. Optional: Install OracleXEUniv.exe recommended for a small footprint database. Make sure that you read step 1 above before installing. You can get XE from here: http://www.oracle.com/technology/products/database/ xe/index.html.
|
When you are using XE, you will see a warning when you install the database schema that this database version is too old. You can safely ignore this warning as it applies only to production environments. |
3. If needed, configure Oracle XE Universal.
When you are using Oracle XE, you must update database parameters if you have never done this for your database installation. You only have to do this once after installing. Set the processes parameter to >=200 using the following instructions.
[mailto:welcome1@XE sqlplus] sys/welcome1@XE as sysdba <SQL> show parameter session <SQL> show parameter processes <SQL> alter system reset sessions scope=spfile sid='*'; SQL> alter system set processes=200 scope=spfile; <SQL> shutdown immediate <SQL> startup <SQL> show parameter session <SQL> show parameter processes
| Administrative Tools | Services dialog after setting up your parameters. |
[edit] Checking your browser
Oracle SOA Suite 11gR1 has specific browser version requirements.
1. Enterprise Manager requires Firefox 3 or IE 7.
Firefox 3 get a portable version, such as the one available from http://portableapps.com, if you want it to co-exist peacefully with your Firefox 2 installation. Firefox 2 and IE 6 are not supported and will not work.
2. BAM requires IE 7.
Beware of certain IE 7 plugins that can create conflicts (a few search plugins have proved to be incompatible with BAM).IE 8 is not supported with 11gR1 (but is on the roadmap). IE 6 has a few issues and Firefox will not work with BAM Studio.
[edit] Checking your JDK
If you are going to install WebLogic server and JDeveloper on the same machine, you will use the JDK from WebLogic for JDeveloper too. However, if you are going to install on two machines, you need Java 1.6 update 11 JDK for JDeveloper.
1. JDK 1.6 update 11 from the Sun downloads page:
[http://java.sun.com/ http://java.sun.com/products/archive/]
You must use Java 1.6 update 11. Update 12 does not work.
[edit] Installing Admin Server and Managed Servers
Now that you have verified that everything is ready, you can begin installation.
[edit] Installing WebLogic Server
First, you install Oracle WebLogic Server.
1. To install WebLogic Server, open a command window and enter:
cd c:\stageSOA wls1031_win32.exe
2. When the Welcome screen for the install wizard comes up, click on Next.
3. Select Create a new Middleware Home and enter:
C:\Oracle\Middleware\home_11gR1.
4. This document assumes that path. If you use a different middleware home then adjust accordingly when C:\Oracle\Middleware\home_11gR1 is referenced throughout this document.
5. Click on Next.
6. Enter email address to register for security alerts or deselect the checkbox and decline whichever you prefer and click on Next.
7. Select Typical, and click on Next.
8. Review installation directories.
9. Click on Next.
10. Select "All Users" Start Menu folder and click on Next.
11. Review Summary.
12. Click on Next to start the installation process. Installation takes about three minutes.
13. When the installation is complete, deselect the Run Quickstart checkbox and click on Done.
[edit] Dropping the existing schema
If this is the first time you are installing, you do not need to go through this step and you should jump ahead to the Configuring schema step. Otherwise, if you are reinstalling, continue with these steps to drop your existing schema first. If you would like to keep your existing schema, jump ahead to the Configuring schema step and use a new schema prefix when prompted.
1. To drop your existing schema, copy the following into a command window:
cd c:\stageSOA\rcuHome\bin rcu.bat
2. The bat command returns to the prompt immediately and after a few seconds, the Repository Creation Utility opens.
3. On the Welcome screen, click on Next.
4. Select Drop.
5. Click on Next.
6. Complete the database information.
7. Click on Next.
8. The pre-requisites are reviewed. When completed, click on OK. The utility moves to the next page with a slight delay, just wait for it.
9. The utility finds the existing schema and offers the drop-down list of all prefixes. Check that the prefix is correct and review the schema.
10. In this example, we are dropping the schema with the SH prefix.
Click on Next.
11. On the drop schema warning, click on OK.
12. The pre-requisites for this step are reviewed. When completed, click on OK
to move to the next page with a slight delay, just wait for it.
13. Click on Drop to drop the schema. This takes a few minutes.
14. When it is finished, click on Close.
[edit] Configuring schema
Now, create the database schema for the BAM and SOA servers.
1. To create the new schema, open a command window and enter the following:
cd c:\stageSOA\rcuHome\bin rcu.bat
2. The bat command returns to the prompt immediately and, after a few seconds, the Repository Creation Utility opens (if you just ran the utility to drop the schema, it opens the second time much more quickly).
3. On the Welcome screen, click on Next.
4. Select Create and click on Next.
5. Enter the database information.
6. Click on Next.
7. If you are using XE, you will see a warning at this point that this version is too old. You can safely ignore this warning as it applies only to production environments.
8. The pre-requisites are reviewed. When complete, click on OK. The utility moves to the next page with a slight delay, just wait for it.
9. On the Select Components screen, enter DEV in the field for creating a new prefix.
10. Select the component SOA Infrastructure. Dependent schemas are selected automatically.
11. If you choose to select other components, these install instructions may not match your install experience. Also, you may have to increase processes in XE (you will get a message telling you what is required).
12. Click on Next.
13. The pre-requisites for this step are checked. When completed, click on OK.
14. Select the radio button to Use the same password for all schemas. Enter a schema password. The password welcome1 is assumed in this document
but you should choose your own secure password or a different one for each schema and be sure to record your passwords as you will need them later.
15. Click on Next.
16. Review the tablespaces and schema owners for the components.
17. Accepting the defaults, click on Next, and then click on OK to create the tablespaces.
18. When the pre-requisites for this step are completed, click on OK.
19. Click on Create to create the tablespaces. This takes about two minutes.
20. When completed, click on Close.
[edit] Installing SOA
Once the database is configured, you can install the SOA server into the Oracle Home
on the WebLogic server.
1. In a command window, enter:
cd c:\stageSOA\soa\Disk1 setup -jreLoc C:\Oracle\Middleware\home_11gR1\jdk160_11
2. When the install wizard Welcome screen comes up, click on Next.
3. Wait for the pre-requisite check to complete (it's quick!).
4. Click on Next.
5. On the Specify Installation Location screen, select the middleware home:
C:\Oracle\Middleware\home_11gR1.
6. Enter Oracle home: Oracle_SOA1. If you use a different Oracle home, then adjust accordingly when Oracle_SOA1 is referenced throughout this document.
7. Click on Next.
8. Review Summary.
9. Click on Install.
10. Wait for the installation to complete it takes a few minutes.
11. Click on Finish.
[edit] Creating Domain
From the Oracle Home location, you configure the WebLogic server domain for the SOA and BAM servers.
1. In a command window, enter:
cd C:\Oracle\Middleware\home_11gR1\Oracle_SOA1\common\bin config.cmd
2. When the configuration wizard's Welcome screen comes up, select Create a new WebLogic domain, and then click on Next.
3. Select Generate a domain and select SOA Suite, Enterprise Manager, and Business Activity Monitoring. Dependent products are selected automatically.
4. Click on Next.
5. Enter the domain name: domain1.
6. Click on Next.
7. Enter the user name as weblogic and a password. The password welcome1 is assumed in this document but you should choose your own secure password and remember it for later in the document when the password is referenced.
8. Click on Next.
9. Select the Sun SDK 1.6_11 and leave Development Mode checked.
10. Click on Next.
11. On the Configure JDBC Component Schema screen, you select the components that you want to change, and then enter the property value for those components. First, select all of the components and enter welcome1 for the password in the Schema Password field.
12. With all of the checkboxes selected, enter the Service, Host, and Port values.
13. Now, look at the table. Review the Schema Owner column and confirm that the values are the same as what you configured in the Configure Schema section when you ran the RCU. Go back and review the screenshots in that section of this document for the schema owners if you do not remember them.
14. Complete the following if the schema owners need to be updated:
i. Deselect all the component checkboxes. ii. Select BAM Schema only. iii. Enter the Schema Owner for BAM. iv. Next, deselect BAM Schema and select the next one. v. Enter the schema owners one-by-one. vi. Continue until all schema owners are entered.
15. Click on Next.
16. The data source connections are all tested.
17. If all are successful, click on Next, otherwise click on Previous and correct any errors.
18. Click on Next once more, accepting defaults (no optional configurations), and you reach the Configuration Summary screen.
19. Click on Create.
20. Wait for the creation to finish it takes just a minute.
21. Click on Done.
[edit] Installing JDeveloper and SOA Composite Editor
Now that your servers are install JDeveloper and the JDeveloper extension for SOA Composite Editor.
[edit] Installing JDeveloper
After installing the servers, you can install the JDeveloper IDE.
|
If you are installing JDeveloper on a machine that is not the same as your WebLogic server installation, you must have installed the JDK 6 update 11 first. See the pre-requisites section for download location. |
1. Open a command window and enter (if you copy/paste, make sure there is no space after the = sign and eliminate trailing spaces):
set JAVA_HOME=C:\Oracle\Middleware\home_11gR1\jdk160_11 cd c:\stageSOA
%JAVA_HOME%\bin\java.exe -jar jdevstudio11111install.jar
You will see a message that the JAR is extracting:
%JAVA_HOME%\bin\java.exe -jar jdevstudio11111install.jar
Extracting 0%..........................
When it reaches 100%, the installation wizard will open. This takes a few minutes.
| If you see the splash screen briefly but then you do not see the extracting message and the installation wizard does not open, it's probably because the Java is the wrong version. Enter %JAVA_HOME%\bin\java.exe version to see the version. It must be version 1.6_11. |
Complete the installation wizard as follows
| Installing JDeveloper also installs an embedded WebLogic Server that you can use for testing Java applications. You will use this in one of the labs |
.
2. Welcome Screen click on Next.
3. Choose Middleware Home Directory: select Create a new Middleware Home and enter C:\Oracle\Middleware\jdev_11gR1. This document assumes that path. If you enter something else, then adjust accordingly when C:\Oracle\Middleware\jdev_11gR1 is referenced.
4. Click on Next.
5. Choose Install Type as Complete, and then click on Next.
6. JDK Selection: you will see your JAVA_HOME.
7. Click on Next.
8. Confirm Product Installation Directories. You should see:
Middleware Home Directory: C:\Oracle\Middleware\
jdev_11gR1
JDeveloper and ADF: C:\Oracle\Middleware\jdev_11gR1\
jdeveloper
WebLogic Server: C:\Oracle\Middleware\jdev_11gR1\
wlserver_10.3
9. Click on Next.
10. Choose Shortcut location: "All Users", and then click on Next.
11. Review Installation Summary.
12. Click on Next and the installation starts.
13. Wait for the installation to complete a few minutes.
14. When installation completes, deselect Run Quickstart and click on Done.
[edit] Updating JDeveloper with latest SOA
SOA design time in JDeveloper requires a JDeveloper extension called SOA Composite Editor. While this is normally updated over the network when using release-level software, you can also perform the update manually if you have the extension file. JDeveloper periodically prompts you to accept an automatic network update. Since this is released software, you have the option to click on OK to update to a newer version. The SOA extension is about 230 MB and may take some time
to download.
1. Start JDeveloper Studio 11.1.1.1.0 from the Windows Programs menu: Oracle Fusion Middleware 11.1.1.1.0 or run C:\Oracle\Middleware\ jdev_11gR1\jdeveloper\jdeveloper.exe.
During startup, select the following when prompted:
2. Select Default Role, deselect Show this dialog every time, and click on OK.
3. Click on No to "Migrate from previous release"
4. If you are prompted to select file extensions to associate with JDeveloper, deselect everything or select the ones you would like for your machine and continue.
5. After starting JDeveloper, wait for the Integrated Weblogic Domain to be created. This domain is created the first time you run JDeveloper after installation. It is not used by SOA. Watch for the completion message for setting up the domain in the JDeveloper Messages log window at the bottom of the JDeveloper IDE:
[12:37:11 PM] Creating Integrated Weblogic domain... [12:38:05 PM] Extending Integrated Weblogic domain... [12:38:14 PM] Integrated Weblogic domain processing completed successfully.
Now you can update the SOA Composite Editor extension. These instructions show you how to update the extension over the network.
1. Select Help | Check For Updates; click on Next.
2. Select Search Update Centers and select Oracle Fusion Middleware Products.
3. Click on Next. The system will search the update center for extensions.
4. From the list of extensions, select Oracle SOA Composite Editor and click on Next to begin downloading. The extension is about 230 MB and takes a few minutes to download.
5. When the extension has finished downloading, it is listed with the version number detail.
6. Confirm that the SOA Composite Editor version matches the version number detail as shown: 11.1.1.0.0.52.19.
|
The Update Center provides the most recent version of the SOA Composite Editor that is compatible with your version of JDeveloper and you may have a newer version than the one listed here. The last two numbers, 52.19, refer to the version that was released in July 2009. If the Update Center gives you a newer version, take note of the version number for verification in the step below. |
7. Click on Finish.
8. Restart JDeveloper when prompted. You will say No again to Migrate from previous release question as JDeveloper starts up.
9. When JDeveloper is running again, go to Help | About and
confirm the JDeveloper version is as shown: JDEVADF_11.1.1.1.0_
GENERIC_090615.0017.5407.
10. Select the Version tab, and confirm the SOA Composite Editor was installed properly by confirming the version: 11.1.1.0.0.52.19, or the version you noted above.
Additional actions
In the following section, you will be performing additional configuration that is optional but will greatly improve performance and usability in the context of the development work you are about to start with the tutorial.
Setting memory limits
Review the memory settings. This value is dependent on your machine resources and may need to be adjusted for your machine. Allocating less memory for startup will give you better performance on a machine with less memory available. This value is appropriate for a 3 GB memory machine or less.
1. Edit the SOA domain environment file found here (make sure you have the SOA Domain environment file):
C:\Oracle\Middleware\home_11gR1\user_projects\domains\ domain1\
bin\setSOADomainEnv.cmd
2. Set memory values:
set DEFAULT_MEM_ARGS=-Xms512m -Xmx512m
Starting and stopping
Now it's time to start your servers. You can start them using the provided script or you can start them separately. Instructions for both methods are included.
Starting
First set boot.properties and then start the servers.
1. Before you start, set the boot properties so you are not prompted to log in during server startup. Copy C:\po\bin\boot.properties to C:\Oracle\ Middleware\home_11gR1\user_projects\domains\domain1.
2. Edit the copied file to reflect the password for your configuration (entered during domain configuration). The first time the server is started this file
is encrypted and copied to the server locations.
You can start the servers one at a time or you can use the start_all script to start the admin and SOA managed servers (not BAM). To start them one at a time instead, skip to step 6.
3. Copy the startup script to the Oracle directory:
C:\po\bin\start_all.cmd to C:\Oracle\Middleware
4. Edit the copied file to reflect your environment.
5. Open a command window and start your servers as shown. You must specify how many seconds to wait after starting the admin server before starting the managed server. The admin server must be in the RUNNING state before the managed server starts (see the following screenshot). Try 180 seconds and adjust as necessary. You will need more time the first time you start after a machine reboot than for subsequent restarts:
cd C:\Oracle\Middleware start_all.cmd 180
Your servers are now starting automatically so you can skip steps 6-10. Jump to step 12 to continue.
To start the servers manually, continue with the following steps.
6. Open three command windows, one for the WebLogic admin server, one for the SOA managed server, and one for the BAM managed server (only start BAM when you need it for a BAM lab).
7. Start the Admin Server first:
cd C:\Oracle\Middleware\home_11gR1\user_projects\domains\domain1 startWebLogic.cmd
8. Wait for the Admin Server to finish starting up. It takes a few minutes watch for status RUNNING in the log console window:
9. Start the SOA managed server in the second command window. This start script is in the bin directory. You can also run it directly from the bin directory:
cd C:\Oracle\Middleware\home_11gR1\user_projects\domains\domain1 bin\ startManagedWebLogic.cmd soa_server1
10. When prompted, enter the username weblogic and password welcome1. If you did step 1 and set boot.properties, you will not be prompted. The server is started when you see the message, INFO: FabricProviderServlet.stateChanged SOA Platform is running and accepting requests.
11. Start the BAM managed server in the third command window do this only when needed for the BAM lab:
cd C:\Oracle\Middleware\home_11gR1\user_projects\domains\domain1 bin\ startManagedWebLogic.cmd bam_server1
12. When prompted, enter the user name weblogic and password welcome1. If you did step 1 and set boot.properties, you will not be prompted. Watch for the RUNNING status.
Console URLs Log in with weblogic/welcome1 for all consoles:
Weblogic console: [http://localhost:7001/console http://localhost:7001/console] Enterprise Manager console: [http://localhost:7001/em http://localhost:7001/em] SOA worklist:[http://localhost:8001/integration/worklistapp http://localhost:8001/integration/worklistapp] B2B console: [http://localhost:8001/b2b http://localhost:8001/b2b] BAM (must use IE browser): [http://localhost:9001/OracleBAM http://localhost:9001/OracleBAM]
Stopping servers
Whenever you need to stop the servers complete the following:
1. Stop the managed servers first by entering Ctrl+C in the command window.
Wait until stopped.
2. Stop the admin server by entering Ctrl+C in the command window.
WebLogic Server console settings
There are two suggested changes to make in the WebLogic Server console.
First, you will be viewing application deployments often using the WebLogic server console. This is a lot more convenient if you change the settings not to show libraries as this makes the list a lot shorter and you can find what you need more quickly.
1. Start the WebLogic Admin Server (WLS) if it is not already running. 2. Log in to the WLS console [http://localhost:7001/console http://localhost:7001/console]. 3. Click on Deployments in the left navigation bar. 4. Click on Customize this table at the top of the Deployments table. 5. Change the number of rows per page to 100 (there are only about 30). 6. Select the checkbox to exclude libraries and click on Apply.
Second, when the server is started, internal applications like the WLS console are not deployed completely and you see a slight delay when you first access the console. You saw this delay just now when you first accessed the console URL. You can change this behavior to deploy internal applications at startup instead and then you don't get the delay when you access the console. This is convenient for demos (if you want to show the console) and also if you tend to use the console each time you start up the server.
1. Click on domain1 in the left navigation bar in the WLS console. 2. Click on Configuration | General tab. 3. Deselect Enable on-demand deployment of internal applications checkbox. 4. Click on the Save button.
EM settings for development
The Enterprise Manager can provide different levels of information about composite runtime instances based on a property setting. During development, it is helpful to have a higher setting. These settings are not used on production machines except when specifically needed for debugging purposes as there is a performance cost.
1. Start your servers if they are not already running.
2. Log in to the EM console at [http://localhost:7001/em http://localhost:7001/em].
3. Right-click on the soa-infra (soa_server1) in the left navigation bar to open the SOA menu and select SOA Administration | Common Properties.
4. Select Audit Level: Development and select the checkbox for Capture
Composite Instance State.
5. Click on Apply and click on Yes.
If you need to uninstall JDeveloper and servers If you need to uninstall everything, complete the following:
1. First save anything from C:\Oracle\Middleware\jdev_11gR1\
jdeveloper\mywork that you want to keep as this directory will be deleted.
2. Run Uninstall from the program menu to completion for both JDeveloper and WLS.
3. Delete C:\Oracle\Middleware\jdev_11gR1 and C:\Oracle\Middleware\ home_11gR1. If you get an error message about not being able to delete because a name or path is too long, change the names of the composite directories within home_ 11gR1\user_projects\domains\domain1\ deployed-composites to a\b\c\d and try deleting again.
4. Delete program groups from C:\Documents and Settings\All Users\ Start Menu\Programs\:
Oracle Fusion Middleware 11.1.1.1.0 Oracle SOA 11g - Home1 Oracle WebLogic
5. Complete the Dropping existing schema section earlier in this tutorial to clean up the database.
[edit] Source
The source of this content is Chapter 4: Installing Oracle SOA Suite 11gR1of Getting Started With Oracle SOA Suite 11g R1– A Hands-On Tutorial by Heidi Buelow, Manas Deb, Jayaram Kasi, Demed L???Her, Prasen Palvankar(Packt Publishing, 2009).
