GCOS Integration in the J2EE Connector Architecture

1
GCOS Integration in theJ2EE Connector
Architecture
GCOS 8 Session
TechSem 2001 Paris, March 28-30

• by
• Michael Giroux Jim Gallagher

2
GCOS e-Business evolution
Transactional Cooperation GCOS TUXEDO
GCOS Integration to Web/Internet
Transactional Integrity XA
GCOS-Application Servers Integration
3
e-Business / GCOS integration
4
Agenda

• J2EE 1.2 Application Integration
• J2EE 1.3 Connector Architecture
• Application Development for e-Business

5
J2EE Glossary
6
J2EE Application Integration

• Java Language
• Flexible technology
• Java Server Pages
• Enterprise Java beans
• N-Tier
• Standard APIs
• JDBC
• JMS
• Robust Development Tools
• BEA WebGain
• IBM Visual Age
• J2EE Connector Architecture in J2EE 1.3

7
J2EE Architecture

• CLIENT
• HTML
• Java Applets
• Mobile

• EnterpriseSYSTEMS
• Database
• Business
• Logic
• ERP

JCA J2EE Connector Architecture
8
J2EE 1.2 access to GCOS

• J2EE 1.2 used today to integrate GCOS data into
  open applications
• JOLT access to TUXEDO services
• Leverage existing TUXEDO applications
• GTEA direct access to GCOS 8 services
• Simplified architecture if TUXEDO is not already
  installed

9
J2EE 1.2 with TUXEDO
Business TPR coded as subroutine TP Connect
provides all message processing Global
transactions supported between TUXEDO and
GCOS JOLT connects J2EE to TUXEDO
Business TPR
GCOS8
TP8
(COBOL record)
TP Connect
XA/8 Switch Board
GTEA ( TCP/IP network )
G8 RM
XA TM
J2EE
Application bean (Java)
TUXEDO
AIX/NT
Host Connect
Interface bean (Java)
User App (C/Cobol)
JOLT
10
J2EE 1.2 with GTEA
Business TPR coded as subroutine Message TPR
contains all message processing Global
transactions not supported
Business TPR
GCOS8
TP8
(COBOL record)
Message TPR
GTEA ( TCP/IP network )
GTEA for JAVA uses standard java.net classes User
coded Interface bean contains GTEA calls and
provides abstract view of the TP8 TPR
Application bean implements business logic
GTEA
J2EE
AIX/NT
Interface bean (Java)
Application bean (Java)
11
Business Application View
J2EE 1.2 Application Server
JSP
EJB
EJB
User Coded JSP
EJB
Interface bean
User Coded beans
User coded Interface component
GTEA or JTDS
J2EE Services
GCOS TPR
User Coded TPR
12
Agenda

• J2EE 1.2 Application Integration
• J2EE 1.3 Connector Architecture
• Application Development for e-Business

13
J2EE 1.3 Connector Architecture

• Standard Java architecture
• for connecting J2EE 1.3 Application Servers (such
  as WebLogic Server) to Enterprise Information
  System (GCOS)
• Connection Pool management
• Security management
• Transaction management
• Read more
• http//java.sun.com
• Search for JSR016

14
Overview of Connector Architecture
Container-Component Contracts
Customer Application Components
J2EE 1.3 Application Server
Common Client API
Connector (Resource Adapter)
System Contracts
EIS Specific Interface
Enterprise Information Server
15
Connector Architecture Example
J2EE 1.3 Application Server
16
Business Application View
J2EE 1.3 Application Server
JSP
EJB
EJB
User Coded JSP
EJB
Interface bean
User Coded beans
Tool generated Interface component
GCOS Connector
J2EE Services
GTEA
GCOS TPR
User Coded TPR
17
Benefits

• Leverage existing GCOS Applications
• No need to modify existing TPRs
• Single TPR for multiple open platforms
• TUXEDO
• J2EE Application Server
• BEA WebLogic Server
• Oracle Application Server
• Others
• Microsoft Windows 2000 COM
• J2EE platform portability
• Single product supporting
• Existing TPRs (terminal emulation)
• New TPRs (message mode)

18

J2EE Connectors to GCOS Architecture and tools
19
Message Mode Connector
Business logic TPR coded as subroutine to
maximize reuse Message handler provides all
message processing Global transactions not
supported
Business TPR
GCOS8
TP8
(COBOL record)
Message Handler
GTEA ( TCP/IP network )
GCOS Connector supports J2EE Connector
Architecture interfaces Interface bean contains
all connector calls and provides abstract view of
the TP8 TPR Application bean implements business
logic
GCOS Connector
J2EE
AIX/NT
Interface bean (Java)
Application bean (Java)
20

Terminal Emulation (Forms) Mode
Existing TDS, TP8 and TSS programs see the
connector as a standard terminal No changes
required on the GCOS side
TSS programs
GCOS7 / 8
TP8 TPRs
TDS TPRs
TCP/IP connection to GCOS or to a gateway (Ggate
or Mainway)
GTEA / GR GGATE / TNVIP
GCOS Connector has Glink for Java terminal
emulation and comms inside Interface bean
contains all connector calls and implements the
terminal dialog Application bean implements
business logic
GCOS Connector
J2EE
AIX/NT
Interface bean (Java)
Application bean (Java)
21

Glink Connector for IBM and UNIX
Existing IBM mainframe, AS/400 or UNIX programs
see the connection as a standard 3270, 5250 or VT
terminal
IBM/UNIX
CICS / IMS programs
OS400 programs
UNIX Appl.
TCP/IP connection to host or TN3270 gateway
TN3270 / TN5250 / Telnet
Glink Connector has Glink for Java terminal
emulation and comms inside Interface bean
contains all connector calls and implements the
terminal dialog Application bean implements
business logic
Glink Connector
UNIX/NT
J2EE
Interface bean (Java)
Application bean (Java)
22
Agenda

