Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Portal Server 6 2004Q2 Migration Guide 

Chapter 7
Migrating the Gateway, Netlet, and NetFile

Note

All instances of the Sun™ ONE Portal Server 3.0 product refer to what were formerly known as the iPlanet™ Portal Server 3.0, Service Pack 3a, iPlanet™ Portal Server 3.0, Service Pack 4 products, and iPlanet™ Portal Server 3.0, Service Pack 5 products.

This chapter describes the migration of the Sun ONE Portal Server 3.0 gateway attributes, NetFile, and Netlet to Sun™ ONE Portal Server, Secure Remote Access 6.2.

This chapter contains the following sections:

Overview

Migrating Sun ONE Portal Server, Secure Remote Access-related data from 3.0 to 6.2 involves running the Sun ONE Portal Server 3.0 Data Migration Tool Suite provided with Sun™ ONE Portal Server 6.2 and the Sun ONE Portal Server, Secure Remote Access migration scripts. If you install the Sun ONE Portal Server, Secure Remote Access migration scripts after installing the Sun ONE Portal Server 3.0 Data Migration Tool Suite, the Sun ONE Portal Server, Secure Remote Access installation of the migration tools copies the srapmigration.jar (containing the class files required for the migration) into the BaseDir/SUNWps/migration/modules/lib directory and creates the BaseDir/SUNWps/migration/modules/srap and BaseDir/SUNWps/migration/modules/srap_dp directories and places the modules in them.

Table 7-1 shows the file names and descriptions of the modules in the BaseDir/SUNWps/migration/modules/srap directory. This two-column table lists the module file name in the first column and the module description in the second column.

Table 7-1  Module File Names in the BaseDir/SUNWps/migration/modules/srap Directory 

Module File Name

Module Description

70srapexport

Copies gateway certificates to the export directory.

70srapconvert

Converts gateway data, NetFile, and Netlet.

70srapimport

Imports gateway certificates if detected, gateway data, NetFile, and Netlet into Sun ONE Portal Server, Secure Remote Access 6.2.

Table 7-2 shows the file names and descriptions of the modules in the BaseDir/SUNWps/migration/modules/srap_dp directory. This two-column table lists the module file name in the first column and the module description in the second column.

Table 7-2  Module File Names in the BaseDir/SUNWps/migration/modules/srap_dp Directory 

Module File Name

Module Description

43srapconvert

Creates display profile data for Sun ONE Portal Server, Secure Remote Access 6.2.

43srapimport

Imports display profile data created with the 43srapconvert module into Sun ONE Portal Server, Secure Remote Access 6.2.

You need to run the Sun ONE Portal Server 3.0 Data Migration Tool Suite script convertps to migrate the NetFile- and Netlet-related information.

The migration tools required for gateway migration are installed when you choose the option Install SRA Migration Tools during installation of Sun ONE Portal Server, Secure Remote Access 6.2.

Table 7-3 shows the two migration scripts and their descriptions. This two-column table shows the name of the migration script in the left column and its description in the right column.

Table 7-3  Sun ONE Portal Server, Secure Remote Access 6.2 Migration Tools

Name of Script

Description

exportsrap

Exports all Sun ONE Portal Server 3.0 gateway information. Use this tool only on the Sun ONE Portal Server 3.0 gateway system.

importsrap

Imports all exported gateway information into Sun ONE Portal Server, Secure Remote Access 6.2 in the required format. Use this tool only on the Sun ONE Portal Server 6.2 gateway system.

Gateway migration involves migrating the CA certificates from the certificate database.

You need to install the Sun ONE Portal Server, Secure Remote Access 6.2 migration tools on the Sun ONE Portal Server 3.0 gateway machine and also on the Sun ONE Portal Server, Secure Remote Access 6.2 gateway system.

Migrating the Sun ONE Portal Server, Secure Remote Access 6.2 components involves the following configurations of Sun ONE Portal Server 3.0 portal server and the gateway:

Sun ONE Portal Server 3.0 Gateway and Server on the Same Machine

This scenario requires installation of:

Sun ONE Portal Server 3.0 Gateway and Server on Different Machines

This scenario requires installation of:

To Add the Migration Tools to the Sun ONE Portal Server 3.0 Gateway Machine

To install only the migration tools on the Sun ONE Portal Server 3.0 Gateway Machine:

  1. Insert the Java Enterprise System CD into the Sun ONE Portal Server 3.0 Gateway Machine.
  2. Change directories to the directory where the SUNWpsmig and SUNWpsgwm packages are located. The packages are located in the Product/portal_srv/Packages directory. The location of the Product directory is at the same level as the installer script and depends on the platform you are using. For example, if using Solaris SPARC:

    3. cd /orion/s9orion/orion1of2_sparc.s9_orion/latest/Solaris_sparc/
    Product/portal_srv/Packages

  3. Use the pkgadd command to add the two gateway migration packages.

    4. pkgadd SUNWpsmig

    pkgadd SUNWpsgwm

    The migration tools are installed in BaseDir/SUNWps/migration/

