Installation guide

WebAccess

Product version 7.10

Date 7.10.1

Solutions of Generix Group

 C opyright

Generix Group may hold patents, applications for patents, or may own rights to trademark, copyright or other
intellectual property rights covering all or part of the components covered by this document. This guide does not
constitute in any case a license for these above-mentioned patents, trademarks copyrights or intellectual
property rights, unless otherwise stated in a written license agreement issued by Generix Group.

© 2010 Generix Group. All rights reserved. INFLUE is a registered trademark of GENERIX Group.

Disclaimer

Generix Group reserves the right to make changes to this document without prior notice. Except where otherwise
stated, names of companies, organizations, products, persons or events mentioned in this document are given as
example only. Any resemblance to actual names or events is coincidental. Users must comply with the Copyright
law applicable in the country of use. No part of this document shall be reproduced, stored or entered into a
retrieval system, or disseminated for any reason or by any means whatsoever, without the express written consent
of Generix Group.

Trademarks

The names of companies and products mentioned in this document are trademarks or registered trademarks of
their respective owners.

TradeXpress ®
Generix Group 2010 - All rights reserved 2
 Version History

Versioning Date Validation status

version 7.07.1 04/04/2007 Validated

version 7.08.1 08/23/2007 Update w3i_confedi.cfg file’s

description

version 7.09.1 06/02/2008 Added SCROLLING parameter in

w3i_confedi.cfg file

version 7.09a.1 03/06/2009 Added LDAP configuration

version 7.09a.2 08/11/2009 Minor corrections

version 7.09a.3 09/25/2009 Added LDAP parameters

version 7.10.1 03/18/2010 Added Charset parameters

Added Labels localization

TradeXpress ®
Generix Group 2010 - All rights reserved
 Table of contents

Version History ............................................................................................. 3

About this guide... ................................................................................. 6
General ....................................................................................................... 6
Target audience ............................................................................................ 6
Typographical Convention ............................................................................... 6
List of used acronyms ..................................................................................... 7
Other manuals on the WebAccess for TradeXpress module ....................................... 7
Technical Support ......................................................................................... 7

1 Presenting the module..................................................................... 9

General description ............................................................................... 10
Description of module components ............................................................ 11
Tree structure description ...................................................................... 12
Description of working files ..................................................................... 13
Session files ............................................................................................... 13
Database decription files ............................................................................... 13
Temporary filter files ................................................................................... 13
Permanent filter files ................................................................................... 13
LDAP cache file ........................................................................................... 13

2 Installing WebAccess ..................................................................... 14

Prerequisites ....................................................................................... 15
Installation details ................................................................................. 16
Module access tests ............................................................................... 18
Should a problem occur .......................................................................... 19

3 Configuring the server WEB ............................................................ 20

Introduction ........................................................................................ 21
Web server ................................................................................................ 21
Authentication and autorization ...................................................................... 22
Apache Configuration ............................................................................. 25
Virtual directories ....................................................................................... 25
Apache internal authentication................................................................................ 25
Authentification via a LDAP database ....................................................................... 27
Netscape configuration ........................................................................... 30
Virtual directories ....................................................................................... 30
Server protection ........................................................................................ 31
Microsoft Internet Information Server v3 configuration ................................... 34
Virtual directories ....................................................................................... 34
Server protection ........................................................................................ 36
Microsoft Internet Information Server v4 configuration ................................... 37
Virtual directories ....................................................................................... 37
Server protection ........................................................................................ 39
Microsoft Internet Information Server v5 configuration .................................. 40

4 Trace file ................................................................................... 46

TradeXpress ®
Generix Group 2010 - All rights reserved 4
 Table of contents

Introduction ........................................................................................ 47
Traced data ......................................................................................... 48

5 Parameters settings ...................................................................... 49

Initial configuration ............................................................................... 50
Accessing the configuration file ...................................................................... 50
Configuration file ........................................................................................ 50
Profile association for local users ............................................................................. 55
Profile association via LDAP .................................................................................... 55
Defining users ............................................................................................ 57
Configuring the configuration interface ..................................................................... 57
Using the configuration interface .................................................................... 58
Defining profiles ......................................................................................... 59
WebUser parameters............................................................................................. 59
Defining custom links ............................................................................................ 60
Uploading files..................................................................................................... 61
Accessing database ............................................................................................... 62
Options for accessing a database ..................................................................... 62
Coloring Entries ................................................................................................... 63
Setting filters ...................................................................................................... 63
Predefined actions ............................................................................................... 64
Configurable actions ............................................................................................. 65
List of authorized directories .................................................................................. 67
Specificities to directories ...................................................................................... 68
Renaming files ..................................................................................................... 69
Defining MIME viewing extensions............................................................................. 70
Access to the Manager Log ............................................................................. 70
Parameter settings for accessing the Logmgr database................................................... 70
Prerequisites to access Manager Log ......................................................................... 71
Troubleshooting................................................................................................... 71
w3i_access.profil example files ................................................................ 74
w3i_access.partner ...................................................................................... 74
w3i_access.userview .................................................................................... 74
w3i_access.userupdt .................................................................................... 74
w3i_access.exploitview ................................................................................ 75
w3i_access.exploitupdt ................................................................................ 75
w3i_access.admin ....................................................................................... 75
w3i_access.adminfull ................................................................................... 75
w3i_access.view ......................................................................................... 76
w3i_access.illicom ....................................................................................... 76

TradeXpress ®
Generix Group 2010 - All rights reserved 5
 A bout this guide...

General

This document explains how to install and configure the WebAccess for TradeXpress module:

Target audience

This document is aimed at administrators who wish to install and set up the parameters for
the WebAccess for TradeXpress module.

Typographical Convention

This guide uses the following typographical convention:

Type Signification
Bold Used for GUI items (menus, windows, buttons...) or for
highlighting important information

Italics Used for cross-references. Hypertext links are col-

ored in orange.

Code Used for examples of code, screen text

or commands.
Used for Warnings

Used for Notes

Used for tips, to access or operate a functionality.

TradeXpress ®
Generix Group 2010 - All rights reserved 6
 About this guide...

List of used acronyms

The following guide uses known acronyms and terms such as:

Terms or Acronyms Definition

CGI Common Gateway Interface
Communication protocol used between the WEB server and
the programs

RTE Reliable Translation Engine

TradeXpress programming language

HTML HyperText Markup Language

The HyperText pages description language

HTTP HyperText Transport Protocol

The transport protocol used on the WEB

HTTP/S HyperText Transport Protocol/Secure

The secure transport protocol used on the WEB

WEB World Wide Web

An Internet service that allows access to Hypertext
documents.

IIS Internet Information Server

Web Server for Windows NT platform

EdiUser The name given to an EDI user declared for TradeXpress.

Corresponds to an EDI environment.

WebUser The name given to a WEB user declared for WEB server
purposes.

Other manuals on the WebAccess for TradeXpress module

The WebAccess for TradeXpress module is supplied with the following manuals:

UserGuide

This document provides a generic presentation on how to use the various functions provided
by the WebAccess for TradeXpress module, assuming that these functions are authorized for
use by the user.

Programming guide

Distributed with the WebAccess Pro for TradeXpress module, this document presents the
programming files that can be used by programmers who want to define modification screens
for their own TradeXpress databases.

Technical Support

For more information or support regarding your TradeXpress software, do not hesitate to
contact your local reseller. Send your comments regarding the documentation content, by
email to: [email protected].

TradeXpress ®
Generix Group 2010 - All rights reserved 7
 About this guide...

TradeXpress ®
Generix Group 2010 - All rights reserved 8
1/ Presenting the module

General description
Description of module components
Tree structure description
Description of working files
 Presenting the module
General description

General description

The Web Access for TradeXpress module is the TradeXpress WEB client. It can be used with
HTTP or HTTPS (secure mode) protocols.

There are two versions of WebAccess:

• WebAccess for TradeXpress 4.x: this version consists in an optional module which provides,
using an Inernet browser, access to all TradeXpress Enterprise databases as well as to
application databases in TradeXpress format (Allegro, etc...).

• WebAccess for TradeXpress 5.0: this version is provided as standard and grants access only
to monitoring databases (syslog, logmanager, bplog, and archive).

In both version, the module handles additional functions such as: the file downloading, file
uploading, managing MIME viewing extensions, user profiles, or even menu customizing (color,
logo, ...).

The WEB Access Pro module offers the same features, but also allows creating user interfaces
for new TradeXpress databases

TradeXpress ®
Generix Group 2010 - All rights reserved 10
 Presenting the module
Description of module components

Description of module components

The WebAccess for TradeXpress module has been developed in RTE and in ‘C’. It uses the CGI
protocol to communicate with the WEB server.

The module is made up of several CGI scripts. These scripts may be found in the [EDIHOME]/
WebAccess/cgi directory:

Name Description
w3i_first.cgi The application entry point. Allows access to the databases
that the user is allowed to view and/or modify.

w3i_entries.cgi Displays database entries.

w3i_files.cgi Displays the files belonging to a database.

w3i_filter Enables to create/delete filters

w3i_page.cgi HTML pages analysis engine used to create and/or modify

entries in the database

w3i_upload.cgi Handles the upload of files on a server.

