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



Chapter 4   Testing Your TradingXpert Installation

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

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

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:

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



Note

Be sure to copy the required map files to BDGHOME/maps. See "Copying TradingXpert Map Files to ECXpert" for the Solaris platform and "Copying TradingXpert Map Files to ECXpert" for the Windows platform.



Setting up ECXpert Manually

To set up the necessary memberships, service lists, and partnerships for the test scenario manually, rather than import them (see "Importing/Deleting Setup Data"), you perform the following steps:

To set up ECXpert manually

  1. Set up memberships for TXhost and webuser1.
    1. TXhost with EDI trading address of ZZ:TXhost.
    2. webuser1 with EDI trading address of ZZ:webuser1.

  2. Set up a service list and partnership for the following exchanges:
  3. 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 webuser1

This section explains how to set up the service list and partnership needed for TXhost to send purchase orders to webuser1.

Service List Setup A

This 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 4-1 and the accompanying Table 4-1 show how to set up a service list for this exchange.

Figure 4-1    Service List Screen for TXhost Sending Purchase Order to webuser1

Table 4-1    Service List details for TXhost Sending Purchase Order to webuser1 

Field

Value

Explanation

Service List Details

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.

Partnership Setup A

The partnership setup includes a number of screens corresponding to the different tabs required to configure the partnership.

Partnership Info    Figure 4-2 and the accompanying Table 4-2 show how to set up the Partnership Info tab for this exchange.

Figure 4-2    Partnership Info for TXhost Sending Purchase Order to webuser1

Table 4-2    Partnership Information for TXhost Sending Purchase Order to webuser1 

Field

Value

Explanation

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)
or
850html.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.

Input EDI    Figure 4-3 and the accompanying Table 4-3 show how to set up the Input EDI tab for this exchange.

Figure 4-3    Input EDI for TXhost Sending Purchase Order to webuser1

Table 4-3    Input EDI Information for TXhost Sending Purchase Order to webuser1

Field

Value

Explanation

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.

Protocols    Figure 4-4 and the accompanying Table 4-4 show how to set up the Protocols tab for this exchange.

Figure 4-4    Protocols for TXhost Sending Purchase Order to webuser1

Table 4-4    Protocols for TXhost Sending Purchase Order to webuser1

Field

Value

Explanation

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 TXhost

This section explains how to set up the service list and partnership needed for webuser1 to send invoices to TXhost.

Service List Setup B

Figure 4-5 and the accompanying Table 4-5 show how to set up a service list for this exchange.

Figure 4-5    Service List for webuser1 Sending Invoices to TXhost

Table 4-5    Service List details for webuser1 Sending Invoices to TXhost  

Field

Value

Explanation

Service List Details

Service List Data Type

EDI

Indicates the type of document being serviced

Sending Member ID

webuser1

Applies to browser-based ECXpert partner

Receiving Member ID

*

Applies to any receiving member

Select Service to add to List

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)

Partnership Setup B

The partnership setup includes a number of screens corresponding to the different tabs required to configure the partnership.

Partnership Info    Figure 4-6 and the accompanying Table 4-6 show how to set up the Partnership Info tab for this exchange.

Figure 4-6    Partnership Info for webuser1 Sending Invoices to TXhost

Table 4-6    Partnership Information for webuser1 Sending Invoices to TXhost

Field

Value

Explanation

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)
or
html810.mmc (Windows)

The map file used to convert TradingXpert format to outbound 810 documents (Application to EDI)

Incoming SMTP

[Parameters]

Default

Not needed for this document exchange.

Input HREC    Figure 4-7 and the accompanying Table 4-7 show how to set up the Input HEC tab for this exchange.

Figure 4-7    Input HREC for webuser1 Sending Invoices to TXhost

Table 4-7    Input HREC for webuser1 Sending Invoices to TXhost

Field

Value

Explanation

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

Output EDI    Figure 4-8 and the accompanying Table 4-8 show how to set up the Output EDI tab for this exchange.

Figure 4-8    Output EDI for webuser1 Sending Invoices to TXhost

Table 4-8    Output EDI for webuser1 Sending Invoices to TXhost

Field

Value

Explanation

Enveloping Options

EDI Envelope

ECXpert generates (or overrides) entire envelope

Standard

ANSI

[Remaining parameters]

Default

Not needed for this document exchange.

Protocols    Figure 4-9 and the accompanying Table 4-9 show how to set up the Protocols tab for this exchange.

Figure 4-9    Protocols for webuser1 Sending Invoices to TXhost

Table 4-9    Protocols for webuser1 Sending Invoices to TXhost

Field

Value

Explanation

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

[Remaining parameters]

Default

Not needed for this document exchange.



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.



Exchange C: webuser1 Sends File Attachment to TXhost

This section explains how to set up the service list and partnership needed for webuser1 to send file attachments to TXhost.

Service List Setup C

Figure 4-10 and the accompanying Table 4-10 show how to set up a service list for this exchange.

