Oracle® Fusion Middleware

Installation Guide for Application Developer

11g Release 1 (11.1.1)

E14827-02

November 2009

Oracle Fusion Middleware Installation Guide for Application Developer 11g Release 1 (11.1.1)

E14827-02

Copyright © 2009, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Kevin Hwang

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Intended Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Installing Application Developer

- 1.1 Preparing to Install

- 1.1.1 System Requirements and Certification

- 1.1.2 Create Schemas for Application Developer

- 1.1.2.1 Check for Supported Database

- 1.1.2.2 Create the Schemas

- 1.1.3 Install Oracle WebLogic Server and Create the Middleware Home

- 1.2 Install and Configure Java Access Bridge (Windows Only)

- 1.3 Installing on DHCP Hosts

- 1.3.1 For UNIX Platforms

- 1.3.2 For Windows x86 Platforms

- 1.3.3 Installing a Loopback Adapter (Windows Only)

- 1.3.4 Removing a Loopback Adapter (Windows Only)

- 1.4 Installing on a Non-Networked Computer

- 1.5 Installing on a Multihomed Computer

- 1.6 Using Custom Port Numbers

- 1.7 Installation Instructions

- 1.7.1 Starting the Installer

- 1.7.2 Installation Log Files

- 1.7.3 Inventory Screens (UNIX Only)

- 1.7.4 Installation Screens and Instructions

2 Configuring Application Developer

- 2.1 Configuration Instructions

- 2.1.1 Starting the Configuration Wizard

- 2.1.2 Configuration Log Files

- 2.1.3 Creating a New Domain

- 2.1.4 Extending an Existing Domain

- 2.1.5 Configuration Wizard Optional Configuration Screens

- 2.1.5.1 Administration Server Options

- 2.1.5.2 Managed Server, Clusters and Machines Options

- 2.1.5.3 Deployments and Services Options

- 2.1.5.4 JMS File Store Options

- 2.1.5.5 RDBMS Security Store Options

- 2.2 Applying Java Required Files (JRF)

- 2.3 Starting the Administration Server

- 2.4 Verifying the Installation

3 Deinstalling Application Developer

- 3.1 Deinstallation Instructions

- 3.1.1 Stopping Oracle Fusion Middleware

- 3.1.2 Removing the Application Developer Schemas

- 3.1.2.1 Starting RCU

- 3.1.2.2 Instructions for Dropping the Application Developer Schemas

- 3.1.3 Removing Application Developer

- 3.1.3.1 Starting the Deinstaller

- 3.1.3.2 Deinstallation Screens and Instructions

- 3.1.4 Removing Oracle WebLogic Server

- 3.1.5 Removing Oracle JDeveloper

- 3.1.6 Removing Program Groups (Windows Only)

- 3.2 Reinstallation

A Application Developer Installation Screens

- A.1 Specify Inventory Directory Screen (UNIX Only)

- A.2 Inventory Location Confirmation Screen (UNIX Only)

- A.3 Welcome Screen

- A.4 Prerequisite Checks Screen

- A.5 Specify Installation Location Screen

- A.6 Installation Summary Screen

- A.7 Installation Progress Screen

- A.8 Installation Completed Screen

B Application Developer Configuration Screens

- B.1 Welcome Screen

- B.2 Select a WebLogic Domain Directory Screen

- B.3 Select Domain Source Screen

- B.4 Select Extension Source Screen

- B.5 Specify Domain Name and Location Screen

- B.6 Configure Administrator Username and Password Screen

- B.7 Configure Server Start Mode and JDK Screen

- B.8 Configure JDBC Component Schema Screen

- B.9 Test Component Schema Screen

- B.10 Select Optional Configuration Screen

- B.11 Configure Administration Server Screen

- B.12 Configure Managed Servers Screen

- B.13 Configure Clusters Screen

- B.14 Assign Servers to Clusters Screen

- B.15 Create HTTP Proxy Applications Screen

- B.16 Configure Machines Screen

- B.17 Assign Servers to Machines Screen

- B.18 Target Deployments to Servers or Clusters Screen

- B.19 Target Services to Servers or Clusters Screen

- B.20 Configure JMS File Stores Screen

- B.21 Configure RDBMS Security Store Database Screen

- B.22 Configuration Summary Screen

- B.23 Creating Domain Screen

C Application Developer Deinstallation Screens

- C.1 Welcome Screen

- C.2 Deinstall Oracle Home Screen

- C.3 Deinstall Progress Screen

- C.4 Deinstall Completed Screen

D Silent Installation

- D.1 What is a Silent Installation?

- D.2 Creating Response Files

- D.2.1 Contents of the sampleResponse.rsp File

- D.2.2 Creating Your Own Response Files

- D.2.3 Securing Your Silent Installation

- D.3 Pre-Installation Tasks

- D.3.1 UNIX Users: Creating the oraInst.loc File

- D.3.2 Windows Users: Creating the Registry Key

- D.4 Silent Installation Instructions

- D.4.1 Sample Commands

- D.4.2 Sample Output

- D.5 Silent De-Installation

E Troubleshooting

- E.1 General Troubleshooting Tips

- E.2 Troubleshooting Oracle Fusion Middleware Installation

- E.2.1 Installation Log Files

- E.2.2 Configuration Log Files

- E.3 Keeping Track of Your JRE Location

- E.4 Need More Help?

Index

Preface

The Oracle Fusion Middleware Installation Guide for Application Developer provides information and instructions for installing, configuring, troubleshooting, and removing Application Developer.

Intended Audience

This guide is intended for users who are installing Oracle Fusion Middleware for the first time and are comfortable running some system administration operations, such as creating users and groups, adding users to groups, and installing operating system patches on the computer where your components will be installed. Users on UNIX systems who are installing need root access to run some scripts.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

Related Documents

For additional information, see the following manuals:

- Oracle Fusion Middleware Installation Planning Guide

- Oracle Fusion Middleware Administrator's Guide

- Oracle Fusion Middleware Concepts

- Oracle Fusion Middleware High Availability Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Installing Application Developer

This chapter describes how to install Application Developer.

The following topics are covered in this chapter:

- Section 1.1, "Preparing to Install"

- Section 1.2, "Install and Configure Java Access Bridge (Windows Only)"

- Section 1.3, "Installing on DHCP Hosts"

- Section 1.4, "Installing on a Non-Networked Computer"

- Section 1.5, "Installing on a Multihomed Computer"

- Section 1.6, "Using Custom Port Numbers"

- Section 1.7, "Installation Instructions"

1.1 Preparing to Install

Make sure you have read the information in this section before you install Application Developer:

- Section 1.1.1, "System Requirements and Certification"

- Section 1.1.2, "Create Schemas for Application Developer"

- Section 1.1.3, "Install Oracle WebLogic Server and Create the Middleware Home"

1.1.1 System Requirements and Certification

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the components you are installing. Both of these documents are available on Oracle Technology Network (OTN).

The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches:

http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

The certification document covers supported installation types, platforms, operating systems, databases, JDKs, and third-party products:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Note:
If you are installing the 32-bit version of the product, the system on which you are installing must also be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported.

1.1.2 Create Schemas for Application Developer

Application Developer includes Oracle WSM Policy Manager and Oracle WSM-PM Extension. These components require that the MDS schema exists in an Oracle database prior to installation. You must run Repository Creation Utility (RCU) to create the MDS schema in your database. Follow the instructions in this section to do so.

For detailed information about using RCU, refer to Oracle Fusion Middleware Repository Creation Utility User's Guide.

1.1.2.1 Check for Supported Database

Installation of Application Developer requires the availability of a database. This database must be up and running, and does not have to be on the same system where you are installing the components.

For the latest information about supported databases, visit the following URL:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

1.1.2.2 Create the Schemas

To create the MDS schema in your database:

1. Insert the RCU CD-ROM and start RCU from the rcuHome/bin (on UNIX operating systems) or rcuHome\bin (on Windows operating systems) directory:
On UNIX operating systems:

./rcu

On Windows operating systems:

rcu.bat

You can also download a .zip file containing RCU from Oracle Technology Network (OTN):

http://www.oracle.com/technology/

After downloading the .zip file, extract the contents to a directory of your choice, and run RCU from the RCU_HOME/bin (on UNIX operating systems) or RCU_HOME\bin (on Windows operating systems) directory with the commands shown above, where RCU_HOME is the folder where RCU was unzipped, or the drive or mount point of the CD-ROM.

Note:
On Windows systems, make sure that you do not extract the RCU .zip file to a directory name containing spaces.

2. Welcome Screen
Click Next.

3. Create Repository Screen
Click Create.

Click Next.

4. Database Connection Details Screen
Select the type of database on your system. This is the database in which you will create the MDS schema.

Provide the necessary credentials for RCU to be able to connect to your Oracle database:

- Host Name: Specify the name of the machine on which your database resides in the format host.domain.com. For Oracle RAC databases, specify the Virtual IP name or one of the node names as the host name.

- Port: Specify the database listener port number. The default port number for Oracle databases is 1521.

- Database Name: Specify the service name for the database. Typically, the service name is the same as the global database name.
If you are unsure what the service name for your database is, you can obtain it from the SERVICE_NAMES parameter in the database's initialization parameter file. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: sales.mydomain.com.

- Username: Specify the name of a user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is SYS.

- Password: Specify the password for your database user.

- Role: Select the database user's role from the drop-down list. The SYS user requires the SYSDBA role.

If you are using a Microsoft SQL Server database, provide the following credentials:

- Unicode Support: Select Yes or No from the drop-down list.

Note:
Oracle SOA Infrastructure schemas are created with Unicode support (database tables created with NVARCHAR) only, regardless of the option selected in this field.

- Server Name: Enter the host name, IP address, or complete server name in host\server format of the server where your database is running..

- Port: Specify the database listener port number.

- Database Name: Specify the name of your database.

- Username: Specify the name of a user with DBA or SYSDBA privileges.

- Password: Specify the password for your database user.

Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.

5. Select Components Screen
Near the top of the screen, select Create a New Prefix. The default prefix is DEV.

Select the MDS schema.

Note:
You must remember or make a note of these schema names and the prefix value from this screen; you will need them later when you are configuring your components. You will need to provide the schema name in the format prefix_schemaname. For example, if you used the default prefix DEV, you will supply the following schema name for the MDS schema:
DEV_MDS

Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.