Migrating Sun ONE Portal Server 3.0 Gateway Data

Migrating the gateway data involves running the exportsrap script on the Sun ONE Portal Server 3.0 gateway machine, and the importsrap script on the Sun ONE Portal Server, Secure Remote Access 6.2 gateway system.

Run exportsrap if the gateway is on a standalone machine. Otherwise SRA Migration is an option on the export menu when you run exportps.

Note

If you have installed the Sun ONE Portal Server, Secure Remote Access 6.2 migration tools, Netlet and NetFile are migrated as part of the Sun ONE Portal Server 3.0 Data Migration tools.

Ensure that you run the Sun ONE Portal Server 3.0 Data Migration Tool Suite and the Sun ONE Portal Server, Secure Remote Access 6.2 migration scripts for a complete gateway migration.

Migrating Gateway Data From a Stand-Alone Gateway System

Migrating the Sun ONE Portal Server 3.0 gateway data involves several steps as follows:

  1. As root on the gateway system, change to the directory containing the Sun ONE Portal Server, Secure Remote Access migration tools. For example:

    2. cd BaseDir/SUNWps/migration/bin

  2. Run the exportsrap script. For example:

    3. ./exportsrap

    You see the messages similar to the following on your screen:

    Which directory should be created to store the gateway certificates? [/tmp/psExport]

  3. Press Enter to accept the default directory /tmp/psExport or type in the name of another directory. You see messages similar to the following.

    4. If the export directory already exists, you see a message similar to the following:

    Export directory /tmp/psExport already exists.

    Delete the directory /tmp/psExport?

  4. Type yes and press Enter if you want to delete the directory or type no if you do not wish to delete the directory. You see messages similar to the following:

    5. Found iPS version 3.0sp5

    Begin export process at Tue Sep 17 01:26:41 GMT 2003

    Error file: /tmp/psExport/logs/error.13026

    Report file: /tmp/psExport/logs/report.13026

    Copying certificates

    Successful completion of export process at Tue Sep 17 01:26:42 GMT 2003

  5. On the Sun ONE Portal Server 3.0 system, change to the directory above the export directory containing the data output by the export tool.

    6. For example, if you used the default directory (/tmp/psExport) for exporting the Desktop, you would type:

    cd /tmp

  6. Save the export directory using the tar command. For example:

    7. tar cvf export.tar psExport

  7. Use an FTP program to transfer the export.tar file to the Sun ONE Portal Server 6.2 gateway system.
  8. Extract the files from export.tar using the tar command. For example:

    9. tar xvf export.tar

  9. On the Sun ONE Portal Server 6.2 system, change to the migration tool directory:

    10. cd BaseDir/SUNWps/migration/bin

  10. Run the importsrap command. For example:

    11. ./importsrap

  11. You see output similar to the following on your screen:

    12. Which directory contains the exported gateway certificates? [/tmp/psExport]

  12. Press Enter to accept the default directory /tmp/psExport or type in the name of the directory containing the exported data. You see messages similar to the following:

    13. Begin import process at Tue Sep 17 12:16:40 IST 2003

    Error file: /tmp/psExport/logs/error.14557

    Report file: /tmp/psExport/logs/report.14557

    Gateway platform configuration file created.

Migrating Gateway Data From a System Containing the Gateway and Server

This section provides instructions for running the three migration tools that make up the Sun ONE Portal Server 3.0 Data Migration Tool Suite.

