Sun ONE logo     Previous      Contents      Index      Next     
Sun ONE Integration Server B2B, ECXpert 3.6.2 Installation Guide



Appendix B   Reinstalling ECXpert

This appendix provides instructions on reinstalling ECXpert 3.6.2 over an existing installation of ECXpert 3.6.2. Instructions are provided for both the Solaris™ and Windows platforms.

Begin by reading the section "The Reinstallation Process" to become familiar with the basic process. Then continue by reading the section below that describes reinstallation on your platform.

The Reinstallation Process

Reinstalling ECXpert 3.6.2 is a non-trivial operation. You should read the entire section pertaining to your platform (Solaris or Windows) before attempting a reinstallation. You need to make sure you allocate sufficient disk space for the reinstallation, as well as enough time in which to perform the process.

You need to complete the following tasks to reinstall ECXpert:

  1. Shut down all ECXpert services.

  2. Check database connectivity.

  3. Backup your Oracle database.

  4. Preserve files from current installation.

  5. Reinstall ECXpert.

  6. Remove the previous installation and database backup.

Reinstalling on Solaris

Complete the tasks described in the following sections to reinstall ECXpert on Solaris.

Shut Down ECXpert Services

If you are using a previous installation of ECXpert, you must log out of the Product Administrative Interface (Support UI) and shut it down. Follow these steps to log out and shut down ECXpert. For figure references, see the screen shots in Appendix A.

  1. Log out of the ECXpert Product Administrative Interface.

    2. Click the Logout link, 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.

    Click the Admin link to display the ECXpert Server Administration menu.

  3. Click the switch for the ECXpert Administration Server to OFF. This turns off all currently running servers.

  4. Click the Update Screen button and wait until the screen is refreshed. When all servers are shown to be OFF, you can proceed.

  5. Shut down the Sun™ ONE Web Server by navigating to the server's home directory and issuing the stop command.

  6. Shut down the Sun ONE Administration server by navigating to the server's home directory and issuing the stop command.

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

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

Check Database Connectivity

  1. Check your tnsnames.ora file.

    2. 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

  2. Connect to the database from the UNIX command line.

    3. # 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 4.

  3. Repeat the test from inside SQL*Plus:

    4. SQL> connect ECX36/ECX36@your_connect_string

    SQL> exit

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

  4. Correct any connectivity problems.

    5. If the test at either Step 2 or Step 3 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 2 above.

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

Back Up Your Existing ECXpert 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.

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:

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

    Connected to: Oracle8i Release 8.1.6.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 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 ECXpert 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 directory tree and any previous ECXpert installation's directory tree.

    • outside the /tmp directory

  2. Copy the following files into your temporary holding directory:

    • In all cases, from RBDGHOME/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/
      - RBDGHOME/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

Reinstall ECXpert

At this point you are ready to begin reinstalling ECXpert.

  1. Begin to install the current ECXpert version, as described in Chapter 3, "Installing ECXpert on Solaris". The current version also includes the server install of Partner Agent.

    2. After the command-line-based installation completes, a browser appears with the browser-based installation steps.

  2. Proceed normally through the screens for Installer Step One to Step Five.

  3. Click Skip on Step Six of the browser-based installation.

  4. Click Skip on Step Seven of the browser-based installation.

  5. Proceed normally through the screens for Installer Step Eight to Step Ten and complete the rest of the tasks inChapter 3, "Installing ECXpert on Solaris".

    • If you reinstall ECXpert in the same location, you do not need to modify your web server configuration files.

    • If you reinstall ECXpert to a new location, you must modify your web server configuration files (as directed by the installer) to reflect your changes.

  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 RBDGHOME/SNMP/config/ directory.

    2. Open your old ecx.ini file and the newly installed ecx.ini in a text editor and manually update the newly installed file very carefully by copying 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.


      Caution

      Always work very carefully when manually editing your bdg.ini or ecx.ini file. Minor errors here can seriously impact system function and eat up valuable time in troubleshooting and correcting. In particular, be aware of the following two restrictions:

      • Never duplicate a section heading ([...]) within the ecx.ini file.

      • Never duplicate a parameter assignment within a section.

  7. Re-establish SunONE Web Server security.

  8. Restore live data from your full database backup.

