Nubridges Commerce Suite™ Getting Started Guide: Ersion

nuBridges Commerce Suite™
Getting Started Guide
Document Version 08.07
VERSION 3.4.1.1
© 2001-2007 nuBridges, Inc. All rights reserved.
Information in this document is subject to change without notice and does not represent a commitment on the
part of nuBridges. The documentation is provided “as is” without warranty of any kind including without
limitation, any warranty of merchantability or fitness for a particular purpose. Further, nuBridges does not
warrant, guarantee, or make any representations regarding the use, or the results of the use, of the software or
written material in terms of correctness, accuracy, reliability, or otherwise.
nuBridges is a trade name and registered trademark in the United States and other countries. The names of actual
companies and products mentioned herein may be the trademarks of their respective owners.
Table of Contents
Chapter 1: Introduction
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Introduction to the Commerce Suite Documentation Set . . . . . . . . . . . . . . 3
Commerce Suite Documentation Roadmap. . . . . . . . . . . . . . . . . . . . . . . . 4
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Introduction to AS2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
AS2 Communication Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Roadmap for Establishing nuBridges Connectivity . . . . . . . . . . . . . . . . . . 8
Typical Commerce Suite Administrator Duties . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2: Preparing to Install Commerce Suite

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Commerce Suite System Requirements - Windows . . . . . . . . . . . . . . . . 11
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Administrator Rights for Windows NT and 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Recommended Software for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Commerce Suite System Requirements - UNIX . . . . . . . . . . . . . . . . . . . 13
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Recommended Software for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
OS Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table of Contents, continued
Chapter 3: Commerce Suite Firewall Configuration Settings

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Commerce Suite Firewall Considerations . . . . . . . . . . . . . . . . . . . . . . . . 15
External Trading Partner Inbound Firewall Considerations . . . . . . . . . . . 16
External Trading Partner Outbound Firewall Considerations . . . . . . . . . . 17
Chapter 4: Licensing and Upgrading Commerce Suite

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
About License Key Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Licensing Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Upgrading Your Commerce Suite Software . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 5: Installing Commerce Suite

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Installing on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Installing on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing on IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installing on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Installing on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Uninstalling on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Java 2 Runtime Environment Installation Verification . . . . . . . . . . . . . . . 28
Chapter 6: Configuring Commerce Suite

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Commerce Suite Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Commerce Suite Manager System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Step 1 - Initializing Commerce Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
For UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
For Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Using an Existing Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Step 2 - Editing a Trading Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . 38
Step 3 - Configuring Your Inbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Chapter 6: Configuring Commerce Suite, continued

Step 4 - Configuring Your Outbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 5 - Creating Certificates and Keys . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Step 6 - Adding a New Trading Partner . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Step 7 - Saving the Commerce Suite Configuration File . . . . . . . . . . . . . 48
Step 8 - Reloading the Commerce Suite Configuration File. . . . . . . . . . . 48
Step 9 - Closing Commerce Suite Manager. . . . . . . . . . . . . . . . . . . . . . . 48
Step 10 - Testing Commerce Suite Connectivity . . . . . . . . . . . . . . . . . . . 49
Chapter 7: Testing Commerce Suite

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Testing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Testing Commerce Suite Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Step 1 - Accessing and Logging In to the Self-Test Web Site. . . . . . . . . . . . . . . . . . 53
Step 2 - Verifying the Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Step 3 - Uploading Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Step 4 - Receiving Test Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Error Code Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Step 5 - Sending Test Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter 8: Understanding Commerce Suite Files and Directories

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
About Commerce Suite Files and Directories . . . . . . . . . . . . . . . . . . . . . 63
Chapter 9: Post Installation Considerations

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Starting and Stopping Commerce Suite . . . . . . . . . . . . . . . . . . . . . . . . . . 65
For Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
For UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Starting Commerce Suite Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Stopping Commerce Suite Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Testing Trading Partner Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Editing AS2 Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 9: Post Installation Considerations, continued

Editing Your IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Editing Firewall Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Configuring for HTTPS or Secure FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configuring for AS1 or Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Monitoring the Commerce Suite Log File . . . . . . . . . . . . . . . . . . . . . . . . . 72
Running Commerce Suite Server as a Windows Service . . . . . . . . . . . . 74
Installing Commerce Suite as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Installing with a Specific Service Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Starting Commerce Suite as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Stopping Commerce Suite as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Running Commerce Suite in the Background on UNIX Systems . . . . . . . 76
Running Commerce Suite as a Daemon on UNIX Systems . . . . . . . . . . 77
Appendix A: Conducting Manual Commerce Suite Operations

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Starting and Stopping Commerce Suite . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Starting Commerce Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Stopping Commerce Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Checking Commerce Suite Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Understanding Configuration and Work Order Files . . . . . . . . . . . . . . . . 81
What is the icssvr.cfg Configuration File? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Rules for Editing the icssvr.cfg File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Editing the icssvr.cfg File Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
What are Work Order Files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Sending Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Performing One Time Sends. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Sending Data Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Introduction ...................................................................................................... 1
About This Document ...................................................................................... 1
Audience.......................................................................................................... 2
Introduction to the Commerce Suite Documentation Set................................. 3
Commerce Suite Documentation Roadmap .................................................... 4
Documentation Conventions............................................................................ 6
Introduction to AS2 .......................................................................................... 7
AS2 Communication Requirements................................................................. 8
Roadmap for Establishing nuBridges Connectivity .......................................... 8
Typical Commerce Suite Administrator Duties ................................................ 9
Introduction
Introduction
Welcome to the Commerce Suite Getting Started Guide. This guide describes the
nuBridges AS2 solution and how it benefits your Internet-based trading community.
This document also provides instructions for installing, configuring, and testing
Commerce Suite with nuBridges to enable connectivity between your enterprise and
nuBridges.
About This Document

The Commerce Suite Getting Started Guide contains the following chapters:
• Chapter 1: Introduction describes the nuBridges AS2 solution and explains how
it will benefit and simplify the exchange of EDI data.
• Chapter 2: Preparing to Install Commerce Suite describes the system
requirements necessary for installing and running Commerce Suite.
• Chapter 3: Commerce Suite Firewall Configuration Considerations provides
the necessary guidelines to facilitate configuration of your firewall for use with
the Commerce Suite application.
• Chapter 4: Licensing and Upgrading Commerce Suite describes nuBridges
licensing and how to upgrade your existing copy of Commerce Suite .
• Chapter 5: Installing Commerce Suite describes how to install Commerce
Suite on Windows and UNIX operating systems.
• Chapter 6: Configuring Commerce Suite describes how to install and configure
the Commerce Suite application.
• Chapter 7: Testing Commerce Suite describes how to test your Commerce
Suite connectivity with nuBridges.
• Chapter 8: Understanding Commerce Suite Files and Directories describes the
Commerce Suite directory structure and explains the different types of files that
will populate each subdirectory.
• Chapter 9: Post Installation Considerations describes some of the tasks you
may need to perform after installing and testing Commerce Suite.
• Appendix A: Conducting Manual Commerce Suite Operations describes how to
perform basic Commerce Suite tasks using a DOS command prompt.
1
Audience
Audience
This guide is intended primarily for use by nuBridges Commerce Suite data
administration personnel responsible for installation, configuration, maintenance, and
use of the Commerce Suite system.
This document has been written with the assumption that nuBridges Commerce Suite
administrators and users have a general understanding of the following concepts and
technologies:
• Your business application software and business practices

• Electronic Data Interchange over the Internet (EDI-INT)
• E-Commerce
• Uniform Code Council (UCC)
• Data types
• Transport protocols
• Security standards
• The Internet
• Windows operating systems
• UNIX operating system
2
Introduction to the Commerce Suite Documentation Set
Introduction to the Commerce Suite Documentation Set

The following documents make up the nuBridges Commerce Suite library:
• The Commerce Suite Release Notes describes new features, maintenance

updates, documentation updates, and important notes.
• The Commerce Suite Getting Started Guide lists hardware and software
requirements, describes Commerce Suite installation, configuration, and testing
procedures, and includes post-installation considerations.
• The Commerce Suite Database Connectivity Guide describes how to configure
Commerce Suite for use with supported Relational Database Management
Systems (RDBMS).
• The Configuring Commerce Suite Clusters guide describes Commerce Suite
clusters and their benefits, and explains how to configure Commerce Suite
clusters using a configuration file or database.
• The Commerce Suite Administration Guide describes how to manage
Commerce Suite servers, trading partners, and certificates, and provides other
important information for managing the Commerce Suite application.
• The Commerce Suite Command Reference presents an overview of the
Commerce Suite administration commands.
• The Commerce Suite Protocol Connectivity Guide provides instructions for
configuring Commerce Suite connectivity using FTP, SSL, and AS1 protocols.
• The Commerce Suite Trading Community Manager User Guide describes
how to configure and manage your trading community using the Trading
Community Manager graphical user interface.
• The Commerce Suite Trading Community Manager Release Notes describes
new features, maintenance updates, documentation updates, and important
notes relative to the Trading Community Manager.
3
Commerce Suite Documentation Roadmap

The documentation should be read in the following order for you to understand and
master the concepts and configurations required to get Commerce Suite up and
running quickly:
1. Commerce Suite Release Notes
2. Commerce Suite Getting Started Guide
3. Commerce Suite Database Connectivity Guide
4. Configuring Commerce Suite Clusters

The following table provides links to useful information in the Commerce Suite
documentation set. Topics include installation instructions, configuration procedures,
and administration tasks that are focused on providing you with the information you
need to get up and running quickly.
Read... To Learn About...

Commerce Suite Release Notes • New features
• Maintenance updates
• Documentation updates
• Important notes
Commerce Suite Getting Started Guide • The nuBridges AS2 solution
• Installing Commerce Suite
• Firewall configuration
• Licensing and upgrading
• Configuring Commerce Suite
• Testing Commerce Suite
• Work orders
• Configuration files
• Sending and receiving data
• Adding new trading partners
• Testing trading partner connectivity
4
Read... To Learn About...