6. Schema Passwords Screen
There are three ways to specify schema passwords on this screen:

- Select Use same password for all schemas if you want to use a single password for all schemas and their auxiliary schemas. In the Password field, enter your password. Enter your password again in the Confirm Password field.

- Select Use main schema passwords for auxiliary schemas if you want to specify different passwords for the main schemas, but still have the same password used for their respective auxiliary schemas. If you select this option, only the main schemas will be visible in the table. For each schema, you must enter each schema's password in the Password column in the table, and enter the same password in the Confirm Password column.

- Select Specify different passwords for all schemas if you want to specify unique passwords for the main schemas and auxiliary schemas. If you select this option, all main schemas and auxiliary schemas will be visible in the table. For each schema and auxiliary schema, you must enter the password in the Password column in the table, and enter the same password in the Confirm Password column.

Note:
You must remember or make a note of the password(s) from this screen; you will need them later when you are configuring your components.

Click Next.

7. Map Tablespaces Screen
Click Next. A "Creating Tablespaces" screen will appear. After the tablespaces are created with no errors, click OK to dismiss the screen.

8. Summary Screen
Click Create. A "CREATE" screen will appear. After the schemas are created with no errors, click OK to dismiss the screen.

9. Completion Summary Screen
Click Close.

1.1.3 Install Oracle WebLogic Server and Create the Middleware Home

Application Developer requires an Oracle WebLogic Server on your system. If you do not already have one, follow the instructions in this section to install Oracle WebLogic Server.

1. Insert the Oracle WebLogic Server CD-ROM or download the installer from the following URL:

http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html

You are looking for the following executable files:

- wls1032_linux32.bin (for 32-bit Linux systems)

- wls1032_win32.exe (for 32-bit Windows systems)

- wls1032_generic.jar (for all 64-bit platforms)

The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server. Refer to the Oracle Fusion Middleware certification document for a list of supported JDKs for your platform:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

2. Run your installer file directly from the CD-ROM, or copy the file to your local system and run it locally.
Some notes for running the installer:

- Before running the installer, set the DISPLAY environment variable on your system.

- Replace JAVA_HOME with the installation location of the supported JDK you installed for your platform.

- If you are installing a 64-bit Oracle WebLogic Server on a 64-bit platform, use the -d64 flag when using 32/64-bit hybrid JDK's (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).
Execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version on 32/64-bit hybrid JDKs) to ensure that your JAVA_HOME refers to a 64-bit JDK.

To run the installer on a 32-bit Linux operating system:

./wls1032_linux32.bin

To run the installer on 32-bit Windows operating systems:

wls1032_win32.exe

To run the installer on 64-bit UNIX operating systems:

JAVA_HOME/bin/java -jar wls1032_generic.jar

or

JAVA_HOME/bin/java -d64 -jar wls1032_generic.jar

To run the installer on 64-bit Windows operating systems:

JAVA_HOME\bin\java -jar wls1032_generic.jar

3. Welcome Screen
Click Next.

4. Choose Middleware Home Directory Screen
Select Create a new Middleware Home to create a new Middleware Home directory.

Specify the desired location of your new Middleware Home directory. If this directory already exists on your system, it must be an empty directory. If this directory does not already exist, then it will be created for you.

For more information about the Middleware Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.

Click Next.

5. Register for Security Updates Screen
Select whether or not you want to receive the latest product and security updates. If you choose not to receive anything, you will be asked to verify your selection before continuing.

Click Next.

6. Choose Install Type Screen
A Typical installation includes all Oracle WebLogic Server components by default. It also includes both Sun SDK 1.6.0_14 and Oracle JRockit SDK 1.6.0_14. If you want to perform a Typical installation, select Typical and and click Next to go to the Choose Product Installation Directories Screen.

A Custom installation gives you the choice of selecting the following components for installation:

- 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 Plugins

- UDDI and Xquery Support

- Server Examples (not selected by default)

If you want to perform a Custom installation, select Custom. You will see the following two screens:

1. Choose Products and Components Screen
Select the products you want to install.

Note:
In order to be configured properly, Oracle SOA Suite requires that Configuration Wizard and Upgrade Framework is selected.

2. JDK Selection Screen
Select the JDKs you want to install.

Oracle recommends that you use the Sun SDK if you are installing in a development environment. Typically, this environment provides a more relaxed security configuration and enables you to auto-deploy applications. In a development environment, boot.properties is used for user names and passwords and polling is used for application deployment.

If you are installing in a production environment, Oracle recommends that you use the Oracle JRockit SDK. Production environments are for applications running in their final form. Full security is enabled and applications may be clustered or use other advanced features. In this mode, user names and passwords are required and polling is not used for application deployment.

Click Next.

7. Choose Product Installation Directories Screen

Specify the desired location for your WebLogic Server Home directory. The default location is wlserver_10.3 inside your Middleware Home directory.

For more information about the WebLogic Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide..

Click Next.

8. Choose Shortcut Location (Windows only)
If you are installing on a Windows system, you will be asked to specify a location where you would like Windows to create a shortcut to Oracle products.

Click Next.

9. Installation Summary Screen
Click Next.

10. Installation Progress Screen
Click Next.

11. Installation Complete Screen
De-select Run Quickstart.

Click Done.

For more information about installing Oracle WebLogic Server, refer to Oracle WebLogic Server Installation Guide.

1.2 Install and Configure Java Access Bridge (Windows Only)

If you are installing on a Windows system, you have the option of installing and configuring Java Access Bridge for Section 508 Accessibility. For more information on how to do this, refer to "Install and Configure Java Access Bridge (Windows Only)" in Oracle Fusion Middleware Administrator's Guide.

1.3 Installing on DHCP Hosts

If you are installing Application Developer on a DHCP host, you must follow the configuration steps in this section for your platform.

1.3.1 For UNIX Platforms

On UNIX systems, configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following entries:

127.0.0.1 hostname.domainname hostname
127.0.0.1 localhost.localdomain localhost

After doing so, check that the host name resolves to the loopback IP address by entering the following command:

/bin/ping hostname.domainname

1.3.2 For Windows x86 Platforms

On Windows systems, install a loopback adapter on the DHCP server (see Section 1.3.3, "Installing a Loopback Adapter (Windows Only)"). This assigns a local IP address to your computer.

After installing the adapter, add a line to the %SYSTEMROOT%\system32\drivers\etc\hosts file with the following format, immediately after the localhost line:

IP_address   hostname.domainname   hostname

Replace IP_address with the local IP address of the loopback adapter.

1.3.3 Installing a Loopback Adapter (Windows Only)

To install a loopback adapter on Windows 2003 or Windows XP:

1. Open the Windows Control Panel.
Windows 2003: Select Start > Control Panel > Add Hardware.

Windows XP: Select Start > Control Panel, then double-click Add Hardware.

2. In the "Welcome" window, click Next.

3. In the "Is the hardware connected?" window, select Yes, I have already connected the hardware, then click Next.

4. In the "The following hardware is already installed on your computer" window, in the list of installed hardware, select Add a new hardware device, then click Next.

5. In the "The wizard can help you install other hardware" window, select Install the hardware that I manually select from a list, then click Next.

6. In the "From the list of hardware types, select the type of hardware you are installing" window, select Network adapters, then click Next.

7. In the "Select Network Adapter" window, make the following selections:

- Manufacturer: Microsoft

- Network Adapter: Microsoft Loopback Adapter

8. Click Next.

9. In the "The wizard is ready to install your hardware" window, click Next.

10. In the "Completing the Add Hardware Wizard" window, click Finish.

11. If you are using Windows 2003, restart your computer.

12. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.

13. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

14. On the "General" tab, select Internet Protocol (TCP/IP), then click Properties.

15. In the "Properties" dialog box, click Use the following IP address and do the following:

1. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

192.168.x.x (x is any value between 1 and 255)
10.10.10.10

2. Subnet mask: Enter 255.255.255.0.

3. Record the values you entered, which you will need later in this procedure.

4. Leave all other fields empty.

5. Click OK.

16. In the "Local Area Connection 2 Properties" dialog, click OK.

17. Close Network Connections.

18. Restart the computer.

1.3.4 Removing a Loopback Adapter (Windows Only)

To remove a loopback adapter on Windows 2003 or Windows XP:

1. Start the System Control panel.
Windows 2003: Select Start > Control Panel > System.

Windows XP: Select Start > Control Panel, then double-click System.

2. In the "Hardware" tab, click Device Manager.

3. In the "Device Manager" window, expand Network adapters. You should see Microsoft Loopback Adapter.

4. Right-click Microsoft Loopback Adapter and select Uninstall.

5. Click OK.

1.4 Installing on a Non-Networked Computer

You can install Application Developer on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you have to install all the components that you need on the computer.

In addition, you must follow the instructions in Section 1.3, "Installing on DHCP Hosts" to install a loopback adapter and modify the hosts file on your system.

1.5 Installing on a Multihomed Computer

You can install Application Developer on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name; additionally, you can set up aliases for each hostname.

The installer picks up the fully qualified domain name from the first entry in /etc/hosts (on UNIX operating systems) or %SYSTEMROOT%\system32\drivers\etc\hosts (on Windows operating systems) file. So if your file looks like the following:

127.0.0.1 localhost.localdomain localhost
10.222.333.444 myhost1.mycompany.com myhost1
20.222.333.444 devhost2.mycompany.com devhost2

myhost1.mycompany.com would be picked for configuration.

For specific network configuration of a system component, refer to the individual component's configuration documentation.

1.6 Using Custom Port Numbers

By default, the servers that are created in each domain use the same set of port numbers (for example, the Admnistration Server uses port 7001). If you want to use custom port numbers, you can change the port number when you run the Oracle Fusion Middleware Configuration Wizard:

- The Administration Server port number can be changed on the Configure Administration Server Screen.

- The port number for all managed servers in your domain can be changed on the Configure Managed Servers Screen.

For more information, refer to Chapter 2, "Configuring Application Developer".

Fore more information about port numbers, refer to "Port Numbers" in Oracle Fusion Middleware Administrator's Guide.

1.7 Installation Instructions

