Sun ONE logo     Previous      Contents      Index      Next     

Sun logo
IS B2B: ECXpert and TradingXpert 3.6.3 Installation Guide 

Appendix A
Upgrading to ECXpert 3.6.3

This appendix describes the planning and tasks you must perform to upgrade from ECXpert Version 3.6.2 to ECXpert 3.6.3. It includes instructions for both the Solaris™ and the Windows platforms.

Upgrading on Solaris

Complete the tasks described in this section to upgrade ECXpert on the Solaris platform.

Shut Down ECXpert Services

If you are using a previous installation of the ECXpert Product Administrative Interface, you must log out and shut it down. Follow these steps to log out and shut down ECXpert.

  1. Log out of the ECXpert Support Interface.

    2. Click the Logout bar, then choose Applet > Quit if using the Applet Viewer.

  2. Shut down all ECXpert services.

    3. Display the ECXpert Main Menu in your browser by entering the URL:

    http://hostname:port#

    where hostname is the name of your ECXpert host and port# is the port number it uses.

  3. Click the Admin button to display the ECXpert Server Administration menu.

    4. If any ECXpert services are running, you will see more entries than the ECXpert Administration Server with an ON indication.

  4. Click the switch for the ECXpert Administration Server to OFF. This turns off all currently running servers.
  5. Click the Update Screen button and wait until the screen is refreshed. When all servers are shown to be OFF, you can proceed.
  6. Shut down your web server.

    7. In a terminal window, enter the following commands, replacing machine_name with the name of your ECXpert host machine:

    # cd WebServer_Install_Dir /https_machine_name

    # ./stop

  7. Verify that no ECXpert processes are still running.

    8. In a terminal window, enter the following command:

    # ps -ef | grep NS_apps

    If other processes are running, kill them manually.

  8. If running SNMP, make sure the SNMP agent is shut down.

    9. Manually kill the process ID for Program.o.

Database Migration

Complete the tasks described in this section to migrate to Oracle 9i. This involves

Upgrading to Oracle 9i

If you have not already done so, you need to upgrade to Oracle 9i, Enterprise Edition. See Preinstallation Tasks for instructions on installing Oracle or contact your Oracle service provider or database administrator for assistance.

Note

When you upgrade Oracle, do not create a new Oracle user to own the ECXpert tables. You must use the existing Oracle user who owns the ECXpert tables.

Set up and Test Your Database Connectivity 

