Sun ONE logo    
Sun ONE Integration Server B2B, TradingXpert 3.6.2 Release Notes



Release Notes for Sun™ ONE Integration Server, B2B Edition (TradingXpert)

Version 3.6.2

Part Number 816-6724-10 

Updated April, 2003




These release notes contain important information available at the time of release of Version 3.6.2 of Sun™ Open Network Environment (Sun ONE) Integration Server, B2B Edition (TradingXpert). New features and enhancements, known limitations and problems, technical notes, and other information are addressed here. Read this document before you begin using TradingXpert 3.6.2.

The most up-to-date version of these release notes can be found at the Sun ONE documentation web site: http://docs.sun.com/db/coll/S1_IntegrationServer_B2B_362. Check the web site after installing your software, and then periodically thereafter, to view the most up-to-date version of these notes.

These release notes contain the following sections:

TradingXpert Documentation Updates

Some of the TradingXpert 3.6.2 documentation has been updated from Version 3.6.1 and 3.6.0 of the product. TradingXpert 3.6.2 documents can be found at the Sun ONE documentation web site: http://docs.sun.com/db/coll/S1_IntegrationServer_B2B_362.

Installation Guide

The TradingXpert 3.6.2 product includes an updated TradingXpert Installation Guide, available in both Acrobat (.pdf) and HTML formats. In addition, you can obtain an ASCII formatted version by contacting your technical support representative.

Administrator's and Developer's Handbook

The TradingXpert Administrator's and Developer's Handbook has not been updated in TradingXpert 3.6.2, and is available in Acrobat (.pdf) format. In addition, you can obtain an ASCII formatted version by contacting your technical support representative.

New in TradingXpert 3.6.2:
Support for Sun ONE Application Server 7.0

The TradingXpert 3.6.2 product includes all the features of earlier TradingXpert releases, and, in addition, is now also supported in a Sun ONE Application Server, Standard Edition, Version 7.0 environment.

If you have previously run TradingXpert in a Sun ONE Application Server 6.5 environment, and want to migrate to a Sun ONE Application Server 7.0 environment, you need to make changes in all custom HTML templates you are using. See "Migrating From an Application Server 6.5 Environment to Application Server 7.0".


Note

Sun ONE Application Server 7.0 is supported on Windows 2000 and XP (but not on Windows NT). However, TradingXpert has been tested and certified only for Application Server 7.0 on Windows 2000.

Where to Find Dependent Software Products

TradingXpert 3.6.2 has critical dependencies on a number of external software products, which can be found in the locations shown in the table below.

Table 1    TradingXpert 3.6.2 Dependent Software Locations

Dependent Product

Used For

Location

ECXpert 3.6.2

 

Dispatching and transforming documents and managing trading partnerships.

 

Sun ONE Integration Server, B2B Edition 3.6.2 CD-ROM distribution set. ECXpert 3.6.2 is located in the ECXpert3.6.2 directory of both the Solaris™ and Windows CD.

 

Oracle database

 

ECXpert dependency: Storing partnership and process tracking data.

 

Not provided by Sun ONE Integration Server, B2B Edition 3.6.2. Available from Oracle at http://www.oracle.com/.

 

Sun ONE Application Server, Enterprise Edition, 6.5 Environment

Sun ONE Web Server, Enterprise Edition 6.0 SP5

 

Accessing TradingXpert from a browser-based ECXpert trading member

 

Sun ONE Integration Server, B2B Edition 3.6.2 CD-ROM distribution set. Web Server 6.0 SP5 is located in the WebServer6.0SP5 directory of both the Solaris and Windows CD.

 

Sun ONE Application Server, Standard Edition 6.5 SP1

 

Application server support

 

This distribution can be obtained at the following download site:

http://wwws.sun.com/software/download/products/appsvr6.5sp1.htm

When prompted for your product key enter the following:

  • Solaris: 145835986-3948305918

  • Windows: 955802486-66921301
 

Sun ONE Application Server, Standard Edition, 7.0 Environment

Sun ONE Application Server, Standard Edition 7.0

 

Application server support and accessing TradingXpert from a browser-based ECXpert trading member.

 

Sun ONE Integration Server, B2B Edition 3.6.2 CD-ROM distribution set. Application Server 7.0 for both Solaris and Windows is located on the Sun ONE Application Server 7.0 CD.

 

Compatibility Issues

TradingXpert 3.6.2 is fully compatible with earlier TradingXpert versions. Upgrading from earlier versions requires you to make no changes, unless you are migrating to an Application Server 7.0 environment (see "New in TradingXpert 3.6.2: Support for Sun ONE Application Server 7.0").

TradingXpert 3.6.2 is fully compatible with TradingXpert 3.6.1 and earlier versions, unless it is installed in a Sun ONE Application Server 7.0 environment. In that case, the software is installed in a different location, and any previously customized forms will not only need to be copied to the new location, but will also need to be modified as described in "Migrating From an Application Server 6.5 Environment to Application Server 7.0".