w3i_envexec_NT.cgi Used to execute a command (‘reprocess’, ‘mkscanfile’ or

w3i_envexec_UNIX.cgi other) within a process that is detached with the EdiUser
environment.

w3i_config.cgi The user management interface

w3i_test.cgi Debug script that presents all retrieved environment

variables.
Note: During the production phase, it is recommended to
delete this script as the information it provides may be used
by a hacker.

TradeXpress ®
Generix Group 2010 - All rights reserved 11
 Presenting the module
Tree structure description

Tree structure description

Installing the WebAccess for TradeXpress module will create the file layout shown below on
the EDI server.

Directory Description
[EDIHOME] Represents the TradeXpress installation directory

/WebAccess Represents the Web Access module installation directory

/cgi Contains the CGI scripts of the module

/conf Contains the configuration files

/html Contains the components used in the HTML pages

(Javascript libraries, stayle sheets, etc.).

/img Contains all the used pictures.

/w3i_html Contains the directories corresponding to the various

databases.

/databasename

...

Each w3i_html subdirectory contains the pages used to create/modify/view entries in the
corresponding database. It is therefore possible to add more to handle specific databases.

TradeXpress ®
Generix Group 2010 - All rights reserved 12
 Presenting the module
Description of working files

Description of working files

Session files

A session is created when the user is viewing a database. A file assigned to this session allows
to save the information a user enters into the various pages.

File name: [EDIHOME]/w3/W3_key.xxxxxxxxx

These files are deleted after 24 hours.

Database decription files

Two files are created each time a user views a database:

• the first one describes the format of each field in the database: [HOME]/base/w3/tmp/
W3_format.ref.

• the second one describes the name of each field in the database: [HOME]/base/w3/tmp/
W3_libelle.ref.

Temporary filter files

A temporary filter file is created to save the parameters of the filter being created; the filter
is shown in the interface with the name custom.

File name: [HOME]/base/w3/W3_key.xxxxxxxxx

These files are deleted after 24 hours.

Permanent filter files

Permanent filter files correspond to the filters a user define to view a database.

File name: [HOME]/base/w3/filtre.WebUser.flt

LDAP cache file

The LDAP cache file allows not to repeat frequent conections to the LDAP database

File name : [WAHOME]/conf/w3i_confedi.cfg.cache

TradeXpress ®
Generix Group 2010 - All rights reserved 13
2/ Installing WebAccess

Prerequisites
Installation details
Module access tests
Should a problem occur
 Installing WebAccess
Prerequisites

Prerequisites

The WebAccess for TradeXpress module works with the following WEB servers:

• Apache (for Windows or UNIX),

• Microsoft (PWS, IIS3.0 or higher),

• Netscape (Fastrack/Enterprise).

The Apache server is strongly recommended as the other induce the following restrictions:
- Microsoft: Webusers are not created automatically: the number of entries selected to
execute an action for a database is limited.
- Netscape: Webusers are not created automatically.

TradeXpress ®
Generix Group 2010 - All rights reserved 15
 Installing WebAccess
Installation details

Installation details

The WebAccess for TradeXpress 5.x module is installed as standard when installing
TradeXpress. However, you still need to configure access to the module.

If you use a previous version of WebAccess, do not forget to save WebAccess configuration
files before installing the module, in order to avoid these files to be overwritten during the
installation.

Étape 1: WEB configuration

Configure the WEB server and a WebUser (see Configuring the server WEB on page 20).

Étape 2.: Module configuration

Configure the WebAccess for TradeXpress module to allow access for a WebUser having
the w3i_access.adminfull profile (see Initial configuration on page 50).

Étape 3.: Configuring WEB redirection

To avoid having to enter systematically the full URL used to access the module, you can
use the index.html file located in the [EDIHOME]/WebAccess/html/index.html
directory. The latter contains the full URL used to access the module (see example file).

Étape 4.: Execution rights - logadd and logview (UNIX)

In UNIX, make sure the copied programs loggadd and logview in the [EDIHOME]/bin
directory have execution rights for everyone.

chmod +x logadd
chmod +x logview

Étape 5.: Execution rights - CGI scripts (UNIX)

In UNIX, make sure the CGI scripts present in the [EDIHOME]/WebAccess/cgi directory
have execution rights for everyone, have the « setuid bit » set, and belong the the ROOT
user from the EDUSERS group

chmod +xs w3i_*.cgi

chown root:ediusers w3i_*.cgi

Under UNIX, the setting of setuidbit allow an ordinary user to run a program as the user who
owns the file. Be careful to security problems this may cause.

TradeXpress ®
Generix Group 2010 - All rights reserved 16
 Installing WebAccess
Installation details

We recommend you to update your logview and logadd versions to get the latest module
evolutions (numbering).
For more details, refer to the WebAccess for TradeXpress User Guide, section About
numbering

TradeXpress ®
Generix Group 2010 - All rights reserved 17
 Installing WebAccess
Module access tests

Module access tests

1. Check the whole behaviour of the module by opening a WEB browser and calling the URL:

http://workstation/tradexpress/index.html

2. A login/password based authentication window should be displayed. Once authentication

is finished, you can access all the functions defined for your Profile.

The following elements must especially be tested:

• access to the ManagerLog which requires creating a dedicated directory (see Access to the
Manager Log on page 70),

• executing actions which with UNIX require the correct execution rights for CGI scripts (see
Installation details on page 16).

TradeXpress ®
Generix Group 2010 - All rights reserved 18
 Installing WebAccess
Should a problem occur

Should a problem occur

Refer to the log files of your WEB server. It traces all URL requests and infor you about the
error co,dition.

You can also call up the w3i_test.cgi script (name to be filled in the URL instead of
w3i_first.cgi), which inform you about the list of environement variables the WebAcess for
TradeXpress module receives.

TradeXpress ®
Generix Group 2010 - All rights reserved 19
3/ Configuring the server WEB

Introduction
Apache Configuration
Netscape configuration
Microsoft Internet Information Server v3
configuration
Microsoft Internet Information Server v4
configuration
Microsoft Internet Information Server v5
configuration
 Configuring the server WEB
Introduction

Introduction

Web server

To be able to use the WebAccess for tradeXpress module, you need to configure tyour WEB
server:

• to give access to the directories where the module is installed

• to secure the access to these directories

Three virtual directories needs to be defined:

Type of access Virtual directory Actual directory

Execution /tradexpress/cgi/ [EDIHOME]/WebAccess/cgi/

Read /tradexpress/img/ [EDIHOME]/WebAccess/img

Read /tradexpress/ [EDIHOME]/WebAccess/html/

Furthermore, identification/authentication is mandatory to access the directories presented

above.

The three sections below present the configuration parameters settings for Apache,
Netscape,Microsoft Internet Information Server v3, Microsoft Internet Information server v4
and Microsoft Internet Information server v5.

The Apache server is strongly recommended as the other induce the following restrictions:
Microsoft: Webusers are not created automatically: the number of entries selected to
execute an action for a database is limited.
Netscape: Webusers are not created automatically.

The use of HTTP/S protocol with the WebAccess module for TradeXpress is fully transparent.
The only impact is at the WEB server configuration menu level, as the module adapts
automatically to the protocol.

TradeXpress ®
Generix Group 2010 - All rights reserved 21
 Configuring the server WEB
Introduction

Authentication and autorization

The autentication of users is made via the Web server, i.e Apache. You can either:

• use the Apache configuration files in local mode (1)

• set a connection to a LDAP directory.(2)

Autorization rights are defined in the WebAccess configuration files.

You can link autorizations (permision profiles) to users:

1- in local mode:

• by the WebAccess module(3)

2 -Users are linked to autorization rights in a LDAP directory:

• either by the WebAccess module (4)

• either via Apache (be aware of prerequisites described in chapter Parameters settings).(5)

The following schema resumes the authentication and autorization options.

TradeXpress ®
Generix Group 2010 - All rights reserved 22
 Configuring the server WEB
Introduction

LOCAL

Configuration Configuration
Web Server WebAccess
1 3 User/Profile
User association
authentication

Http://URL_WebAccess

Permission
settings
Attempt to
connect

Web Server
(Apache)
Retrieving user
autorizations
Retrieving user
autorizations

REMOTE
5 4
(LDAP)
User
authentication

LDAP directory

The following table gives the list of step to complete according to the chosen configuration
mode.

TradeXpress ®
Generix Group 2010 - All rights reserved 23
 Configuring the server WEB
Introduction

Connectio Settings
Nbr Configuration Steps
n mode level
1 Local Apache Authentication Refer to the Apache internal
authentication section

2 LDAP Apache Authentication Refer to the Authentification via a LDAP

database section

3 Local WebAccess Association user/webuser/ Refer to the Initial configuration chapter,

profile Configuration file section Profile
association for local users part

4 LDAP Apache Association user/webuser/ Refer to the Authentification via a LDAP

profile database section

5 LDAP WebAccess Association user/webuser/ Refer to the Initial configuration chapter,

profile Configuration file section Profile
association via LDAP part

TradeXpress ®
Generix Group 2010 - All rights reserved 24
 Configuring the server WEB
Apache Configuration

Apache Configuration

Virtual directories

