ecxpert and tradingxpert 3.6.3 installation guide...6 ecxpert and tradingxpert 3.6.3 •...

Sun™ ONE Integration Server B2B

ECXpert and TradingXpert 3.6.3Installation Guide

February 2004

Sun Microsystems, Inc.4150 Network CircleSanta Clara, CA 95054U.S.A.

Part No: 817-5780-10

Copyright © 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, Solaris, Sun[tm] ONE and the Sun[tm] ONE logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc.Products covered by and information contained in this service manual are controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited.DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID._______________________________________________________________________________________________________________Copyright © 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés.Droits du gouvernement américain, utlisateurs gouvernmentaux - logiciel commercial. Les utilisateurs gouvernmentaux sont soumis au contrat de licence standard de Sun Microsystems, Inc., ainsi qu aux dispositions en vigueur de la FAR (Federal Acquisition Regulations) et des suppléments à celles-ci.Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d'autres pays et licenciée exclusivement par X/Open Company, Ltd.Sun, Sun Microsystems, le logo Sun, Java, Solaris, Sun[tm] ONE et le logo Sun[tm] ONE sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits protant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.Les produits qui font l'objet de ce manuel d'entretien et les informations qu'il contient sont régis par la législation américaine en matière de contrôle des exportations et peuvent être soumis au droit d'autres pays dans le domaine des exportations et importations. Les utilisations finales, ou utilisateurs finaux, pour des armes nucléaires, des missiles, des armes biologiques et chimiques ou du nucléaire maritime, directement ou indirectement, sont strictement interdites. Les exportations ou réexportations vers des pays sous embargo des États-Unis, ou vers des entités figurant sur les listes d'exclusion d'exportation américaines, y compris, mais de manière non exclusive, la liste de personnes qui font objet d'un ordre de ne pas participer, d'une façon directe ou indirecte, aux exportations des produits ou des services qui sont régi par la législation américaine en matière de contrôle des exportations et la liste de ressortissants spécifiquement désignés, sont rigoureusement interdites.LA DOCUMENTATION EST FOURNIE “EN L'ÉTAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFAÇON.

3

Contents

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

List of Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Audience for This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Organization of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Directory Variable Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Other Documentation Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21The ECXpert Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21The TradingXpert Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Sun ONE Integration Server B2B Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

ECXpert Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24TradingXpert Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25ECXpert/TradingXpert Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

About the Sun ONE Integration Server B2B Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27About the ECXpert Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Installer Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28What the ECXpert Installer Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

About the TradingXpert Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Installer Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29What the TradingXpert Installer Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Installed Sun ONE Integration Server B2B Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Installed ECXpert Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

ECXpert Software Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 ECXpert and TradingXpert 3.6.3 • Installation Guide • February 2004

Installed ECXpert Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installed TradingXpert Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

TradingXpert Software Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Installed TradingXpert Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

ECXpert User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Upgrading to ECXpert Version 3.6.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Where To Go Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 2 Preinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Verify Hardware and Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Solaris Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Windows Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Verify Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Disk Space on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Disk Space on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Verify TCP/IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Connectivity on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Connectivity on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Create an ECXpert Admin User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Set Up and Verify Oracle Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Data Storage in ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Working With Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Oracle on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Increase the Size of the Oracle Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Edit the initECX.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Create the Oracle ECXpert User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Set Up and Test Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Oracle on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Increase the Size of the Oracle Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Edit the initECX.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Create the Oracle ECXpert User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Set Up and Test Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Install and Configure an LDAP Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Restarting and Configuring LDAP on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Restarting and Configuring LDAP on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Install the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Creating an AS2 or AIAG Protocol Listener on the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Install Sun ONE Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Creating an Application Server Instance for TradingXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Modifying the server.policy File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Install the Sun ONE Messaging Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Install the Sun ONE Secure Trading Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Installing Secure Trading Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Contents 5

Configuring ECXpert to Work with Secure Trading Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Where To Go Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 3 Installing ECXpert and TradingXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Starting the Sun ONE Integration Server B2BInstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Installing ECXpert and TradingXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

ECXpert Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101TradingXpert Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Applying Web Server Configuration File Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Set Up Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Setting Environment Variables On Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Setting Enviroment Variables On Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Starting the ECXpert Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Enabling Special Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Enable the Billing Code Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Enable the AIAG Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Configuring TradingXpert to Run on a Different Machine from ECXpert . . . . . . . . . . . . . . . . . . . . . 109Configuring TradingXpert to run on a machine different from ECXpert . . . . . . . . . . . . . . . . . . . . 110

Setting up TX Host as if ECXpert Were Installed Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Setting up TX Host to Access the Oracle Database Used by ECXpert . . . . . . . . . . . . . . . . . . . . 112

Where To Go Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Chapter 4 Testing Your ECXpert Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Getting Ready to Test on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Getting Ready to Test on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Install the Windows FTP Server Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Get Ready to Test ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Testing ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Chapter 5 Testing Your TradingXpert Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Setting Up ECXpert for the Test Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Setting up ECXpert Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Exchange A: TXhost Sends Purchase Orders to webuser1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Exchange B: webuser1 Sends Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Exchange C: webuser1 Sends File Attachment to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Importing/Deleting Setup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Importing Setup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Deleting Setup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Testing TradingXpert with the Test Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154


Appendix A Upgrading to ECXpert 3.6.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Upgrading on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Shut Down ECXpert Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Database Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Upgrading to Oracle 9i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Set up and Test Your Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Back Up Your Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Back Up LDAP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Back Up ECX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Upgrade to Current ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Remove Saved Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Upgrading on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Shut Down ECXpert Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Upgrade to Oracle 9i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Set up and Test Your Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Back Up Your Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Back Up LDAP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Back up ECX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Upgrade to Current ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Remove Saved Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Appendix B Reinstalling ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179The Reinstallation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Reinstalling on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Shut Down ECXpert Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Check Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Back Up Your Existing ECXpert Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Back up ECXpert Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Reinstall ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Remove the Previous Installation and Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Reinstalling on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Shut Down ECXpert Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Check Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Back Up Your Existing ECXpert Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Back up ECXpert Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Reinstall ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Remove the Previous Installation and Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Appendix C Installing Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Oracle Installation for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Configure Shared Memory and Semaphores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Create the Oracle User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Contents 7

Set Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Install Oracle 8.1.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Run the root.sh Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Oracle Installation for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Create the Oracle User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Install Oracle 8.1.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Appendix D Installing Solaris Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Determining Which Patches to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Solaris 2.6 Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Solaris 2.7 Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Solaris 2.8 Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

9

List of Figures

Figure 1-1 ECXpert Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 1-2 TradingXpert Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 1-3 TradingXpert/ECXpert Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 2-1 Log On Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 2-2 Add Server Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 2-3 Add Server Success Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 2-4 Server On Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

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

Figure 3-2 Sun License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Figure 3-3 Integration Server B2B Solaris system requirements dialog . . . . . . . . . . . . . . . . . . . . . . 78

Figure 3-4 Integration Server B2B Windows system requirements dialog . . . . . . . . . . . . . . . . . . . 78

Figure 3-5 Integration Server B2B Installation Directory Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 3-6 Integration Server Component Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Figure 3-7 ECXpert Java Version Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Figure 3-8 UserId and GroupID Information Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Figure 3-9 Secure Trading Agent Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 3-10 Partner Agent Server Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Figure 3-11 Database Configuration Parameters Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Figure 3-12 Oracle Schema Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Figure 3-13 Mail Server Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figure 3-14 AS2 Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Figure 3-15 Additional Parameters for AS2 Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Figure 3-16 AIAG Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Figure 3-17 Configure ECXpert Startup on Reboot Dialo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Figure 3-18 EXC Configuration Path Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Figure 3-19 Application Server Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Figure 3-20 WebMail Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97


Figure 3-21 ECXpert Information Verification Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

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

Figure 3-23 Integration Server B2B Installation Summary Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Figure 3-24 Post Installation Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Figure 3-25 ECXpert Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 3-26 ECXpert Administration Screen: Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Figure 3-27 TradingXpert and ECXpert on Different Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110



Figure 4-3 Product Administrative Interface Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Figure 4-4 ECXpert Support User Interface Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Figure 4-5 ECXpert Partnership Administration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Figure 4-6 ECXpert Partnership Search Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Figure 4-7 Partnership Search Results Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Figure 4-8 ECXpert Demo Partnership Info Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Figure 4-9 ECXpert Demo Partnership Outgoing Protocols Page . . . . . . . . . . . . . . . . . . . . . . . . . 124

Figure 4-10 Completed Partnership Protocols Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Figure 4-11 ECXpert Utilities Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Figure 4-12 ECXpert Utilities Document Submission Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Figure 4-13 Completed Submission Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Figure 4-14 Submitted File Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Figure 4-15 ECXpert Support UI Tracking Tab File Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Figure 5-1 Service List Screen for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . . . . 137

Figure 5-2 Partnership Info for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . . . . . . 138

Figure 5-3 Input EDI for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . . . . . . . . . . . . 139

Figure 5-4 Protocols for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . . . . . . . . . . . . 140

Figure 5-5 Service List for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Figure 5-6 Partnership Info for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . 142

Figure 5-7 Input HREC for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . 143

Figure 5-8 Output EDI for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Figure 5-9 Protocols for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Figure 5-10 Service List for webuser1 Sending Attachments to TXhost . . . . . . . . . . . . . . . . . . . . . . 147

Figure 5-11 Partnership Info for webuser1 Sending Attachments to TXhost . . . . . . . . . . . . . . . . . . 148

Figure 5-12 Protocols for webuser1 Sending Attachments to TXhost . . . . . . . . . . . . . . . . . . . . . . . . 149

Figure 5-13 ECXpert Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Figure 5-14 ECXpert Utilities Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Figure 5-15 Document Submission Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

List of Figures 11

Figure 5-16 TradingXpert Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Figure 5-17 Trade Center Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Figure 5-18 Inbound Documents Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Figure 5-19 Purchase Order Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Figure 5-20 Attachment Options at Bottom of an Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

13

List of Tables

Table 1 Book Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table 2 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 3 DirectoryVariables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 4 ECXpert Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table 5 TradingXpert Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Table 1-1 ECXpert Software Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 1-2 Installed Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 1-3 TradingXpert Software Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Table 1-4 Installed J2EE Module Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 1-5 Installed Application Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 2-1 Hardware and Operating System Requirements for Solaris . . . . . . . . . . . . . . . . . . . . . 40

Table 2-2 Hardware and Operating System Requirements for Windows . . . . . . . . . . . . . . . . . . . 41

Table 2-3 LARGE Values for Parameters in the initECX.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table 2-4 Recommended Sizes for SYSTEM, TEMPORARY_DATA, and ROLLBACK_DATA Tablespaces 52

Table 2-5 LARGE Values for Parameters in the initECX.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Table 2-6 LDAP Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Table 2-7 Secure Trading Agent Information Required to Install ECXpert . . . . . . . . . . . . . . . . . . 65

Table 2-8 Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

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

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

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

Table 3-4 Oracle Configuration fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Table 3-5 Values for the AS2 Configuration Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

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

Table 3-7 Values for AIAG Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Table 3-8 Application Server Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Table 3-9 Values for WebMail Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97


Table 4-1 Demo Partnership Protocol Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Table 4-2 Submission Information for Solaris and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Table 4-3 Common Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Table 4-4 Post-installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Table 5-1 TCP Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Table 5-2 Service List details for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . . . . . 137

Table 5-3 Partnership Information for TXhost Sending Purchase Order to webuser1 . . . . . . . . . 139

Table 5-4 Input EDI Information for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . 140

Table 5-5 Protocols for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . . . . . . . . . . . . . 140

Table 5-6 Service List details for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . 141

Table 5-7 Partnership Information for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . 143

Table 5-8 Input HREC for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Table 5-9 Output EDI for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Table 5-10 Protocols for webuser1 Sending Invoices to TXhost . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Table 5-11 Service List details for webuser1 Sending Attachments to TXhost . . . . . . . . . . . . . . . . 147

Table 5-12 Partnership Information for webuser1 Sending Attachments to TXhost . . . . . . . . . . . 148

Table 5-13 Protocols for webuser1 Sending Attachments to TXhost . . . . . . . . . . . . . . . . . . . . . . . . 149

Table 5-14 Parameters for TXhost Sending Purchase Order to webuser1 . . . . . . . . . . . . . . . . . . . . 155

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

Table C-1 Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Table C-2 Login Information Values for the Oracle User Account . . . . . . . . . . . . . . . . . . . . . . . . 201

Table C-3 Values for the Create User Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Table D-2 Solaris Version 2.7 (OS 5.7) Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215



15

List of Procedures

To verify that your system is properly configured on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

To verify that your system is properly configured on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

To create a tnsnames.ora file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

To configure and restart the LDAP server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

To configure and restart the LDAP server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

To create a Protocol Listener for the AS2 or AIAG protocol: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

To create an Application Server instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

To modify the server.policy file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

To start the Installer on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

To start the Installer on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

To configure Sun ONE Web Server files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

To set the BDGHOME and NSBASE environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

To set the BDGHOME variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

To set the NSBASE variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

To start the ECXpert Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

To use the Billing Code feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

To configure TradingXpert to run on a machine different from ECXpert . . . . . . . . . . . . . . . . . . . . . . 110

To set up TX Host as if ECXpert were installed locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

To set up TX Host to access Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

To install the Windows FTP server service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

To submit the test Input_810.txt document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

To set up ECXpert manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

To import Test Scenario setup data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

To delete Test Scenario setup data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

To conduct the TradingXpert test scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

To upgrade to current ECXpert on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

To log out and shut down ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171


To set up and test your database connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

To back up your existing ECXpert database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

To back up important files from your current ECXpert installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

To upgrade to current ECXpert in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177


To log out and shut down all ECXpert services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

To check database connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187


To back up important files from your current ECXpert installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

To reinstall ECXpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

To configure shared memory and semaphores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

To create an Oracle user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

To set environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

17

Preface

This book explains how to install Sun™ Open Net Environment (Sun ONE) Integration Server, B2B Edition software (ECXpert and TradingXpert 3.6.3). This preface contains the following sections:

• “Audience for This Guide”

• “Organization of This Guide” on page 18

• “Conventions” on page 19

• “Other Documentation Resources” on page 21

Audience for This GuideThe audience for this guide is ECXpert and TradingXpert administrators who wish to install an ECXpert/TradingXpert system.

Organization of This Guide


Organization of This GuideAll users should read the introduction and pre-installation chapters before continuing on to the installation chapter. The following table briefly describes the contents of each chapter.

Table 1 Book Contents

Chapter Description

Chapter 1, “Introduction” Explains the ECXpert and TradingXpert software dependencies, what the installer does, and where ECXpert and TradingXpert software modules are installed.

Chapter 2, “Preinstallation Tasks”

Describes the tasks that must be completed before installing ECXpert and TradingXpert.

Chapter 3, “Installing ECXpert and TradingXpert”

Describes the installation of ECXpert and TradingXpert software on the Solaris™ and Windows Operating Environments.

Chapter 4, “Testing Your ECXpert Installation”

Explains how to test your ECXpert installation using a sample test scenario.

Chapter 5, “Testing Your TradingXpert Installation”

Explains how to test your TradingXpert installation using a sample test scenario.

Appendix A, “Upgrading to ECXpert 3.6.3”

Explains how you upgrade ECXpert 3.6.2 to ECXpert 3.6.3.

Appendix B, “Reinstalling ECXpert”

Explains how you reinstall ECXpert 3.6.3.

Appendix C, “Installing Oracle”

Explains how you install Oracle 8.1.7.

Appendix D, “Installing Solaris Patches”

Explains how you install the appropriate Solaris patches for the Solaris version you are using.

Conventions

Preface 19

ConventionsThis section provides information about the conventions used in this document.

Text Conventions

Table 2 Document Conventions

Format Description

italics Italicized text represents a placeholder. Substitute an appropriate clause or value where you see italic text. Italicized text is also used to designate a document title, for emphasis, or for a word or phrase being introduced.

monospace Monospace text represents example code, commands that you enter on the command line, directory, file, or path names, error message text, class names, method names (including all elements in the signature), package names, reserved words, and URL’s.

[] Square brackets to indicate optional values in a command line syntax statement.

ALL CAPS Text in all capitals represents file system types (GIF, TXT, HTML and so forth), environment variables (IMQ_HOME), or acronyms (ECXpert, JSP).

Key+Key Simultaneous keystrokes are joined with a plus sign: Ctrl+A means press both keys simultaneously.

Key-Key Consecutive keystrokes are joined with a hyphen: Esc-S means press the Esc key, release it, then press the S key.

Conventions


Directory Variable ConventionsECXpert documentation makes use of two directory variables whose values depend on the platform on which ECXpert and TradingXpert are installed. Table 3 describes these variables and explains how they are used.

In this guide, BDGHOME and TX_HOME are shown without platform-specific environment variable notation or syntax (for example, $BDGHOME and $TX_HOME on UNIX).

Table 3 DirectoryVariables

Variable Description

BDGHOME This is an ECXpert environment variable that specifies the location of the ECXpert installed software.

BDGHOME = Root_ECX_Install/NS-apps/ECXpert

Root_ECX_Install is the root installation directory of ECXpert software.

On Windoes NT or Windows 2000, if you installed ECXpert in the C:\Apps\ directory, the value of BDGHOME would be

C:\Apps\NS-apps\ECXpert

On Solaris, if you installed ECXpert in the directory MyECX, the value of BDGHOME would be

/MyECX/NS-apps/ECXpert

TX_HOME This variable is used in the documentation to refer to the root TradingXpert installation directory.

When you install TradingXpert standalone, you can select any directory in which to install TradingXpert files.

TX_HOME = arbitrary installation directory

When you install TradingXpert along with ECXpert, TradingXpert files are installed in the Root_ECX_Install/TX directory:

On Windows NT or Windows 2000, if you installed ECXpert in the C:\Apps\ directory, TX_HOME would be

C:\Apps\TX

On Solaris, if you installed ECXpert in the directory MyECX, TX_HOME would be

/MyECX/TX

For more information about these two configurations, see “ECXpert/TradingXpert Configurations” on page 26

Other Documentation Resources

Preface 21

Other Documentation ResourcesIn addition to this guide, ECXpert provides additional documentation resources.

The ECXpert Documentation SetThe documents that comprise the ECXpert documentation set are listed in Table 4 in the order in which you would normally use them.

Table 4 ECXpert Documentation Set

Document Audience Description

ECXpert Installation Guide Administrators Explains how to install ECXpert software on Solaris and Windows platforms.

ECXpert Release Notes Administrators and developers

Includes descriptions of new features, limitations, and known bugs, as well as technical notes.

ECXpert Administrator’s Guide

Users, administrators, developers

Explains the concepts, structure, and operation of ECXpert. It also describes ECXpert functions and provides guidelines for administering the system.

ECXpert Developer’s Guide Developers Describes the concepts, interface and underlying data organization of the ECXpert Software Developer’s Kit and the Java™ Native Interface API Class Library.

You only need to use this manual if you are running command line utilities or you are developing C++ programs that submit files to ECXpert or access the ECXpert database.