Set up and test your database to be sure that user root has access to the database, so you can successfully migrate ECXpert. If user root doesn’t have access to the database, you will get error messages during the ECXpert migration process.

  1. Log in as user root.

    2. # su - root

  2. Determine the shell that root uses.

    3. # echo $SHELL

    The output of this command identifies the shell that root uses, which determines its associated environment file:

    Output

    Shell Being Used

    Environment File

    /sbin/sh

    Bourne

    .profile

    /sbin/csh

    C

    .cshrc

    /sbin/ksh

    Korn

    .profile or .kshrc

  3. Determine the shell that oracle uses.

    4. # cat /etc/passwd | grep oracle

    The output of this command lists the shell at the end, as in the sample below:

    oracle:x:50004:10003::/export/home/oracle:/bin/csh

    where the shell is csh.

  4. Get into the oracle shell.

    5. Locate the shell in the “Output” column of the table in Step 2 above, then look up the entry in the “Environment File” column for the same row.

    1. If you are using the C shell, enter the following command:

      2.   # source ~oracle/.cshrc

      where oracle is your Oracle user, typically oracle.

    2. If you are using the Korn shell or the Bourne shell, enter the following command:

      3.   # . ~oracle/your_environment_file

      where oracle is your Oracle user, and your_environment_file is the name of your environment file.

  5. Check the environment settings.

    6. # env

    The following sample output of this command lists the environment variables that must be set:

    $ORACLE_HOME=$ORACLE_HOME from worksheet
    $ORACLE_SID=myHost
    $NLS_LANG=$NLS_LANG from worksheet
    $LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
    $PATH=$ORACLE_HOME/bin:$ORACLE_HOME:$PATH
    $DISPLAY=hostname:0.0
    $TNS_ADMIN=$ORACLE_HOME/network/admin

  6. Correct environment variable definitions as necessary.

    7. If any of the above environment variables are not properly defined, do the following:

    1. Log in as or change to your Oracle user, typically oracle. For example:

      2. # su - oracle.

    2. Open the environment file that you referenced in Step 4 above in a text editor and add or modify the definitions as necessary.
    3. Save the environment file and exit the text editor.
  7. Enable changes in environment variable definitions.

    8. If you made changes in the environment file in Step 2 above, you can enable those changes now by switching to another user and then switching back to your Oracle user. For example:

    # su - root

    # su - oracle

    Alternatively, you could restart your system and log in as your Oracle user.

  8. Check your tnsnames.ora file.

    9. Check your tnsnames.ora file to make sure it contains the correct information. The following are likely locations of your tnsnames.ora file:

    • ORACLE_HOME/network/admin
    • /var/opt/oracle
    • the directory specified by the TNS_ADMIN environment variable
  9. Connect to the database from the UNIX command line:

    10. # sqlplus ECX36/ECX36@your_connect_string

    where ECX/ECX is the username/password of the ECXpert table-owner. If this test fails, skip to Step 7.

  10. Repeat the test from inside SQL*Plus:

    11. SQL> connect ECX36/ECX36@your_connect_string

    SQL> exit

    where ECX36/ECX36 is the username/password of the ECXpert table-owner.

  11. Correct any connectivity problems.

    12. If the test at either Step 5 or Step 6 failed, check the tnsnames.ora and listener.ora file to validate the settings, such as hostname and SID.

    After making any necessary changes, go back to Step 5 above.

    If you have successfully connected to the database using SQL*Plus, you will be able to connect during the ECXpert migration. If you cannot connect to the database using this method, you definitely will not be able to connect during the ECXpert migration.

Back Up Your Database

The database backup is a major operation. You should plan carefully for both the disk space that will be required and the time slot in which the backup is executed.

The backup will require as much disk space as the current database and the rollback tablespace in Oracle must be set to as much as 1.5 times the tablespace setting.

The backup process can take 12 hours or more for a large database. Without proper planning, the process may abort part-way through. Refer to your Oracle documentation for further guidelines and recommendations.

Follow the steps in this section to back up your existing ECXpert database.

  1. Change to the BDGHOME/dbadmin/oracle directory.
  2. Open the exp_ecx_tables.sh file in a text editor.
  3. Change the character string name/password@dbAlias in the first line to be the username/password@dbAlias of your ECXpert table-owner user.
  4. Enter the following command to run exp_ecx_tables.sh.

    5. # ./exp_ecx_tables.sh

    If this command is successful, you should see output similar to the following, depending upon your currently installed version of Oracle with the ECXpert database:

    Export done in US7ASCII character set and US7ASCII NCHAR character set

    About to export specified tables via Conventional Path ...

    . . exporting table MEMBERS 10 rows exported

    . . exporting table MBADDRESSES 15 rows exported

    . . exporting table PARTNERSHIPS 3 rows exported

    . . exporting table PNSTD 3 rows exported

    . . exporting table PNGROUP 3 rows exported

    . . exporting table KEYPAIRS 8 rows exported

    . . exporting table CERTIFICATES 8 rows exported

    . . exporting table TRACKING 1 rows exported

    . . exporting table TRKINTCHG 0 rows exported

    . . exporting table SERVICES 7 rows exported

    . . exporting table MSGFORMATS 678 rows exported

    . . exporting table EVENTLOG 0 rows exported

    . . exporting table UNIQUEKEYS 19 rows exported

    . . exporting table DTSERVICES 7 rows exported

    . . exporting table SCHEDULEINFO 0 rows exported

    . . exporting table TRKGROUP 0 rows exported

    . . exporting table TRKDOC 0 rows exported

    . . exporting table PNDOCS 3 rows exported

    . . exporting table TRKDOCDETAILS 0 rows exported

    . . exporting table CRL 0 rows exported

    . . exporting table PNCARD 0 rows exported

    . . exporting table MDNINFO 0 rows exported

    . . exporting table BLOBINFO 8 rows exported

    . . exporting table CERTTYPEINFO 5 rows exported

    Export terminated successfully without warnings.

    #

    If instead you get the following error message:

    ./exp_ecx_tables.sh: Permission denied

    enter the following command to set the proper permissions on the file:

    # chmod 775 exp_ecx_tables.sh

    and repeat this step.

