STC eBusiness Integration
e*Gate 4.1 Upgrade Seminar

Los Angeles, CA

June 2000

DISCLAIMER:This information is being posted without express consent of STC.The content comes directly from their “e*Gate Upgrade Seminar” booklet which was distributed to seminar attendees on Thursday, June 1, 2000.Please note that while many of the slides have been re-typed here, for your benefit, the graphics such as charts and diagrams were not reproduced.Also note that because most of us are concerned with the e*Gate 4.1 upgrade, the notes stop at the “Questions & Answers” session.The balance of the seminar focused on e*Xchange and HIPAA.Separate costs apply to each product.In the interest of my sleep, this is where my re-typing efforts stopped.

SEMINAR FORMAT:The bulk of the seminar was a PowerPoint presentation.Almost all of the slides displayed during the seminar are printed in the manual that was distributed to seminar attendees.

HOT DISCUSSION TOPICS:

·no journaling – Sam Domingo explained that the new queues retain a memory of messages, the messages are not cleared as they are with pre e*Gate 4.1 versions.The drawback is that the new queues do not store the messages in the same format as the journals do.

·monitoring– it was painfully noted by many attendees that the Windows Explorer like view of the e*Ways was not very intuitive and they expressed concern that the operations staff would not be able to easily determine who should be notified with the alert. 

·message tracking and status of external systems are also difficult to determine in e*Gate 4.1

·logs – new process IDs for an e*Way log append to the log file, log files do not archive automatically, but a script can be written to archive logs

I. Agenda

8:00 – 8:30  Welcome & Overview

8:30 – 9:00  e*Gate 4.1 Advantages

9:00 – 9:45  e*Gate 4.1 Architecture & Features

9:45 – 10:00  Break

10:00 – 10:45 Upgrade Tools & Processes

10:45 – 12:00 Upgrade Demo

12:00 – 1:00  Lunch

1:00 – 2:15  Upgrade Demo (continued)

2:15 – 3:15  Questions & Answers

3:15 – 3:30  Break

3:30 – 4:30  e*Xchange & HIPAA

4:30 – 5:00  Wrap Up

II. Upgrade Seminar Goals

A. Introduce e*Gate 4.1

B. Explain the Advantages

C. Explain the Demo and Upgrade Tools & Process

D. e*Xchange Integrator and HIPAA Readiness

III. STC Vision For Business Integration—“To manage the flow of information across all systems, applications and enterprises on a global basis.”

IV. Most eBusiness Solutions Are Piecemeal—“Result: Time wasted on integrating the integration solutions!”

A. Business Process Management

1. process modeling

2. real-time monitoring & analysis

3. process data warehouse

4. business events alerts

B. B2B Integration

1. trading partner management

2. security

3. transport

4. eBusiness protocols

C. A2A Integration

1. message transformations

2. application interfaces

3. message deliver publish/subscribe

4. content based routing

V. STC Provides a Complete Solution

A. e*Xchange eBusiness Integration (eBI) Suite

1. process

a) Business Process Management

b) eBusiness Process Manager

c) e*Xchange

2. relationships

a) B2B Integration

b) ePartner Manager

c) eSecurity Manager

d) Integrator

3. integration

a) A2A Integration

b) e*Gate Integrator

VI. Take-Aways

A. It is in all our best interests for STC to continue to be the eBusiness market leader

B. STC is committed to honoring the letter and spirit of every DataGate contract with e*Gate 4.1

C. Automatically convert from e*Gate 3 to e*Gate 4.1—with minimal or no programming required

D. You likely already own all the hardware you’ll need for the e*Gate 4.1

 

e*Gate 4.1 Advantages

VII. e*Gate 4.1 Highlights

A. rich development

1. team development

2. open collaboration services

3. CORBA, COM, EJB

B. robust WEB platform

1. HTTP(S)

2. web servers, java application servers

C. highest performance and availability

D. world of connectivity

E. distributed architecture

F. dynamic pub/sub

G. open, intelligent queue service

H. generic e*Way extension kit

I. multi-threaded for high performance

J. robust security

K. totally GUI driven

L. supports e*Gate 3.6 and earlier

VIII. e*Gate 4.1 Advantages

A. enhancements in e*Gate 4.1

B. support for latest OS’s

C. updated adapters

D. updated e*Index

E. new STC eBusiness products

IX. Enhancements in e*Gate 4.1

A. powerful configuration management system

B. highly scalable distributed architecture

C. flexible architecture

D. dynamic configuration updates to all components

E. native Windows NT/2000 monitoring system

F. Monk-enabled alerting system

G. support for executing business rules in Java

H. enhanced internal messaging protocol