When you run the installer, Application Developer is installed onto your system. After the product is installed, you must run the Configuration Wizard to configure Application Developer.

This section contains the following topics:

- Section 1.7.1, "Starting the Installer"

- Section 1.7.2, "Installation Log Files"

- Section 1.7.4, "Installation Screens and Instructions"

1.7.1 Starting the Installer

The installer requires the location of a Java Runtime Environment (JRE) on your system. When you installed Oracle WebLogic Server (Section 1.1.3, "Install Oracle WebLogic Server and Create the Middleware Home"), a JRE was installed on your system. You can use this location (the location of the jre directory) to start the installer. The default location for the JRE is MW_HOME/jdk160_14_R27.6.4-18 (on UNIX systems) or MW_HOME\jdk160_14_R27.6.4-18 (on Windows systems), where MW_HOME is the Middleware Home directory.

On 64-bit platforms, the JRE location is the JAVA_HOME you used to install Oracle WebLogic Server. Refer to Section 1.1.3, "Install Oracle WebLogic Server and Create the Middleware Home" for more information.

Note:
Starting the installer as root user is not supported.

On UNIX operating systems:

./runInstaller -jreLoc JRE_LOCATION

On Windows operating systems:

setup.exe -jreLoc JRE_LOCATION

Note:
Specify the absolute path to your JRE_LOCATION; relative paths are not supported.

You must also specify the JRE location in the same manner if you are installing Oracle Application Developer on a 64-bit platform with a 32-bit JDK.

If no JRE location is specified, you will be prompted to provide the location of your JRE before the installer is started. For example, on a UNIX system:

[> ./runInstaller
Platform is Linux X86 32 bit
Starting Oracle Universal Installer...

Checking if CPU speed is above 300 MHz.    Actual 2999 MHz    Passed
Checking Temp space: must be greater than 150 MB.   Actual 60229 MB    Passed
Checking swap space: must be greater than 512 MB.   Actual 1013 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 256    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-01_02-45-07PM. Please wait ...
Please specify JRE/JDK location ( Ex. /home/jre ), <location>/bin/java should exist :

Specify the absolute path to the JRE on your system before you continue.

1.7.2 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. Refer to Section E.2.1, "Installation Log Files" for more information about the log files and their contents.

1.7.3 Inventory Screens (UNIX Only)

If you are installing on a UNIX system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 1-1 to configure the inventory directory information. For more help, click on the screen name in the table below, or click the Help button in the GUI.

Table 1-1 Inventory Directory and Group Screens

No.

Screen

Description and Action Required

1

Specify Inventory Directory Screen (UNIX Only)

Specify the Oracle inventory directory and group permissions for that directory. The group must have write permissions to the Oracle inventory directory.

Click OK to continue.

2

Inventory Location Confirmation Screen (UNIX Only)

Run the createCentralInventory.sh script as root.

Click OK to continue.

1.7.4 Installation Screens and Instructions

Follow the instructions in Table 1-2 to install the Application Developer software.

Note:
Running the installer as root user is not supported.

If you need additional help with any of the installation screens, refer to Appendix A, "Application Developer Installation Screens" or click Help to access the online help.

Table 1-2 Installation Flow for Install and Configure Option (Common Screens)

No.

Screen

When Does This Screen Appear?

Description and Action Required

1

Welcome Screen

Always.

Click Next to continue.

2

Prerequisite Checks Screen

Always.

Click Next to continue.

3

Specify Installation Location Screen

Always.

Specify the Middleware Home location. The Oracle Common Home (oracle_common) will automatically be created inside the Middleware Home.

Click Next to continue.

4

Installation Summary Screen

Always.

Verify the installation about to be performed.

Click Install to continue.

5

Installation Progress Screen

Always.

This screen shows the progress of the installation.

Click Next to continue.

6

Installation Completed Screen

Always.

Click Finish to dismiss the screen.

After the installation is complete., you must configure your products before you can begin using them. Go to Chapter 2, "Configuring Application Developer".

2 Configuring Application Developer

This chapter describes how to configure Application Developer after the software has already been installed.

The following topics are covered:

- Section 2.1, "Configuration Instructions"

- Section 2.2, "Applying Java Required Files (JRF)"

- Section 2.3, "Starting the Administration Server"

- Section 2.4, "Verifying the Installation"

2.1 Configuration Instructions

After the installation is complete, you can configure the components using the Oracle Fusion Middleware Configuration Wizard. The instructions in this section describe how to do so.

This section contains the following conent:

- Starting the Configuration Wizard

- Configuration Log Files

- Creating a New Domain

- Extending an Existing Domain

- Configuration Wizard Optional Configuration Screens

2.1.1 Starting the Configuration Wizard

The Configuration Wizard is located in the MW_HOME/oracle_common/common/bin (on UNIX operating systems) or MW_HOME\oracle_common\common\bin (on Windows operating systems) directory. Go to this directory, then run the config.sh (on UNIX operating systems) or config.cmd (on Windows operating systems) script to start the Configuration Wizard:

On UNIX operating systems:

./config.sh

On Windows operating systems:

config.cmd

If this is a new installation and you need to create a new WebLogic domain, follow the instructions in Section 2.1.3, "Creating a New Domain". You can also run the Configuration Wizard to extend an existing WebLogic domain, as described in Section 2.1.4, "Extending an Existing Domain".

If you are using a 32-bit operating system, Oracle JRockit SDK is installed as part of the Oracle WebLogic installation (see Section 1.1.3, "Install Oracle WebLogic Server and Create the Middleware Home"). This is the JDK that the Configuration Wizard will use by default. If you want to invoke the Configuration Wizard with the Sun JDK, do the following prior to starting the Configuration Wizard:

1. Set the JAVA_HOME environment variable to the location of the Sun JDK. For example, you can set it to the Sun JDK that was installed with Oracle WebLogic Server in the MW_HOME/jdk160_14_R27.6.4-18 (on UNIX operating systems) or MW_HOME\jdk160_14_R27.6.4-18 (on Windows operating systems) directory.

2. Set the JAVA_VENDOR environment variable to "Sun."

2.1.2 Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:

On UNIX operating systems:

./config.sh -log=log_filename

On Windows operating systems:

config.cmd -log=log_filename

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the MW_HOME/oracle_common/common/bin (on UNIX operating systems) or MW_HOME\oracle_common\common\bin (on Windows operating systems) directory.

2.1.3 Creating a New Domain

Follow the instructions in Table 2-1 to create a new WebLogic domain for Application Developer.

Note:
For more information about WebLogic Server domains, refer to "WebLogic Server Domain" in Oracle Fusion Middleware Installation Planning Guide.

If you need additional help with any of the configuration screens, refer to Appendix B, "Application Developer Configuration Screens" or click Help at the bottom of each screen to access the online help for that screen.

Table 2-1 Configuration Flow for Creating a New Domain

No.

Screen

Description and Action Required

1

Welcome Screen

Select Create a new WebLogic Domain.

Click Next to continue.

2

Select Domain Source Screen

Select components you want to create in your domain.

Click Next to continue.

3

Specify Domain Name and Location Screen

Specify the name and location for the new domain.

Click Next to continue.

4

Configure Administrator Username and Password Screen

Specify a user and password for the Administrator role.

Click Next to continue.

5

Configure Server Start Mode and JDK Screen

Select the WebLogic domain startup mode and the JDK to be used for the domain.

Click Next to continue.

6

Configure JDBC Component Schema Screen

This screen only appears if you selected Oracle WSM Policy Manager on the Select Domain Source Screen. If you did not, skip to the Select Optional Configuration Screen.

Configure the schema owner and password for each component schema listed on this screen. Changes to any of the fields on this screen are applied to all selected component schema in the table.

For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port).

If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only.

Click Next to continue.

7

Test Component Schema Screen

Test and verify the connections to your component schema.

Click Next to continue.

8

Select Optional Configuration Screen

Select the category or categories for which you want to make additional configuration changes:

- If you select Administration Server, see Section 2.1.5.1, "Administration Server Options".

- If you select Managed Servers, Clusters and Machines, see Section 2.1.5.2, "Managed Server, Clusters and Machines Options".

- If you select Deployments and Services, see Section 2.1.5.3, "Deployments and Services Options".

- If you select JMS File Store, see Section 2.1.5.4, "JMS File Store Options".

- If you select RDBMS Security Store, see Section 2.1.5.5, "RDBMS Security Store Options".

If you choose not to select anything on this screen, skip to the Configuration Summary Screen.

Click Next to continue.

9

Configuration Summary Screen

Review the contents of your domain.

Click Create to continue.

10

Creating Domain Screen

Click Done when finished.

2.1.4 Extending an Existing Domain

While creating your WebLogic domain, if you chose not to configure all of the components on the Select Domain Source Screen, you can add these components at a later date by extending your domain. If this is a first time installation or you do not want to add more components, you can skip this section and move to the next section.

Note:
Before proceeding, make sure that schemas exist in your database for the components you are configuring when you extend the domain. For example, if you are planning to extend the domain and configure Oracle WSM Policy Manager, then make sure the required schema for this component (MDS) exists in your Oracle database before you continue.

Follow the instructions in Table 2-2 to extend an existing domain.

Table 2-2 Configuration Flow for Extending an Existing Domain

No.

Screen

Description and Action Required

1

Welcome Screen

Select Extend an existing WebLogic Domain.

Click Next to continue.

2

Select a WebLogic Domain Directory Screen

Select the WebLogic directory to which you want to add your applications and services.

Click Next to continue.

3

Select Extension Source Screen

Select the components with which you want to extend this domain.

Click Next to continue.

4

Configure JDBC Component Schema Screen

This screen only appears if you selected Oracle WSM Policy Manager on the Select Extension Source Screen. If you did not, skip to the Select Optional Configuration Screen.

Configure the schema owner and password for each component schema listed on this screen. Changes to any of the fields on this screen are applied to all selected component schema in the table.

For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port).

If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only.

Click Next to continue.

5

Test Component Schema Screen

Test and verify the connections to your component schema.

Click Next to continue.

6

Select Optional Configuration Screen

Select the category or categories for which you want to make additional configuration changes:

- If you select Managed Servers, Clusters and Machines, see Section 2.1.5.2, "Managed Server, Clusters and Machines Options".