ECXpert Operations Reference Guide

Adminstrators Explains the operational issues in managing ECXpert. It also provides a reference on error messages that can be generated by ECXpert or passed through from third-party software components that ECXpert uses.

Other Documentation Resources


The TradingXpert Documentation SetThe documents that comprise the TradingXpert documentation set are listed in Table 5 in the order in which you would normally use them.

Table 5 TradingXpert Documentation Set

Document Audience Description

TradingXpert Administrator’s and Developer’s Guide

Users, administrators, and developers

Provides a quick-start tutorial for users, customizing instructions for administrators, and programming information for developers.

23

Chapter 1

Introduction

This chapter provides an overall introduction to installing the ECXpert product. It covers the following topics:

• “Sun ONE Integration Server B2B Software Dependencies” on page 23

• “About the Sun ONE Integration Server B2B Installer” on page 27

• “Installed Sun ONE Integration Server B2B Software” on page 30

• “ECXpert User Accounts” on page 36

• “Upgrading to ECXpert Version 3.6.3” on page 37

• “Where To Go Next” on page 37

Sun ONE Integration Server B2B Software Dependencies

The following sections describe the relationship between ECXpert, TradingXpert, and external software systems these two products depend on, and discuss possible ECXpert/TradingXpert configurations.

• ECXpert Software Dependencies

• TradingXpert Software Dependencies

• ECXpert/TradingXpert Configurations



ECXpert Software DependenciesTo manage document exchange between trading partners, ECXpert depends on a number of external software systems. Figure 1-1 illustrates the relationship between ECXpert and the following systems:

Communications agent support Some ECXpert communications agents depend on additional software support that you must install. For example, if you’re using JMS, you need to install the Sun™ ONE Message Queue product; if you are using e-mail (SMTP) communications, then an external mail server is necessary; or, if you are using ebXML communications, you must install Sun ONE Secure Trading Agent (STA) software. For additional information, see Table 1-1 on page 31.

Figure 1-1 ECXpert Software Dependencies

Oracle DBMS An Oracle® database system is required to store data about members (users), trading partnerships, and the processing of document exchanges by ECXpert.

LDAP server (optional) You can also store member (user) information in an LDAP server instead of in the Oracle database.

Oracle DBMS

Web Server

MailServer

SMTPSecureTradingAgent

CommunicationsAgents

File SystemStore

LDAP Server(Optional)

ebXML

JMS

HTTP

url

Web

Page

Browser-basedAdministration

ECXpert

Mercator

FTP

JMSMessageServer


Chapter 1 Introduction 25

Web server ECXpert uses a browser-based administration console that requires Web server support. A web server is also required for other HTTP-based ECXpert communication agents.

Data transformation software ECXpert uses two engines for transforming data exchanged by trading partners: a built-in XML Style Sheet Translator (XSLT) for transforming XML documents, and Mercator software, which is automatically installed, for transforming incoming Electronic Data Interchange (EDI) or XML formatted documents.

The ECXpert 3.6.3 platform certification matrix available at http://docs.sun.com/coll/S1_IntegrationServer_B2B_363 contains information about the supported versions for ECXpert software dependencies, including those illustrated in Figure 1-1 on page 24.

ECXpert 3.6.3 is supported on Solaris and Windows operating systems and platforms. The hardware and software requirements for these platfoms are specified in the platform certification matrix.

TradingXpert Software DependenciesTradingXpert provides a browser-based front end for ECXpert. It is used to support ECXpert trading partners that do not have Electronic Data Interchange (EDI) processing capability. TradingXpert makes it possible for these partners to use ECXpert to submit HTML formatted documents to their partners and retrieve similarly formatted documents from them.

To perform these document exchange functions, TradingXpert has critical dependencies on a number of external software systems, as illustrated in Figure 1-2:

ECXpert TradingXpert is a front end for ECXpert, submitting documents to ECXpert for processing and retrieving documents processed by ECXpert. TradingXpert relies upon the dispatching, data transformation, and partner management support provided by ECXpert.

Oracle DBMS In addition to interacting with ECXpert to submit documents, TradingXpert accesses the ECXpert Oracle database (in which ECXpert partnership and tracking information is stored) to retrieve documents processed by ECXpert.

http://docs.sun.com/coll/S1_IntegrationServer_B2B_363



Figure 1-2 TradingXpert Software Dependencies

Application server TradingXpert runs in an application server environment.

Web server A web server is required to support the interaction of browser-based ECXpert partners with TradingXpert—for receiving and sending of HTML formatted documents. The web server can be integrated with the application server (as in Sun ONE Application Server 7.0) or be a stand-alone product (as in Sun ONE Web Server 6.1).

The ECXpert 3.6.3 platform certification matrix available at http://docs.sun.com, contains information about the supported versions for TradingXpert software dependencies, including those illustrated in Figure 1-2 on page 26.

TradingXpert 3.6.3 is supported on Solaris and Windows operating systems and platforms. The hardware and software requirements for these platfoms are specified in the ECXpert 3.6.3 platform certification matrix.

ECXpert/TradingXpert ConfigurationsWhen installing TradingXpert, there are two basic configurations (see Figure 1-3): TradingXpert and EECXpert installed on the same host machine or on different machines. If TradingXpert and ECXpert are running on different machines, then both must be running the same operating system platform: Solaris or Windows.

OracleDBMS

url

Web

Page

Browser-basedECXpert Partner

ECXpert

TradingXpert

ECXpert API

Application Server

WebServer

url

Web

Page

Browser-basedECXpert Partner

http://docs.sun.com

About the Sun ONE Integration Server B2B Installer


Figure 1-3 TradingXpert/ECXpert Configurations

Running TradingXpert on a machine different from ECXpert requires a few additional configuration tasks compared to running both on the same machine (see “Configuring TradingXpert to Run on a Different Machine from ECXpert” on page 109). Both machines in this setup need to run the same operating system.


The Sun ONE Integration Server B2B 3.6.3 Installer allows you to install the ECXpert and TradingXpert component products together or separately. The following sections describe dependent software you should install prior to installating the component products, and what the Sun ONE Integration Server B2B 3.6.3 Installer does when installing the two component products:

• About the ECXpert Installer

• About the TradingXpert Installer

TradingXpert

ECXpert

ECXpert

On Same Machine On Different Machines

TradingXpert



About the ECXpert InstallerYou can install the ECXpert 3.6.3 product from the Sun ONE Integration Server, B2BEdition CD-ROM set. For detailed instructions, see the procedures in subsequent chapters.

Installer DependenciesWhile a number of external software systems are needed to run ECXpert (see “ECXpert Software Dependencies” on page 24), the ECXpert installer requires only the Oracle database and a web server in order to complete successfully.

Nevertheless, it is strongly recommended that other software systems on which ECXpert depends be installed prior to running the ECXpert installer. This allows the installer to configure ECXpert to run with these systems. It is recommended, for example, that the following software be installed before installing ECXpert:

• Web server (used for ECXpert’s browser-based administration tools)

• Independently installed communications agent support (optional):

❍ Mail server (used for SMTP communications)

❍ Web server HTTP/AS2 listener (used for AS2 communications)

❍ Web server HTTP/AIAG listener (used for AIAG communications)

❍ Sun ONE Secure Trading Agent (used for ebXML communications)

❍ Sun ONE Message Queue (used for JMS communications)

See Chapter 2, “Preinstallation Tasks” for more information about ECXpert installer dependencies.

What the ECXpert Installer DoesThe ECXpert installer performs the following tasks:

• sets up a directory structure and copies ECXpert files into the appropriate directories (see “Installed ECXpert Directory Structure” on page 31)

• modifies the ECXpert configuration file (ecx.ini)

• creates a schema in the Oracles DBMS and populates the tables with default information

• imports digital certificates used for authentication and encryption

• installs the Mercator SDK (on Solaris only).



• on Windows only:

❍ updates the Windows registry

❍ places ECXpert components in an ECXpert program group

• the installer prompts the user to modify the Web server’s magnus.conf and object.conf files to point to ECXpert's .cgi and HTML files

These modifications configure the Web server to support ECXpert's browser-based administration tools.

About the TradingXpert InstallerYou install the TradingXpert 3.6.3 product using the software distribution provided on the Sun ONE Integration Server, B2B Edition CD-ROM set. For detailed instructions, see the procedures in subsequent chapters.

Installer DependenciesThe software systems on which TradingXpert depends should be installed prior to running the TradingXpert installer. This allows you to configure these systems to support TradingXpert. The following software should be installed before installing TradingXpert:

• ECXpert

If you plan on installing TradingXpert on a separate machine, make sure you have a functioning ECXpert installation (including its associated Oracle database). Otherwise, if you plan on installing ECXpert and TradingXpert on the same machine, you only need to have an Oracle database for the combined installation of ECXpert and TradingXpert.

For more information, see “ECXpert/TradingXpert Configurations” on page 26.

• Application server

TradingXpert is deployed into an application server environment, making the application server a prerequisite to installing TradingXpert.

• Web server (should be independently installed if it is not already integrated with the application server—for example, Sun ONE Application Server 7.0 has a built in web server.)

See Chapter 2, “Preinstallation Tasks” for more information about TradingXpert installer dependencies.

Installed Sun ONE Integration Server B2B Software


What the TradingXpert Installer DoesTradingXpert installation places TradingXpert files into two directory trees (see “Installed TradingXpert Directory Structure” on page 33). The installation modifies the TradingXpert configuration file (TXproperties) to point to the root TradingXpert installation directory and to the ECXpert configuration file. It also deploys the TradingXpert Web Archive File (TX.war) to the Sun ONE Application Server.

Once the TradingXpert installer completes its work, you have to manually perform the following configurations in “TradingXpert Configuration Tasks” on page 102.

• update the Native library path for the Application Server to point to ECXpert’s JRE

• update the Application Server’s server.policy file with read, write, and delete permissions for TradingXpert files and users

• copy TradingXpert map files, as needed, to the appropriate ECXpert map directory

• optionally, configure TradingXpert to run on a different host machine from ECXpert (as shown in “ECXpert/TradingXpert Configurations” on page 26).


Depending on your choice of components, the Sun ONE Integration Server Installer can install the following on your machine:

• Installed ECXpert Software

• Installed TradingXpert Software

Installed ECXpert Software The software installed by the ECXpert installer consists of a number of different modules, as described in “ECXpert Software Modules,” below. These modules are placed in a directory structure outlined in “Installed ECXpert Directory Structure” on page 31.



ECXpert Software ModulesTable 1-1 describes the software modules included with the ECXpert product.

Installed ECXpert Directory StructureTable 1-2 shows the installed directory stucture for an ECXpert installation. All subdirectories are under the directory referenced by the BDGHOME environment variable (See Table 3 on page 20), namely:

Root_ECX_install/NS-apps/ECXpert

where Root_ECX_install corresponds to the directory in which ECXpert was installed.

Table 1-1 ECXpert Software Modules

Module Contents

Communications agents Processes that enable document delivery between business partners over various communication protocols: FTP, SMTP, HTTP, JMS, ebXML and so forth.

Dispatcher The central software engine that manages document translation and exchange between business partners.

Translator Software used to translate documents being exchanged between business partners: Mercator is used to transform Electronic Data Interchange (EDI) documents, and an XSLT translator is used to transform XML documents.

Scheduler Software used to schedule the receipt of input documents and the sending of output documents.

Database access software Software that provides access to an Oracle database.

Administration An administration server and cgi scripts used to support browser-based administration of ECXpert.

ECXpert SDK A software development kit used by programmers to access ECXpert functions directly.

Table 1-2 Installed Directory Structure

Subdirectory Contents

./UI HTML files used principally for ECXpert’s browser-based administration

./bin ECXpert binaries



./bin/jms Sun ONE MQ implementation libraries for use by jms client that’s built in to ECXpert.

./bin/ebxml/ Files used by ebXML Agent demonstration program.

./bin/ebxml/test ebXML Agent demonstration program.

./certificates Location used for exported and imported certificate files

./cgi-bin ECXpert cgi binaries used for ECXpert’s browser-based administration

./config ECXpert configuration files, such as ecx.ini

./data Contains subdirectories used to store temporary files. The most important subdirectories are:

/log location for log files written by the administration server

/work locations where work files are created and then deleted

/input location of received files waiting to be translated

/output location of translated files and other output files waiting to be sent

./dbadmin Oracle SQL scripts

./ecxsdk API library files, sdk binaries, documentation, and other files that comprise the ECXpert SDK

./legacy Map files used for exchanges with legacy applications, such as SAP

./lib ECXpert libraries

./maps Mercator mapping files

./mercsdk Mercator software program files (Solaris only)

./smtp Files used by the SMTP communications agent

./snmp Files used by an external management application for monitoring ECXpert resources

./servlet Solaris only: servlets and other information required for exchanges using Automotive Industry Accreditation Group (AIAG) formats

./dtd Solaris only: contains dtd’s required for exchanges using Automotive Industry Accreditation Group (AIAG) formats

Table 1-2 Installed Directory Structure (Continued)




Installed TradingXpert SoftwareThe software installed by the TradingXpert installer consists of a number of different modules, as described in “TradingXpert Software Modules,” below. These modules are placed in a directory structure outlined in “Installed Directory Structure” on page 25.

TradingXpert Software ModulesTable 1-3 identifies the software modules included with the TradingXpert product.

Installed TradingXpert Directory StructureTradingXpert files are installed in two separate locations: a J2EE module directory and a TradingXpert application directory. In this structure, the TradingXpert Java programs that enable TradingXpert operations are placed in a different location than their corresponding source code, and customizable files are separated from static user interface components.

Table 1-3 TradingXpert Software Modules

Module Description

Forms HTML forms used to view standard EDI document types. These use tags to insert data.

Graphical User Interface (GUI)

HTML templates and code used to implement browser screens in TradingXpert’s Trade Center user interface.

Java programs Programs (and corresponding source code) that enable TradingXpert operations. Many of these use the ECXpert API to submit documents to ECXpert and to access and update data in the ECXpert Oracle database.

ECXpert API An implementation of the ECXpert API that is used by TradingXpert’s Java programs.

Maps Software used to transform EDI-formatted documents to TradingXpert format (name-value pairs) and visa versa

Logger Software that tracks, logs, and reports TradingXpert activity.



J2EE Module DirectoryThe J2EE module directory is created automatically when the TradingXpert Web Archive file (TX.war) is deployed to the application server. It contains the subdirectories shown in Table 1-4 within the following application server directory path:

Root_AS_Install/domains/domain1/appServer_instance/applications/J2EE-modules/TX_1

where Root_AS_Install is the root installation directory for the application server and appServer_instance is the name of an application server instance you create to support TradingXpert.

TradingXpert Application DirectoryThe TradingXpert application directory structure is created when you install TradingXpert into a TX_HOME directory of your choice. Table 1-5 shows the installed subdirectory structure under TX_HOME:

Table 1-4 Installed J2EE Module Directory Structure


./web/en_us Static HTML templates used to implement screens in the Trade Center user interface.

./WEB-INF Contains a web.xml file that references files installed in the TradingXpert application directory (Table 1-5 on page 34) plus the following subdirectories:

/classes Java program files that enable TradingXpert operations

/lib ECXpert API libraries (ecxsdkjni.jar) used by Java program files.

Table 1-5 Installed Application Directory Structure


./config Contains the TradingXpert configuration file (TXproperties).

./document Working directory for processing document files.



./forms/en_us HTML forms and data for displaying documents:

/default Location for default forms (XSL stylesheets) representing EDI document types, as well as rules files (.rules) used for document turnarounds and order files (.order) used to assist ECXpert mapping. Subdirectories can contain files customized to various partners.

/from_scratch_data Data files (.dat) used to provide default values for from-scratch documents.

./lib ECXpert API native libraries.

./maps_etc Map files and other assorted files used to support TradingXpert operations:

/customization Sample customization files demonstrating creation of a new “cinfo” document type for processing by TradingXpert.

/import Data files containing ECXpert setup information (memberships, partnerships, and service lists) used in testing TradingXpert installation.

/map_sources Source code (in .zip format) that can be used to customize TradingXpert maps.

/maps/platform Maps for all document types supported (by default) by TradingXpert, where platform is nt and/or solaris.

/newmember Java programs (and source) used to support new member self-registration.

/reports Java programs (and source) used to support tracking and reporting of document status.

/sampledata Example data files to demonstrate various TradingXpert customizations.

./src Source code corresponding to Java programs that enable TradingXpert operations:

/document Source code for Java programs used to retrieve, manage, and process documents in response to Trade Center button clicks.

/events Source code for Java programs used to support email notification of inbound and outbound documents that have reached their expiration dates.

/login Source code for Java programs used to log in to ECXpert and return the opening Trade Center screen.

/profile Source code for Java programs used to access and update ECXpert membership information.

/tradeCenter Source code for Java programs used to implement operations in the main Trade Center screen.

Table 1-5 Installed Application Directory Structure (Continued)


ECXpert User Accounts


ECXpert User AccountsYou must make sure that software is installed under user accounts that allow ECXpert to function properly with its dependent software. Default values for these accounts depend on the installation platform.

The following user accounts are needed:

ECXpert admin user This is the account under which ECXpert is installed and administered. By default, the account name is ecxadmin.

Oracle administrator This is the account under which the Oracle database is installed and administered.

ECXpert Oracle user This is the account under which ECXpert accesses the Oracle database. By default, the account name is ECX36.

Web server administrator This is the account under which the Web server is installed and administered. It should be the same as the ECXpert administrator account.

SMTP mail user This is the account under which ECXpert accesses the SMTP (Pop3) mail server. On Solaris, if you use SendMail, you don’t need to set up this account.

./templates/en_us Dynamic XSL style sheets used to implement screens in the Trade Center user interface.

./users Location for user-specific information. User-specific subdirectories contain files such as document templates created by users in the Trade Center user interface.

Table 1-5 Installed Application Directory Structure (Continued)


Upgrading to ECXpert Version 3.6.3


Upgrading to ECXpert Version 3.6.33.6.3 is fully compatible with ECXpert 3.6.2 (except for Mercator data transformation issues). However, ECXpert 3.6.3 is generally not compatible with ECXpert 3.5 or earlier versions, largely because of changes in internal and external data formats and because of the version of Oracle database supported by ECXpert 3.6.3.

Appendix A, “Upgrading to ECXpert 3.6.3.” describes the upgrade process from ECXpert 3.6.2 to ECXpert 3.6.3. Please consult the ECXpert Release Notes for additional information about upgrading from earlier versions.

When upgrading an earlier version of ECXpert to Version 3.6.3, you must be careful not to over-write important configuration and data files. ECXpert maintains configuration, membership, and partnership data, as well as information stored in the Oracle database tables, that will be lost if you are not careful about how you perform an upgrade. For this reason it is recommended that you not try to install ECXpert 3.6.3 over earlier versions, without first reading the detailed steps for performing an upgrade, as provided in Appendix A, “Upgrading to ECXpert 3.6.3.”