Commerce Suite Database Connectivity • Connecting Commerce Suite to a
Guide supported RDBMS
• Oracle database support
• SQL database support
• DB2 database support
• Access database support
• Informix database support
Configuring Commerce Suite Clusters • Understanding Commerce Suite
clusters
• Setting up a cluster using a
configuration file
• Setting up a cluster using a supported
database
Commerce Suite Administration Guide • Commerce Suite basics
• Managing Commerce Suite servers
• Managing Commerce Suite trading
partners
• Managing Commerce Suite
certificates
• Configuring a backup administrator
• Commerce Suite error messages
Commerce Suite Command Reference • Commerce Suite commands and
parameters
Commerce Suite Protocol Connectivity • Configuring Commerce Suite for use
Guide with AS1, FTP, and SSL.
Trading Community Manager User • Trading Community Manager (TCM)
Guide hardware and software requirements
• Installing TCM
• Configuring TCM
• Managing organization
• Managing servers and services
• Managing groups and users
• Managing trading partners and
relationships
• Managing work orders and certificates
• Managing events and reports
5
Documentation Conventions
Documentation Conventions
This section will familiarize you with the features of this guide. As you will notice,
the left side of this guide has a section that is used for notes, references, and warnings.
These notes are identified by the following icons:
Designates a reference relevant to the adjacent text. The
reference may refer to a procedure, text in another
document, or a definition.
Designates there is additional information that is relevant
to the text on the right side.
Designates a warning or important piece of information.
This guide also utilizes text formatting to help you locate and identify information.
Review the table below for details on the text formatting used in this guide.
Text Format Example Explanation

Click Done.
Denotes a section of a screen, field, button,
Bold or page, or menu.
Go to the User Details section.
See the Introduction section on page 6.
Denotes a reference to a document section,
Italics or
chapter, or a filename.
Open the configuration.cfg file.
e222
or
Bold Italics Denotes a product name or document title.
Review the nuBridges Commerce Suite
User Guide for more information.
SMALL CAPS Press ENTER. Denotes a key located on the keyboard.
Denotes that both keys specified should be pressed
at the same time. For example, to execute CTRL +
KEY + KEY CTRL + N
N, you would simultaneously press the CTRL key
and the letter N on the keyboard.
addpair <from> <to> <to-URL>↵ Indicates the line of code wraps to the next line in
this documentation only. When you enter the code
↵ <rcpt-URL> <notify-name>↵ in Commerce Suite, it should not be split between
<inbox> [in|out] [<send-parma>] multiple lines.
{} -tb<timeout{s|ms}>
Indicates a set of choices from which you must
choose one.
Separates two mutually exclusive choices in a
| [in|out] syntax line. Type one of the choices, not the
symbol.
[] Indicates optional parameters. You typically type
[in|out] only the information within the brackets, not the
brackets.
... importkey <from> <to> <usage>↵
Indicates that a parameter can be repeated several
times in a command line. You enter only the
<option> [...] information, not the ellipsis (...).
6
Introduction to AS2
Introduction to AS2
The nuBridges Commerce Suite solution provides secure exchange of data over the
Internet between companies and their business partners. Commerce Suite supports
established industry standards such as AS1, AS2, HTTP, HTTP/S, SFTP, SMTP, and
Rosettanet, enabling businesses to send and receive any type of data using multiple
communications protocols and security models.
AS1 and AS2 are draft specifications developed by the Internet Engineering Task
Force (IETF) for securely exchanging business documents over the Internet.
EDI-INT is an internet specification from the IETF for reliably exchanging structured
messages over the internet. The IETF is a large, open, international community of
network designers, operators, vendors, and researchers concerned with the evolution
of the Internet architecture and the smooth operation of the Internet.
AS2 is a draft specification first published in the IETF standard’s track. AS2 provides
an Internet solution for securely exchanging EDI over the Internet using Multipurpose
Internet Mail Extensions (MIME) and the hypertext transmission protocol (HTTP)
instead of the simple mail transport protocol (SMTP) as the transport protocol. AS2
specifies the means to connect, deliver, validate, and reply to (receipt) data in a secure
and reliable way. AS2 does not concern itself with the content of the EDI document,
only the transport.
AS2 essentially creates a wrapper around EDI flat files that enables sending them over
the Internet, instead of using a dial-up connection to a VAN (value-added network).
AS2 is a real-time technology that provides security and encryption around the HTTP
packets. A VAN is a private network provider that is hired by a company to facilitate
secure EDI.nubridges
Commerce Suite solution is certified by the Uniform Code Council (UCC) and is also
in full compliance with the IETF EDI-INT specification. This support for the EDI-INT
specification ensures that trading partners can use the Internet as a transport medium to
conduct business between their respective EDI systems and provide secure EDI over
the Internet.
The Commerce Suite application provides your enterprise with the following business
benefits:
• Supports multiple data types, transport protocols, and security standards.

• Supports a wide range of platforms.
• Utilizes high-performance technology to maximize throughput.
• Enables complete privacy, authentication, integrity, and non-repudiation of all
transactions.
• Supports certificates from all major security vendors and provides a Public Key
Infrastructure (PKI) solution generating X.509 certificates.
• Offers high-availability failover and restart.
7
AS2 Communication Requirements
AS2 Communication Requirements

Your organization must meet the following requirements in order to successfully
communicate with other trading partners exchanging data using AS2 capability to
accept and translate EDI data.
• nuBridges Commerce Suite software.

• High-speed Internet connection with a static IP address.
• TCP/IP network interface.
• 24x7 server availability for communication with other AS2 servers.
• Dedicated network capacity on reserve to handle peak traffic at unpredictable
times.
• Management of digital certificates.
• Firewall rules in place to communicate with AS2 partners - Trading partner may
require inbound and outbound firewall modifications to account for all trading
partner IP addresses and port numbers.
Note: nuBridges recommends a dedicated machine to host the AS2 server, but it is not
mandatory for the application to run properly.
Roadmap for Establishing nuBridges Connectivity

Proper installation and configuration for enabling connectivity between your
Commerce Suite implementation and nuBridges involves the following tasks.
1. Contact nuBridges to obtain a copy of the nuBridges Commerce Suite

software.
2. Install the nuBridges Commerce Suite software.
3. Configure the Commerce Suite software and test with nuBridges.
8
Typical Commerce Suite Administrator Duties
Typical Commerce Suite Administrator Duties

Your organization’s Commerce Suite system administrator is a critical resource for
setting up and managing the Commerce Suite system. Typical Commerce Suite
administration tasks include the following:
• Installing Commerce Suite.

• Configuring Commerce Suite and performing connectivity testing between
your automated internal systems and between the Internet and nuBridges.
• Controlling user access policies and registration to the Commerce Suite server
and its processes.
• Creating and exchanging partner profile information and certificates with your
trading partners.
• Monitoring the Commerce Suite system status.
• Receiving and responding to system alerts and notifications.
• Upgrading Commerce Suite software to implement new releases and
functionality.
• Overseeing system security, including managing certificates for you and your
partners.
• Contacting nuBridges Technical Support, if you have purchased support, to
resolve Commerce Suite issues. When working with Technical Support, it is
advisable that your organization assign a single point of contact.
9
Chapter 2: Preparing to Install
Commerce Suite
Introduction .....................................................................................................11
Commerce Suite System Requirements - Windows .......................................11
Hardware Requirements ................................................................................................... 11
Software Requirements ....................................................................................................12
Administrator Rights for Windows NT and 2000 ...............................................................12
Recommended Software for Windows .............................................................................12
Commerce Suite System Requirements - UNIX ............................................ 13

Hardware Requirements ...................................................................................................13
Software Requirements ....................................................................................................13
Recommended Software for UNIX ...................................................................................13
OS Patches.................................................................................................... 13
Introduction
Introduction
The Commerce Suite applications is distributed via email or FTP download within a
ZIP file or compressed archive file. The contents of the file must be extracted and
executed on your local system.
This chapter provides information on how to prepare for a Commerce Suite

installation.
You must register with nuBridges Support to receive a user ID and password in order
to perform the connectivity testing described in Chapter 7: Testing Commerce Suite .
Go to the nuBridges website at support.nubridges.com and select the New User?
link.
Commerce Suite System Requirements - Windows

This section details the hardware and software requirements necessary to run
Commerce Suite on a Windows operating system.
Hardware Requirements
A Windows system must have the following minimum configuration to run the
Commerce Suite server.
• A Pentium-class processor running at 400 Mhz or faster

• Random Access Memory
• 256MB recommended
• 128MB minimum
• 15MB available hard drive space
Much of this drive space requirement is necessary for database executables,

which can range from 10MB to 15MB.
• TCP/IP network interface
• Persistent Internet connection
11
Commerce Suite System Requirements - Windows
Software Requirements
A Windows computer must have the following software installed for the Commerce
Suite server application to function properly.
• One of the following Windows operating system versions:

• Windows NT 4.0 Server, SP 6
• Windows 2000, SP 3
• Windows XP Professional
Commerce Suite does not support Windows 98 or Windows XP Home.
• Java 2 Platform, Standard Edition, v 1.4.1 (J2SE) Java 2 Runtime Environment
(JRE)
Refer to the Chapter 5: Installing Commerce Suite chapter for instructions on

downloading and verifying installation of the JRE software.
• Internet Explorer 6.0 or later
Administrator Rights for Windows NT and 2000

For Windows NT or Windows 2000, you must have administrator rights to
successfully install Commerce Suite. If you are not sure whether you have
administrator rights for the installation machine, check with your system administrator.
Recommended Software for Windows

In addition, you need Adobe Acrobat Reader to view and print the Commerce Suite
documentation, which is provided in a portable document format (PDF) file. Acrobat
Reader is available free from Adobe Systems, Inc. at http://www.adobe.com.
12
Commerce Suite System Requirements - UNIX
Commerce Suite System Requirements - UNIX

