What is the fastest way to generate an POST or GET SOAP XML payload for SuiteTalk Web services? - netsuite

Hopefully someone can help me.
I am currently using POSTMAN to run SOAP web service tests on NetSuite.
Annoyingly, I am having to generate the body of an XML request from scratch, and would really like a method whereby a basic template is generated for me, and I simply fill in the gaps. Creating an XML web request from scratch is prone to errors hence my question. I tried SOAPUI but it does not
Any ideas is most appreciated!

hope you remember me!! The easiest way would be to download any of the existing working SOAP web request from any running build and modify that to suit your need. There is no out of the box built in template that you could build on at least as per my knowledge. Please specify the record for which you are building the SOAP request

The easiest way is to not use POSTMAN.
I used to do a lot of this and what I'd do is:
generate the java client for SuiteTalk
install a recording proxy (I think WireMock does this -- the one I used to use doesn't seem to be around anymore)
use JUnit tests to hit SuiteTalk
in the test setup override the SSL config to ignore host name verification
test an API call
extract the complete working SOAP from the proxy logs
templatize the SOAP and use it where needed.

Related

Apigee Java Call Out Response

In a standalone java code, using Apache HTTPClient libs, implementing the NTLM Authentication with SharePoint Server and accessing its Web Service and receiving the huge XML content as response. Now this final output is in String format. Created the Java Call Out Policy and uploaded all the jars.
I need some help here,
How to pass the java's final output response to Apigee's response.
My requirement is: If I hit the Apigee API Proxy then I need to receive the Java's output(String) as Apigee's response.
Which policy is more appropriate to handle this response.
Appreciate your help! Thanks in Advance.
You can use the javacallout policy to author custom java code. Here is a related post in SO: Working With JAVA Callout in apigee?
You can try
message.setContent(string) to create the content, and
messageContext.setResponseMessage(Message)
in java code to directly write to output.

Difference between logging in into salesforce sandbox with and without consuming wsdl?

I am very new to Salesforce and it's API.
I am having a sandbox org and with it I have url, username, password, security token and last but not the least partner.wsdl
My aim was to connect and retrieve/create data.
Technologies at hand was nodejs
So here is how I started.
I searched over the internet and came to know that I need to create a client, SOAP client in order to login, create the connection and use that connection to create and access the Leads data.So I followed this sample where the wsdl was being consumed.
So I was able to connect
I was very happy on this success and then suddenly I wasn't able to identify/find a way where I can get the sObject.I looked hard for this but no luck. So posted a question on SO
Meanwhile I also looked for other node module and found jsforce
I used jsforce starting guide and created a client that was connecting to salesforce however without using the wsdl file.
Again I was happy, even more happy because I was having the sObject with me.
Now, what is the fundamental difference if I login using the local wsdl file and without wsdl file in the language of salesforce. Which one is the correct way of logging in?
Sorry if this question is not according to SO rules or if there is a typo.
I'm the author of jsforce you mentioned.
In that lib we use REST API mostly and SOAP APIs are only used in some specific calls like login or metadata. Even in such calls we don't use WSDLs because there's no good lib to generate client modules from WSDL in JavaScript/Node.js area. Instead we wrote modules for each APIs which generate SOAP XML strings and parse the response XML.
It is enough because these API message schema are static and fiesible in the specific version, unlike SOAP API Enterprise WSDL differs in organizations. So we can hard code the client module directly w/o generate it from WSDL.

#DocuSignAPI Unspecified_Error

I am trying to use CreateEnvelopesFromTemplatesAndForms.
I have used the PDF that I am uploading effectively using the simple CreateEnvelope. I have also used the PDF effectively by manually uploading it via the Web UI. So I don't think the error relates to the PDF.
Any hints on how to troubleshoot "Unspecified_Error" ?
I would suggest downloading SoapUI from SmartBear, then create a new SOAP Project and point it at DocuSign's WSDL: https://demo.docusign.net/api/3.0/api.asmx?WSDL. SoapUI will create sample calls for each of the DocuSign SOAP methods in the WSDL.
The error message you're getting means (generally) that you're not providing a field value that's required, or you have included a node tree that isn't necessarily required but since you included it, all of the values need to be valid.

how to call soap wcf webservices using ws.js or wcf.js node modules?

I have installed soapjs module and tried to access those service.
This service contains complexContent:
http://www.reportingsales.com/DeFactoSF1.asmx?WSDL
Could we get wcf service wsdl details(methods, input, output) using soapjs?
http://mli.crmnext.com/CRMnextWebApi/CRMnextService.svc?wsdl
Kindly give me some suggestions..
if possible give me some working soap client examples of those modules
ws.js and wcf.js are about defining security/mtom. they do not deal with the xml format, you need to bring the xml out of band (maybe copy a working sample from your logs).

WSDL off ServiceStack REST API

I know this at least IMO is a stupid request. Because WSDL is old hat and sucks compared to just doing a RESTful API. But I have a corporate "mandate" where we want to do a REST API but then corporate wants a WSDL still. I know..it makes no sense and apparently we can't push back and say NO and tell them to just use our future REST API.
So can you generate a WSDL if I were to start creating a REST API with ServiceStack? Meaning I add uri attributes and such? So that I can "make them happy"?
I prefer not to use WCF, it's a nightmare with a ton of attributes and configuration to try and hack a RPC style web service to try and be RESTful. Obviously that doesn't work out too well.
SOAP along with REST is supported and you can have REST API along with soap wsdl. There are some recommendations posted in servicestack wiki that you can review and get started! You just need to implement the restful service and soap, json, xml etc are automatically supported.

Resources