- If you select Deployments and Services, see Section 2.1.5.3, "Deployments and Services Options".

- If you select JMS File Store, see Section 2.1.5.4, "JMS File Store Options".

If you choose not to select anything on this screen, skip to the Configuration Summary Screen.

Click Next to continue.

7

Configuration Summary Screen

Review the contents of your domain.

Click Extend to continue.

8

Creating Domain Screen

Click Done when finished.

2.1.5 Configuration Wizard Optional Configuration Screens

The Select Optional Configuration Screen gives you the following optional configuration options:

- Administration Server Options

- Managed Server, Clusters and Machines Options

- Deployments and Services Options

- JMS File Store Options

- RDBMS Security Store Options

2.1.5.1 Administration Server Options

If you select Administration Server on the Select Optional Configuration Screen, you will see the Configure Administration Server Screen. This screen enables you to customize your Administration Server settings, such as the server name, port number, and secure connection settings.

2.1.5.2 Managed Server, Clusters and Machines Options

If you select Managed Servers, Clusters, and Machines on the Select Optional Configuration Screen, you will see the screens described in Table 2-3:

Table 2-3 Managed Servers, Clusters, and Machines Advanced Settings Screens

No.

Screen

Description and Action Required

1

Configure Managed Servers Screen

Add new managed servers, or edit and delete existing managed servers.

Click Next to continue.

2

Configure Clusters Screen

Create clusters if you are installing in a high availability environment. For more information, refer to Oracle Fusion Middleware High Availability Guide.

Click Next to continue.

3

Assign Servers to Clusters Screen

Assign your managed servers to a cluster in your domain.

Click Next to continue.

4

Create HTTP Proxy Applications Screen

Select whether or not you want a configure an HTTP proxy server for your cluster.

This screen only appears if you have configured a managed server outside of a cluster.

Click Next to continue.

5

Configure Machines Screen

Configure the machines that will host the managed servers.

Click Next to continue.

6

Assign Servers to Machines Screen

Assign each managed server to the machine on which it runs.

Click Next to continue.

2.1.5.3 Deployments and Services Options

If you select Deployments and Services on the Select Optional Configuration Screen, you will see the screens described in Table 2-4.

The Configuration Wizard automatically takes care of all necessary deployment and services targeting. You should not have to change anything on these screens unless specifically directed to do so.

Table 2-4 Deployments and Services Advanced Settings Screens

No.

Screen

Description and Action Required

1

Target Deployments to Servers or Clusters Screen

Target your deployments to servers or clusters.

Click Next to continue.

2

Target Services to Servers or Clusters Screen

Target your services to servers or clusters.

Click Next to continue.

2.1.5.4 JMS File Store Options

If you select JMS File Store on the Select Optional Configuration Screen, you will see the Configure JMS File Stores Screen. This screen enables you to configure the names, location, and write policy for your file stores.

2.1.5.5 RDBMS Security Store Options

If you select RDBMS Security Store on the Select Optional Configuration Screen, you will see the Configure RDBMS Security Store Database Screen. This screen enables you to configure an external relational database management system (RDBMS) as a data store for various security providers.

2.2 Applying Java Required Files (JRF)

Java Required Files (JRF) consists of those components not included in the Oracle WebLogic Server installation and that provide common functionality for Oracle business applications and application frameworks.

JRF consists of a number of independently developed libraries and applications that are deployed into a common location. The components that are considered part of Java Required Files include: Oracle Application Development Framework, Oracle Fusion Middleware Audit Framework, Dynamic Monitoring Service, Infrastructure Security, Java Object Cache, Oracle Platform Security Services, logging, MDS, Oracle Web Services, and Oracle Web Services Manager.

You must apply JRF to a Managed Server or cluster in certain circumstances.You can only apply JRF to Managed Servers that are in a domain in which JRF was configured. That is, you must have selected Oracle JRF in the Configuration Wizard when you created or extended the domain.

For more information, see "Applying Java Required Files to a Managed Server or Cluster" in Oracle Fusion Middleware Administrator's Guide.

2.3 Starting the Administration Server

To get your deployments up and running, you must start the Administration Server by running the startWebLogic.sh (on UNIX operating systems) or startWebLogic.cmd (on Windows operating systems) script in the directory where you created your new domain.

On UNIX systems:

MW_HOME/user_projects/domains/domain_name/startWebLogic.sh

On Windows systems:

MW_HOME\user_projects\domains\domain_name\startWebLogic.cmd

You entered the domain name and location on the Specify Domain Name and Location Screen in the Configuration Wizard.

2.4 Verifying the Installation

To verify the installation, start your browser and enter the following URLs:

- To access the Administration Server console:

http://host:admin_server_port/console

- If you configured your Administration Server to accept SSL connection, use the following URL to access the Administration Server console in secure mode:

https://host:secure_admin_server_port/console

- To access Enterprise Manager:

http://host:admin_server_port/em

3 Deinstalling Application Developer

This chapter describes how to remove Application Developer and related products from your system.

You should always use the instructions provided in this chapter for removing the software. If you try to remove the software manually, you may experience problems when you try to reinstall the software again at a later time. Following the procedures in this chapter will ensure that the software is properly removed. See Section 3.2, "Reinstallation" for more information.

The following topics are covered:

- Section 3.1, "Deinstallation Instructions"

- Section 3.2, "Reinstallation"

3.1 Deinstallation Instructions

The deinstaller will attempt to remove the Oracle Home from which it was started; for Application Developer, this directory is the oracle_common directory. This procedure will not remove any WebLogic domains that you have created - it only removes the software in oracle_common.

Before you choose to remove this directory, make sure that it is not in use by an existing domain, and also make sure you stop all running processes that use the oracle_common directory. After you remove the software, you will no longer be able to use your WebLogic domain.

Deinstalling Application Developer properly involves the following tasks:

- Stopping Oracle Fusion Middleware

- Removing the Application Developer Schemas

- Removing Application Developer

- Removing Oracle WebLogic Server

- Removing Oracle JDeveloper

- Removing Program Groups (Windows Only)

3.1.1 Stopping Oracle Fusion Middleware

Before deinstalling Oracle Fusion Middleware software components, you should stop all servers and processes.

1. Sop the WebLogic Managed Servers.
On UNIX operating systems:

MW_HOME/user_projects/domains/domain_name/bin/stopManagedWeblogic.sh managed_server_nanme admin_url username password

On Windows operating systems:

MW_HOME\user_projects\domains\domain_name\bin\stopManagedWeblogic.cmd managed_server_nanme admin_url username password

2. Stop WebLogic Administration Server.
On UNIX operating systems:

MW_HOME/user_projects/domains/domain_name/bin/stopWeblogic.sh username password admin_url

On Windows operating systems:

MW_HOME\user_projects\domains\domain_name\bin\stopWeblogic.cmd username password admin_url

For both commands, specify the admin_url using the following format:

http://admin_server_host.admin_server_domain:admin_server_port

For more information about starting and stopping Oracle Fusion Middleware, refer to "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

3.1.2 Removing the Application Developer Schemas

Run the Repository Creation Utility (RCU) to drop the Application Developer schemas from your database.

3.1.2.1 Starting RCU

Insert the RCU CD-ROM and start RCU from the rcuHome/bin (on UNIX operating systems) or rcuHome\bin (on Windows operating systems) directory:

On UNIX operating systems:

./rcu

On Windows operating systems:

rcu.bat

If you download the RCU .zip file from OTN, then you can also start RCU as shown above from the rcuHome/bin (on UNIX operating systems) or rcuHome\bin (on Windows operating systems) directory on your system.

3.1.2.2 Instructions for Dropping the Application Developer Schemas

Follow the instructions below to drop the MDS schema:

1. Welcome Screen
Click Next.

2. Create Repository Screen
Select Drop.

Click Next.

3. Database Connection Details Screen
Provide the following credentials to connect to your Oracle database. These are the same credentials you provided on this screen when you created the MDS schema. See Section 1.1.2, "Create Schemas for Application Developer" for more information.

Click Next. A "Checking Prerequisites" screen will appear. If there are errors, some details about the error will be displayed on the Database Connection Details Screen. Fix the error messages and click Next again.

After the checking is complete with no errors, click OK to dismiss the screen.

4. Select Components Screen
Select the prefix and schemas you want to drop from the repository.

Click Next. A "Checking Prerequisites" screen will appear. If there are errors, some details about the error will be displayed on the Select Components Screen. Fix the error messages and click Next again.

After the checking is complete with no errors, click OK to dismiss the screen.

5. Summary Screen
Click Drop. A "DROP" screen will appear. If there are errors, some details about the error will be displayed on the Summary Screen. Fix the error messages and click Next again.

After the schemas are dropped with no errors, click OK to dismiss the screen.

6. Completion Summary Screen
Click Close.

3.1.3 Removing Application Developer

The deinstaller will attempt to remove the oracle_common directory. Before you choose to remove your Application Developer Oracle Home, make sure that it is not in use by an existing domain, and also make sure you stop all running processes that use this Oracle Home.

This procedure will not remove any WebLogic domains that you have created - it only removes the software in the Application Developer Oracle Home.

3.1.3.1 Starting the Deinstaller

Go to the MW_HOME/oracle_common/oui/bin (on UNIX operating systems) or MW_HOME\oracle_common\oui\bin (on Windows operating systems) directory and start the deinstaller.

On UNIX operating systems:

./runInstaller.sh -deinstall -jreLoc JRE_LOCATION

On Windows operating systems:

setup.exe -deinstall -jreLoc JRE_LOCATION

Note:
Specify the absolute path to your JRE_LOCATION; relative paths are not supported.

3.1.3.2 Deinstallation Screens and Instructions

Follow the instructions in Table 3-1 to deinstall Application Developer.

Note:
The deinstaller will attempt to remove the Oracle Home from which it was started; before you choose to remove the Oracle Home, make sure that it is not in use by an existing domain.

If you need additional help with any of the deinstallation screens, refer to Appendix C, "Application Developer Deinstallation Screens" or click Help to access the online help.

Table 3-1 Deinstallation Flow

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Deinstall Oracle Home Screen

Verify the Oracle Home you are about to deinstall.

Click Deinstall to continue.

3

Deinstall Progress Screen

