Friendz Corps..

Best Practices and Troubleshooting While installing The SOA11g server

Page | 1

Contents
1 Introduction............................................................................................................. 3 1.1 Order Of Installation Tasks................................................................................3 2 Step 1 : Preparing to Install..................................................................................... 5 2.1 System Requirements....................................................................................... 5 2.2 Install Database................................................................................................ 5 2.2.1 Steps to Install Database (Oracle Database 10g Express Edition)...............5 3 Step 2 : Create Schemas using RCU........................................................................9 3.1 Steps to Create Schemas.................................................................................. 9 4 Step 3 : Install the Oracle WebLogic Server...........................................................23 4.1 Steps to Install WebLogic Server.....................................................................25 5 Step 4 : Install Oracle SOA Suite............................................................................36 5.1 Steps to Install Oracle SOA Suite (11.1.1.2.0).................................................37 6 Step 5 : Apply the Patch Set (11.1.1.3.0)...............................................................45 6.1 Steps to run Patch Set Installer.......................................................................45 7 Step 6 : Create WebLogic Domain and Configure Oracle SOA Suite......................51 7.1 Steps to Create WebLogic Domain and Configure SOA Suite..........................51 8 Post-Installation tasks............................................................................................ 63 8.1 Launching the Server...................................................................................... 63 8.2 Verify the Installation...................................................................................... 64

Page | 2

1 Introduction
Oracle WebLogic Server is a scalable, enterprise-ready Java Platform, Enterprise Edition (Java EE) Application Server. The WebLogic Server infrastructure supports the deployment of many types of distributed applications and is an ideal foundation for building applications based on Service Oriented Architecture (SOA). Complete implementation of the WebLogic Server provides a standard set of APIs for creating distributed applications that can access a wide variety of services, such as databases, messaging services, and connections to external enterprise systems. End-user clients access these applications using Web browser clients or Java clients. WebLogic Server enables enterprises to deploy applications in a robust, secure, highly available, and scalable environment. These features allow enterprises to configure clusters of WebLogic Server instances to distribute load, and provide extra capacity in case of hardware or other failures. Extensive security features protect access to services, keep enterprise data secure, and prevent malicious attacks.

1.1 Order Of Installation Tasks

Page | 3

Step 1 : Prepare the System environment for Installation. If there is no database (supported version), install it. Ensure it is up and running. Step 2 : Create Oracle SOA Suite schemas by running the RCU(Repository Creation Utility). Step 3 : Install the Oracle WebLogic Server. Step 4 : Install Oracle SOA Suite. Step 5 : To upgrade the Oracle SOA Suite Software, run the Patch Set Installer. Step 6 : Run the Configuration Wizard to create the Weblogic Domain and Configure the Oracle SOA Suite.

Page | 4

2 Step 1 : Preparing to Install

2.1 System Requirements
Ensure that your system environment meets the general installation requirements for Oracle Fusion Middleware as well as WebLogic Server, Oracle SOA Suite and RCU. Ensure that there is required hardware and software, minimum disk space and memory and required system libraries, packages, or patches present in the system.

2.2 Install Database

Installation of Oracle SOA Suite requires a database of the supported version. This database must be up and running. It does not have to be on the same system where you are installing the products. The database must also be compatible with Repository Creation Utility (RCU), which is used to create the schemas.

2.2.1 Steps to Install Database (Oracle Database 10g Express Edition)

1. 2. In the Oracle Database 10g Express Edition - Install Wizard welcome window, click Next.

Page | 5

3.

In the License Agreement window, select I accept and then click Next.

4.

In the Choose Destination Location window, accept the default then click Next.

Page | 6

5.

In the Specify Database Passwords window, enter the password to use for the SYS and SYSTEM database accounts. Then click Next.

6.

In the Summary window, review the installation settings, click Install. If not satisfied with the settings click Back and modify the settings as necessary.

Page | 7

7.

In the InstallShield Wizard Complete window, click Launch the Database homepage to display the Database Home Page. Then click Finish.

Page | 8

3 Step 2 : Create Schemas using RCU

Prior to installation, Oracle Fusion Middleware components require the existence of schemas in a database. These schemas are created and loaded in your database using the Repository Creation Utility (RCU).

3.1 Steps to Create Schemas

1. 2. Open cmd prompt. Go to rcuHome\BIN (D:\ofm_rcu_win_11.1.1.3.0_disk1_1of1\rcuHome\BIN) and run rcu.bat file.

