Approximately within 2 weeks, I did a research about it. In the research, the goal is to call the Web Service of Web Application Server belong to SAP Netweaver 2004 ver 6.4. In addition the calling is in at runtime. It means, we call the service based on the data of wsdl url which is specified in database.
I have difficulty in making it as dynamic as possible (runtime invoking) and also authentication cases to communicateto SAP. However, I did two ways or two option in order to comunicate to Web Service of SAP. Those are:
- By generating the proxy class first and then call the class.
- By using the SOAP Toolkit 3.0
However, those are still not a good option i think, each of them has the advantage and drawback. First, if we use generated proxy class, we should download the WSDL become the local file, since if we access directly, it need authentication. in order to download it, we should specify the authentication. Moreover, we should generate the local WSDL file to be a proxy class in the format *.cs and then compile it to be an assembly. The last, we should add the assembly as the project reference. The drawbacks of this way is related to performance and optimization, since we do many steps to take goal which is communicate to SAP Web Service.
Besides, there is another way, which is the second option. That is we use SOAP Toolkit 3.0 We just use the SoapCLient30 class object in order to communicate to other system like SAP. We just provide the property in order to communicate like Url of WSDL, method or procedure we want to call, and also the authentication path. However, this way based on forum and also my senior in Inersia having a problem with Windows Server 2003 in some cases. And we can predict the possibility to those cases. Sometimes, it may work, sometime it works. But, when I use the system in Window Server 2003 32 bit, it works. However, i haven’t test it in 64 bit version. I guess it may not work in 64 bit version.
Actually, I have another way which is on the research and it is on going… I use the SOAP message directly by using Webrequest class object provided by .NET. But, the format of SOAP message to communicate to SAP is not found yet…
Hopefully this Monday it is done…
Cybecitzen's Weblog 