| Author |
Message
|
| JoseR |
 Posted: Wed Apr 12, 2006 11:51 am Post subject: Web Service Router |
 |
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
Hello,
I have WMB v6 fp1 running on AIX. I recently run into the following request:
1) Developer from his/her Application server (WAS/WPS v6) calls a web service (SOAP request)
2) If the App from a Dev environment requests the web service (Broker web service router). The Broker should route the request to the development web service.
3) But if the same App from a Production environment requests the web service (Broker web service router). The Broker should route the request to the production web service.
The routing mechanisim is the request.
The reason for this is that the Application developer would not have to change his/her code when moving it from Dev to Prod.
Me challenge is the following:
Identify from which server (Dev or Prod) the request is coming from and route the SOAP request to the correct web service according to this finding. Hence using the broker as a web service router.
_________________
Jose R
WWJD
< ))><< |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Apr 12, 2006 11:53 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
yuck... mixing production and test environments is always asking for trouble. IMHO.
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 12, 2006 12:04 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It'd be easier to use hosts files to fake the service address to point to a dev broker or a prod broker in different environments.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JoseR |
| Posted: Wed Apr 12, 2006 12:25 pm Post subject: |
|
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
The idea behind this request is that the developer would only have to create one Application which would then get promoted to QA and later PROD with no new developer intervention.
The current scenario works as follows:
<no broker involved>
AppServer1 [from DEV]->(soap request http://mydevsoap)->WebService[DEV]
AppServer1 [from PROD]->(soap request http://myprodsoap)->WebService[PROD]
Note: to promote this Application to QA and Prod the developer needs to make an application update to point to the Production WebService.
Proposed scenario:
AppServer1 [fromDEV]->Broker (soap request http://mybrokersoap)->(soap request http://mydevsoap)->WebService[DEV]
AppServer1 [from PROD]->Broker (soap request http://mybrokersoap)->(soap request http://myprodsoap)->WebService[PROD]
Allowing the developer to interface with a unique WebService (coming from the broker) and hidding the dev and prod web services from them.
_________________
Jose R
WWJD
<))><< |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 12, 2006 12:40 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So the developer needs to use a properties file and read the URL to access from there - and have a different properties file for dev than for prod.
But you SHOULD NOT be running Dev and Prod on the same hardware.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JoseR |
| Posted: Wed Apr 12, 2006 1:09 pm Post subject: |
|
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
It seems like a fear solution.
I want to thank you for all your input on this subject.
_________________
Jose R
WWJD
<))><< |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 12, 2006 1:31 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you're in any kind of situation where your IT architecture is audited, you will get flagged *big time* for mixing environments.
There are also lesser things to worry about - like processing production customer data on a dev system.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
