Sun ONE logo     Previous      Contents      Index      Next     

Sun logo
IS B2B: ECXpert and TradingXpert 3.6.3 Installation Guide 

Chapter 3 
Installing ECXpert and TradingXpert

This chapter describes how to use the Sun ONE Integration Server B2B Installer to install ECXpert and TradingXpert on the Solaris™ and Windows platforms. It covers the following topics:

Refer to the Installation Worksheet in Table 2-8 as you perform these tasks. Make sure that you have installed all needed dependent software, as described in Chapter 2, "Preinstallation Tasks," before you install either ECXpert or TradingXpert.

All the instructions in this chapter are written for a new install of ECXpert and TradingXpert. It is assumed that ECXpert and TradingXpert have either not been previously installed on the target system or that you have deleted all files and directories from any previous installation.

If you are upgrading from ECXpert version 3.6.2, see Appendix A, "Upgrading to ECXpert 3.6.3."

If you are upgrading from TradingXpert version 3.6.2, see the ECXpert Release Notes, at http://docs.sun.com/coll/S1_IntegrationServer_B2B_363.

If you are re-installing ECXpert Version 3.6.3, see Appendix B, "Reinstalling ECXpert."

Starting the Sun ONE Integration Server B2BInstaller

    To start the Installer on Solaris
  1. You should already be logged in as the ECXpert admin user.
  2. Make sure that the Oracle database is running:

    3. %ps -ef | grep ora

  3. If you are installing ECXpert remotely, from a C shell window, set your remote host to display on your local host.

    4. On the local host, enter:

    # setenv DISPLAY hostname:0.0

    where hostname is the name of the machine on which you are physically located.

    On the remote host, enter:

    # /usr/openwin/bin/xhost +

  4. Make sure you have a valid host name and domain name.

    5. To verify this, enter:

    # /bin/hostname

    # /bin/domainname

    Consult your system administrator if either your host name or domain name does not have a valid value.

  5. Change to the /cdrom directory.

    6. # cd /cdrom/ECXpert

    If this command does not work, enter the following command:

    # cd /cdrom/cdrom0

  6. Start the installer by running the setup executable.

    7. Do not run setup as a background process.

    # ./setup

    The Sun ONE Integration Server B2B Installer starts. This installer is based on the Setup SDK installer and works on both Solaris and Windows platforms.

    The figures in this chapter are taken from the Solaris Installer, and all paths are in Unix format. Ex: keylime/ecx_3_6_3. Some screens are only available on the Solaris platform, and are noted as such in the installation procedure.

    To start the Installer on Windows
  1. Log in as a user with administrative privileges.
  2. Make sure you have a valid host name and domain name.

    3. Consult your system administrator if either your host name or domain name does not have a valid value.

  3. Select the CD drive in the Explorer.
  4. Start the installer by double-clicking the setup.exe file.

    5. A Setup dialog box appears momentarily while some installer files are copied temporarily to your hard drive from the CD.

    The Sun ONE Integration Server B2B installer starts. This installer is based on the Setup SDK installer and works on both Solaris and Windows platforms.

    The figures in this chapter are taken from the Solaris installer, and all paths are in Unix format. Ex: keylime/ecx_3_6_3. Some screens are only available on the Solaris platform, and are noted as such in the installation procedure.

Installing ECXpert and TradingXpert

After starting the Sun ONE Integration Server B2B Installer as described in Starting the Sun ONE Integration Server B2BInstaller, the installer displays the Welcome Dialog as shown inFigure 3-1.