The configuration is set by using the srm.conf file where the virtual directories that allow
access to the module are defined.

# File srm.conf
# TradeXpress WWW Client Configuration
#
# Replace d:/tradexpress5/ with your EDIHOME
#
# NOTICE use /'s instead of \'s
#
ScriptAlias /tradexpress/cgi/ c:/tradexpress5/WebAccess/cgi/
Alias /tradexpress/img/ c:/tradexpress5/WebAccess/img/
Alias /tradexpress/ c:/tradexpress5/WebAccess/html/

In the above example, the virtual directories are defined as for Windows configuration. To
configure under Unix, use a path of the type: /usr/Tradexpress5/WebAccess/...

Apache internal authentication

The choice has been made to use the srm.conf and the access.conf file, in addition to the
httpd.conf file. Depending on the Apache version level used, you may have to allow reading
these files in httpd.conf by deleting the comment from the following lines:
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf
Nevertheless, you can copy the content of these two files at the end of the httpd.conf file

The configuration is set by using the access.conf, ediusers.w3 and edigroups.w3 files.

The access.conf file allow to define rules for accessing the module directories.

TradeXpress ®
Generix Group 2010 - All rights reserved 25
 Configuring the server WEB
Apache Configuration

# File access.conf
# TradeXpress WWW Client Configuration
# NOTICE use /'s instead of \'s
#
<Location /tradexpress/>
Options Indexes FollowSymLinks ExecCGI
AllowOverride AuthConfig
#
# Only Users in 'ediusers' group are allowed to use TradeXpress Client
#
<Limit GET POST>
order allow,deny
require group ediusers
allow from all
</Limit>
AuthName TradeXpress
AuthType Basic
AuthUserFile "c:/Program Files/apache/conf/ediusers.w3"
AuthGroupFile "c:/Program Files/apache/conf/edigroups.w3"
</Location>

The ediusers.w3 and edigroups.w3 files are automatically modified by the user management
interface of the WebAccess for TradeXpress module; however, to reach this interface, you
must have define a user. Therefore, you will be complied to manually modify these files the
first time.

The ediusers.w3 file lists the name of the Webusers and their passwords.

##########################################################
# Filename : ediusers.w3
# Description : This file gives password for all Web User
# Notice that both name and password are case sensitive.
# Update : Apache/bin/htpassword Apache/conf/ediusers.w3 newuser
##########################################################
#
admin:$apr1$ag/.....$2FHyDpsU1Hw097m5mly3/0
ediprod:$apr1$ag/.....$2FHyDpsU1Hw097m5mly3/0
viewprod:$apr1$ci/.....$lgsbvRJWU.JXMX.8fi8Qt/

To add a user and his password to the file, execute the following command:
APACHE]\bin\htpasswd [APACHE]\conf\ediusers.w3 login

The edigroups.w3 file lists the name of Webusers by group.

TradeXpress ®
Generix Group 2010 - All rights reserved 26
 Configuring the server WEB
Apache Configuration

# File edigroups.w3
# Description : Here you can specify which WebUser are ediusers
# Format :
# ediusers:ediprod view1 Demo
#
ediusers:ediprod viewprod

Modification of Webusers per group is done either via the user interface, or via the
edigroups.w3 file.

If users are modified via edigroups.w3, and are too many to be hold on the same line, you may
insert a line break with the character "/", which will tell teh module to read the following
lines.

If users are modified via the user interface, line breaks are not retranscripted into the file,
but are interpreted by the module. All users are displayed on the same line, but the missing
line breaks does not prevent the file to be red by the module.

Authentification via a LDAP database

We assume the system relies on any database entry containing the following attributes:

• cn (corresponds to the login name)

• userPassword (is used for the authentification)

• userClass (is used to define TradeXpress environement)

• bootFile (is used to stroe the configuration file path)

The described configuration is valid for Apache version 2.2.*; if other version, adjustments
may be needed.

To configure an authentification via LDAP directory:

1. Activate the LDAP module, by adding (or uncommenting) the following lines in the
httpd.conf file:

LoadModule authnz_ldap_module modules/mod_authnz_ldap.so

LoadModule ldap_module modules/mod_ldap.so

TradeXpress ®
Generix Group 2010 - All rights reserved 27
 Configuring the server WEB
Apache Configuration

2. Define the access rules to the module directories by modifying the access.conf file.

# TradeXpress WWW Client Configuration

# NOTICE use /'s instead of \'s
#
<Location /tradexpress/>
Options Indexes FollowSymLinks ExecCGI
AllowOverride AuthConfig
#
<Limit GET POST>
order allow,deny
allow from all
</Limit>
AuthName TradeXpress
AuthType Basic
AuthBasicProvider ldap
AuthLDAPURL ldap://xxx.xxx.xxx.xxx/dc=generix,dc=com?cn,userClass,bootFile?sub
Require ldap-filter &(userPassword=*) (bootFile=*) (userClass=*)
</Location>

Optional Bind LDAP

You can optionally add the following parameters:

AuthLDAPBindDN Nom_applicatif_connu_de_la_base
AuthLDAPBindPassword Mot_de_passe_bind

at the AuthLDAPURL parameter level if access have been set to the LDAP database.

These "minimal" settings may of course get more elaborated according to the needs and the
associated LDAP database.

The filter indicated here is only an example, to be adapted according to the structure of the
used LDAP database.

These modifications replace the current mechanism to authenticate to WebAccess wi th no

other needed modification, i.e. aliases and associated profile files remain to be defined in the
w3i_confedi.cfg configuration file, if userClass and bootFile parameters are not used.

Both authentication mecanisms may coexist, i.e. start a LDAP search, and if no result comes
from this search, search in the Apache configuration files for the autentication inormation.

Association profile/TXuser optional

You can ask Apache to supply the fields needed by WebAccess to resolve TradeXpress
environment and profile, allowing thus to avoid starting later an additional search into the
database.

To do so, you need first to have the attributes containing this information contained in the
same LDAP object than the User and Password information. Next, set Apache so as it passes

TradeXpress ®
Generix Group 2010 - All rights reserved 28
 Configuring the server WEB
Apache Configuration

these values in the HTTP framework, by adding the attributes name in the AuthLDAPURL (see
example below with userClass and bootFile attributes)

AuthLDAPURL ldap://xxx.xxx.xxx.xxx/dc=generix,dc=com?cn,userClass,bootFile?sub

(parameter to be set in the Apache configuration file)

Next you need to defin in the WebAccess configuration file (w3i_confedi.cfg) the following
parameters:

LDAP_VARNAME_EDIUSER=userClass
LDAP_VARNAME_PROFILE=bootFile

Adding these parameters allows not to set again a conection to the LDAP database to find the
correct values.

TradeXpress ®
Generix Group 2010 - All rights reserved 29
 Configuring the server WEB
Netscape configuration

Netscape configuration

Virtual directories

The configuration is set via the server administration interface.

Defining the virtual directory /tradexpress/cgi/

TradeXpress ®
Generix Group 2010 - All rights reserved 30
 Configuring the server WEB
Netscape configuration

Defining the virtual directories /tradexpress/img/ and /tradexpress/

Server protection

.Access restrictions are set via the administration interface, under the «Access control»
heading.

TradeXpress ®
Generix Group 2010 - All rights reserved 31
 Configuring the server WEB
Netscape configuration

Defining Webusers having access to the WebAccess module for TradeXpress.

TradeXpress ®
Generix Group 2010 - All rights reserved 32
 Configuring the server WEB
Netscape configuration

Shows that access to the service is controlled («Access control = on»)

TradeXpress ®
Generix Group 2010 - All rights reserved 33
 Configuring the server WEB
Microsoft Internet Information Server v3 configuration

Microsoft Internet Information Server v3

configuration

Virtual directories

The configuration is set via the server administration interface, as shown in the below
screenshots.

You can reach this interface via the Start>Programs>Microsoft Internet Information
Server>Internet Service Manager.

«Directory» tab of the administration tool

TradeXpress ®
Generix Group 2010 - All rights reserved 34
 Configuring the server WEB
Microsoft Internet Information Server v3 configuration

1/ Virtual directory /tradexpress/

2/ Virtual directory /tradexpress/cgi/

The creation of the virtual directory /tradexpress/img/is the same as for the directory /
tradexpress/

TradeXpress ®
Generix Group 2010 - All rights reserved 35
 Configuring the server WEB
Microsoft Internet Information Server v3 configuration

Server protection

The «Basic» authentication must be selected so that the server displays an identification grid
to the user. Furthermore, you will need to disable "anonymous" access.

Microsoft IIS v3 authentification settings

WebUsers who have access to the WebAccess for TradeXpress module are NT users. Therefore,
they need to be added from the «User manager» menu. Each user has to be given the «log on
locally» permission granted via the menu «User Rights Assignement».

TradeXpress ®
Generix Group 2010 - All rights reserved 36
 Configuring the server WEB
Microsoft Internet Information Server v4 configuration

Microsoft Internet Information Server v4

configuration

Virtual directories

The configuration is set via the server administration interface, as shown in the below
screenshots.

You can access the administration interface via Start>Programs>Windows NT4 Option
Pack>Microsoft Internet Information Server>Internet Service Manager.

Adminsitration interface