TradingXpert 3.6.2 is also compatible with ECXpert 3.6.1 and earlier versions, and with their respective versions of Oracle database.

When upgrading an earlier version of TradingXpert to Version 3.6.2, you should first back up all customized files, install Version 3.6.2, and then place the customized files in their correct respective locations in the TradingXpert or ECXpert directory structure.


Note

On Solaris platforms, please ignore the update_exe file found at the following location on the Sun ONE Integration Server, B2B Edition 3.6.2 Solaris CD-ROM:

    /TradingXpert3.6.2/install-bits/TX_for_AppServer6.5/upgrade_exe

This is a legacy file that should not have been included in the distribution.

Open Bugs in TradingXpert 3.6.2

This section contains a listing of the more important bugs known at the time of the TradingXpert 3.6.2 release.

For a list of current bugs, their status, and workarounds, Java Developer Connection™ members should see the Bug Parade page on the Java Developer Connection web site. Please check that page before you report a new bug. Although not all TradingXpert bugs are listed here, it is a good starting place if you want to know whether a problem has been reported.

The relevant page is:

http://developer.java.sun.com/developer/index.html


Note

Java Developer Connection membership is free but does require registration for access. Details on how to become a Java Developer Connection member are provided on Sun's "For Developers" web page.

To report a new bug or submit a feature request, contact your customer service representative.

Table 2    Bug Descriptions 

Bug Number

Details

4828081

 

If TradingXpert, running in a Sun ONE Application Server 7.0 environment, submits a document to ECXpert, ECXpert cannot be restarted after it has been shut down.

Workaround: Before attempting to restart ECXpert, shut down the Application Server 7.0 instance used by TradingXpert. Restart ECXpert and then restart the application server instance.

 

Migrating From an Application Server 6.5 Environment to Application Server 7.0

If you have been running TradingXpert in an Application Server 6.5 environment and want to migrate to an Application Server 7.0 environment, you will have to modify any customized HTML templates in your TradingXpert system. The modifications replace the GX tags used in the Application Server 6.5 environment with the XSL instruction set required for the Application Server 7.0 environment.

In addition, the template file markup must consist of well-formed HTML. Normally, this requires you to also clean up badly-formed HTML markup to make it comply with the well-formed standards of the XSL instruction set.

The following paragraphs provide guidelines to cleaning up the HTML templates and to replacing GX tags with XSL instructions.

Cleaning up HTML

The following kinds of badly-formed HTML should be cleaned up:

  • All elements must be closed. (This is commonly an issue for:
    <input>, <meta>, <base>, <img>, <br>.)

    • For example

    <br> is replaced with <br/>

    <input type="text" name="var1">

    is replaced with

    <input type="text" name="var1"/>

  • Attribute names must be quoted and white space eliminated.

    • For example

    <input type=text name = var1/>

    is replaced with

    <input type="text" name="var1"/>

  • Entity declaration references must be defined appropriately

    • For example

    &nbsp; becomes &#160;

  • Element names are case sensitive. Make sure that closing element tags match opening element tags in case and name.

    • For example

    <b> some text </B> is replaced with <b> some text </b>

Replacing GX tags with XSL

Once templates have been cleaned up to conform to well-formed HTML, you need to convert GS tags to an XSL instruction set in all your customized HTML templates.

