K
knavneet
Guest
There could be different ways to manage versions. In your case you have two WSA instances named wsa_v1 and wsa_v2. If they are associated with same appserver broker then it will run same version of test.r. So, in your example above you will need test_v1.r and test_v2.r However, if you wanted the .r code name to be same, you could do the following: (I will put a caveat emptor here that this is what I can think of and there could be better ways to do it) 1. create two appserver brokers viz. soapbroker1 and soapbroker2. 2. create version folders say C:\OpenEdge\WRK\pcode\v1 and C:\OpenEdge\WRK\pcode\v2. 3. C:\OpenEdge\WRK\pcode\v1 contains version 1 test.r and C:\OpenEdge\WRK\pcode\v2 has version 2 test.r 4. Add C:\OpenEdge\WRK\pcode\v1 to the propath of soapbroker1 and C:\OpenEdge\WRK\pcode\v2 to propath of sopabroker2 5. Check the appService name for the two instances and associate wsa_v1 with soapbroker1 and wsa_v2 with soapbroker2 proenv> wsaman -i wsa_v1 -getdefaults This will show you all the runtime properties of wsa_v1 including the appserviceName (which by default will be asbroker1) You can change it using wsaman -setdefaults command proenv> wsaman -i wsa_v1 -prop appserviceName -value soapbroker1-setdefaults. Similarly, proenv> wsaman -i wsa_v2 -getdefaults This will show you all the runtime properties of wsa_v1 including the appserviceName (which by default will be asbroker1) You can change it using wsaman -setdefaults command proenv> wsaman -i wsa_v2 -prop appserviceName -value soapbroker2 -setdefaults. Just my two cents on this topic which can have multiple solutions (and I believe better ones). Thanks, Navneet
Continue reading...
Continue reading...