3.

Then we will get Welcome Screen of Repository Creation Utility (RCU). Click Next.

Page | 9

4. In Create Repository Screen, select Create and click Next.

5.

Provide the database connection details in the next screen and click Next. Host Name: Specify the name of the machine on which your database resides in the format host.domain.com Port: Specify the database listener port number. The default port number for Oracle databases is 1521. Service Name: Specify the service name for the database. Username: Specify the name of a user with DBA or SYSDBA privileges. Password: Specify the password for your database user. Role: Select the database users role from the drop-down list. The SYS user requires the SYSDBA role.

Page | 10

6.

In the next screen, Checking Prerequisites screen, you might encounter the following Errors.

Page | 11

Ignore it.

Click OK. 7. Next is the Select Components Screen. Select Create a New Prefix. Default is DEV. Select the necessary schemas for the product you want to install. Dependencies are automatically selected. Schemas required for Oracle SOA Suite products : SOA Infrastructure Business Activity Monitoring User Messaging Service

Page | 12

Click Next. 8. A "Checking Prerequisites" screen will appear. If there are errors, details about the error will be displayed at the bottom of the screen. Fix the error messages and click Next again. Some common errors encountered are :

Page | 13

Page | 14

As a result of the above errors, Prerequisite Check for SOA Infrastructure fails.

ERROR :
RCU-6083:Failed - Check prerequisites requirement for selected component: SOAINFRA. Please refer to RCU log at C:\ofm_rcu_win_11.1.1.3.0_disk1_1of1\rcuHome\rcu\log\logdir.2010-08-02_13-50\rcu.log for details. RCU6107:DB Init Param Prerequisite failure for: processes Current Value is 100. It should be greater than or equal to 200. RCU-6092: Component Selection validation failed. Please refer to log at C:\ofm_rcu_win_11.1.1.3.0_disk1_1of1\rcuHome\rcu\log\logdir.2010-08-02_13-50\rcu.log for details.

Page | 15

SOLUTION : Configure the Database in order to get the required value of the parameter- processes using the following Scripts: SQL> connect sys/password as sysdba; Connected.

SQL> alter system set processes = 1000 scope = spfile; System altered.

SQL> commit; Commit complete.

SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down.

SQL> connect sys/password as sysdba; Connected to an idle instance.

SQL> startup ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size Variable Size Database Buffers Redo Buffers 1289996 bytes 213909748 bytes 587202560 bytes 2904064 bytes

Page | 16

Database mounted. Database opened. To see the parameters execute the script given below: SQL> show parameter sessions NAME java_max_sessionspace_size java_soft_sessionspace_limit license_max_sessions license_sessions_warning logmnr_max_persistent_sessions sessions shared_server_sessions TYPE integer integer integer integer integer integer integer VALUE 0 0 0 0 1 1105

------------------------------------ ----------- -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

After fixing the error, click Next. Prerequisite check will be complete.

Page | 17

Click OK. 9. Next is the Schema Passwords screen. Select Use same password for all schemas and provide the password and Confirm it. Click Next.

Page | 18

10. In Map Tablespaces Screen, click Next. .

Page | 19

A "Creating Tablespaces" screen will appear. If there are errors, details of the error will be displayed on the Map Tablespaces Screen.

Fix the error messages and click Next again 11. In the next screen click OK.

Page | 20

12. Next is the Creating Tablespaces Screen. After the tablespaces have been created without errors, click OK.

Page | 21

13. In the Summary Screen, click Create.

14. A "CREATE" screen will appear. If there are errors, some details of the error will be displayed on the Summary Screen.

Page | 22

Fix the error messages and click Next again. After the schemas are created with no errors, click OK . 15. In the Completion Summary Screen, review the information on this screen and click Close.

If problems are encountered during schema creation, you can troubleshoot the issue using the log files. If errors are encountered during a Create operation, or if a Create operation fails for any component, the Cleanup for failed components checkbox appears on the Completion Summary Screen and is selected by default. If selected, RCU will perform cleanup operations for the component that failed during the Create operation. If you choose not to select this checkbox, you can cleanup the failed component at a later time by performing a Drop operation for the failed component(s).

4 Step 3 : Install the Oracle WebLogic Server

At the time of Oracle 11g JDeveloper installation, WebLogic Server gets installed automatically. If you do not already have one, follow the instructions in this section to install Oracle WebLogic Server. Before installation, determine the appropriate installation mode. There are 3 installation modes : graphical mode, console mode, or silent mode.

