Title: Arial 28pt'

1
INT411 zOS Integration
Dan Smith Staff Architect and Team
Lead dsmith_at_sybase.com August 15-19, 2004
2
The Enterprise. Unwired.
3
The Enterprise. Unwired.
Industry and Cross Platform Solutions
Unwire People
Unwire Information
Manage Information

• Adaptive Server Enterprise
• Adaptive Server Anywhere
• Sybase IQ
• Dynamic Archive
• Dynamic ODS
• Replication Server
• OpenSwitch
• Mirror Activator
• PowerDesigner
• Connectivity Options
• EAServer
• Industry Warehouse Studio

• Unwired Accelerator
• Unwired Orchestrator
• Unwired Toolkit
• Enterprise Portal
• Real Time Data Services

• SQL Anywhere Studio
• M-Business Anywhere
• Pylon Family (Mobile Email)
• Mobile Sales
• XcelleNet Frontline Solutions
• PocketBuilder
• PowerBuilder Family
• AvantGo

Sybase Workspace
4
zOS Integration

• Topics
• A Short zOS Integration History.
• Legacy Sybase Tools
• Sybases Contribution to Integration
• New Sybase Tools
• Reasons for Integration
• Demos
• Questions and Answers

5
A Short History

• Hardwired File Transfer
• Home Grown File Transfer
• 3270 Emulators
• Screen Scraping
• Sybase entered the S390 market during this time
  frame

6
Sybase History
Open Client Open Server (TDS)
Open Client IMS CICS to LAN data
DB2
ASE
Non SQL data
Mainframe Applications, and Transactions
Open Server CICS Programs, Data, And DB2 SQL
Access to MF Data and Applications
Direct Connect for OS/390
7
Unwired zOS Sybase Contributions
Mainframe TDS, XML, HTML, and Replication
Rep Agent for DB2
DB2
CICS Programs, Data HTTP, MQ, Web Serv.
ASE
IMS Programs, Data, HTTP, MQ
Direct Connect for OS/390
Mainframe Applications, and Transactions
Navigate CICS HostBridge, Web Serv., Transactions
MQSeries
Access to MF Data and Applications (Server
Options and XJS/390)
Integrate with MainframeCONNECT
MQSeries
Today, All zOS data can be Unwired, no matter
how complex!!
8
Reasons for Integration

• The reasons are many
• Mergers
• Acquisitions
• Changing Sales Force Needs
• Patriot Act
• Company Growth
• New Technologies
• Telecommuting
• The list is nearly endless

9
New Sybase Tools

• Direct Connect to anything, IBM, Oracle, others.
• Rep Agents to Anything.
• Enterprise Portal
• Integration Orchestrator
• Unwired Orchestrator
• the list keeps growing.

10
Unwiring Everything

• The Unwired Example (next slide)
• Note that all data sources are LAN based.
• Is this for real?
• In our experience this is rarely a real world
  example.
• Lets get a little familiar with our example.
• Well skip most details.

DEMO
11
Insurance Sample Overview
1
2
3
7
8
View BizTracker Monitor
Create Claim
View Claim
Add Policy
Add Customer
EAServer
IO
BizTracker
Web Apps
Email to Repair Shop
JMS
AMS
HQ Insurance
West Insurance
Central Insurance
East Insurance
Repair Shops
Repair Estimates
Add Claim Details
Select Repair Shop
Look-up Repair Estimates
4
6
5
12
Insurance Sample Overview

• The Insurance Sample contains 8 major
  demonstration steps
• Add Customer An insurance agent creates a new
  customer by entering information via web browser.
• Add Policy An insurance agent creates one or
  more auto insurance policies for a customer by
  entering pertinent information via web browser.
• Create Claim Customer calls insurance company
  from the accident site. Customer provides their
  customer id and vehicle (policy) information. The
  insurance agent creates a new claim by entering
  the information via web browser.
• Add Claim Details Insurance adjuster sync their
  Pocket PC to pick-up new claims, data needed for
  repair estimates and an updated list of
  recommended repair shops. Then the adjuster goes
  to the accident site and enters detailed
  information for the claim and the customers
  selected repair shop.
• Look-up Repair Estimates - While the insurance
  adjuster is at the accident site, they can use
  their Pocket PC to look-up estimated costs for
  various damages.

13
Insurance Sample Overview (Continued)

• The Insurance Sample last 3 steps
• Select Repair Shop While the insurance adjuster
  is at the accident site, they can provide a list
  of recommended local repair shops for the
  customer to choose from.
• View Claims The insurance agent can view a list
  of claims and select an individual claim to view
  its details. This can be done at anytime, before
  and/or after the claim details have been entered
  by the adjuster.
• View Business Metrics - The insurance company
  manager can view metrics of the insurance
  companys business related to claim and cost
  amounts.

14
Add Customer
1
Add Customer
EAServer
Web App
EAServer
customer
IO
HQ Insurance
West Insurance
Central Insurance
East Insurance
15
Add Customer Details

• Input customer data into an HTML form, which
  submits the data to a Web Application running in
  EAServer.