To Run the Export Tool

  1. On the Sun ONE Portal Server 3.0 system, change to the migration tool directory:

    2. cd BaseDir/SUNWps/migration/bin/

  2. Run the exportps command:

    3. ./exportps [-a] [-p LDAP passphrase] [ExportDir]

    Table 7-4 describes the options available for exporting gateway data and gateway certificates. This two-column table lists the options in the first column and their descriptions in the second column.

    Table 7-4  Options Available for Exporting Gateway Data and Gateway Certificates

    Option

    Description

    -a

    Runs all modules without a menu. If you do not use the -a option, the tool will display an export menu listing the exportable types of data.

    To choose to export only gateway data and gateway certificates from the export menu, do not use the -a option.

    -p LDAP passphrase

    Sets the LDAP passphrase in order to avoid the LDAP passphrase prompt. If you do not use the -p LDAP passphrase option with the -a option, the tool will prompt you for the LDAP passphrase.

    ExportDir

    Specifies the directory where the information is to be saved. If you do not use the ExportDir option, the tool prompts you for the export directory.

  3. The system displays message similar to the following:

    4. Which directory should be created to store the Portal Server system? [/tmp/psExport]

    You see this prompt only if you do not specify the output directory on the command line. You can choose the default directory /tmp/psExport or enter the export directory.

    Type the directory and press Enter.

  4. The system displays a message similar to the following:

    5. Delete the directory /tmp/psExport?

    You see this message only if there is already exported data in the ExportDir directory. If you have not already exported gateway data and certificates, you may keep the export directory without risking any conflicts in the data. If you have already exported gateway data and certificates, you should delete the directory to avoid conflicts.

  5. The system displays a message similar to the following:

    6. Found iPS version 3.0sp5

    Begin export process at Mon Sep 9 10:30:14 PDT 2003

    Error file: /tmp/psExport/logs/error.11390

    Report file: /tmp/psExport/logs/report.11390

    Metrics file: /tmp/psExport/logs/export_metrics.11390

    Export Menu:

    1) LDAP Database

    2) Desktop

    3) Certificate Databases

    4) SRA Migration

    5) All of the above

    6) Exit

    Select one of the listed options to export:

    You see the export menu only if you do not specify the -a option. The SRA Migration option exports only the certificate data. When exporting the LDAP database, you must also export the Desktop.

  6. Type 4 and press Enter to export the gateway.
  7. The system displays the following message:

    8. Enter the LDAP admin passphrase :

    You see this prompt only if you select a full export using the -a option and you do not specify the -p LDAP passphrase option.

    Type the LDAP admin passphrase and press Enter.

    You see output similar to the following:

    Enter the LDAP admin passphrase :

    Dumping the ldap database

    organizationalPerson

    user

    role

    domain

    application

    Dumping xml

    .....................

    Copying templates and resource bundles

    Copying certificates

    Exporting gateway certificates

    Successful completion of export process at Mon Sep 9 10:33:34 PDT 2003

  8. Change to the export directory you specified in Step 2 or Step 3. For example:

    9. cd ExportDir

    Substitute the export directory for ExportDir. If you used the default export directory, for example, use /tmp/psExport.

    Type ls to see the directories created by the export tool.

    Table 7-5 shows the directory created by the export tool when exporting gateway data and gateway certificates. This two-column table lists the directory in the first column and its description in the second column.

    Table 7-5  Directory Created by the Export Tool When Exporting Gateway Data and Gateway Certificates 

    Directory

    Description

    ExportDir/srap

    Contains the gatecert subdirectory where exported gateway certificates are stored.

    After the export has completed, or if you run into problems, check the ExportDir/logs directory for the report.PID, error.PID, and export_metrics.PID files (where PID is the process ID). The report.PID file contains actions the export tool has or has not taken. The error.PID file contains warnings or errors so that you can correct any problems. The export_metrics.PID file contains metrics detailing when various elements of the export tool started, stopped, and the total time it took to export the data. You can look at the stdout header to know which log and report files to examine for the exportps command you are running.

  9. Examine the exported data and verify all instances of the name of the Sun ONE Portal Server 3.0 system have been changed to the name of the Sun ONE Portal Server 6.2 system. Although the tool should pick up these values from the Sun ONE Portal Server 6.2 packages, you must still verify these values and manually change, if necessary before converting the data. If the port numbers on the two systems are different, you must verify and change these manually if necessary as well.

    10. If you are performing a single-system migration, server names will be the same, but port numbers will be different. Again, you need to verify and change port numbers manually if necessary before converting the data.