TradeXpress ®
Generix Group 2010 - All rights reserved 37
 Configuring the server WEB
Microsoft Internet Information Server v4 configuration

1/ Virtual directory /tradexpress/

2/ lVirtual directory /tradexpress/cgi/.

The creation of the virtual directory /tradexpress/img/is the same as for the directory/
tradexpress/

TradeXpress ®
Generix Group 2010 - All rights reserved 38
 Configuring the server WEB
Microsoft Internet Information Server v4 configuration

Server protection

The «Basic» authentication must be selected so that the server displays an identification grid
to the user. Furthermore, you will need to disable «anonymous» connections.

The screen below is obtained by choosing «Tradexpress» from the list of WEB sites defined for
the machine («Default Web site»).

Microsoft IIS v4 authentification settings

WebUsers who have access to the WebAccess for TradeXpress module are NT users. Therefore,
they need to be added from the «User manager» menu. Each user has to be given the «log on
locally» permission granted via the menu «User Rights Assignement».

TradeXpress ®
Generix Group 2010 - All rights reserved 39
 Configuring the server WEB
Microsoft Internet Information Server v5 configuration

Microsoft Internet Information Server v5

configuration

This chapter describes how to configure step by stype a server Web with IIS 5.0. The
configuration is made of three steps:

• Virtual directories declaration

• Server protection

• Webusers configuration

1. Go to the menu Start > Programs > Control panel > Administrative tools > Internet
Services Manager.

2. From the Internet information Service, unfold your server name.

3. From the left window pane, right-click on a Web site, point on New and click on Virtual
directory. A creation wizard is displayed.

4. From the first screen of the New Virtual Directory wizard, enter an alias or name for the
virtual directory (for instance Tradexpress), then click on Next.

5. From the next screen, you need to define the content directories of Tradexpress. You
need to repeat this operation for each directory. Click on Browse to select the path to a
WebAccess content directory.

Tradexpress directory

TradeXpress ®
Generix Group 2010 - All rights reserved 40
 Configuring the server WEB
Microsoft Internet Information Server v5 configuration

CGI directory

6. Give the following rights to each directory:

Tradexpress and img directories (read rights)

TradeXpress ®
Generix Group 2010 - All rights reserved 41
 Configuring the server WEB
Microsoft Internet Information Server v5 configuration

CGI directory (Execute rights)

7. Click then on Next to end the wizard.

Hereunder the site manager screen such as it should be displayed:

TradeXpress ®
Generix Group 2010 - All rights reserved 42
 Configuring the server WEB
Microsoft Internet Information Server v5 configuration

Site manager screen

The «Basic» authentication must be selected so that the server displays an identification grid
to the user. Furthermore, you will need to disable «anonymous» connections.

To do so:

1. From the Internet Information Services console, right click on the name of the site alias
(for instance: Tradexpress), click on Properties, then on the Directory Security tab. This
screen is displayed:

TradeXpress ®
Generix Group 2010 - All rights reserved 43
 Configuring the server WEB
Microsoft Internet Information Server v5 configuration

Directory security properties

2. Click on the Edit... button from the area Authentication and access control area. this
screen is displayed:

TradeXpress ®
Generix Group 2010 - All rights reserved 44
 Configuring the server WEB
Microsoft Internet Information Server v5 configuration

Authentification control

3. Uncheck the Enable anonymous connection box and check the Basic authentification
box. Define the default domain and the domain for users.

WebUsers who have access to the WebAccess for TradeXpress module are 2000 or XP users.
Therefore, they need to be added from the «User manager» menu. Each user has to be given
the «log on locally» permission granted via the menu «User Rights Assignement».

TradeXpress ®
Generix Group 2010 - All rights reserved 45
4/ Trace file

Introduction
Traced data
 Trace file
Introduction

Introduction

The WebAccess for TradeXpress module may be configured to keep a trace of all of the actions
that the users perform on the databases (except for basic connection/consultation actions).

Example of the parameter setting required in file w3i_confedi.cfg:

LOGFILE=%%CSTE_EDIHOME%%/WebAccess/log/logging

It is possible to use the %%CSTE_EDIUSER%% or %%CSTE_WEBUSER%% variables to specify a

filename that will be different for every user (EDI or WEB). It is also possible to use the
%%CSTE_DATE%% variable (date format is YYYYMMDD) so that a trace file can be created for
each day

TradeXpress ®
Generix Group 2010 - All rights reserved 47
 Trace file
Traced data

Traced data

The following information is saved:

• the date in DD/MM/YYYY format,

• the time in hh:mm:ss format,

• the IP address retrieved from the WEB server (REMOTE_ADDR environment variable),

• the name of the connected WebUser,

• the name of the corresponding EdiUser, between square brackets,

• the type of performed actions (ACTION, CREATION, MODIFICATION, DELETION,

DOWNLOAD),

• the detail action information (name of the database, file or index)

Example of trace file:

#28/09/2002 16:52:05 [192.168.72.204] pcahurel [ediprod]

DOWNLOAD base 'syslog'
(fichier=C:\TradeXpress4\users\pcahurel\syslog\files\xml\30)
28/09/2002 16:52:05 [192.168.72.204] pcahurel [ediprod]
ACTION 'c:\tradexpress4\bin\reprocess.exe
-C REPROCESS_ACTION=TRANSLATE 21'
28/09/2002 17:09:32 [192.168.72.204] pcahurel [ediprod]
CREATION base 'partner' (Index=80)
28/09/2002 17:09:42 [192.168.72.204] pcahurel [ediprod]
MODIFICATION base 'partner' (Index=80)
28/09/2002 17:09:47 [192.168.72.204] pcahurel [ediprod]
ACTION 'c:\tradexpress4\bin\logremove.exe
-s C:\TradeXpress4\users\pcahurel\partner -i 80'

TradeXpress ®
Generix Group 2010 - All rights reserved 48
 5/ Parameters settings

Initial configuration
w3i_access.profil example files
 Parameters settings
Initial configuration

Initial configuration

Accessing the configuration file

WebAccessThe configuration file's full name is given in the w3i_confweb.cfg file located by
default in the same directory as the CGI scripts ([EDIHOME]/WebAccess/cgi/). However, if
the W3I_FILECONF environment variable is defined, it is used in place of this file.

# File [EDIHOME]/WebAccess/cgi/w3i_confweb.cfg
# Description : Set the full pathname of webaccess configuration
file
#
../conf/w3i_confedi.cfg

Configuration file

The name and location of this file are described either in the w3i_confweb.cfg or in the
W3I_FILECONF environment variable (typically $EDIHOME/WebAccess/conf/
w3i_confedi.cfg).

It contains the general parameters that allow WebAccess for TradeXpress module to work
properly, as well as the user defintion of the module.

When a parameter is defined, it can be referred to by the %%CSTE_parametre%% variable

The first parameter must be the [EDIHOME] directory declaration

TradeXpress ®
Generix Group 2010 - All rights reserved 50
 Parameters settings
Initial configuration

# Filename : EDIHOME/WebAccess/conf/w3i_confedi.cfg
# Description : Configure the WebMonitoring module
#

# Directory to where TradeXpress is installed. MUST BE THE FIRST

FIELD !!!!

EDIHOME=/home/tx432

# URL of all CGI

WEBHOME=/tradexpress/

# Home directory of WebMonitoring

# default is %%CSTE_EDIHOME%%/WebAccess
WAHOME=%%CSTE_EDIHOME%%/WebAccess

# URL of images (default value is %%CSTE_WEBHOME%%img/)

IMAGES=%%CSTE_WEBHOME%%img/

# Compatibility Date for WebMonitoring

# Set COMPATIBILTY variable to hide or not some specials
# functions like the retry panel.
#-----------
# Some improvement's date :
# - "14.05.2004 11:51:45" : Add retry panel in partner.
# So with a prior date to this one, the panel retry will be hidden.
#-----------
# For BIGGEST compatibility then comment next line.
#COMPATIBILITY="01.05.2004"

# Parameter for tRFC use.

#TRFC_WORK_DIR=

TradeXpress ®
Generix Group 2010 - All rights reserved 51
 Parameters settings
Initial configuration

# Nbr of icons/line on first page. (default = 5)

#NBR_ICONS_LINE=4

# Choose look of GUI (graphic user's interface)

# possible value : 1, 2, 3. (default = 1)
WAGUI=1

# Time before update of List page (number of seconds, default=120)

PAGE_UPDATE=120

# Choose charset for display

TXP_WA_CHARSETS=iso-8859-1

# Use Frame or not to display base

# FRAME=YES display with frame, otherwise nothing.
FRAME=YES

# Allow scrolling for list of files on consulting base entry

# SCROLLING=YES display frame elevator if needed
#SCROLLING=YES

# Filter option (SIMPLE or DOUBLE) (default=SIMPLE)

FILTERSEL=SIMPLE

# menu for numbers of line on base display. (default =

10,50,100,500,ALL)
# 10 must be in the list (it's the default displayed value)
# COMBOBOX_NBR_LINES=5,10,25,250

# Language (used with images names and file LANGFILE)

LANG=FR

# File where all texts are defined (depend of LANGUAGE)

LANGFILE=%%CSTE_WAHOME%%/conf/w3i_language%%CSTE_LANG%%.cfg

