
John Dean (FNZ Securities) asked a question.
I'm investigating moving an existing SOAP API under the classic appserver to PAS.
When we deployed under the classic AppServer, we were able to access different SOAP API versions under the same URL. I can't seem to find a way to do this under PAS, if I try and deploy multiple wsm files to the same application, it fails after the first deployment.
The only way I can see this working under PAS, is to create different applications in PAS for each of the versions, which means they now have different URL's.
Under Classic AppServer
---------------
$ wsaman -port <AdminServerPort> -i <instanceName> -appname TreasuryGUIv1 -enable
$ wsaman -port <AdminServerPort> -i <instanceName> -appname TreasuryGUIv2 -enable
$ wsaman -port <AdminServerPort> -i <instanceName> -appname TreasuryGUIv3 -enable
Under PAS.
---------------
Create new applications, under the same PAS instance.
tcman.bat deploy -a TreasuryGUIv1 %DLC%/servers/pasoe/extras/oeabl.war
tcman.bat deploy -a TreasuryGUIv2 %DLC%/servers/pasoe/extras/oeabl.war
tcman.bat deploy -a TreasuryGUIv3 %DLC%/servers/pasoe/extras/oeabl.war
Deploy SOAP API to new applications.
deploySOAP. TreasuryGUIv1.wsm TreasuryGUIv1
deploySOAP. TreasuryGUIv2.wsm TreasuryGUIv2
deploySOAP. TreasuryGUIv3.wsm TreasuryGUIv3
Is there a way to do this under PAS, so the different versions can be accessed using the same URL, using the namespace to hit the different versions.
Hi @John Dean (FNZ Securities) this requires further investigation to provide you with a possible solution. If you haven't done so already, please consider creating a ticket with Technical Support @ Support Link landing Page