Figure 3-1  Sun ONE Integration Server B2B installer welcome dialog

  1. Click Next to continue with the installation.

    2. The installer displays the Sun license agreement as shown in Figure 3-2.

    Figure 3-2  Sun License Agreement

  2. Click Yes (Accept Agreement) to continue with the installation.

    3. The installer displays system requirements for Integration Server B2B on Solaris as shown in Figure 3-3. The system requirements for Integration Server B2B on Windows are shown in Figure 3-4.

    Figure 3-3  Integration Server B2B Solaris system requirements dialog

    Figure 3-4  Integration Server B2B Windows system requirements dialog

    You can continue to install ECXpert and TradingXpert from this point if your machine does not have the amount of recommended RAM, but you may not be able to operate in a high-volume production environment without the recommended amount of RAM.

  3. Click Next to continue with the installation.

    4. The Installation Directory dialog appears as shown in Figure 3-5.

    Figure 3-5  Integration Server B2B Installation Directory Dialog

    Caution

    If you are upgrading from an earlier version of ECXpert or TradingXpert do not simply install the current version over the old one.

    If a version of ECXpert is already installed in the default installation location, click Browse to specify a different directory into which to install the new version. For more information on reinstalling ECXpert, see Appendix B.

    For more information on upgrading TradingXpert, see the ECXpert Release Notes.

  4. To install ECXpert into a different directory than the default, click Browse to select the directory you want, and then click Next. Otherwise, simply click Next.

    5. The installer displays the Component Selection dialog as shown in Figure 3-6.

    Figure 3-6  Integration Server Component Selection Dialog

  5. Select the Integration Server B2B components to install and click Next.
    • If you want to install TradingXpert on the same machine with ECXpert, it is recommended that you install it with ECXpert at the same time.
    • If you want to install TradingXpert on a separate machine from ECXpert, select ECXpert only, complete the installation process for ECXpert, and read Configuring TradingXpert to Run on a Different Machine from ECXpert after completing the ECXpert installation.
    • If you are installing just TradingXpert on your machine, select TradingXpert and skip ahead to Step 18.

      • For more information about ECXpert/TradingXpert configurations, see ECXpert/TradingXpert Configurations.

      Note

      If the installer does not detect a supported version of Sun ONE Application Server on the machine, it will not allow installation of TradingXpert 3.6.3. Refer to the ECXpert Certification Matrix for the supported version of Sun ONE Application Server.

      The installer displays the Java Version dialog as shown inFigure 3-7.

      Figure 3-7  ECXpert Java Version Dialog

  6. To point to a Java Runtime Environment (JRE) that is already installed on your system: click Browse, locate the JRE’s bin directory, and click Next. Otherwise, click Next to install the bundled JRE.

    7. The installer displays the UserID and GroupID information dialog as shown in Figure 3-8.

    Note

    The JRE selected must be the supported version number or higher. For the supported version of the JRE, consult the Sun ONE Integration Server B2B certification matrix at:
    http://docs.sun.com/coll/S1_IntegrationServer_B2B_363.

    Figure 3-8  UserId and GroupID Information Dialog

  7. Fill inUserID and GroupID fields for the machine that will host ECXpert and click Next. Consult the values you specified in Table 2-8.

    8. Table 3-1  Values for the UserID and GroupID Dialog 

    Field

    Value

    UserID

    The UserID you created when filling out the pre-installation check list.

    The value is normally ecxadmin.

    GroupID

    The Group ID you created when filling out the pre-installation check list.

    This field only applies to Solaris platforms.

    Host Name

    The host where you want to install ECXpert.

    Domain Name

    The domain on which the ECXpert host resides.

    IP Address

    The IP address for the ECXpert machine.

    The installer displays the Secure Trading Agent Configuration dialog as shown in Figure 3-9.

    Figure 3-9  Secure Trading Agent Configuration Dialog

  8. Fill in the Secure Trading Agent configuration fields and click Next. Consult the values you specified in Table 2-8.

    9. If you do not want to install the Secure Trading Agent feature, select Skip Secure Trading Agent Configuration and click Next.

    If you are installing on Solaris, the installer displays the Partner Agent Server Configuration dialog as shown inFigure 3-10. If you are installing on Windows, skip to Step 10.

    Table 3-2  Values for the Secure Trading Agent Configuration Dialog 

    Field

    Value

    STA Home Path (ebRoot)

    The path to the Secure Trading Agent Installation Message Service Handler (MSH).

    The default paths for Solaris and Windows platforms are as follows:

    Solaris: /opt/SUNWebXML/S1ISSTA

    Windows: C:\Sun\SUNWebXML\S1ISSTA

    Specify the default path or your custom path if you modified the defaults.

    STA Login and Password

    The user Id and password for the Secure Trading Agent user that has access to send and retrieve messages. This user can be a Secure Trading Agent administrator or simply a Secure Trading Agent regular user.

    Secure Trading Agent uses the system user Id and system password to authenticate Secure Trading Agent administrators and regular users. Refer to the Secure Trading Agent documentation for more information.

    B2B Sender and Password

    All documents retrieved by the ebXML Communication Agent are submitted with this member as the sending member. Enter the name and password of this member.

    Figure 3-10  Partner Agent Server Configuration Dialog

  9. If you plan to use the ECXpert Partner Agent server, you must enter the port numbers that the server will use. You can specify any port number that is not in use; the port number must be greater than 1024.

    10. The installer displays the Database Configuration Parameters dialog as shown in Figure 3-11.

    Note

    If you do not use Partner Agent, you must still supply the port numbers as shown in Figure 3-10. You can use these ports for other purposes, but to proceed with the ECXpert installation, you must supply this information.

    Table 3-3  Values for the Partner Agent Server Configuration Dialog 

    Field

    Value

    Partner Agent Server
    Admin Port

    The port used to Administer the Partner Agent Server. The port number should be greater than 1024. The default port number is 55001.

    Partner Agent Server
    Agent daemon Port

    The port used as the Partner Agent Server general Agent. The port number should be greater than 1024. The default port number is 55002.

    Partner Agent Server
    FTP daemon Port

    The port used by the Partner Agent Server for FTP communication. The port number should be greater than 1024. The default port number is 55003.

    Partner Agent Server
    HTTP daemon Port

    The port used by Partner Agent Server for HTTP communication. The port number should be greater than 1024. The default port number is 55004.

    Partner Agent Server
    HTTPS daemon Port

    The port used the Partner Agent Server for HTTPS communication. The port number should be greater than 1024. The default port number is 55005.

    Figure 3-11  Database Configuration Parameters Dialog

  10. Fill in the Database fields and click Next.
  11. For the Database entries, consult the values you specified in Table 2-8 when you installed and configured your Oracle database.

    12. If a value for Oracle Home is already listed, you can leave it as is. Otherwise, specify the directory path where you installed the Oracle database you want to use with ECXpert.

    The installer displays the Oracle Schema Configuration dialog as shown in Figure 3-12.

    Table 3-4  Oracle Configuration fields 

     

     

    Oracle Home

    (ORACLE_HOME)

    Enter the directory that contains the Oracle software. This is the ORACLE_HOME path name. Instructions for installing Oracle are given in Installing Oracle.

    Solaris: /oracle/ora81
    /oracle/ora92

    Windows: D:\oracle\ora81
    D:\oracle\ora92

    Oracle SID

    (ORACLE_SID)

    Enter the Oracle SID, which is the name of the Oracle Server Instance. To get this value, see Installing Oracle.

    Solaris: myOracleSID

    Windows: myOracleSID

     

    NLS Language

    Enter the NLS _LANG character set. To get this value, see Table C-1.

    If you are using an Oracle 8 database, use AMERICAN_AMERICA.US7ASCII.

    If you are using an Oracle 9 database, use

    on Solaris:

    AMERICAN_AMERICA.WE8ISO8859P1

    on Windows:
    AMERICAN_AMERICA.WE8MSWIN1252

    Note that the character set specified by this value must match the character set specified for your Oracle installation. If these values do not match, you will not be able to install ECXpert.

    SQL*Net TNS Alias

    (Solaris)

    Server (Windows)

    Find this value in the tnsnames.ora file. This value is also known as the SQL*Net Connect String.

    ECXpert Oracle User

    (Windows)

    Database user

    (Solaris)

    Enter the name of the user who owns the ECXpert tables in the database.

    Solaris: Specify the value you used when you created the Oracle user in Create the Oracle ECXpert User Account.

    Windows: Specify the value you used when you created the Oracle user in Create the Oracle ECXpert User.

    Database password

    Enter the password of the user who owns the ECXpert tables in the database.

    Solaris: Specify the value you used when you created the Oracle user password in Create the Oracle User.

    Windows: Specify the value you used when you created the Oracle user password in Create the Oracle User.

    Figure 3-12  Oracle Schema Configuration Dialog

  12. Select Drop Tables and Create New to automatically run the SQL scripts that drop the database schema for the ECXpert database.

    13. Caution

    If you are upgrading or reinstalling ECXpert, stop here. If you select this option and click Next, your existing database will be overwritten.

    • If you are migrating from ECXpert Version 3.6.2, uncheck this option and click Next. Then complete the rest of the steps and tasks described in this chapter. Resume with the upgrade procedure at Step 5 for Solaris and Step 4 for Windows.
    • If you are re-installing ECXpert Version 3.6.3, uncheck this option and click Next. Then complete the rest of the steps and tasks described in this chapter. Resume with the reinstall procedure at Step 5 for Solaris and Step 4 for Windows.

    The installer displays the Mail Server Settings dialog as shown in Figure 3-13.

    Figure 3-13  Mail Server Settings Dialog

  13. Enter values to configure the mail server: you have a choice of using SENDMAIL or POP3.
    • If you choose Sendmail, you must supply a value for the Mail Spool file entry in the following format:

      • /var/mail/ECX_user_name

      The Mail Spool file will default to the Mail Host directory if it is not specified. Make sure that the user specified as the ECX user is part of the mail group so that this user can send and receive mail.

    • If you choose POP3, you must also specify the POP3 user name and password, as shown in Figure 3-13.

      • The installer displays the AS2 Configuration dialog as shown in Figure 3-14.

      Figure 3-14  AS2 Configuration Dialog

  14. Fill in the AS2 configuration fields and click Next. Consult the values you specified in Table 2-8. If you want to Skip AS2 configuration, check Skip AS2 Configuration and click Next.

    15. The installer displays the Additional Parameters for AS2 dialog as shown in Figure 3-15. If you chose to skip AS2 configuration, go to Step 16.

    Table 3-5  Values for the AS2 Configuration Fields 

    Field

    Value

    Web Server ROOT

    The path to the Web Server to be used for AS2 communication.

    AS2 Web Server Instance

    The name of the Web server instance you specified in Creating an AS2 or AIAG Protocol Listener on the Web Server

    AS2 Server Port

    Port to use to connect to the AS2 Web Server you specified Creating an AS2 or AIAG Protocol Listener on the Web Server.

    This port should be a unique number greater than 1024.

    Keystore Path (optional)

    Path to the Java Keystore file used by AS2.

    Example: /export/ecx_keystore.jks

    Keystore Password (optional)

    The password for an AS2 keystore.

    HTTP Proxy Host (optional)

    Name of proxy host for AS2 communication through a proxy server.

    HTTP Proxy Port (optional)

    Port number for AS2 communication through a proxy.

    Figure 3-15  Additional Parameters for AS2 Dialog

  15. Fill in additional Receiver and Sender information for AS2 communication between ECXpert and the AS2 Web Server and click Next.

    16. The installer displays the AIAG Configuration dialog as shown in Figure 3-16.

    Note

    AIAG configuration is only supported on the Solaris platform. If you are installing ECXpert on Windows, skip to Step 17.

    Table 3-6  Values for AS2 Sender and Receiver Dialog Fields 

    Field

    Value

    Submit Sender Name

    This value sets up a member name for an ECXpert partnership which uses the AS2 protocol.

    This value need not be filled in at this time. You can fill this value when setting up an AS2 trading partnership.

    Submit Receiver Name

    This value sets a receiver member name for an ECXpert partnership which uses the AS2 protocol.

    This value need not be filled in at this time. You can fill this value when setting up an AS2 trading partnership.

    Submit Sender Password

    This value sets the sender password for an ECXpert partnership which uses the AS2 protocol.

    This value need not be filled in at this time. You can fill this value when setting up an AS2 trading partnership.

    Submit File Type

    This value sets up a default file type for an ECXpert partnership which uses the AS2 protocol.

    This value need not be filled in at this time. You can fill this value when setting up an AS2 trading partnership.

    Host Name of
    Oracle Server

    Fully qualified host name of the oracle server.

    This value must be filled in.

    Figure 3-16  AIAG Configuration Dialog

  16. Fill in values for AIAG Configuration and click Next.

    17. The Automotive Industry Action Group (AIAG) protocol is intended only for partners that trade with other AIAG members. If you do not need to use AIAG as a protocol, check Skip AIAG Configuration and click Next.

    The installer displays the Configure ECXpert Startup on Reboot dialog, as shown in Figure 3-17.

    Table 3-7  Values for AIAG Configuration Dialog

    Field

    Value

    Web Server ROOT

    The path to the Web Server to be used for AIAG communication.

    AIAG Web Server Instance

    The name of the Web server instance you specified in Creating an AS2 or AIAG Protocol Listener on the Web Server.

    In the example, the instance is aiagws.

    Figure 3-17  Configure ECXpert Startup on Reboot Dialo

    If you ran the installer as a root user on Solaris or as an Administrator on Windows, you can configure ECXpert to startup on reboot.

  17. Select Configure Startup on Reboot and click Next to configure ECXpert to restart when you reboot or restart your machine. Otherwise, click Next.

    18. The installer displays the ECXpert Configuration path dialog, as shown in Figure 3-18.

    Figure 3-18  EXC Configuration Path Dialog

  18. Enter the path to the mounted ECXpert home (BDGHOME) installation you want to associate with TradingXpert and click Next to proceed with the installation.

    19. This field is only available to you when you are installing TradingXpert on a different machine than ECXpert. For more information, see Configuring TradingXpert to Run on a Different Machine from ECXpert.

    In a default installation, the path to BGDHOME is
    ECX_Inst_Dir/NS-apps/ECXpert

    where ECX_Inst_Dir is the directory where you installed ECXpert.

    Note

    If you are installing only ECXpert, the Path to ECXpert Home (BDGHOME) field is unavailable to you. Proceed to Step 21.

    The installer displays the Application Server Configuration dialog for TradingXpert, as shown in Figure 3-19.

    Figure 3-19  Application Server Configuration Dialog

  19. Fill in the values for the Application Server instance on which TradingXpert will be installed and click Next.

    20. Select SSL enabled for if SSL is turned on for the Application Server.

    The Application Server is used by the TradingXpert client to trade documents with ECXpert.

    The WebMail Configuration dialog appears, as shown in Figure 3-20.

    Table 3-8  Application Server Configuration Values 

    Field

    Value

    Application Server Home

    The path to the Application Server on the target machine

    Examples:

    on Solaris /keylime/s1as7

    on Windows C:\Sun\AppServer7

    Instance in Server

    Instance in the Application Server where TradingXpert will be deployed.

    Admin UserID

    The User ID for the application server administrator.

    Admin Password

    The password used by the application server administrator.

    Port of Application Server

    The administration port for the application server.

    Figure 3-20  WebMail Configuration Dialog

  20. Fill in the WebMail configuration values and click Next.

    21. If you do not want to configure WebMail, check Skip WebMail Configuration and click Next.

    The installer displays the ECXpert Information Verification dialog, as shown in Figure 3-21.

    Table 3-9  Values for WebMail Configuration Dialog 

    Field

    Value

    Messaging Server
    Instance Home

    Path to the Messaging Server Instance.

    Example: keylime/s1msg52/msg-instance1

    Messaging Server
    Host Name

    The host where the messaging server is installed.

    Application Server
    Host Name

    The host where the Application Server is installed.

    Messaging Server Port

    The messaging server instance port number.

    This should be a unique port number over 1024.

    TX Instance Port Number

    Port number of Application Server instance in which TradingXpert is deployed.

    This should be a unique port number over 1024.

    Figure 3-21  ECXpert Information Verification Dialog

  21. Scroll through the collected information for the Integration Server B2B installation. If you are satisfied with the values collected, click Install Now. Otherwise click Back to navigate to the screen that contains the values you want to change.

    22. Once you click Install Now, the installer displays the Installing... progress dialog, as shown in Figure 3-22.

    Figure 3-22  Integration Server B2B Installing... Progress Dialog

    Click Stop at any time to abort the installation. When the installation is complete, the Installation Summary dialog appears, as shown in Figure 3-23.

    Figure 3-23  Integration Server B2B Installation Summary Dialog

    Click View Log to view the installation log file created during the installation.

  22. Click Next to receive post-installation instructions.

    23. The installer displays the Post Installation Configuration dialog, as shown in Figure 3-24.

    Figure 3-24  Post Installation Configuration Dialog

  23. Click Finish to complete the installation.
  24. Read and follow the post installation instructions referenced in the postinstall.txt file in the ECXpert install directory.