This section details the hardware and software requirements necessary to run
Commerce Suite on a UNIX operating system.
Hardware Requirements
A UNIX system must have the following minimum configuration to successfully
install Commerce Suite:
• A Pentium-class processor running at 400 Mhz or faster

• Random Access Memory
• 256MB recommended
• 128MB minimum
• 15MB available hard drive space
Much of this drive space requirement is necessary for database executables,
which can range from 10MB to 15MB.
• TCP/IP network interface
• Persistent Internet connection with a static IP address
Software Requirements
A UNIX system must have one of the following UNIX operating systems to
successfully install Commerce Suite:
• HP-UX 11.00
• IBM AIX 4.3.3, 5.1
• Sun Solaris 8 (SunOS 5.8)
• SuSe 8.x, 9.0
• Red Hat 7.3, 8.0, 9.0
Recommended Software for UNIX

In addition, you need Adobe Acrobat Reader to view and print the Commerce Suite
documentation, which is provided in a portable document format (PDF) file. Acrobat
Reader is available free from Adobe Systems, Inc. at http://www.adobe.com.
OS Patches
Patches for some operating systems are required to support the technology that
Commerce Suite uses. For a list of recommended patches, see the Commerce Suite
release notes in your installation directory.
13
Chapter 3: Commerce Suite Firewall
Configuration Settings
Introduction .................................................................................................... 15
Commerce Suite Firewall Considerations...................................................... 15
External Trading Partner Inbound Firewall Considerations ........................... 16
External Trading Partner Outbound Firewall Considerations......................... 17
Introduction
Introduction
The following configuration considerations will provide your firewall administrator
the information needed to make the necessary firewall configuration changes to
support communication with the Commerce Suite application.
The Commerce Suite application running in your environment requires a static IP

address that is addressable from the Internet. If you are using the Commerce Suite
application behind a firewall, this address will normally be the address of the firewall.
You must configure the firewall to support inbound and outbound connections with the
Commerce Suite application.
Commerce Suite Firewall Considerations

Use the following guidelines to facilitate the configuration of your firewall for use
with the Commerce Suite application. You can record your firewall configuration
information in the spaces provided below each step.
1. Determine and record your firewall IP address.
_____________________________________________
2. Determine and record the port number that will be used for inbound AS2
messages. It is recommended that you use a port number such as 4080 or 5080.
This port number will be referred to as the external port number.
_____________________________________________
3. Determine and record the actual IP address of the internal machine running the
____________________________________________
4. Assign and record the port number that Commerce Suite, on the internal
machine, will use for it’s HTTP listener. The address and port number is
required during the Commerce Suite configuration process. We recommend
that you use the same port number as your external port. This port number will
be referred to as the internal port number.
_____________________________________________
15
External Trading Partner Inbound Firewall Considerations
5. Record the combination of your firewall IP address and your external port
number. This address will be provided to your trading partners and used by the
Commerce Suite configuration process.
_____________________________________________
6. Configure the firewall ports for TCP as the protocol.
7. If you are using Network Address Translation (NAT) to allow connections to

your internal machine, you will need to create NAT rules at the firewall. Refer
to the internal machine address and port information you recorded earlier in this
section. For more information on configuring NAT rules for your firewall,
consult your firewall documentation.
External Trading Partner Inbound Firewall Considerations

Use the following guidelines to facilitate the configuration of your firewall to support
inbound trading partner communications.
1. You must configure a firewall inbound rule for the trading partner on the
external port number you selected.
2. Identify your trading partners’ sending IP address and potential port range they
will use.
_____________________________________________
The following table provides the configuration information you need in order to
conduct connectivity testing with nuBridges.
Inbound From nuBridges Test Server Configuration Information
IP Definition Configuration Value

Source IP Address 66.180.117.26
Source Port Range Greater than 1023
Note: All AS2 messages sent from the nuBridges Test server will originate
from the source IP address listed in table above. In addition, the nuBridges AS2
server can initiate multiple concurrent sending operations and will send from a
range of ports listed in the table above.
3. Ensure each trading partner is configured for inbound and outbound AS2 traffic
through your firewall based on their trading partner specific IP address and port
information.
16
External Trading Partner Outbound Firewall Considerations
External Trading Partner Outbound Firewall Considerations

The following configuration definitions will provide your firewall administrator the
information needed to make the necessary firewall configuration changes to support
outbound trading partner communications.
Your external trading partners will provide you with the external IP address and port
on which they will receive the AS2 messages you send. You will use this information
to configure your Commerce Suite application for the trading relationship with this
partner. Additionally, you will need to configure your firewall to allow the Commerce
Suite application on the secure side of your network to send messages to the trading
partner’s AS2 server.
You must configure outbound firewall rules for each trading partner on the port
number that matches the trading partner’s external port number.
Send to nuBridges Test Server Configuration Information
IP Definition Configuration Value

66.180.117.26
Destination IP Address
(selftest.nubridges.com)
Destination Port 4080
Note: Each trading partner requires inbound and outbound modifications to your
firewall based on trading partner specific IP address and port information.
For outbound firewall rules, it is recommended that you configure for the primary
destination port of 4080, as well as the manual testing ports 4081 - 4088.
17
Chapter 4: Licensing and Upgrading
Commerce Suite
Introduction .................................................................................................... 19
About License Key Generation ...................................................................... 19
Licensing Requirements ................................................................................ 19
Upgrading Your Commerce Suite Software ................................................... 20
Introduction
Introduction
The nuBridges Commerce Suite application, as shipped, starts and operates in
Demonstration mode. When the product is purchased, you are supplied with license
key material that enables you to convert the product to operate in Authorized
Installation mode.
This chapter provides information on generating licenses, licensing requirements, and

upgrading Commerce Suite software.
About License Key Generation

Your nuBridges sales representative obtains the configuration information for each
machine on which you will run Commerce Suite. This information is given to
nuBridges Technical Support.
nuBridges Technical Support creates icssvr.lic and icssvr.ini files based on your
configuration information, which contains an authentication number unique to each
machine. This authentication number, combined with a serial number in the icssvr.ini
file, are used to generate a license file (icssvr.lic). This license file allows your copy of
the software to run in Authorized Installation mode. As long as the icssvr.lic file
resides in the same directory as the icssvr binary file, you do not need to enter any
authentication codes to start the application in Authorized Installation mode.
Licensing Requirements
If you are configuring the product for Authorized Installation mode, you must
complete the following before licensing:
• TCP/IP configuration must be complete.

• Obtained valid icssvr.lic and icssvr.ini file from nuBridges Technical Support.
• You must have successfully installed the software, and the icssvr.lic file and the
icssvr.ini file must reside in the same directory as the icssvr binary file.
If TCP/IP configuration is not complete or is changed after installation, you must

contact nuBridges Technical Support to obtain new licensing information.
19
Upgrading Your Commerce Suite Software
Upgrading Your Commerce Suite Software

As Commerce Suite upgrades become available, they may be downloaded from the
nuBridges Technical Support website. Please contact your nuBridges sales
representative for information regarding Commerce Suite upgrades and availability.
Upgrades for the nuBridges Commerce Suite software are available as complete
replacement modules within a ZIP or compressed archive file. As the upgrade occurs,
existing directory structures remain intact and system settings are unaffected. To
ensure your replacement module is applied, start Commerce Suite and issue a status
command to verify that you have properly upgraded your Commerce Suite
application.
20
Introduction .................................................................................................... 22
Installing on Windows .................................................................................... 22
Installing on UNIX .......................................................................................... 23
Installing on IBM AIX ........................................................................................................23
Installing on Linux .............................................................................................................24
Installing on HP-UX ..........................................................................................................25
Installing on Sun Solaris ...................................................................................................26
Uninstalling on UNIX...................................................................................... 27
Java 2 Runtime Environment Installation Verification .................................... 28
Introduction
Introduction
This chapter provides instructions for installing Commerce Suite on Windows and
UNIX operating systems as well as verifying Java 2 Runtime Environment
installation.
Before installing Commerce Suite, review Chapter 2: Preparing to Install Commerce

Suite to ensure that you have the proper hardware, software, and communications in
place for a successful installation.
Please review
the Documentation
Conventions on page 6 to Note: In the code samples throughout this book, you may see an arrow symbol (↵) at
“Documentation Conventions” the end of some lines of code. This indicates the line of code wraps to the next line in
for more information on text
formatting. this documentation only. When you enter the code in Commerce Suite, it should not be
split between multiple lines.
Installing on Windows
Follow the steps below to install Commerce Suite in a Windows environment.
1. Create directory named c:\isoft on your local file system.
2. Copy the ZIP file you received into that directory.
3. Unzip the file using a common ZIP file manager and extract the Commerce
Suite software files into the isoft directory. The following should be present
after unzipping the file:
• isoft_csm(x).jar
• pki folder
• documentation folder
• icssvr
• test.txt
• TP_Info.ini
4. Copy the license files icssvr.lic and icssvr.ini to your c:\iSoft directory.
5. Double-click the icssvr.exe to start the Commerce Suite application.
6. Commerce Suite has now been installed and you are ready to run Commerce
Suite Manager. Review Chapter 6: Configuring Commerce Suite for
instructions on running the Commerce Suite Manager.
When the application starts, Authorized License displays.
22
Installing on UNIX
Installing on UNIX
Instructions for installing Commerce Suite on UNIX operating systems are provided
in the following sections:
• Installing on IBM AIX

• Installing on Linux
• Installing on HP-UX
• Installing on Sun Solaris
• Uninstalling on UNIX
Installing on IBM AIX