Back Up LDAP Data

If your site uses an LDAP directory server to store ECXpert data you will need to back up this data, in addition to backing up your Oracle data.

Refer to Chapter 4 of the iPlanet Directory Server Administrator’s Guide for information on backing up and restoring data.

Back Up ECX Files

Follow the steps in this section to back up the important files from your current ECXpert installation:

  1. Set up a temporary holding directory that is:
    • outside both the current ECXpert version and any previous ECXpert Version directory trees.
    • outside the /tmp directory
  2. Copy the following files into your temporary holding directory:
    • In all cases, from BDGHOME/config, copy the file ecx.ini.
    • If using SNMP, copy the BDGHOME/SNMP/config/CONFIG file.
    • Copy your maps and extra input card files from:
      - BDGHOME/maps/
      - BDGHOME/data/input/
    • Copy your live data—the following complete directories:
      - BDGHOME/data/work/trk
      - BDGHOME/data/output
      - BDGHOME/data/bundle
      - BDGHOME/smtp/inbound
      - BDGHOME/smtp/outbound

Upgrade to Current ECXpert

    To upgrade to current ECXpert on Solaris
  1. Begin to install the current ECXpert version, as described in Chapter 3, "Installing ECXpert and TradingXpert".
  2. Proceed normally through the screens for the Installer up to and including Step 10.

    3. Be sure to stop at Step 12. Do not execute Step 12.

  3. Uncheck the Drop Tables and Create New checkbox and click Next on Step 12 of the browser-based installation.
  4. Proceed normally through the screens for Installer Step 13 through the rest of the Installer, and complete the rest of the tasks in Chapter 3, "Installing ECXpert and TradingXpert."

    5. Be sure to follow instructions for updating the web server configuration files.

  5. To update the ECXpert tables, run the SQL migration scripts in the directory BDGHOME/dbadmin/oracle/migration/36.2_to_36.3

    6. Connect to your database from the UNIX command line:

    #su -oracle
    #sqlplus ECX36/ECX36@your_connect_string

    where ECX36/ECX36 is your ECXpert Oracle user name and password and your_connect_string is the string you use to connect to your database. Execute the following script from the command line:

    # start Root_ECX_Install/NS-apps/ECXpert/dbadmin/oracle/migration/36.2_to_36.3/ sql_script

    where sql_script is one of the migration scripts in the migration directory listed above.

  6. Restore configuration settings from the temporary holding directory for your previous installation.
    1. If using SNMP, copy the entire CONFIG file back to the new
      BDGHOME/SNMP/config/ directory.
    2. Open your previous version of the ecx.ini file and the newly installed ecx.ini in a text editor and manually update the newly installed file very carefully by copying the following items in from the old one:

      3. any [...] sections for user-defined comms in their entirety

      any other parameters, from any [...] sections, where the old settings differ from those in the newly installed file.

      Note

      Some parameter names have changed slightly in current ECXpert; the new names are similar enough that you should be able to recognize them easily from the old names; be sure to check for a name change and replace any old names with the new names in any parameters that you copy into your new ecx.ini file.

      Be aware of the following two restrictions as you edit the new ecx.ini file:

      • Never duplicate a section heading within the ecx.ini file.
      • Never duplicate a parameter assignment within a section.