Post-Installation Tasks

ECXpert Configuration Tasks

    To configure Sun ONE Web Server files

The postinstall.txt file contains instructions that you must follow to modify two configuration files: magnus.conf and obj.conf, for the Sun ONE Web Server. Information in these files is used to support the browser-based ECXpert Administration interface.

Follow the instructions shown in the postinstall.txt file to edit the files magnus.conf, and obj.conf. For these changes to take effect, you will need to shut down and restart the Web Server. See the section Applying Web Server Configuration File Changes to apply the configuration changes to the Web Server.

TradingXpert Configuration Tasks

If you installed TradingXpert, the postinstall.txt file contains additional instructions that you must follow to configure TradingXpert.

  1. Reference ECXpert’s Native library path for the Application Server.
  2. Set the read, write, delete permissions on ECXpert files in the Application Server’s server.policy file.
  3. Set environment variables for the TradingXpert machine.

After you complete the instructions in the postinstall.txt file, you must stop and then start the Application Server and restart the machine hosting TradingXpert for your changes to take effect.

Applying Web Server Configuration File Changes

Follow these steps to apply the changes you have made to the web server configuration files obj.conf, and magnus.conf.

  1. Start your web browser and go to the following URL.

    2. http://machine_name:port#/admin-serv/bin/index

  2. Enter the user ID and password.

    3. Enter a user ID and password for a Sun ONE Web Server user with administrative privileges.

  3. Apply any changes you made to the web server configuration files.
    1. A message window appears telling you that you must apply your changes. Click OK.
    2. In the Sun ONE Web Server bar at the top of the screen, click Apply. The Apply Changes screen appears.
    3. Click Load Configuration Files for the Sun ONE Web Server.
    4. If the changes are successfully applied, a “success” message window appears. Click OK to continue.
  4. Exit your web browser.