To Run the Conversion Tool

  1. On the Sun ONE Portal Server 3.0 system, change to the directory above the export directory containing the data output by the export tool.

    2. For example, if you used the default directory (/tmp/psExport) for exporting the gateway data and gateway certificates, you would type:

    cd /tmp

  2. Save the export directory using the tar command. For example:

    3. tar cvf export.tar psExport

  3. Use an FTP program to transfer the export.tar file to the Sun ONE Portal Server 6.2 system.
  4. Extract the files from export.tar using the tar command. For example:

    5. tar xvf export.tar

  5. On the Sun ONE Portal Server 6.2 system, change to the migration tool directory:

    6. cd BaseDir/SUNWps/migration/bin

  6. Run the convertps command:

    7. ./convertps [-a] [-f] [-i ExportDir] [-o ImportDir]

    Table 7-6 describes the options available for the convertps command. This two-column table lists the options in the first column and their descriptions in the second column.

    Table 7-6  Options Available for Converting Gateway Data and Gateway Certificates  

    Option

    Description

    -a

    Runs all modules without a menu. If you do not use the -a option, the tool will display a convert menu listing the convertible types of data.

    To choose to convert only gateway data and gateway certificates from the conversion menu, do not use the -a option.

    -f

    Converts Sun ONE Portal Server 3.0 roles to Sun ONE Identity Server roles and places users under the organization. This option retains the multiple role to user assignment similar to Sun ONE Portal Server 3.0, but does not retain the hierarchical role functionality. All roles are created under the organization and are not prioritized. The display profile documents are prioritized and merged accordingly. To see if the roles have been migrated to roles, view the roles under the organization in the admin console.

    If you do not use the -f option, the conversion tool converts Sun ONE Portal Server 3.0 roles to Sun ONE Identity Server suborganizations and places users under the suborganization. Without the -f option, the conversion tool retains the hierarchical functionality and customizations from Sun ONE Portal Server 3.0. The disadvantage is that it is difficult to move users from one suborganization to another. To see if the roles have been migrated to suborganizations, view the hierarchy in the admin console.

    The Sun ONE Portal Server, Secure Remote Access 6.2 migration tools do not support flat role migration. If you do not use this option when migrating SRA data, you should also not use the -f option when migrating Desktop data also.

    -i ExportDir

    Specifies the input directory for the conversion. The input directory is the directory which contains the exported data created by the export tool. The conversion tool searches for export data in /tmp/psExport unless you specify a different input directory using the -i ExportDir option.

    If you specify a directory which does not contain data exported with the export tool, the conversion tool notifies you that the directory does not have export data and prompts you to enter a valid export directory.

    -o ImportDir

    Specifies the output directory for the conversion tool. The output directory is the directory used by the import tool.

    If you choose an import directory which already contains converted data, the conversion tool notifies you that modifying an existing migration may render import data unusable and prompts you to delete the import directory.

  7. The system displays the following messages:

    8. Found Portal Server version 6.2

    Enter Identity Server Internal LDAP Authentication User password:

    Type in a valid password.

    Which directory should be created to store the converted data? [/tmp/psImport]

    You see this prompt only if you do not specify the output directory using the -o ImportDir option. You can choose the default directory or enter another import directory.

    Import directory /tmp/psImport already exists.

    If you do not wish to overwrite data within this directory, please exit this migration process and rename the directory.

    Delete the directory /tmp/psImport?

    You see the message about an existing import directory only if the import directory already contains converted data. If you have already converted the gateway data and gateway certificates, you should exit this migration process by pressing Ctrl-C and rename the directory before converting the data.

  8. After you choose the output directory, you see output similar to the following:

    9. Begin conversion process at Tue Sep 17 15:41:55 SGT 2003

    Error file: /tmp/psImport/logs/error.27888

    Report file: /tmp/psImport/logs/report.27888

    Metric file: /tmp/psImport/logs/convert_metrics.27888

    Conversion Menu

    1) LDAP Database

    2) SRA Components Desktop

    3) Gateway Rules to Rewriter Rules

    4) Desktop

    5) Certificate Databases

    6) SRA Migration

    7) All of the above

    8) Exit

    Select one of the listed options to convert:

    You see the conversion menu only if you do not specify the -a option.

  9. Type 2 and press Enter to convert only secure remote access components.

    10. The system displays messages similar to the following:

    *** Extracting templates ***

    *****

    10.Begin SRA conversion process at Tue Sep 17 15:42:55 SGT 2003

    *** Creating SRA display profile ***

    Converting channel display profile.

    Converting domain desktop preferences.

    Converting role desktop preferences.

    Converting user desktop preferences.

    End SRA conversion process at Tue Sep 17 15:43:05 SGT 2003

    Successful completion of conversion process at Mon Sep 9 12:20:01 PDT 2003

  10. Change to the import directory making sure to substitute the import directory that you selected in Step 7. For example:

    11. cd ImportDir

    Substitute the import directory for ImportDir. If you used the default import directory, for example, use /tmp/psImport.

  11. Type ls to see the directories created by the conversion tool.

    12. Table 7-7 shows the directories created by the conversion tool when migrating the gateway. This two-column table lists the directories in the first column and their descriptions in the second column.

    Table 7-7  Directories Created by the Conversion Tool When Converting Gateway Data

    Directory

    Description

    ImportDir/logs

    Contains error.PID, export_metrics.PID, and report.PID files (where PID is the process ID)

    ImportDir/srap

    Contains subdirectories for gateway-related desktop data such as gateway certificates, Netlet, NetFile's user, role, and organization attributes, and desktop display profile XML files.

    After the conversion has completed, or if you run into problems, check the ImportDir/logs directory for the report.PID, error.PID, and convert_metrics.PID files (where PID is the process ID). The report.PID file contains actions the conversion tool has or has not taken and also alerts you to any customizations which you need to convert manually. The error.PID file contains warnings or errors so that you can correct any problems. The convert_metrics.PID file contains metrics detailing when various elements of the conversion tool started, stopped, and the total time it took to convert the data. You can look at the stdout header to know which log and report files to examine for the convertps command you are running.