• J2EE 1.2 Application Integration
• J2EE 1.3 Connector Architecture
• Application Development for e-Business

23
Emulation Mode Tool

• Based on Glink for Java Professional Edition
• Use Glink for Java terminal emulation to step
  through a series of host forms
• Use Glink for Java API to extract information
  from the host forms and to move from one form to
  another
• Plug input data into forms
• Mark output data in intermediate and/or final
  form
• Generate Interface component (EJB) that navigate
  through the recorded set of forms and return the
  marked screen data

24
Terminal Emulation Interface Generator
howToBuyConnector() Input Country
The generated Interface component bean know how
to execute the correct sequence of forms
Output Bull sales information - Name - Phone
number - E-mail address
25
Message Mode Tool

• Generate interface component from COBOL record
  description
• TPRs dedicated to e-Business
• Message mode
• TP8 Connect with TUXEDO mode

26
Interface Component Generator
TP Connection Parameters
Input record description
Output record description
Component Template
Component Generator
Interface Component
27
Component Generator Interface
28
Component Generator Interface
1. Specify name of Java Package and Class
2. Specify TP8 node name and mailbox
3. Specify file name containing the COBOL data
record describing input message
4. Specify file name containing the COBOL data
record describing output message
6. Generate the Java source code
5. Specify file name for generated Java class
source
29
Interface bean benefits

• Application insulated from EIS details
• (Enterprise Information System)
• Data presented as object properties
• Centralized configuration
• Host node and mailbox
• TP8 command name
• Generalized interface
• Input properties
• Output properties
• Execute method

30
Message Mode Example

• Message Mode tool generates Java beans from COBOL
  data records
• Application programmer writes business beans that
  use tool output
• Application syntax is intuitive as illustrated in
  following example

31
Cobol Data Records

• COBOL Input Record
• 01 ID-RECORD.
• 02 NAME PIC X(12).
• 02 ID-NUMBER PIC 9(6).
• COBOL Output Record
• 01 INFO-REC.
• 02 FIRST-NAME PIC X(12).
• 02 LAST-NAME PIC X(14).
• 02 ITEMS-PURCHASED PIC 999.
• 02 PURCHASE-VALUE PIC ,9.99.

32
_idRecord class

• /
• 1 01 ID-RECORD.
  
• 2 02 NAME PIC X(12).
  
• 3 02 ID-NUMBER PIC 9(6).
  
• /
• class _idRecord
• byte messageData new byte18
• void setIdRecord(String val) throws
  Exception asciiToMessage(val, messageData, 0,
  18, false)
• void setName(String val) throws
  Exception asciiToMessage(val, messageData, 0,
  12, false)
• void setIdNumber(java.math.BigDecimal
  val) throws Exception decimalToMessage(val,
  messageData, 12, 6, 0)
• String buildCommandLine() throws
  Exception
• return new String(messageData)

33
_infoRec class

• /
• 1 01 INFO-REC.
  
• 2 02 FIRST-NAME PIC X(12).
  
• 3 02 LAST-NAME PIC X(14).
  
• 4 02 ITEMS-PURCHASED PIC 999.
  
• 5 02 PURCHASE-VALUE PIC
  ,9.99.
• /
• class _infoRec
• byte messageData new byte39
• String getInfoRec() throws Exception
  return asciiFromMessage(messageData, 0, 39)
• String getFirstName() throws Exception
  return asciiFromMessage(messageData, 0, 12)
• String getLastName() throws Exception
  return asciiFromMessage(messageData, 12, 14)
• java.math.BigDecimal getItemsPurchased()
  throws Exception return decimalFromMessage(messa
  geData, 26, 3, 0)
• String getPurchaseValue() throws
  Exception return asciiFromMessage(messageData,
  29, 10)
• void setResults(byte data) throws
  Exception
• messageData data

34
Generated Interface bean

• class custInfo extends dataWay
• _idRecord idRecord new _idRecord()
• _infoRec infoRec new _infoRec()
• public void execute(String commandLine) throws
  Exception
• // code to invoke connection execute() method
  not shown

35
Using generated class example

• class testDemox
• testDemox()
• // constructor does nothing
• public void runner()
• try
• demox demo new demox()
• demo.idRecord.setName("smith")
• demo.idRecord.setIdNumber(new
  BigDecimal("231"))
• demo.execute("command"
  demo.idRecord.buildCommandLine())
• System.out.println(demo.infoRec.getFir
  stName())
• System.out.println(demo.infoRec.getLas
  tName())

Application developer writes business logic
36
COM

• We are doing the same for COM
• Support standard Windows COM interfaces for
  pooled connections
• Interface component generator tool for access to
  connection using COM objects
• Configuration tool for management of connections
• Support for TSS and TP8 applications

37
Bull introduces HooX

• HooX for Host object oriented conneXion
• a new family of connectors to plug seamlessly
  existing transactional applications into
  e-business applications
• JCA connectors and their tools to generate
  interface EJB for J2EE 1.3 application servers
• COM connectors and their tools to generate COM
  components for the Microsoft .Net framework
• HooX is developed by Bull in co-operation with
  our partner Gallagher Robertson

38
What HooX means for you

• Fast availability of complete e-business
  applications
• reuse valuable existing applications and
  integrate them with your new e-business
  transactions
• faster application development
• the host developer generates easily the access
  components with the toolkit
• the Java developer uses them without having to
  know about the host transactions and connectivity
  

39
With HooX, seamlessly plug your legacy
transactions into your e-business applications
40
Questions?