I. Monk support for XML, HL7 3.0 and UNICODE

X. Support for New STC eBusiness Products

A. e*Xchange

B. new e*Way adapters

C. secure messaging extension

D. new and updated converters

XI. e*Xchange

A. eBPM

1. business Process

a) modeling

b) monitoring

c) reporting

2. GUI message repair

B. ePM

1. GUI configuration of HIPAA – Compliant X12 enveloping and ACK/NACK logic

2. message audit trails

3. support for emerging B2B standards

a) Rosetta Net

b) Biz Talk

C. eSM

1. security manager

a) digital authentication of messages based on digital signatures

(1) X12

(2) Rosetta Net

XII. New e*Way Adapters

A. IMS

B. CICS

C. HTTP/HTTPS

D. Apache Web Server

E. Microsoft IIS Web Server

F. iPlanet (Netscape) Web Server

G. scriptable TCP/IP

H. CNT

I. Java generic API kit

J. email LDAP

K. WAB

L. BroadVision (SAP, Siebel)

M. PeopleSoft (Onyx, SAP)

N. SAP – Siebel

O. Onyx – SAP

P. i2

XIII. Secure Messaging Extensions

A. allow e*Ways & BOBs (Business Object Brokers) to:

1. encrypt messages

2. decrypts messages

3. sign messages

B. based on SMIME RSA library

XIV. New and Updated Converters

A. COBOL Copybook

B. XML DTD

XV. New and Updated Message Structures

A. EDIFACT EDT Library D95A

B. X12

1. updated about 1 QTR after new release

2. currently have all versions since version 2001

 


e*Gate 4.1 Architecture & Features

XVI. e*Gate 4.1 Terminology


 
New Terminology
Old Terminology
e*Gate 3.5/3.6
DataGate 3.5, 3.6, 3.6.2
custom e*Ways
communication clients
e*Gate 3.5/3.6 e*Ways 
super clients, DataGateWays
collaboration rules
xlates
collaboration IDs
IDs
schema
tables
intelligent queue (IQ)
queues
event type definition (ETD)
message structures
PUB/SUB paradigm
routing paradigm

XVII. e*Gate 4.1 Terminology

A. e*Way

1. a generic communication component that connects an external system to a queue

2. supports connection to external system

3. contains user defined business logic/code defining the collaboration

B. BOB (Business Object Broker)

1. optional component

2. a type of e*Way that only exchanges data with other e*Gate components

3. does not communicate directly with external systems

4. queue to queue

5. contains user defined business logic/code defining the collaboration

C. Intelligent Queues

1. persistent storage for data exchange

2. medium independent

a) STC standard

b) Oracle

c) Sybase

d) MQ Series

3. subscriber pooling

4. priorities

D. Collaborations

1. containers for business rules

2. manage the publication/ subscription logic

3. manage data transformation

4. run in a separate thread within e*Ways or BOBs

5. Monk, C, Java Language

E. Control Broker

1. startup/shutdown of all components

2. forwards notifications of alerts and status of all components

F. Registry

1. storing and serving files

2. configuration information

3. registry host (the computer running the e*Gate registry Service/Daemon)

4. team registry


5.distributed registry

a) primary

b) secondary

G. Schema

1. for organizing files and configuring info

2. resides in registry

3. unique name

XVIII. e*Gate 4.1 Architecture

A. Completely Distributed

1. configuration

2. monitoring and control

3. runtime execution

B. Open & Extensible Utilizing Standard APIs

1. collaboration service

2. intelligent queue service

3. multiple language support for collaboration rules (Monk, Java, C)

4. core APIs—e*Way extension kits

C. Platform Independent—MIx and Match

1. as simple as configuring a component on one machine and moving it to another when needed

XIX. Differences Between e*Gate 4.1 and e*Gate 3.6/3.5

A. publish/subscribe vs. routing

B. no central bottleneck

C. multi-threaded e*Ways and BOBs

D. configurable queues

E. nomenclature changes

F. additional products

G. message structures (event type definitions)

H. ID/translation logic (collaboration rule logic)

I. Monk functions

J. 3.5/3.6 e*Ways

K. tales mode logic

L. 3.5/3.6 e*Gate routes

M. e*Way configuration files

Upgrade Tools & Process

XX. Upgrade Tools

A. Components

1. schema configuration utility

2. route table collaboration service

3. communication client proxy e*Way

4. e(|*Way configuration file conversion utility

XXI. Route Table Collaboration Service

A. used within e*Ways or BOBs

B. supports “Tables” mode

C. supports “MONK” mode

D. DataGate server functionality in a BOB or e*Way

XXII.