Set Up Environment Variables

Setting Environment Variables On Solaris

The routine operation of the ECXpert system, require the BDGHOME and NSBASE environment variables be properly set.

The value of BDGHOME is

Root_ECX_Install/NS-Apps/ECXpert

Root_ECX_Install is the directory that you specified as the directory for ECXpert at installation time.

The value of NSBASE is

Root_ECX_Install

Root_ECX_Install is the directory that you specified as the directory for ECXpert at installation time.

You must set the BDGHOME and NSBASE variables explicitly if you plan to start ECXpert from the command shell. If you start ECXpert from a browser, you do not need to set the variable.

    To set the BDGHOME and NSBASE environment variables
  1. Change to the ECXpert Administrator user. For example:

    2. # su - ecxadmin

  2. Determine the environment file to edit.

    3. # echo $SHELL

    The output of this command determines which environment file you must edit:

    Output

    Shell Being Used

    Environment File

    /sbin/sh

    Bourne

    .profile

    /sbin/csh

    C

    .cshrc

    /sbin/ksh

    Korn

    .profile or .kshrc

  3. Edit the definitions of BDGHOME and NSBASE into the shell startup file according to the following instructions:
    • If you are using the C shell, add the following lines:

      •   # setenv BDGHOME Root_ECX_Install/NS-apps/ECXpert

        # setenv NSBASE Root_ECX_Install

    • If you are using the Bourne or Korn shell, add the following line:

      •   # set BDGHOME=Root_ECX_Install/NS-apps/ECXpert

        # set NSBASE=Root_ECX_Install

  4. Save the file and exit the text editor.
  5. Enable the BDGHOME and NSBASE environment variables.

    6. Adding BDGHOME and NSBASE to the environment file for the ECXpert Administrator user ensures that it is enabled every time the ECXpert Administrator user logs in. You can now enable BDGHOME and NSBASE by switching to another user and then switching back. For example:

    # su - root
    # su - ecxadmin

    Alternatively, you could restart your system and log in as the ECXpert Administrator user.