If you run the convertps tool again in order to convert data other than certificate databases, the tool will prompt you to delete the import directory. Type no if you wish to keep the certificate databases you have already converted.

To Run the Conversion Tool to Convert Display Profile Data

  1. On the Sun ONE Portal Server 6.2 system, change to the migration tool directory:

    2. cd BaseDir/SUNWps/migration/bin

  2. Run the convertps command:

    3. ./convertps [-a] [-f] [-i ExportDir] [-o ImportDir]

  3. The system displays the following messages:

    4. Found Portal Server version 6.2

    Enter Identity Server Internal LDAP Authentication User password:

    Type in a valid password.

    Which directory should be created to store the converted data? [/tmp/psImport]

    You see this prompt only if you do not specify the output directory using the -o ImportDir option. You can choose the default directory or enter another import directory.

    Import directory /tmp/psImport already exists.

    If you do not wish to overwrite data within this directory, please exit this migration process and rename the directory.

    Delete the directory /tmp/psImport?

    Do not delete the directory.

  4. After you choose the output directory, you see output similar to the following:

    5. Begin conversion process at Mon Sep 9 12:16:38 PDT 2003

    Error file: /tmp/psImport/logs/error.19178

    Report file: /tmp/psImport/logs/report.19178

    Metric file: /tmp/psImport/logs/convert_metrics.19178

    Conversion Menu

    1) LDAP Database

    2) SRA Components Desktop

    3) Gateway Rules to Rewriter Rules

    4) Desktop

    5) Certificate Databases

    6) SRA Migration

    7) All of the above

    8) Exit

    Select one of the listed options to convert:

    You see the conversion menu only if you do not specify the -a option.

  5. Type 6 and press Enter to perform only NetFile, Netlet, and gateway conversion. The system displays messages similar to the following:

    6. *** Extracting templates ***

    10.Begin SRA conversion process at Tue Sep 17 15:45:05 SGT 2003

    Migrating SrapAttrs

    Outputfile : /tmp/psImport/srap/gateway/ldif/user.ldif Inputfile : /tmp/psExport/ldif/user.ldifdoConvert : 7

    Converting LDIF entries corr. to users from file:/tmp/psExport/ldif/user.ldif.....

    Processing dn : uid=authentication,ou=People,o=AdminRole,o=siroe.com,o=isp , org - ,o=AdminRole,o=siroe.com,o=isp

    Processing dn : uid=gateway-jughead.siroe.com,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=gateway-default,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=gateway-archie.siroe.com,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    /etc/opt/SUNWips/platform.conf (No such file or directory)

    Processing dn : uid=root,ou=People,o=AdminRole,o=siroe.com,o=isp , org - ,o=AdminRole,o=siroe.com,o=isp

    Processing dn : uid=vicky,ou=People,o=AdminRole,o=siroe.com,o=isp , org - ,o=AdminRole,o=siroe.com,o=isp

    Processing dn : uid=netfileuser1,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netfileuser2,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netfileuser3,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netfileuser4,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netletuser1,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netletuser2,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netletuser3,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netletuser4,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processing dn : uid=netletuser,ou=People,o=defaultRole,o=siroe.com,o=isp , org - ,o=defaultRole,o=siroe.com,o=isp

    Processed 15 entries

    Output available in file /tmp/psImport/srap/gateway/ldif/user.ldif

    Converting gateway data

    Converting LDIF entries corr. to users from file:/tmp/psExport/ldif/domain.ldif.....

    Output available in file /tmp/psImport/srap/gateway/xml/GatewayOrgAttrs.xml

    Converting LDIF entries corr. to users from file:/tmp/psExport/ldif/role.ldif.....

    Output available in file /tmp/psImport/srap/gateway/xml/GatewayRoleAttrs.xml

      End gateway conversion process at Tue Sep 17 15:45:18 SGT 2003

    Converting netlet data

    Converting LDIF entries corr. to users from file:/tmp/psExport/ldif/domain.ldif.....

    Output available in file /tmp/psImport/srap/netlet/xml/NetletOrgAttrs.xml

    Converting LDIF entries corr. to users from file:/tmp/psExport/ldif/role.ldif.....

    Output available in file /tmp/psImport/srap/netlet/xml/NetletRoleAttrs.xml

    End netlet conversion process at Tue Sep 17 15:45:19 SGT 2003

    Converting netfile data

    Converting LDIF entries corr. to users from file:/tmp/psExport/ldif/domain.ldif.....

    Output available in file /tmp/psImport/srap/netfile/xml/NetfileOrgAttrs.xml

    Converting LDIF entries corr. to users from file:/tmp/psExport/ldif/role.ldif.....

    Output available in file /tmp/psImport/srap/netfile/xml/NetfileRoleAttrs.xml

    End netfile conversion process at Tue Sep 17 15:45:20 SGT 2003

    Certificates copied

    Successful completion of conversion process at Tue Sep 17 15:45:21 SGT 2003

  6. Change to the import directory making sure to substitute the import directory that you selected in Step 7. For example:

    7. cd ImportDir

    Substitute the import directory for ImportDir. If you used the default import directory, for example, use /tmp/psImport.

  7. Type ls to see the directories created by the conversion tool.

    8. Table 7-8 shows the directories created by the conversion tool when converting gateway data, including NetFile, and Netlet. This two-column table lists the directories in the first column and their descriptions in the second column.

    Table 7-8  Directories Created by the Conversion Tool When Converting Gateway Data

    Directory

    Description

    ImportDir/logs

    Contains error.PID, export_metrics.PID, and report.PID files (where PID is the process ID)

    ImportDir/srap

    Contains subdirectories for gateway-related desktop data such as gateway certificates, Netlet, NetFile's user, role, and organization attributes and desktop display profile XML files.