This screen shows the progress and status of the deinstallation.

4

Deinstall Completed Screen

Click Finish to dismiss the screen.

3.1.4 Removing Oracle WebLogic Server

To deinstall Oracle WebLogic Server:

1. Start the deinstaller from the WebLogic_Home/uninstall (on UNIX operating systems) or WebLogic_Home\uninstall (on Windows operating systems) directory. You specified the location of the WebLogic Home directory on the Choose Product Installation Directories Screen in Section 1.1.3, "Install Oracle WebLogic Server and Create the Middleware Home".
On UNIX systems:

./uninstall.sh

On Windows systems:

uninstall.cmd

On Windows systems, you can also start the deinstaller from the Start menu by selecting Programs > Oracle WebLogic > Uninstall Oracle WebLogic.

2. Welcome Screen
Click Next.

3. Choose Components Screen
By default, all components are selected.

Click Next.

4. Uninstalling WebLogic Platform Screen
Click Done.

After this is finished, you must manually remove the WebLogic Home directory. For example, if your WebLogic Home directory was /home/Oracle/Middleware on a UNIX operating system:

> cd /home/Oracle
> rm -rf Middleware

On a Windows operating system, if your WebLogic Home directory was C:\Oracle\Middleware, use a file manager window and navigate to the C:\Oracle directory, then right-click on the Middleware folder and select Delete.

3.1.5 Removing Oracle JDeveloper

If you have installed Oracle JDeveloper on your system, refer to Oracle Fusion Middleware Installation Guide for Oracle JDeveloper for instructions on how to remove this software from your system.

3.1.6 Removing Program Groups (Windows Only)

On Windows systems, you must also manually remove the program groups from the Start Menu\Programs folder. As an example (the folder names and program group names on your system may be different), you might remove the following from C:\Documents and Settings\All Users\Start Menu\Programs:

- Oracle Fusion Middleware 11.1.1.2.0

- Oracle WebLogic

3.2 Reinstallation

The installer does not allow reinstallation of Application Developer in a directory that already contains an Oracle product. To reinstall Application Developer in the same directory as before, you must follow the instructions in this chapter to deinstall the software, then follow the instructions in Chapter 1, "Installing Application Developer" to reinstall the software.

A Application Developer Installation Screens

This appendix contains screenshots and descriptions for all of the Application Developer installation screens:

- Specify Inventory Directory Screen (UNIX Only)

- Inventory Location Confirmation Screen (UNIX Only)

- Welcome Screen

- Prerequisite Checks Screen

- Specify Installation Location Screen

- Installation Summary Screen

- Installation Progress Screen

- Installation Completed Screen

A.1 Specify Inventory Directory Screen (UNIX Only)

This screen appears for UNIX systems only; if this is your first Oracle installation on this host, you must specify the location of the inventory directory. This inventory directory is used by the installer to keep track of all Oracle products installed on the computer.

The default inventory location is USER_HOME/oraInventory.

In the Operating System Group name field, select the group whose members you want to grant access to the inventory directory; all members of this group will be able to install products on this system.

A.2 Inventory Location Confirmation Screen (UNIX Only)

This screen appears for UNIX systems only; you are asked to run the inventory_directory/createCentralInventory.sh script as root.

If you do not have root access on this system but wish to continue with the installation, select Continue installation with local inventory.

A.3 Welcome Screen

The Welcome screen is displayed each time you start the installer.

A.4 Prerequisite Checks Screen

If there is a problem, a short error message appears in the bottom portion of the screen. Fix the error and click Retry to try again.

If you want to ignore the error and warning messages and contiune with the installation, click Continue.

Click Abort to stop prerequisite checking for all components.

A.5 Specify Installation Location Screen

In the Oracle Middleware Home field, specify the absolute path to your existing Oracle Middleware Home directory; this is the directory that was created when you installed Oracle WebLogic Server. If you do not know the full path to your Middleware Home, you can click Browse to select an existing directory in your system.

With Application Developer, you are installing the products that are required for the Oracle Common home directory. In the Oracle Home Directory field, notice that the directory oracle_common is already populated and can not be changed. This directory will be created inside the location you specify for your Middleware home.

If you are performing an installation on a Windows operating system, be sure that your directory paths are valid and do not contain double backslashes (\\).

A.6 Installation Summary Screen

Review the information on this screen, and click Install to begin the installation. The operations summarized on this page will be performed when you click Install.

If you want to make any changes to the configuration before starting the installation, use the navigation pane and select the topic you want to edit.

If you want to save this configuration to a text file, click Save. This file can be used later if you choose to perform the same installation from the command line. See Appendix D, "Silent Installation" for more information.

A.7 Installation Progress Screen

This screen shows you the progress of the installation.

If you want to quit before the installation is completed, click Cancel. Doing so will result in a partial installation; the portion of the software that was installed on your system before you click Cancel will remain on your system, and you will have to remove it manually.

A.8 Installation Completed Screen

This screen summarizes the installation that was just completed.

If you want to save this summary information to a text file for future reference, click Save.

B Application Developer Configuration Screens

This appendix contains screenshots and descriptions for all of the Application Developer configuration screens:

- Welcome Screen

- Select a WebLogic Domain Directory Screen

- Select Domain Source Screen

- Select Extension Source Screen

- Specify Domain Name and Location Screen

- Configure Administrator Username and Password Screen

- Configure Server Start Mode and JDK Screen

- Select Optional Configuration Screen

- Configure Administration Server Screen

- Configure Managed Servers Screen

- Configure Clusters Screen

- Assign Servers to Clusters Screen

- Configure Machines Screen

- Assign Servers to Machines Screen

- Target Deployments to Servers or Clusters Screen

- Target Services to Servers or Clusters Screen

- Configure RDBMS Security Store Database Screen

- Configuration Summary Screen

- Creating Domain Screen

B.1 Welcome Screen

The Welcome screen is displayed each time you start the Oracle Fusion Middleware Configuration Wizard.

Select Create a new WebLogic domain to create a new WebLogic domain in your projects directory.

Select Extend an existing WebLogic domain if you want to add applications and services, or to modify existing configuration settings.

B.2 Select a WebLogic Domain Directory Screen

Select the WebLogic directory to which you want to add your applications and services.

B.3 Select Domain Source Screen

Select the source from which you want to create your new domain.

Select Generate a domain configured automatically to support the following products to create your domain to support selected products. Then, select the products for which you want support.

Select Base this domain on an existing template to create your domain based on an existing domain template. Click Browse to navigate your directories to find an existing template.

B.4 Select Extension Source Screen

Select the source from which you want to extend your domain.

Select Extend my domain automatically to support the following added products to extend your domain to support selected products. Then, select the products for which you want support.

Select Extend my domain using an existing extension template to extend your domain based on an existing extension template. Click Browse to navigate your directories to find an existing template.

If a conflict with an existing product is detected, you will see the following screen:

Select the action you want to take to resolve the conflict, then click OK. Select Apply this selection if further conflicts are detected (don't prompt) if this is the action you want to take for all conflicts during domain extension. You will not be prompted again.

B.5 Specify Domain Name and Location Screen

Specify the following information for the domain you are creating:

- 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. The default location is MW_HOME/user_projects/domains (on UNIX operating systems) or MW_HOME\user_projects\domains (on Windows operating systems), but you can specify any location.

Note:
On Windows systems, be sure to include the drive letter when you specify the domain location.

- Application Location
The absolute path to the directory where applications created in this domain should reside. The default location is MW_HOME/user_projects/applications (on UNIX operating systems) or MW_HOME\user_projects\applications (on Windows operating systems).

Note:
On Windows systems, be sure to include the drive letter when you specify the application location.

B.6 Configure Administrator Username and Password Screen

Create a user that will be assigned to the Administrator role. This user is the default administrator used to start development mode servers.

- User name
Specify the user name. The default name is weblogic.

- User password
Specify the password for the user.

- Confirm user password
Re-enter the user password.

- Description
Enter a description for the user. This field is optional.

B.7 Configure Server Start Mode and JDK Screen

In the WebLogic Domain Startup Mode section, select one of the following startup modes:

- Development Mode
Development mode should be used while you are developing your applications. Development mode uses a relaxed security configuration and enables you to auto-deploy applications. In this mode, boot.properties is used for username and passwords and polling is used for application deployment.

- Production Mode
Production mode shouldbe used when your application is running in its final form. A production domain uses full security and may use clusters or other advanced features. In this mode, usernames and passwords are required and polling is not used for application deployment.

In the JDK Selection section, select the recommended JDK for your startup mode from the list of available JDKs, or select Other JDK and click Browse to find another JDK on your system. The recommended JDKs are described in the text for each mode in the WebLogic Domain Startup Mode section.

B.8 Configure JDBC Component Schema Screen

Configure the schema owner and password for each component schema listed on this screen. Changes to any of the fields on this screen are applied to all selected component schema in the table.

For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port).

If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only.

Review the table on this screen and identify which fields you need to modify:

- 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 schema owner was assigned when you created the schema using RCU.

- Password
Specify the password for the schema. You specified this password when creating the schema 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 system where your database is running.

- Port
Specify the database listen port number.

B.9 Test Component Schema Screen

Verify that the connections to your data sources are successful.

B.10 Select Optional Configuration Screen

Select any category for which you want to perform custom or advanced configuration:

- Administration Server
Select this to edit your Administration Server settings. You will be able to:

- Change the name of your Administration Server (default is AdminServer).

- Specify custom port numbers.

- Configure the Administration Server to accept SSL connections.

- Managed Servers, Clusters and Machines
Select this to add or delete managed servers, clusters, and machines. You can also modify the settings of any existing server, cluster, or machine.

- Deployments and Services
Select this to customize how deployments and services are targeted to machines and clusters.

- JMS File Store
Select this to customize your JMS file store settings.

- RDBMS Security Store
Select this if you want to configure an external relational database management system (RDBMS) as a data store for various security providers.

B.11 Configure Administration Server Screen

The Administration Server is the primary tool used to manage a WebLogic Server domain.

One WebLogic Server instance in each domain is configured as the Administration Server. If you have multiple WebLogic Server instances, then all the other instances are referred to as Managed Servers. In a domain with only one WebLogic Server instance, that instance functions both as Administration Server and Managed Server.