For information on how to upgrade TradingXpert 3.6.2 to TradingXpert 3.6.3, see the ECXpert Release Notes.

Where To Go NextBefore attempting to install ECXpert and TradingXpert, be sure to read the information contained in Chapter 2, “Preinstallation Tasks.”

Where To Go Next


39

Chapter 2

Preinstallation Tasks

This chapter describes the tasks you must perform before you can install ECXpert. ECXpert depends upon a number of external software systems, and these systems must be in place before you can install ECXpert.

Before you install ECXpert, you must do the following:

• “Verify Hardware and Operating System Requirements”

• “Verify Disk Space Requirements” on page 41

• “Verify TCP/IP Connectivity” on page 43

• “Create an ECXpert Admin User Account” on page 45

• “Set Up and Verify Oracle Support” on page 46

• “Install and Configure an LDAP Directory Server” on page 56

• “Install the Web Server” on page 59

• “Install Sun ONE Application Server” on page 61

• “Install the Sun ONE Messaging Server” on page 64

• “Install the Sun ONE Secure Trading Agent” on page 64

• “Installation Worksheet” on page 66

• “Where To Go Next” on page 71

The following sections describe these tasks in greater detail and provide instructions that are specific to each installation platform.

Verify Hardware and Operating System Requirements


Verify Hardware and Operating System Requirements

This section describes the hardware and operating system requirements for installing ECXpert. For other software requirements, refer to the certification matrix at: http://docs.sun.com.

Solaris PlatformTable 2-1 shows the hardware and operating system requirements for installing and using ECXpert in the Sun™ Solaris™ operating environment.

NOTE Print out the section “Installation Worksheet” on page 66 and complete the information required in Table 2-8 as you complete the tasks described in this section. You will need this information during installation.

Table 2-1 Hardware and Operating System Requirements for Solaris

Hardware Platform Operating System Memory

Sun Ultra™ 1 (or compatible) workstation that is TCP/IP networked

For the Mercator’s Mercator Map Authoring System: Intel-based workstation running Windows 2000 or Windows NT.

Sun Solaris 2.6 (OS version 5.6) plus the patches listed in “Solaris 2.6 Patches” on page 214.

-or-

Sun Solaris Version 2.7 (OS version 5.7) plus the patch cluster listed in “Solaris 2.7 Patches” on page 215.

-or-

Sun Solaris Version 2.8 (OS version 5.8) - plus the patch cluster listed in “Solaris 2.8 Patches” on page 216.

Sun Solaris Version 2.9 (OS version 5.9)- plus the current patch cluster for Solaris 9 downloaded from SunSolve.

ECXpert only:

256 MB RAM (recommended) for each ECXpert machine.

ECXpert and TradingXpert:

512 Mbytes

http://docs.sun.com

Verify Disk Space Requirements

Chapter 2 Preinstallation Tasks 41

For hard disk space requirements, see “Verify Disk Space Requirements” on page 41.

Windows PlatformTable 2-2 shows the minimum hardware and operating system requirements for installing and using ECXpert in the Windows operating environment.

For hard disk space requirements, see “Verify Disk Space Requirements.”

Verify Disk Space RequirementsBefore you install ECXpert, make sure that you have sufficient disk space to run the application and its supporting Oracle database. Disk space requirements include the following:

• 500 MB for ECXpert

• approximately 200 MB for TradingXpert

Document storage might require up to 6 Gbytes.

• 1 GB for Oracle (Oracle does not have to be installed on the same host as ECXpert).

In addition, for Oracle, you must allocate sufficient disk space for tablespace and rollback management.

Table 2-2 Hardware and Operating System Requirements for Windows

Hardware Platform Operating System Memory

Intel Pentium or Pentium Pro workstation or server

Windows 2000 Server (Service Pack 4.0). If you anticipate installing TradingXpert on the same machine, you will need to install both products (ECXpert and TradingXpert) on Windows 2000.

ECXpert only:

256 MB RAM (recommended) for each ECXpert machine.

ECXpert andTradingXpert:

512 Mbytes

Verify Disk Space Requirements


Tablespace management Use the following formula to estimate the Oracle tablespace size needed:

2.5 KB x dailyDocs x daysRetained

where

dailyDocs specifies the number of documents you expect to receive daily

daysRetained specifies the number of days you must retain these documents

For example, if you receive 5000 documents daily and you retain them for thirty days, you would calculate the required tablespace size as follows:

2.5 x 5000 x 30= 375,000 KB

Rollback Segment Estimate 1.5 - 2 times the largest tablespace.

Disk Space on SolarisUse the following command to see the available volumes and their disk usage:

# df -k

The resulting output is similar to the following:

Make a note of the volumes you plan to use in the installation process. The ECXpert directory structure is shown in “Installed ECXpert Directory Structure” on page 31. This structure requires that the directories be created on a local device or an NFS-mounted device.

File system kbytes used avail capacity Mounted on/dev/dsk/c0t3d0s0 401389 12499 348760 4% //dev/dsk/c0t3d0s6 105486 87205 7741 92% /usr/proc 0 0 0 0% /procfd 0 0 0 0% /dev/fd/dev/dsk/c0t3d0s4 106012 21457 73955 23% /var/dev/dsk/c0t3d0s7 419319 9 377380 1% /export/home/dev/dsk/c0t3d0s5 1253167 72516 1155341 92% /opt/dev/dsk/c0t3d0s3 236816 106458 106678 50% /usr/openwin/dev/dsk/c0t0d0s2 1952573 1137822 619501 65% /disk00/dev/dsk/c0t1d0s2 14631 10595 2576 81% /disk01/dev/dsk/c0t2d0s2 1952573 1625123 132200 93% /disk02swap 414240 248 413992 1% /tmp

Verify TCP/IP Connectivity


The initial installation of ECXpert creates all of the subdirectories below the installation location you specify (referred to as Root_ECX_Install).

After installing ECXpert, you may change the configuration to move certain directories to other device locations, for performance reasons and to provide better fault tolerance.

Disk Space on WindowsTo determine available disk space on Windows, do the following:

1. Open a Command Prompt window.

2. Change directories (if necessary) to make the disk you want information about your current directory.

3. Assuming you’re planning to install on the C drive, enter the following command:

C: dir

The output of this command specifies the amount of free disk space on the C drive (at the end of the directory listing).

Verify TCP/IP Connectivity To be sure you have TCP/IP networking properly installed, the following conditions must be met:

• A permanent, static IP address is assigned to your machine (not a DHCP IP address).

• TCP/IP is bound to the actual network card

• DNS is configured (your machine’s host name and domain names must be valid DNS entries)

NOTE On Solaris, the ECXpert Installer uses the domain name in /etc/resolv.conf, not an NIS domain name.

Verify TCP/IP Connectivity


Connectivity on Solaris

➤ To verify that your system is properly configured on Solaris

1. Open a terminal window.

2. Determine what your IP address is by entering the following command:

# ifconfig -a

Information similar to the following is displayed in response:

The internet address is specified by the inet value. In the sample reply above, the internet address for the machine is 192.18.112.147.

3. Determine what your host name is by entering the command:

# /bin/hostname

The name for this machine’s host is displayed.

4. Determine what your domain name is. Type the command:

# /bin/domainname

The name for your machine’s domain is displayed.

5. Ping your host by entering the command:

# /usr/sbin/ping hostname

where hostname is the name of your host computer.

If your TCP/IP connectivity is working properly, the feedback from the ping command is:

hostname is alive

lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232 inet 127.0.0.1 netmask ff000000hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 192.18.112.147 netmask fffffe00 broadcast 192.18.113.255 ether 8:0:20:d1:2c:2f

Create an ECXpert Admin User Account


Connectivity on Windows

➤ To verify that your system is properly configured on Windows

1. Open a Command Prompt window.

2. Get configuration information by entering the following command at the prompt:

C:\ ipconfig /all

Or, you can enter this command to ping your host:

C:\> ping host

where host is the host name of your computer.

If your TCP/IP connectivity is working properly, the ping command should return a response like the following. In the output below, host_URL is the URL of your computer and host_IP_address is the IP address of your computer.

Create an ECXpert Admin User AccountFollow the instructions given in the User Guide documentation for your platform to create a user account with administrative privileges. This will be the account under which you install and administer (startup and shut down) ECXpert.

Note the user names and password that you create for your platform in the Installation Worksheet (Table 2-8 on page 66). The name and password pair used in examples in this book are ecxadmin, ecxadmin.

Pinging host_URL [host_IP_address] with 32 bytes of data:Reply from host_IP_address: bytes=32 time<10ms TTL=64Reply from host_IP_address: bytes=32 time<10ms TTL=64Reply from host_IP_address: bytes=32 time<10ms TTL=64Reply from host_IP_address: bytes=32 time<10ms TTL=64C:\>

Set Up and Verify Oracle Support


Set Up and Verify Oracle SupportThis section describes ECXpert’s data storage needs and explains how you set up and verify Oracle support.

Data Storage in ECXpertTwo types of data are used in ECXpert: static data, which is read frequently but modified infrequently, and dynamic data, which is read and modified frequently. For example, in ECXpert, static data is used to record information about individual members; dynamic data is used for metadata about the data files received from a communications agent and processed by the system.

Dynamic data needs to be stored in a way that allows for fast and easy modification. Static data does not need to be updated often, and so the primary concern is speed of access.

• Relational database management systems (RDBMS) are used to modify data records and are well suited for storage of dynamic data. The RDBMS used in ECXpert is Oracle. (Oracle can also handle the storage of static data.)

• Lightweight Directory Access Protocol (LDAP) defines a directory-based data storage model, and is implemented as an API for constructing such a directory system. The directory-based storage model provides for fast and efficient data access, but does not offer much support for data modification. Thus, it is well-suited for storage of static data. ECXpert 3.6.3 supports LDAP directories for static data. See “Install and Configure an LDAP Directory Server” on page 56 for more information.

Because Oracle can meet your needs for both dynamic and static data, you do not need LDAP storage. However, you might want to use LDAP to store information about individual members in those cases where that information must be shared with other systems that expect a directory structure. If you do decide to use an LDAP store, you need to determine whether ECXpert will act as the authority in maintaining, updating, and synchronizing data stored in Oracle with LDAP data; or whether your LDAP store should be read-only, leaving it to other software to make sure that data shared by LDAP and Oracle is properly updated in the Oracle database.



Working With OracleECXpert depends upon the support of a relational database management system. If you don’t already have an Oracle installation, Appendix C, “Installing Oracle” explains how you install Oracle 8.1.7 on the Solaris and Windows platforms. Please review this appendix and make sure that your Oracle database is installed and properly configured to support ECXpert.

When setting up your Oracle database, you might also be interested in configuring a multi-threaded server (MTS). This is a server that allows many user processes to share a few server processes, thus maximizing the number of users that can be supported. With MTS configuration, many user processes connect to a dispatcher that directs multiple incoming network session requests to a common queue. An idle shared server process from a shared pool of server processes can then pick up a request from the queue. This allows a small pool of server processes to serve a large number of clients.

It is recommended that MTS be turned on when you install Oracle. Consult with your data base administrator to determine the compatibility of MTS with other Oracle instances.

Oracle on SolarisAfter installing Oracle, as described in Appendix C, “Installing Oracle”, you must complete the following tasks:

• Increase the Size of the Oracle Tablespaces

• Edit the initECX.ora File

• Create the Oracle ECXpert User Account

• Set Up and Test Database Connectivity

These tasks are described in the following sections.

NOTE It is recommended, but not required, that you upgrade your existing Oracle 8.1.7 database to an Oracle 9i database for use with ECXpert 3.6.3.



Increase the Size of the Oracle TablespacesYou might need to increase the Oracle tablespace USER_DATA from its default size to a size that will accommodate the volume of ECXpert transactions you anticipate generating. The section “Verify Disk Space Requirements” on page 41 provides a formula you can use to estimate tablespace size requirements.

It is recommended that you allocate at least 100 MB for your USER_DATA tablespace. When setting the tablespace size, you should also enable the Oracle Auto-Extend feature, and set its value to approximately one fourth of the size you allocated for your tablespace. This ensures that your Oracle database will function properly with ECXpert.

Edit the initECX.ora FileYou should open and edit, as needed, the initECX.ora file to verify the use of the LARGE default values generated during the Oracle Enterprise Server installation process. Recommended values are indicated by the parameters shown in Table 2-3.

Create the Oracle ECXpert User AccountFollow these steps to create the Oracle ECXpert user account:

1. Log onto Solaris with your Oracle account. For example:

login: oraclepassword: oracle

2. Launch the Oracle Server Manager utility.

Table 2-3 LARGE Values for Parameters in the initECX.ora File

Parameter Recommended LARGE Value

db_file_multiblock_read_count 32

db_block_buffers 3200

shared_pool_size 9000000

processes 200

dml_locks 500

log_buffer 163840

sequence_cache_entries 100

sequence_cache_hash_buckets 89



# svrmgrlSVRMGR> connect system/manager

The default password is manager; yours may differ.

3. Create an ECXpert Oracle user; the following command creates the user account ECX36:

SVRMGR> create user ECX36 identified by ECX36default tablespace USERS temporary tablespace TEMP;SVRMGR> grant connect, resource to ECX36;SVRMGR> grant unlimited tablespace to ECX36;SVRMGR> exitServer Manager Complete#

Set Up and Test Database ConnectivityBefore you install ECXpert, set up and test your database to be sure that user root has access to the database, so that you can successfully install ECXpert. If user root does not have database access, you will get error messages during ECXpert installation.

1. Log in as user root.

# su - root

2. Determine the shell that root uses.

# echo $SHELL

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

3. Determine the shell that oracle uses.

# cat /etc/passwd | grep oracle

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

Output Shell Being Used Environment File

/sbin/sh Bourne .profile

/sbin/csh C .cshrc

/sbin/ksh Korn .profile or .kshrc



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

where the shell is csh.

4. Get into the oracle shell.

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.

❍ If you are using the C shell, type the following command:

# source ~oracle/.cshrc

❍ If you are using the Korn shell or the Bourne shell, type the following command:

# . ~oracle/your_environment_file

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

5. Check the environment settings.

# env

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

In addition to the values above, on Solaris 2.6, you must also set the TNS_ADMIN variable as follows:

TNS_ADMIN = $ORACLE_HOME/network/admin

6. Correct environment variable definitions as necessary.

If any of the above environment variables are not properly defined:

❍ Change to user oracle .

# su - oracle

$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



❍ Open the environment file that you referenced in Step 4 above in a text editor and add or modify the definitions as necessary.

❍ Save the environment file and exit the text editor.

7. Enable changes in environment variable definitions.

If you made changes in the environment file in Step 6 above, enable those changes now by switching to another user and then switching back:

# su - root# su - oracle

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

8. Check your tnsnames.ora file.

Check your tnsnames.ora file to make sure it contains the correct information. For example:

SX = ECX36(DESCRIPTION =(ADDRESS = PROTOCOL = TCP) (Host=bobo) (Port=1521)(CONNECT_DATA = (SID = ECX36)

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

# sqlplus ECX36/ECX36@your_connect_string

If this test fails, skip to Step 11.

10. Repeat the test from inside SQL*Plus:

SQL> connect ECX36/ECX36@your_connect_stringSQL> exit

11. Correct any connectivity problems.

If the test at either Step 9 or Step 10 failed, check the tnsnames.ora and listener.ora file to validate the settings, such as host name and SID. After making any necessary changes, go back to Step 9 above.

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

For further Oracle troubleshooting tips, refer to the ECXpert Operations Reference Guide.



Oracle on WindowsAfter installing Oracle, as described in Appendix C, “Installing Oracle”, you must complete the tasks described in this section in order to do the following:

• Increase the Size of the Oracle Tablespaces

• Edit the initECX.ora File

• Create the Oracle ECXpert User

• Set Up and Test Database Connectivity

Increase the Size of the Oracle TablespacesYou might need to increase the Oracle tablespace USER_DATA from its default size to a size that will accommodate the volume of ECXpert transactions you anticipate generating. The section “Verify Disk Space Requirements” on page 41 provides a formula you can use to estimate tablespace size requirements.

It is recommended that you allocate at least 100 MB for your USER_DATA tablespace. When setting the tablespace size, you should also enable the Oracle Auto-Extend feature, and set its value to approximately one fourth of the size you allocated for your tablespace. This ensures that your Oracle database will function properly with ECXpert.

For the other tablespaces the following size allocations are recommended:

These are general guidelines, and may not suit the requirements of your particular operating environment. Consult with your Oracle database administrator to evaluate the precise requirements for your site.

Table 2-4 Recommended Sizes for SYSTEM, TEMPORARY_DATA, and ROLLBACK_DATA Tablespaces

Tablespace Recommended size allocation

SYSTEM At least 50 MB

TEMPORARY_DATA At least 50 MB

ROLLBACK_DATA 1.5 to 2 times the size of the largest tablespace; at least 100 MB



Edit the initECX.ora FileIt is recommended that you review values stored in the initECX.ora file and edit these values if necessary. The file resides in the following directory:

drive:\Oracle\admin\host_name\pfile\

Specify the drive where your installed Oracle for drive; specify the name of the machine where you installed oracle for host_name.

These LARGE default values are generated during the Oracle Enterprise Server installation process. These default values are specified by the parameters shown in Table 2-5.

Create the Oracle ECXpert User Use this procedure to create the user that will be accessing ECXpert database tables:

1. Log onto a Windows Oracle account that has Oracle superuser privileges.

2. Start SQL*Plus.

3. In the User Name field, enter system.

4. In the Password field, enter manager.

Table 2-5 LARGE Values for Parameters in the initECX.ora File

Parameter Recommended LARGE Value

db_file_multiblock_read_count 32

db_block_buffers 3200

shared_pool_size 9000000

processes 200

dml_locks 500

log_buffer 163840

sequence_cache_entries 100

sequence_cache_hash_buckets 89



5. At the SQL prompt, enter the following three SQL commands:

SQL> create user ECX36 identified by ECX36 default tablespace USERS temporary tablesapce TEMP;SQL> grant connect, resource to ECX36;SQL> grant unlimited tablespace to ECX36;

Set Up and Test Database ConnectivityFollow the steps below to create a tnsnames.ora file. In an Oracle 8.1.7 installation, a sample tnsnames.ora file is in the directory C:\ORANT\NETWORK\NET80\ADMIN\SAMPLE, and you should use this file as a template for creating your own tnsnames.ora file.

➤ To create a tnsnames.ora file

1. Using Notepad, open the file:

C:\ORANT\NETWORK\NET80\ADMIN\SAMPLE\TNSNAMES.ORA.

2. Copy the following section from that file into a new ASCII text file:

myHost.world =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS =

(COMMUNITY = qa.world)(PROTOCOL = TCP)(HOST = sol)(PORT = 1521)

))(CONNECT_DATA =

(SID = OracleHost)(GLOBAL_NAME = myHost.world)

))

