|
Oracle® Developer Suite Installation Guide
10g (9.0.4) for Windows, Linux, Solaris, and HP-UX Part No. B10579-02 |
|
|
|
|
Oracle® Developer Suite Installation Guide
10g (9.0.4) for Windows, Linux, Solaris, and HP-UX Part No. B10579-02 |
|
|
|
|
This appendix provides basic information about migrating or upgrading from a previous version of Oracle Developer Suite. The following topics are included:
Oracle Business Intelligence Beans
Oracle Discoverer Administrator
Oracle Software Configuration Manager
The previous versions of Oracle Developer Suite 10g (9.0.4) were Oracle 9iDS Developer Suite Release 2 (9.0.2), and before that Oracle Internet Developer Suite version 1.0.2.4.x. Oracle Developer Suite 10g (9.0.4) uses new versions of all components, as listed in Table A-1.
Table A-1 Updated Oracle Developer Suite Components
| Component | Release 1 Version 1.0.2.4.1 | Release 2 (9.0.2) Version | 10g (9.0.4) Version |
|---|---|---|---|
| Oracle9i JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) | 3.2.3Foot 1 | 9.0.2.x | 9.0.4.x |
| Oracle Reports Developer
|
6i Release 2 | 9.0.2.x | 9.0.4.x |
| Oracle Discoverer Administrator (formerly Discoverer Administration Edition) including Oracle Discoverer Desktop | 4.1.37 | 9.0.2.39 | 9.0.4.x |
| Oracle Warehouse Builder | 2.1.1.34.11 & 9.0.2.56.0 | 9.0.2.x | N/AFoot 2 |
| Oracle Forms Developer
|
6i Release 2, Patch 4a | 9.0.2.x | 9.0.4.0.4 |
| Oracle9i Application Server Clickstream Intelligence | N/A | 9.0.2.xFoot 3 | N/A |
| Oracle Software Configuration Manager
|
6i Release 4 | 9.0.2.80.11 | 9.0.4.x |
| Oracle Designer
|
6i Release 4 | 9.0.2.80.11 | 9.0.4.x |
Some components were also released individually. For example, Oracle9i JDeveloper was released as version 9.0.3, after the release of Oracle9i Developer Suite Release 2 (9.0.2). The version history for each component is documented in the component's specific instructions in this guide, and also in the component's release notes.
To successfully migrate from Oracle Internet Developer Suite version 1.0.2.x to Oracle Developer Suite 10g (9.0.4), you must install Oracle Developer Suite into a new Oracle home. See Section 2.6, "Coexistence in One Oracle Home" for information about installing Oracle Developer Suite over the former version.
After installing Oracle Developer Suite and performing the required postinstallation tasks, refer to the following subsections for migration information about each component.
You can migrate user settings from the production release of JDeveloper 9.0.2 to JDeveloper 9.0.4. Your system settings, libraries, and connections will be migrated.
Oracle does not support direct migration from version 3.2.3 to 9.0.4.
|
Note: Any time you use the following procedure to migrate user settings from another installation of JDeveloper, you lose any settings that you have made in the current installation. |
To migrate your user settings:
Start JDeveloper from a command line or shell prompt with the -migrate flag:
jdev -migrate
JDeveloper displays the Migrate User Settings dialog.
Select a version of JDeveloper to migrate.
If the Version dropdown list is empty, click Browse to search for a version. Select the directory previous_install_home\jdev\system (for Windows) or previous_install_home/jdev/system (for Linux, Solaris, and HP-UX), where previous_install_home is the home directory of the JDeveloper installation from which you want to migrate.
Select the settings and customizations you want to migrate. Oracle recommends that you select all the options.
Click OK. JDeveloper migrates your user settings.
If you are upgrading Oracle Business Intelligence Beans from a previous release, then you must configure your JDeveloper BI Beans projects. The procedure is slightly different if you are upgrading from release 9.0.2 than if you are upgrading from release 9.0.3.
To migrate projects created in release 9.0.2 to Oracle BI Beans release 9.0.4, perform the following tasks in the order shown. You must perform these steps for each project you wish to migrate:
Allow JDeveloper to configure the project.
Because JDeveloper 9.0.4 uses a different file format for its workspaces and projects, you must follow these steps to upgrade your existing workspaces and projects:
Open the workspace within JDeveloper 9.0.4.
Click Yes when prompted to upgrade the workspace.
The Upgrade UIX Installables dialog box appears if you are migrating an application that uses uiXML. Choose Do Nothing. You will perform the migration manually in step 5.
Configure the project to remove the ORB options.
Borland® Enterprise Server VisiBroker® Edition is no longer required to connect to Oracle9i. To remove all ORB-related VM options, follow these steps:
In the JDeveloper System Navigator, right-click the project node and choose Project Settings from the drop-down list.
Under Development, click Runner.
Delete the following Java Options:
Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB
Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB
DORBdisableLocator=true
Update the project settings.
|
Note: This step is necessary only if you have not added anything to the project. If you have added a tag or otherwise extended the project, then these steps will have happened automatically. |
Oracle BI Beans projects require the Oracle9i Release 2 JDBC drivers. It you have not already done so, you must upgrade the drivers, as described in Section 3.2.2.2, "Oracle Business Intelligence Beans" under "Additional Tasks". In addition, because BI Beans no longer supports Oracle9i Release 1, you must update the OLAP library. After the drivers have been upgraded, complete these steps:
While in the Project Settings dialog box with Runner selected, enter the following in the Java Options field, replacing oracle_home with the absolute path of the directory where JDeveloper is installed:
-Djava.ext.dirs=oracle_home/jdev/bibeans/jdbc/lib_92
Click Libraries.
Move Oracle JDBC 92 from Available Libraries to Selected Libraries.
Move OLAP API 92 from Available Libraries to Selected Libraries.
Click OK.
Upgrade applications that contain Oracle BI Beans servlets (Servlets only).
Note: Oracle BI Beans no longer supports Apache JServ.
In an application that contains a Oracle BI Beans servlet, you must update the servlet to reference the new style sheet. To do so, override the getStyleSheetName method in your BIController# class to return biaddins.xss, the name of the new style sheet.
Base classes for the BI Servlet have moved. You can address this change by creating a new project and generating a new servlet or, if you prefer, you can restore the base classes to their location in 9.0.2. If you choose to do this, then you will see a number of deprecation warnings, which you can ignore. To restore the 9.0.2 base classes, follow these steps:
Copy biservlet_902.zip from the bibeans/lib directory into the project source directory.
In the JDeveloper System Navigator, select the project that contains the servlet.
From the File menu, open biservlet_902.zip, which adds it to that project.
In the System Navigator, right-click the project node and choose Project Settings from the drop-down list.
Under Common, select Input Paths.
Click Edit to edit the Java Source Path field.
In the Edit Java Source Path dialog box, click Add Entry.
Browse to the project source directory and select biservlet_902.zip.
Click Select.
Upgrade the cabo directory (HTML-client applications only).
When you create an HTML project in JDeveloper, the cabo directory is created under the public_html directory. It contains the uiXML and Oracle BI Beans images, style sheet, and Javascript files, which can change between releases. To upgrade this directory, follow these steps:
Navigate to the public_html directory of the project to be upgraded.
Rename the cabo directory to cabo.9.0.2.
In JDeveloper, create a new project in the same workspace.
Select the project and, from the File menu, choose New.
In the Business Intelligence category, select Servlet application. (Even if you are not upgrading a servlet, you must choose Servlet application to ensure that you are getting the latest images.)
Complete the screens in the Servlet Wizard. After you specify a BI Designer, you can simply accept the defaults. When the servlet is generated, it creates a new cabo directory for the project.
Navigate to the public_html directory for this new project and copy the new cabo directory to the public_html directory of the project you are upgrading from BI Beans 9.0.2.
If your old directory (cabo.9.0.2) contained any other files (for example, if you created a new stylesheet or .xss file), then you must copy those files to the new cabo directory.
(Optional) You can safely delete the new project that was created.
Upgrade the Oracle BI Beans Catalog.
Perform the following steps to upgrade your Oracle BI Beans Catalog.
Important: If your existing BI Beans Catalog runs against release 8.1.7 of the Oracle database, then before performing these steps, you must upgrade the database to Oracle9i using standard database migration tools.
Ensure that the environment variable JDEV_ORACLE_HOME is set to the Oracle home directory.
Ensure that the environment variable JAVA_HOME is set to the directory where the JDK is installed.
Use the upgrade utility to upgrade the catalog. The utility is located in the oracle_home/bibeans/bin directory. Its syntax is as follows:
bi_upgradecatalog -u username -p password [-j oci8|thin] [-s servicename] | [-h hostname -po portnumber -sid sid]]
Example (using the recommended thin driver):
bi_upgradecatalog -u BIBCAT -p BIBCAT -j thin -h test-lap -po 1521 -sid orcl
To migrate projects created in release 9.0.3 to Oracle BI Beans release 9.0.4, perform the following tasks in the order shown.You must perform these steps for each project you wish to migrate:
Allow JDeveloper to configure the project.
Because JDeveloper 9.0.4 uses a different file format for its workspaces and projects, you must follow these steps to upgrade your existing workspaces and projects:
Open the workspace within JDeveloper 9.0.4.
Click Yes when prompted to upgrade the workspace.
The Upgrade UIX Installables dialog box appears if you are migrating an application that uses uiXML. Choose Do Nothing. You will perform the migration manually in step 4.
This changes the workspace and project files from the 9.0.3 format to the 9.0.4 format.
Update the library used by the project (for projects that used Oracle9i Release 1).
BI Beans 9.0.4 no longer supports Oracle9i Release 1. You must update the OLAP library used in your projects by performing the following steps:
In the system Navigator, right-click the project node and choose Project Settings from the drop-down list.
Under Development, click Libraries.
Select OLAP API 92 in the list of available libraries, then click the Move button (>) to move it to the list of selected libraries.
Select OLAP API 901 in the list of selected libraries, then click the Remove button (<) to remove it from the list.
Do not close the dialog. Continue with the next procedure.
Update the project settings.
|
Note: This step is necessary only if you have not added anything to the project. If you have added a tag or otherwise extended the project, then these steps will have happened automatically. |
BI Beans projects require the Oracle9i Release 2 JDBC drivers. It you have not already done so, you must upgrade the drivers, as described in Section 3.2.2.2, "Oracle Business Intelligence Beans" under "Additional Tasks". Because the location of the Release 2 JDBC drivers has changed, you must upgrade to the new drivers even if you did so in release 9.0.3. After the drivers have been upgraded, you must update the Java Options for each project, as follows:
While in the Project Settings dialog box, under Development, click Runner.
Enter the following in the Java Options field, replacing oracle_home with the absolute path of the directory where JDeveloper is installed:
-Djava.ext.dirs=oracle_home/jdev/bibeans/jdbc/lib_92
Click Libraries.
Move Oracle JDBC 92 from Available Libraries to Selected Libraries.
Click OK.
Upgrade the cabo directory (HTML client applications only).
When you create an HTML project in JDeveloper, the cabo directory is created under the public_html directory. It contains the uiXML and BI Beans images, style sheet, and Javascript files, which can change between releases. To upgrade this directory, follow these steps:
Navigate to the public_html directory of the project to be upgraded.
Rename the cabo directory to cabo.9.0.3.
In JDeveloper, create a new project in the same workspace.
Select the project and, from the File menu, choose New.
In the Business Intelligence category, select Servlet application. (Even if you are not upgrading a servlet, you must choose Servlet application to ensure that you are getting the latest images.)
Complete the screens in the Servlet Wizard. After you specify a BI Designer, you can simply accept the defaults. When the servlet is generated, it creates a new cabo directory for the project.
Navigate to the public_html directory for this new project and copy the new cabo directory to the public_html directory of the project you are upgrading from BI Beans 9.0.3.
If your old directory (cabo.9.0.3) contained any other files (for example, if you created a new stylesheet or .xss file), then you must copy those files to the new cabo directory.
(Optional) You can safely delete the new project that was created.
If you want to reuse the 6i Reports server persistent file and server configuration file, you can copy them to the Oracle Reports Server 10g 9.0.4 (Reports Server) directory. Reports Server will automatically convert your 6i files to the Reports Server 10g 9.0.4 format. To do this, copy the following files:
For Windows:
6i_oracle_home\reports60\server\report_server_name.ora
to
10g_oracle_home\reports\conf\report_server_name.ora
6i_oracle_home\reports60\server\report_server_name.dat
to
10g_oracle_home\reports\server\report_server_name.dat
For Linux, Solaris, and HP-UX:
6i_oracle_home/reports60/server/report_server_name.ora
to
10g_oracle_home/reports/conf/report_server_name.ora
6i_oracle_home/reports60/server/report_server_name.dat
to
10g_oracle_home/reports/server/report_server_name.dat
After opening a .rdf file from an earlier version of Oracle Reports, you must recompile the PL/SQL.
If you have installed a version of Oracle Discoverer from Oracle9iAS version 1.0.x, you will have Visibroker 3.4 running on your computer. Oracle Application Server Reports Services 10g (9.0.4) requires Visibroker 4.5, which cannot be run simultaneously with Visibroker 3.4. If you plan to install Oracle Application Server Reports Services 10g (9.0.4) onto the same computer with your older version of Oracle Discoverer, you must first shut down Visibroker 3.4. After installation, if you need to run your older version of Oracle Discoverer, you must manually stop Visibroker 4.5 and start Visibroker 3.4. Note that, when you have taken this action, you are effectively disabling the Oracle Application Server Reports Services 10g (9.0.4) component until you return to running Visibroker 4.5.
If you have an earlier version of Discoverer Administrator (formerly Discoverer Administration Edition) on your computer, you need to upgrade the End User Layer before you can use Oracle Discoverer Administrator to perform administration tasks (unless you have version 9.0.2.53 or later, in which case no EUL upgrade is required).
To upgrade an EUL, follow the instructions in Chapter 23 "Upgrading from earlier versions of Discoverer" of the Oracle Discoverer Administrator Administration Guide in the Oracle Developer Suite Documentation Library.
Review the guide Oracle Forms Developer and Forms Services: Migrating Forms Applications from Forms6i in the Oracle Developer Suite Documentation Library.
Oracle Software Configuration Manager was formerly Oracle Repository.
Please check OracleMetalink (http://metalink.oracle.com) for any patchsets to the product "Designer", release "Designer/Repository 9i" and upgrade your client software by installing the latest 9.0.4 patchset into the existing oracle_home before you upgrade/install your server side repository. This will avoid having to upgrade the repository twice.
If you are migrating from a pre-6i repository:
Install Oracle Developer Suite 10g using the Rapid Application Development or Complete install option.
Follow the instructions for installing a new repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
Follow the instructions for migrating data from an existing pre-6i repository to a new one in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
If you are upgrading from a release 6i or later repository:
Follow the instructions for upgrading a release 6i or later repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
Please check OracleMetalink (http://metalink.oracle.com) for any patchsets to the product "Designer", release "Designer/Repository 9i" and upgrade your client software by installing the latest 9.0.4 patchset into the existing Oracle home before you upgrade/install your server side repository. By doing this, you will avoid having to upgrade the repository twice.
If you are migrating from a pre-6i repository:
Install Oracle Developer Suite 10g using the Rapid Application Development or Complete install option.
Follow the instructions for installing a new repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
Follow the instructions for migrating data from an existing pre-6i repository to a new one in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
If you are upgrading from a release 6i or later repository:
Follow the instructions for upgrading a release 6i or later repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
All components have online help that is installed with the product. Some components provide additional documentation that is available on the Oracle Developer Suite Documentation Library.
For information on viewing and installing the Oracle Developer Suite Documentation Library, see Appendix C, "Installing the Documentation Library".
For documentation updates, white papers, or other collateral, please visit the Oracle Technology Network at