- Name
Specify the name of your Administration Server. The default name is AdminServer.

- Listen Address
Use the drop-down list to select an address or range of addresses that the Administration Server will listen to for events. The default selection is All Local Addresses.

- Listen Port
Specify the listen port number. The default port number is 7001.

Select SSL enabled if you want your Administration Server to accept SSL connections. Be sure to specify the SSL Listen Port if you select the SSL enabled option.

B.12 Configure Managed Servers Screen

A managed server is an instance of WebLogic Server used to host enterprise applications. A typical production environment has at least one managed server, which is managed by the Administration Server.

Use this screen to add or delete managed servers; click Add to add a managed server. To delete a managed server, select the server name and click Delete.

For each managed server, specify:

- Name
Name of the managed server. Each server within the domain must have a unique name. The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only.

- Listen Address
Enter an IP address or DNS name if you want to limit the number of valid addresses for a server instance. Otherwise, URLs to the server can specify any of the host computer's IP address, any DNS name that maps to one of the IP addresses, or the localhost string.

- Listen Port
Enter the port number from which you want to access the server instance. If you run multiple server instances on a single computer, each server must use its own listen port.

Note:
Do not set the listen port number to 7001; this is the default port for the Administration Server.

- SSL Listen Port
Enter the port number from which you want to access the server instance for SSL connections - this column is only active if the corresponding SSL enabled checkbox in the same row is selected.

Click Switch Display to see the managed server information in tabs rather than in a table.

B.13 Configure Clusters Screen

A cluster consists of multiple managed server instances working together to provide increased scalability and reliability.

Use this screen to add or delete clusters; click Add to add a cluster. To delete a cluster, select the cluster name and click Delete.

For each cluster, specify:

- Name
Name of the cluster.

- Cluster messaging mode
If you are creating a cluster within a new WebLogic Server environment, Oracle recommends that you use the Unicast messaging type.

If you are creating a cluster within an existing WebLogic Server environment or you need to ensure backward compatibility with older versions of WebLogic Server, you must use the Multicast messaging type. This enables multiple applications to subscribe to a given IP address and port number and listen for messages.

Select "multicast" or "unicast" from the drop-down list. If you select "multicast" you must also provide:

- Multicast address
A multicast address is an IP address in the range from 224.0.0.0 to 239.255.255.255. The valid range is from 224.0.0.0 to 239.255.255.255. The default value used by WebLogic Server is 239.192.0.0. You should avoid using multicast addresses in the range x.0.0.1. This address must be unique to this cluster and should not be shared by other applications.

- Multicast port
The multicast port is used by cluster members to communicate with each other. Valid values are between 1 and 65535.

- Cluster address
Address of the cluster.

Click Switch Display to see the cluster information in tabs rather than in a table.

B.14 Assign Servers to Clusters Screen

This screen only appears if you created at least one cluster on the Configure Clusters Screen.

Use this screen to assign each managed server in your domain to a cluster.

B.15 Create HTTP Proxy Applications Screen

An HTTP proxy server proxies requests from a web server to WebLogic Server instances in a cluster, and provides load balancing and failover for the proxied HTTP requests.

If you want to proxy requests for a cluster, select Create HTTP Proxy next to the cluster name, then select a proxy server from the drop-down list in the "Proxy Server" field.

B.16 Configure Machines Screen

A machine is the logical representation of the computer that hosts one or more WebLogic Server instances. Each Managed Server must be assigned to a machine. The Administration Server and Node Manager are used to manage the machines defined on this screen.

If you are creating a new machine on a non-UNIX operating system, specify the following:

- Name
Name of the machine. This name is used to identify the machine within the WebLogic Server domain; it does not have to correspond to the machine's network name.

- Node manager listen address
Enter the DNS name or IP address on which the Node Manager listens.

- Node manager listen port
Enter the port number on which the Node Manager listens for incoming requests.

For UNIX machine, click the "Unix Machine" tab and specify the following:

- Name
Name of the machine. This name is used to identify the machine within the WebLogic Server domain; it does not have to correspond to the machine's network name.

- Post bind GID enabled and Post bind GID
Select Post bind GID enabled to specify a non-privileged group account under which the server instance runs, then enter the group in the Post bind GID column. The default group is nobody, which is a standard UNIX group ID that provides the least possible privileges. In a production environment, Oracle recommends that you create a group account specifically for running instances of WebLogic Server. .

- Post bind UID enabled and Post bind UID
Select Post bind UID enabled to specify a non-privileged user account under which the server instance runs, then enter the user in the Post bind UID column. The default user is nobody, which is a standard UNIX account that provides the least possible privileges. In a production environment, Oracle recommends that you create a user account specifically for running instances of WebLogic Server.

- Node manager listen address
Enter the DNS name or IP address on which the Node Manager listens.

- Mode manager listen port
Enter the port number on which the Node Manager listens for incoming requests.

B.17 Assign Servers to Machines Screen

Use this screen to assign each WebLogic Server instance to the corresponding machine on which it runs.

B.18 Target Deployments to Servers or Clusters Screen

Use this screen to target your deployments to servers or clusters. Doing so enables WebLogic Server to serve the deployment to clients.

The Configuration Wizard automatically takes care of all necessary deployment targeting. You should not have to change anything on this screen unless specifically directed to do so.

In the left pane, select the server or cluster. Then, select the deployment in the right pane that you want to target to the selected server or cluster. The "Target" column in the right pane shows you the servers and clusters to which each deployment is targeted.

B.19 Target Services to Servers or Clusters Screen

Use this screen to target your deployments to servers or clusters. Doing so enables WebLogic Server to serve the deployment to clients.

The Configuration Wizard automatically takes care of all necessary services targeting. You should not have to change anything on this screen unless specifically directed to do so.

In the left pane, select the server or cluster. Then, select the service in the right pane that you want to target to the selected server or cluster. The "Target" column in the right pane shows you the servers and clusters to which each service is targeted.

B.20 Configure JMS File Stores Screen

Edit the configuration information for the JMS file stores, which are used to store persistent messages and durable subscribers.

- Name
Alphanumeric (no spaces) name of your JMS file store. Each JMS file store configuration in your WebLogic environment must have a unique name, regardless of the domain or cluster in which it resides.

- Directory
Directory where the JMS file store is located.

- Synchronous write policy
Use the drop-down list to select one of the following for each file store:

- Cache-Flush
Transactions cannot complete until all of their writes have been flushed down to disk. This policy is reliable and scales well as the number of simultaneous users increases.

- Direct-Write
File store writes are written directly to disk. This policy is supported on Solaris and Windows. If this policy is set on an unsupported platform, the file store automatically uses the Cache-Flush policy instead.

- Disabled
Transactions are complete as soon as their writes are cached in memory, instead of waiting for the writes to successfully reach the disk. This policy is the fastest, but the least reliable (that is, transactionally safe). It can be much faster than the other policies, but power outages or operating system failures can cause lost or duplicate messages.

B.21 Configure RDBMS Security Store Database Screen

To make changs on this screen, select a database type from the drop-down list in the "Database Type" field. Then, select the appropriate driver in the "Driver" field.

Provide the following credentials for the selected database:

- DBMS SID
The service ID of your database; this is usually the same as the global ID.

- DBMS Host
The name of the system on which the database is running.

- DBMS Port
The listen port number of the database.

- User Name
The user name to access the database.

- User Password
The password for the database user.

- Confirm User Password
Re-enter the password for the database user.

Click Test Connection to make sure that the connection to your database is valid.

B.22 Configuration Summary Screen

Verify the information on this screen. In the Summary View field, select a category from the drop-down list to view information about that category:

- Deployment
Shows the deployments that will be configured in each cluster and server. You can click on the name of a deployment to view detailed information about the selected deployment.

- Application
Shows the applications that will be configured in each cluster and server. You can click on the name of an application to view detailed information about the selected application.

- Service
Shows the services that will be configured in each cluster and server. You can click on the name of a service to view detailed information about the selected service.

- Cluster
Shows the clusters that will be configured in this domain and the servers that will be configured in each cluster. You can click on each server name to view information specific to that server.

- Machine
Shows the machines that will be configured in this domain and the servers that will be configured in each machine. You can click on each server name to view information specific to that server.

- JMS Server
Shows the JMS file store information for each managed server.

Use the Previous button if you want to return to a previous screen to alter some portion of the configuration.

B.23 Creating Domain Screen

This screen shows the progress of the domain creation.

C Application Developer Deinstallation Screens

This appendix contains screenshots and descriptions for all of the Application Developer deinstallation screens:

- Welcome Screen

- Deinstall Oracle Home Screen

- Deinstall Progress Screen

- Deinstall Completed Screen

C.1 Welcome Screen

The Welcome screen is displayed each time you start the deinstaller.

C.2 Deinstall Oracle Home Screen

This screen shows the Oracle Home directory that is about to be deinstalled. This is the Oracle Home directory from which the deinstaller was started.

Note:
Before you choose to remove this Oracle Home, make sure that it is not in use by an existing domain.

C.3 Deinstall Progress Screen

This screen shows you the progress of the deinstallation.

If you want to quit before the deinstallation is completed, click Cancel.

C.4 Deinstall Completed Screen

This screen summarizes the deinstallation that was just completed.

D Silent Installation

This appendix describes how to install Application Developer from the command line in silent mode. This appendix contains the following topics:

- Section D.1, "What is a Silent Installation?"

- Section D.2, "Creating Response Files"

- Section D.3, "Pre-Installation Tasks"

- Section D.4, "Silent Installation Instructions"

- Section D.5, "Silent De-Installation"

D.1 What is a Silent Installation?

Silent installation eliminates the need to monitor the Application Developer installation because no graphical output is displayed and no input by the user is required.

Silent installation of Application Developer is accomplished by supplying the installer with a response file and using the -silent flag on the command line. The response file is a text file containing variables and parameter values which provide answers to the installer prompts.

Note:
For UNIX users, if this is a first time installation of Application Developer, you must create the oraInst.loc file before starting. Please refer to Section D.3.1, "UNIX Users: Creating the oraInst.loc File" for more information.
Following installation of Application Developer, you need to run the root.sh script as the root user. The root.sh script detects settings of environment variables and enables you to enter the full path of the local bin directory.