Setting Enviroment Variables On Windows

Parts of the installation process, as well as the routine operation of the ECXpert system, require the $BDGHOME and $NSBASE environment variable be properly set.

    To set the BDGHOME variable
  1. From the Windows NT or Windows 2000 task bar, select Start > Settings > Control Panel > System.
  2. In the System Properties window, select the Environment tab.
  3. In the Variable input field, type BDGHOME.
  4. In the Value input field, type the full path you specified for the directory into which you installed ECXpert (Root_ECX_Install), and append “\NS-apps\ECXpert” to the end of the path.

    5. For example, if you had specified the path c:\foo\bar\mumble as the value of the Root_ECXInstall environment variable, you would set BDGHOME as

    c:\foo\bar\mumble\NS-apps\ECXpert

    You do not neet to reboot the machine to have these variable settings take effect; however, only new command-shell windows will see the changes.

    To set the NSBASE variable
  1. From the Windows NT or Windows 2000 task bar, select Start > Settings > Control Panel > System.
  2. In the System Properties window, select the Environment tab.
  3. In the Variable input field, type NSBASE.
  4. In the Value input field, type the full path you specified for the directory into which you installed ECXpert (Root_ECX_Install).

    5. For example, if you had specified the path c:\foo\bar\mumble as the value of the Root_ECXInstall environment variable, you would set NSBASE as

    c:\foo\bar\mumble

    You do not neet to reboot the machine to have these variable settings take effect; however, only new command-shell windows will see the changes.

