Also what is the default connection time out for SMS.
Thanks,
Tarun

Hi,
In the SMS webservice sample client -
it is recommended to keep connection to AES /ACD open over multiple requests to avoid initial setup time. So I am planning to implement a pool of ServiceRequest objects, My doubt is if the connection context is lost - then what kind of indication / exception will I get so that I van attempt reconnect ? Also Is there a way in API to know if the transport connection and / or connection context is valid ? appreciate your reply on this.

Thanks,
Tarun

Hi Craig,


Thanks for your explanation. How do I get CM SAT - is it a thick client that needs to be downloaded . Where can I download from ?

Appreciate your help as always.

Regards,
Tarun

Hi,

I am trying to figure out the query semantics of the webservices interface to AES .

In samples I see to list 5 agents following xml is used
<modelFields>
<Station>
<Extension></Extension>
<Type></Type>
<Port></Port>
<Name></Name>
</Station>
</modelFields>
<operation>list</operation>
<objectname></objectname>
<qualifier>count 5</qualifier>

Is there any example of update operation - Say if I need to update skill of an agent, where does the where clause and update values go ? Is there any documentation around on this, Appreciate your help on this,

Thanks,
Tarun

Thanks for your reply. I dont see this problem anymore as there was un upgrade done to the ACD AES and now I see the results - The other issue however is I see is I get folliwing exception while accessing SMS programmatically.

java.security.cert.CertificateException: No subject alternative names present if I try to use https, in Browser I can see that certificate is invalid.

Is there anything that I can do on the client side to ignore this error ?

Appreciate your response.

Thanks,
Tarun

I changed from https to http and I dont get this error any more on my windows machine .
However when I submit the example xml that comes bundled with the example app.



<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:submitRequest xmlns:ns2="http://xml.avaya.com/ws/SystemManagementService/2008/07/01" xmlns:ns3="http://xml.avaya.com/ws/session">
<modelFields>
<Station>
<Extension></Extension>
<Type></Type>
<Port></Port>
<Name></Name>
</Station>
</modelFields>
<operation>list</operation>
<objectname></objectname>
<qualifier>count 5</qualifier>
</ns2:submitRequest>



Response I get is

execRequest:: submitRequestThe request returned an error (result_code ==1);com.avaya.smsxml.ModelChoices@23cd4638;1 00000000 5bc5 "station" is an invalid entry; please press HELP

Is it returned by SMS ? if yes then is there anything wrong with the request xml or on the SMS side ?


Is there any documentation that talks about effect of "operations" on the model elements. e,g if I send skill update for an agent using xml - if agent is in 2 branches and skill update is only for one branch - then is the update applied only to one branch or it will wipe out the other branch.

Appreciate your help.
Thanks,
Tarun

I dont see last error in my dev environment - So looks likes it has got something to do with paths in unix. In dev env I however get following exception
Caused by: java.security.cert.CertificateException: No subject alternative names present
   at sun.security.util.HostnameChecker.matchIP(HostnameChecker.java:142)
   at sun.security.util.HostnameChecker.match(HostnameChecker.java:91)
   at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:347)
   at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:203)
   at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126)
   at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1319)

Any ideas how to get past this ?

Thanks,
Tarun

Thanks for your reply . I have checked . It is well formatted. It is SystemManagementService,wsdl that comes with examples . I have not made any change to it.

I changed the location in wsdllocation in build and now I get slightly different error.

Instead of S it complains on . now .

om.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected charac
ter '.' (code 46) in prolog; expected '<'
at [row,col,system-id]: [1,1,"file:/apps/opt/aims2/appserver/lib/"]
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:267)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:95)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:110)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:100)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.hasWSDLDefinitions(RuntimeWSDLParser.java:220)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:130)
at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:271)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:234)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:182)
at weblogic.wsee.jaxws.spi.WLSServiceDelegate.<init>(WLSServiceDelegate.java:40)
at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.<init>(WLSProvider.java:380)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:79)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
at javax.xml.ws.Service.<init>(Service.java:56)

I am getting folowing error while connecting with the the webs service via stubs generated in my client code. Will appreciate any help or pointers.

com.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected charac
ter 'S' (code 83) in prolog; expected '<'
at [row,col,system-id]: [1,1,"file:/apps/opt/aims2/appserver/config/ws/wsdl_xml/"]
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:267)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:95)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:110)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:100)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.hasWSDLDefinitions(RuntimeWSDLParser.java:220)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:130)
at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:271)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:234)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:182)
at weblogic.wsee.jaxws.spi.WLSServiceDelegate.<init>(WLSServiceDelegate.java:40)
at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.<init>(WLSProvider.java:380)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:79)
...skipping...
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:182)
at weblogic.wsee.jaxws.spi.WLSServiceDelegate.<init>(WLSServiceDelegate.java:40)
at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.<init>(WLSProvider.java:380)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:79)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
at javax.xml.ws.Service.<init>(Service.java:56)
at com.avaya.smsxml.SystemManagementService.<init>(SystemManagementService.java:42)
at com.verizon.cms.server.comm.ServiceRequest.setup(ServiceRequest.java:163)
at com.verizon.cms.server.comm.ServiceRequest.execRequest(ServiceRequest.java:275)
at com.verizon.cms.server.AESTask.processTask(AESTask.java:161)
at com.verizon.cms.server.AES$AESConnectionThread.run(AES.java:379)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'S' (code 83) in prolog; expected '<'
at [row,col,system-id]: [1,1,"file:/apps/opt/aims2/appserver/config/ws/wsdl_xml/"]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:623)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at com.sun.xml.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:92)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:76)
... 17 more


Thanks,
Tarun Jindal
Verizon

I see that sessionId returned is not the same when I execute the requests over a single connection.

Hi,

I am using java client to connect to SMS service. I open a session and maintain it for a batch of change requests.
What I see is after 2 successful processing of requests for the session - I start seeing this in error log

--> SOAP message: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><S
OAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>Connection Failed: Login resources unavailable: CM Server Closed Co
nnection
</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
---> FAULT: Connection Failed: Login resources unavailable: CM Server Closed Connection

---> FAULT CODE: SOAP-ENV:Server
javax.xml.ws.WebServiceException: java.lang.RuntimeException: [SOAP-ENV:Fault: null]
at com.sun.xml.ws.handler.ClientSOAPHandlerTube.callHandlersOnResponse(ClientSOAPHandlerTube.java:173)
at com.sun.xml.ws.handler.HandlerTube.processResponse(HandlerTube.java:162)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:877)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
at com.sun.xml.ws.client.Stub.process(Stub.java:272)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.


After this none of the requests go through.

In my code I release the session using following if I see null result from previous request and wait for 10 seconds before attempting new session.

public void releaseSession() {

try {

responseSID = SIDHandler.getSID();
logger.warn(" ServiceRequest::releaseSession before close responseSID " + responseSID);
ReturnType returnType = port.release(null);
Result returnResult = returnType.getReturn();
logger.warn(" ServiceRequest::releaseSession returnResult " + returnResult);
logger.warn(" ServiceRequest::releaseSession returnResult.getMessageText(); " + returnResult.getMessageText());
logger.warn(" ServiceRequest::releaseSession returnResult.getResultCode(); " + returnResult.getResultCode());
responseSID = SIDHandler.getSID();
logger.warn(" ServiceRequest::releaseSession after close responseSID " + responseSID);

}


This very puzzling - I see it working end to end for 2 requests and then it starts failing - any idea where the issue may be ?


Thanks,
Tarun