Note:
For Windows users, if this is a first time installation of Application Developer, you must create the registry keys before starting. Registry key creation is described in Section D.3.2, "Windows Users: Creating the Registry Key"

D.2 Creating Response Files

Before doing a silent installation, you must provide information specific to your installation in a response file. The installer will fail if you attempt an installation using a response file that is not configured correctly. Response files are text files that you can create or edit in a text editor

A sample response file called sampleResponse.rsp is provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory on the installation CD-ROM. After using this response file to install Application Developer, you will still need to run the Configuration Wizard to configure the software.

The only parameters you need to specify in this file are ORACLE_HOME and MIDDLEWARE_HOME. See Section D.2.1, "Contents of the sampleResponse.rsp File" to view the contents of this file.

D.2.1 Contents of the sampleResponse.rsp File

This section shows the contents of the Disk1/stage/Response/sampleResponse.rsp response file on a UNIX system:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Provide the Oracle Home location. The location has to be the immediate child under the specified Middleware Home location. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character. The total length has to be less than or equal to 128 characters. The location has to be an empty directory or a valid Application Developer Oracle Home.
ORACLE_HOME=/home/Oracle/Middleware/Oracle_APPDEV1

#Provide existing Middleware Home location.
MIDDLEWARE_HOME=/home/Oracle/Middleware

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

D.2.2 Creating Your Own Response Files

There are two ways to response create your own response file:

- Use the sampleResponse.rsp file as a template and copy it to any location on your system. You can then alter the contents as needed and use it for your silent installation.

- Run the installation GUI, then click Save on the Installation Summary Screen. You will be prompted for a name and location where you want to create this response file. After it is created, you can use it exactly as-is to replicate the installation on other systems, or modify it as needed.

D.2.3 Securing Your Silent Installation

Your response files contain certain passwords required by the installer. To minimize security issues regarding these passwords in the response file, follow these guidelines:

- Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent installation.

- If possible, remove the response files from the system after the silent installation is completed.

D.3 Pre-Installation Tasks

This section covers the pre-installation tasks that may be required before you are able to perform a silent installation.

The following topics are covered:

- Section D.3.1, "UNIX Users: Creating the oraInst.loc File"

- Section D.3.2, "Windows Users: Creating the Registry Key"

D.3.1 UNIX Users: Creating the oraInst.loc File

The Oracle inventory directory is used by the installer to keep track of all Oracle products installed on the computer. The inventory directory is stored in a file called oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation. This file is used by the installer.

1. Log in as the root user.

prompt> su

2. Using a text editor such as vi or emacs, create the oraInst.loc file in the directory of your choice. The contents of the file consist of the following two lines:

inventory_loc=oui_inventory_directory
inst_group=oui_install_group

Replace oui_inventory_directory with the full path to the directory where you want the installer to create the inventory directory. Then, replace oui_install_group with the name of the group whose members have write permissions to this directory.

3. Exit from the root user.

# exit

D.3.2 Windows Users: Creating the Registry Key

If you have not installed Application Developer on your computer, then you need to create the following Registry key and value:

HKEY_LOCAL_MACHINE / SOFTWARE / Oracle / inst_loc = [inventory_directory]

Replace Inventory_Directory with the full path to your installer files. For example:

C:Program Files\Oracle\Inventory

D.4 Silent Installation Instructions

The syntax for running the installer from the command line on UNIX systems is shown below:

runInstaller [-mode] [-options] [(<CommandLinevariable=Value>)*]

On Windows systems:

setup.exe [-mode] [-options] [(<CommandLinevariable=Value>)*]

Table D-1 Installer Command Line Parameters

Parameter

Description

Installation Modes - Only One Mode Can be Specified

-i

-install

Launches the installer in GUI mode. This is the default mode and is used if no mode is specified on the command line.

-silent

Install in silent mode. The installer must be passed either a response file or command line variable value pairs.

-d

-deinstall

Launches the installer in GUI mode for deinstallation.

-p

-prerequisite

Launches the installer in GUI mode but only checks the prerequsites. No software is installed.

-v

-validate

Launches the installer in GUI mode and performs all prequisite and validation checking, but does not install any software.

-sv

-silentvalidate

Performs all prerequisite and validation checking in silent mode. You must pass the installer either a response file or a series of command line variable value pairs.

Installation Options

-help

--help

--usage

Displays the usage parameters for the runInstaller command.

-invPtrLoc file

Pointer to the inventory location file. Replace file with the full path and name of the oraInst.loc file.

-response file

-responseFile file

Pointer to the response file. Replace file with the full path and name of the response file.

-jreLoc location

Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the jre directory where your JRE is installed.

-logLevel level

Specify the level of logging performed by the installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:

- severe

- warning

- info

- config

- fine

- finer

- finest

-debug

Obtain debug information from the installer.

-force

Allow the silent installation to proceed in a non-empty directory.

-printdiskusage

Log debugging information pertaining to disk usage.

-printmemory

Log debugging information pertaining to memory usage.

-printtime

Log debugging information pertaining to time usage. This command causes the timeTakentimestamp.log file to be created.

-waitforcompletion

Windows only - the installer will wait for completion instead of spawning the Java engine and exiting.

-noconsole

Messages will not be displayed to the console window.

-ignoreSysPrereqs

Ignore the results of the system prequisite checks and continue with the installation.

-executeSysPrereqs

Execute the system prequisite checks only, then exit.

-paramFile file

Specify the full path to the oraparam.ini file. This file is the initialization file for the installer. The default location of this file is Disk1/install/platform (on UNIX operating systems) or Disk1\install\platform (on Windows operating systems).

-novalidation

Disables all validation checking performed by the installer.

-nodefaultinput

For the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated.

Command Line Variables

Installer Variables

Installer variables are specified using varName=value.

An example for UNIX systems:

ORACLE_HOME=/home/Oracle/Middleware/Oracle_APPDEV1

An example for Windows systems:

ORACLE_HOME=C:\Products\Oracle\Middleware\Oracle_APPDEV1

Session Variables

Session variables are specified using session:varName=value.

Component Variables

Component variables are specified using session:compInternalName:[Version:]varName=value.

D.4.1 Sample Commands

If this is the first time you are installing on your system (meaning there is no pre-existing Oracle Inventory location), use the following command to perform a silent installation on UNIX systems:

./runInstaller -silent -response file -invPtrLoc file

On Windows systems:

setup.exe -silent -response file -invPtrLoc file

Below is a full example of this command for UNIX systems:

./runInstaller -silent -response /home/Oracle/response/appdev_inst.rsp -invPtrLoc /home/jdoe/oraInst.loc

On Windows operating systems:

setup.exe -silent -response C:\home\Oracle\response\appdev_inst.rsp -invPtrLoc c:\home\Oracle\oraInst.loc

If you have already installed an Oracle product on your system and do not need to specify an inventory location, then you can use a command similar to the following on UNIX systems:

./runInstaller -silent -response file

On Windows systems:

setup.exe -silent -response file

Below is a full example of this command on a UNIX system:

./runInstaller -silent -response /home/Oracle/response/appdev_inst.rsp

On Windows operating systems:

setup.exe -silent -response c:\home\Oracle\response\appdev_inst.rsp

D.4.2 Sample Output

Below is a sample output from a silent install using the sampleResponse.rsp template:

$ ./runInstaller -jreLoc /home/Oracle/Middleware/jdk160_14_R27.6.4-18/ -silent -response /home/Oracle/response/sampleResponse.rsp
Platform is Linux X86 32 bit
Starting Oracle Universal Installer...

Checking if CPU speed is above 300 MHz.    Actual 2999 MHz    Passed
Checking Temp space: must be greater than 150 MB.   Actual 69795 MB    Passed
Checking swap space: must be greater than 512 MB.   Actual 4029 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-22_12-35-31PM. Please wait ...[user@system Disk1]$ Log: /home/Oracle/oraInventory/logs/install2009-04-22_12-35-31PM.log
Copyright Â© 1999, 2009, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Expected result: One of enterprise-4,enterprise-5,redhat-4,redhat-5,SuSE-10
Actual Result: enterprise-4
Check complete. The overall result of this check is: Passed
CertifiedVersions Check: Success.
Checking for gcc-3.4.3-22.1; found gcc-3.4.6-10.0.1-i386.       Passed
Checking for gcc-c++-3.4.3-22.1; found gcc-c++-3.4.6-10.0.1-i386.       Passed
Checking for openmotif21-2.1.30-11.RHEL4.4 ; found openmotif21-2.1.30-11.0.1.RHEL4.6-i386.      Passed
Checking for setarch-1.6-1; found setarch-1.6-1-i386.   Passed
Checking for pdksh-5.2.14-30; found pdksh-5.2.14-30.6-i386.     Passed
Checking for sysstat-5.0.5-1; found sysstat-5.0.5-19.el4-i386.  Passed
Checking for gnome-libs-1:1.4.1.2.90-44.1; found gnome-libs-1:1.4.1.2.90-44.2-i386.     Passed
Checking for libstdc++-3.4.3-22.1 ; found libstdc++-3.4.6-10.0.1-i386.  Passed
Checking for libstdc++-devel-3.4.3-22.1; found libstdc++-devel-3.4.6-10.0.1-i386.       Passed
Checking for compat-libstdc++-296-2.96-132.7.2; found compat-libstdc++-296-2.96-132.7.2-i386.   Passed
Checking for compat-db-4.1.25-9; found compat-db-4.1.25-9-i386. Passed
Checking for control-center-2.8.0-12; found control-center-1:2.8.0-12.rhel4.5-i386.     Passed
Checking for glibc-common-2.3.4-2.9; found glibc-common-2.3.4-2.41-i386.        Passed
Checking for binutils-2.15.92.0.2-13; found binutils-2.15.92.0.2-25-i386.       Passed
Checking for make-1:3.80-5; found make-1:3.80-7.EL4-i386.       Passed
Checking for xscreensaver-4.18-5.rhel4.2; found xscreensaver-1:4.18-5.rhel4.14.0.1-i386.        Passed
Check complete. The overall result of this check is: Passed
Packages Check: Success.
Checking for VERSION=2.6.9; found VERSION=2.6.9-78.0.0.0.1.ELxenU.      Passed
Checking for hardnofiles=4096; found hardnofiles=4096.  Passed
Checking for softnofiles=4096; found softnofiles=4096.  Passed
Check complete. The overall result of this check is: Passed
Kernel Check: Success.
Expected result: ATLEAST=2.3.4-2.19
Actual Result: 2.3.4-2.41
Check complete. The overall result of this check is: Passed
GLIBC Check: Success.
Expected result: 922MB
Actual Result: 4000MB
Check complete. The overall result of this check is: Passed
TotalMemory Check: Success.
Verifying data......
Copying Files...
-----------20%----------40%----------60%----------80%--------100%

