Skip Headers

Oracle9i Application Server Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2)
Release 2 (9.0.2) for Windows NT/2000

Part Number A96157-02
Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

2
Using the Oracle9iAS Migration Assistant

This chapter describes the Oracle9iAS Migration Assistant, a tool that migrates Oracle HTTP Server, Oracle9iAS Containers for J2EE, and Web Cache from Oracle9iAS Release 1 (1.0.2.2.x) to Oracle9iAS Release 2 (9.0.2). The Assistant is available in GUI and command-line versions.


Note:

Oracle only supports the use of the Assistant for migrations from Release 1 (1.0.2.2.x).


By automating much of the migration process, the Oracle9iAS Migration Assistant eliminates errors associated with migrating files manually and expedites what can otherwise be a very lengthy process. It also prepares applications for use immediately after migration, enabling you to use the new Oracle9iAS release soon after installation.

This chapter contains these sections:

Understanding the Migration Assistant

Installing the Migration Assistant

Migrating Applications

Restarting the Oracle9iAS Migration Assistant

Understanding the Migration Assistant

This section details the overall functionality of the Assistant, and the specialized functionality for each of the migration options. The Migration Assistant is designed to:

Before starting the Assistant, read the section for each option you plan to use.

The Oracle HTTP Server Migration Process

This section describes the functionality of the Oracle HTTP Server migration option, and lists the elements migrated for each component. It contains the following topics:

Oracle HTTP Server Migration Candidates

The Oracle HTTP Server migration option recognizes the following configuration files, programs, static documents, and modules as candidates for migration:

Default modules

Table 2-1 lists the default set of modules shipped in Oracle9iAS Release 1 (1.0.2.2.x).

Table 2-1 Default Modules
Module Name

access_module

dir_module

oprocmgr_module

action_module

dms_module

perl_module

alias_module

env_module

proxy_module

anon_auth_module

expires_module

rewrite_module

asis_module

fastcgi_module

setenvif_module

auth_module

headers_module

speling_module

autoindex_module

imap_module

so_module

cern_meta_module

includes_module

ssl_module

cgi_module

info_module

status_module

config_log_module

isapi_module

userdir_module

dbm_auth_module

mime_module

usertrack_module

digest_module

mime_magic_module

digest_auth_module

negotiation_module

Default Directives in httpd.conf

Table 2-2 lists the directives found in both versions of the httpd.conf file.

Table 2-2 httpd.conf Default Directives
Directive Name

AccessFileName

HeaderName

AddCharset

HostnameLookups

ScriptAlias

AddEncoding

IfModule

ServerAdmin

AddHandler

IndexIgnore

ServerName

AddIcon

IndexOptions

ServerRoot

AddIconByEncoding

KeepAlive

ServerSignature

AddIconByType

KeepAliveTimeout

ServerType

AddLanguage

LanguagePriority

SetEnvIf

AddModule

Listen

SetHandler

AddType

LoadModule

SSLEngine

Alias

Location

SSLLog

Allow

LogFormat

SSLLogLevel

AllowOverride

LogLevel

SSLMutex

BrowserMatch

MaxKeepAliveRequests

SSLOptions

ClearModuleList

MaxRequestsPerChild

SSLPassPhraseDialog

CustomLog

MIMEMagicFile

SSLSessionCache

DefaultIcon

Options

SSLSessionCacheTimeout

DefaultType

Order

ThreadsPerChild

Deny

PerlHandler

Timeout

Directory

PerlModule

TransferLog

DirectoryIndex

PerlSendHeader

TypesConfig

DocumentRoot

PidFile

UseCanonicalName

ErrorLog

Port

UserDir

ExtendedStatus

ReadmeName

VirtualHost

Files

ScoreBoardFile

This is the default set of directives for Oracle HTTP Server migration. These directives occur in the default versions of the httpd.conf files in the 1.0.2.2 and 9.0.2 instances. The Assistant highlights the differences so that you can select them for migration. If the setting for a directive is the same in both files, no action is taken.

In the discussion of the migration process below, directives are described as primitive directives or container directives. Primitive directives occupy a single line; for example:

Timeout 300

KeepAlive on

