Do you have to communicate directly to the DB2 server AND/OR the application server? I would image you have a bunch of options.
My initial thought is to install unixODBC with the proper driver for connecting to DB2. This way you can develop scripts on the Linux server to expose an interface to Flex and access the DB2 data. My experience with unixODBC for connections to DB2 have been successful when the datasets are small. If you are just going to be talking to the Websphere server and the server is already exposing web services you can consume them on the Linux server and expose them to Flex. I am assuming here that the Linux server does have access to DB2 and Websphere. At the very least you will probably want to get a LAMP stack running on the Linux machine. Just some thoughts. Nick --- In [email protected], "byte.sensei" <byte.sen...@...> wrote: > > I've been working with Flex using .NET HTTP/SOAP web services and MS SQL > Server for a while. Recently I started a new project using IBM Websphere > Application Server (6.1) and DB2. The environment is setup with a simple > Apache/Linux web server (no Websphere or other app server components), then a > Webspere App Server 6.1 behind a firewall, and finally a DB2 server (also > behind the firewall). The only server that is accessible externally is the > Apache/Linux web server. > > My Flex app requires data from the DB2 database, and I'm used to getting it > via HTTP/SOAP web service calls. However, with nothing but a bare > Apache/Linux web server that is accessible externally, I'm trying to figure > out how to best create a simple server-side HTTP listener that will take data > requests, communicate with the WAS/DB2 servers, then send the data back to > the Flex client. > > What choices/options are there for this scenario? I do have the capability of > installing some server-side components to the Apache/Linux web server. >
