• Post Reply Bookmark Topic Watch Topic
  • New Topic

Web Services, CICS, OLTP

 
Nigel Kat
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a simple 'proof of concept' project to build, & there are some moving parts that I'm not entirely familiar with. I was wondering if there was a consise map of the parts and/or steps out there somewhere:
From a Web application wrap a user-given SQL statement in a pre-defined XML header. Ship the transaction to an OS/390 CICS Web-owning region, calling an online transaction that will pass the transacation off for processing to the CICS application (proven & running) and return the result. No massage of data required in the transfer, XML wrapper applied in web app.
I have WSAD & VAJ EE at my disposal. Not exactly an expert with these things, but I'm comfortable enough getting around.
There are lots of good articles and tutorials out there on these subjects, most focusing on B2B. This app is entirely internal and eliminates some of the layers required with B2B services. The biggest stumbling block seems to be putting it all together in a consise list or map. Any ideas?
Thanks!
Kat
>^..^<
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kat,
Why do you need to pass the SQL statement to a CICS transaction? This is EXACTLY what DADX Web services (described in detail in the tutorials for WSAD) are for -- you can run the web service directly on DB2 on the 390 and don't even need the transaction!
Kyle
 
Nigel Kat
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Personally, I'd love to, but that would require retooling of the host application that we aren't quite ready to do yet. The application it hits is not entirely DB2, depending on the specific request, the data may come from VSAM files or DB2. Consequently there is a controlling program in the front of it all that will take of the transaction processing from the point of the XML wrapper. I can use this guy, pretty much as-is. I'm more directed to getting a web app to talk to a CICS
transaction/application with the minimum number of moving parts in between.
DAXD just went on my list though....
Thx
Kat
>^..^<
 
Nigel Kat
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Probably the best explanation is an attempt to interact with a proprietary subsystem architected over 10 years ago that allowed applications to use a limited subset of SQL to select or update data on a remote system(no joins, etc). We have 3 possible interfaces to this system, the easiest of which adds a very basic XML wrapper to the SQL statement & allows the same message to be handled via 2 different protocols (SNA LU6.2 or MQSeries messaging). For the protocol, we'll build both, but this piece is the LU6.2 between 2 CICS regions. We currently have a way of exercising the MQS version. All the processing in the background remains the same.
I'm working through the details of a basic web service/application that will handle the XML wrapper & the sending & recieving of the message from the user.
Am I being clear as mud?
Kat
>^..^<
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!