Container directives occupy multiple lines, have a start directive and an end directive, and contain arguments (which are primitive directives). For example:

<Directory "myDirectory">
    Options FollowSymLinks MultiViews
    AllowOverride None
</Directory> 

The container directive above has start and end directives <Directory "myDirectory"> and </Directory. The arguments are the primitive directives Options FollowSymLinks MultiViews and AllowOverride None.

HTTP Server Elements Not Migrated

The Oracle HTTP Server migration option does not migrate:

JServ - JServ is included in Oracle9iAS Release 2 (9.0.2) only to support legacy use; the preferred servlet environment is Oracle9iAS Containers for J2EE (OC4J). If you used JServ in Release 1 and want to use OC4J in Release 2, see "Migrating JServ to OC4J". The manual process for migrating JServ is described there.

Configuration files related to the use of mod_plsql - Files such as oracle_apache.conf, plsql.conf, dads.conf and cache.conf and the Include directive in httpd.conf (for oracle_apache.conf) are excluded from the migration.

See Also:

Chapter 4, "Migrating Portals Components", "Migrating Database Access Descriptors" for instructions on migrating the mod_plsql configuration and "mod_plsql Parameter Changes in Release 2" for a complete list of parameter changes.

The HTTP Server Directive Migration Process

To migrate directives, the Assistant:

  1. Presents directives in the 1.0.2.2 httpd.conf file that are different from the default (uncustomized) file, httpd.conf.default, or that are new (not part of the default set of directives). The default file, httpd.conf.default, must be present or the program will not function.

    By default, all such directives are selected for migration via a checkbox and presented in a scrolling list. You can exclude a directive from the migration by clearing its checkbox.


    Note:

    An exception to this default selection of directives is the mod_proxy directive. All mod_proxy directives are unchecked by default. They will not be migrated unless they are explicitly selected in the httpd.conf: Directives screen (shown).



    Notes:

    Container directives are migrated as a whole; when you select a container directive for migration, you select all of the arguments (primitive directives) in it. For this reason, only the top level (that is, the start and end directives) of the container directive is presented as a migration selection.

    Path-related directives are presented with the destination path instead of the source path. For example, a directive from the Release 1 configuration such as

    ORACLE_HOME_1\Apache\Apache\myAlias

    will appear on the screen as

    ORACLE_HOME_2\Apache\Apache\myAlias


  2. Writes selected directives to a difference file.

  3. Merges the difference file with the 9.0.2 httpd.conf file as follows:

    • Default directives with changed settings replace the corresponding directive in the 9.0.2 httpd.conf file.

    • Non-default directives (that is, those not listed in Table 2-2) are written to the end of the 9.0.2 httpd.conf file.

  4. Discards JServ directives.

Migration of SSL Settings

To accommodate the replacement of standard SSL with mod_ossl in Oracle9iAS Release 2 (9.0.2), the Assistant automatically creates a directive for mod_ossl, SSLWallet, based on the Release 1 configuration. It then starts a program that generates an Oracle wallet. You can choose not to generate the wallet during migration by commenting out the SSL configuration in the Release 1 file before you start the Migration Assistant.

See Also:

Oracle9i Application Server Security Guide

To ensure that a valid wallet gets generated in the migration, you must specify the trust points (the signers of the certificates) in the Release 1 configuration. There are two ways to do this:

You can also import other certificate authority certificates into the wallet, by specifying them with the SSLCACertificateFile and SSLCACertificatePath in the Release 1 httpd.conf file.


Note:

The Release 1 default SSL certificate is signed by the certificate authority 'oracle demoCA', whose certificate is at

ORACLE_HOME_1\Apache\Apache\conf\ssl.crt\demoCAcert.crt 

Before migration, you must set the SSLCertificateChainFile directive to point to the default SSL certificate:

SSLCertificateChainFile ORACLE_HOME_
1\Apache\Apache\conf\ssl.crt\demoCAcert.crt

The Migration Assistant manages SSL certificate key file and wallet passwords as follows:

Table 2-3 SSL Password Requirements
If Release 1 SSL Certificate Key File has... Then during migration...

the default 'welcome' password

you are not prompted for a password.

