I found the issue myself. Since I used the work manager customer service 2.0 deploye executable. It hardcoded web socket sub URL /SAPWM. So the app name you defined in smp server can not work And /SAPCS in the document can not work either. Unfortunetly there is no document on this. I found the clue in the server startup log. Since smp3 service pack 3 still only support one agentry server running at a time I can see how this hard coded name will work. My guess is in the future it will change and the app name user defined in smp server shall be used to differeniate which app the client want to connect to.
↧