Starting the ECXpert Administration Server

    To start the ECXpert Administration Server
  1. Start up a Web browser
  2. Display the ECXpert Administration home page.

    3. Enter the URL hostname:port_number, where hostname is the name of the machine on which your web server resides, and port_number is the number of the port on which your web server is listening.

    The ECXpert Main Screen appears, as shown in Figure 3-25.

    Figure 3-25  ECXpert Main Menu

  3. Save the URL to the ECXpert Main Menu as a bookmark.
  4. Click Admin to start the ECXpert Administration Server.

    5. The ECXpert Administration Server is not pre-configured with password protection. Use the Sun ONE Web Server Administration interface to enable this feature, if desired.

    The Management screen appears, as shown in Figure 3-26 when the ECXpert Administration Server is On. If your screen shows the ECXpert Administration Server Off, click the On portion of the button’s toggle to turn on the server.

    Figure 3-26  ECXpert Administration Screen: Main Menu

  5. Click the UpdateScreen button to refresh the screen.
  6. Check that the following buttons are turned on. If they are not, turn them on now.
    • ECXpert Admin Server
    • TCP/IP connector
    • Dispatcher
    • Gateway
    • FTP Client for Application Data
  7. Click Support in the top right corner.
  8. Enter the default ECXpert user name and password (ECX, ECX) as directed.

    9. This will confirm that the directory server and database connections are functioning properly.