Follow the steps below to install Commerce Suite on an IBM AIX server.
1. Log in as the root user.
2. Create an ICSSVR group. This is the recommended group name; however, you
can create a group using another name.
3. Create an ICSSVR user. This is the recommended user name; however, you can
create a user using a another name.
4. Create a directory named /opt/icssvr.
5. Obtain the current AIX .tar file. This .tar file contains the following files:
• pki folder
• icssvr
• test.txt
• TP_Info.ini
• buildcfg
6. Extract the file to the /opt/isoft directory.
7. Before using the Commerce Suite software, you must obtain the following files
from nuBridges:
• icssvr.lic
• icssvr.ini
23
Installing on UNIX
8. Both of these files must be placed into the /opt/isoft directory.
9. Enter chmod 755 icssvr to ensure that the icssvr file has executable permission.
10. Change to the /opt/isoft directory.
11. Enter ./icssvr to execute the icssvr binary.
12. The following message displays: Authorized License
Commerce Suite has now been installed and you are ready to run the Commerce Suite
Manager. Please review Chapter 6: Configuring Commerce Suite for instructions on
running Commerce Suite Manager.
Note: In order for Commerce Suite to operate properly on AIX 5.1 with Oracle, select:
System Management Interface Tool (SMIT) > Devices > Asynchronous I/O >
Change/Show Characteristics of Asynchronous I/O
The STATE to be Configured at System Restart option should display Available.

Contact Oracle support if you are still experiencing errors after validating this
configuration setting.
Installing on Linux
Follow the steps below to install Commerce Suite on a Linux server.
2. Create an icssvr group. This is the recommended group name; however, you
3. Create an icssvr user. This is the recommended user name; however, you can
4. Create a directory named /opt/isoft.
5. Obtain the current Linux .tar file. This .tar file contains the following files:
• pki folder
• icssvr
• test.txt
• TP_Info.ini
24
Installing on UNIX
from nuBridges:
• icssvr.lic
• icssvr.ini
Both of these files must be placed into the /opt/isoft directory.
10. Enter ./icssvr to execute the icssvr binary. The message Authorized License
displays.
Commerce Suite has now been installed and you are ready to run the
application. Review Chapter 6: Configuring Commerce Suite for instructions
on running Commerce Suite Manager.
Installing on HP-UX
Follow the steps below to install Commerce Suite on an HP-UX server.
4. Create the /opt/isoft directory on each client machine.
5. Obtain the current HP-UX .tar file. This .tar file contains the following files:
• pki folder
• icssvr
• test.txt
• TP_Info.ini
• buildcfg
25
Installing on UNIX
from nuBridges:
• icssvr.lic
• icssvr.ini
displays.
11. Commerce Suite has now been installed and you are ready to run Commerce
Suite Manager. Please review Chapter 6: Configuring Commerce Suite for
instructions on running Commerce Suite Manager.
Installing on Sun Solaris

Follow the steps below to install Commerce Suite on a Sun Solaris 8 (SunOS 5.8)
server. Sun Solaris version 9.0 is not supported at this time.
4. Create a directory named /opt/isoft.
5. Obtain the current Sun Solaris .tar file. This .tar file contains the following
files:
• pki folder
• icssvr
• test.txt
• TP_Info.ini
26
Uninstalling on UNIX
• buildcfg
from nuBridges:
• icssvr.lic
• icssvr.ini
displays.
Commerce Suite has now been installed and you are ready to run Commerce
Suite Manager. Please review Chapter 6: Configuring Commerce Suite for
instructions on running Commerce Suite Manager.
Uninstalling on UNIX
Follow the steps below to uninstall Commerce Suite from a UNIX computer:
1. Log into the account you created.
2. Shut down all Commerce Suite applications.
3. Run the following command:
rm -rf /opt/isoft
27
Java 2 Runtime Environment Installation Verification

In order for Commerce Suite to operate properly, you must have the correct Sun Java 2
Runtime Environment installed on your system.
Follow the steps below to verify that you have the correct version of the Sun JRE
installed.
1. The enter the command java -version in a command console window:
If you have JRE version 1.4.x or later, you can use it to run Commerce Suite.
Proceed to step 8 and continue following the directions.
If you do not have JRE version 1.4.x or later, continue to proceed to step 2 for
instructions on downloading and installing the JRE software.
2. Enter the following in a web browser:

http://java.sun.com/j2se/1.4.2/download.html
3. From within the Download J2SE v 1.4.x section, click Download from the JRE
column for the following software:
32-bit/64-bit for Windows/Linux/Solaris SPARC

32-bit for Solaris x86
4. Accept the JRE download terms and conditions.
5. Windows users must click Windows Offline Installation, Multi-language. For

other platforms, select the appropriate download.
6. Save the downloaded file to a directory.
7. Execute the JRE installation file to install the Java Runtime Environment.
28
8. Ensure the isoft_csm(x).jar file is co-located in the directory where the

nuBridges Commerce Suite application (icssvr) is located.
9. Ensure that the Commerce Suite application is running by double-clicking on

the icssvr.exe or by entering ./icssvr for UNIX.
Note: If you are running the nuBridges server as a service or daemon, stop it,
and run it in the foreground for the initial testing of the Commerce Suite
Manager (CSM).
10. After starting Commerce Suite (icssvr), enter the following command:
set -opworkorder -of
11. You are now ready to initialize Commerce Suite and configure it for
exchanging data with your trading partners.
29
Introduction .................................................................................................... 31
Commerce Suite Manager Overview............................................................. 31
Commerce Suite Manager System Requirements ...........................................................31
Step 1 - Initializing Commerce Suite.............................................................. 32

For UNIX...........................................................................................................................32
For Windows.....................................................................................................................33
Using an Existing Configuration File.................................................................................36
Step 2 - Editing a Trading Partner Profile ...................................................... 38

Step 3 - Configuring Your Inbox ..................................................................... 39
Step 4 - Configuring Your Outbox .................................................................. 41
Step 5 - Creating Certificates and Keys......................................................... 44
Step 6 - Adding a New Trading Partner ......................................................... 47
Step 7 - Saving the Commerce Suite Configuration File ............................... 48
Step 8 - Reloading the Commerce Suite Configuration File .......................... 48
Step 9 - Closing Commerce Suite Manager .................................................. 48
Step 10 - Testing Commerce Suite Connectivity............................................ 49
Introduction
Introduction
This section describes the steps necessary to configure Commerce Suite as a stand-
alone transport agent using a configuration file that will be read by the application
upon startup.
Commerce Suite Manager Overview

The Commerce Suite Manager (CSM) is a graphical user interface (GUI) that allows
you to initialize and manage your Commerce Suite environment utilizing a file-based
configuration.
CSM helps you create the icssvr.cfg configuration file read by Commerce Suite upon
startup. It also helps you edit, add, and delete trading partner relationships, create
relationship certificates and key pairs, and test your Commerce Suite installation with
the nuBridges Self-Test Server.
Commerce Suite Manager System Requirements

The CSM currently requires you to have the Java Runtime Environment installed on
the machine running the application. If you do not already have the Java Runtime
Environment installed on your machine, please review Chapter 5: Installing
Commerce Suite for instructions on downloading and installing the JRE.
For platforms other than Windows, please download Sun’s Java Runtime Environment
from Sun Microsystem’s Web site located at http://java.sun.com/j2se.
31
Step 1 - Initializing Commerce Suite

Refer to the following appropriate platform-specific section to start the Commerce
Suite Manager and initialize Commerce Suite.
For UNIX
Follow the steps below to start Commerce Suite Manager on AIX, HPUX, Linux, and
Solaris clients.
1. Enable execute permissions on the isoft_csm.jar binary.
2. Open a terminal and navigate to the location of the isoft_csm.jar file and enter:
java -jar isoft_csm.jar
The Initialization dialog box displays. Please review the For Windows section
on page 33 to Step 2 within the For Windows section to continue initializing
Commerce Suite.
32
For Windows
Perform the following steps to initialize Commerce Suite and create the icssvr.cfg
configuration file:
1. Use Windows Explorer to navigate to the directory where the isoft_csm(x).jar

file is located.
2. Double-click the isoft_csm(x).jar file to start the CSM application. The

Commerce Suite Manager Initialization screen displays.
3. Complete the Commerce Suite Manager Initialization screen using the field
descriptions below.
My AS2 Name Enter your AS2 name. This is the AS2 name you want
associated with your business. Your trading partner will
use this name to communicate with you. This AS2 name
is a case-sensitive alphanumeric string (maximum 32
characters) that must not contain any spaces. It should
be descriptive and unique between trading partners,
No, I do not have a

firewall Select this option if you do not you have a firewall
device in front of your Commerce Suite server. Enter
the address of the machine running the AS2 server
application in the My IP Address field.
33
Yes, I have a
firewall Select this option if you do have a firewall device in
front of your Commerce Suite server. Enter the firewall
address into the Firewall IP Address field.
This firewall could represent either a corporate device

on a separate machine, a DSL/Cable modem router/
firewall, or a personal software firewall running on the
same machine as the Commerce Suite server.
Corporate Firewall - If you have a corporate firewall

on another machine, you need to coordinate with the
firewall administrator to obtain the correct external
address. The firewall administrator will create the
firewall rules to allow trading partners to talk with your
Commerce Suite server on the port designated for AS2
communications.
DSL/Cable Modem/Firewall - If you have DSL/Cable

Modem Router/Firewall, refer to the device
documentation if you need to enable Network Address
Translation (NAT) or Port forwarding to talk to the
server that is actually running the Commerce Suite
server application.
Personal Firewall - If you have a software personal

firewall on your machine, you should refer to the
software documentation to determine how to create the
necessary firewall rules to allow communication with
your trading partners. In this case, your External
Address will most likely be the same as your Internal
Address.
Organization Enter the name of your organization. This information is

used to create descriptive information contained within
the certificate.
City Enter the name of your city. This information is used to

create descriptive information contained within the
certificate.
34
State Enter the name of your state. This information is used to