Page | 23

Graphical mode It is an interactive, GUI-based method for installing. It can be run on both Windows and UNIX systems.

Console mode It is an interactive, text-based method for installing from the command line, on either a UNIX system or a Windows system.

Silent mode It is a non-interactive method of installing. It uses an XML properties file to specify the installation options. It can be run from either a script or from the command line. In this mode we can define the installation configuration only once, and then use that configuration to duplicate the installation on many machines.

Components installed in a typical WebLogic Server installation are : Core Application Server Administration Console Configuration Wizard and Upgrade Framework Web 2.0 HTTP Pub-Sub Server WebLogic SCA WebLogic JDBC Drivers Third-Party JDBC Drivers WebLogic Server Clients WebLogic Web Server Plug-Ins UDDI and XQuery Support Coherence Product Files

Page | 24

Oracle Enterprise Pack for Eclipse

4.1 Steps to Install WebLogic Server

1. 2. Go to the directory that contains the installation program. Double-click the installation file (wls1033_win32.exe). If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages (informational, warning, error, and fatal) about events that occur during the installation process. This type of file can be especially useful for silent installations. To create a verbose log file during installation, include the -log=full_path_to_log_file option in the command line. For example, to create a verbose log file for the Oracle WebLogic Server net installer for Windows,enter: wls1033_win32.exe -log=D:\Oracle\Middleware\logs\server_install.log The path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file.

The installation program begins to install the software. 3. Initial screen is the Welcome screen. The Welcome screen is displayed each time you start the installer Click Next.

Page | 25

4. In Choose Middleware home directory screen, specify the Middleware home directory that will serve as the
central support directory for all Fusion Middleware products installed on the target system, including WebLogic Server. The default Middleware home directory is C:\Oracle\Middleware. Each Fusion Middleware product will be installed in its own product directory in the Middleware home directory. If you already have a Middleware home directory on your system, you can select that directory (recommended) or create another Middleware home directory. If you choose to create a directory by typing a new directory name in the Middleware Home Directory field, the installation program automatically creates one for you. You can also click Browse and select an existing directory from the Middleware Home Directory screen. Sometimes when we select Use an existing Middleware Home option and provide a Middleware Home which contain products whose maintenance level is not compatible with the one being installed, we will get an error. In such a case use Create a new Middleware Home option. Click Next.

Page | 26

5.

In Register for Security Updates screen, specify whether you want to register the Oracle WebLogic Server installation with My Oracle Support. By registering, Oracle Support notifies you immediately of any security updates that are specific to your installation. If you want to register your installation, enter your My Oracle Support email address and your My Oracle Support password. If you want to decline registration, uncheck the I wish to receive security updates via My Oracle Support check box. An Are You Sure? dialog box appears. Click Yes to continue.

Page | 27

6.

Select the installation type. Click Next.

TypicalAll the software components included in your installation program are installed on your
system. Typical installation does not include the Server Examples.

Custom If you do not want to install some of these components, or if you want to install additional
components, perform a Custom installation.

Page | 28

7.

In Choose Products and Components specify the components to be installed by selecting or clearing the appropriate check boxes. Click Next.

Page | 29

8.

JDK Selection screen displays a list of JDKs. This list contains JDKs that are available for (and common across) previous installations of all the selected WebLogic Server components. Select the JDK that you want to install with the product. You can also browse for and select a local JDK (at least 1.6.0_05) installed on your machine. Click Next.

Page | 30

9.

Next is the Choose Product Installation Directories screen. We can accept the default product directories or specify new directories for each product you are installing. The product directories that are listed on this screen depend on the products selected for installation. We may have to specify up to three installation directories, one each for Oracle WebLogic Server, Oracle Enterprise Pack for Eclipse, and Oracle Coherence.

Page | 31

If we are adding components to an existing product installation, confirm the product installation directory. These are the directories in which we previously installed WebLogic Server, Oracle Enterprise Pack for Eclipse, or Oracle Coherence. The selected components are installed in the product installation directory we specified during the initial installation.

Page | 32

10. In Install Windows Service Screen we need to choose whether we want to install the Windows services indicated, specifically the Oracle WebLogic Server Node Manager service. Node Manager is used to monitor, start, and stop server instances in a WebLogic domain. If Yes, enter the Node Manager Listen Port in the appropriate field. The default is 5556. Click Next