After the conversion has completed, or if you run into problems, check the ImportDir/logs directory for the report.PID, error.PID, and convert_metrics.PID files (where PID is the process ID). The report.PID file contains actions the conversion tool has or has not taken and also alerts you to any customizations which you need to convert manually. The error.PID file contains warnings or errors so that you can correct any problems. The convert_metrics.PID file contains metrics detailing when various elements of the conversion tool started, stopped, and the total time it took to convert the data. You can look at the stdout header to know which log and report files to examine for the convertps command you are running.

To Run the Import Tool

  1. On the Sun ONE Portal Server 6.2 system, change to the import tool directory. For example:

    2. cd BaseDir/SUNWps/migration/bin

  2. Run the importps command:

    3. ./importps [-a] [-k] [-m] [ImportDir]

    Table 7-9 describes the options available for importing secure remote access data. This two-column table lists the options in the first column and their descriptions in the second column.

    Table 7-9  Options Available for Importing Secure Remote Access Data 

    Option

    Description

    -a

    Runs all modules without a menu. If you do not use the -a option, the tool will display an import menu listing the importable types of data.

    To choose to import only the secure remote access data from the import menu, do not use the -a option.

    -k

    Specifies that the tool does not overwrite existing users.

    When you run importps without the -k option, if it encounters a conflict with an existing user, it will delete the existing user and import the new user entry defined in ImportDir/ldap/user.ldif.

    If you run importps -k, if it encounters a conflict with an existing user, it leaves the existing user and places the rejected user entry in ImportDir/ldap/rejected_users.ldif.

    If the user has a display profile document in the ImportDir/dp/user/ directory, the display profile file may change. The -k option does not affect importing user display profile documents. The -k option only affects whether an existing LDAP user’s LDIF record is updated. The updates to the LDIF record include everything except display profile updates.

    -m

    Merges display profile documents.

    When you run importps without the -m option, it overwrites any existing display profile documents it finds. This means that the root suffix, organization, suborganization, and user level display profile documents, if they exist, are overwritten.

    If you run importps -m, when the tool encounters a conflict with an existing display profile document it will merge it.

    ImportDir

    Specifies the directory where the converted data is located. If the directory does not exist or if the directory does not contain valid converted data, the import tool prompts you to enter a directory containing the converted data to be imported. If you do not specify an import directory, the import tool will search /tmp/psImport.

  3. The system displays a message similar to the following:

    4. Found Portal Server version 6.2

    Enter Identity Server Internal LDAP Authentication User password:

    Type in a valid password.

    Enter Appserver Administrator password.

    You see this prompt only if you are migrating onto a Sun ONE Application Server web container.

    Begin import process at Tue Sep 17 16:03:22 SGT 2003

    Error file: /tmp/psImport/logs/importerror.3127

    Report file: /tmp/psImport/logs/importreport.3127

    Metric file: /tmp/psImport/logs/import_metrics.3127

    Import Menu:

    1) LDAP Database

    2) SRA Components Desktop

    3) Rewriter Rules

    4) Desktop

    5) Certificate Databases

    6) SRA Migration

    7) All of the above

    8) Exit

    Select one of the listed options to import:

    You see the import menu only if you do not specify the -a option.

  4. Type 2 and press Enter to import only the secure remote access components Desktop.

    5. Note

    Do not select option 2 before option 1. If you have not yet migrated LDAP data, follow the instructions in Chapter 2, "Migrating LDAP Data" before selecting option 2 to import SRA Components Desktop

    The system displays messages similar to the following:

    Importing dp xml

    Adding Netlet provider.

    ERROR: Duplicate name found. Use a different name.

    [DEBUG] Line 1: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w hanates

    t -d o=siroe.com,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.

    xml

    SUCCESS!

    [DEBUG] Line 3: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=siroe.com,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 5: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=dog,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 7: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=NetFile-Java2dom,o=isp -m /tmp/psImport/srap/destop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 9: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=nfj1,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 11: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=nfj11,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 13: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=vrush,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 15: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=netlet,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 17: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=murali,o=isp -m /tmp/psImport/srap/desktop/dp/initialOrganization.xml

    SUCCESS!

    [DEBUG] Line 19: modify -u uid=amAdmin,ou=People,o=siroe.com,o=isp -w passphrase -d o=siroe.com,o=isp -m /tmp/psImport/srap/desktopdp/tab/siroe.com/modify/NewsTemplatePanelContainer.xml

    SUCCESS!

    Redeploying portal web application

    /opt/SUNWam/servers/https-admserv /opt/SUNWam/servers/https-host1.siroe.com

    Deploying to instance host1.siroe.com...

    Successful completion of import process at Mon Sep 17 16:05:22 SGT 2003