create descriptive information contained within the
certificate.
Country Enter a Country or Country code. Your Country or

Country code cannot contain any spaces.
Configure for
Wal-Mart Select Yes or No. If you select Yes to configure for Wal-
Mart, you must also select the appropriate Wal-Mart
location so that Commerce Suite Manager can create
the required configuration entries. You may choose from
the following locations: US, Canada, Mexico, UK, BR,
AR, CN, DE.
4. Click the Write Initial Configuration File button. The system creates your
Commerce Suite directories and the icssvr.cfg configuration file located in the
isoft root directory. The following screen displays.
5. Click OK. The following screen displays.
6. Click OK. The Commerce Suite Manager main window displays. From the
main Commerce Suite Manager window, you can manage relationships,
perform testing, view log files, and adjust Commerce Suite Manager and
configuration file settings.
35
Using an Existing Configuration File

If you are running the Commerce Suite Manager application for the first time and
have an existing configuration file (icssvr.cfg), the application will read the current
values from your existing configuration file.
Perform the following steps to initialize Commerce Suite when a previous nuBridges
Commerce Suite configuration file exists:
1. Use Windows Explorer to navigate to the directory where the isoft_csm(x).jar

file is located.
2. Double-click the isoft_csm(x).jar file to start the Commerce Suite Manager

application. If Commerce Suite detects an existing configuration file
(icssvr.cfg), the following dialog box displays.
3. Click OK to dismiss the Error dialog box and display the CSM Settings page
of the Commerce Suite Manager dialog box.
36
4. Under Certificate Detail Fields, click Edit to enable the Organization, City,
State, and Country fields. Enter your appropriate information.
5. Click Save to confirm your settings.
6. Under My IP Configuration, click Edit to enable the My IP Address and

HTTP Port fields. Enter your appropriate information.
8. Under Firewall Configuration, click Edit to enable the option buttons. Select
your firewall configuration.
10. Under My AS2 Names, click Add Name to specify your AS2 name.
37
Step 2 - Editing a Trading Partner Profile
Step 2 - Editing a Trading Partner Profile

You can edit an existing trading partner profile and update your icssvr.cfg
configuration file using Commerce Suite Manager.
Follow the steps below to edit an existing trading partner profile using Commerce
Suite Manager:
1. Click the Relationships tab to view existing relationships.
2. Click the trading partner you want to edit from the Trading Partners table.
This will highlight the selected trading partner row.
3. Click Edit Trading Partner. Text fields display at the bottom of the dialog
box. Use these fields to edit the trading partner’s information.
38
Step 3 - Configuring Your Inbox

Data received from a specific trading partner is sent to the directory specified in the
Inbox Location field of the MyAS2 page of Commerce Suite Manager. This is also
the same directory specified in the addpair command in the icssvr.cfg file.
The Inbox can be any directory that the Commerce Suite server can access.
Refer to the nuBridges
Commerce Suite
Command Reference for more Note: You must make sure that the directory exists before specifying it as the inbox. If
information on the addpair the inbox directory does not exist, errors are generated when attempting to receive
command.
files.
Follow the steps below to specify an inbox to be used for receiving data:
2. In the Trading Partners table, click the row that contains the trading partner
you want to edit. The selected row is highlighted.
39
3. Click Edit Trading Partner. Editable text fields display at the bottom of the
dialog box.
4. Locate the Inbox Location field and click the ... (Browse) button. Navigate to
the location you want to use as the inbox for this relationship.
5. Click Select Directory to choose the selected inbox directory. The path to that
directory displays in the Inbox Location field.
Note: If you select a directory path that contains spaces, you will receive an
error message. Ensure that the directory path does not contain spaces.
40
Step 4 - Configuring Your Outbox

Commerce Suite Manager supports persistent sends that scan a directory at regular
intervals looking for a file to send. When a file is located, Commerce Suite sends the
first file listed in the directory.
Follow the steps below to configure an automatic outbox using Commerce Suite
Manager.
1. Create a subdirectory within your outbox directory.
41
4. Click Edit Trading Partner. Editable text fields display at the bottom of the
dialog box.
5. Click Configure Outbox. The Auto Outbox Configuration dialog box

displays.
42
6. Click Yes, I want an Outbox for this Trading Partner. The Auto Outbox
Configuration dialog box displays.
7. Click the ... (Browse) button to select your outbox location.
8. Click Save to confirm your outbox configuration. Commerce Suite will now
scan the specified directory at regular intervals looking for a file to send with an
.out extension. When a file is located, Commerce Suite sends the first file listed
in the directory.
43
Step 5 - Creating Certificates and Keys

From Commerce Suite Manager you can generate new certificates and keypair files.
You can re-create keys using work orders that are submitted to the server to generate
the keypair. The work order file is then written to the work order.
Follow the steps below to create certificates and keys:
1. Start Commerce Suite Manager. The Commerce Suite Manager main window
opens.
44
4. Click Configure Keys to configure your trading relationship certificates. The

Key Configuration dialog box displays.
5. Select Create new relationship key. The My Relationship Key Pair field
displays.
6. Enter a filename in the My Relationship Key Pair field. This filename should
have a .cer extension. There should not be any spaces in the filename.
45
7. Click Save. A work order that will generate a new key pair will be written to
the workorder directory. If you have the Commerce Suite server console open,
a message confirming the generation and export of the key-pair displays once
the work order is processed.
8. Click Save Changes to keep your modified values, or click Cancel to discard
your changes.
9. Keys created by the initialization routing are placed in the Commerce Suite pki
directory and are available the next time the server is recycled.
10. From the Relationships page, click Configure Keys to make the keys active.
The Key Configuration dialog box displays.
11. Select the Use existing key option.
12. Click the ... (Browse) button to select the newly created public key, which will
be located in pki/new directory.
13. Under Trading Partner Key, select the Use existing key option as your trading
partner will provide you with a certificate to be used in the trading relationship.
The TP Provided Certificate field displays.
14. Click the Browse (...) button next to the TP Provided Certificate field and
select the trading partner’s public key.
15. Click Save to save your settings and return to the Relationships page of the
CSM.
46
Step 6 - Adding a New Trading Partner
Step 6 - Adding a New Trading Partner

A trading partner relationship (or pair) consists of a set of data describing how data
may be transferred from one defined trading partner to another defined trading partner.
A trading partner may be identified and defined using an alphanumeric sequence of
characters or a user-defined company or institution name.
Follow the steps below to define a new trading partner pair using Commerce Suite
Manager.
2. From the Relationships page, click Add New Trading Partners. The Add
New Trading Partner dialog box displays.
47
Step 7 - Saving the Commerce Suite Configuration File
3. Complete the Add New Trading Partner dialog box using the field
descriptions below.
My AS2 Name Select your AS2 name from the drop down list.
Protocol From the drop down list, select the protocol to be used
for this trading relationship.
Import Trading
Partner Select your trading partner from the drop down list.
Selecting a trading partner from this list automatically
populates the remaining trading partner fields. If your
trading partner is not displayed in the list, enter the
appropriate information into the remaining trading
partner fields.
4. Click the ... (Browse) button located next to the Inbox Location, to select the
inbox for this relationship.
5. Click Add once you have entered all of the trading partner information. The
new trading partner relationship now displays within the Trading Partners list
on the Relationships page.
Step 7 - Saving the Commerce Suite Configuration File

Once you are satisfied with the configuration changes, you need to save the
configuration file. From the File menu, select the Save Config File option. The
modified values are saved and a new icssvr.cfg file is written to your system.
Step 8 - Reloading the Commerce Suite Configuration File

To reload the configuration file, select File > Reload Config File. This forces the
Commerce Suite server to load the new configuration into memory and read your
changes.
Step 9 - Closing Commerce Suite Manager

To close Commerce Suite Manager, select File > Exit. If you have made changes but
did not save them, you will be prompted to either save or cancel your changes.
48
Step 10 - Testing Commerce Suite Connectivity
Step 10 - Testing Commerce Suite Connectivity

You can test your Commerce Suite installation with the nuBridges Self-Test server.
The nuBridges Self-Test allows you to send a test file to the nuBridges Self-Test
server. This test verifies that your Commerce Suite instance can send an encrypted
file using a digital certificate as well as request a signed receipt.
Please review Chapter 7: Testing Commerce Suite for detailed instructions on using
the nuBridges Self-Test website to test your firewall configuration and Commerce
Suite connectivity.
When prompted from the nuBridges Self-Test Server Web site, click the appropriate
Send nuBridges Test X button to create the work order file that will be executed by
the Commerce Suite server.
In addition to using the nuBridges Self-Test server to test your connectivity with
nuBridges, you can perform a connectivity test for every trading partner you add to
your trading community.
49
Introduction .................................................................................................... 51
Testing Requirements .................................................................................... 52
Testing Commerce Suite Connectivity ........................................................... 53
Step 1 - Accessing and Logging In to the Self-Test Web Site...........................................53
Step 2 - Verifying the Requirements .................................................................................55
Step 3 - Uploading Files....................................................................................................56
Step 4 - Receiving Test Files ............................................................................................58
Error Code Example...................................................................................................59
Step 5 - Sending Test Files ...............................................................................................60

Introduction
Introduction
This section describes the procedures for using the nuBridges Self-Test website to test
your firewall configuration and Commerce Suite connectivity. The self-testing process
consists of the following steps:
• Accessing the nuBridges Self-Test Web site
Initial access of the nuBridges Self-Test Web site enables nuBridges to