Remove the Previous Installation and Database Backup

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 the current version of ECXpert has been in production mode for a week or so, you may safely delete the previous installation and the Oracle database backup.

Reinstalling on Windows

Complete the tasks in this section to reinstall ECXpert on Windows NT or Windows 2000.

Shut Down ECXpert Services

Make sure all users are logged off of ECXpert, and then shut it down. Follow these steps to log out and shut down. For figure references, see the screen shots in Appendix A, "Upgrading to ECXpert 3.6.2."

To log out and shut down all ECXpert services

  1. To log out of the ECXpert Product Administrative Interface, click the Logout link, 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_name

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

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

  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 by navigating to the server's home directory and issuing the stop command.

  7. Shut down the Sun ONE Administration server by navigating to the server's home directory and issuing the stop command.

  8. If running SNMP, make sure the SNMP agent is shut down. In the Windows NT task bar, right click and select Task Manager. In the Task Manager's Processes tab, scan the list of processes for Program.o. Highlight it, and click the End Process button.

Check Database Connectivity

This section tests to make sure that you have access to the database, so that you can successfully reinstall ECXpert. If you don't have access to the database, you will receive error messages during the ECXpert reinstallation process.

To check database connectivity

  1. 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

    • The directory specified by the TNS_ADMIN environment variable

  2. Connect to the database from the Windows NT Command window:

    3. 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 4.

  3. Repeat the test from inside SQL*Plus:

    4. SQL> connect ECX36/ECX36@your_connect_string
    SQL> exit

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

  4. Correct any connectivity problems.

    5. If the test at either Step 2 or Step 3 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 2 above.

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

Back Up Your Existing ECXpert Database

Database backup is a non-trivial operation. You need to make sure you allocated sufficient disk space for the backup, and you need to make sure you allot enough time in which to do the backup.

The backup will require as much disk space as the current database. 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.

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. In 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:

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

    Connected to: Oracle8i Release 8.1.6.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 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 ECXpert Files

To back up important files from your current ECXpert installation

  1. Set up a temporary holding directory that is:

    • outside both the current ECXpert directory tree and the directory tree of any previous ECXpert installation.

    • outside the \tmp directory

  2. Copy the following files into your temporary holding directory:

    • Copy the file ecx.ini from In all cases, BDGHOME\config.

    • If using SNMP, copy the BDGHOME\SNMP\config\CONFIG file.

    • Copy your maps and extra input card files from:
      -BDGHOME\maps
      - BDGHOME\datainput

    • Copy your live data—the following complete directories:
      - BDGHOME\data\work\trk
      - BDGHOME\data\output
      - BDGHOME\data\bundle
      - BDGHOME\smtp\inbound
      - BDGHOME\smtp\outbound

Reinstall ECXpert

At this point you are ready to begin reinstalling ECXpert.

The installer will look for the original magnus.conf and obj.conf files, to configure. So, unless you plan to change these files manually, make sure that the original, unmodified files are available.

To reinstall ECXpert

  1. Install the current ECXpert version, as described in "Installing ECXpert on Windows" up to Step 10.

  2. In Step 10, do NOT select the Create New Tables check box.

  3. Proceed normally through the rest of the installation procedure, starting with Step 11 and complete the rest of the tasks in "Installing ECXpert on Windows".

    • If you are reinstalling to the same location, you don't need to change your web server configuration files (magnus.conf and obj.conf).

    • Remember that if you do not let the installer change the web server configuration files and reinstall to a different location, you must edit the files as directed in "Configuring the Web Server" to reflect the changed location.

  4. 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 old ecx.ini file and the newly installed ecx.ini in a text editor and manually update the newly installed file very carefully by copying in from the old 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. Caution

      Always work very carefully when manually editing your bdg.ini or ecx.ini file. Minor errors can seriously impact system function. In particular, be aware of the following two restrictions:

      Never duplicate a section heading ([...]) within the ecx.ini file.

      Never duplicate a parameter assignment within a section.

  5. Re-establish Sun ONE Web Server security.

  6. Restore live data from your full database backup.

Remove the Previous Installation and Database Backup

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 the current version of ECXpert has been in production mode for a week or so, you may safely delete the previous installation and the Oracle database backup.

Previous      Contents      Index      Next     
Copyright 2003 Sun Microsystems, Inc. All rights reserved.