To migrate GX-tagged templates to XSL

  1. Add the following lines to the top of the template file.

    2. <?xml version="1.0"?>

    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

    <xsl:output method="html" />

    <xsl:template match="/TxTemplate">

  2. Add the following to the bottom of the template file.

    3. </xsl:template>

    </xsl:stylesheet>

  3. Map atomic variables to XSL.

    4. (Atomic variables represent source data in the input template.)

    1. Map atomic variables within attributes. (The general XSL format is:{variable_name}).

      2. Conversion example

      <BASE HREF="%gx type=cell id=BASEHREF%%/gx%">

      is replaced with

      <BASE HREF="{BASEHREF}"/>

    2. Map atomic variables that are stand-alone.

      3. (The general XSL format is: <xsl:value-of select="variable_name"/>).

      Conversion example

      %GX type=cell id=DocumentContent.BFR_1_3%%/GX%

      is replaced with

      <xsl:value-of select="DocumentContent/BIG_1_3"/>

  4. Map conditional variables to XSL.

    5. (Conditional variables depend on data in the input template. These are commonly used to provide expanded text for a set of input codes. For example, YR -> year, MN -> minute, etc.)

    The general XSL format is to:

    • declare a local variable to hold the 'key' value

    • create a list of conditional mappings for each key you want mapped

    Conversion example

    %GX type=cell id="compare.DocumentContent.B10_1_3&#FEDX&#Federal Express"%%/GX%

    %GX type=cell id="compare.DocumentContent.B10_1_3&#OVNT&#Overnight"%%/GX%

    %GX type=cell id="compare.DocumentContent.B10_1_3&#USPS&#US Postal Service"%%/GX% &#160;

    is replaced with

    <xsl:variable name="B103" select="DocumentContent/B10_1_3" />

    <xsl:choose>

    <xsl:when test="$B103='FEDX'"><xsl:text>Federal Express</xsl:text></xsl:when>

    <xsl:when test="$B103='OVNT'"><xsl:text>Overnight</xsl:text></xsl:when>

    <xsl:when test="$B103='USPS'"><xsl:text>US Postal Service</xsl:text></xsl:when>

    </xsl:choose>

  5. Map looping sequences to XSL.

    6. Loop sequences allow for the repetition of a set of values within a TradingXpert template.

    The following example represents PO Acknowledgment line item information that has been excerpted from a TradingXpert data file. (Note that the PO1 element loops twice (PO1_1, PO1_2.)

    PO1_1.BAK_1_2=AT
    PO1_1.PO1_1_2=1
    PO1_1.PO1_1_3=EA
    PO1_1.PO1_1_4=6629.48
    PO1_1.PO1_1_9=DTR-GD-12210-002
    PO1_1.PID_1_5=great stuff
    PO1_1.SCH_1_6=19990403
    PO1_1.AMT_1_2=6629.48
    PO1_2.BAK_1_2=RD
    PO1_2.PO1_1_2=10
    PO1_2.PO1_1_3=EA
    PO1_2.PO1_1_4=22.54
    PO1_2.PO1_1_9=no time
    PO1_2.PID_1_5=white paint
    PO1_2.SCH_1_6=19990404
    PO1_2.AMT_1_2=225.40

    The conversion of an HTML representation of this data to XSL is depicted below. Note that while the syntax is quite different in both cases, the structure of the HTML is very similar.

    Conversion example

    %GX type=tile id=PO1_loop%

    <tr align="right" valign="top">

    <td>%GX type=cell id=PO1_loop.rowid%%/GX%</td>

    <td>

    %GX type=cell id="compare.PO1_loop.BAK_1_2&#AT&#Accepted"%%/GX%

    %GX type=cell id="compare.PO1_loop.BAK_1_2&#RD&#Rejected"%%/GX%

    </td>

    <td>%GX type=cell id=PO1_loop.PO1_1_2%%/GX% </td>

    <td>%GX type=cell id=PO1_loop.PO1_1_3%%/GX% </td>

    <td>%GX type=cell id=PO1_loop.PO1_1_9%%/GX%</td>

    <td>%GX type=cell id=PO1_loop.PID_1_5%%/GX%</td>

    <td>%GX type=cell id=PO1_loop.PO1_1_4%%/GX%</td>

    <td>%GX type=cell id=PO1_loop.SCH_1_6%%/GX%</td>

    <td>%GX type=cell id=PO1_loop.AMT_1_2%%/GX%</td>

    </tr>

    %/GX%

    is replaced with

    <xsl:for-each select="DocumentContent/PO1_loop">

    <tr align="right" valign="top">

    <td>

    <xsl:value-of select="rowid"/></td>

    <td>

    <xsl:variable name="STATUS" select="BAK_1_2" />

    <xsl:choose>

    <xsl:when test="$STATUS='AT'"><xsl:text>Accepted</xsl:text></xsl:when>

    <xsl:when test="$STATUS='RD'"><xsl:text>Rejected</xsl:text></xsl:when>

    </xsl:choose>

    </td>

    <td><xsl:value-of select="PO1_1_2"/> </td>

    <td><xsl:value-of select="PO1_1_3"/> </td>

    <td><xsl:value-of select="PO1_1_9"/></td>

    <td><xsl:value-of select="PID_1_5"/></td>

    <td><xsl:value-of select="PO1_1_4"/></td>

    <td><xsl:value-of select="SCH_1_6"/></td>

    <td><xsl:value-of select="AMT_1_2"/></td>

    </tr>

    </xsl:for-each>

How to Report Problems

If you have a support contract and you have problems with TradingXpert, contact Sun ONE customer support using one of the following mechanisms:

  • Sun ONE online support web site at http://www.sun.com/service/sunone/software/index.html

    • This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.

  • The telephone dispatch number associated with your maintenance contract

So that we can best assist you in resolving problems, please have the following information available when you contact support:

  • Description of the problem, including the situation where the problem occurs and its impact on your operation

  • Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem

  • Detailed steps on the methods you have used to reproduce the problem

  • Any error logs or core dumps

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this address:

docfeedback@sun.com

Please include the part number (816-6724-10) of the document in the subject line and the book title (TradingXpert 3.6.2 Release Notes) in the body of your email.

For More Information

Beyond the TradingXpert documentation, you can find additional information as indicated below.

Discussion Forums

Sun ONE Software Forum

There is a TradingXpert forum available at the following location:

http://softwareforum.sun.com/NASApp/jive/forum.jsp?forum=76

Java Technology Forum

There is a JMS forum in the Java™ Technology Forums that might be of interest.

http://forum.java.sun.com

Sun ONE Information

Useful Sun ONE information can be found at the following Internet locations:

Copyright 2003 Sun Microsystems, Inc. All rights reserved.


Part Number 816-6724-10

Last Updated April 14, 2003