After the import has completed, or if you run into problems, check the ImportDir/logs directory for the importreport.PID, importerror.PID, and import_metrics.PID files (where PID is the process ID). The importreport.PID file contains actions the import tool has or has not taken and also alerts you to any customizations which you need to import manually. The importerror.PID file contains warnings or errors so that you can correct any problems. The import_metrics.PID file contains metrics detailing when various elements of the import tool started, stopped, and the total time it took to import the data. You can look at the stdout header to know which log and report files to examine for the importps command you are running.

To Run the Import Tool to Import Display Profile Data

  1. On the Sun ONE Portal Server 6.2 system, change to the import tool directory. For example:

    2. cd BaseDir/SUNWps/migration/bin

  2. Run the importps command:

    3. ./importps [-a] [-k] [-m] [ImportDir]

    Table 7-10 describes the options available for importing secure remote access data. This two-column table lists the options in the first column and their descriptions in the second column.

    Table 7-10  Options Available for Importing Secure Remote Access Data 

    Option

    Description

    -a

    Runs all modules without a menu.

    To choose to import only the secure remote access data from the import menu, do not use the -a option.

    -k

    Specifies that the tool does not overwrite existing users.

    When you run importps without the -k option, if it encounters a conflict with an existing user, it will delete the existing user and import the new user entry defined in ImportDir/ldap/user.ldif.

    If you run importps -k, if it encounters a conflict with an existing user, it leaves the existing user and places the rejected user entry in ImportDir/ldap/rejected_users.ldif.

    If the user has a display profile document in the ImportDir/dp/user/ directory, the display profile file may change. The -k option does not affect importing user display profile documents. The -k option only affects whether an existing LDAP user’s LDIF record is updated. The updates to the LDIF record include everything except display profile updates.

    -m

    Merges display profile documents.

    When you run importps without the -m option, it overwrites any existing display profile documents it finds. This means that the root suffix, organization, suborganization, and user level display profile documents, if they exist, are overwritten.

    If you run importps -m, when the tool encounters a conflict with an existing display profile document it will merge it.

    ImportDir

    Specifies the directory where the converted data is located. If the directory does not exist or if the directory does not contain valid converted data, the import tool prompts you to enter a directory containing the converted data to be imported. If you do not specify an import directory, the import tool will search /tmp/psImport.

  3. The system displays messages similar to the following:

    4. Found Portal Server version 6.2

    Enter Identity Server Internal LDAP Authentication User password:

    Type in a valid password.

    Enter Appserver Administrator password.

    You see this prompt only if you are migrating onto a Sun ONE Application Server web container.

    Begin import process at Thu Sep 19 13:08:09 IDT 2003

    Error file: /tmp/psImport/logs/importerror.19657

    Report file: /tmp/psImport/logs/importreport.19657

    Metric file: /tmp/psImport/logs/import_metrics.19657

    Import Menu:

    1) LDAP Database

    2) SRA Components Desktop

    3) Rewriter Rules

    4) Desktop

    5) Certificate Databases

    6) SRA Migration

    7) All of the above

    8) Exit

    Select one of the listed options to import:

    You see the import menu only if you do not specify the -a option.

  4. Type 6 and press Enter to import only the secure remote access data.

    5. The system displays messages similar to the following:

    Success 0: Successfully completed.

    Success 0: Successfully completed.

    Lowering the priorities of the assigned Netlet policies.

    Netlet data migrated.

    Success 0: Successfully completed.

    Error 10: Cannot process requests: null

    Lowering the priorities of the assigned Netfile policies.

    Adding netfile channel to desktop.

    Success 0: Successfully completed.

    Success 0: Successfully completed.

    Success 0: Successfully completed.

    Netfile data migrated.

    Adding srapGatewayAccessService to required services list.

    Info 112: Entering ldapAuthenticate method!

    Success 0: No Exceptions! LDAP Authentication success!

    Info 113: Calling SSO method!

    Info 107: Calling XML PARSER

    Info 108: XML file to parse:/var/opt/SUNWps/tmp/migSUNWpsgws_requests.xml

    Info 101: Processing /var/opt/SUNWps/tmp/migSUNWpsgws_requests.xml

    Info 111: Requests generated by amadmin

    Info 102: Done processing /var/opt/SUNWps/tmp/migSUNWpsgws_requests.xml

    Success 0: Successfully completed.

    Importing gateway data.

    modifying entry uid=authentication,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=authentication,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=gateway-host1.siroe.com,ou=People,o=defaultRole,o=siroe.com,o=isp

    modifying entry uid=gateway-host1.siroe.com,ou=People,o=defaultRole,o=siroe.com,o=isp

    modifying entry uid=gateway-default,ou=People,o=defaultRole,o=siroe.com,o=isp

    modifying entry uid=gateway-default,ou=People,o=defaultRole,o=siroe.com,o=isp

    modifying entry uid=gateway-host1.siroe.com,ou=People,o=defaultRole,o=siroe.com,o=isp

    modifying entry uid=gateway-host1.siroe.com,ou=People,o=defaultRole,o=siroe.com,o=isp

    modifying entry uid=root,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=root,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=root,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=root,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=vicky,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=vicky,ou=People,o=AdminRole,o=siroe.com,o=isp

    modifying entry uid=netfileuser1,ou=People,o=defaultRole,o=siroe.com,o=isp

    Success 0: Successfully completed.

    Error 10: Cannot process requests: null

    Success 0: Successfully completed.

    Gateway data migrated.

    Redeploying portal web application

    /opt/SUNWam/servers/https-admserv /opt/SUNWam/servers/https-host1.siroe.com

    Deploying to instance host1.siroe.com...

    Successful completion of import process at Thu Sep 19 18:41:47 IST 2003

