| Author |
Message
|
| kotha |
 Posted: Fri Mar 25, 2005 6:16 am Post subject: WAS issues |
 |
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
presently we are using IIS server for all web application and want to move to WAS for workflow applications. Instead of communicating WAS with exisiting IIS server, I want to make WAS, presently using for development, as main server for my workflow application.
To make transition from IIS to WAS, what are the issues to be considered and what are the merits and demerits?.
Could anyone support me to make desicion. |
|
| Back to top |
|
 |
| vennela |
| Posted: Sun Mar 27, 2005 7:21 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| If you use WAS, then IBM supports the web client. |
|
| Back to top |
|
|
| kotha |
| Posted: Tue Mar 29, 2005 11:01 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
Vennela,
If I use IIS and Work Flow Standard Client, do I need WAS? |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Mar 29, 2005 11:06 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| I think IIS is somekind of webserver an equivalent of IBM HTTP server. But for running the IBM standard web client you need a J2EE app server like WAS or WebLogic or Apache or something like that. |
|
| Back to top |
|
|
| kotha |
| Posted: Tue Mar 29, 2005 11:18 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| vennela wrote: |
| But for running the IBM standard web client you need a J2EE app server like WAS or WebLogic or Apache or something like that. |
Yes IIS will replace HTTP Server. As you said, we need WAS etc to run web client but if i use Standard Client (the other one we use with out WAS) do I need to install WAS to make the communication between IIS and Workflow ? |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Mar 29, 2005 11:20 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
By "Standard Client" if you mean the thick runtime client, then you dont need WAS. you will need an MQServer or MQClient to communicate with WF Server.
_________________
-Ratan |
|
| Back to top |
|
|
| kotha |
| Posted: Tue Mar 29, 2005 11:26 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| Ratan wrote: |
| you will need an MQServer or MQClient to communicate with WF Server. |
Yes, i mean thick clinet. Is WS Server is part of the Workflow? or is it another software? |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Mar 29, 2005 12:07 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Yes, i mean thick clinet. Is WS Server is part of the Workflow? or is it another software? |
It is another software. WAS is WebSphere Application Server. |
|
| Back to top |
|
|
| kotha |
| Posted: Tue Mar 29, 2005 12:34 pm Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| Ratan wrote: |
| By "Standard Client" if you mean the thick runtime client, then you dont need WAS. you will need an MQServer or MQClient to communicate with WF Server. |
vennela,
in the previous message, WS Server is typo. in the above quoted message, WF server mentioned.
My question: is WF Server another software? |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Mar 29, 2005 12:40 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
WF Server is Workflow (MQSeries Workflow).
_________________
-Ratan |
|
| Back to top |
|
|
| kotha |
| Posted: Tue Mar 29, 2005 12:42 pm Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
|
| Back to top |
|
|
| CHF |
| Posted: Tue Mar 29, 2005 1:30 pm Post subject: |
|
|
Master
Joined: 16 Dec 2003
Posts: 297
|
|
| Back to top |
|
|
|
|