determine the external IP address of your machine. This is the IP address that is
used for testing.
• Logging in to the nuBridges Self-Test Web site
Logging into the nuBridges Self-Test Web site authenticates your nuBridges
Customer Support credentials, allowing you to continue with the test.
• Meeting the Self-Test requirements
Ensures the necessary requirements are met prior to conducting the Self-Test.
• Uploading your public key and configuration file
Uploading your public key and configuration file is necessary for configuring
your Commerce Suite instance as a trading partner with nuBridges and for
encryption and signature verification.
• Receiving test files
The receiving test verifies that Commerce Suite can receive a file from the
nuBridges test server, return an MDN, verify a digital signature, decrypt an
encrypted file, and decompress a compressed file
• Sending test files
The sending test verifies that Commerce Suite can send a digitally-signed,
encrypted, compressed file, requesting an MDN, to the nuBridges test server.
51
Testing Requirements
Testing Requirements
In order to run the self-test workflow, the following is required:
• You must register with nuBridges Support to receive a user ID and password for
performing the send and receive testing. Go to support.nubridges.com and
select the New User link located under the login box.
• You must be running a standards-based Internet browser, such as Internet
Explorer 6.0 or greater.
• You must run the self-test on the same machine as Commerce Suite.
• During the self-test, you must not double click the form buttons or use the
browser’s Back button.
• If you do not already have it, you must download the ISOFTAS2TEST.cer file to
your \isoft\pki directory.
52
Testing Commerce Suite Connectivity

Follow the steps below to conduct Commerce Suite connectivity testing using the self-
test workflow.
Step 1 - Accessing and Logging In to the Self-Test

Web Site
Follow the steps below to access the nuBridges Self-Test website.
1. Start Commerce Suite by double-clicking the icssvr.exe file.
For all non-Windows platforms, navigate to your isoft installation directory (/

opt/isoft/) and enter the following at your terminal:
./icssvr
2. Start your Internet browser and go to http://selftest.nubridges.com. The Login

screen displays.
3. Enter the username and password given to you when you registered with
nuBridges.
53
4. Click Login. The main Self-Test screen displays.
5. Follow the steps on this screen in numerical order to complete the nuBridges
Self-Test procedure.
54
Step 2 - Verifying the Requirements

Follow the steps below to verify that you have met all the Self-Test requirements.
1. From the main Self-Test screen, select Requirements for Configuration Self
Test. The Requirements screen displays.
2. Make sure all the requirements listed on this screen have been met.
3. Click Continue. The nuBridges Self-Test main screen displays.
55
Step 3 - Uploading Files

To conduct the send and receive testing, you need to upload the SendToiSoftServer.cfg
file and your public certificate. (For example: yourfile-isoft.cer). Both of these files
were generated during the initial configuration process (please review Chapter 6:
Configuring Commerce Suite for more information).
1. From the main Self-Test screen, select Upload SendToiSoftServer.cfg. The

Upload screen displays.
2. Click Browse to navigate to the location of the SendToiSoftServer.cfg file, and

select this file from the list.
3. Click Upload Configuration. When the file has been uploaded successfully, a
verification screen displays.
56
4. Click Continue. The Upload Certificate screen displays, showing the name of
the public certificate file you need to upload.
5. Click Browse to navigate to the location of the public certificate file displayed,
and select this file from the list.
6. Click Upload Configuration. When the file has been uploaded successfully, a
verification screen displays.
7. Click Continue. The main Self-Test screen displays.
57
Step 4 - Receiving Test Files

The self-test workflow contains a receive test, in which you receive a file from the
nuBridges Self-Test server. During this test, you need to monitor your Commerce
Suite console, as well as your inbox, to verify the receipt of the file sent from the
nuBridges test server.
1. From the main Self-Test screen, select Start Test 1. The Test 1 screen displays.
2. Click Start Test 1 to start the test. Once the test begins, the following screen
displays.
58
If this test is successful, the results are displayed and a file appears in your
inbox. If notices are turned on, a notice of a received file displays in your
notice directory. If the test is unsuccessful, an error message will be displayed.
If no results are returned within 3 minutes of starting the test, you should
consider the test unsuccessful and click Recheck Test 1 Results Now to repeat
the receive test.
3. When you have successfully finished the receive test, click Continue. The main
Self-Test screen displays.
Error Code Example

If the receive test is not successful, an error code displays. A common error you may
see during this test is error code 5391, indicating that the nuBridges Self-Test server
cannot connect to server. This generally indicates an incorrectly configured Firewall,
or that Commerce Suite was not started prior to testing.
59
Step 5 - Sending Test Files

The self-test workflow contains a send test, during which the application checks a
database to verify that the file was received successfully by the self-test server. If
notice records are turned on, you can validate the receipt of each file by checking your
notice directory for a record of the send. You can also use the Commerce Suite server
console to monitor the files being sent.
Note: Ensure that the icssvr application is running before performing this test.
Follow the steps below to begin sending the test file.
1. From the nuBridges Self-Test main screen, select Start Test 2. The Test 2
screen displays.
This test verifies that you can send a file to the nuBridges test server. It displays
a send command to use for testing.
2. Make sure the Commerce Suite command window is open.
60
3. Copy and paste the send command shown on the Send Test screen into the
Commerce Suite command window.
or
Enter the command manually in the Commerce Suite command window.
4. Click Check Test 2 Results. If this test is successful, and you have notice
records turned on, an outbound file notice is sent to the notice directory.
This completes connectivity testing on the Commerce Suite server. You can now
proceed to configuring and testing with your external trading partners.
Note: At any time during your testing, you can click Reset Tests to start the testing
procedure over from the beginning.
61
Chapter 8: Understanding Commerce Suite
Files and Directories
Introduction .................................................................................................... 63
About Commerce Suite Files and Directories................................................ 63
Chapter 8: Understanding Commerce Suite Files and Directories
Introduction
Introduction
Prior to installation, you are asked to create an nuBridges directory. The nuBridges
directory acts as a repository for files and folders used to interact with other trading
partners defined in your Commerce Suite configuration. For this reason, the nuBridges
directory can be considered a support directory for the nuBridges products installed on
your system.
About Commerce Suite Files and Directories

The files in the nuBridges directories are essential for ensuring the nuBridges
application operates correctly on your system. In addition to properly executing the
application, the application files perform the following types of functions:
• Inbound/outbound document storage

• System activity logs
• Public key infrastructure certificate and private key storage
• Receipt storage
• The following types of files are stored in the nuBridges folders:
• Status or event files
• Work order files
• Failed transaction files
The following table illustrates the directory structure created for you by Commerce
Suite Manager during Commerce Suite configuration. This directory structure also
provides an example of a typical structure you might create as a repository for files
you use when exchanging EDI data with other trading partners.
Installation Directories
Directory Contents
error Contains files that could not be sent or properly received.
inbox Default inbound document storage location.
log Contains daily log files of system activity.
notice Contains status files indicating results of document transactions.
outbox Contains outgoing files.
pki Default location for all certificate and key files.
receipt Location of AS2 receipt documents.
workorder Location of instruction (.wo) files providing parameters for sending files.
63
Introduction .................................................................................................... 65
Starting and Stopping Commerce Suite......................................................... 65
For Windows.....................................................................................................................65
For UNIX...........................................................................................................................65
Starting Commerce Suite Server................................................................................65
Stopping Commerce Suite Server ..............................................................................65
Testing Trading Partner Connectivity ............................................................. 66

Editing AS2 Names........................................................................................ 68
Editing Your IP Address ................................................................................. 69
Editing Firewall Information ........................................................................... 69
Configuring for HTTPS or Secure FTP .......................................................... 70
Configuring for AS1 or Alerts ......................................................................... 71
Monitoring the Commerce Suite Log File ...................................................... 72
Running Commerce Suite Server as a Windows Service.............................. 74
Installing Commerce Suite as a Windows Service ...........................................................74
Installing with a Specific Service Name......................................................................75
Starting Commerce Suite as a Windows Service .............................................................75

Stopping Commerce Suite as a Windows Service............................................................76
Running Commerce Suite in the Background on UNIX Systems .................. 76

Running Commerce Suite as a Daemon on UNIX Systems.......................... 77
Introduction
Introduction
This chapter provides information procedures you may need to execute after installing
Commerce Suite.
Starting and Stopping Commerce Suite

This section provides instructions for starting and stopping Commerce Suite.
Although it is not necessary to start Commerce Suite prior to setting up its

configuration, you may run the program prior to its configuration to ensure that the
Commerce Suite executable has not been damaged or digitally altered.
For Windows
Follow the steps below to start Commerce Suite.
1. Use Windows Explorer to navigate to the directory where the icssvr.exe file is
located.
2. Double-click the icssvr.exe file to start the Commerce Suite application.
For UNIX
This section provides instructions on how to start and stop Commerce Suite on a
supported UNIX platform.
Starting Commerce Suite Server

Follow the steps below to start Commerce Suite server on a supported UNIX platform.
1. Open a terminal session.
2. Navigate to the isoft directory (/opt/isoft).
3. Enter ./icssvr to start the Commerce Suite server.
Stopping Commerce Suite Server

To stop Commerce Suite server on a supported UNIX platform, type shutdown at the
Commerce Suite command prompt.
65
Testing Trading Partner Connectivity

You can perform a connectivity test for every trading partner you add to your trading
community.
The trading partner test enables you to send a test file to your trading partner that will
verify that your Commerce Suite instance can send an encrypted file using a digital
certificate and requesting signed receipt.
Follow the steps below to test your connectivity with one of your trading partners.
opens.
2. Click the Testing tab to open the Testing page.
66
3. Complete the screen using the field descriptions below.
Select Trading
Partner Select a trading partner from the drop down list.
Select File To Send Enter the name of the file you want to end, or click the
browse button to select the file.
Encrypt File
Before Sending? Specify if you want to test Commerce Suite encryption.
Your choices are Yes and No.
Use Digital
Signature? Specify if you want to test using a digital signature.
Your choices are Yes and No.
Request Signed
Receipt? Specify if you want to request a signed receipt with your
test file. Your choices are Yes and No.
4. Click Send Test File. The test file is sent to the trading partner.
67
Editing AS2 Names
Editing AS2 Names

