EC Gateway is an enterprise-wide message management software, designed specifically to support inter- and intra-company electronic messages. EC Gateway has three main functions: process management, communications, and scheduling, and includes extensive reporting facilities, a trading partner interface, a single ODBC-compliant log database, and archive/restore functions.
The EDI Server 4.2 product bundle for EC Gateway includes:
EC Gateway (1 production, 3 non-production, 1 cold backup)
EC Gateway Operations Viewer (1 seat)
This table identifies documentation specific to EC Gateway 4.2.
Title |
Description |
Location |
|---|---|---|
EC Gateway Reference Guide |
Includes essential technical information you need to use EC Gateway to route, process, and manage electronic messages. |
ecgunix.pdf and ecgwin.pdfin \doc folder of your install directory. |
EC Gateway Operations Viewer Reference Guide |
Provides technical information and topics that help you understand and use EC Gateway Operations Viewer to monitor activities from a remote location. |
ecgops.pdfin \doc folder of your install directory. |
EC Gateway Remote Reference Guide |
Tells you how to extend the capabilities of EC Gateway to process scripts on remote computers without the need for multiple EC Gateway systems. |
ecgrem.pdfin \doc folder of your install directory. |
EC Gateway Installation Keys |
Includes the product key you need to install EC Gateway components. There are separate key documents for:
|
Print only |
CR |
Description |
|---|---|
276973 |
New Feature: New Find and Replace options let you search for and replace strings in specific modules. Find and Replace options are available in the Comm Channel, Mailbox, Trade Partner, Company ID, and Process modules. See the EDI Product 4.2 New Features Guide for additional information. |
291351 |
Problem: GetMessage command seems to permanently remove messages from the queue. � Resolution: When the GetMessage command gets a message from the queue, the message is temporarily removed from the queue. If you want to put the message back onto the queue, use a RestoreMessage command. If you want to permanently remove the message from the queue, use a RemoveMessage command. � When the script exits, any messages temporarily removed by the script will be removed permanently. |
318262 |
New Feature: New wsproces command line arguments support parameter passing. The switches for these parameters are –p1 to –p20. � With these new switches, you can pass parameters from the command line to scripts. This new feature is supported by both wsproces DLL and executable. See the EDI Products 4.2 New Feature Guide for additional information. |
330141 |
New Feature: A new Copy Processes command is available in the Process module that lets you copy a process (or script) from the current DSN (specified by the current system) to another DSN (may be specified by any system). � This lets you run the same process against multiple Trading Partner databases. |
331033 |
Problem: Reports are failing to run when the Trade Partner and Log DSNs are different. � Resolution: This has been fixed for 4.2. There are now two sets of reports, one will be called when the TP and Log are in the same database and one will be called when the TP and Log are in different databases. This will work w/out user intervention in all cases except when the user has two different DSN names pointing to the same database for TP and Log. |
340539 |
Problem: Reports generate an 'error detected by database dll' error when the Trade Partner database is different from the system database. � Resolution: When the Trade Partner and Log DSNs were the same, there was no issue. However, when the Trade Partner and Log DSNs were different, the above error was received. The reports have been modified so they will work in either circumstance. |
348251 |
Problem: If the database supports table ownership but the environmental variable ALL_TB_OWNERS is not set, there is no change in processing.� Resolution: If the database supports table ownership and the environmental variable ALL_TB_OWNERS is set, the code will first attempt to get a match on both table name and owner name as usual. � But if there is a match on table name, but no match on owner name, the code will check further to see if the current user has read and delete privileges on the table. If the current user does have these privileges, then the code returns to ECGATEWAY or ECMAP the return value to indicate that the table exists. |
353439 |
Problem: EC Gateway 2.9.5 process failed running in 4.0.6 if the process contained a String Concatenate command. The process had to be recompiled to run properly.� Resolution: Fixed. These processes would now run without recompilation. |
353929 |
Problem: When EC Gateway 2.9 scripts with a StringFind command were run on EDI 4.0.6 they failed unless they were recompiled. � Resolution: Fixed. They now run without recompilation. |
355525 |
Problem: In EC Gateway, the copy command on UNIX copy did not replicate the permissions of the source file onto the destination file. � Resolution: Fixed. File permissions are now the same on the original and on the copied file. |
355953 |
Problem: wsproces scripts that called pfsasync with a script name were hanging. � Resolution: Problem corrected. |
357421 |
Problem: In the Email command screen, when a Gateway filename is used as the Message To Send, the command failed with the message: Invalid Indicator for Message To Send. This failure occurred in EBF 4.0.6 but not in EBF 4.0.5. � Resolution: Fixed. |
358508 |
Problem: wsproces scripts compiled before EBF 4.0.6, failed to run EFTP, unless recompiled. � Resolution: wsproces and EFTP were modified to allow versions, compiled prior to 4.0.6, to run EFTP without requiring recompilation. |
364009 |
Problem: In EC Gateway 4.0.6 running with MQ Series 5.3 and Win2K SP4 that writes messages to a queue and a Parameter is used for the CommChannel, a Dr. Watson type memory error occurs after writing a few successful messages. There is no problem when a simple CommChannel name is used, instead of a parameter. � Resolution: Fixed. |
If your script includes multiple GetMessage statements, you must include explicit commands to move messages on and off the queue.
Each GetMessage statement gets a message from the queue; the message remains on the queue but is marked as having been read. To permanently remove the message from the queue, use a RemoveMessage command. To replace the message on the queue, as though it had not been read, use the RestoreMessage command.
If you want Scheduler to run tasks from the end of one year to a next date in the upcoming year, check the End Date/Time values in Advanced Scheduling. Set the correct field values or disable them completely.
Use these instruction to schedule end of year processing:
Start the Scheduler module.
Click Task, choose Add.
– Or –
Right-click a task, choose Edit.
Bring the Scheduler tab into focus. From the Frequency drop down box, choose Monthly.
In the Properties group, choose Run each month(s) using the next scheduled.
Click Months, then choose the months you want to schedule the run.
Click Advance Scheduling. Do one of the following:
Make sure the End Date/Time fields values are correct.
– Or –
Uncheck the End Date/Time check box. You must deselect this value for monthly transactions to cross yearly boundaries.
You can now set the scheduling resolution from the command line when you start the UNIX Scheduler daemon with the “-r” switch followed by the number of seconds. Sybase recommends a time greater than 5 seconds and less than 60 seconds. This depends on how many tasks you need to run plus their frequency.
Although the amount of free space required to upgrade the log table varies, the amount of free space in the database should be greater than the size (including data) of the current log table (TRLOG). If the amount of free space is greater, the upgrade should succeed. If not, the process will fail.
New wsproces command line arguments support parameter passing, including run IDs for 997 maps. The switches for these parameters are –p1 to –p20. With these new switches, you can pass parameters from the command line to scripts. This new feature is supported by both the wsproces DLL and executable. See the EDI Products 4.2 New Features Guide for additional information.
See the EDI Products 4.2 New Features Guide for a list of new and obsolete features.
Some customers requested additional documentation about the ACKTA1, PWD_GEN and SYS_SECU tables.
Column Name |
Data Type |
Length |
Description |
|---|---|---|---|
RUN_ID |
Integer |
9 |
Normal Run ID |
RUN_DATE |
Date/Time |
8 |
Normal Run Date |
SEND_QUAL |
Alphanumeric |
4 |
Sender qualifier from originating Interchange |
SEND_CODE |
Alphanumeric |
35 |
Sender Code from originating Interchange |
RECV_QUAL |
Alphanumeric |
4 |
Receiver Qualifier form originating Interchange |
RECV_CODE |
Alphanumeric |
35 |
Receiver Code from originating Interchange |
INTERCHANG |
Alphanumeric |
35 |
Interchange Control Number |
ORIG_INT_NUM |
Alphanumeric |
35 |
Interchange Control Number from originating interchange |
ORIG_DATE |
Alphanumeric |
6 |
Date of originating interchange |
ORIG_TIME |
Alphanumeric |
4 |
Time of originating interchange |
INT_ACK_CD |
Alphanumeric |
1 |
Acknowledgement code for originating interchange (Accepted, Rejected, etc.) |
INT_NOTE_CD |
Alphanumeric |
3 |
Type of Error (if any) for the originating interchange |
Column Name |
Data Type |
Length |
Description |
|---|---|---|---|
GW_VERSION |
Alphanumeric |
50 |
Gateway version number |
ONE_USERID |
Alphanumeric |
1 |
Flag for Unique User ID for Communication Channels |
ONE_LOGIN |
Alphanumeric |
1 |
Flag for Unique Login for Each Communication Channel |
ONE_ALPHA |
Alphanumeric |
1 |
Flag for At Least One Alphabetic Character in the Password of Communication Channels |
ONE_DIGIT |
Alphanumeric |
1 |
Flag for At Least One Numeric Character in the Password of Asynchronous Channels |
PWD_MINLEN |
Integer |
10 |
Minimum Password Length in Communication Channels |
BAD_ATTEMP |
Integer |
10 |
Lockout after Bad Attempts |
PWD_EXPIRE |
Integer |
10 |
Password Expires after Days |
PWD_GEN |
Integer |
10 |
Generations for Password History |
Column Name |
Data Type |
Length |
Description |
|---|---|---|---|
USER_ID |
Alphanumeric |
50 |
User ID for the Gateway Communication Channels |
USER_TYPE |
Alphanumeric |
50 |
Communication Channel Type |
PWD_GEN |
Integer |
10 |
Which Generation for the Password History |
USER_PWD |
Alphanumeric |
50 |
Password for the Gateway Communication Channels |