a password other than 'welcome'

you are prompted to enter the correct password.

no password assigned

you are not prompted for a password, and the generated wallet password is set to 'welcome'.


Note the following changes:

The following directives are invalid in mod_ossl, and replaced by SSLWallet:

During migration, the Assistant extracts certificate-related directives and starts a program that generates a wallet. The wallet-related directives are written to the difference file. The value of SSLWallet is the value of SSLCertificateFile, or, if path-related:

ORACLE_HOME_2\Apache\Apache\conf\ssl.wlt\certificate name 

Wallet Generation for Default Virtual Host

The Assistant automatically generates the wallet for any virtual host that is SSL-enabled. The default httpd.conf file only defines one virtual host. If you override the certificate that is associated with the virtual host named in the Release 1 httpd.conf file, you can manually modify the Release 2 httpd.conf file after migration so that it points to the newly generated wallet.

Backup and Auditing Measures for Oracle HTTP Server Migration

The Assistant performs the following functions to provide a way to audit the migration process:

The Oracle9iAS Containers for J2EE (OC4J) Migration Process

This section explains the functionality of the OC4J migration option. It contains the following topics:

OC4J Migration Candidates

The OC4J migration option recognizes these configuration files and applications as candidates for migration:

Standalone OC4J Instances and Migration

If you installed OC4J in a standalone configuration prior to installing Oracle9iAS Release 1 (1.0.2.2.x), be aware that the Migration Assistant only migrates the OC4J instance bundled with Oracle9iAS Release 1 (1.0.2.2.x).

For example, suppose that:

  1. An OC4J instance was installed and configured, with applications deployed.

  2. Subsequently, Oracle9iAS Release 1 (1.0.2.2.x) was installed, with its bundled OC4J instance. The applications are still deployed on the original instance.

  3. The Migration Assistant is run.

    No applications are migrated, since they were not found on the Oracle9iAS Release 1 (1.0.2.2.x) OC4J instance.

The OC4J Configuration File Migration Process

The OC4J migration option does the following:

  1. Copies selected principals.xml and data-sources.xml from ORACLE_HOME_1\J2EE_containers\j2ee\home\config to ORACLE_HOME_2\j2ee\home\config.

  2. Reads application information from the server.xml file in ORACLE_HOME_1 and prompts you to select the applications to migrate.

  3. Starts a default OC4J instance in ORACLE_HOME_2.

  4. Re-deploys the migrated applications in ORACLE_HOME_2.

  5. Stops the default OC4J instance (and all of Oracle9iAS, if it was running).

J2EE Compliance Requirements for OC4J Migration

In Oracle9iAS Release 2 (9.0.2), OC4J deployment enforces J2EE compliance rules. For this reason, the Oracle9iAS Migration Assistant may not migrate applications that are not 100% J2EE compliant. The Assistant simply reads the files and attempts to deploy them to Oracle9iAS Release 2 (9.0.2); if deployment fails, it could be because an application is not J2EE compliant.

If the Assistant cannot deploy an application for any reason, it logs the exception, however, the exception may not be explicitly described as a compliance issue.

While the development of J2EE applications is standardized and portable, the XML configuration files are not. You may have to configure multiple XML files before deploying an application to OC4J. The configuration needed depends on the services the application uses. For example, if the application uses a database, you must configure the DataSource object in the data-sources.xml file.

Validating EAR Files for J2EE Compliance

The dcmctl utility (ORACLE_HOME_2\dcm\bin\dcmctl) provides a J2EE compliance validation command. It takes one input, the name of an EAR file, and lists non-compliant characteristics of that file. The syntax is:

dcmctl validateEarFile -v -f name.ear

where name is the name of the EAR file. -v specifies the verbose option of dcmctl; this provides the most detailed output of commands.

You must configure proxy settings so that the validation routine can access DTDs on the Web, if necessary (for example, on the Sun Microsystems site). To do this, you define an environment variable called ORACLE_DCM_JVM_ARGS, which specifies a hostname and port for the proxy. The command to do this is:

set ORACLE_DCM_JVM_ARGS=-Dhttp.proxyHost=host -Dhhtp.proxy.port=port