Remove Saved Files

If you have followed the recommendation to move the earlier ECXpert install directory to a temporary location, leave the archival copy of the previous installation and the Oracle database backup in place until you are certain that the new installation of current ECXpert is working properly.

When the new version of ECXpert has been in production mode for a week or more, you may safely delete the previous installation and the Oracle database backup.

Upgrading on Windows

Complete the tasks described in this section to upgrade your ECXpert installation on Windows.

Shut Down ECXpert Services

If you are using a previous installation of the ECXpert Product Administrative Interface, you must log out and shut it down.

    To log out and shut down ECXpert
  1. To log out of the ECXpert Product Administrative Interface, click the Logout bar, then choose Applet > Quit if using the Applet Viewer.
  2. To shut down all ECXpert services, display the ECXpert Main Menu in your browser by entering the URL:

    3. hostname:port_number

    where hostname is the name of your ECXpert host and port_name is the port number it uses.

  3. Click the Admin button to display the ECXpert Server Administration menu.

    4. The state of each service is indicated by the switch icon to the left of the service name. Services that are currently running have the switch set to ON, and those that are not running are set to OFF.

  4. Click the switch for the ECXpert Administration Server to OFF. This turns off all currently running servers.
  5. Click the Update Screen button and wait until the screen is refreshed. When all servers are shown to be OFF, you can proceed.
  6. Shut down the Sun™ ONE Web Server:

    7. In a command shell window, enter the following commands, replacing machine_name with the name of your ECXpert host machine and Root_ECX_Install with the name of the directory where you installed ECXpert.

    C:\> cd Root_ECX_Install\NS-apps\ns-home\http_prefix-machine_name
    C:\> ./stop-admin

    In the above cd command, supply a value for http_prefix as follows:

    • httpd for an unsecured Netscape FastTrack Server
    • https for a secured Netscape FastTrack Server or Sun ONE Enterprise Server
  7. Shut down the Sun ONE Administration server.

    8. In a terminal window, enter the following commands:

    C:\> cd Root_ECX_Install\NS-apps\ns-home\
    C:\> ./stop-admin

  8. Verify that no ECXpert processes are still running.

    9. Right-click the Windows NT task bar, and select the Task Manager. Select the Processes tab. Scan the list of processes. If there are any ECXpert processes currently executing, click them one by one, and for each one click the End Process button.

  9. If you are running SNMP, make sure the SNMP agent is shut down.

    10. In the Task Manager Processes tab, scan the list for a process called Program.o. If such a process is currently executing, highlight it and click the End Process button.

Database Upgrade

Complete the tasks described in this section to upgrade to Oracle 9i. This involves the following:

Upgrade to Oracle 9i

If you have not already done so, you need to upgrade to 9i, Enterprise Edition. See Preinstallation Tasks for instructions on installing Oracle or contact your Oracle service provider or dba for assistance.

Note

When you upgrade Oracle, do not create a new Oracle user to own the ECXpert tables. You must use the existing Oracle user who owns the ECXpert tables.

Set up and Test Your Database Connectivity