Figure 4-10    Service List for webuser1 Sending Attachments to TXhost

Table 4-10    Service List details for webuser1 Sending Attachments to TXhost  

Field

Value

Explanation

Service List Details

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

Select Service to add to List

OutPrep

Marks files that do not need processing as ready for the Gateway service.

Gateway

Uses Gateway to send document to receiving member (TXhost)

Partnership Setup C

The partnership setup includes a number of screens corresponding to the different tabs required to configure the partnership.

Partnership Info    Figure 4-11 and the accompanying Table 4-11 show how to set up the Partnership Info tab for this exchange.

Figure 4-11    Partnership Info for webuser1 Sending Attachments to TXhost

Table 4-11    Partnership Information for webuser1 Sending Attachments to TXhost  

Field

Value

Explanation

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.

Map Name

No map file is needed.

Incoming SMTP

[Parameters]

Default

Not needed for this document exchange.

Protocols    Figure 4-12 and the accompanying Table 4-12 show how to set up the Protocols tab for this exchange.

Figure 4-12    Protocols for webuser1 Sending Attachments to TXhost

Table 4-12    Protocols for webuser1 Sending Attachments to TXhost

Field

Value

Explanation

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

The directory where the file will be deposited

Outbound Pattern

attachment

[Remaining parameters]

Default

Not needed for this document exchange.



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.



Importing/Deleting Setup Data

Rather than manually setting up ECXpert to support the TradingXpert test scenario, as detailed in "Setting up ECXpert Manually", you can import the memberships, service lists, and partnerships for the test scenario using the import files provided on your installation disk.



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



Importing Setup Data

You 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 Directory Structure").
  3. cd TX_HOME/maps_etc/import

  4. Make backup copies of the tx-mem.imp and del-tx-mem.imp files.
  5. Edit the tx-mem.imp and del-tx-mem.imp files.
  6. 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".

  7. Make sure BDGHOME is set to the location of the ECXpert installation (see Table 3) so that the application server will use the same ecx.ini file that ECXpert uses.
  8. 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.

  9. Make sure the application server can reference the BGDHOME/lib directory.
  10. 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

  11. Populate the database.
  12. 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.


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


Deleting Setup Data

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

Testing TradingXpert with the Test Scenario

This 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:
  2. 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 4-13) appears.

    Figure 4-13    ECXpert Home Page

  3. Click the Utilities button.
  4. The ECXpert Utilities Menu (Figure 4-14) appears.

    Figure 4-14    ECXpert Utilities Menu

  5. Click the Document Submission Form link.
  6. The Document Submission Form (Figure 4-15) appears.

    Figure 4-15    Document Submission Form

  7. Enter parameters for the submit command.
  8. Refer to Table 4-13 for detailed information about the parameters.

    Table 4-13    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

    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

  9. Click the Submit button.
  10. A message appears providing feedback on the command. If any errors are encountered they are displayed first.

  11. Optionally, view the tracking information for your submission.
    1. Log in to the ECXpert Product Administrative Interface.
    2. Click the Tracking button on the left.
    3. The Enter Search Constraints tab appears.

    4. Set Search Level to Document.
    5. Enter today's date.
    6. Click the Search button.

  12. Open the TradingXpert user interface by entering the following URL in your browser:
  13. 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 4-16) appears.

    Figure 4-16    TradingXpert Login Screen

  14. Log in to TradingXpert as webuser1.
  15. Use the User ID webuser1 and the Password webuser1 and click Login.

    The Trade Center Screen (Figure 4-17) appears.

    Figure 4-17    Trade Center Screen

  16. View the incoming purchase order.
    1. Click the Inbound icon to view incoming documents.
    2. The Inbound Documents Screen (Figure 4-18) appears.

    Figure 4-18    Inbound Documents Screen

    1. Search for all incoming documents from TXhost.
    2. Find the purchase order just sent from TXhost and click View.
    3. The Purchase Order Document (Figure 4-19) is displayed.

    Figure 4-19    Purchase Order Document

  17. Create an invoice from the purchase order.
  18. At the bottom of the purchase order, click the Create Invoice button.

    An invoice form (Figure 4-20) will appear; the data fields will be pre-filled with data from the purchase order.

    Figure 4-20    Attachment Options at Bottom of an Invoice

  19. Attach a file to the invoice.
  20. 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.

  21. Submit the invoice with attachment to TXhost by clicking the Submit Document button.
  22. A screen will appear confirming that the document was submitted successfully.

  23. Verify receipt of the invoice and attachment in ECXpert.
    1. Return to the ECXpert administration interface:
    2. 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.

    3. On the ECXpert home page (Figure 4-13), click Support.
    4. Enter the ECXpert administrator user name and password and click Enter.
    5. Click the Tracking button, then enter search constraints to find the 810 invoice document sent by webuser1 to TXhost.
    6. View tracking information for the inbound document and attached file.


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