NOTE In all examples of directories, “C:\” is used as the drive specifier. If you have installed Oracle on a drive other than C:\ you should use that drive specifier instead of C:\.



3. In the first line of the above text, substitute the name of your server for the word myHost. For instance:

my_ecx_server.world=

Make sure the server name you use here is exactly the same as the one you enter during the installation, when the installer asks you for the name of your server.

4. Delete the following line from the file:

(COMMUNITY=tcp.world)

5. Enter the real name of the host on which you are installing ECXpert.

In the seventh line, change the word sol to the name of the machine on which you are performing the installation. For example:

(HOST=my_ecx_server)

6. Change the port number.

In the eighth line, change the port number to the number of the port on which your server will be listening. For example:

(PORT=5000)

7. In the line

(SID = OracleSID)

change OracleSID to your Oracle SID.

8. Save the new tnsnames.ora file.

Whatever text editor you used to create the file, make sure you save the file in ASCII format.

Now that you have a new, correctly edited tnsnames.ora file, you can test connectivity on your system.

1. In the Windows NT task bar, select Start > Programs > Oracle for Windows NT > Select Application Development > SQL Plus.

2. In the SQL*Plus Log On dialog box, enter the username and password you created for your ECXpert account. In the Host String field, enter the host name you used in the tnsnames.ora file.

Install and Configure an LDAP Directory Server


Figure 2-1 Log On Dialog Box

If everything is working correctly, the Oracle server will return with the following status message:

Connected to:Oracle8 Enterprise Edition Release 8.1.7 - ProductionWith the Partitioning and Objects optionsPL/SQL Release 8.1.7 - Production

If you don’t see the above message (or one similar to it), or you get an error message, check both the tnsnames.ora file and the listener.ora file to make sure all the values are correct. Repeat Step 1 and Step 2 above. If everything is correct you will see the above status message. If you don’t, or you see an error message, go back and make sure you have set everything up correctly.

For further Oracle troubleshooting tips, refer to your Oracle documentation and the ECXpert Operations Reference Guide.

Install and Configure an LDAP Directory ServerYou have the option of using an LDAP server. ECXpert supports the use of LDAP directory servers for storage of static data, such as membership information. You can also use Oracle to store membership information and other static data. If you prefer to use LDAP, you must install it and configure it as explained in the documentation provided by your LDAP provider. (If you are using the Sun ONE Directory Server as your LDAP provider, you must install the Sun ONE Directory Server before you install the Sun ONE Web Server.)



Once you configure ECXpert for use with LDAP, any changes to the LDAP repository will also be applied to the Oracle database, however, ECXpert will use the LDAP repository for membership information retrieval and authentication. When using ECXpert’s graphical administration interface or ECXpert’s API, both reporistories are kept in sync, but the LDAP respository is the primary source.

For information about ECXpert’s use of dynamic and static data, see “Data Storage in ECXpert” on page 46.

If you already have an LDAP server installed, you will need to restart it in order for the server to be properly configured. The ECXpert installer will add some predefined membership information to this directory at installation time if LDAP is installed and properly configured.

Refer to the Sun ONE Directory Server 5.2 Installation Guide for complete information on installing the Sun ONE Directory Server.

For instructions on configuring an LDAP directory server, refer to Chapter 5 of the ECXpert Administrator’s Guide, as well as the Sun ONE Directory Server Administrator’s Guide.

Refer to the ECXpert Administrator’s Guide for configuration information for both Sun ONE Directory Server and the Sun ONE Web Server.

Table 2-6 lists information you will need if you install an LDAP server.

Table 2-6 LDAP Installation Worksheet

Item Description

LDAP_USER Enter the Root Disntiguished Name for your LDAP server. This entry must match the Root DN entry set for ECXpert in the Sun ONE Administration server.

Example: Directory Manager, o=sun.com

LDAP_PASSWORD Enter the password associated with the LDAP_USER.

example: &7i#@dfI

Organization Enter the organization known by the LDAP server.

example: o=Netscape_org_unit

Organizational Unit Enter the organizational unit known by the LDAP server This entry must match the organizational unit set for ECXpert in the Sun ONE Administrative Server.

example: o=Netscape_org_unit

Host Enter the name of the host on which the LDAP server resides. This can be a local or remote host.

example: LDAP_ECX



Restarting and Configuring LDAP on Solaris

➤ To configure and restart the LDAP server on Solaris

1. Shut down the LDAP server (if any).

# ./LDAP_Install_dir/slapd-conf/stop-slapd

where LDAP_Install_dir is your LDAP server installation directory.

2. Copy the files ECXpert_user_at.conf and ECXpert_user_oc.conf (in the $BDGHOME/dbadmin/oracle/ directory) to the directory LDAP_Install_dir/slapd-hostname/config.

3. Make the following entries in the file LDAP_Install_dir/ns-schema.conf:

include LDAP_Install_dir/slapd-host/config/ECXpert_user_at.confinclude LDAP_Install_dir/slapd-host/config/ECXpert_user.oc.conf

4. Restart the LDAP sever:

# LDAP_Install_dir/slapd-host/restart-slapd

Restarting and Configuring LDAP on Windows

➤ To configure and restart the LDAP server on Windows

1. Shut down the LDAP server (if any).

In a Command shell window, type:

C:\> .\LDAP_Install_dir\slapd-conf\stop-slapd

where LDAP_Install_dir is your LDAP server installation directory.

2. Copy the files ECXpert_user_at.conf and ECXpert_user_oc.conf (in the BDGHOME\dbadmin\oracle\ directory) to the directory LDAP_Install_dir\slapd-host\config

Port Enter the port number of the LDAP server. By default, this is set to 389.

example: 447

Table 2-6 LDAP Installation Worksheet (Continued)

Item Description

Install the Web Server


3. Add the following lines to the LDAP_Install_dir\ns-schema.conf file:

include LDAP_Install_dir\slapd-host\config\ECXpert_user_at.confinclude LDAP_Install_dir\slapd-host\config\ECXpert_user.oc.conf

4. Restart the LDAP sever.

In the Command window type:

C:\> LLDAP_Install_dir\slapd-host\restart-slapd

Install the Web ServerECXpert’s administration GUI uses a web server to provide a browser-based administration interface. If you do not have a web server installed on your machine, you need to install it before installing ECXpert. (For ECXpert 3.6.3, you will need to install the Sun ONE Web Server version 6.1.)

• On the Solaris platform, install the Sun ONE Web Server, Enterprise Edition by following the instructions provided with the software.

When you install the Sun ONE Web Server, be sure to create an Enterprise Server instance with Server User set to the same user ID as the one you specified in “Create an ECXpert Admin User Account” on page 45.

• On the Windows platform, install the Sun ONE Web Server, Enterprise Edition by following the instructions provided with the software.

When you install the Sun ONE Web Server, be sure to log onto your Windows machine using the ECXpert admin user account you created in “Create an ECXpert Admin User Account” on page 45.

Creating an AS2 or AIAG Protocol Listener on the Web ServerIf you plan on using either the AS2 or AIAG protocol with ECXpert, you must create a web server instance to act as an HTTP listener for incoming messages. Before creating the web server instance, ensure that the following products are installed and running:

• Oracle® 8i or 9i

• The Administration Server for the Sun ONE Web Server 6.1

Install the Web Server


➤ To create a Protocol Listener for the AS2 or AIAG protocol:

1. Open the Web Server Administration Server interface from a web browser.

2. Click the Add Server link on the left side of the Servers tab page.

See Figure 2-2 for an example of the screen.

Figure 2-2 Add Server Screen

3. The fully qualified server name appears by default in the Server Name field.

4. Set the Server Port value to an unused port (9000 in the example).

5. Set the Server Identifier to the recommended default, AS2 or AIAGWS.

6. Set the Server User to the ECXpert login name (excadmin in the example).

7. Accept the default MTA Host, localhost.

8. Click the OK button. Figure 2-3 shows an example of the resulting screen.

Install Sun ONE Application Server


Figure 2-3 Add Server Success Screen

9. Click the Configure your new server... link.

10. Click the Server On button. This results in the screen shown in Figure 2-4.

Figure 2-4 Server On Screen

Install Sun ONE Application ServerCheck that Sun ONE Application Server 7.0—which includes a built-in web server—is installed and properly configured. (If Sun ONE Application Server 7.0 has not previously been installed, you must log in as root to install it.) With the application server running, perform the following steps:



1. Log in under your TradingXpert user account (for example, ecxadmin).

2. Create an application server instance that will host TradingXpert (see “Creating an Application Server Instance for TradingXpert” below).

3. Modify the server.policy file for the application server instance so that the TradingXpert setup script can delete temporary files (see “Modifying the server.policy File” on page 63).

Creating an Application Server Instance for TradingXpert

➤ To create an Application Server instance

1. Launch the Sun ONE Application Server’s Administration Server.

2. Enter the Administration Console URL:

http://AS_admin_host:port

where AS_admin_host is the server hosting the Application Server’s administration server and port is the port number of the listener.

3. Log in under the application server administrator account.

The Administration Console window opens, displaying existing application server instances.

4. Click New.

The new application server instance dialog appears.

5. Enter the Instance Name.

This is the name of the application server instance that will host TradingXpert (for example, tradingx).

6. Enter the HTTP Port.

This is the port on which the application server instance (web server instance) will be listening for requests from the TradingXpert browser-based user interface.



7. Enter a user account in the Run As User field.

Use the account under which TradingXpert will be running (for example, ecxadmin).

8. Click OK.

The Administration Console window displays the new application server instance.

9. Click the link for the newly created application server instance.

A multi-tabbed dialog appears.

10. Click Start to turn on the new server instance.

Modifying the server.policy File

➤ To modify the server.policy file

1. Open the server.policy file found in the following directory:

Root_AS_Install/domains/domain1/appServer_instance/config/

where Root_AS_Install is the root installation directory for the application server and appServer_instance is the name of the application server instance to be used by TradingXpert (for example, tradingx)—see “Creating an Application Server Instance for TradingXpert” on page 62.

2. Find the following entry:

permission java.io.FilePermission <<ALL FILES>>, read,write;

3. Add permission to delete.

read,write,delete

4. Save the file.

5. Restart the appliction server instance for the change to take effect.

Install the Sun ONE Messaging Server


Install the Sun ONE Messaging Server If you are planning to use SMTP as one of your communications protocols, you should install the Sun ONE Messaging Server. For installation instructions, refer to the Sun ONE Messaging Server Installation Guide for your platform.

• On Solaris, ECXpert 3.6.3 supports either POP3 (which requires the Sun ONE Messaging server) or SendMail. If you use the SendMail interface, then you do not have to install the messaging server.

• On Windows, you must install the Sun ONE Messaging server to use SMTP.

Install the Sun ONE Secure Trading AgentThis release of ECXpert includes Sun Open Net Environment (Sun ONE) Integration Server, Secure Trading Agent, which provides an environment for deploying ebXML agreements and exchanging ebXML messages with trading partners based on those agreements. (Secure Trading Agent is supported on Windows 2000 and Solaris version 8.)

When you install ECXpert, you can configure it to retrieve ebXML messages from and send ebXML messages to a Secure Trading Agent installation.

NOTE It is recommended that you install Secure Trading Agent before installing ECXpert. This allows the installer to automatically update your ecx.ini file at install time so ECXpert can access your Secure Trading Agent Installation.

However, if you install ECXpert first and later decide to install Secure Trading Agent, you can edit your ecx.ini file so ECXpert can access your Secure Trading Agent installation. For information on how to manually edit your ecx.ini file, refer to the manual ECXpert Support for ebXML Messaging.

Install the Sun ONE Secure Trading Agent


Installing Secure Trading AgentTo install Secure Trading Agent, follow the instructions in the Secure Trading Agent Installation Guide. Secure Trading Agent and the Secure Trading Agent Installation Guide are available on the Secure Trading Agent CD provided with your ECXpert distribution.

For information on how to configure ECXpert so it can access a Secure Trading Agent installation, refer to the manual ECXpert Support for ebXML Messaging, which is an addendum to the ECXpert Administrator’s Guide.

Configuring ECXpert to Work with Secure Trading AgentWhen installing ECXpert the ECXpert installer prompts you for the following information about your Secure Trading Agent installation:

Table 2-7 Secure Trading Agent Information Required to Install ECXpert

Information Description

Path to Secure Trading Agent root directory

Default paths for Solaris and Windows platforms:

Solaris: /opt/SUNWebXML/S1ISSTA

Windows: C:\Sun\SUNWebXML\S1ISSTA

Secure Trading Agent user Id 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.

ebXML B2B user The ebXML B2B user corresponds to a Secure Trading Agent user role. You define the name of the Secure Trading Agent user role in Secure Trading Agent.

If you have not yet defined a user role in Secure Trading Agent, pick a name for the ebXML B2B user here and use that name later to define the user role in Secure Trading Agent.

Installation Worksheet


Installation WorksheetPlease fill out the following Installation Worksheet table. You will need this information when you install ECXpert.

Table 2-8 Installation Worksheet (1 of 6)

Item Value

Install Directory

or

Destination Directory

Enter the full path name for Root_ECX_Install, that is, the directory in which you installed ECXpert.

Solaris example: /disk1

Windows example: c:\Apps

Enter your value here:

Web Server Instance Port and Host Name

If the Windows installer detects a web server (http server) on your machine, it displays the port number associated with that server and the name of the host on which it runs. If you want ECXpert to use a different web server, specify its port number and host name.

For example:

1055

joannahost

Enter your values here:

Web Server Instance destination location

The directory where your web server instance is located.

Windows: c: \apps\myWS


ECXpert Admin User This is the information you entered when you completed the tasks in “Create an ECXpert Admin User Account” on page 45.

Solaris: note the User ID and Group ID.

Windows: note the User ID and Password.


Secure Trading Agent Information (optional)

EBROOT

(Secure Trading Agent Home Path)

The path to your installation of Secure Trading Agent. The default paths for Solaris and Windows platforms are as follows:



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




ebXML User

Id 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 normal user.



ebXML B2B User The ebXML B2B user corresponds to a Secure Trading Agent user role. You define the name of the Secure Trading Agent user role in Secure Trading Agent.

If you have not yet defined a user role in Secure Trading Agent, pick a name for the ebXML B2B user here and use that name later to define the user role in Secure Trading Agent.


B2B Sending Member and Password

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


Partner Agent Information (Solaris only)

PAS Admin Port If you are using Partner Agent, specify the port number you want assigned to this port. If you are not using Partner Agent, you must still assign a port number to complete your installation of ECXpert; however, the port will not be used and will be available for your use. The port number must be greater than 1024 and be unique.


PAS Agentd Port If you are using Partner Agent, specify the port number you want assigned to this port. If you are not using Partner Agent, you must still assign a port number to complete your installation of ECXpert; however, the port will not be used and will be available for your use. The port number must be greater than 1024 and be unique.


PAS FTPD Port If you are using Partner Agent, specify the port number you want assigned to this port. If you are not using Partner Agent, you must still assign a port number to complete your installation of ECXpert; however, the port will not be used and will be available for your use. The port number must be greater than 1024 and be unique.



Item Value



PAS HTTPD Port If you are using Partner Agent, specify the port number you want assigned to this port. If you are not using Partner Agent, you must still assign a port number to complete your installation of ECXpert; however, the port will not be used and will be available for your use. The port number must be greater than 1024 and be unique.


PAS HTTPSD Port If you are using Partner Agent, specify the port number you want assigned to this port. If you are not using Partner Agent, you must still assign a port number to complete your installation of ECXpert; however, the port will not be used and will be available for your use. The port number must be greater than 1024 and be unique.


Oracle Information

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” on page 193.

Solaris: /oracle/ora81/oracle/ora92

Windows: D:\oracle\ora81D:\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” on page 193.

Solaris: myOracleSID

Windows: myOracleSID


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

By default, the value for Oarcle 8.1.7 isAMERICAN_AMERICA.US7ASCII.

By default, the value for Oracle 9i on Windows isAMERICAN_AMERICA.WE8MSWIN1252

By default, the value for Oracle 9i on Solaris isAMERICAN_AMERICA.WE8ISO8859P1

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.



Item Value



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” on page 48.

Windows: Specify the value you used when you created the Oracle user in “Create the Oracle ECXpert User” on page 53.


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” on page 195.

Windows: Specify the value you used when you created the Oracle user password in “Create the Oracle User” on page 200.


Mail Server Information

POP3 User Enter the user id for the POP3 user. (This is the user account created in the POP3 SMTP server.)


POP3 Password Enter the password for the POP3 user. (This is the user account created in the POP3 SMTP server.)


Mail Host Enter your mail host name. If you are using, Sendmail, this is the name of the machine you are receiving mail on. If you are using POP3, this is the name of the SMTP server.


Mail Spool File

(SendMail only)

Enter the path to your mail directory.

Solaris example: /var/mail/ecxadmin


AS2 Information (optional)

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



Item Value



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” on page 59.

In the example, the instance is as2.


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” on page 59.

This port should be a unique number greater than 1024. In the example, the port is 9000.


Keystore Path (optional) The path to an AS2 Web server certificate file.

Example: /export/ecx_keystore.jks


Keystore Password (optional)

The password to the Java keystore file.


HHTP Proxt 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.


Host Name of Oracle Server

Fully qualified host name of the oracle server.

This value must be filled in.


AIAG Information (optional)

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” on page 59.

In the example, the instance is aiagws.


Application Server Information (TradingXpert)

Application Server home

The path to the Application Server on the target machine

Examples:

on Solaris /keylime/s1as7

on Windows C:\Sun\AppServer7



Item Value

Where To Go Next


Where To Go NextYou are now ready to install ECXpert. For installation instructions, see Chapter 3, “Installing ECXpert and TradingXpert.”.

Instance in server Instance in the Application Server where Trading Xpert will be deployed.


Admin UseID The User ID for the application server administrator.


Admin password The password used by the application server administrator.

Port of Admin Server The administration port for the application server.


WebMail Information (TradingXpert)

Messaging ServerInstance Home

Path to the Messaging Server Instance.

Example: keylime/s1msg52/msg-instance1


Messaging ServerHost Name

The host where the messaging server is installed.


Application ServerHost 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.




Item Value

Where To Go Next


73

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:

• Starting the Sun ONE Integration Server B2BInstaller

• Installing ECXpert and TradingXpert

• Post-Installation Tasks

• Starting the ECXpert Administration Server

• Enabling Special Features

• Configuring TradingXpert to Run on a Different Machine from ECXpert