Set up and test your database to be sure that user root has access to the database, so you can successfully migrate ECXpert. If user root doesn’t have access to the database, the migration will fail.

    To set up and test your database connectivity
  1. Check the environment variable settings. The following table lists the environment variables that must be set. Check the Installation Worksheet, Table 2-8, for the correct values.

    2. Table A-1  Environment Variable Settings for Testing Database Connectivity 

    Variable

    Value

    ORACLE_HOME

    Use the value in your installation worksheet

    ORACLE_SID

    Use the value from your installation worksheet. For example, myHost

    NLS_LANG

    Use the value in your installation worksheet.

    PATH

    ORACLE_HOME\bin:ORACLE_HOME:PATH

    TNS_ADMIN

    ORACLE_HOME\network\admin

  2. Modify environment variable definitions as necessary.

    3. From the Windows NT task bar, select Start > Settings > Control Panel > System. In the System Properties window, select the Environment tab.

  3. Enter the variable name in the Variable entry field and the value in the Value entry field.

    4. For each Variable/Value pair, click Set to set the value. When you have made all your changes, click OK to save the changes.

  4. Check your tnsnames.ora file to make sure it contains the correct information.

    5. Likely locations for your tnsnames.ora file include:

    • ORACLE_HOME\network\admin
    • The directory specified by the TNS_ADMIN environment variable
  5. Connect to the database.

    6. In the Command window, navigate to your ORACLE directory, and enter:

    C:\> sqlplus ECX36/ECX36@your_connect_string

    where ECX36/ECX36 is the username/password of the ECXpert table-owner. If this test fails, skip to Step 7.

  6. Repeat the test from inside SQL*Plus:

    7. SQL> connect ECX36/ECX36@your_connect_string

    SQL> exit

    where ECX36/ECX36 is the username/password of the ECXpert table-owner.

  7. Correct any connectivity problems.

    8. If the test at either Step 5 or Step 6 failed, check the tnsnames.ora and listener.ora files to validate the settings, such as hostname and SID.

    After making any necessary changes, go back to Step 5 above.

    If you have successfully connected to the database using SQL*Plus, you will be able to connect during the ECXpert migration. If you cannot connect to the database using this method, you definitely will not be able to connect during the ECXpert migration.

Back Up Your Database

Database backup is a major operation, and should be delegated to your site’s Oracle database administrator. Plan carefully for the amount of disk space required to accommodate your data, and the amount of time the backup will take.

The backup will require as much disk space as the current database. The rollback double-space in Oracle must be set to as much as 1.5 times the tablespace setting.

The backup process can take 12 hours or more for a large database. Without proper planning, the process may abort part-way through. Refer to your Oracle documentation for further guidelines and recommendations.

    To back up your existing ECXpert database
  1. Go to the BDGHOME\dbadmin\oracle directory.
  2. Open the exp_ecx_tables.sh file in a text editor.
  3. Change the character string name/password@dbAlias in the first line to be the username/password@dbAlias of your ECXpert table-owner user.
  4. From the Windows NT Command window, enter the following command to run exp_ecx_tables.sh:

    5. C:\> ./exp_ecx_tables.sh

    If this command is successful, you should see output similar to the following example:

    Export: Release 8.0.4.0.0 - Production on Thu Mar 4 16:21:34 1999

    (c) Copyright 1997 Oracle Corporation. All rights reserved.

    Connected to: Oracle8 Release 8.0.4.0.0 - Production

    PL/SQL Release 8.0.4.0.0 - Production

    Export done in US7ASCII character set and US7ASCII NCHAR character set

    About to export specified tables via Conventional Path ...

    . . exporting table MEMBERS 10 rows exported

    . . exporting table MBADDRESSES 15 rows exported

    . . exporting table PARTNERSHIPS 3 rows exported

    . . exporting table PNSTD 3 rows exported

    . . exporting table PNGROUP 3 rows exported

    . . exporting table KEYPAIRS 8 rows exported

    . . exporting table CERTIFICATES 8 rows exported

    . . exporting table TRACKING 1 rows exported

    . . exporting table TRKINTCHG 0 rows exported

    . . exporting table SERVICES 7 rows exported

    . . exporting table MSGFORMATS 678 rows exported

    . . exporting table EVENTLOG 0 rows exported

    . . exporting table UNIQUEKEYS 19 rows exported

    . . exporting table DTSERVICES 7 rows exported

    . . exporting table SCHEDULEINFO 0 rows exported

    . . exporting table TRKGROUP 0 rows exported

    . . exporting table TRKDOC 0 rows exported

    . . exporting table PNDOCS 3 rows exported

    . . exporting table TRKDOCDETAILS 0 rows exported

    . . exporting table CRL 0 rows exported

    . . exporting table PNCARD 0 rows exported

    . . exporting table MDNINFO 0 rows exported

    . . exporting table BLOBINFO 8 rows exported

    . . exporting table CERTTYPEINFO 5 rows exported

    Export terminated successfully without warnings.

    #

