|
Oracle® Developer Suite Installation Guide
10g Release 2 (10.1.2) for Solaris, Windows and Linux x86 B16012-03 |
|
 Previous |
 Next |
|
Oracle® Developer Suite Installation Guide
10g Release 2 (10.1.2) for Solaris, Windows and Linux x86 B16012-03 |
|
|
Previous |
Next |
Before you proceed with your installation, make sure you have reviewed and performed the preinstallation tasks described in Chapter 2, "Getting Started".
This chapter provides detailed installation steps and basic postinstallation tasks. The topics include:
For instructions on starting the installer, see Section 2.11.4, "Starting the Installer".
|
Note:
|
The installer first does automatic prerequisite checks. These run in a command line window which appears before the installer displays the Welcome screen. If a prerequisite check fails, the installer displays an error message and then stops. Section 2.11.2, "Installer Prerequisite Checks" describes the installer's automatic prerequisite checks.
Next, the installer displays the Welcome screen.
Review the Welcome screen and click Next.
The Welcome screen provides information about Oracle Universal Installer.
The following buttons appear on the Welcome screen and all installation screens that follow it:
Help: Provides detailed information about the functionality of each screen.
Installed Products: Displays currently installed products and deinstall products.
Back: Returns to the previous screen. This button is disabled on the Welcome screen.
Next: Advances to the next screen. This button may be disabled on some screens.
Install: Begins installing the files
|
Note: The Install button is disabled until you reach the Summary screen. |
Cancel: Terminates the installation process and exits the installer.
The Welcome screen has two additional buttons. They are:
Deinstall Products: Deinstalls individual products or all products.
About Oracle Universal Installer: Displays the version of the installer you are using.
For more detailed information about the Installed Products and Deinstall Products options, see Section 4.1.1, "Deinstalling Using the Installer".
If this is the first time you have installed an Oracle product on this computer, the installer creates the inventory directory for installation-related files (see Section 2.11.3, "The Installer Inventory Directory" for more information about this directory). The creation process differs between Windows, Linux, and Solaris:
Windows: The installer creates the directory system_default_drive\Program Files\Oracle\Inventory, where system_default_drive is the drive where you installed Windows, usually C.
Linux and Solaris: The Specify Inventory Directory screen appears. You must enter an existing directory as the location for the inventory directory. For example, you might use
/private1/oraInventory.
To navigate through the file system to select the inventory directory, use the Browse button.
To continue the installation process, click OK.
For Linux and Solaris only: (First time installation) At the UNIX Group Name screen, enter a group name.
The UNIX Group Name screen only appears when you run the installer for the first time on a computer. You use this screen to specify a group that has permission to read from and write to the inventory directory. For more information, refer to Section 2.9.6, "Creating Linux and Solaris Accounts and Groups".
UNIX Group Name: Enter the group name. This group should have read and write access to the inventory directory. The user that you are using to run the installer should be a member of this group.
When you have finished, click Next to continue.
For Linux and Solaris only: The installer displays a screen that prompts you to run the shell script orainstRoot.sh. You must run this script with root privileges. You may need to execute the shell script by typing "./" before orainstRoot.sh.
The screen lists the location of the shell script file. The script creates pointers to the components as the installer installs them in the computer so that they can be identified later in the installation procedure. The script creates the file /var/opt/oracle/oraInst.loc on Solaris, and /etc/oraInst.loc on Linux. This file provides a pointer to your inventory directory.
After you have run the script, return to this screen and click Continue to continue.
At the Specify File Locations screen, verify the source and destination paths and enter or select an Oracle home name.
The Specify File Locations screen lets you enter the full path for the source and destination locations for your installation.
Source: This is the full path to the products.jar file from which the product will be installed. The installer detects and uses the default values of the products.jar file of the installation program. Do not change the path.
Destination: This is the name and full path to the Oracle home where the product will be installed.
You may use the default name and path provided or select another name. See Section 2.7.1, "Oracle Home Considerations" if you need more information.
|
Note: The Oracle home path must be a real, absolute path. It cannot contain environment variable names or spaces. |
Do not install Oracle Developer Suite into an existing:
Oracle Developer Suite 10g (9.0.4) home directory
Oracle9iDS Release 2 (9.0.2) home directory
Oracle Internet Developer Suite home directory (former version of Oracle Developer Suite 10g (10.1.2.0.0)
Any Oracle Database home directory
For more information about Oracle homes, see Section 2.7, "Coexistence in One Oracle Home".
Browse: To navigate through the file system to find source and destination locations, click the Browse button.
When you have finished entering the information, click Next to continue.
If the computer you are installing on is part of a hardware cluster, the Specify Hardware Cluster Installation Mode screen may appear. Choose the option Single Node or Cold Failover Cluster Installation, which performs the installation on the current install node only (The Active Failover Cluster Installation option is not supported in this release).
At the Select Installation Types screen, select the type of installation you want to perform and the product languages to install. The available install options are:
J2EE Development: Select this option to install Oracle10g JDeveloper and its subcomponents (Oracle Business Intelligence Beans, UIX, Bali, and XDK), and Oracle Application Server Containers for J2EE (OC4J). This option configures OC4J as the default listener for testing purposes.
|
Note: OracleBI Beans is a component of JDeveloper. To use OracleBI Beans, install the J2EE Development option as well. |
Complete: Select this option to install all Oracle Developer Suite components. This option installs Oracle Forms Developer, Oracle Reports Developer, and Oracle10g JDeveloper. This option also installs OC4J, Oracle Application Server Reports Services, and Oracle Application Server Forms Services, and configures OC4J as the default listener for testing purposes.
Not all components are available on Linux and Solaris. See Table 2-3, "Operating Environments and Oracle Developer Suite Components" for the Oracle Developer Suite components that are installed on Linux and Solaris.
Product Languages: To select the languages that Oracle Developer Suite will run in, click the Product Languages button to display the Language Selection screen. You can install multiple languages and then switch between languages by changing the NLS_LANG environment variable. At runtime, if translations are available for the language specified in NLS_LANG, the component will display in the specified language, otherwise the product will run in English.
At the Language Selection screen, select the languages you want the installed product to run in. If you are running the installer in a locale that uses English, only English will be selected. If you are running the installer in a locale that uses another language, English and the locale's default language will be selected.
The Language Selection screen lets you select multiple languages to be installed. Do the selection by shuttling languages from the Available Languages list to the Selected Languages list. To do this:
Select a language or languages from the Available Languages list. To select more than one language, select one language and then hold down the CTRL key and select additional languages. Note that selecting languages here does not affect the language of the installation program itself.
After making your selections, click the right arrow button to move the selected languages to the Selected Languages list.
To select all the languages, click the double right arrow button.
To deselect a language, click the language and click the left arrow button to move the selected language back to the Available Languages list. To deselect all the languages, click the double left arrow button.
When you have finished selecting languages, click OK to continue.
When you have selected the type of installation you want to perform, and you have selected the product languages you want, click Next to continue.
For the Complete installation type, the installer displays the Provide Outgoing Mail Server Information screen. This screen lets you enter a name for the outgoing mail server that Oracle Application Server Reports Services (Reports Services) uses to distribute reports and send job success notifications through e-mail.
An example of a outgoing mail server name is mysmtp01.mycorp.com.
If you do not wish to use this feature, leave the name blank. You can change or configure it later.
When you have finished, click Next to continue.
Verify the information in the Summary screen and click Install to begin installing the files.
The Summary screen lets you review the selections you have made before the actual installation starts. The Summary list includes the source and destination locations, installation type, product languages, space requirements, and the components to be installed.
To make changes to any of the selections, click Back to return to the appropriate screen.
|
Note: Insufficient disk space is indicated in red under Space Requirements. |
The Install screen appears and the installer begins copying the required files for Oracle Developer Suite. Installation operations include executing actions such as file copy and linking, and execution decision points and calculations. At the Install screen, you can:
Monitor the installation process.
See the full path of the installation log. For more information about the installation log, see Section 2.11.3, "The Installer Inventory Directory".
Click Stop Installation... to discontinue the installation process. You can then choose to stop the installation of the entire product (default) or an individual component. Oracle recommends that you stop the entire product installation. If you choose to stop the installation of an individual component, associated components in the product may not function properly.
The Configuration Assistants screen may appear while the Oracle Net Configuration Assistant is running. This assistant configures basic network components and creates the tnsnames.ora and sqlnet.ora files for you. The Oracle Net Configuration Assistant tool is started by the installer. Click Help on the Oracle Net Configuration Assistant Welcome screen if you need information on how to use the tool.
Once you are finished with this screen, click Next to continue.
|
Note: The configuration assistant may run in silent mode, which means that its user interface will not be visible while it is running. The user interface may also appear only briefly before the assistant finishes. If the user interface appears and the installation pauses, the assistant has encountered an error. |
At the Configuration Assistants screen, you can:
Monitor the configuration process.
Click Stop to quit a configuration tool.
View the configuration settings that have been made by a configuration tool. Click a configuration tool name to display the configuration details in the display window.
Click Retry to execute the configuration tool again, if the tool failed to complete the configuration successfully.
For users of Windows assistive technologies: If you are using assistive technologies and you encounter a problem with the screen reader at this stage of the installation, follow these instructions:
Press ALT-F4 to cancel the Net Configuration Assistant, then exit the installer. This does not affect the Oracle Developer Suite installation; it only stops the Net Configuration Assistant tool.
Install Java Access Bridge 1.2 into the JVM locations on your computer. See Section 2.9.4, "Installing Java Access Bridge (Windows only)" for information on downloading and installing Java Access Bridge 1.2.
Set the following environment variable if it has not been set:
ORACLE_OEM_CLASSPATH=program_drive:\Program Files\Oracle\jre\1.4.2\ lib\access-bridge.jar;program_drive:\Program Files\Oracle\jre\1.4.2\ lib\jaccess.jar
where program_drive is the drive that contains the directory Program Files.
Restart your screen reader.
Restart the Net Configuration Assistant tool on the Windows Start Menu as follows:
Start | Programs | Oracle - DevSuiteHome | Configuration and Migration Tools | Net Configuration Assistant
If the installer is still displaying the Configuration Assistants screen, click Next to continue.
After installing the product, the installer displays the End of Installation screen.
To exit the installation program, click Exit. A message dialog appears, prompting you to confirm that you want to exit the installation program. Click Yes to exit; click No to continue with the installation program.
After successfully installing the product, proceed to Section 3.2, "Postinstallation Tasks" for further instructions.
The postinstallation tasks for Oracle Developer Suite are divided into the following parts:
Section 3.2.2, "Completing Component-specific Postinstallation Tasks"
Section 3.3, "Starting a Component"
|
Note: Unless otherwise noted,DevSuiteHome denotes the Oracle Developer Suite home directory you used during installation.
|
Review the following general postinstallation checklist and perform the tasks that apply to your installation and environment.
Once you have completed your installation, you should check for the latest certification and software updates on OracleMetalink (http://metalink.oracle.com). OracleMetalink provides access to technical information and assistance from Oracle Support Services, including information about:
product availability
certification
product alerts
bug information
patches
technical solutions
service request logging
Oracle Technology Network (http://www.oracle.com/technology/) also provides services and resources that developers can use to build, test, and deploy applications using Oracle products and industry-standard technologies.
You may have to perform some postinstallation tasks to enable NLS support for the components you have installed.
You can display the user interface for Oracle Developer Suite components (except for BI Beans) in any language you selected during installation. To do this, you set the NLS_LANG environment variable.
NLS_LANG controls the language, territory dependent conventions, and character set used by the component. Until you change NLS_LANG to a different value, all Oracle Developer Suite components will use its settings.
NLS_LANG has three parts: language, territory, and character set. They are set with the format
<language>_<territory>.<character_set>
For example, the value Japanese_Japan.JA16EUC sets NLS_LANG so that components run in Japanese, use Japanese cultural conventions, and use the EUC character set for data manipulation.
Refer to the Oracle Application Server Globalization Support Guide (included in the Oracle Application Server Documentation Library) for more documentation about NLS_LANG.
When you choose a set of product languages during installation, the installer automatically installs fonts so that the JDK can display the languages correctly. The fonts are installed in the directory DevSuiteHome/jdk/jre/lib/fonts.
Later, you may need to display text in a language that you did not choose during installation. If you are using a Java-dependent component, such as Oracle JDeveloper, UIX, or Oracle Reports Developer, you will not have the font that Java needs. To fix this, you can install the font manually.
The following Table 3-1 describes the fonts that are included with Oracle Developer Suite.
Table 3-1 NLS Fonts included with Oracle Developer Suite
| File Name | Description |
|---|---|
|
ALBANWTJ.TTF |
Albany WT Japanese font |
|
ALBANWTK.TTF |
Albany WT Korean font |
|
ALBANWTS.TTF |
Albany WT Simplified Chinese font |
|
ALBANWTT.TTF |
Albany WT Traditional Chinese font |
|
ALBANYWT.TTF |
Albany WT font for non-English languages other than Japanese, Chinese, or Korean. |
To install a font, choose the appropriate font name from the table, then install it by performing the following steps:
CD-ROM: Mount the Oracle Developer Suite CD-ROM labeled Disk 2. For instructions on how to mount the CD-ROM for your platform, see Section 2.11.4, "Starting the Installer".
DVD: Mount the Oracle Developer Suite DVD labeled "Oracle Developer Suite and Documentation." For instructions on how to mount the DVD for your platform, see Section 2.11.4, "Starting the Installer".
If the installer starts up, close it. You will not use it to install the fonts.
CD-ROM: Navigate to the root directory of the CD-ROM, then navigate to the subdirectory /extras/fonts.
DVD: Navigate to the root directory of the DVD, then navigate to the subdirectory /developer_suite/extras/fonts.
Copy the font file to DevSuiteHome/jdk/jre/lib/fonts.
Depending on the installation type selected, the tnsnames.ora and sqlnet.ora files may be installed in the DevSuiteHome\network\admin folder (Windows) or DevSuiteHome/network/admin directory (Linux and Solaris). You can update the files manually using a text editor, or use the configuration tool, Oracle Net Configuration Assistant. For more information about the configuration tool, refer to Oracle Database Net Services Administrator's Guide in the Oracle database documentation library.
The installer automatically assigns ports to Oracle Developer Suite components that require them. If the installer detects a port conflict while installing a component, it chooses an alternate port in the port number range allocated to the component. After installation, the installer creates a file that shows the port assignments it has made. You should review the port assignments to make sure that they are acceptable.
The port assignment file is called portlist.ini. It is located in the DevSuiteHome\install folder (Windows) or DevSuiteHome/install directory (Linux and Solaris). This file lists component entries as "port name = port value". For example:
Oracle Java Object Cache port = 7000 Oracle Intelligent Agent = 1748, 1754, 1808, 1809
Table 3-2 lists the default port numbers for each component, and the port number range that the installer uses if it detects a conflict:
Table 3-2 Port Numbers
| Components | Default Port Number | Port Number Range |
|---|---|---|
|
8888-8907 23910-23929 9240-9259 |
|
|
8888-8907 |
If you choose an installation type that installs both OC4J instances, then the installer sets port numbers that do not conflict with each other or with other port numbers.
To start and stop Oracle Developer Suite OC4J instances for Oracle Forms and Oracle Reports testing, do the following:
Linux and Solaris: use the scripts located in the DevSuiteHome/j2ee/DevSuite directory:
startinst.sh
stopinst.sh
Windows: use the scripts located in the DevSuiteHome\j2ee\DevSuite directory:
startinst.bat
stopinst.bat
or use the Start Menu to access the scripts, using one of the following:
Start | Programs | Oracle Developer Suite - DevSuiteHome | Forms Developer
Start | Programs | Oracle Developer Suite - DevSuiteHome | Reports Developer
and then selecting
Start OC4J Instance to start an OC4J instance
Shutdown OC4J Instance to stop an OC4J instance
If you use assistive technologies such as screen readers to work with Java-based applications and applets, the Windows-based computer where you have installed Oracle Developer Suite must have Sun's Java Access Bridge installed in all the Java virtual machine locations on the computer.
Use the steps below to make sure the Java Access Bridge files are set up properly.
To verify that Java Access Bridge files are installed:
These instructions assume that you have downloaded the Java Access Bridge 1.2 zip file, extracted the contents of the Zip file into a temporary directory named accessbridge_home, and installed Java Access Bridge 1.2. (See Section 2.9.4, "Installing Java Access Bridge (Windows only)" for more information.)
Confirm that the following files have been installed in the <DevSuiteHome>\jdk\jre\lib\ext directory, or copy them from <accessbridge_home>\installer\installerFiles:
access-bridge.jar
jaccess-1_3.jar
jaccess-1_4.jar
JavaAccessBridge.dll
JAWTAccessBridge.dll
WindowsAccessBridge.dll
Confirm that JavaAccessBridge.dll, JAWTAccessBridge.dll, and WindowsAccessBridge.dll, are added to the Windows\System32 folder. This ensures that the files are in the system path.
Ensure that the PATH environment variable has been updated to include the directory where the .DLL files are installed, <DevSuiteHome>\jdk\jre\lib\ext.
Ensure that the file accessibility.properties is in the folder <DevSuiteHome>\jdk\jre\lib. If necessary, copy the file from accessbridge_home\installer\installerFiles.
Ensure that the file accessibility.properties includes the following lines:
assistive_technologies=com.sun.java.accessibility.AccessBridge AWT.EventQueueClass=com.sun.java.accessibility.util.EventQueueMonitor AWT.assistive_technologies=com.sun.java.accessibility.AccessBridge
Start your screen reader.
Start the Developer Suite component.
Review the component-specific postinstallation checklist and perform any required tasks.
To effectively use Oracle10g JDeveloper, follow the instructions in this section. For information about supported deployment environments, see Section B.1, "Oracle10g JDeveloper".
You can migrate user settings from the production release of JDeveloper (9.0.2) or JDeveloper (9.0.4), to JDeveloper (10.1.2). To learn how to do this, see Section A.2.1, "Migrating JDeveloper User Settings from Release 9.0.2 to Release 10.1.2".
Oracle does not support direct migration from Oracle JDeveloper version 3.2.3 to 9.0.4 or 10.1.2.
Before you can use an extension in JDeveloper, you first need to download it from Oracle Technology Network. Some example extensions in JDeveloper include:
JUnit
WebDAV
iSQL*Plus
To automatically download and install an extension:
Start JDeveloper.
From the JDeveloper main menu, select Help | Check for Updates.
This menu option lists extensions that you don't have, lists newer versions of ones you have, and installs them after you select them.
To manually download an extension:
Go to the Oracle Technology Network page for JDeveloper extensions, http://www.oracle.com/technology/software/products/jdev/.
Select an extension.
Follow the instructions to download the Zip file.
To manually install an extension:
Shut down any instances of JDeveloper that are currently running on your computer.
Verify if there are additional installation instructions in the extension archive.
Unzip the downloaded Zip file into the directory DevSuiteHome\jdev\lib\ext.
Restart JDeveloper to use the extension.
For more information about JDeveloper extensions, see the JDeveloper online help.
A connection to an Oracle Software Configuration Manager (Oracle SCM) repository is required to perform source code control using Oracle SCM from JDeveloper. The repository resides within an Oracle database and must be precreated. Install the Rapid Application Development or Complete option, then use the Repository Administration Utility in Oracle SCM to create the repository in the database. For instructions on creating the repository, see the Oracle SCM Repository Installation Guide, which is available from the Start menu of the Oracle SCM client.
If you see an error similar to:
Font specified in font.properties not found [--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific]
when starting JDeveloper on a Linux and Solaris computer, your JDK is not configured to use the listed font. By default, JDeveloper uses the information in the file font.properties included with each JDK. If this file refers to fonts that are not available on your computer, you will see the error or one like it. To fix this, you either need to install a new font, or change your font.properties file. For information on installing new fonts on your computer, contact your vendor. For information on updating the font.properties file, see your JDK vendor's documentation or Sun's Font Overview documentation at
http://java.sun.com/j2se/1.3/docs/guide/intl/addingfonts.html
If you have set the IDE option to use hosted documentation, JDeveloper is pre-configured to use documentation hosted on Oracle Technology Network. The URL to the documentation set is:
http://www.oracle.com/technology/products/hosted_doc/jdev/jdeveloper/
When you start the hosted help system for the first time, it may take several minutes to initialize.
In addition to this site, you can set up your own host for serving hosted documentation. You may want to do this if you are behind a firewall, or you find network access times slow, or if you want to add information to the JDeveloper documentation. If you want to extend the JDeveloper documentation, refer to the Oracle Help for Java (OHJ) documentation, which is included with JDeveloper.
To host JDeveloper documentation:
Uncompress the jar files located in DevSuiteHome/jdev/doc/ohj onto your Web server. If you have the base install, you will have to download the documentation from Oracle Technology Network. Each Jar file should be uncompressed into its own directory.
Modify the jdeveloper.hs file to point to the correct URL for each of the subhelpsets on your server. Look at the file jdeveloper-hosted-example.xml in DevSuiteHome/jdev/doc/ohj/jdeveloper.jar for an example of how to configure this file.
Once you have done that, your users will have to set their copies of JDeveloper to use your new server. To do this:
From the JDeveloper main menu, select Tools | Preferences.
Navigate to Documentation.
Select the Use Hosted Documentation radio button.
Provide the URL to the jdeveloper.hs file on your server. This URL should include the port number, even if you are using the default port (80).
You can install JDeveloper in Microsoft Terminal Server or Citrix WinFrame environment, allowing many clients to access one installation of JDeveloper. In all cases, users can save their projects locally.
When you install and configure JDeveloper for a multiuser environment, you need to consider usage and resources, such as number of users and power of the server, so that you can provide the best performance.
Installing JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server
You need to have administrative privileges to install JDeveloper.
To install JDeveloper on a Citrix or Microsoft Server:
Install JDeveloper by selecting the J2EE Development installation type as described earlier.
Define the user home directory environment variable (see below).
Configuring User Home Directories in a Multiuser Environment
Although the following information is written for Windows, the configurations apply to Linux and Solaris as well.
Before you start JDeveloper in a terminal server environment, you must define the user home environment variable, and set its value for each user, so that JDeveloper can correctly identify individual user home directories. If the variable is not defined and set, JDeveloper uses the DevSuiteHome\jdev as the home directory for all users. Using this directory for all users may cause unstable behavior in JDeveloper.
To define the name of the user home environment variable:
Open the file DevSuiteHome\jdev\bin\jdev.conf in a text editor. Use an editor that recognizes Linux and Solaris end-of-line characters, such as WordPad.
Find the entry:
SetUserHomeVariable JDEV_USER_DIR
This is the default variable that JDeveloper will look for at startup. As the terminal server's administrator, you may change the name of this variable to follow your computer's naming conventions.
Save the file. If you are using WordPad, it will warn you that it is about to save the file in text-only format. You can ignore this warning.
To set the environment variable:
|
Note: Every user of JDeveloper on a multiuser computer must follow this procedure. |
From the Windows Start menu, choose Control Panel |System.
Select the Advanced tab, then Environment tab.
In the User Variables section, click New.
Add JDEV_USER_DIR, or the name you chose for SetUserHomeVariable, as a user-level environment variable.
Set its value to your home directory (e.g., N:\users\jdoe) and click OK.
To check your variable setting, open a command shell and enter
set
You should see output similar to the following:
JDEV_USER_DIR=N:\users\jdoe
Launch JDeveloper.
JDeveloper will ask if you would like your user home directory to be created. Select Yes.
Choose Help |About to verify that the value of ide.user.dir is set to your user home directory.
Configuring Terminal Server Clients for Running JDeveloper
These topics assume that you have already installed a Citrix WinFrame or Microsoft Terminal Server client locally and that JDeveloper has been installed and configured by the System Administrator.
To configure a terminal server client for JDeveloper:
Verify that the color resolution of the terminal server client has been set to a minimum of 256 colors. This minimum resolution is required by the JDK.
Log on to your terminal server.
Verify that the user home environment variable has been defined: Ask your System Administrator for the naming convention that is used on your computer. The default variable is JDEV_USER_DIR.
Set the user home environment variable:
From the Windows Start menu, choose Control Panel | System.
Select the Advanced tab, then click Environment Variables.
Add the variable to your User Variables and click OK. For example, you can define JDEV_USER_DIR as the variable containing the path to the user's home directory.
To check the correct variable settings, open a command shell and enter:
set
You should see output similar to the following:
JDEV_USER_DIR=n:\users\jdoe
Launch JDeveloper.
JDeveloper will ask if you would like your user home directory to be created. Select Yes.
Choose Help |About to verify that the value of ide.user.dir is set to your user home directory.
If you run JDeveloper in a multiuser environment and you see the error
The system DLL ole32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL Dynamically Allocated Memory occupied an address range reserved for Windows NT system DLLs. The vendor supplying the DLL should be contacted for a new DLL.
you need to update the DevSuiteHome\jdev\bin\jdev.conf file by adding the line:
AddVMOption -Xheapbase10000000
Use an editor, such as WordPad, that recognizes Linux and Solaris end-of-line characters. You may have to change the number if you still get the error when starting JDeveloper. When you save the file, WordPad will warn you that it is about to save the file in text-only format. Disregard this warning.
In addition, you will need to set the same option with the same value in Project | Default Project Settings | Runner | Java options.
To make this setting available to all users, exit JDeveloper, log on as an administrator and then copy the file
DevSuiteHome\jdev\multi\system\DefaultWorkspace\Project1.jpr
to
userhome\system\DefaultWorkspace\Project1.jpr
The J2EE Development installation includes a fully functioning version of Oracle Application Server Containers for J2EE (OC4J). If you use JDeveloper to test your applications, you are using the embedded version of OC4J, and you do not have to make any modifications to your configuration. If you would like to use the same configuration for your server, you can use the version included with JDeveloper.
To configure the OC4J server for non-embedded mode:
At the command line, in DevSuiteHome/j2ee/home run the command
java -jar oc4j.jar -install
The server will auto-unpack several jars. You will then be prompted to enter an admin password.
Enter a password and press Enter. Confirm the password by typing it again and press Enter.
Write down the password. You need this password to administer and stop the OC4J server.
The OC4J server is now installed and configured. You can now start the server.
|
Note: The administrative username is nowadmin, and the administrative password is the password you just entered. Use this username and password to administer and stop the server.
|
To start the OC4J server for use in non-embedded mode:
For Windows: Navigate to the directory DevSuiteHome\jdev\bin:
To start the server, run start_oc4j.bat:
DevSuiteHome\jdev\bin\start_oc4j.bat
To stop the server, run stop_oc4j.bat:
DevSuiteHome\jdev\bin\stop_oc4j.bat
For Linux and Solaris: Navigate to the directory DevSuiteHome/jdev/bin:
To start the server, run start_oc4j:
DevSuiteHome/jdev/bin/start_oc4j
To stop the server, run stop_oc4j:
DevSuiteHome/jdev/bin/stop_oc4j
Several jar files are auto-deployed and the server displays the following line:
Oracle Application Server Containers for J2EE 10g (10.1.2.0.2) initialized
For more information on fine tuning the OC4J server, see the OC4J documentation in the Oracle Developer Suite Documentation Library.
|
Note: The server must be running when you deploy projects to it. |
Using the included server will have no impact on using JDeveloper for testing and running your projects.
First, follow the steps in Section 3.2.1.6, "Assistive Technologies (Windows only)" to make sure the Java Access Bridge files have been installed properly. Then use the following instructions to make sure JDeveloper works with Java Access Bridge:
Start your screen reader.
Start JDeveloper.
A console window that contains error information (if any) will open first and then the main JDeveloper window will appear, once JDeveloper has started. Then the main JDeveloper window will appear once JDeveloper has started. Any message that appears will not affect the functionality of JDeveloper.
Complete the post-installation tasks that are appropriate for your site. Note that:
Before you can install the OracleBI Beans Catalog, you need access to a database user with DBA role privileges.
Before you can connect to data in JDeveloper, you must install and configure Oracle Database.
BI Beans supports data stored in the Oracle9i Release 2 Database or Oracle Database 10g Enterprise Edition. However, only particular releases and patchsets are supported as described in Section B.3.1, "Database Requirements for Oracle Business Intelligence Tools".
Consult the following sections, based on the database version to which BI Beans applications will connect:
Section 3.2.3.1.1, "Preparing an Oracle9i Release 2 Database for Use with BI Beans"
Section 3.2.3.1.2, "Preparing Oracle Database 10g Enterprise Edition for Use with BI Beans"
Complete the following tasks to run against Oracle9i Release 2 Database:
If you have not already done so, install the Oracle9i Release 2 Database.
For instructions, download the Oracle9i installation guide for the appropriate platform from Oracle Technology Network:
See Section B.3.1, "Database Requirements for Oracle Business Intelligence Tools" for information on which database versions are supported.
Note: When you install the database client, be sure to install it into a separate Oracle home directory.
Configure the database, following the configuration settings shown in Best Practices for Tabular Cube Aggregation and Query Operations. To access this document, download patch set 2529822. You must follow these configuration settings exactly to ensure that BI Beans works correctly and performs well. Because this document is updated as needed, check for a new version whenever you download a new patch set.
Define the appropriate OLAP metadata, as described in the Oracle9i OLAP Release 2 - User's Guide. This book is available on Oracle Technology Network (http://www.oracle.com/technology). If you do not define appropriate metadata, then you will not be able to create OLAP queries. Use one of the following tools to define the metadata:
The OLAP management tool of Oracle Enterprise Manager. See the Help system for Oracle Enterprise Manager for information.
OracleBI Warehouse Builder. See the OracleBI Warehouse Builder User's Guide for information.
To run against Oracle Database 10g Enterprise Edition, complete the following tasks:
If you have not already done so, install Oracle Database 10g Enterprise Edition.
For instructions, download the Oracle Database 10g Enterprise Edition installation guide for the appropriate platform from Oracle Technology Network:
See Section B.3.1, "Database Requirements for Oracle Business Intelligence Tools" for information on which database versions are supported.
Note: When you install the database client, be sure to install it into a separate Oracle home directory.
Configure the database, following the configuration settings shown in Best Practices for Tabular Cube Aggregation and Query Operations. To access this document, download patch set 3760779. You must follow these configuration settings exactly to ensure that BI Beans works correctly and performs well. Because this document is updated as needed, check for a new version whenever you download a new patch set.
Define the appropriate OLAP metadata, as described in the Oracle OLAP Application Developer's Guide. This book is available on Oracle Technology Network (http://www.oracle.com/technology). If you do not define appropriate metadata, then you will not be able to create OLAP queries. Use one of the following tools to define the metadata:
The OLAP management tool of Oracle Enterprise Manager. See the Help system for Oracle Enterprise Manager for information.
OracleBI Warehouse Builder. See the OracleBI Warehouse Builder User's Guide for information.
Analytic Workspace Manager. See the Oracle OLAP Application Developer's Guide for information.
In addition to preparing the database, perform the following tasks, as appropriate for your site:
See Appendix E, "Migrating Existing BI Beans Projects" for migration information.
By default, JDeveloper expects the JDK to be in the ..\..\jdk directory. If your JDK is not in the default location, then you must edit BIT_DevSuiteHome/jdev/bin/jdev.conf to change the setting of the SetJavaHome option.
During design with JDeveloper, your analyses are saved in your project. However, if you or your end users want to be able to share analyses and objects with other developers and end users, then you must install and configure the BI Beans Catalog, as described in the Help topic "Installing and Configuring the BI Beans Catalog."
To test your applications, you must install your chosen deployment environment. For more information, see the Help topic, "Requirements for the Deployment Environment."
BI Beans includes a utility that examines and reports on the configuration of your client environment. The purpose of the configuration diagnostic utility is to gather information about your configuration in order to diagnose problems. It displays information such as the release numbers for BI Beans, JDeveloper, and the Oracle Database, and it runs diagnostic tests against the OLAP Catalog metadata.
For complete information, see the "Verifying a BI Beans Client Configuration" topic in the BI Beans Help system.
To enable Oracle Application Server Portal integration, see Oracle Application Server Reports Services Publishing Reports to the Web in the Oracle Developer Suite Documentation Library.
If you plan to create reports of multidimensional data from Oracle Express Server, review the instructions for configuring the Express data source in the Oracle Reports Builder online help. Search for the topic "Configuring the Express Data Source." Oracle Reports Developer release notes also contain important information about preparing connections to the Oracle Express Server.
|
Note: Note: The Oracle Reports connection to Oracle Express Server is not supported on Linux. |
To start and stop Reports Services, see Oracle Application Server Reports Services Publishing Reports to the Web in the Oracle Developer Suite Documentation Library.
You can change the outgoing e-mail server in the Reports Server configuration file, reports_server_name.conf, located in the DevSuiteHome\reports\conf directory (Windows) or DevSuiteHome/reports/conf directory (Linux and Solaris).
Any reports that use the Merant JDBC drivers supplied with Oracle Application Server must be deployed with Oracle Application Server only. If you wish to deploy reports with JDBC queries against another application server, you must license the Merant drivers or use other JDBC drivers for development and deployment.
To use the Merant JDBC drivers supplied with Oracle Application Server, install the J2EE and Web Cache install option of Oracle Application Server into the Oracle home where you installed Oracle Developer Suite. Then modify the DevSuiteHome\reports\conf\jdbcpds.conf file (Windows) or DevSuiteHome/reports/conf/jdbcpds.conf file (Linux and Solaris) to specify the driver information of the Merant JDBC drivers.
The driver information is typically the driver name, connect string format, and the driver class.
For example, an entry for the Merant driver for Sybase would look like:
<driver name = "sybase-merant"
sourceDatabase = "sybase"
subProtocol = "merant:sybase"
connectString = "jdbc:subProtocol://databaseName"
class ="com.merant.datadirect.jdbc.sybase.SybaseDriver">
</driver>
where:
name is any unique name by which you want to refer to a specific JDBC driver you use in Oracle Reports Developer.
sourceDatabase is the name of the database you want to access.
subProtocol is a driver-specific name that you can find in the driver documentation. For example, for the Merant driver to the Sybase database, subProtocol is merant:sybase and for sql-server database it is sqlserver.
connectString is the format of the connect string of the driver.
In the example,
jdbc:subProtocol://databaseName specifies the format.
class is the main Java class file name of the driver. This value is specific to each driver; you can find it in the driver documentation. For example, the driver class name for the Merant driver to the Sybase database is com.merant.datadirect.jdbc.sybase.SybaseDriver and, for sql-server database, it is com.merant.datadirect.jdbc.sqlserver.SQLServerDriver.
For more information, see the chapter "Configuring and using JDBC PDS " of the Oracle Application Server Reports Services Publishing Reports to the Web manual in the Oracle Developer Suite Documentation Library. More guidelines on configuring the custom drivers are given in the DevSuiteHome\reports\conf\jdbcpds.conf file (Windows) or DevSuiteHome/reports/conf/jdbcpds.conf file (Linux and Solaris). You can also refer to the section "JDBC PDS" in the Oracle Reports Developer online help.
Before you can work with stored Java objects in Oracle Forms Developer 10g (10.1.2.0.2, Oracle Forms), you must install the necessary Java classes and PL/SQL package to the Oracle10g database. Follow these steps to install the Java Object support in Oracle Forms Developer:
Locate the installation scripts in the DevSuiteHome\dbs directory (Windows) or DevSuiteHome/dbs directory (Linux and Solaris). You will need the following files to install Java Object support:
dejavins.sql
dejavaux.sql
derefls.plb
dereflb.plb
dedbjava.jar
Run SQL*Plus from the same directory where the scripts are located.
Log in as SYSTEM.
If the installation is correct, then you will see the ORA_DE_REFLECTION package (derefls.plb and dereflb.plb) under the schema SYSTEM.
See Oracle Application Server Forms Services Deployment Guide in the Oracle Developer Suite Documentation Library for information about deploying Oracle Forms Developer applications to the Web using Oracle Application Server.
See Oracle Forms Developer and Forms Services Migrating Forms Applications from Forms6i in the Oracle Developer Suite Documentation Library for information that developers, system administrators, and DBAs need to know in order to migrate Oracle Forms Developer applications from Forms6i to Oracle Forms Developer 10g.
See the Oracle Forms Developer online help for the steps you need to take to configure source control management and the debugger, if you plan to use these features.
To configure a database for TranslationHub, use the Schema Manager. For information on using the Schema Manager, see the TranslationHub online help.
Before you start an Oracle Developer Suite component, make sure you have completed the general and component-specific postinstallation steps described in previous sections. Also, if you are upgrading from a previous version of a component, make sure you perform the necessary upgrade steps. Each component's upgrade procedure is documented in Appendix A, "Upgrade Notes".
For starting a component in a Linux86-64 environment, see Chapter 1, "Certification" in Oracle Developer Suite Release Notes.
Once you have completed a component's postinstallation and upgrade steps you can start the component, as follows:
Windows: To start JDeveloper, run the program DevSuiteHome\jdev\bin\jdevw.exe. To see a console window that displays diagnostic information, run the program DevSuiteHome\jdev\bin\jdev.exe.
Linux and Solaris: To start JDeveloper, run the program DevSuiteHome/jdev/bin/jdev.
Oracle Business Intelligence Beans is available as part of JDeveloper.
Windows: To start Reports Builder, from the Taskbar choose Start | Programs | Oracle Developer Suite - DevSuiteHome | Oracle Reports Developer | Reports Builder.
Linux and Solaris: To start Oracle Reports Developer, navigate to the DevSuiteHome/bin directory, then run rwbuilder.sh.