Page | 33

11. In Choose Shortcut Location screen, select one of the options and click Next.

All Users Start menu folder

Select this option to provide all users registered on the machine with access to the installed software.

Local User's Start menu folder

Selecting this option ensures that other users registered on this machine do not have access to the installed software.

Page | 34

12. In the Summary screen, review the details and click Next.

13. Once the installation is complete, we get the Installation Complete screen.

Page | 35

5 Step 4 : Install Oracle SOA Suite

Prior to the application of patchset 2 (11.1.1.3.0), it is necessary to install SOA Suite 11.1.1.2.0. If we try to install Oracle SOA Suite 11.1.1.3.0 directly without installing SOA Suite 11.1.1.2.0, we will encounter the following errors : INST-07100 : The Oracle Home provided does not contain Oracle SOA Suite 11.1.1.2.0 INST-07293 : Middleware home location specified does not have the required Oracle Homes installed in it.

Page | 36

Before applying 11.1.1.3.0 to SOA, make sure we have Oracle WebLogic Server version 10.3.3 Some schemas [PORTAL, OID, SOAINFRA..] must be updated in database to bring schemas to 11.1.1.3.0.

5.1 Steps to Install Oracle SOA Suite (11.1.1.2.0)

1. Go to 11g SOA Suite setup folder and then click on setup.exe.

Page | 37

The installer requires the location of a Java Runtime Environment (JRE) on the system.When we installed Oracle WebLogic Server, a JRE was installed on your system. You can use this location (the location of the

jre directory)

to start the installer. JRE is also installed when we install Oracle Jdeveloper. We can also use this location.

Provide the JRE location and press Enter.

Page | 38

This opens the Installer.

Page | 39

2.

Initially we will get the Welcome Screen. Click Next.

3.

Next is the Prerequisite Check screen. If there is a problem, a short error message appears at the bottom of the screen. Fix the error and click Retry to try again. Click Continue to ignore the error and warning messages and continue with the installation. Click Abort to stop prerequisite checking for all components. When finished, click Next to continue.

Page | 40

4. Next is the Specify Installation Location screen. In the Oracle Middleware Home field, specify the absolute path to your existing Oracle Middleware Home directory where WebLogic Server is installed. In the Oracle Home Directory field, specify the directory inside the Oracle Middleware Home where you want to install your products: If we specify a directory that already exists, it must be an empty directory and it must be inside the Oracle Middleware Home. If we specify a new directory, it will be created inside the Oracle Middleware Home. This will be the Oracle Home directory(SOA Oracle Home). Runtime components cannot write to this directory.

Page | 41

5.

Review the information on Installation Summary screen, and click Install to begin the installation.

Page | 42

6.

Next is the Installation Progress screen. Once the installation is complete click Next.

Page | 43

7.

Installation Complete screen summarizes the installation that was just completed. If we want to save this summary information to a text file for future reference, click Save. Click Finish to dismiss the screen.

Page | 44

6 Step 5 : Apply the Patch Set (11.1.1.3.0)

To upgrade the Oracle Fusion Middleware components, use Patch Set installer. Back up Middleware home directory and all sub-directories, along with Domain home and Oracle instance home directories because if patch installation in unexpectedly interrupted, or if we choose to cancel out of the installation before it is complete, it might not be possible to install the patch unless the environment is restored to the previous configuration before running the Patch Set Installer again. There is no deinstallation option with the Patch Set Installer. Before running Patch Set Installer, stop all servers and processes. The Patch Set Installer requires Oracle WebLogic Server version 10.3.3.

6.1 Steps to run Patch Set Installer

1. Go to the directory containing the setup file and run setup.exe.

Page | 45

2.

Provide the JRE location.

Page | 46

3.

Patch Set Installer starts and A Welcome screen appears.

Page | 47

4.

Next is the Specify Installation Location Screen Specify your existing Oracle Middleware home and product Oracle home locations. Click Next to continue.

5.

In Installation Summary Screen, verify the details and click Install.

Page | 48

6.

Installation Progress Screen shows the progress of the installation Once the installation is complete, click Next.

Page | 49

7.

Click Finish to dismiss the screen

Page | 50

7 Step 6 : Create WebLogic Domain and Configure Oracle SOA Suite

After successfully running the installer, configure Oracle SOA Suite using the Oracle Fusion Middleware Configuration Wizard.