• Where To Go Next

Refer to the Installation Worksheet in Table 2-8 on page 66 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.”

http://docs.sun.com/coll/S1_IntegrationServer_B2B_363

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:

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

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.

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.


Chapter 3 Installing ECXpert and TradingXpert 75

5. Change to the /cdrom directory.

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

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.

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.

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 TradingXpertAfter starting the Sun ONE Integration Server B2B Installer as described in “Starting the Sun ONE Integration Server B2BInstaller” on page 74, 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.

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.

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.

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 on page 179.

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.

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” on page 109 after completing the ECXpert installation.

❍ If you are installing just TradingXpert on your machine, select TradingXpert and skip ahead to Step 18 on page 95.

For more information about ECXpert/TradingXpert configurations, see “ECXpert/TradingXpert Configurations” on page 26.



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.

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

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.

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.

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 on page 66.

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

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.



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 on page 66.

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 on page 86.

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:



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



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.

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

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.


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.

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

Field Value



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 ServerAdmin 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 ServerAgent 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 ServerFTP 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 ServerHTTP 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 ServerHTTPS 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 on page 66 when you installed and configured your Oracle database.

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” on page 193.

Solaris: /oracle/ora81/oracle/ora92

Windows: D:\oracle\ora81D:\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” on page 193.

Solaris: myOracleSID

Windows: myOracleSID

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

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” on page 48.

Windows: Specify the value you used when you created the Oracle user in “Create the Oracle ECXpert User” on page 53.

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” on page 195.

Windows: Specify the value you used when you created the Oracle user password in “Create the Oracle User” on page 200.

Table 3-4 Oracle Configuration fields (Continued)



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.

The installer displays the Mail Server Settings dialog as shown in Figure 3-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 on page 169 for Solaris and Step 4 on page 177 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 on page 185 for Solaris and Step 4 on page 190 for Windows.



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 on page 66. If you want to Skip AS2 configuration, check Skip AS2 Configuration and click Next.

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 on page 93.

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” on page 59

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” on page 59.

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



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.

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

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.

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

Table 3-5 Values for the AS2 Configuration Fields (Continued)

Field Value



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.


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


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


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.

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” on page 59.

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.

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.

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” on page 109.

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

where ECX_Inst_Dir is the directory where you installed ECXpert.

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

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



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.

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.



Figure 3-20 WebMail Configuration Dialog

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

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.

Admin Password The password used by the application server administrator.

Port of Application Server The administration port for the application server.

Table 3-9 Values for WebMail Configuration Dialog

Field Value

Messaging ServerInstance Home

Path to the Messaging Server Instance.

Example: keylime/s1msg52/msg-instance1

Messaging ServerHost Name

The host where the messaging server is installed.

Table 3-8 Application Server Configuration Values (Continued)

Field Value



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.

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

Application ServerHost Name

The host where the Application Server is installed.

Messaging Server Port The messaging server instance port number.


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


Table 3-9 Values for WebMail Configuration Dialog (Continued)

Field Value



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.

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

Post-Installation Tasks


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.


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” on page 102 to apply the configuration changes to the Web Server.

TradingXpert Configuration TasksIf 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 ChangesFollow 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.

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

2. Enter the user ID and password.

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.

a. A message window appears telling you that you must apply your changes. Click OK.

b. In the Sun ONE Web Server bar at the top of the screen, click Apply. The Apply Changes screen appears.

c. Click Load Configuration Files for the Sun ONE Web Server.

d. 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 SolarisThe 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:

# su - ecxadmin



2. Determine the environment file to edit.

# echo $SHELL

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

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.

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 WindowsParts of the installation process, as well as the routine operation of the ECXpert system, require the $BDGHOME and $NSBASE environment variable be properly set.



/sbin/csh C .cshrc




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

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

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


Starting the ECXpert Administration Server➤ To start the ECXpert Administration Server

1. Start up a Web browser

2. Display the ECXpert Administration home page.

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.

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.

Starting the ECXpert Administration 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.

Enabling Special Features


8. Enter the default ECXpert user name and password (ECX, ECX) as directed.

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

Enabling Special FeaturesThe following sections explain how to do the following:

• Enable the Billing Code feature

• Enable the AIAG feature (Solaris only)

Enable the Billing Code FeatureThe 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:

On Solariscd $BDGHOME/dbadmin/oracle

On Windowscd %BDGHOME%\dbadmin\oracle

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

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:

sqlplus> @ora_pkgbody.sql

4. Restart ECXpert.

Configuring TradingXpert to Run on a Different Machine from ECXpert


Enable the AIAG FeatureECXpert 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:

• oracle_username is the login name used to login to oracle (e.g. oracle)

• oracle_password is the password used to log in to the oracle database. (e.g. oracle.sunone)

• tns_alias is the TNS alias string used to identify the oracle instance (e.g. ORAINST.SUNONE)

• {create|purge} where the create option creates the AIAG Transaction table if it does not exist, and the purge option deletes all records from AIAGTransaction Table


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:

• “TX Host” is the host for TradingXpert. This includes, also, the Sun ONE Application Server and an Oracle client.

• “ECX Host” is the host for ECXpert and can also host an Oracle client (if Oracle is running on a remote host).

• “Oracle Host” is the host for the Oracle database server. (Oracle might also be running locally on ECX Host.)



Figure 3-27 TradingXpert and ECXpert on Different Machines

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” on page 112.

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.

TradingXpert

ECXpert

ECXpert

On Same Machine On Different Machines

TradingXpert



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.

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):

a. Open the ecx.ini file.

The file is located in the BDGHOME/config directory

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

port_location = staticadmin_port_type = manualadmin_port = any unused portlistener_port_type = manuallistener_port = any unused port

c. Restart ECXpert for these changes to take effect.



6. Modify TradingXpert’s TXproperties file on TX Host.

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.

a. Turn on the TXremoteSubmission property:

TX.remoteSubmission: TRUE

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

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.

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

Where To Go Next


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

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 aliasDB_USER=Oracle usernameDB_SERVER=Oracle password

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

Where To Go NextIf 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.

Where To Go Next


115

Chapter 4

Testing Your ECXpert Installation

This chapter explains how to test your ECXpert installation and helps you decide what your next step should be. Begin by reading the material that is appropriate for your platform:

• “Getting Ready to Test on Solaris”

• “Getting Ready to Test on Windows” on page 117

Then, proceed to test your ECXpert installation as described in the section:

• “Testing ECXpert” on page 119

Finally, read the section “What’s Next?” on page 133 to determine what to do next.

Getting Ready to Test on SolarisAfter you have installed ECXpert, it is a good idea to submit a test document to make sure you have installed and configured Oracle and ECXpert correctly.

Follow the steps below to submit a test document using the Input_810.txt document.

1. Create a backup copy of the test document by entering the following commands:

# cd $BDGHOME/maps

# cp Input_810.txt /tmp/Input_810.txt

Getting Ready to Test on Solaris


2. If you have not already done so, start up your web browser.

You can be logged on as user root, system, or the ECXpert admin user. Then, enter the following commands:

$ cd Root_ECX_Install/NS-apps/navigator$ ./netscape

3. If you have not already done so, display the ECXpert Administration home page now.

If you created a bookmark for the ECXpert Administration home page, select it now, or enter the URL:

http://hostname:port#

where hostname is the name of the machine on which your web server resides and the port number is the number of the port on which the web server is listening.

The ECXpert main menu screen is displayed as shown in Figure 4-1.


4. Click the Support link to open the Product Administrative Interface Login window and proceed to the section “Testing ECXpert” on page 119.

NOTE The DISPLAY environment variable must be set correctly or the browser does not run.

Getting Ready to Test on Windows

Chapter 4 Testing Your ECXpert Installation 117

Getting Ready to Test on WindowsBefore you test ECXpert on the Windows platform, you need to

• Install the FTP Server

• Get ready to test your installation

This section explains how you complete these tasks.

Install the Windows FTP Server ServiceIf you want to receive incoming FTP requests, you must install the Windows NT FTP Server service as described in this section before continuing on to the instructions in the “Get Ready to Test ECXpert” section.

➤ To install the Windows FTP server service

1. From the Windows task bar select Start > Settings > Control Panel.

2. Double-click Network.

3. Click Services, click Add, and then click Microsoft Peer Web Services.

4. Click OK, then type the path for the Windows NT source files.

For example, if you are using the Windows NT CD-ROM drive D:\, enter

D:\i386

5. Click OK to start the Microsoft Peer Web Services Setup.

6. The FTP Service is selected by default, but you may want to clear the check boxes for options you do not want to install.

The FTP Service, along with other Peer Web Service components, can be configured by using the Internet Service Manager tool.

NOTE If you are using Windows NT Server 4.0 instead of Windows NT Workstation 4.0, substitute Microsoft Internet Information Server 2.0 for each occurrence of Microsoft Peer Web Services throughout the following instructions.

Getting Ready to Test on Windows


7. Start Microsoft Internet Service Manager:

❍ If you are using Windows NT Workstation 4.0, from the Windows task bar select Start > Programs > Microsoft Peer Web Services > Internet Service Manager.

❍ If you are using Windows NT Server 4.0, from the Windows task bar select Start > Programs > Microsoft Internet Server (common) > Internet Service Manager.

❍ If you are using Windows 2000, you will need to install FTP service from the main installation disk (Add-On Components). You can then access the Internet Services Manager by selecting Control Panel > Administrative Tools >Internet Services Manager.

8. Click the FTP icon.

Select Properties > Service Properties. Deselect Allow only anonymous connections.

9. Click Yes.

10. Select Directories, and click Add to create directory aliases for use with ECXpert.

When you have finished creating all the directory aliases you need, click Apply, then click OK.

11. Select Properties > Exit.

Get Ready to Test ECXpertAfter you have installed ECXpert, it is a good idea to submit a test document to make sure you have installed and configured Oracle and ECXpert correctly.

➤ To submit the test Input_810.txt document

1. Create a backup copy of the test document. Navigate to the directory $BDGHOME\maps. Copy the file Input_810.txt to another file name.

2. If you have not already done so, start your web browser. (You should be logged in as root, system, or the ECXpert admin user.)

Testing ECXpert


3. Open the bookmark to the ECXpert Administration home page, or 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 server is listening. The ECXpert Main Menu screen is displayed as shown in Figure 4-2.


4. Click Support to open the Product Administrative Interface Login window and proceed to the section “Testing ECXpert” on page 119.

Testing ECXpertThe Product Administrative Interface Login window is shown in Figure 4-3.

Figure 4-3 Product Administrative Interface Login Window

1. Enter the default user name/password: ECX/ECX.

Testing ECXpert


When you have entered your login information, click Enter. The ECXpert Support Administrative screen is displayed as shown in Figure 4-4.

Figure 4-4 ECXpert Support User Interface Main Screen

2. Click the Partnership tab. The Partnership Administration screen appears, as shown in Figure 4-5.

NOTE If you are using a browser on Windows NT to interact with ECXpert, the user interface may not display with the correct colors if your video display settings are at 256 colors.

To correct this problem, set your video display to use more colors (for example, High Color - 16 bit, True Color - 24 bit).I

Testing ECXpert


Figure 4-5 ECXpert Partnership Administration Screen

3. Click Change. The Partnership Search screen appears, as shown in Figure 4-6.

Figure 4-6 ECXpert Partnership Search Screen

4. Click Search. The Partnership Results screen appears as shown in Figure 4-7.

Testing ECXpert


Figure 4-7 Partnership Search Results Screen

All of the available partnerships appear in the Partnership Results screen. Select the following partnership:

❍ Sender - PartnerA

❍ Receiver - ECX

❍ Doc Type - 810

❍ Version - 003020

Then click Retrieve (or double-click the highlighted partnership).

After briefly displaying the message ‘Please Wait……’, the Partnership Info tab is displayed with the partnership details, as shown in Figure 4-8.

Testing ECXpert


Figure 4-8 ECXpert Demo Partnership Info Tab

5. Click the Protocols Tab to display the Outgoing Protocol page, as shown in Figure 4-9. The default protocol you will see is SMTP.

Testing ECXpert


Figure 4-9 ECXpert Demo Partnership Outgoing Protocols Page

6. Set up the demo trading partnership to use the FTP Protocol. From the Outgoing Protocol drop-down list, change the default value of SMTP and select FTP.

7. Enter the following values, shown in Table 4-1, for the other fields on this page:

Testing ECXpert


Table 4-1 Demo Partnership Protocol Values

Field Name Field Description Enter This Value

Outgoing Protocol The protocol used to send the outgoing message

FTP

Pre-Communications Service

A custom service to invoke before using this protocol

No value

Delivery Timing Specifies when messages should be delivered.

• Immediate - all messages are sent as soon as they are ready to be sent.

• Scheduled - messages are sent at the time(s) specified via the ECXpert Scheduler

Immediate

Host Name The name of the FTP server The name of your FTP server

Port The IR port number for the FTP server—typically 21

The port number of your FTP server

User Name User Name for the member Your username

Account Account ID for the member No value

Password The password for the member’s user number or account ID

Your Password

Confirm Password The password for the member’s user number or account ID, entered again for verification

Your Password

Outbound Transfer Mode

The transfer mode used when sending outgoing files

Binary

Outbound Dir The directory where ECXpert's ftp-local-application comm agent will ftp the final, bundled file.

Solaris: $BDGHOME/tmp

Windows: C:\temp

Outbound Pattern The filename that will be used for the final, bundled file, not including the filename extension. This filename will be given an A## extension which will increment each time the Partnership is used to process a file. For example, if you use invoice.data as the outbound pattern, ECXpert will create:

invoice.data.A1invoice.data.A2invoice.data.A3and so on

invoice.data

Testing ECXpert


When you have finished filling in the Protocols tab, it should look similar to Figure 4-10 (with your values for host, port, user name, and account).

Inbound Dir A fully qualified pathname for the directory from which ECX will retrieve inbound documents (ftp get)

No value

Inbound Pattern A pattern (any set of characters) to search for in the Inbound directory. Files matching the pattern are retrieved into ECX; other files are left in the directory. If you leave the field blank, no files are retrieved. You can use any wild-card supported by FTP (like *, for example ‘PO.*’) to pick up multiple files

No value

Inbound File Type The file type of inbound files. This must match the data type specified in the Service List.

No value

Table 4-1 Demo Partnership Protocol Values (Continued)

Field Name Field Description Enter This Value

Testing ECXpert


Figure 4-10 Completed Partnership Protocols Tab

8. Click Change. On the verification window that appears, click Yes to verify the change. The change has been made when the Partnership Administration screen is displayed.

9. Go to the ECXpert Main Menu, and click the Utilities link.

The Utilities screen appears, as shown in Figure 4-11.

Testing ECXpert


Figure 4-11 ECXpert Utilities Window

10. Click the Document Submission Form link. The Submission Information form is displayed, as shown in Figure 4-12.

❍ On Solaris™

Copy the test file

/Root_ECX_Install/NS-apps/ECXpert/maps/Input_810.txt

to /temp.

In place of Root_ECX_Install in the first path, specify the ECX install directory.

❍ In Windows

Copy the test file

drive:\ecx36\NS-apps\ECXpert\maps\Input_810.txt

to C:\temp.

In place of drive in the first path, specify the drive specifier for the location where you have ECXpert installed.

Testing ECXpert


Figure 4-12 ECXpert Utilities Document Submission Screen

Enter the following information in the Submission Information form:

When you have finished filling in the Submission Information form, it should look similar to that shown in Figure 4-13.

Table 4-2 Submission Information for Solaris and Windows

Field Name Field Description Enter this Value

Sending Member The name of the member sending the file. PartnerA

Password The sending member’s password. No value is needed if the sending member is trusted.

No value

Receiving Member The name of the member receiving the file. ECX

File Name The fully qualified pathname for the file you want to send.

Windows: C:\TEMP\INPUT_810.txt

Solaris: /tmp/Input_810.txt

File Type The file type of the file you want to send. EDI

Testing ECXpert


Figure 4-13 Completed Submission Information Screen

11. Click Submit. When the file has been submitted, a screen appears, shown in Figure 4-14, indicating registration of the file for submission and confirmation that the submission is done. If an error appears, proceed to step 16.

Figure 4-14 Submitted File Screen

12. For any error messages that appear on the submittal screen, use the error and resolution descriptions provided in Table 4-3 to resolve common error messages. Once the document has been successfully submitted, continue with Step 13.

NOTE The screen showing completed submission used an internal working data path to the demo data versus the production data path specified in Table 4-2.

Testing ECXpert


13. Log onto the Product Administrative Interface again. Click the Support link. Then enter your login information in the Login window. The default user name/password is ECX/ECX.

When you have entered your login information, click Enter.

14. Verify that the document was submitted without an error.

15. Click the Tracking tab. The Enter Search Constraints tab appears, as shown in Figure 4-15.

Table 4-3 Common Errors

Error Resolution