Example 2-1 validateEarFile Command and Output for J2EE-Compliant Application

ORACLE_HOME_2\dcm\bin> dcmctl validateEarFile -v -f ORACLE_HOME_
2\j2ee\home\applications\simple.ear

ORACLE_HOME_2\dcm\bin> echo off


No J2EE XML/DTD validation errors were found

Example 2-2 validateEarFile Command and Output for non- J2EE-Compliant Application

ORACLE_HOME_2\dcm\bin> dcmctl validateEarFile -v -f
ORACLE_HOME_2\j2ee\home\applications\petstore.ear
ORACLE_HOME_2\dcm\bin> echo off


Warning: J2EE/DTD validation errors were found
Cannot get xml document by parsing WEB-INF\web.xml in petstore.war:
Invalid element `servlet' in content of `web-app', expected elements
`[servlet-mapping, session-config, mime-mapping, welcome-file-list, 
error-page, taglib,resource-ref, security-constraint, login-config, 
security-role, env-entry, ejb-ref]'.

It is a good idea to review all applications for overall J2EE compliance before migrating them, since there are cases in which an application is deployable, but delivers unpredictable or undesirable server behavior. For example, ensure that content is served correctly by defining a unique context root for each application in application.xml.

Backup and Auditing Measures for OC4J Migration

The Assistant performs the following functions to provide a way to audit the migration process:

The Oracle9iAS Web Cache Migration Process

This section explains the functionality of the Web Cache migration option. It contains the following topics:

Web Cache Migration Candidates

The Web Cache migration option recognizes most of the elements in the webcache.xml file in ORACLE_HOME_1. They are listed in "The Web Cache Migration Process" below.

The Assistant does not migrate:

Migration of Session Definitions

A session defnition consists of a session name, a cookie, a URL parameter, and a default value. The Migration Assistant migrates session definitions as follows:

The Web Cache Migration Process

The Web Cache migration option does the following:

  1. Copies the following elements of the webcache.xml file from ORACLE_HOME_1 to ORACLE_HOME_2:

Backup and Auditing Measures for Web Cache Migration

The Assistant performs the following functions to provide a way to audit the migration process:

  1. Creates a backup copy of the webcache.xml file from ORACLE_HOME_2. The backup file is named webcache.xml.backup.

  2. Logs all migration activity and errors in

    ORACLE_HOME_2\migration\log\iASMigration.log 
    


    Note:

    The logging mechanism writes all pathnames with forward slashes instead of backward slashes.


Installing the Migration Assistant

This section provides information about hardware and software requirements for installation of Oracle9iAS Migration Assistant. The topics include:

Hardware Requirements

The following table, Table 2-4, "Oracle9iAS Migration Assistant Hardware Requirements" contains the minimum hardware requirements for the Oracle9iAS Migration Assistant.

Table 2-4 Oracle9iAS Migration Assistant Hardware Requirements

Hardware Items Minimum Requirements

CPU

An Intel-compatible 486 or higher processor

Memory

128 MB

Monitor

256 color viewing capability

Software Requirements

The Oracle9iAS Migration Assistant requires the following software:

Operating System Requirements

Table 2-5 lists the operating system requirements for the Oracle9iAS Migration Assistant.

Table 2-5 Oracle9iAS Migration Assistant Operating System Requirements

Software Items Version

Operating System

  • Microsoft Windows NT 4.0 with Service Pack 6a

  • Microsoft Windows 2000 with Service Pack 1 or higher

Virtual Memory

At least 360 MB of free virtual memory. To change the virtual memory setting, go to Control Panel and select System, then change the amount of memory under the Performance tab.

Starting Oracle Universal Installer

Follow these steps to launch Oracle Universal Installer, which installs the Oracle9iAS Migration Assistant:

  1. Stop all Oracle processes and services (for example, the Oracle database) running on the computer.

  2. Ensure that you are logged in to the computer as a member of the Windows Adminstrators group.

  3. Insert the Supplemental CD into the CD-ROM drive.

  4. Open the Start menu, select Run, and type G:\Setup.exe, where G is the CD-ROM drive letter.

    The Welcome screen appears (Figure 2-1).

    Figure 2-1 Oracle Universal Installer Welcome screen

    Text description of ouiwelNT.gif follows.

    Text description of the illustration ouiwelNT.gif

  5. Click Next.

    The File Locations screen appears (Figure 2-2).

    Figure 2-2 Oracle Universal Installer File Locations screen

    Text description of ouifilNT.gif follows.

    Text description of the illustration ouifilNT.gif

  6. Complete the Source... field with the location of the products.jar file on the Supplemental CD. You can type the path, or click Browse... to navigate to it.

  7. Complete the Destination... field with the Oracle home in which you want to install the Oracle9iAS Migration Assistant. The Name drop-down box contains a list of all middle-tier Oracle homes on the computer.


    Note:

    You can only install the Assistant into an existing Oracle9iAS Release 2 (9.0.2) Oracle home in a middle tier type of installation. You cannot install it into an infrastructure installation.


  8. Click Next.

    The Summary screen appears (Figure 2-3).

    Figure 2-3 Oracle Universal Installer Summary screen

    Text description of ouisumNT.gif follows.

    Text description of the illustration ouisumNT.gif

    This screen summarizes the choices on the File Locations screen: the path to products.jar and the destination Oracle home, as well as the installation type, language, and space requirements.

  9. If you need to change the source or destination path, click Previous and enter or select the path you want. Otherwise, continue with Step 6.

  10. Click Next.

    The Install screen appears (Figure 2-4).

    Figure 2-4 Oracle Universal Installer Install screen

    Text description of ouiinsNT.gif follows.

    Text description of the illustration ouiinsNT.gif

    This screen shows the progress of the installation of the Assistant to the selected Oracle home. The text above the progress bar indicates the installation actions as they occur. When the process completes, the End of Installation screen appears (Figure 2-5).

    Figure 2-5 Oracle Universal Installer End of Installation screen

    Text description of ouiendNT.gif follows.

    Text description of the illustration ouiendNT.gif

    This screen indicates the results of the installation process.

  11. Click Exit.

Migrating Applications

This section provides guidelines for preparing for a migration, and step-by-step instructions for starting and operating the Assistant.

Preparing to Migrate

This section outlines prerequisite steps for migrating.


Note:

You do not need to start Oracle9iAS before using the Migration Assistant. The Assistant will start an OC4J instance to deploy the OC4J applications, and then stop it when deployment is complete.


Information Requirements

Before you start the Assistant, be prepared with the following (as required for the components you plan to migrate):

SSL Configuration Requirements

If you want to use SSL with the Oracle HTTP Server in the Oracle9iAS Release 2 (9.0.2) environment, ensure that the following directives are configured (uncommented) in the httpd.conf file before you start the Assistant:

SSLCertificateFile and SSLCertificateKeyFile are necessary for any SSL-enabled web site, and if the configuration being migrated is an SSL configuration, these will be configured in httpd.conf in the Release 1 installation.

You must also ensure that the trust points are specified by some directive in the Release 1 installation. See "Migration of SSL Settings" for instructions on how to do this.

Using the Oracle9iAS Migration Assistant (GUI Version)

  1. If necessary, change to the directory in which the Assistant is installed (ORACLE_HOME_2\migration).

  2. Start the Assistant with the command:

    MigAssistant.bat
    
    

    The Oracle Home screen appears (Figure 2-6).

    Figure 2-6 Oracle Home screen

    Text description of ohoNT.gif follows.

    Text description of the illustration ohoNT.gif

  3. Complete the Source... field with the full path to ORACLE_HOME_1. You can:

    • Type the full path into the field.

    • Click Browse... to specify the path by navigating.

  4. Complete the Destination... field with the full path to ORACLE_HOME_2. You can:

    • Type the full path into the field.

    • Click Browse... to specify the path by navigating.

    If OC4J was not found in the Source... path you specified, the J2EE Home screen appears (Figure 2-7).


    Note:

    The Migration Assistant performs an existence check for OC4J in:

    ORACLE_HOME_1\J2EE_containers\j2ee\home,

    and presents the J2EE Home screen if it does not find it there.

    However, the Oracle9iAS Release 1 (1.0.2.2.x) installation may have placed it in:

    ORACLE_HOME_1\J2EE_containers\oc4j\j2ee\home.


    Figure 2-7 J2EE Home screen

    Text description of j2eehoNT.gif follows.

    Text description of the illustration j2eehoNT.gif

  5. If OC4J was installed in a location other than the Source... path, click the Migrate OC4J radio button and complete the 1.0.2.2 J2EE home path (type it or navigate to it), then click Next.

  6. If OC4J is not installed, or you do not intend to migrate it, click the Exclude OC4J radio button, then click Next.

    The Components screen appears (Figure 2-8). By default, all of the components are selected for migration.

    Figure 2-8 Components screen

    Text description of componNT.gif follows.

    Text description of the illustration componNT.gif

  7. To deselect a component for migration, click the checkbox to clear it.

  8. Click Next.

    If OC4J was selected, the OC4J screen appears (Figure 2-9). By default, all applications are selected for migration. See "OC4J Migration Candidates" for information on how the configuration files and applications are identified for migration.

    Figure 2-9 OC4J screen

    Text description of oc4jfiNT.gif follows.

    Text description of the illustration oc4jfiNT.gif

  9. To deselect a file or application for migration, click the checkbox to clear it.

  10. Click Next.

    If Oracle HTTP Server was selected, the Oracle HTTP Server screen appears (Figure 2-10). By default, all of the configuration files, CGI applications, and static documents found are selected for migration. See "Oracle HTTP Server Migration Candidates" for information on how the configuration files and applications are identified for migration.

    Figure 2-10 Oracle HTTP Server screen

    Text description of ohsfiNT.gif follows.

    Text description of the illustration ohsfiNT.gif

  11. To deselect a file or application for migration, click the checkbox to clear it.

  12. Click Next.

    If an SSL certificate file was found with a password other than the default 'welcome', the httpd.conf: Passwords screen appears (Figure 2-11).

    Figure 2-11 httpd.conf: Passwords screen

    Text description of passwoNT.gif follows.

    Text description of the illustration passwoNT.gif

  13. Complete the password field with the password for the certificate key file. The SSL wallet will be generated with this password.


    Note:

    The Assistant allows you three attempts to enter the correct password before setting the SSL-enabled component to non-migratable status. If this happens, you must migrate the component manually.


  14. Click Next.

    The httpd.conf: Directives screen appears (Figure 2-12), which is populated with the directives you can choose to migrate. By default, all directives except for mod_proxy are selected for migration. See "The HTTP Server Directive Migration Process" for information on how the Assistant compiled this list of directives.


    Note:

    A new directive will appear for the default virtual host to indicate the location of the wallet. Deselect this directive if you do not want it to be appended to the Release 2 httpd.conf file. See "Wallet Generation for Default Virtual Host".


  15. To deselect a directive, click the checkbox to clear it.

    Figure 2-12 httpd.conf: Directives screen

    Text description of directNT.gif follows.

    Text description of the illustration directNT.gif

  16. Click Next.

    The Summary screen appears (Figure 2-13), showing your choices of Oracle homes, configuration files, and applications.

    Figure 2-13 Summary screen

    Text description of summaNT.gif follows.

    Text description of the illustration summaNT.gif

  17. Review the choices.

  18. If necessary, click Back to navigate to previous screens to make changes.

  19. Click Next.

    The Warning screen appears (Figure 2-14).

    Figure 2-14 Warning screen

    Text description of warniNT.gif follows.

    Text description of the illustration warniNT.gif


    Warning:

    If you click Next now, the Assistant will begin to apply the current migration selections. Once the migration begins, you can click Cancel to stop the Assistant. It will finish the migration in progress (Oracle HTTP Server, OC4J or Web Cache), and then stop. No other selected migrations will start.

    To undo a migration, you must manually restore the configuration files in the 9.0.2 instance from a backup.

    For a description of backups and file names, see:


  20. Click Next to apply the migration choices you have made, or click Back to navigate to previous screens to make changes.

    The Migration Status screen appears with a progress bar showing the percentage of the migration completed (Figure 2-15).

    Figure 2-15 Migration Status screen

    Text description of statNT.gif follows.

    Text description of the illustration statNT.gif

  21. Click Finish to close the Migration Assistant.

  22. Review the log files.

  23. Perform tests for each application you migrated.

Using the Oracle9iAS Migration Assistant (Command Line Version)

  1. If necessary, change to the directory in which the Assistant is installed (ORACLE_HOME_2\migration).

  2. Start the Assistant with the command:

    MigAssistantCmd.bat
    
    

    The following prompt appears:

    Source Oracle home?
    
    
  3. Enter the path to ORACLE_HOME_1.

    The following prompt appears:

    Target Oracle home?
    
    
  4. Enter the path to ORACLE_HOME_2.

    A prompt resembling the following appears.

    Select components to migrate Migrate all components?[YES]n 
    
    
  5. Press Enter to accept the default in brackets, or type n and press Enter to answer No.

    The next prompt appears.

  6. Repeat Step 4 for each prompt. The remaining prompts resemble the following:

    Migrate all subComponents of PlugIn  Oracle9iAS Web Cache?[YES]n 
    
    Migrate webcache.xml[YES] 
    
    Migrate all subComponents of PlugIn Oracle9iAS Containers for 
    J2EE(OC4J)?[YES]n 
    
    Migrate data-sources.xml[YES] 
    
    Migrate principals.xml[YES] 
    
    Migrate all subComponents of PlugIn  Oracle HTTP Server?[YES]n 
    
    Migrate httpd.conf[YES] 
    
    Migrate Globals.java[YES] 
    
    Migrate Globals.class[YES] 
    
    Migrate Globals$__jsp_StaticText.class[YES] 
    
    Migrate globals.ser[YES] 
    
    Migrate _index.java[YES] 
    
    Migrate _index.class[YES] 
    
    Migrate _index$__jsp_StaticText.class[YES]
    
    Questionaire PlugIn Oracle HTTP Server httpd.conf 
    Please enter the password for ORACLE_HOME_
    1\conf\ssl.crt\server.crt:[welcome]
    
    
  7. Press Enter to accept the default password welcome, or type the password and press Enter.

    A summary of selections resembling the following appears:

    Summary page PlugIn Oracle9iAS Web Cache  
    webcache.xml PlugIn 
    Oracle9iAS Containers for J2EE(OC4J)  
    data-sources.xml  
    principals.xml  
    news.ear  
    petstore.ear  
    atm.ear PlugIn 
    Oracle HTTP Server  
    Globals.java  
    Globals.class  
    Globals$__jsp_StaticText.class  
    globals.ser  _index.java  _index.class  _index$__jsp_StaticText.class
    Start migration...
    
    
  8. Press Enter to start the migration.

    Migration processing begins. Status messages resembling the following appear:

    Migrating plugin   Oracle9iAS Web Cache
    Outcome Status code       0
    Status description            SUCCESS
    Migrating plugin   Oracle9iAS Containers for J2EE(OC4J)
    Outcome Status code       0
    Status description            SUCCESS
    Migrating plugin   Oracle9iAS HTTP Server
    Outcome Status code       0
    Status description            SUCCESS
    
    
  9. Review the log files.

  10. Perform tests for each application you migrated to ensure it is working as it did in the previous release.

Completing the Web Cache Migration

To complete the Web Cache migration, you may need to perform the following tasks. Use the Administration user interface to review and, if necessary, change the configuration as follows:


Note:

If, because of a port conflict, the Web Cache administration process does not start, you must specify the correct administration port in the MULTIPORT element of the webcache.xml file, and restart Web Cache.


Restarting the Oracle9iAS Migration Assistant

You must restore the Oracle9iAS Release 2 (9.0.2) instance to its pre-migration condition before you restart the Migration Assistant. Follow these steps:

  1. Delete the flag file firstRun from the Release 2 Oracle home directory.

  2. Restore all configuration files and directories to their pre-migration state. (Use the log file to determine which files were altered or copied.)

  3. Follow the instructions in:

    "Using the Oracle9iAS Migration Assistant (GUI Version)"

    or

    "Using the Oracle9iAS Migration Assistant (Command Line Version)" .


Go to previous page Go to next page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index