Enabling Special Features

The following sections explain how to do the following:

Enable the Billing Code Feature

The billing code feature in this release requires customers to update the database stored procedure.

    To use the Billing Code feature
  1. Navigate to your Oracle directory:

    2. On Solaris
    cd $BDGHOME/dbadmin/oracle

    On Windows
    cd %BDGHOME%\dbadmin\oracle

  2. Start sqlplus using a command line with the following:

    3. sqlplus myaccount/mypassword@myserver

    where myaccount/mypassword@myserver is your configured account and its password.

    For example:

    sqlplus ECX36/ECX36@myHost

  3. From the sqlplus prompt, run the script:

    4. sqlplus> @ora_pkgbody.sql

  4. Restart ECXpert.

Enable the AIAG Feature

ECXpert 3.6.3 supports the AIAG E-5 2000 protocol standard on the Solaris platform. If your site uses this standard for business document processing, you will need to install support for documents exchanged with this protocol. The AIAG_setup.sh script creates or purges the AIAGTransaction Table, based on which option you specify. The syntax for invoking the AIAG_setup.sh script from a Bourne shell command line is:

% AIAG_setup.sh oracle_userame oracle_password tns_alias {create|purge}

Where:

Configuring TradingXpert to Run on a Different Machine from ECXpert

This section provides additional configuration tasks required if TradingXpert is installed on a machine different from ECXpert, as shown in Figure 3-27. The tasks described assume the following scenario:

The general procedures required to set up this configuration are detailed in the following sections for each platform.

Configuring TradingXpert to run on a machine different from ECXpert

    To configure TradingXpert to run on a machine different from ECXpert
  1. Set up TX Host as if ECXpert were installed locally. This involves setting up a BDGHOME environment variable and mounting the ECXpert installed directory when installing TradingXpert on the TX Host machine. See Setting up TX Host as if ECXpert Were Installed Locally.
  2. Set up TX Host to access the Oracle database used by ECXpert (it is assumed that ECX Host is already set up to access the database). See Setting up TX Host to Access the Oracle Database Used by ECXpert.