Back Up LDAP Data

If your site uses an LDAP directory server to store ECXpert data you will need to back these data up, in addition to backing up your Oracle data.

Refer to Chapter 4 of the iPlanet Directory Server Administrator’s Guide for information on backing up and restoring data.

Back up ECX Files

Follow the steps in this section to back up the important files from your current ECXpert installation.

    To back up important files from your current ECXpert installation
  1. Set up a temporary holding directory that is:
    • outside both your current ECXpert directory tree, and any other ECXpert directory trees from previous releases
    • outside the system related directories.
  2. Copy the following files into your temporary holding directory.
    • Copy the the file ecx.ini.from the BDGHOME\config directory.
    • If using SNMP, copy the file

      • BDGHOME\config\CONFIG.

    • Copy your maps and extra input card files from:
      - BDGHOME\maps\
      - BDGHOME\data\input\
    • Copy your live data—the following complete directories:
      - BDGHOME\data\work\trk
      - BDGHOME\data\output
      - BDGHOME\data\bundle
      - BDGHOME\smtp\inbound
      - BDGHOME\smtp\outbound
  3. Proceed normally through the screens for the Installer up to and including Step 10.

    4. Be sure to stop at Step 12. Do not execute Step 12.

  4. Click Skip on Step 12 of the Installer.

Upgrade to Current ECXpert

    To upgrade to current ECXpert in Windows
  1. Install the current ECXpert version, as described in Chapter 3, "Installing ECXpert and TradingXpert" up to and including Step 10.

    2. Be sure to stop at Step 12. Do not execute Step 12.

  2. Uncheck the Drop Tables and Create New checkbox and click Next on Step 12 of the Installer
  3. Proceed normally through the screens for Installer Step 13 through the rest of the Installer, and complete the rest of the tasks in Chapter 3, "Installing ECXpert and TradingXpert."

    4. Be sure to follow instructions for updating the web server configuration files.

  4. Update the ECXpert tables.

    5. Execute the SQL migration scripts in the directory BDGHOME\dbadmin\oracle\migration\36.2_to_36.3 .

    Connect to your database from the Windows NT Command window:

    C:\> sqlplus ECX36/ECX36@your_connect_string

    where ECX36/ECX36 is the username/password of the ECXpert table-owner and your_connect_string is the string you use to connect to your database.

  5. Restore configuration settings from the temporary holding directory for your previous installation.
    1. If using SNMP, copy the entire CONFIG file back to the new BDGHOME\SNMP\config directory.
    2. Open your older version of the ecx.ini file and the newly installed ecx.ini in a text editor and manually update the newly installed file very carefully by copying the following items from the older version to the new one:
    3. any [...] sections for user-defined comms in their entirety
    4. any other parameters, from any [...] sections, where the old settings differ from those in the newly installed file.

      5. Note

      Some parameter names have changed slightly in current ECXpert; the new names are similar enough that you should be able to recognize them easily from the old names; be sure to check for a name change and replace any old names with the new names in any parameters that you copy into your new ecx.ini file.

      Be aware of the following two restrictions as you edit the new ecx.ini file:

      • Never duplicate a section heading within the ecx.ini file.
      • Never duplicate a parameter assignment within a section.

Remove Saved Files

If you have followed the recommendation to move the earlier ECXpert install directory to a temporary location, leave the archival copy of the previous installation and the Oracle database backup in place until you are certain that the new installation of ECXpert is working properly.

When you are satisfied that your new installation is fully operational, you may safely delete the previous installation and the Oracle database backup.



Previous      Contents      Index      Next     

Copyright 2004 Sun Microsystems, Inc. All rights reserved.