Submission failed. [Error# 6012]

Go to ECXpert Main Menu > Admin > Management and make sure that the ECXpert Administration Server, FTP Server for Application Data, and TCP/IP Connector On/Off switches are in the On position.

Size of input file happens to be zero.[Error# 6024]

You have either incorrectly entered the file name in the Submission Information form, or the file does not exist. Check the BDGHOME/maps directory to make sure the file Input_810.txt file is there. If it is not, copy it from the backup version you created in step 1 and try submitting again.

Invalid trading partnership.[Error #603]

The Input_810.txt file contains an invalid trading partner, or the test data and the partnership do not match.

Open the Support UI and verify the Trading Partnership has the correct sender and receiver. For example, “ZZ/PartnerA” and “ZZ/ECXmember”.

Testing ECXpert


Figure 4-15 ECXpert Support UI Tracking Tab File Constraints

16. In the Date/Time portion of the screen, click the Calendar icon immediately to the right of the From Date: field. Today’s date appears in the From Date: field. Click Search.

The File Level Results tab appears, displaying all of today’s submissions. You can identify your submission by looking for the appropriate sender, receiver, and doc type.

If there is a green dot in the far left column of your submission, the test document was submitted correctly. Oracle and ECXpert have been installed and configured correctly.

What’s Next?


What’s Next?Now that you have successfully installed ECXpert 3.6.3, use the information in the following table to determine what your next step should be:

Table 4-4 Post-installation Steps

If you want to… Refer to…

Learn more about tuning and scaling your ECXpert System

ECXpert Administrator’s Guide.

Set up certificates ECXpert Administrator’s Guide, Chapter 9, “Working with Certificates”

Enable SNMP support ECXpert Administrator’s Guide

Enable Automatic Reboot of your ECXpert system

ECXpert Operations Reference Guide, “System Monitoring and Recovery Procedures” chapter. Refer specifically to the following section: “Recovery Following System Failure.”

Install Sun ONE Messaging Server The Sun ONE Messaging Server documentation included on separate media in your ECXpert package

Install Mercator Authoring System and mapping files

• ECXpert Administrator’s Guide, Appendix D.

• Mercator Getting Started Guide

Use older Mercator maps (version 5.0 or earlier)

Recompile all older maps using the Mercator 6.7.1 authoring tool, which is now built into ECXpert. This is particularly important if you use XML data.

Configure ECXpert to work with MSOutlook

ECXpert Administrator’s Guide

Enable AIAG (Solaris) See “Enable the AIAG Feature” on page 109.

Enable JMS See the ECXpert Administrator’s Guide, Appendix J and K, for information on enabling JMS support.

Configure ECXpert to access Secure Trading Agent (ebXML messaging) support.

See ECXpert Support for ebXML Messaging.

Configure ECXpert to access AS2 support.

See ECXpert Support for AS2 Messaging.

Configure ECXpert to access Custom Java Communications Agents.

See ECXpert Support for Custom Java Communications Agents.

Configure ECXpert to use WebMail. See ECXpert Support for WebMail.

What’s Next?


135

Chapter 5

Testing Your TradingXpertInstallation

This chapter explains how to test your TradingXpert installation using an example document exchange scenario. In this test scenario, a browser-based ECXpert trading partner (webuser1) receives a purchase order from an EDI-based trading partner (TXhost), and turns that purchase order around to submit an invoice, as well as a file attachment, back to TXhost.

To carry out the test scenario, you must first set up the required ECXpert service lists and partnerships between webuser1 and TXhost. Once this is done, you can run through the test scenario: TXhost submits a purchase order (EDI doc type = 850) to ECXpert, and webuser1 uses TradingXpert to retrieve that document and send back an invoice (EDI doc type = 810), as well as an attachment, to TXhost.

This chapter covers two topics:

• “Setting Up ECXpert for the Test Scenario”

• “Testing TradingXpert with the Test Scenario” on page 154

Setting Up ECXpert for the Test ScenarioIn order to conduct the test scenario, ECXpert must first be set up with the memberships, partnerships, and service lists required to perform the example document exchange. You can do the set up in either of two ways:

• using the ECXpert user interface to manually perform the setup—this helps you understand how to set up ECXpert for browser-based trading partners

• importing setup data provided in the TradingXpert software distribution—this might save you time.

Setting Up ECXpert for the Test Scenario


The sections that follow describe these two approaches.

Either way, the test scenario assumes that TXhost receives documents over FTP protocols, and you are therefore required to provide the TCP configuration information indicated in the following worksheet:

Setting up ECXpert ManuallyTo set up the necessary memberships, service lists, and partnerships for the test scenario manually, rather than import them (see “Importing/Deleting Setup Data” on page 150), you perform the following steps:

➤ To set up ECXpert manually

1. Set up memberships for TXhost and webuser1.

a. TXhost with EDI trading address of ZZ:TXhost.

b. webuser1 with EDI trading address of ZZ:webuser1.

2. Set up a service list and partnership for the following exchanges:

Exchange A: TXhost sends purchase order to webuser1

Exchange B: webuser1 sends an invoice back to TXhost

Exchange C: webuser1 sends a file attachment back to TXhost

The procedures for Step 2 are covered in detail in the following sections.

Exchange A: TXhost Sends Purchase Orders to webuser1This section explains how to set up the service list and partnership needed for TXhost to send purchase orders to webuser1.

Table 5-1 TCP Configuration Worksheet

FTP Configuration Parameter Default string in setup data Your Value

Host_name:port ftphost

User name ftpusername

Password ftpuserpwd

Outbound directory outputdir


Chapter 5 Testing Your TradingXpert Installation 137

Service List Setup AThis service list does not include the Gateway service: after a purchase order (ANSI X.12 850) is parsed and translated to TradingXpert format, it is stored by ECXpert until being retrieved by TradingXpert. If Gateway is in this service list, ECXpert attempts to send purchase orders directly to the trading partner.

Figure 5-1 and the accompanying Table 5-2 show how to set up a service list for this exchange.

Figure 5-1 Service List Screen for TXhost Sending Purchase Order to webuser1

Table 5-2 Service List details for TXhost Sending Purchase Order to webuser1

Field Value Explanation

Service List Details



Partnership Setup AThe partnership setup includes a number of screens corresponding to the different tabs required to configure the partnership.

Partnership Info Figure 5-2 and the accompanying Table 5-3 show how to set up the Partnership Info tab for this exchange.

Figure 5-2 Partnership Info for TXhost Sending Purchase Order to webuser1

Service List Data Type EDI Indicates the type of document being serviced

Sending Member ID * Applies to any sending member

Receiving Member ID webuser1 Applies to browser-based ECXpert partner

Select Service to add to List

Parse Breaks incoming EDI into its constituent parts.

Translate Converts documents from one format to another.

Table 5-2 Service List details for TXhost Sending Purchase Order to webuser1 (Continued)




Input EDI Figure 5-3 and the accompanying Table 5-4 show how to set up the Input EDI tab for this exchange.

Figure 5-3 Input EDI for TXhost Sending Purchase Order to webuser1

Table 5-3 Partnership Information for TXhost Sending Purchase Order to webuser1


Partnership Details

Sending Member TXhost EDI-enabled ECXpert partner sending the purchase order

Receiving Member webuser1 Browser-based ECXpert partner receiving the purchase order by way of TradingXpert

Document Type 850 ANSI X.12 doc type for purchase order

Partnership Type EDI to Application The document will be picked up by the TradingXpert application

Map Name 850html.sun (Solaris)or850html.mmc (Windows)

The map file used to convert inbound 850 documents to TradingXpert format (EDI to Application)

Incoming SMTP

[Parameters] Default Not needed for this document exchange.



Protocols Figure 5-4 and the accompanying Table 5-5 show how to set up the Protocols tab for this exchange.

Figure 5-4 Protocols for TXhost Sending Purchase Order to webuser1

Table 5-4 Input EDI Information for TXhost Sending Purchase Order to webuser1


Interchange Level Information

Sender Qualifier ID ZZ:TXhost EDI trading address

Receiver Qualifier ID ZZ:webuser1 EDI trading address

Standard ANSI Using ANSI X.12 doc type

Group Level Information

Functional ID Code PO Corresponds to purchase order

Group Version 004010

Functional Acknowledgments

[Parameters] Default Not needed.

Table 5-5 Protocols for TXhost Sending Purchase Order to webuser1


Outgoing Protocol

Drop-down protocol list POLL TradingXpert will retrieve the document, as opposed to its being sent to the Gateway



Exchange B: webuser1 Sends Invoices to TXhostThis section explains how to set up the service list and partnership needed for webuser1 to send invoices to TXhost.

Service List Setup BFigure 5-5 and the accompanying Table 5-6 show how to set up a service list for this exchange.

Figure 5-5 Service List for webuser1 Sending Invoices to TXhost

Table 5-6 Service List details for webuser1 Sending Invoices to TXhost



Service List Data Type EDI Indicates the type of document being serviced

Sending Member ID webuser1 Applies to browser-based ECXpert partner



Partnership Setup BThe partnership setup includes a number of screens corresponding to the different tabs required to configure the partnership.


Figure 5-6 Partnership Info for webuser1 Sending Invoices to TXhost

Receiving Member ID * Applies to any receiving member


Parse Breaks incoming document into its constituent parts.

Translate Converts documents from one format to another

Gateway Uses Gateway to send document to receiving member (TXhost)

Table 5-6 Service List details for webuser1 Sending Invoices to TXhost (Continued)




Input HREC Figure 5-7 and the accompanying Table 5-8 show how to set up the Input HEC tab for this exchange.

Figure 5-7 Input HREC for webuser1 Sending Invoices to TXhost

Table 5-7 Partnership Information for webuser1 Sending Invoices to TXhost


Partnership Details

Sending Member webuser1 Browser-based ECXpert partner sending the invoice by way of TradingXpert

Receiving Member TXhost EDI-enabled ECXpert partner receiving the invoice

Document Type 810 ANSI X.12 doc type for invoice

Partnership Type Application to EDI

The document will be sent by the TradingXpert application to ECXpert

Map Name html810.sun (Solaris)orhtml810.mmc (Windows)

The map file used to convert TradingXpert format to outbound 810 documents (Application to EDI)

Incoming SMTP




Output EDI Figure 5-8 and the accompanying Table 5-9 show how to set up the Output EDI tab for this exchange.

Figure 5-8 Output EDI for webuser1 Sending Invoices to TXhost

Table 5-8 Input HREC for webuser1 Sending Invoices to TXhost


Interchange Level Information

Sender Qualifier ID ZZ:webuser1 EDI trading address

Receiver Qualifier ID ZZ:TXhost EDI trading address

Standard ANSI Using ANSI X.12 doc type

Group Level Information

Application Sender NONE

Application Receiver NONE

Functional ID Code IN Corresponds to invoice

Group Version 004010




Figure 5-9 Protocols for webuser1 Sending Invoices to TXhost

Table 5-9 Output EDI for webuser1 Sending Invoices to TXhost


Enveloping Options

EDI Envelope ECXpert generates (or overrides) entire envelope

Standard ANSI

[Remaining parameters] Default Not needed for this document exchange.



Exchange C: webuser1 Sends File Attachment to TXhostThis section explains how to set up the service list and partnership needed for webuser1 to send file attachments to TXhost.

Table 5-10 Protocols for webuser1 Sending Invoices to TXhost


Outgoing Protocol

Pull-down protocol list FTP

Precommunications Service

<NONE>

Delivery Timing Immediate

Host Name myserver The name of the machine on which the invoice will be deposited

Port 21 The ftp port of the machine on which the invoice will be deposited, typically 21

Username ftpuser The username you will use to log on to the machine on which the invoice will be deposited

Password ****** The password for the user you entered in the Username field

Confirm Password ****** The password for the user you entered in the Username field, entered a second time for confirmation

Outbound Transfer Mode Binary

Outbound Dir /tmp (Solaris)D:\temp (Windows)

The directory where the file will be deposited

Outbound Pattern invoice_data


NOTE You should also go to the ECXpert Server Administration interface to check that the ECXpert FTP server is on. For instructions, see your ECXpert Administrator’s Guide, Chapter 3.



Service List Setup CFigure 5-10 and the accompanying Table 5-11 show how to set up a service list for this exchange.

Figure 5-10 Service List for webuser1 Sending Attachments to TXhost

Table 5-11 Service List details for webuser1 Sending Attachments to TXhost



Service List Data Type ATTACH Indicates the type of document being serviced

Sending Member ID webuser1 Applies to browser-based ECXpert partner

Receiving Member ID * Applies to any receiving partner


OutPrep Marks files that do not need processing as ready for the Gateway service.



Partnership Setup CThe partnership setup includes a number of screens corresponding to the different tabs required to configure the partnership.


Figure 5-11 Partnership Info for webuser1 Sending Attachments to TXhost

Gateway Uses Gateway to send document to receiving member (TXhost)

Table 5-12 Partnership Information for webuser1 Sending Attachments to TXhost


Partnership Details

Sending Member webuser1 Browser-based ECXpert partner sending the attachment by way of TradingXpert

Receiving Member TXhost EDI-enabled ECXpert partner receiving the attachment

Document Type ATTACH ANSI X.12 doc type for invoice

Partnership Type Application to Application

Neither partner is EDI-enabled.

Table 5-11 Service List details for webuser1 Sending Attachments to TXhost (Continued)





Figure 5-12 Protocols for webuser1 Sending Attachments to TXhost

Map Name No map file is needed.

Incoming SMTP


Table 5-13 Protocols for webuser1 Sending Attachments to TXhost


Outgoing Protocol

Table 5-12 Partnership Information for webuser1 Sending Attachments to TXhost




Importing/Deleting Setup DataRather than manually setting up ECXpert to support the TradingXpert test scenario, as detailed in “Setting up ECXpert Manually” on page 136, you can import the memberships, service lists, and partnerships for the test scenario using the import files provided on your installation disk.

Pull-down protocol list FTP

Precommunications Service

<NONE>

Delivery Timing Immediate

Host Name myserver The name of the machine on which the invoice will be deposited

Port 21 The ftp port of the machine on which the invoice will be deposited, typically 21

Username ftpuser The username you will use to log on to the machine on which the invoice will be deposited

Password ****** The password for the user you entered in the Username field

Confirm Password ****** The password for the user you entered in the Username field, entered a second time for confirmation

Outbound Transfer Mode Binary

Outbound Dir /tmp The directory where the file will be deposited

Outbound Pattern attachment


NOTE You should also go to the ECXpert Server Administration interface to check that the ECXpert FTP server is on. For instructions, see your ECXpert Administrator’s Guide, Chapter 3.

Table 5-13 Protocols for webuser1 Sending Attachments to TXhost




Importing Setup DataYou import data in the tx-mem.imp file into the ECXpert Oracle database using the ECXpert import utility.

➤ To import Test Scenario setup data

1. Log in to the TradingXpert machine as the same user under which you installed TradingXpert.

2. Change to the maps_etc/import directory in the TradingXpert installed directory structure (see “Installed TradingXpert Directory Structure” on page 33).

cd TX_HOME/maps_etc/import

3. Make backup copies of the tx-mem.imp and del-tx-mem.imp files.

4. Edit the tx-mem.imp and del-tx-mem.imp files.

Using a text editor, do a global search and replace of the strings “ftphost,” “ftpusername,” “ftpuserpwd,” and “outputdir” with the appropriate values from the table “TCP Configuration Worksheet” on page 136.

5. Make sure BDGHOME is set to the location of the ECXpert installation (see Table 3 on page 20) so that the application server will use the same ecx.ini file that ECXpert uses.

On Solaris:

setenv BDGHOME /disk1/Root_ECX_Install/NS-apps/ECXpert

where Root_ECX_Install is the root installation directory of ECXpert software.

On Windows:

In the Control Panel of the machine on which ECXpert is installed, double-click the System icon, then click the Environment tab. Make sure the BDGHOME variable has the value:

Root_ECX_Install\NS-apps\ECXpert

where Root_ECX_Install is the root installation directory of ECXpert software.

NOTE The import files provided on your installation disk are intended only to provide example data. The import files should not be modified except as instructed in the following procedure. Also, because of an error in the import file, you must correct the imported data, as described in the note appended to Step 8 on page 152.



6. From the BDGHOME/maps/ directory, make a copy of the map files with the following names:

On Windows

copy 850html.mmc 850html.map

copy html810.mmc html810.map

On Solaris

cp 850html.sun 850html.map

cp html810.sun html810.map

7. Make sure the application server can reference the BGDHOME/lib directory.

On Solaris:

If it is not, use the following syntax to modify the LD_LIBRARY_PATH environment variable in the administrator user’s .profile or .login file.

For the C shell:

setenv LD_LIBRARY_PATH BGDHOME/lib:$LD_LIBRARY_PATH

For the Bourne shell:

LD_LIBRARY_PATH=BGDHOME/lib:$LD_LIBRARY_PATH

export LD_LIBRARY_PATH

On Windows:

In the Control Panel of the machine on which ECXpert is installed, double-click the System icon, then click the Environment tab. Make sure the PATH environment variable includes the value:

BGDHOME/lib

8. Populate the database.

Use the ECXpert import utility, which is located at BDGHOME/bin/import. Type the following command in the Command Prompt window:

BDGHOME/bin/import ECX ECX TX_HOME/maps_etc/import/tx-mem.imp /tmp/good /tmp/bad

where

❍ ECX is both the username and the password of the ECXpert administrator

❍ TX_HOME/maps_etc/import/tx-mem.imp is the location of the import file that will populate TradingXpert members, partnership, and service lists



❍ /tmp/good is the log file that records successful data imports

❍ /tmp/bad is the log file that records rejected data.

Deleting Setup DataTo clean up the database and erase all the TradingXpert members, partnerships, and service lists that you just created, follow these steps:

➤ To delete Test Scenario setup data

1. Log in to the TradingXpert machine as the same user under which you installed TradingXpert.

2. Erase the TradingXpert Commerce Integration Suite test data in the database.

Use the ECXpert import utility, which is located at BDGHOME/bin/import. Type the following command in the Command Prompt window:

BDGHOME/bin/import ECX ECX TX_HOME/maps_etc/import/del-tx-mem.imp /tmp/good /tmp/bad

where

❍ ECX is both the username and the password of the ECXpert administrator

❍ TX_HOME/maps_etc/import/del-tx-mem.imp is the location of the import file that will delete the TradingXpert setup data.

❍ /tmp/good is the log file that records successful data deletions

❍ /tmp/bad is the log file that records rejected data deletions.

NOTE You will see error messages after running the import command line. Note that one record is rejected: the EDIFACT INVOIC partnership does not import correctly. To remedy this, log in to the ECXpert Administration interface and perform the following tasks:

1. Select the partnership of Doc Type INVOIC.

2. Select the Output EDI tab.

3. Change the Standard from ANSI to EDIFACT.

4. In the Version Number field, type “D”

5. In the Release Number field, type “97A”

6. Save the partnership.

Testing TradingXpert with the Test Scenario


Testing TradingXpert with the Test ScenarioThis section describes the procedure for conducting the TradingXpert test scenario: TXhost submits a purchase order (EDI doc type = 850) to ECXpert, and webuser1 uses TradingXpert to retrieve that document and send back an invoice (EDI doc type = 810), as well as an attachment.

➤ To conduct the TradingXpert test scenario

1. Open the ECXpert administration interface by entering the following URL in your browser:

http://ECXhostname:port/

where ECXhostname is the name of the host machine where ECXpert is installed, and port is the port number ECXpert is using.

The ECXpert Home Page (Figure 5-13) appears.

Figure 5-13 ECXpert Home Page

2. Click the Utilities button.

The ECXpert Utilities Menu (Figure 5-14) appears.



Figure 5-14 ECXpert Utilities Menu

3. Click the Document Submission Form link.

The Document Submission Form (Figure 5-15) appears.

Figure 5-15 Document Submission Form

4. Enter parameters for the submit command.

Refer to Table 5-14 for detailed information about the parameters.

Table 5-14 Parameters for TXhost Sending Purchase Order to webuser1

Parameter Value Explanation

Sending Member TXhost The sending member’s ID

Password **** Password for the sending member

Receiving Member webuser1 The receiving member’s ID



5. Click the Submit button.

A message appears providing feedback on the command. If any errors are encountered they are displayed first.

6. Optionally, view the tracking information for your submission.

a. Log in to the ECXpert Product Administrative Interface.

b. Click the Tracking button on the left.

The Enter Search Constraints tab appears.

c. Set Search Level to Document.

d. Enter today’s date.

e. Click the Search button.

7. Open the TradingXpert user interface by entering the following URL in your browser:

http://TradingXpert_hostname:port/TX

where hostname is the name of the host machine where TradingXpert is installed, and port is the port number TradingXpert is using.

The TradingXpert Login Screen (Figure 5-16) appears.

File Name 850edi.txt The name of the EDI purchase order file to be submitted to TradingXpert. The demo file, which is included in the /maps_etc/sampledata directory, is named 850edi.txt.

File Type EDI The type of data file being submitted to ECXpert

Table 5-14 Parameters for TXhost Sending Purchase Order to webuser1 (Continued)

Parameter Value Explanation



Figure 5-16 TradingXpert Login Screen

8. Log in to TradingXpert as webuser1.

Use the User ID webuser1 and the Password webuser1 and click Login.

The Trade Center Screen (Figure 5-17) appears.

Figure 5-17 Trade Center Screen

9. View the incoming purchase order.

a. Click the Inbound icon to view incoming documents.

The Inbound Documents Screen (Figure 5-18) appears.



Figure 5-18 Inbound Documents Screen

b. Search for all incoming documents from TXhost.

c. Find the purchase order just sent from TXhost and click View.

The Purchase Order Document (Figure 5-19) is displayed.

Figure 5-19 Purchase Order Document



10. Create an invoice from the purchase order.

At the bottom of the purchase order, click the Create Invoice button.

An invoice form (Figure 5-20) will appear; the data fields will be pre-filled with data from the purchase order.

Figure 5-20 Attachment Options at Bottom of an Invoice

11. Attach a file to the invoice.

At the bottom of the invoice screen is an Attach File section. Attach any file on your hard drive by first either entering the full path of the file or clicking Browse to select a file, and then selecting Any Type from the drop-down menu.

12. Submit the invoice with attachment to TXhost by clicking the Submit Document button.

A screen will appear confirming that the document was submitted successfully.

13. Verify receipt of the invoice and attachment in ECXpert.

a. Return to the ECXpert administration interface:

http://ECXhostname:port

where ECXhostname is the name of the host machine where ECXpert is installed, and port is the port number ECXpert is using.

b. On the ECXpert home page (Figure 5-13), click Support.



c. Enter the ECXpert administrator user name and password and click Enter.

d. Click the Tracking button, then enter search constraints to find the 810 invoice document sent by webuser1 to TXhost.

e. View tracking information for the inbound document and attached file.

161

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”

• “Upgrading on Windows” on page 170

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

• “Shut Down ECXpert Services”

• “Database Migration” on page 163

• “Back Up Your Database” on page 166

• “Back Up LDAP Data” on page 167

• “Back up ECX Files” on page 176

• “Upgrade to Current ECXpert” on page 168

• “Remove Saved Files” on page 170

Shut Down ECXpert ServicesIf 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.

Upgrading on Solaris


1. Log out of the ECXpert Support Interface.

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

2. Shut down all ECXpert services.

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


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.

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.

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.

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.

Manually kill the process ID for Program.o.


Appendix A Upgrading to ECXpert 3.6.3 163

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

• Upgrading to Oracle 9i

• Checking your database connectivity

• Backing up your existing ECX database

• Backing up LDAP data

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

Set up and Test Your Database ConnectivitySet 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.

# su - root

2. Determine the shell that root uses.

# echo $SHELL

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

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.



/sbin/csh C .cshrc




3. Determine the shell that oracle uses.

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

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.

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

# source ~oracle/.cshrc

where oracle is your Oracle user, typically oracle.

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

# . ~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.

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

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

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

# su - oracle.

b. Open the environment file that you referenced in Step 4 above in a text editor and add or modify the definitions as necessary.

c. Save the environment file and exit the text editor.

7. Enable changes in environment variable definitions.

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.

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:


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


SQL> connect ECX36/ECX36@your_connect_string

SQL> exit

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




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

# ./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:



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

Export done in US7ASCII character set and US7ASCII NCHAR character setAbout 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 exportedExport terminated successfully without warnings.#



Back Up ECX FilesFollow 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” on page 73.

2. Proceed normally through the screens for the Installer up to and including Step 10 on page 86.

Be sure to stop at Step 12 on page 88. Do not execute Step 12.

3. Uncheck the Drop Tables and Create New checkbox and click Next on Step 12 on page 88 of the browser-based installation.



4. Proceed normally through the screens for Installer Step 13 on page 89 through the rest of the Installer, and complete the rest of the tasks in Chapter 3, “Installing ECXpert and TradingXpert.”

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

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.

a. If using SNMP, copy the entire CONFIG file back to the new BDGHOME/SNMP/config/ directory.

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

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.

Upgrading on Windows


Remove Saved FilesIf 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 WindowsComplete the tasks described in this section to upgrade your ECXpert installation on Windows.

• “Shut Down ECXpert Services”

• “Database Upgrade” on page 172

• “Back Up Your Database” on page 174

• “Back Up LDAP Data” on page 176

• “Back up ECX Files” on page 176

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.



• “Upgrade to Current ECXpert” on page 177

• “Remove Saved Files” on page 178

Shut Down ECXpert ServicesIf 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:

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.

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.



6. Shut down the Sun™ ONE Web Server:

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_nameC:\> ./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.

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.

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.

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 UpgradeComplete the tasks described in this section to upgrade to Oracle 9i. This involves the following:

• Upgrading to Oracle 9i

• Checking your database connectivity

• Backing up your existing ECX database

• Backing up LDAP data

Upgrade to Oracle 9iIf you have not already done so, you need to upgrade to 9i, Enterprise Edition. See “Preinstallation Tasks” on page 39 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 ConnectivitySet 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 on page 66, for the correct values.

2. Modify environment variable definitions as necessary.

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.

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.

Likely locations for your tnsnames.ora file include:

❍ ORACLE_HOME\network\admin

❍ The directory specified by the TNS_ADMIN environment variable

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



5. Connect to the database.

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.



SQL> exit



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.


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





4. From the Windows NT Command window, enter the following command to run exp_ecx_tables.sh:

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 - ProductionPL/SQL Release 8.0.4.0.0 - ProductionExport done in US7ASCII character set and US7ASCII NCHAR character setAbout 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 exportedExport terminated successfully without warnings.#



Back Up LDAP DataIf 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 FilesFollow 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


❍ 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 on page 86.


4. Click Skip on Step 12 on page 88 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” on page 73 up to and including Step 10 on page 86.


2. Uncheck the Drop Tables and Create New checkbox and click Next on Step 12 on page 88 of the Installer

3. Proceed normally through the screens for Installer Step 13 on page 89 through the rest of the Installer, and complete the rest of the tasks in Chapter 3, “Installing ECXpert and TradingXpert.”

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

4. Update the ECXpert tables.

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:


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.


a. If using SNMP, copy the entire CONFIG file back to the new BDGHOME\SNMP\config directory.

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

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



Remove Saved FilesIf 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.

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.


179

Appendix B

Reinstalling ECXpert

This appendix provides instructions on reinstalling ECXpert 3.6.3 over an existing installation of ECXpert 3.6.3. 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.

• “Reinstalling on Solaris” on page 180

• “Reinstalling on Windows” on page 186

The Reinstallation Process Reinstalling ECXpert 3.6.3 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:


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


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

• “Shut Down ECXpert Services” on page 180

• “Check Database Connectivity” on page 181

• “Back Up Your Existing ECXpert Database” on page 182

• “Back up ECXpert Files” on page 184

• “Reinstall ECXpert” on page 184

• “Remove the Previous Installation and Database Backup” on page 186

Shut Down ECXpert ServicesIf 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.

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


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


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.



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


Appendix B Reinstalling ECXpert 181

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.

Manually kill the process ID for Program.o.

Check Database Connectivity1. Check your tnsnames.ora file.

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


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





SQL> exit





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


1. Change to the BDGHOME/dbadmin/oracle directory.



4. Enter the following command to run exp_ecx_tables.sh.

# ./exp_ecx_tables.sh

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



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.

Export: Release 8.1.6.0.0 - Production on Fri Nov 3 16:21:34 2000(c) Copyright 2000 Oracle Corporation. All rights reserved.

Connected to: Oracle8i Release 8.1.6.0.0 - ProductionPL/SQL Release 8.0.4.0.0 - ProductionExport done in US7ASCII character set and US7ASCII NCHAR character setAbout 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 exportedExport terminated successfully without warnings.#



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


❍ outside both the current ECXpert version directory tree and any previous ECXpert installation’s directory tree.

❍ outside the /tmp 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 ECXpertAt this point you are ready to begin reinstalling ECXpert.

1. Begin to install the current ECXpert version, as described in Chapter 3, “Installing ECXpert and TradingXpert” on page 73. The current version also includes the server install of Partner Agent.

2. Proceed normally through the screens for the Installer up to and including Step 10 on page 86. Stop at Step 12 on page 88. Do not execute Step 12.

3. Uncheck the Drop Tables and Create New checkbox and click Next on Step 12 on page 88 of the Installer.



4. Proceed normally through the screens for Installer Step 13 on page 89 through the rest of the Installer, and complete the rest of the tasks in Chapter 3, “Installing ECXpert and TradingXpert” on page 73.

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


a. If using SNMP, copy the entire CONFIG file back to the new RBDGHOME/SNMP/config/ directory.

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

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

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

6. Re-establish SunONE Web Server security.

7. Restore live data from your full database backup.

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. In particular, be aware of the following two restrictions:

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


Reinstalling on Windows


Remove the Previous Installation and Database BackupIf 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 WindowsComplete the tasks in this section to reinstall ECXpert on Windows NT or Windows 2000.

• “Shut Down ECXpert Services” on page 186

• “Check Database Connectivity” on page 187

• “Back Up Your Existing ECXpert Database” on page 188

• “Back up ECXpert Files” on page 189

• “Reinstall ECXpert” on page 190

• “Remove the Previous Installation and Database Backup” on page 191

Shut Down ECXpert ServicesMake 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.3” on page 161.

➤ 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:

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.



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 ConnectivityThis 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


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






SQL> connect ECX36/ECX36@your_connect_stringSQL> exit





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


1. Change to the BDGHOME\dbadmin\oracle directory.



4. In the Windows NT Command window, enter the following command to run exp_ecx_tables.sh.

C:\> ./exp_ecx_tables.sh

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



Back up ECXpert Files

➤ To back up important files from your current ECXpert installation


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

❍ outside the \tmp 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

Export: Release 8.1.6.0.0 - Production on Fri Apr 5 16:21:34 2002(c) Copyright 2002 Oracle Corporation. All rights reserved.

Connected to: Oracle8i Release 8.1.6.0.0 - ProductionPL/SQL Release 8.0.4.0.0 - ProductionExport done in US7ASCII character set and US7ASCII NCHAR character setAbout 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 exportedExport terminated successfully without warnings.#



❍ 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 ECXpertAt 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 Chapter 3, “Installing ECXpert and TradingXpert” on page 73 up to and including Step 10 on page 86.

Stop at Step 12 on page 88. Do not execute Step 12.

2. Uncheck the Drop Tables and Create New checkbox and click Next in Step 12 on page 88 of the Installer.

3. Proceed normally through the screens for Installer Step 13 on page 89 through the rest of the Installer, and complete the rest of the tasks in Chapter 3, “Installing ECXpert and TradingXpert” on page 73.

❍ 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 “To configure Sun ONE Web Server files” on page 101 to reflect the changed location.


a. If using SNMP, copy the entire CONFIG file back to the new BDGHOME\SNMP\config\ directory.



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

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

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

5. Re-establish Sun ONE Web Server security.

6. Restore live data from your full database backup.

Remove the Previous Installation and Database BackupIf 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.

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.

193

Appendix C

Installing Oracle

This appendix describes the procedures required to install Oracle on Solaris™ and Windows. Read the section that describes the installation process for your platform.

• “Oracle Installation for Solaris”

• “Oracle Installation for Windows” on page 200

Oracle Installation for SolarisThis section describes how you install Oracle 8.1.7 on Solaris. This process includes the following tasks:

• “Configure Shared Memory and Semaphores” on page 194

• “Create the Oracle User” on page 195

• “Set Environment Variables” on page 196

• “Install Oracle 8.1.7” on page 198

• “Run the root.sh Script” on page 199

ECXpert Version 3.6.3 is certified to run with Oracle 8.1.7 Enterprise Server edition (also known as Oracle 8i). If you have an earlier installed version of Oracle, refer to the Oracle 8.1.7 Installation documentation or contact Oracle for instructions on upgrading to version 8.1.7. Once you have upgraded to 8.1.7, continue with the section “Create the Oracle User” on page 195.

Oracle Installation for Solaris


Configure Shared Memory and SemaphoresBefore you install Oracle 8.1.7, you must edit the /etc/system file to properly configure shared memory and semaphores.

The values for shared memory and semaphores given below are the recommended minimum values from Oracle. They are intentionally low. If you set your shared memory parameters too high for your system, you might not be able to reboot your machine. Refer to your operating system documentation for parameter limits.

➤ To configure shared memory and semaphores

1. Log in as, or become, the root user:

# su - root

2. Change to the /etc directory

# cd /etc

3. Create a backup copy of your system file:

# cp system system.backup

4. Carefully edit the system file to append the following lines to the end of your file. Insert these lines immediately following the comments regarding “set.”

NOTE The instructions and guidelines that follow and the previous information on sizing your tablespace and rollback segment might not fit your production environment. Consult your Oracle dba or equivalent Database Administrator to verify that the suggested settings apply to your environment.

set shmsys: shminfo_shmmax = 134217728set shmsys: shminfo_shmmin = 1set shmsys: shminfo_shmmni = 100 set shmsys: shminfo_shmseg = 50 set semsys: seminfo_semmns = 1750set semsys: seminfo_semmni = 70set semsys: seminfo_semmsl = 200 set semsys: seminfo_semmap = 100set semsys: seminfo_semmnu = 300set semsys: seminfo_semume = 100set semsys: seminfo_semopm = 100


Appendix C Installing Oracle 195

5. Reboot your machine.

For the changes to take effect, you must reboot your machine using the following two commands:

# sync

# init 6

Create the Oracle UserThe next step is to create an Oracle user on Solaris. If you want to set up Oracle in a remote client configuration you must create an oracle user ID on each machine.

➤ To create an Oracle user

1. Log on as or become the root user:

# su - root

2. Create the dba group if the machine you are using does not already have one.

# groupadd dba

3. Create a home directory for the Oracle user using a command like the following:

# mkdir /disk1/oracle

where /disk1/oracle is the oracle user’s UNIX home directory.

4. Add the oracle user. For example:

# useradd -g dba -d /disk1/oracle -s /bin/csh oracle

5. Transfer ownership of the oracle user’s home directory. For example:

# chown oracle /disk1/oracle

6. Change the group association of the oracle user’s home directory:

# chgrp dba /disk1/oracle

7. Set the oracle user’s password; typically this is set to oracle. In the example below, password is the new password for the oracle user.

# passwd oracleNew password: passwordRe-enter new password: password



Set Environment VariablesYou must set the variables described in this section to set up the environment for installation. These variables are defined in the Oracle user’s .profile or .login file.

➤ To set environment variables

1. Log on as or become user Oracle:

# su - oracle

2. Set up the environment for the installation.

Use the following syntax to set the environment variables:

For the C shell:

setenv variable_name value

For the Bourne shell:

set variable_name value

export variable_name

Use the information in Table C-1 to determine how to set up each environment variable.

Table C-1 Environment Variables

Environment Variable Configuration Details

DISPLAY Set to the name and monitor of the machine from which you are installing the Oracle software.

Example: myhost:0.0

LD_LIBRARY_PATH Set to include $ORACLE_HOME/lib and the directory containing your Motif libraries.

Important: When you set up your environment prior to installing or upgrading, make sure that the $ORACLE_HOME/lib directory appears as the first value in the $LD_LIBRARY_PATH environment variable. If you do not do this, you will get errors when you later use SQL*Plus.

Note: The default location for Motif libraries on Solaris 2.x is /usr/openwin/lib or /usr/dt/lib.

ORACLE_BASE Set to the directory at the top of the Oracle software.

Example: /export2/oracle8i/app/oracle



ORACLE_HOME Set to the directory containing the Oracle software for a given Oracle Server release. The OFA-recommended value is:

$ORACLE_BASE/product/release

Example: /export2/oracle8i/app/oracle/product/8i

Important: Write this value in Table 2-8 on page 66.

ORACLE_SID Set to the Oracle SID, which is the name of the Oracle Server instance.

Note: If you are installing Oracle as a remote client, set this value to the database on the server machine.

Example: myHost

Important: Write this value in item 10 of the Configuration Worksheet on Table 2-8 on page 66.

ORACLE_TERM Set to the terminal definition resource file to be used with the Installer. Refer to your Oracle documentation for a complete list of terminal definition resource files.

Example: xterm

NLS_LANG Set to the correct NLS_LANG character set. The character set name is case sensitive. The character set is named according to the following convention:

<language>_<territory>.<number>

To determine the Oracle database character set, you need to be able to see the table V$NLS_PARAMETERS. Typically, only the users system or manager can see this table.

Use the following SQL statement to check the character set language:

select * from V$NLS_PARAMETERS where parameter = ‘NLS_LANGUAGE’

Use the following SQL statement to check the character set territory:

select * from V$NLS_PARAMETERS where parameter = ‘NLS_TERRITORY’

Use the following SQL statement to check the character set number:

select * from V$NLS_PARAMETERS where parameter = ‘NLS_CHARACTERSET’

Example: For Oracle 8.1.7: american_america.US7ASCII

For Oracle 9i on Windows: AMERICAN_AMERICA.WE8MSWIN1252

For Oracle 9i on Solaris: AMERICAN_AMERICA.WE8ISO8859P1

Important: Enter this value in Table 2-8 on page 66.

Table C-1 Environment Variables (Continued)




Install Oracle 8.1.71. Log on as or become the oracle user. You must be logged in as user oracle; do

not run the Installer as root user.

# su - oracle

oratab Create an oratab file as follows:

Example:

#cd /var

where $ORACLE_HOME is the $ORACLE_HOME of the new Oracle 8i, release 8.1.6 or 8.1.7 installation.

Note: This environment variable must be properly set if you plan to use a non-US7ASCII character set.

PATH Set to include:

• $ORACLE_HOME/bin

• /bin

• /usr/bin

• /usr/ccs/bin

Example: /export2/oracle8i/app/oracle/product/8.1.6/ bin:/bin:/usr/bin:/usr/ccs/bin:$PATH

TNS_ADMIN Set this as follows:

TNS_ADMIN = $ORACLE_HOME/network/admin

TERM Set this to the same value as the ORACLE_TERM environment variable.

Example: xterm

USER Set this to the oracle user.

Example: oracle

Table C-1 Environment Variables (Continued)




2. Run the Oracle Universal Installer.

Insert your Oracle8i, release 8.1.7 CD-Rom in the CD drive

Change to the CD installation directory:

# cd /cdrom/oracle8i/

To start the installer, enter the following command:

# ./setup

The Oracle Universal Installer will lead you through the Oracle installation process. The typical installation type option will suffice for most installations. When asked about installing the Multi-threaded Server option (MTS), accept installation using that option. Other custom installation options should be handled by an experienced Oracle database administrator.

During installation, you will be prompted for some of the environment variables set according to the guidelines presented in Table C-1 on page 196. You will also be instructed to open another terminal window and log in as root to run the root.sh script.

Run the root.sh Script1. Log on as or become the root user.

# su root

2. Change to the ORACLE_HOME/orainst directory:

# cd $ORACLE_HOME/orainst

3. Run the root.sh script:

# ./root.sh

If you run root.sh from a directory other than ORACLE_HOME, you get the following message:

ORACLE_HOME does not match the home directory for oracle.Okay to continue? [N]:

If you indicate Yes, the root.sh script continues, using the ORACLE_HOME environment variable you specified.

Depending on the products you installed, you may be prompted for user names and may be given further instructions. Refer to your Oracle documentation for more information on these messages.

Oracle Installation for Windows


4. Return to “Oracle on Solaris” on page 47 to complete database configuration and testing before installing ECXpert.

Oracle Installation for WindowsThis section describes how you install Oracle 8.1.7 on Windows. This process includes the following tasks:

• “Create the Oracle User” on page 200

• “Install Oracle 8.1.7” on page 202

On the Windows platform, environment variables that relate to Oracle are automatically set during installation.

ECXpert Version 3.6.3 is certified to run with Oracle 8.1.7 Enterprise Server edition (also known as Oracle 8i). If you have an earlier installed version of Oracle, refer to the Oracle 8.1.7 Installation documentation or contact Oracle for instructions on upgrading to version 8.1.7. Once you have upgraded to 8.1.7, continue with the section “Create the Oracle User” on page 200.

Create the Oracle User 1. From the Windows task bar, select Start > Programs > Oracle > Extended

Administration > Enterprise Security Manager.

2. Fill in the Login Information dialog box with the following values:

NOTE The message

Please raise the ORACLE owner’s ulimit per the IUG.

is purely informational and does not require action.

NOTE The instructions and guidelines that follow and information on sizing your tablespace and rollback segment might not fit your production environment. Consult your Oracle dba or equivalent Database Administrator to verify that the suggested settings apply to your environment.



3. Click OK. The Oracle Security Manager window appears.

4. In the Oracle Security Manager, select User > Create to display the Create User dialog box.

5. Fill in the Create User dialog box with the following values:

6. Click the Roles/Privileges tab. From the Privilege Type dropdown list, select Roles.

7. From the Available list box, select Connect and Resource.

8. Click the down arrow icon to move Connect and Resource to the Granted list.

9. Click Create to create the user ORACLE.

10. In the Oracle Security Manager window, select File > Exit to quit.

Table C-2 Login Information Values for the Oracle User Account

Field Value

Username system

Password manager

Service (leave blank)

Connect As Normal

Table C-3 Values for the Create User Dialog Box

Field Value

Name ORACLE (all capitals)

Profile DEFAULT

Enter Password ORACLE (all capitals)

Confirm Password ORACLE (all capitals)

NOTE The default tablespace is USER_DATA, and the default temporary tablespace is TEMPORARY_DATA. You can use different tablespaces if you want to.



Install Oracle 8.1.7The Oracle Universal Installer will lead you through the Oracle installation process. The typical installation option will suffice for most installations. When asked about installing the Multi-threaded Server option (MTS), accept that option. Other custom installation options should be handled by an experienced Oracle DBA. The typical installation option requires approximately 1.3Gb of disk space.

Depending on which installation options you choose, the Oracle installation can take a considerable amount of time to complete.

1. Insert your Oracle8i, release 8.1.7 CD-ROM in the CD drive.

2. Change to the CD installation directory:

# cd C:\> \cdrom\oracle8i\

3. To start the installer, double click the file setup.exe. You will see the Oracle splash screen, illustrated in Figure C-1.

NOTE If you want to set up Oracle in a remote client configuration you must create an oracle user ID on each machine.



Figure C-1 Oracle Installation Splash Screen

4. Click Next. You will see the File Locations screen, as shown in Figure C-2.



Figure C-2 File Locations Screen

5. In the Destination Name field, enter the name that will be used to represent the full path to your Oracle installation. This name is used as the ORACLE_HOME environment variable.

6. In the Destination Path field, enter the full path on which you want the Oracle distribution to be located.

7. Click Next. You will see the Available Products screen, illustrated in Figure C-3.



Figure C-3 Available Products Screen

8. Click the radio buttons for the product(s) you want to install.

9. Click Next. You will see the Installation Types screen, illustrated in Figure C-4.



Figure C-4 Installation Types Screen

10. Unless your site has special requirements you should select the Typical installation.

Click the radio button for Typical.

11. Click Next. You will see the Database Identification screen, illustrated in Figure C-5.



Figure C-5 Database Identification Screen

12. In the Global Database Name field, enter the name you want to use to identify this Oracle database.

13. The SID field is automatically populated with whatever you entered in the Global Database Name field. However, if you want to use a different Oracle system identifier, enter the name you want to use.

14. Click Next. You will see the Installer Summary screen, as illustrated in Figure C-6.



Figure C-6 Installer Summary Screen

15. Review the installation summary to make sure all the settings are correct.

If you find something you need to change, click the Previous button as many times as you need to in order to get to the screen where you can fix the incorrect entry. Then click Next until you come back to the installation summary screen.

16. When you are satisfied that all the settings are correct, click Install. This launches the actual installation process. The Install screen is displayed, as illustrated in Figure C-7.



Figure C-7 Install Screen

17. The installation process takes considerable time to complete. If no errors occur, the installation process completes and displays the Configuration Tools screen, illustrated in Figure C-8.



Figure C-8 Configuration Tools Screen

18. If you do not want any of displayed tools to be started at the present time, click that tool and click Stop.

If a tool that you would like to be automatically started has encountered some sort of problem launching, click that tool and click Retry.

19. Click Next. The End of Installation screen is displayed, as illustrated in Figure C-9.



Figure C-9 End of Installation Screen

20. If you want to install other Oracle products click Next Install.

If you want to view a list of currently installed products click Installed Products.

If you want to exit the installation program click Exit.

21. When you click Exit the Oracle Database Configuration Assistant Alert screen is displayed, as illustrated in Figure C-10.



Figure C-10 Oracle Database Configuration Assistant Alert Screen

22. Click OK.

23. Return to “Oracle on Solaris” on page 47 to complete database configuration and testing before installing ECXpert.

213

Appendix D

Installing Solaris Patches

Depending on the version of Solaris™ you are using, you must apply different Solaris patches. Solaris patches are available from Sun Microsystems’ SunSolve home page:

http://sunsolve.sun.com/

The following sections contain specific URLs where you can download the particular patches you must apply to the different versions of Solaris.

Begin by reading the section “Determining Which Patches to Use.” Then read the section that describes the patches of interest.

• “Solaris 2.6 Patches” on page 214



Determining Which Patches to UseTo find out what operating system patches have been applied to your system, use the following command:

# showrev -p

If you see the following output, patches have been applied which enable the ECXpert Java™ user interface to function properly.

http://sunsolve.sun.com/

Solaris 2.6 Patches


If you see the following output, it means that no patches at all have been applied:

Solaris 2.6 PatchesIf you are using Solaris 2.6, apply the patches shown in Table D-1. Refer to the following README file link for more information on the patch cluster that includes these patch IDs.

http://sunsolve.Sun.COM/pub-cgi/retrieve.pl?doctype=patch&doc=2.6_Recommended.README

You may instead choose to apply the latest Solaris recommended patch cluster for Solaris 2.6. The Solaris recommended patch cluster is updated every 15 days, so it will be a later version than the Sun-recommended patch cluster and will not have been tested with ECXpert.

Download the latest Solaris recommended 2.6 patch cluster from:

ftp://sunsolve.Sun.COM/pub/patches/2.6_Recommended.tar.Z

Refer to the following README file for instructions on applying this patch cluster:

ftp://sunsolve.Sun.COM/pub/patches/2.6_Recommended.README

# showrev -pPatch: 103663-08 Obsoletes: 103683-01, Requires:, Incompatibles:, iss_sparc-01 Packages: SUNWcsu, SUNWcsr, SUNWheaPatch: 103594-10 Obsoletes: , Requires:, 103663-01, Incompatibles: Packages: SUNWcsuPatch: 103680-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWcsuPatch: 103686-02 Obsoletes: , Requires:, 103663-01, Incompatibles: Packages: SUNWnisu

# showrev -pshowrev: opendir

http://sunsolve.Sun.COM/pub-cgi/retrieve.pl?doctype=patch&doc=2.6_Recommended.README

ftp://sunsolve.Sun.COM/pub/patches/2.6_Recommended.tar.Z

ftp://sunsolve.Sun.COM/pub/patches/2.6_Recommended.README

Solaris 2.7 Patches

Appendix D Installing Solaris Patches 215

Solaris 2.7 PatchesIf you are using Solaris 2.7, apply the patches shown in Table D-2: Refer to the following file link for each base patch ID on the http://sunsolve.Sun.COM site (e.g., 106980, 107636, and so forth). Alternatively, you can search for the patch ID using the Search SunSolve text entry box.

Table D-1 Solaris Version 2.6 (OS 5.6) Patches

Patch ID Note Description

105490-07 required Linker Patch

105568-16 required Libthread Patch

105210-27 required LibC Patch

106040-13 required X Input and Output Method Patch

105633-36 required (1) Open Windows 3.6 Xsun Patch

106409-01 required (2) Fixes the Chinese True Type Fonts

108091-03 required (3) SunOS 5.6: ssJDK1.2.1_03 fails with fatal error in ISO8859-01 Locales.

105181-19 recommended Kernal Update (socket close/hang)

105669-10 recommended CDE 1.2 libDTSvc Patch (dtmail)

105284-31 recommended Motif 1.2.7 Runtime Library Patch



106980-10 required Libthread Patch

107636-03 required X Input and Output Method Patch

107081-11 required Motif 1.2.7 and 2.1.1: Runtime Library Patch for Solaris 7.

108376-03 required Open Windows 3.6.1 Xsun Patch

http://sunsolve.Sun.COM

Solaris 2.8 Patches


Solaris 2.8 PatchesIf you are using Solaris 2.8, apply the patches shown in Table D-3:

Download the latest recommended Solaris 2.8 patch cluster from:

http://java.sun.com/j2se/1.3/install-solaris-patches.html#2.8

To find out which, if any, patch cluster has been applied to your machine, use either of the following commands:



108652-33 or later

required

108921-12 or later

required Fixes spurious FOCUS_LOST and FOCUS_GAINED events.

108940-24 or later

required Fixes problem that in some situations results in core dumps.

showrevuname -a

http://java.sun.com/j2se/1.3/install-solaris-patches.html#2.8

Solaris 2.8 Patches

Appendix D Installing Solaris Patches 217

If the patch cluster has been applied, the showrev command produces output similar to the following:

If the patch cluster has been applied, the following command

uname - a command

produces output similar to the following:

# showrevHostname: myhostHostid: 80859468Release: 5.6Kernel architecture: sun4uApplication architecture: sparcHardware provider: Sun_MicrosystemsDomain: myserver.comKernel version: SunOS 5.6 Generic 105490-07 September 2000

# uname -aSunOS myhost 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-1

Solaris 2.8 Patches


219

Index

Aadd web server 60Admin Password 97Admin UserID 96AIAG feature 109AIAG Web Server Instance 70, 93AIAG_setup.sh script 109american_america.US7ASCII 87AMERICAN_AMERICA.WE8ISO8859P1 87AMERICAN_AMERICA.WE8MSWIN1252 87Application Server 71

Admin password 71Admin UseID 71installing and configuring 61Port of Admin Server 71relation to TradingXpert 26TradingXpert installer dependencies 29TradingXpert installer, and 30

Application Server Home 96Application Server home 70Application Server Host Name 98Application Server Port 97AS2

HHTP Proxt Host 70Host Name of Oracle Server 70HTTP Proxy Port 70Keystore Password 70Keystore Path 70Server Port 70Web Server Instance 70

AS2 Sender and Receiver values 92

AS2 Server Port 90AS2 Web Server Instance 90

BB2B Sender 67, 84BDGHOME variable 20, 104

setting on Solaris 103setting on Windows 105

Ccommunication agents 24configuration

TCP 136TradingXpert with ECXpert 26

cshrc file 104

Ddata transformation 25Database password 87Database user 87dependencies

about 25Application Server 26, 29

Section E


ECXpert 25, 29for TradingXpert installer 29Oracle 25product support matrix 25, 26web server 26, 29

directory structureof ECXpert 31of TradingXpert 33

directory variable, TX_HOME 20disk space

computing required 41Solaris 42Windows 43

DISPLAY variable 196Domain Name 82Drop Tables and Create New 88

EebRoor 83EBROOT variable 66ebXML B2B user 67ECX36 user (Solaris) 48, 53ECXpert 48

AIAG feature 109communication agents 24configuration with TradingXpert 26data storage in 46data transformation 25destination directory 66directory structure 31environment variables 103, 104install directory 66installation worksheet 66platform requirements 40product support matrix 25, 26reinstalling 179relation to TradingXpert 25SDK 31tablespace size 48testing on Solaris 115testing on Windows 117, 118TradingXpert installer dependencies 29

upgrading on Solaris 161upgrading on Windows 170upgrading to 3.6.3 37user accounts, See user accounts

ECXpert administration servershutting down (Solaris) 162shutting down (Windows) 171starting on Windows 106testing on Solaris 115testing on Windows 117

ECXpert Oracle User 87environment file 104, 163, 165environment variables

BDGHOME 20, 103, 104ECXpert 103NSBASE 104Oracle 196

Ffiles

backing up ECXpert (Solaris) 168backing up ECXpert (Windows) 176cshrc 104environment 104, 163, 165listener.ora 166, 174, 181, 188root.sh 199shrc 104tnsnames.ora 166, 174, 181, 188

FTP serverinstalling on Windows 117

GGroupID 82

Hhardware requirements

Solaris 40

Section I

Index 221

Windows 41Host Name 82HTTP Proxy Host 91HTTP Proxy Port 91

IinitECX.ora file (Solaris) 48initECX.ora file (Windows) 53install directory 66installation worksheet 66installer

dependencies 28download options 28installation worksheet 66installed directory structure 31starting 74tasks performed by 28

Instance in Server 96IP Address 82

JJava Runtime Environment 81JRE 81

KKeystore Password 91Keystore Path 90

LLD_LIBRARY_PATH variable 196LDAP 57LDAP server

backing up (Solaris) 167backing up (Windows) 176host 57installing and configuring 57introduced 24port for 58restarting on Solaris 58restarting on Windows 58use for 46

LDAP_PASSWORD variable 57LDAP_USER variable 57listener.ora file 166, 174, 181, 188

Mmagnus.conf file 29Mail Host 69, 89Mail Spool 89mail spool file 69Messaging Server Host Name 71, 97Messaging Server Instance Home 71, 97Messaging Server Port 71, 98migrating, from 3.6.2 161multi-threaded server (MTS) 47

NNLS _LANG character set 68, 87NLS Language 87NLS_LANG variable 197NSBASE variable 104

setting on Windows 105

Oobject.conf file 29Oracle

backing up (Solaris) 166

Section P


backing up (Windows) 174database connectivity (Solaris) 49ECXpert user 69, 87ECXpert user account (Solaris) 48, 53initECX.ora file (Solaris) 48installation decisions 200multi-threaded-server support 47password 69, 87post-installation tasks on Solaris 47reinstalling (Solaris) 182reinstalling (Windows) 188relation to TradingXpert 25requirement for 24Server 69, 87SID 68SQL*Net connect string 69, 87SQL*Net TNS Alias 69, 87tablespace requirement 42tablespace, increasing (Solaris) 48tablespace, increasing (Windows) 52tnsnames.ora file (Solaris) 51upgrade decisions 200upgrading (Solaris) 163upgrading (Windows) 172user (Solaris) 195user (Windows) 200variables, setting (Solaris) 196

ORACLE_BASE variable 196ORACLE_HOME 86ORACLE_HOME variable 68, 86, 197ORACLE_SID variable 68, 87, 197ORACLE_TERM variable 197oratab file 198

PPartner Agent Server

Admin Port 85Agent daemon Port 85FTP daemon Port 85HTTP daemon Port 85HTTPS daemon Port 85

PAS Admin Port 67PAS Agentd Port 67

PAS FTPD Port 67PAS HTTPD Port 68PAS HTTPSD Port 68PATH variable 198POP3 89POP3 user 69post-installation tasks

configure MSOutlook 133enable auto-reboot 133enable SNMP support 133install Mercator 133install Netscape Messaging Server 133set up certificates 133tuning ECXpert 133

product requirements 59

Rreinstalling

database (Solaris) 182database (Windows) 188ECXpert 179

requirements 59root.sh script 199

SSecure Trading Agent

ebXML B2B user 67home path 66

semaphores 194SENDMAIL 89shared memory 194shrc file 104software dependencies, See dependenciessoftware modules

ECXpert 31TradingXpert 33

software requirementsSolaris 40

Section T

Index 223

Windows 41Solaris patches required

Solaris 2.6 214Solaris 2.7 215Solaris 2.8 216

SQL*Net Connect String 69, 87SQL*Net TNS Alias 69, 87STA Home Path 83STA Login 84STA Password 84Sun ONE Messaging Server 64supported products and platforms 25, 26

TTCP configuration 136TCP/IP

connectivity 43Solaris 44Windows 45

TERM variable 198Testing TradingXpert

test scenario 135testing TradingXpert

running the test scenario 154setting up ECXpert

importing data 150manually 136

TNS_ADMIN variable 198tnsnames.ora file 166, 174, 181, 188tnsnames.ora file (Solaris) 51, 54TradingXpert

Application Server home 70TX Instance Port Number 71, 98TX_HOME directory variable 20

Uuser accounts

ebXML user 66

ECX36 (Solaris) 48, 53ECXpert user 66introduced 36Oracle (Solaris) 48, 53, 195Oracle (Windows) 200Solaris 36

USER variable 198UserID 82

Wweb server

adding 60creating AIAG listener 59creating AS2 listener 59ECXpert use of 25installing 59location 66name and password for 66relation to TradingXpert 26TradingXpert installer dependencies 29

Web Server ROOTAIAG listener 93AIAG web server 70AS2 listener 90AS2 web server 69

WebMail 97Application Server Host Name 71Messaging Server Host Name 71Messaging Server Instance Home 71Messaging Server Port 71TX Instance Port Number 71

Section W