7.1 Steps to Create WebLogic Domain and Configure SOA Suite

1. Start the Configuration Wizard config.cmd. This Configuration Wizard is located in SOA_ORACLE_HOME\common\bin.

2.

Next we get the Welcome Screen. Select Create a New WebLogic Domain and click Next.

Page | 51

3.

In Select Domain Source Screen, select Generate a domain configured automatically to support the following products, then select required products. Click Next.

Page | 52

4.

Next is the Specify Domain Name and Location Screen. Specify the following domain information: Domain name: The name of the domain you want to create. The default name is base_domain. Domain location: The absolute path to the directory where this domain should be created. Application location: The absolute path to the directory where applications created in this domain should reside. Click Next.

Page | 53

5.

In Configure Administrator Username and Password Screen, specify the following credentials for your administrator: User name: The name of the administrator for this domain. The default name is weblogic. User password: The administrators password. Confirm user password: Re-enter the administrators password. Description: Enter a description for this user, or leave the default description as is. This field is optional. Click Next.

Page | 54

6.

Next is the Configure Server Start Mode and JDK Screen In the "WebLogic Domain Startup Mode" portion of the screen, Select Development Mode. In the "JDK Selection" portion of the screen, select the JDK that is recommended for your platform in Development Mode. Click Next.

Page | 55

7.

Next is the Configure JDBC Component Schema Screen. Configure the schema information for each data source listed on this screen. When you make changes to any field on this screen, the changes are applied to selected data sources only. The changes are saved automatically as you type. Provide the following information: Vendor: Select the vendor for your database from the drop-down list. Driver: Select the driver type from the drop-down list. Schema Owner: Specify the schema owner for the schema; this is the name of the schema for this component in the following format: prefix_schema-name This information was specified on the Select Components Screen when the schemas were created using RCU. Password: Specify the password for the schema. You specified this password on the Schema Passwords Screen when creating the schemas using RCU DBMS/Service: Specify the service name for your database. This is the database on which the schema resides. Host Name: Specify the name of the machine where your database is running. Port: Specify the database listen port number.

Page | 56

BAM Schema

Page | 57

SOA Infrastructure

User Messaging Service

Page | 58

OWSM MDS Schema

Page | 59

SOA MDS Schema

8.

In Test Component Schema Screen, verify that the connections to your data sources are successful. Click Next.

Page | 60

9.

Next is the Select Optional Configuration Screen. Do not select anything on this screen. Click Next.

Page | 61

10. In Configuration Summary Screen, verify the information and click Create.

11. Next is the Creating Domain Screen. When the domain has been successfully created, click Done to dismiss the Configuration Wizard. The last line in the summary information is the URL of the Administration Server. Make a note of this URL so that you can access the Administration Server after it has been started.

Page | 62

8 Post-Installation tasks
8.1 Launching the Server
To get the deployments up and running, you must start the Administration Server and various Managed Servers. 1. To start the Administration Server, run the startWebLogic.cmd script in the directory where the new domain is created. On UNIX operating systems: MW_HOME/user_projects/domains/domain_name/startWebLogic.sh On Windows operating systems: MW_HOME\user_projects\domains\domain_name\startWebLogic.cmd 2. To start the Managed Servers, run the startManagedWebLogic.cmd script in the bin directory inside the directory where the new domain is created. This command also requires a server name. The servers that need to be started are:

Page | 63

soa_server1 (Oracle SOA Server) bam_server1 (Oracle BAM Server) Example : startManagedWebLogic.cmd soa_server1 http://btp3sb40:7001 startManagedWebLogic.cmd bam_server1 http://btp3sb40:7001

If we do not know the names of the managed servers that need to be started, we can view the contents of the following file : Middleware_Home\user_projects\domains\domain_name\startManagedWebLogic_readme.txt Or, access the Administration Server console at the following URL: http://host:admin_server_port/console (http://btp3sb40:7001/console) Supply the username and password that was specified on the Configure Administrator Username and Password Screen of the Configuration Wizard. Then, navigate to Environment > Servers to see the names of the managed servers.

8.2 Verify the Installation

Start your browser and enter the following URLs: To access the Administration Server: http://host:admin_server_port (http://btp3sb40:7001) To access the Administration Server console: http://host:admin_server_port/console (http://btp3sb40:7001/console) To access Enterprise Manager: http://host:admin_server_port/em (http://btp3sb40:7001/ems)

Page | 64