Follow the steps below to configure additional AS2 names or edit existing AS2 names
using the CSM:
opens.
2. Click the CSM Settings tab to view your Commerce Suite settings.
3. Click Add Name to add a new AS2 Name.
4. Enter the new AS2 name in the Add AS2 Name field (maximum 32
characters).
5. Click Save to save your changes.
6. Click OK. The new AS2 name displays in the My AS2 Names list.
7. Select the File menu Save Config File option to keep your modified values, or
click Cancel to discard your changes.
8. Select the File menu Write Configuration File option to write your Commerce
Suite Manager modifications to the configuration file.
9. From the File menu, select Exit. Commerce Suite Manager closes.
68
Editing Your IP Address
Editing Your IP Address

Follow the steps below to edit your IP Address using the Commerce Suite Manager .
1. Start the Commerce Suite Manager. The Commerce Suite Manager main
window displays.
2. Click the CSM Settings tab. Your Commerce Suite settings display.
3. Under My IP Configuration, click Edit. The My IP Address and http Port

fields become active.
4. This is the actual address and port of the machine that runs the Commerce Suite
server (icssvr).
5. Enter your new IP address and http port in the appropriate fields.
7. From the File menu, select the Save Config File option to keep your modified
values, or click Cancel to discard your changes.
8. From the File menu, select the Write Configuration File option to write your
Commerce Suite Manager modifications to the configuration file.
Editing Firewall Information

Follow the steps below to edit your firewall information using Commerce Suite
Manager.
opens.
2. Click the CSM Settings tab to view your Commerce Suite settings.
3. Under Firewall Configuration, click Edit.
4. Enter your firewall address and port number in the Firewall IP Address field.
5. Click Save.
7. From the File menu, select the Write Configuration File option. Commerce
Suite Manager writes the modifications to the configuration file.
69
Configuring for HTTPS or Secure FTP
Configuring for HTTPS or Secure FTP

When configuring an HTTPS or Secure FTP trading partner, you must ensure that
HTTPS keys have been defined prior to assigning the relationship protocol. These
keys can be configured using the CFG Setting page of the CSM application.
Follow the steps below to configure an HTTPS or Secure FTP trading partner using
Commerce Suite Manager.
opens.
2. Click the CFG Settings tab. Your Commerce Suite HTTPS configuration
settings display.
3. Under HTTPS configuration, click Edit. The Public and Private Key fields
are enabled.
4. Click the ... (Browse) button next to the Public Key field to select a public key.
5. Click the ... (Browse) button next to the Private Key field to select a private
key.
6. Enter your HTTPS port number in the https Port field.
7. Click Save.
70
Configuring for AS1 or Alerts
Configuring for AS1 or Alerts

If you are using AS1 trading relationships, you must configure SMTP and POP3 server
information. If you are configuring for email alerts, you will need to configure for a
SMTP server, alert level, and alert email address.
Follow the steps below to configure an AS1 trading partner using the Commerce Suite
Manager.
opens.
2. Click the CFG Settings tab. Your Commerce Suite HTTPS configuration
settings display.
3. Under SMTP/POP3 Configuration, click Edit. The SMTP and POP3 related
fields are enabled.
71
Monitoring the Commerce Suite Log File

Follow the steps below to monitor the Commerce Suite log file via Commerce Suite
Manager.
opens.
2. Select the Logging tab. The Commerce Suite log file displays.
3. Click the ... (Browse) button next to the Select Current Log File field and
select a log file to monitor.
4. In the Number of Lines to Read field, enter the number of lines that will be
displayed from the end of the file.
72
5. Click View a Log File to start the file viewing cycle. The file contents will be
refreshed every 10 seconds.
Suite Manager writes modifications to the configuration file.
8. From the File menu, select the Exit. Commerce Suite Manager closes.
73
Running Commerce Suite Server as a Windows Service

Running Commerce Suite as a service in Windows NT, Windows 2000, or Windows
XP Professional provides the following functionality:
• Windows can start the Commerce Suite server application during the Windows
system initialization process and stop the application when Windows is shut
down.
• The Windows system administrator can use Windows services to manually start
or stop the service from the local machine that hosts Commerce Suite.
• Multiple users of a single machine hosting the Commerce Suite application can
log on and off without disruption to the Commerce Suite application.
The following topics are provided for using Commerce Suite as a Windows service:
• Installing Commerce Suite as a Windows Service

• Starting Commerce Suite as a Windows Service
• Stopping Commerce Suite as a Windows Service
Installing Commerce Suite as a Windows Service

Before you can run Commerce Suite as a Windows service, you must first install it as
a service and place it in the Windows services list.
From a command line prompt on your Windows machine, type the following:
icssvr -install
This places the Commerce Suite application in the Windows service list. You can now
start the service either from the command line or from the Administrative Tools >
Services option in the Windows Control Panel.
Note: When running as an Windows service, Commerce Suite receives all commands
via work orders. The icssvr.cfg file must have the -of option set in order to allow
proper communication with the application. Please review the nuBridges Commerce
Suite Command Reference for more information on the -of option.
74
Installing with a Specific Service Name

You can install Commerce Suite as a service with a specific service name. This allows
you to have more than one installation of Commerce Suite on a single server, and run
these installations as services.
Follow the steps below to install Commerce Suite as a service with a specific service
name
1. Open the icssvr.cfg file using a text editor (e.g., Notepad).
2. Add the following two lines above the opening <xml> tag:
[Settings]
ServiceName = <service_name>
where <service_name> is the name of the specific service.
Starting Commerce Suite as a Windows Service

You can use the Windows Control Panel to start Commerce Suite manually or
automatically upon system startup.
1. Select Start > Control Panel > Administrative Tools Services. The list of
installed Windows services displays.
2. Select icssvr from the services list and choose Action > Properties. The
Properties dialog displays.
3. From the Startup Type drop down list, select Manual to manually start
Commerce Suite or select Automatic to start Commerce Suite automatically
when the system is booted.
75
Running Commerce Suite in the Background on UNIX Systems
Stopping Commerce Suite as a Windows Service

You can stop Commerce Suite running as a Windows service from the Windows
Control Panel.
To stop Commerce Suite from the Control Panel:
1. Select Start > Control Panel > Administrative Tools Services. The list of
installed NT services displays.
2. Select icssvr from the services list and choose Action > Stop. This stops the
To stop Commerce Suite from the command line, enter the following command:
net stop icssvr
To remove Commerce Suite from the Windows services list, enter the following
command:
icssvr -remove
Running Commerce Suite in the Background on UNIX Systems

Execute the following command to run Commerce Suite in the background on a UNIX
server.
icssvr -e
This command completely frees the Commerce Suite application from a term session
and will survive any interruption with the exception of a hardware change.
Note: Adding nohup to the command (e.g., nohup icssvr -e) causes the daemon to
ignore SIGHUP, if needed.
76
Running Commerce Suite as a Daemon on UNIX Systems
Running Commerce Suite as a Daemon on UNIX Systems

Use the following script as either a command line startup and shutdown, or as a boot
init script.
case “$1” in
‘start’)
if [ -f /opt/isoft/icssvr ]; then
cd /opt/icssvr
nohup icssvr -e
fi
;;
stop’)
/usr/bin/pkill -x -u 0 ‘(icssvr)’
;;
*)
echo “Usage: $0 { start | stop ]”
exit 1
;;
esac
exit 0
77
Appendix A: Conducting Manual
Commerce Suite Operations
Introduction .................................................................................................... 79
Starting and Stopping Commerce Suite......................................................... 79
Starting Commerce Suite..................................................................................................79
Stopping Commerce Suite ................................................................................................80
Checking Commerce Suite Status ....................................................................................80
Understanding Configuration and Work Order Files ...................................... 81

What is the icssvr.cfg Configuration File?.........................................................................81
Rules for Editing the icssvr.cfg File ............................................................................83
Editing the icssvr.cfg File Manually ............................................................................83
What are Work Order Files? .............................................................................................84
Sending Data ................................................................................................. 85

Performing One Time Sends ............................................................................................85
Sending Data Automatically..............................................................................................86
Introduction
Introduction
This appendix contains the following sections:
• Starting and Stopping Commerce Suite

• Understanding Configuration and Work Order Files
• Sending Data

To demonstrate how to start and stop the Commerce Suite server from a DOS
command prompt, this section assumes a Windows operating system platform with a
base directory named c:\isoft\icssvr.
Starting Commerce Suite

Follow the steps below to start Commerce Suite.
1. Open a command prompt console window.

2. Change your directory to the c:\isoft\icssvr directory.
3. Type icssvr and press ENTER.
c:\isoft\icssvr\icssvr
Once the program properly initializes, a console window similar to the one
below displays.
When the initialization tasks are complete, a blinking cursor appears below the
title message. The Commerce Suite application is now ready to accept
commands from the local console.
Although the Commerce Suite application can accept console command at any
time, it may be more desirable to have Commerce Suite read configuration
commands from a configuration file. It is also possible to enter configuration
commands as command-line arguments when the application is started.
79
Stopping Commerce Suite

Depending on the To stop the Commerce Suite application process, enter shutdown in the Commerce
number of active threads, Suite console window. The shutdown command gracefully terminates any operating
several seconds may elapse
before the application thread within the process and then terminates the process itself. The following type of
terminates completely. information displays.
Checking Commerce Suite Status

At any time during the execution of the application, the current general status of the
application can be displayed at the host-computer’s console by entering the status
command. The application will display several lines of information representing the
status of the application.
For more information on

the start gui command
command, please review the
nuBridges Commerce Suite
Command Reference.
To check the status of a Commerce Suite instance when running as an NT service, you
must use the start gui command prior to checking the status.
80
Understanding Configuration and Work Order Files

You can configure Commerce Suite in several ways - through console commands,
local configuration files, or by a remote Administrative Agent. The following section
describes the icssvr.cfg configuration file and the work order (.wo) files that are loaded
and read upon Commerce Suite application startup.
What is the icssvr.cfg Configuration File?