After the import has completed, or if you run into problems, check the ImportDir/logs directory for the importreport.PID, importerror.PID, and import_metrics.PID files (where PID is the process ID). The importreport.PID file contains actions the import tool has or has not taken and also alerts you to any customizations which you need to import manually. The importerror.PID file contains warnings or errors so that you can correct any problems. The import_metrics.PID file contains metrics detailing when various elements of the import tool started, stopped, and the total time it took to import the data. You can look at the stdout header to know which log and report files to examine for the importps command you are running.

Verifying the Migration

After the gateway migration is complete, verify that

Troubleshooting

Deleting Extra NetFile Links from the Desktop

After migration, there will be two sets of entries in the applications channel. They are the old Desktop migrated entries for NetFile lite and NetFile which you must remove because they point to non-existent URLs. There are also links to NetFile Java1 and NetFile Java2 which are not selected by default.

Delete the two NetFile links that appear on the Desktop after migration. Use the following URLs to access NetFile Java1 and NetFile Java2:

For NetFile Java1:

https://gateway_machine:port/http://server:port/portal/
NetFileApplet?Refer=java1

For NetFile Java2:

https://gateway_machine:port/http://server:port/portal/
NetFileApplet?Refer=java2

Adding the MIME Type Entries to the web.xml File

The data migration process removes the MIME type entries from the web.xml file. To restore Netlet and NetFile functionality after the data migration, the Mime type entries need to be added to the web.xml file in the web container directory, for example, websphere-install-dir/WebSphere/AppServer/installedApps/portal.ear/
portal.war/WEB-INF/web.xml.

  1. Add the following lines after the session-config tag in the web.xml file:

    2. <mime-mapping>

      <extension>jar</extension>

      <mime-type>application/octet-stream</mime-type>

    </mime-mapping>

    <mime-mapping>

      <extension>cab</extension>

      <mime-type>application/octet-stream</mime-type>

    </mime-mapping>

  2. Restart the Sun ONE Portal Server and the gateway.



Previous      Contents      Index      Next     

Copyright 2004 Sun Microsystems, Inc. All rights reserved.