These procedures apply to an initial installation of TradingXpert on a separate machine, or to a migration of TradingXpert away from the machine hosting ECXpert. They allow TradingXpert to submit document files to ECXpert, retrieve documents from ECXpert, and access the partnership and process tracking information stored in the Oracle database.

Setting up TX Host as if ECXpert Were Installed Locally

    To set up TX Host as if ECXpert were installed locally
  1. Mount the ECX Host’s ECXpert installed directory structure (the directory referenced by BDGHOME) on TX Host.
  2. Give the TradingXpert user privileges to access (read) ECXpert’s BDGHOME/data directory.
  3. Install TradingXpert on the TX Host machine using the Integration Server B2B installer.
  4. Follow the postinstall.txt instructions for the TX Host.

    5. This includes:

    • updating the Application Server’s Instance Server Native library path to point to the ECXpert libraries installed on the TX Host
    • making changes to the server.policy file for the Application Server instance on which TradingXpert is installed.

      • Stop and then start the Application Server for these changes to take effect.

    • setting the BDGHOME and NSBASE environment variables on TX Host.

      • The BDGHOME environment variable on TX Host should point to the same directory as the BDGHOME environment variable on ECX Host

      The NSBASE environment variable on TX Host should point to the root directory for the ECXpert installation.

  5. Edit the ecx.ini file on ECX Host to specify a static TCP/IP port for communication with ECXpert (this is used to submit documents to ECXpert):
    1. Open the ecx.ini file.

      2. The file is located in the BDGHOME/config directory

    2. Modify the [tcpip-connector] section as follows:

      3. port_location = static
      admin_port_type = manual
      admin_port = any unused port
      listener_port_type = manual
      listener_port = any unused port

    3. Restart ECXpert for these changes to take effect.
  6. Modify TradingXpert’s TXproperties file on TX Host.

    7. If you are upgrading from TradingXpert 3.6.2 to TradingXpert 3.6.3, the FXproperties file is now called TXproperties. You must run a script to migrate from the old file to the new one. For more information, see ECXpert Release Notes.

    1. Turn on the TXremoteSubmission property:

      2. TX.remoteSubmission: TRUE

    2. Set the TXremoteECXPathPrefix property to specify the ECXpert mount point in Step 1.

      3. This path is to be pre-pended to directory paths specified in the ecx.ini file for the retrieval of ECXpert documents. For example, if the mountpoint is /h/ECX_Host, then TradingXpert will retrieve files from ECXpert at /h/ECX_Host/BDGHOME/data...

  7. Restart the TradingXpert machine for environment variables and property edits to take effect.

Setting up TX Host to Access the Oracle Database Used by ECXpert

    To set up TX Host to access Oracle
  1. Install the Oracle client on TX Host, if not already installed.
  2. Give the TradingXpert user privileges to access Oracle client software.
  3. Edit the tnsnames.ora file to reference the Oracle Server
  4. Check that the ORACLE_HOME and ORACLE_SID variables are properly set on ECX Host.

    5. These entries are found in the [ORACLE_ENV] section of the ecx.ini file, locate the DB_SERVER parameter.

  5. Check the DB_SERVER parameter of the ecx.ini file.

    6. In the [DB_SECTION] section of the ecx.ini file, locate the DB_SERVER parameter. If not already included, enter the following lines in the [DB_SECTION] section:

    [DB_SECTION]
    DB_SERVER=    Oracle DB alias
    DB_USER=Oracle username
    DB_SERVER=Oracle password

    where Oracle DB alias is the Oracle database alias from the tnsnames.ora file in Step 3.

Where To Go Next

If you have installed a working instance of ECXpert, continue to the next chapter, Chapter 4, "Testing Your ECXpert Installation," to test your ECXpert installation.

If you have installed TradingXpert and the test of your ECXpert installation is successful, continue on to Chapter 5, "Testing Your TradingXpert Installation," to test your TradingXpert installation.



Previous      Contents      Index      Next     

Copyright 2004 Sun Microsystems, Inc. All rights reserved.