# Log file
#LOGFILE=%%CSTE_WAHOME%%/conf/logging%%CSTE_DATE%%

# Size of first window (0 for no resize)

WIN_HSIZE=0
WIN_VSIZE=0

# Local mode for LOGVIEW , LOGADD, LSTOOL and EFTPGLUE

LOGVIEW=logview -l
LOGADD=logadd -l
LSTOOL=lstool

# Only for UNIX/LINUX without /etc/passwd file , there is the

possibility
# to define cmd line to obtain the uid and gid information.
# Sample for AIX:
# CMD_UID=lsuser -a id pgrp %%CSTE_EDIUSER%%(%%CSTE_EDIUSER%%
id=%uid pgrp=%edigroup)
# CMD_GID=lsgroup -a id %%CSTE_EDIGROUP%%(%%CSTE_EDIGROUP%%
id=%gid)

#Username to be displayed (WEBUSER or EDIUSER)

#USER_AFF=%%CSTE_EDIUSER%%

TradeXpress ®
Generix Group 2010 - All rights reserved 52
 Parameters settings
Initial configuration

# File where additionals actions are defined

#ACTIONFILE=%%CSTE_WAHOME%%/conf/w3i_action.cfg

# Default user to be used, if user is not found behind

DEFAULTUSER=ediprod

# Default access to be used, if access file is not set for user

DEFAULTACCESS=%%CSTE_WAHOME%%/conf/w3i_access.view

# config LDAP
LDAP_USE=YES
LDAP_VARNAME_EDIUSER=userClass
LDAP_VARNAME_PROFILE=bootFile
LDAP_BIND_DN=cn=yyyyyyyyyyy,ou=users,o=generix
LDAP_BIND_PASSWORD=cre
LDAP_URL=ldap://192.168.111.111/ou=WebAccess,o=generix
LDAP_FILTER=(bootFile=*)
LDAP_VERSION=3

PROFILE_DIRECTORY=%%CSTE_WAHOME%%/conf

CACHE_VALIDITY=120

# Description of all WebUsers.

# Keyword is USER, followed by WebUser, EdiUser, and Access File
USER=admin;ediprod;%%CSTE_WAHOME%%\conf\w3i_access.adminfull
USER=ediprod;ediprod;%%CSTE_WAHOME%%\conf\w3i_access.admin
USER=viewprod;ediprod;%%CSTE_WAHOME%%\conf\w3i_access.userview
USER=edib;edi_ob;%%CSTE_WAHOME%%\conf\w3i_access.adminfull

# Default access to be used, if access file is not set for user

DEFAULTACCESS=%%CSTE_WAHOME%%/conf/w3i_access.view
# Description of all WebUsers.
# Keyword is USER, followed by WebUser, EdiUser, and Access File
USER=admin;ediprod;%%CSTE_WAHOME%%\conf\w3i_access.adminfull
USER=ediprod;ediprod;%%CSTE_WAHOME%%\conf\w3i_access.admin
USER=viewprod;ediprod;%%CSTE_WAHOME%%\conf\w3i_access.userview
USER=edib;edi_ob;%%CSTE_WAHOME%%\conf\w3i_access.adminfull

Parameter Description
EDIHOME Is the TradeXpress installation directory.

WEBHOME Is the TradeXpress database virtual directory (/tradexpress/).

WAHOME Is the Webaccess installation directory.

The default value of this parameter is %%CSTE_EDIHOME%%/
WebAccess.

IMAGES Is the picture virtual directory.

NBR_ICONS_LINE Number of icons displayed in the home page. The default value is 5.

COMBOBOX_NBR_LINES Allows to define the drop-down menu options for the number of
entries to be displayed in a page.
10 is a mandatory value
All values should be separated with a colon (,)

TradeXpress ®
Generix Group 2010 - All rights reserved 53
 Parameters settings
Initial configuration

Parameter Description
WAGUI Allows to define the stylesheet to be applied.The default value of
this parameter is 1. Each value corresponds to a stylesheet:

- 1:w3i_style1.css
- 2:w3i_style2.css
- 3:w3i_style3.css

For more details, refer to the WebAccess Programing guide.

TXP_WA_CHARSETS Charset to be used for the Web pages display.

Some Web servers set the charset in HTTP

headers, which prevent a user from setting
the charset at WebAccess level. For instance,
under Apache, you need to have the
instruction "AddDefaultCharset off" in the
configuration file (httpd.conf) to deactivate
this behaviour.

PAGE_UPDATE Default refresh delay of databases (in seconds). «120» is the

default value

FRAME .Allows to display the databases in a frame mode (FRAME=YES), this

way, the action menu is still reachable.

SCROLLING SCROLLING=YES allows to have horizontal elevators into frames

when the frame’s size does not allow to display all the content
(truncated display)

FILTERSEL Defines the number of parameters for creating a filter. Two options
are offered:
- SIMPLE: one parameter
- DOUBLE: two parameters
The defaut value is SIMPLE

LANG Displayed language in the interface. «FR» for French or «EN» for
English.

For more details, refer to the WebAccess Programing guide,

section Labels definition.

LANGFILE Full name of the label definition file in the chosen language.

For more details, refer to the WebAccess Programing guide,

section Labels definition.

LOGFILE Full name of the trace file listing the actions performed by module
users.

WINH_SIZE Default width and height of windows used to access databases. By

WINV_SIZE default, automatic sizing. ‘0’, no sizing.

UPLOAD_PAR_FILE When set to NO, this parameter allows to deactivate the creation
of a PARxxxx file when a user uploads a file.

LOGVIEW Allows to redefine the program and the used options for «logview».

LOGADD Allows to redefine the program and the used options for «logadd».

LSTOOL Allows to redefine the program and the used options for «lstool».

TradeXpress ®
Generix Group 2010 - All rights reserved 54
 Parameters settings
Initial configuration

Parameter Description
CMD_IUD For UNIX/LINUX only. Allows to get the IUD or GID information
CMG_GID without having an /etc/passwd file.

USER_AFF Allows to detail the information displayed about the user: WebUser
or EdiUser

ACTIONFILE .Full name of the file for defining configurable actions.

DEFAULTUSER EdiUser used when the WEB identification procedure is disabled or

the WebUser is not defined.

DEFAULTACCESS Profile used when the WEB identification procedure is disabled or

the WebUser is not defined.

XXXXX_NOM Defines a pseudo-database, name of the «.cfg» file.

XXXXX_PATH Defines a pseudo-database, full access path.

Profile association for local users

In this case, you need to fill a specific parameter to assign a profile to a user

Parameter Description
USER Line used to associate WebUser↔EdiUser↔Profile.

Configuring this file with the definition of a WebUser with the right to access the user
configuration setting interface, is the minimum required so that the module can operate. The
other users will be defined via the interface.

Profile association via LDAP

In this case, the USER=... lines are not used anymore, information is retrieved from the LDAP
database.

The parameters to be used in the configuration file are the following:

Parameters Description
LDAP_USE YES states that the LDAP database is used to
authenticate.

LDAP_VARNAME_PROFILE used to define the LDAP attribute containing the

configuration file to be loaded for the
authenticated user. In the here above LDAP
configuration example, this attribute is ’bootFile’

LDAP_VARNAME_EDIUSER defines the TradeXpress environement where to

connect. In the here above LDAP configuration
example, this parameter indicates 'userClass'

TradeXpress ®
Generix Group 2010 - All rights reserved 55
 Parameters settings
Initial configuration

Parameters Description
LDAP_GROUP_NAME_FORMAT Variable which states if defined how the LDAP user
is found in the database.
This parameter allows to desceribe how to find:
• ’ environment
• the user profile link to this user.
%%PROFILE%% stands for the user profile;
%%ENV%% stands for the environment name
Example: WebAccess_%%ENV%%-%%PROFILE%%,
which corresponds to group names such as
WebAccess_ediuser-w3i_access.adminfull
(environment: ediuser, profile file:
w3i_access.adminfull), or WebAccess_ediprod-
w3i_access.view (environment: ediprod, profile
file: w3i_access.view)
When this parameter is filled, this deactivates the
use of LDAP_VARNAME_PROFILE and
LDAP_VARNAME_EDIUSER
Nota : To avoid any confusion, take a special
attention to the format name: in the previous
example, the use of '-' is not recommended, and
can be misleading : example: group name:
WebAccess_edi-prod-acces&vue, environment
name: edi-prod and profile file access&vue or
environement name: edi and profile file prod-
access&vue

LDAP_SEARCH_LOGIN_ATTRIBUT Variable which gives the attribute to be searched

when quering LDAP. This variable corresponds to
user login (if this parameter is not filled, the
considered default value is uniqueMember)

LDAP_BIND_DN Used to access the LDAP database

LDAP_BIND_PASSWORD Used to access the LDAP database

LDAP_URL URL of the LDAP database to be used

LDAP_FILTER filter to be used in order to retrieve only one single

LDAP database entry

LDAP_VERSION Version of the used LDAP protocol. Version 3 is the

recommended version.

LDAP_INFO Variable allowing to define if the LDAP database

output should be transformed into uppercase or
lower-case. When LDAP_INFO=MAJ, then the
retrieved information are to be used in uppercase.
If no value has been defined, or if it is different
from MAJ, then the information is considered as
lower-case