• ref_emp_id, holder_fname, holder_lname,
  holder_addr, holder_city, holder_state,
  holder_zip, holder_areacode, holder_phone,
  holder_gender, and holder_dob
• Web App formats data into XML schema and sends a
  JMS text message to a CTS Message queue named
  customer.
• IO Business Process(1) retrieves the message
• Inserts the data into the policy_holder table of
  the Headquarter Insurance database.
• Retrieves the holder_id created for this
  customer. Evaluates rule based on customers
  state and inserts the data (including holder_id)
  into the policy_holder table of one of three
  Regional Insurance databases (East, Central,
  West).

16
Add Policy
2
Add Policy
EAServer
Web App
EAServer
policy
IO
HQ Insurance
West Insurance
Central Insurance
East Insurance
17
Add Policy Details

• HTML form will require input of a Customer ID
  (holder_id), vehicle make, model, year, and
  deductible, which will be submitted to a web
  application running in EAServer.
• ref_holder_id, policy_name (make_model_yyyy),
  deductible
• Web App formats data into XML schema and sends a
  JMS message to a message queue named policy.
• IO Business Process(2) retrieves the message
• Inserts the data into the policy table of the
  Headquarters Insurance database.
• Retrieves the policy_id created for this policy.
  Evaluates rule based on customers state and
  inserts the data (including policy_id) into the
  policy table of one of three Regional Insurance
  databases (East, Central, West).

18
Create Claim
3
Create Claim
EAServer
Web App
EAServer
claim
IO
HQ Insurance
West Insurance
Central Insurance
East Insurance
19
Create Claim Details

• HTML form will require input of a Customer ID
  (holder_id). Then a list of policies for that
  Customer ID will be displayed in a drop-down box.
  A policy will be selected and a claim description
  will be entered. The data will be submitted to a
  Web Application running in EAServer.
• claim_id, ref_policy_id, claim_short_desc
• Web App formats data into XML schema and sends a
  JMS message to a queue named claim.
• IO Business Process(3) retrieves the message
• Inserts the data into the claim table of the
  Headquarters Insurance database.
• Evaluates rule based on customers state and
  inserts the data into the claim table of one of
  three Regional Insurance databases (East,
  Central, West).

20
Add Claim Details
EAServer
BT probe
amsmail
IO
authorization
claim
DB Trigger
West Insurance
HQ Insurance
Java App
Repair Shop
AMS
Mobilink
Add Claim Details
4
21
Add Claims Detail (Pocket PC) details

• With the iAnywhere Adjuster C application the
  user can add detailed information to the claim.
  The following operations can be performed
• While the PocketPC is connected to the network
  (in its cradle), use the Sync button on the
  Adjuster App to initiate the Mobilink client,
  which connects to the Mobilink server for the
  Insurance_West ASA database and performs the
  synchronization. New claims will then show up on
  the Adjuster App.
• Add line items to the claim, ie. fender, tail
  light, bumper. Cost estimates for damaged parts
  can be looked-up using the Pocket PowerBuilder
  Repairs Application. A running sum of total
  damages is calculated by the Adjuster App.
• Add images of the accident site. Images can be
  marked-up to highlight damages and a description
  can be added to each image.
• Submit the claim for processing. This changes the
  status of the claim which removes it from the
  Adjuster App view.
• After the re-connecting the PocketPC to the
  network, use the sync button to, again, initiate
  the Mobilink client. It connects to the Mobilink
  server for the Insurance_West ASA database and
  performs the synchronization. All new claim
  details are uploaded to the Insurance_West
  database.
• The following tables are involved in the
  synchronization process
• claim, claim_items, claim_status, claim_images,
  marked_up, bitmaps, doodles, strokes, points

22
Add Claims Detail (Pocket PC) details (cont.)

• A database trigger is configured on the
  claim.claim_status column. When this column is
  updated the trigger will call the xp_cmdshell
  stored procedure to initiate the Mobilink client,
  which connects to the Mobilink server for the
  Insurance_HQ ASA database and performs the
  synchronization. All new claim information is
  uploaded to the Insurance_HQ database and
  ensuring that HQ, Regional and PocketPC databases
  are all in sync. The same tables as above are
  involved in the synchronization process.

23
Add Claims Detail (IO) details

• Updating data in the Headquarters Insurance
  database fires a trigger which executes the
  xp_cmdshell stored procedure. This in turn will
  run a stand-alone java application which
  retrieves updated claim_id, formats data into XML
  schema and sends a JMS text message to the queue
  named claim.
• IO Business Process (3) retrieves the message
  (claim_id) from claim queue and queries the
  Headquarters Insurance database to get the
  following data and sends it to a BizTracker probe
  for subsequent BizTracker processing
• claim_id, claim_short_descr, claim_date,
  repair_shop_id, repair_shop_name, policy_id,
  holder_id, holder_fname, holder_lname,
  holder_gender, holder_dob, holder_city,
  holder_state, total_amount(), disp_claim_id,
  disp_policy_id
• IO will calculate the total amount for this
  claim by adding claim_item_value fields
  (claim_items table) for this claim_id.