The installation of Oracle Application Developer 11g completed successfully.

D.5 Silent De-Installation

You can also de-install the software on your system by using the -d or -deinstall parameter from the command line.

On UNIX systems:

./runInstaller -silent -deinstall -response file

On Windows systems:

setup.exe -silent -deinstall -response file

E Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Application Developer. It contains the following sections:

- Section E.1, "General Troubleshooting Tips"

- Section E.2, "Troubleshooting Oracle Fusion Middleware Installation"

- Section E.4, "Need More Help?"

E.1 General Troubleshooting Tips

If you encounter an error during installation:

- Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network (http://www.oracle.com/technology/documentation).

- Verify that your computer meets the requirements specified in Section 1.1.1, "System Requirements and Certification".

- If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

- If an error occurred while the installer is copying or linking files:

1. Note the error and review the installation log files.

2. Remove the failed installation by following the steps in Chapter 3, "Deinstalling Application Developer".

3. Correct the issue that caused the error.

4. Restart the installation.

E.2 Troubleshooting Oracle Fusion Middleware Installation

This section contains solutions to common problems that you might encounter when installing Oracle Fusion Middleware. The following topics are covered:

- Section E.2.1, "Installation Log Files"

- Section E.2.2, "Configuration Log Files"

E.2.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the MW_HOME/oracle_common/oraInst.loc file. On Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

- installdate-time-stamp.log
This is the main log ifle.

- installdate-time-stamp.out
This log file contains the output and error streams during the installation.

- installActionsdate-time-stamp.log
This file is used by tbe installer GUI to keep track of internal information.

- installProfiledate-time-stamp.log
This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory and CPU details.

- oraInstalldate-time-stamp.log
This log file contains the output stream of the copy session.

If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log and timedate-time-stamp.log files are created in the same directory:

- timeTakendate-time-stamp.log
This file contains information for the amout of time taken to move between screens (applicable for GUI installations only).

- timedate-time-stamp.log
This file contains time information for the copy session.

If you start the installer with the -printmemory parameter, the memorydate-time-stamp.log file is created. This file contains memory usage information for the copy session.

E.2.2 Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:

On UNIX operating systems:

% ./config.sh -log=log_filename

On Windows operating systems:

G:\ config.cmd -log=log_filename

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the MW_HOME/oracle_common/common/bin (on UNIX operating systems) or MW_HOME\oracle_common\common\bin (on Windows operating systems) directory.

E.3 Keeping Track of Your JRE Location

The JRE location used by the Application Developer installer is stored in the MW_HOME/oracle_common/oui/oraparam.ini (on UNIX operating systems) or MW_HOME\oracle_common\oui\oraparam.ini (on Windows operating systems) file. This file is used by OPatch and Oracle Universal Installer (OUI) to determine the location of your preferred JRE.

It is possible to change the location of your JRE (for example, the JRE directory is moved out of the Middleware Home). If this happens, you will get an error message when trying to run OPatch or OUI since the JRE location can no longer be found. If this happens, you can do one of the following:

- Edit the MW_HOME/oracle_common/oui/oraparam.ini (on UNIX operating systems) or MW_HOME\oracle_common\oui\oraparam.ini (on Windows operating systems) file to point to the new JRE location.

- Use the -jreLoc command line option to point to the new JRE location. See Section 1.7.1, "Starting the Installer" for more information.

E.4 Need More Help?

If this appendix does not solve the problem you encountered, try these other sources:

- Oracle Fusion Middleware Release Notes, available on the Oracle Technology Network (http://www.oracle.com/technology/documentation)

- My Oracle Support (formerly OracleMetaLink: http://metalink.oracle.com)

If you do not find a solution for your problem, open a service request.

Index
A  C  D  E  I  J  L  M  N  O  P  R  S  T  U  V  W

A

accessibility

Java Access Bridge, 1.2

Administration Server

configuring, 2.1.5.1

starting, 2.3

stopping, 3.1.1

Administration Server console

accessing, 2.4

Application Developer

certification information, 1.1.1

configuring, 2

creating schemas for, 1.1.2

custom port numbers, 1.6

deinstalling, 3

installation log files, 1.7.2

installing, 1

installing on a multihomed computer, 1.5

installing on a non-networked computer, 1.4

silent installation, D

silent installation instructions, D.4

starting the deinstaller, 3.1.3.1

system requirements, 1.1.1

verifying the installation, 2.4

applying Java Required Files, 2.2

C

certification information, 1.1.1

clusters

configuring, 2.1.5.2

component schema

configuring, B.8

config.cmd command, 2.1.1 config.sh command, 2.1.1 configuration log files, 2.1.2, E.2.2 Configuration Wizard, 2.1

configuring JDBC component schema, B.8

configuring JMS file stores, B.20

configuring the Administration Server, 2.1.5.1

log files, 2.1.2

starting, 2.1.1

starting with Sun JDK, 2.1.1

configuring Application Developer, 2 configuring clusters, 2.1.5.2 configuring deployments, 2.1.5.3 configuring JMS file store, 2.1.5.4 configuring machines, 2.1.5.2 configuring managed servers, 2.1.5.2 configuring RDBMS security store, 2.1.5.5 configuring services, 2.1.5.3 configuring the Administration Server, 2.1.5.1 createCentralInventory.sh script, 1.7.3 creating a new WebLogic domain, 2.1.3 creating a response file (for silent installation), D.2 creating the Middleware Home directory, 1.1.3 creating the registry keys, D.1 custom port numbers, 1.6

D

deinstaller

starting, 3.1.3.1

deinstaller location, 3.1.3.1 deinstalling Application Developer, 3 deployments

configuring, 2.1.5.3

DHCP server, 1.3 documentation conventions, Preface dropping the Application Developer schemas, 3.1.2

E

Enterprise Manager

accessing, 2.4

extending an existing WebLogic domain, 2.1.4

I

installation instructions

Application Developer

installation instructions, 1.7

installation log files, 1.7.2, E.2.1 installer

running as root user, 1.7.4

installing on a DHCP host, 1.3 installing on a multihomed computer, 1.5 installing on a -networked computer, 1.4

J

Java Access Bridge, 1.2

Java Required Files, 2.2

applying, 2.2

Java Runtime Environment (JRE)

location of, 1.7.1

JDK

recommendations for development and production environments, 1.1.3

selecting, 1.1.3

JMS file store

configuring, 2.1.5.4, B.20

JRF

See Java Required Files

L

log files, 1.7.2, 2.1.2, E.2.1

for Configuration Wizard, E.2.2

for installation, E.2.1

loopback adapter

installing, 1.3.3

removing, 1.3.4

M

machines

configuring, 2.1.5.2

managed servers

configuring, 2.1.5.2

stopping, 3.1.1

MDS schema, 1.1.2.2 Microsoft SQL Server database

connecting with RCU, 1.1.2.2

Middleware Home

specifying the location, 1.7.4

Middleware Home directory

creating, 1.1.3

multihomed computer, 1.5 My Oracle Support, E.4

N

non-networked computer, 1.4

O

Oracle Common Home location, 1.7.4

Oracle database

connecting to, 1.1.2.2

connecting with RCU, 1.1.2.2

Oracle Fusion Middleware

stopping, 3.1.1

Oracle Inventory

specify group permissions, 1.7.3

specify location, 1.7.3

Oracle Inventory location, 1.7.3 Oracle Technology Network, E.4 Oracle WebCenter

creating the Middleware Home directory, 1.1.3

starting the installer, 1.7.1

WebLogic Server Home directory, 1.1.3

Oracle WebLogic Server

download location, 1.1.3

installation type, 1.1.3

installation types, 1.1.3

removing, 3.1.4

starting the installer, 1.1.3

windows shortcut, 1.1.3

Oracle WSM Policy Manager, 1.1.2

creating schemas for, 1.1.2

Oracle WSM-PM Extension, 1.1.2

creating schemas for, 1.1.2

oraInst.loc file, D.1

P

port numbers, 1.6

prefix, 1.1.2.2

R

RDBMS security store

configuring, 2.1.5.5

registry keys

creating, D.1

removing Oracle WebLogic Server, 3.1.4 Repository Creation Utility

connecting to Microsoft SQL Server database, 1.1.2.2

connecting to Oracle database, 1.1.2.2, 1.1.2.2

downloading, 1.1.2.2

mapping tablespaces, 1.1.2.2

specifying schema passwords, 1.1.2.2

starting, 1.1.2.2, 3.1.2.1

response file, D.1

creating, D.2

how to create, D.2.2

sample provided, D.2

root.sh script, D.1

S

sample response file, D.2

sample silent installation commands, D.4.1

sample silent installation output, D.4.2

schema passwords, 1.1.2.2

schema prefix, 1.1.2.2

schemas

dropping, 3.1.2

securing your silent installation, D.2.3 selecting a JDK, 1.1.3 services

configuring, 2.1.5.3

silent de-installation, D.5 silent installation, D

instructions, D.4

sample commands, D.4.1

sample output, D.4.2

securing, D.2.3

starting RCU, 3.1.2.1 starting the Administration Server, 2.3 starting the Configuration Wizard, 2.1.1 starting the installer, 1.7.1 stopping managed servers, 3.1.1 stopping Oracle Fusion Middleware, 3.1.1 stopping the Administration Server, 3.1.1 supported database, 1.1.2.1 system requirements, 1.1.1

T

troubleshooting, E

U

using custom port numbers, 1.6

V

verifying the installation, 2.4

W

WebLogic domain

creating, 2.1.3

extending, 2.1.4

WebLogic Server Home directory, 1.1.3 windows shortcut for Oracle WebLogic Server, 1.1.3

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.