The Commerce Suite configuration file, icssvr.cfg, is an XML-formatted text file
containing configuration commands that are loaded and read each time Commerce
Suite is started. In a clustered environment, this configuration file contains commands
that enable a Commerce Suite instance to act as either a Transport, Router, or
Administrative Agent. This file also contains trading partner information specifying
inbound and outbound definitions, certificate assignments, and commands to invoke
trading partners listeners on IP addresses and ports.
Because the icssvr.cfg file is a text file using an XML command structure, all
configuration files must begin with a beginning xml tag (<xml>) and end with an xml
tag (</xml>).
Warning: Do not include a new-line or carriage-return and line-feed combination

between the <command> tag and the </command> tag. Doing so will result in
Commerce Suite generating errors as the configuration file is parsed.
The following sample icssvr.cfg configuration file is created using the following
command categories:
• set - updates the server variable

• addpair - defines a new trading partner relationship
• importkey - assigns certificates to be used for trading partner relationships
• start - starts an inbound controller or service
81
Sample icssvr.cfg File
<xml>
<comment>configuration settings</comment>
<command>set -eperror -ef</command>
<command>set -lplog -lf</command>
<command>set -npnotice -nf-</command>
<command>set -opworkorder -oswo</command>
<command>set -pppki</command>
<command>set -rpreceipt</command>
<command>set -tr300s</command>
<command>set -hno -hni</command
<comment>iSoft Testing</comment>
<command>addpair MyName ISOFTAS2TEST

http://selftest.isoft.com:4080↵
http://yourip:4080/ MyName inbox </command>
<command>addpair ISOFTAS2TEST MyName↵

http://127.0.0.1:5080/*↵
ISOFTAS2TEST inbox </command>
<comment>iSoft certificates and keys</comment>↵
<command>importkey MyName ISOFTAS2TEST E↵

-fCpki/MyName.cer↵
-fKpki/MyName.prv</command>
<command>importkey MyName ISOFTAS2TEST J↵

-fCpki/ISOFTAS2TEST.cer</command>
<command>importkey ISOFTAS2TEST MyName E↵

-fCpki/MyName.cer -fKpki/MyName.prv</command>
<command>importkey ISOFTAS2TEST MyName J↵

-fCpki/ISOFTAS2TEST.cer</command>
<comment>start services</comment>
<command>start http://127.0.0.1:5080/</command>
</xml>
82
Rules for Editing the icssvr.cfg File

Consider the following issues before editing the configuration file:
1. Always save and copy your icssvr.cfg file before editing it.
2. If you manually edit the configuration file while the Commerce Suite
application is active, any changes you make will not be active until you restart
the application. Furthermore, any changes made through console commands
will not be made permanent unless they are added to the icssvr.cfg file.
3. No validation or value checking occurs while you are editing the icssvr.cfg file.
Any errors detected will be displayed on the console when the application
starts.
Editing the icssvr.cfg File Manually

nuBridges recommends that you use a standard text editor, such as Notepad to modify
the icssvr.cfg file. Do not edit the icssvr.cfg file using a word processing program, such
as Microsoft Word.
Note: If you use Notepad to edit the icssvr.cfg file, make sure that it does not
automatically append a .txt extension to the filename.
83
What are Work Order Files?

Work order files are XML-formatted text files containing valid Commerce Suite
commands like those found in the icssvr.cfg file. Work order files end with a .wo
extension to designate them as work order files. A work order file provides an easy
method for storing single or multiple commands used to process work.
The following example shows the contents of a sample work order file, sendfile.wo.
Sample SendFile.wo Work Order File
<xml>
<command>send http CompanyA CompanyB -fNtest.txt↵
-n1</command>
</xml>
Commands listed in a work order file may be submitted to the Commerce Suite
command queue in the following ways:
• Work order files can be opened and executed using the Commerce Suite batch
command.
Example: batch sendfile.wo

• The icssvr.cfg file can be edited so that Commerce Suite monitors a directory
for the presence of work order files upon startup. When Commerce Suite
detects a work order file, it places the work order file in the Commerce Suite
command queue.
For example, the following entry in an icssvr.cfg file setups a work order
directory that Commerce Suite monitors for files that have a .wo extension:
<command>set -opworkorder -oswo</command>
84
Sending Data
Sending Data
Commerce Suite can be configured to perform manual one time sends or automatic
(persistent) sends depending on your organizations needs.
Performing One Time Sends

Commerce Suite supports manual one time sends using the send command. The send
command initiates an outbound transmission of data and may be issued from the
console.
The following sample command provides the syntax you must use to initiate a one
time data send. Type the following command line at the console window to enable
your one-time send.
<command>send http <fromas2name> <toas2name>↵

-fN<filename> -n5 -s -r1 -e</command>
The following parameter explanations apply to the previous code sample:
• The send http <fromas2name> <toas2name> command specifies the trading

partner sending the data, and the trading partner receiving the data.
• The -fN<filename> parameter specifies the filename to send. You must specify
the fully-qualified path for the file unless the file is located in the working
directory.
• The -n5 parameter specifies the maximum number of send attempts. In this
case, the number of send attempts is limited to five.
• The -s parameter specifies to request a digital signature.
• The -e parameter specifies to use DES3 encryption on the data being sent.
• The -r1 parameter specifies to use the SHA1 algorithm to verify the files
integrity, and requests a SHA-1 hashed-signed receipt.
85
Sending Data
Sending Data Automatically

The send command also supports persistent sends. Persistent sends scan a directory at
regular intervals looking for a file to send. When a file is located, Commerce Suite
sends the first file listed in the directory.
The following code provides an example of a persistent send command:
send http sender receiver -fPoutbox -fSout -fE.processing↵

-tC30s -tE20040101000000 -s -r1 -e -x
The following parameters are required when editing the icssvr.cfg file for persistent
sends: -fP, -fS, -fE, -tC, -tE.
The following parameter explanations apply to the previous code sample:
• The send http sender receiver command specifies the trading partner sending
the data, and the trading partner receiving the data.
• The -fPout parameter specifies the path where the file being sent is located.
• The -fSout parameter specifies the name of the file to be sent.
• The -fE.sent parameter specifies to add the .sent extension to the file after it is
sent.
• The -tC60s parameter specifies that there should be an interval of 60 seconds
between directory scans to search for files to be sent.
• The -tE20040101000000 parameter specifies that the message should be sent
until the specified date and time (Year, Month, Day, Hour, Minute, Second).
86
1000 Abernathy Road · Building 400, Suite 250 · Atlanta, Georgia 30328
800.251.4930 toll free · 770.730.3600 main · 770.730.3784 fax
info@nubridges.com · www.nubridges.com
For technical support, call (866) 830-3600 or email support@nubridges.com.

Nubridges Commerce Suite™ Getting Started Guide: Ersion

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Nubridges Commerce Suite™ Getting Started Guide: Ersion

Hochgeladen von

Copyright:

Verfügbare Formate

nuBridges Commerce Suite™

Getting Started Guide

Document Version 08.07

Chapter 2: Preparing to Install Commerce Suite

Chapter 3: Commerce Suite Firewall Configuration Settings

Chapter 4: Licensing and Upgrading Commerce Suite

Chapter 5: Installing Commerce Suite

Chapter 6: Configuring Commerce Suite

Chapter 6: Configuring Commerce Suite, continued

Chapter 7: Testing Commerce Suite

Chapter 8: Understanding Commerce Suite Files and Directories

Chapter 9: Post Installation Considerations

Chapter 9: Post Installation Considerations, continued

Appendix A: Conducting Manual Commerce Suite Operations

About This Document

• Your business application software and business practices

Introduction to the Commerce Suite Documentation Set

• The Commerce Suite Release Notes describes new features, maintenance

Commerce Suite Documentation Roadmap

1. Commerce Suite Release Notes

2. Commerce Suite Getting Started Guide

3. Commerce Suite Database Connectivity Guide

4. Configuring Commerce Suite Clusters

Read... To Learn About...

Read... To Learn About...

Designates a warning or important piece of information.

Text Format Example Explanation

• Supports multiple data types, transport protocols, and security standards.

AS2 Communication Requirements

• nuBridges Commerce Suite software.

Roadmap for Establishing nuBridges Connectivity

1. Contact nuBridges to obtain a copy of the nuBridges Commerce Suite

2. Install the nuBridges Commerce Suite software.

3. Configure the Commerce Suite software and test with nuBridges.

Typical Commerce Suite Administrator Duties

• Installing Commerce Suite.

Commerce Suite System Requirements - UNIX ............................................ 13

This chapter provides information on how to prepare for a Commerce Suite

Commerce Suite System Requirements - Windows

• A Pentium-class processor running at 400 Mhz or faster

Much of this drive space requirement is necessary for database executables,

• One of the following Windows operating system versions:

Refer to the Chapter 5: Installing Commerce Suite chapter for instructions on

Administrator Rights for Windows NT and 2000

Recommended Software for Windows

Commerce Suite System Requirements - UNIX

• A Pentium-class processor running at 400 Mhz or faster

Recommended Software for UNIX

The Commerce Suite application running in your environment requires a static IP

Commerce Suite Firewall Considerations

1. Determine and record your firewall IP address.

6. Configure the firewall ports for TCP as the protocol.

7. If you are using Network Address Translation (NAT) to allow connections to

External Trading Partner Inbound Firewall Considerations

Inbound From nuBridges Test Server Configuration Information

IP Definition Configuration Value

External Trading Partner Outbound Firewall Considerations

IP Definition Configuration Value

This chapter provides information on generating licenses, licensing requirements, and

About License Key Generation

• TCP/IP configuration must be complete.

If TCP/IP configuration is not complete or is changed after installation, you must

Upgrading Your Commerce Suite Software