• IO Business Process (3) queries the RepairShop
  database to check if the there is an AMS channel
  set for the repair shop select, if so then it
  will send an email with the above data to the
  queue designated for AMS (amsmail) and AMS will
  pick up the message and send an email to the
  repairshop containing claim data. If there is no
  AMS channel set for the repairshop but the
  repairshop id exists in the RepairShop database,
  then claim data will be sent to an
  authorization queue.

24
Lookup Repair Estimates (Pocket PC)
Repair Estimates
Look-up Repair Estimates
5
25
Lookup Repair Estimates (Pocket PC) details

• While the PocketPC is connected to the network
  (in the cradle), use the Pocket PowerBuilder
  Repair App Sync button to initiate the Mobilink
  Client. It connects to the Mobilink Server for
  the Estimates database and synchronizes vehicle
  parts cost data pertinent to all new claims.
  (Note The sync button initiates Mobilink clients
  for both the Estimates and RepairShop database.
  This operation only needs to be performed once
  for both databases to sync.)
• Select the claim you are working on in the
  iAnywhere Adjuster application. This sets a
  global variable in the Repair app.
• Use the menu or button to select Get Estimates.
  The claim number is used to retrieve the vehicle
  type from the CeAdjuster ASA database. Then a
  datawindow is used to retrieve and display part
  cost information for that vehicle.
• Then the part cost can be entered into the
  Adjuster C application for further processing.

26
Select Repair shop (Pocket PC)
Claim-West
Repair Shops
Select Repair Shop
6
27
Select Repair shop (Pocket PC) details

• While the PocketPC is connected to the network
  (in the cradle), use the Pocket PowerBuilder
  Repair App Sync button to initiate the Mobilink
  Client. It connects to the Mobilink Server for
  the RepairShop database and synchronizes all
  recommended auto repair shops. (Note The sync
  button initiates Mobilink clients for both the
  Estimates and RepairShop database. This operation
  only needs to be performed once for both
  databases to sync.)
• Select the claim you are working on in the
  iAnywhere Adjuster application. This sets a
  global variable in the Repair app.
• Use the menu or button to select Repair Shops. A
  datawindow prompts for the city, then retrieves
  and displays recommended repair shops in that
  location.
• Selecting a repair shop enters the repair_shop_id
  into the claim table of the CeAdjuster ASA
  database.

28
View Claims
View Claim
7
EAServer
Web App
HQ Insurance
29
View Claims details

• A web application running in EAServer retrieves a
  list of claims from the Headquarters Insurance
  database.
• An individual claim can be selected to view its
  details.
• This action can be performed at anytime, before
  and/or after the claim details have been added by
  the adjuster.

30
View Business Metrics
View BizTracker Monitor
8
BizTracker
IO
BizTracker Probe
31
View Business Metrics Details

• Use the BizTracker Monitor Console to monitor and
  display the following business metrics
• Claims/day, week, month, year
• Claim Volume/day, week, month, year
• Claims/policy
• Claims/policy holder
• Claims/state
• Claims/city
• Claims by gender (claims for males and
  females)
• Claims by Age (for ex claims for people over
  60)
• Claims by year of birth (for ex claims for
  people born in 1975)
• Claims/repairshop

32
But what if

• the HQ database is zOS DB2 or
• the West coast uses VSAM or
• the Central data is IMS or
• the Legacy data from the East coast is a home
  grown database?
• First lets take a look at the big picture again

33
Insurance Sample Overview
1
2
3
7
8
View BizTracker Monitor
Create Claim
View Claim
Add Policy
Add Customer
EAServer
IO
BizTracker
Web Apps
Email to Repair Shop
JMS
AMS
HQ Insurance zOS DB2
West Insurance VSAM
Central Insurance IMS
East Insurance ARGOL
Repair Shops
Repair Estimates
Add Claim Details
Select Repair Shop
Look-up Repair Estimates
4
6
5
34
With Sybase you have Options
EAServer
IO
Web Apps
JMS
Rep Agent for DB2
ASE
HQ Insurance zOS DB2
This Scenario may give you exactly what you want
DEMO
Because of ASE, IO and EAServer work exactly as
in the original example.
35
Other Options
IO
IO thinks OSC is ASE
Open Client/Server CICS Programs, Data
Open Client/Server IMS Programs, Data
East Insurance ARGOL
West Insurance VSAM
Central Insurance IMS
DEMO
All references to ARGOL are fictional and have
no relation to databases past, present
36
Or a combination of them all
EAServer
IO
BizTracker
Web Apps
JMS
HQ Insurance zOS DB2
West Insurance VSAM
Central Insurance IMS
East Insurance ARGOL
DEMO
Look-up Repair Estimates
37
zOS Integration
Sybases install base is invaluable to many
Financial, Insurance, Telecom, Industrial, and
Other corporations.

• Because of this, when we speak of integration
  Sybase you know Sybase zOS products.
• are robust,
• are efficient,
• are adaptable to your situation,
• are compatible with IBM solutions,
• and they evolve to support new technologies.
• Sybase has the complete integration solution.

38
zOS Integration
When you think of Unwired zOS Enterprise Systems
think Sybase! Any Questions?