PROFILE_DIRECTORY Location of profile files, when only filenames are

stored in the LDAP database.
Recommended when using the
LDAP_GROUP_NAME_FORMAT parameter

CACHE_VALIDITY Validity duration of data retrieved from the LDAP

database. when expired, a LDAP query is run again.

If the user name used when searching an autorization into the LDAP database is not the

TradeXpress ®
Generix Group 2010 - All rights reserved 56
 Parameters settings
Initial configuration

autentication, you need to add a parameter to the Web server.

For instance, if the authentication relies on the uid attribute, but if the autorization is given
by the dn from the user stored into the LDAP database, you need to add if an Apache server is
used the following insrtuction :

AuthLDAPRemoteUserIsDN on

This instruction should be added at the AuthLDAPURL instruction level

Defining users

Apache

Only if LDAP is not used

Only if Apache is used

WebAccess for TradeXpress module has a user configuration interface defined by the
w3i_config.cgi script:

• variable :

- MODE_CONFIG=ADMIN (to be able to manage user accounts).

- MODE_CONFIG=USER (to be only able to change your password).
• defining an external link that allows access to the configuration interface (typically
http://machine/tradexpress/cgi/w3i_config.cgi)

The w3i_access.adminfull Profile file provided as an example in EDIHOME/WebAccess/conf/

w3i_access.adminfull contains this configuration settings.

The interface avoids having to modify manually the w3i_confedi.cfg file when creating/
modifying/deleting a user. When an Apache WEB server is used, the interface also handles
changes in the user definition files

Configuring the configuration interface

The configuration interface is automatically displayed until the configuration settings are
correct. Later, this page becomes accessible from the configuration interface (drop down
menu My options / Configuration).

TradeXpress ®
Generix Group 2010 - All rights reserved 57
 Parameters settings
Initial configuration

Configuring the configuration interface

This screen allows to define fundamental parameters anbling the inerface to work properly:

Parameter Description
Using choice lists Determines whether EdiUsers and Profiles are available
through popup lists or whether the user has to enter them
in full.

Sort by Profile or Sort by Ediusers States whether the list of defined users will be sorted by
Profile or by EdiUser.

Use Apache States whether an Apache WEB server is used. If so, the
next three parameters are required.

User creation program The full name of the Apache program used to create a user
with his password.

Group definition file The full name of the Apache file where the group users
with the right to access the protected directory are
defined.

User definition file The full name of the Apache where the passwords are
defined for all of the users with the right to access the
protected directory.

These parameters are saved into the file w3i_confusers.cfg located under [EDIHOME]/
WebAccess/conf

Using the configuration interface

Apache Once configured, the configuration interface displays the list of users defined for the
WebAccess for TradeXpress module. It then becomes possible to create or delete users.
Creation makes it possible to assign an EdiUser and a Profile to a WebUser, modifying allows
modifying a WebUser's password.

TradeXpress ®
Generix Group 2010 - All rights reserved 58
 Parameters settings
Initial configuration

Configuration interface - Users’ management

The writing into the edigroup.w3 file vary according to the origin of the modification (user
interface, or directly in the file.For more information, see Apache Configuration on page 25.

Defining profiles

The profile concept used in the WebAccess for TradeXpress module allows to define database
access rights and how the interface behaves according to the connected user.

These profiles are defined in the w3i_accesss.profil files located under [EDIHOME]/
WebAccess/conf].They are assigned to a WebUser↔EdiUser pair in the w3i_confedi.cfg file
(USER parameter).

The profiles files are made of:

• lines of «BASE» type, describing parameters or databases the user may access;

• lines of «CHAMP» type, describing parameters values or access restrictions to the

concerned database.

WebUser parameters

Some parameters defined at a general level (w3i_confedi.cfg file concerning all the
WebUsers) may be redefined for a specific profile.

The specific database «paramwebaccess» and lines of type «P» are used:

BASE;paramwebaccess
CHAMP;P;USER_AFF=%%CSTE_WEBUSER%%
CHAMP;P;LANG=FR
CHAMP;P;LANGFILE=%%CSTE_EDIHOME%%/WebAccess/conf/
w3i_language%%CSTE_LANG%%.cfg
CHAMP;P;MODE_CONFIG=USER

TradeXpress ®
Generix Group 2010 - All rights reserved 59
 Parameters settings
Initial configuration

List of parameters that can be redefined at the WebUser level:

• PAGE_UPDATE

• USER_AFF

• LANG

• LANGFILE

• WIN_HSIZE

• WIN_VSIZE

• MODE_CONFIG : Authorizes access to the user configuration interface.

It is possible to define a parameter of CSTE_xxxxx type to access its value from the database
modification pages (%%CSTE_parametre%% parameter). For more information, refer to the
Programing guide of WebAccess for TradeXpress module.

Defining custom links

It is possible to give access to additional links. These links may be of two types:

• Internal: To modify a file in format «Keyword=Value» using a WEB form.

• External: To call up an external URL (remote site, etc.).

Personal links

The specific database « personal » followed by the user name displayed in the drop-down
list is used.

Lines of type «I» for internal links are made of:

• the user name displayed in the drop down list.

• the full path name of the file to be modified (in relative notation from the [HOME]
directory)

TradeXpress ®
Generix Group 2010 - All rights reserved 60
 Parameters settings
Initial configuration

• the full path name of the HTML page allowing the file to be modified (from the
[EDIHOME]/WebAccess/w3i_html/xxxx directory)

Lines of type «X» for external links are made of:

• the user name displayed in the drop down list.

• the external URL address.

Parameters settings example:

BASE;personal;My options
CHAMP;I;FOO parameters;../../.foorc;userinfo/foo.html
CHAMP;X;Influe;http://www.influe.com
CHAMP;X;Configuration;%%CSTE_WEBHOME%%cgi/w3i_config.cgi

For more information on the programming of the HTML pages used by the module, refer to
the WebAccess for TradeXpress module Programming Guide.

Uploading files

The uploading of file to a server may be authorized for a profile.

The specific database «upload», followed by the name displayed in the drop down list is
used.

Lines of type «D» describing the uploading directories are made of:

• the name of the uploading path displayed in the drop down list of the Upload page.

• the full path of the uploading directories.

Parameters setting example:

BASE;upload;Upload
CHAMP;D;$HOME/inbox;%%CSTE_HOME%%/inbox
CHAMP;D;$HOME/bin;%%CSTE_HOME%%/bin

If the specific «personal» database is used, Upload is displayed as an additional option in this
menu (the option name is the one defined in the «BASE» type of line). If not, a menu is
created taking the name of the option.

TradeXpress ®
Generix Group 2010 - All rights reserved 61
 Parameters settings
Initial configuration

On UNIX, make sure the Ediuser has sufficient rights to create a file in the directory specified
for the uploading.

Accessing database

Access can be granted to any database in a TradeXpress format.

The «BASE» type of line is used to declare the databse. It is made of the database name and
the display mode (S: in a single window, M: in multiple windows).

Then, the lines of types «CHAMP» are used to define the behaviour of WebAccess for
TradeXpress module when viewing the database.

These lines are described in the following section.

Non standard database my be defined. This implies

- databases that are not located in the EdiUser’s [HOME] directory
- databases with a «.cfg» definition file that does not match with the named to be dislayed
-These non standard databases are defined in the w3i_confedi.cfg configuration file using
two parameters (XXXXX is the database name used in the Profile file and for display purpose):
- XXXXX NOM: Give the name of the «.cfg» file without its extension
- XXXXX PATH: Give the full name of the directory containing the «.cfg» file.

Options for accessing a database

Access to databases may be customized this way:

• Coloring entries,

• Setting filters

• Predefined actions,

• Configurable actions,

• List of authorized directories,

• Renaming files,

• Defining MIME viewing extensions

The database is searched by default in the EdiUser’s [HOME] directory, or in any user-defined
directory set in the w3i_confedi.cfg. The WebAccess for TradeXpress module expects to find
here a «.cfg» file having the same name as the database.

TradeXpress ®
Generix Group 2010 - All rights reserved 62
 Parameters settings
Initial configuration

Coloring Entries

Coloring database entry is done in relation to a condition of the value of a data of this
database. In some cases, several conditions may be verified, then the colour set for the last
verfied condition will be used.

The lines of type «C» used to set the color are made of:

• the name of the tested field (defined in the «.cfg» file of the database),

• the condition (<, >, <>, =),

• the expected value,

• the color to be used (in hexadecimal notation and RGB format)

Parameter settings example:

BASE;syslog;M
CHAMP;C;STATUS;=;ERROR;#F0AAAA

It is possible to used * and ? wildcards in the expected value of a field

Setting filters

WebAccess for TradeXpress module can be used to hide some database entries for a given
profile. This functionality is particularly useful when you want to limit the access only to
some syslog data streams.

The lines of type «F» used to hide entries are made of:

• ,the name of the tested field (defined in the «.cfg» file of the database),

• the condition (<, >, <>, =),

• the expected value,

• a flag indicating if the filtered field should be visible (V) or not (N).

Parameter setting example:

BASE;syslog;M
CHAMP;F;PARTNER;=;INFLUE;N

TradeXpress ®
Generix Group 2010 - All rights reserved 63
 Parameters settings
Initial configuration

It is possible to used * and ? wildcards in the expected value of a field

If you define a set filter with the filtered field set to not visible for a database, after other
filters have already been defined by the users via the WEB interface, then you will have to
manually delete the name of the filtered field from the [HOME]/base/w3/*.flt files.

Predefined actions

There are several standard actions that can be defined when viewing a database.

Parameter Description
CREAT Creating a new database entry.

MODIF Modifying the selected database entry.

SUPPR Removing the selected database entries.

VIEW Formatted view of the data assigned to the selected entry

FILE View of the files assigned to the selected entry.

REPROC Syslog database only.Reprocesses the selected entries.

EXPORT Exports the selected entries in a «dump» file.

IMPORT Imports a «dump» file.

Setting parameters example:

BASE;partner;S
CHAMP;A;CREAT;MODIF;SUPPR;IMPORT;EXPORT

The creation (CREAT), modification (MODIF) and formatted view (VIEW) use the HTML pages
located under [EDIHOME]/WebAccess/w3i_html/base/. WebAccess Pro for TradeXpress
allows you to access to your own databases. you will then need to develop the corresponding

TradeXpress ®
Generix Group 2010 - All rights reserved 64
 Parameters settings
Initial configuration

HTML pages if you want to modify there the entries.

Configurable actions

WebAccess for TradeXpress module allows to define its own actions that can be used on a
given database. Once the action is defined, it can be added to the list of authorized actions
for a database, just like predifined actions.

Configurable actions are defined in a file whose full name is specified in the w3i_confedi.cfg
file (ACTION parameter), typically [EDIHOME]/WebAccess/conf/w3i_action.cfg. It is made
of lines of type «MNEMO_PRO» (useless for pre/post command actions) and «MNEMO_CMD» where
MNEMO is the mnemonic used to name the action.

The lines of type «MNEMO_PRO» used to define the action’s properties are made of:

• the action’s full name (used in the drop down list of actions),

• A letter specifying if the action does not require the selection of an entry (Z), covers a
single entry (S), is to be run for each selected entry (M) or is to be run once a list of entries
has been selected (L).

Lines of type «MNEMO_CMD» are used to define the command to be run. The following variables
may be used:

Variable Description
%%CSTE_EDIHOME%% TradeXpress installation directory.

%%CSTE_HOME%% EdiUser’s basic directory.

%%CSTE_USER%% EdiUser’s name.

%%CSTE_IDXTMP%% Index of selected entries.

%%CSTE_FILEIDXTMP%% File containing the list of index for the selected entries.

%%CSTE_PATH_BASE%% Full path for accessing the database.

%%CSTE_FILTRE%% Full name of the filter used for viewing.

%%CSTE_BASE_BEFORE_SAVE%% File of the database’s data entries before modification.

Available for pre/post command actions. (CREAT,MODIF,
COPY) (v6.3).

%%CSTE_BASE_AFTER_SAVE%% File of the database’s data entries after modification.

Available for pre/post command actions. (CREAT,MODIF,
COPY) (>=v6.3).

Example of definition files of actions:

TradeXpress ®
Generix Group 2010 - All rights reserved 65
 Parameters settings
Initial configuration

PRINT_PRO=CONSULTER;S
PRINT_CMD=%%CSTE_EDIHOME%%/bin/opfile %%CSTE_IDXTMP%% print

Related parameter settings example:

BASE;syslog;S
CHAMP;A;FILE;REPROC;PRINT;IMPORT;EXPORT

Example of definition for a pre/post command action:

ACT1_CMD=%%CSTE_EDIHOME%%/bin/act1 %%CSTE_BASE_BEFORE_SAVE%%
ACT2_CMD=%%CSTE_EDIHOME%%/bin/act2 %%CSTE_IDXTMP%%

Related parameter settings example:

BASE;partner;S
CHAMP;A;FILE;REPROC;PRINT;MODIF/B.ACT1,A.ACT2;IMPORT;EXPORT

Where ACT1 and ACT2 are the actions’s mnemonic. If the action’s prefix is «A.» (for AFTER), it
is a post-command action (run after the command). If the action’s prefix is «B.» (for
BEFORE), it is a pre-command action (run before the commande).

Pre/post commande actions are enabled by WebAccess version 6.3 (or later)

The mnemonic used to name the action should not match with a predefined action.

Returns handling:

The command's return code is not tested. However, the STDOUT and STDERR output channels
are redirected to ensure three different behaviors:

TradeXpress ®
Generix Group 2010 - All rights reserved 66
 Parameters settings
Initial configuration

• No information on STDOUT and STDERR: No data on STDOUT and STDERR: the command
is run and the database's list of entries display page is displayed again.

• Information on STDOUT: the command is run and shows a page made of a title (action
name), the message retrieved from STDOUT, and a button allowing to get back to the
database’s list of entries display page.

• Information on STDERR: the command is run and shows a page made of a title (action
name), the message retrieved from STDERR and a button allowing to get back to the
database’s list of entries display page.

The STDOUT and STDERR datastreams is displayed without reformatting in the HTML page
and it may therefore contain HTML markers to obtain specific formatting results.

List of authorized directories

This functionality is only available for syslog, archive and managerLog databases.

It allows to specify the list of directories a user may view. This can be particularly useful to
hide directories not required, for example, the series of directories that may be displayed
when using attachements with the SMTP protocol.

Lines of type «L» used to make a list of authorized directories are made of:

• the expected value for the CONNECTION field,

• the list of visible directories, separated by semi-colons.

Parameter settings example:

BASE;syslog;M
CHAMP;L;SND_ORDERS;l;a;f;e;i;x

For more details about the directories’ names, refer to the WebAccess - User Guide, section
Actions on databases.

It is possible to used * and ? wildcards in the expected value of the CONNECTION field

TradeXpress ®
Generix Group 2010 - All rights reserved 67
 Parameters settings
Initial configuration

Specificities to directories

It is possible to define directories having a content type that differs from NAME=VALUE, as for
instance the $HOME/partner/info directory. To do so you need to put in the database
directory (e.g.: $HOME/partner) the users_dir.cfg file, with the DIR_NO_BASE variable like
shown herunder:

DIR_NO_BASE=rep1,rep2,...,repn

where repx stands for the various directories separated with a comma.

This way, the directories’s files will be saved regarding they are not of a NAME=VALUE type.

You can also prevent some directories to be taken into account, when a VIEW or MODIF action
is carried out. In this case, they won’t be modified and could only be viewed with the FILE
action. This can be usefull when unsing a trace file or a log file, assigned to each database
record, especially if these files are bulk files. To do so, use the DIR_NO_LOAD variable in
users_dir.cfg:

DIR_NO_LOAD=rep1,rep2,...,repn

where repx stands for the various directories separated with a comma.

Encodings may be defined for each database extension by specifying the following variables in
the file (example values):

DIR_PAGE_ENCODING.1.DIRLIST=l,lp
DIR_PAGE_ENCODING.1.VALUE=us-ascii

Where DIR_PAGE_ENCODING.x.DIRLIST gives the list of extension with a particular charset,

and DIR_PAGE_ENCODING.x.VALUE the value to be used as charset.

Example of users_dir.cfg file:

TradeXpress ®
Generix Group 2010 - All rights reserved 68
 Parameters settings
Initial configuration

# Avec fichiers <> de type NOM=VALEUR

DIR_NO_BASE=rep1,rep2

# Avec Fichier de log à ne pas charger

DIR_NO_LOAD=rep3

# les logs sont en charset ascii américain

DIR_PAGE_ENCODING.1.DIRLIST=l,lp
DIR_PAGE_ENCODING.1.VALUE=us-ascii

# le fichier in sont au format chinois

DIR_PAGE_ENCODING.2.DIRLIST=in
DIR_PAGE_ENCODING.2.VALUE=gb-18030

Renaming files

This functionality is only available for syslog, archive and managerLog databases.

It is used to display explicit names for the directories assigned to a database entry. This may
be useful for presenting explicit directory names to the user. This configuration setting is
made for a given connection name.

Lines of type «T» used to rename directories are made of:

• the expected value for the CONNECTION field,

• the name of the directory to be renamed,

• the name to be displayed for the directory,

• if needed, other parameters (described in chapter “Defining MIME viewing extensions” on

page 70)

Parameter settings example:

BASE;syslog;M
CHAMP;T;ORDERS_XML2EDI;l;logging
CHAMP;T;ORDERS_XML2EDI;a;application
CHAMP;T;ORDERS_XML2EDI;f;filtred
CHAMP;T;ORDERS_XML2EDI;e;edi
CHAMP;T;ORDERS_XML2EDI;i;interchange
CHAMP;T;ORDERS_XML2EDI;x;transport

It is possible to used * and ? wildcards in the expected value of the CONNECTION field

TradeXpress ®
Generix Group 2010 - All rights reserved 69
 Parameters settings
Initial configuration

Defining MIME viewing extensions

It is used to describe the type of display required for directory files assigned to a database
entry. The type is red by the WEB browser which triggers the appropriate display program.
This may be useful for presenting XML files with a style sheet or for presenting PDF files, for
example. This parameter setting is made for a given connection name.

Lines of type «T» (also used to rename directories) are made of:

• the three parameters related to the renaming (value of the CONNECTION FIELD, name of
the directory, name to be displayed)

• the suffix used in the file name when the user retrieves it.

• the MIME type declaration, used as is to send the file to the browser.

Parameter settings example:

BASE;syslog;M
CHAMP;T;ORDERS_XML2EDI;a;application;xml;Content-type: text/xml

It is possible to used * and ? wildcards in the expected value of the CONNECTION field.

Access to the Manager Log

Parameter settings for accessing the Logmgr database

The specific database Manager Log shows a syslog view of several Ediusers, an additional
column (EDIUSER field) providing the name of the EdiUser owning the data stream is
therefore added.

Lines of type «E» are used to make a list of Ediusers for where the syslog content is to be
viewed. They are made of the list of EdiUsers, separated by semi-colons.

The parameter settings options (color, filters, etc.) are the same as for the syslog.

Parameter setting example:

TradeXpress ®
Generix Group 2010 - All rights reserved 70
 Parameters settings
Initial configuration

BASE;logmgr;M
CHAMP;E;editest;ediprod
CHAMP;A;FILE;VIEW
CHAMP;C;STATUS;=;ERROR;#F0AAAA

It is possible to specify an EdiUser that does not use the same [EDIHOME] directory by
entering the full path used to access the EdiUsers directory. This may be useful in the (rare)
case when it is necessary to monitor the data streams for two instances of TradeXpress at the
same time.

Prerequisites to access Manager Log

This section lists the actions to be performed in order to ensure the running of Manager Log.

• The database type (edioldlegacy or SQLite) must be the same for all users.

• It is necessary to create the [EDIHOME]/logmgr directory so that the WebAccess for

TradeXpress module can store its working files there. Check that write privileges are
assigned to this directory.

Under Unix, run the command chown root:ediusers logmgr to assign the root:ediusers to
this directory.

• Syslogs of users members of the Ediuser group should have read rights

Under Unix, you can run the following commands:

chmod -R ug+rx users/editest/syslog
chmod -R ug+rx users/ediprod/syslog
chmod -R ug+rx users/editest2/syslog
chmod -R ug+rx users/editest3/syslog
etc.

Troubleshooting

1. If your operating system is Windows or Unix:

You need to give a name to the INDEX column. To do so, modify the users’ syslog.cfg files
as follows:

TradeXpress ®
Generix Group 2010 - All rights reserved 71
 Parameters settings
Initial configuration

#==============================================================
# Our names for the creation and modification times
# Note, that the header for index is just four spaces.
#==============================================================
INDEX=INDEX,%7d,
MTIME=MODIFIED,%d.%m.%Y %H:%M, Modified
CTIME=CREATED,%d.%m.%Y %H:%M, Created

into

#==============================================================
# Our names for the creation and modification times
# Note, that the header for index is just four spaces.
#==============================================================
INDEX=INDEX,%7d,Index
MTIME=MODIFIED,%d.%m.%Y %H:%M, Modified
CTIME=CREATED,%d.%m.%Y %H:%M, Created

Viewing the syslog is possible provided that each syslog satabase has been at least once-
accessed, i.e each user has viewed the syslog satabase at least once from its own
environment.

2. If your operating system is Windows:

The «Sort» utility is used to sort entries before displaying data on screen.

WebAccess uses this utility to display data in the LogManager.

Under Windows, the «sort» utility does not have the same options as the «sort» utility
under Unix. To ensure that Logmanager displays the data properly, follow the following
steps:

1. Get the gnu version of the «sort» utility for Windows from the address http://
unxutils.sourceforge.net/

2. Install it in the system environment variable PATH (for instance in %EDIHOME%/bin) with
the name «gsort.exe».

3. If you have a WebAccess version 7.05a ou 7.05b:

the command should be named «gnu_sort.exe».

If you have a version earlier than WebAccess 7.05a:

the utility should be named «sort.exe».

The system searches the command accordingly to the order defined in the PATH environement
variable. Make sure the TradeXpress directory path in which you have installed the sort.exe
command is placed before the directory path «%SystemRoot%\system32». Thus, the correct

TradeXpress ®
Generix Group 2010 - All rights reserved 72
 Parameters settings
Initial configuration

version of sort.exe will be called up by the native version of Windows.

The following table shows the error message that may occur when a user wants to access the
Logmgr database, and the advocated solution to solve the issue.

Error message Solution

Cause : Identified only on Windows. The
«gsort.exe» program (here a version
earlier than 7.06 - thus «gnu_sort.exe»
has not been installed, or cannot be
accessed in the user PATH.

Solution : Get the «sort» program and

install ur on the User or system PATH.

Cause : A user syslog database does not

have a name for the INDEX field.

Solution : Give a name for this field in

the «syslog.cfg» file where it is missing.

TradeXpress ®
Generix Group 2010 - All rights reserved 73
 Parameters settings
w3i_access.profil example files

w3i_access.profil example files

A set of profiles’ definition files are provided as examples. Herunder, the list of each file and
there respective roles:

w3i_access.partner

An external partner profile.

• Access to the syslog and archive databases

• Coloring in red for entries whose STATUS field is ‘ERROR’

• Permission to view the files assigned to the entries.

• Displaying data streams which have a PARTNER field set to ‘ILLICOM’ only.

• Displaying files from directories l, a and e only .

• Renaming the l directory to ‘logging’

• Renaming the a directory to ‘application’ and defining the text/xml MIME type.

• Renaming of the e directory to ‘edi’

w3i_access.userview

A user profile that only has the right to view the databases and their contents.

• Access to the syslog, archive, databases

• Coloring in red for syslog and archive database entries whose STATUS field is ‘ERROR’

• Permission to view the files assigned to the entries.

w3i_access.userupdt

A user profile with the right to modify the databases and their contents.

• Access to uploading of files in the [HOME]/inbox and [HOME]/rte directories.

• Access to the syslog, archive, databases

• Coloring in red for syslog and archive database entries whose STATUS field is ‘ERROR’

TradeXpress ®
Generix Group 2010 - All rights reserved 74
 Parameters settings
w3i_access.profil example files

• Permission to remove, visualise, reprocess, import, and export on the syslog database.

• Permission to remove, visualise, import and export on the archive database.

w3i_access.exploitview

A user profile for monitoring all data streams

• Access to the logmgr database

• Viewing the syslog for EdiUsers editest and ediprod.

• Coloring in red for logmgr database entries whose STATUS field is ‘ERROR’

• Permission to view the files assigned to the entries

w3i_access.exploitupdt

A user profile for monitoring all data streams and with the right to act on these data streams.

• Access to the logmgr database

• Viewing the syslog for EdiUsers editest and ediprod.

• Coloring in red for logmgr database entries whose STATUS field is ‘ERROR’

• Permission to view the files assigned to the entries, to remove or to reprocess entries

w3i_access.admin

An administrator profile with:

• full rights on the syslog, archive,databases.

w3i_access.adminfull

An example of a profile where everything is accessible.

• Redefining the data displayed for the user and the display language (in comment)

TradeXpress ®
Generix Group 2010 - All rights reserved 75
 Parameters settings
w3i_access.profil example files

• Access to two external links, including the WebAccess for TradeXpress module
configuration interface.

• Access to file uploading in the [HOME]/inbox and [HOME]/rte directories

• Access to the SAP configuration

• Coloring in red for syslog and archive database entries whose STATUS field is ‘ERROR’

• Permission to remove, visualise, reprocess, import, and export on the syslog database.

• Permission to remove, visualise, import and export on the archive database.

w3i_access.view

Profile allowing to view the SYSLOG database only

• Access to the Syslog database

• Coloring in red for entries whose INFO field is ‘wait...’

• Coloring in purple for entries whose INFO field is ‘Positive DR received’

• Permission to view files assigned to a database entry

in comments

• Filter on the CONNECTION field with the value «TradInfluent»

• Access to the directories a, x, e.

• Renaming the a directory in application and the x directory in logging.

• Definition of the MIME type application/pdf for the e directory.

w3i_access.illicom

Profile having access to user-defined databases:

• Access to the Borderaux and Bondelivraison databases

• Coloring in green of database entries of the Bordereaux database

• Coloring in red for entries whose INFO field is ‘wait...’ for Bordereaux and
Bondelivraison databases

• Coloring in purple for entries whose INFO field is ‘Positive DR received’ for
Bordereaux and Bondelivraison databases

• Coloring in sky blue for entries whose DATEMISAJOUR field is filed for Bondelivraison
database

• Permission to send an EDI message (ODBC only) for the Bordereaux database

TradeXpress ®
Generix Group 2010 - All rights reserved 76
 Parameters settings
w3i_access.profil example files

• Permission to view the detail of a table (ODBC only) for the bon de livraison database

In comments:

• Filter on the NOMTRANSPORT field with the value «Speedy Gonzales»

• Filter on the DIRECTION field with the value «S» (Send) for the Bondelivraison database

• Filter on the STATUT field with the value «O» for the Bordereaux database.

• Permission to view files assigned to a database entry

TradeXpress ®
Generix Group 2010 - All rights reserved 77