If this is simply a data sync integration between 2 DBs and there is no anticipation of needing the source data in other future cases then Broker is probably not useful.
[Edit] Keep in mind that my default design approach is to not use Broker unless there is a specific benefit to doing so. Others have a default approach in which they use Broker even if there is no immediate benefit, but anticipating future needs.
Also, depending upon other aspects of this scenario, I might not use IS in this case either. Large data movement/batch operations isn’t the best fit for IS. You might consider using an ETL tool and foregoing converting to/from XML representation.
I am using the scheduler to call the webservice in particular time interval. Here i need the last run time of scheduler which i will use to fetch the updated data from webservice. Can i get the last runtime of scheduler in webMethods.
Please see the following html page it is the html for one web service connector. When i run this webservice connector giving proper input. It gives me following error.
com.wm.app.b2b.server.ServiceException: [ISS.0088.9139] Output parameters do not conform to targetOutputSignature:
errorCode=VV-004
pathName=/getCurrencyReturn/code
errorMessage=[ISC.0082.9031] Type mismatch, Document expected
It would appear that the web service response is returning a value directly in /getCurrencyReturn/code but your connector is expecting a document (fields within /getCurrencyReturn/code rather than a value). Or perhaps no value/fields at all but code is required.
I am unable to resolve this problem. Whatever you said may correct but what action should i take to resolve this issue. Please find the screen shot at the following link which i get after clicking Details button at error pop up.
This indicates that the web service is returning a string while your web service connector is expecting a document. Either the WSDL used to create the connector was incorrect/outdated or the web service is not returning the proper data structure.
Regen the service from an updated WSDL may be the right fix.
Can i call a webservice method directly from webMethods ? I dont have the wsdl file to create web service descriptor. I just have following signature to call [webmethod] operation of web service (restless webservice).
Here i found an error while creating WSD. I have researched a lot but not finding any solution. It will be good if you can help on that. Following is the error snipets. I am also attaching the wsdl i am using to create wsd from that.
com.wm.app.b2b.server.ServiceException: com.wm.lang.wsdl.WSDException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9322] External ID is missing the system ID
at wm.server.ws.wsdl2wsd(ws.java:1132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:403)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:631)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:40)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:241)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:228)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:624)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:536)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:237)
at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:151)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:186)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:327)
at com.wm.util.pool.PooledThread.run(PooledThread.java:118)
at java.lang.Thread.run(Thread.java:595)