Handbuch ESR

More documents

Recommendations

Info

4.2 Implementation in C# It is presumed that the preparations in section 2.1 have already been carried out. The first step is to generate the proxy classes. If you are working with Visual Studio .NET you can open a new or existing project. Then select "Add Web Reference" to add a web reference to the project. Enter the URL of the WSDL file in the window that now appears. Next, you can change the namespace, if necessary. The generated class is located in the Reference.cs file. In this case, minor adjustments have to be made to this file. We therefore recommend that you copy the contents of Reference.cs and paste them into a new file, e.g. UploadInvoiceProxy.cs. The new file can, for example, be stored in the project root folder. Because WSE 2.0 is being used, the class declaration needs to be changed: After generation it reads: public class UploadInvoice : System.Web.Services.Protocols.SoapHttpClientProtocol Edit it to read as follows: public class UploadInvoice : Microsoft.Web.Services2.WebServicesClientProtocol The reference to Microsoft.Web.Services2.dll also needs to be added to the project. The WebReferences directory can then be deleted provided that no other web services are linked in. The functionality of the new class can now be used just like an ordinary C# class. You can also create the proxy class with the wsdl command line tool. For our example the command syntax could be as follows: ws dl /n:B2BWebServices /o:UploadInvoiceProxy.cs /protocol:SOAP /l:CS ht tps://ebill-test.yellowworld.ch/B2BWebServices/UploadInvoice.asmx?WSDL In this case as well, the class has to be adjusted as above. Now for the implementation itself. Here we will only show the example of the biller, i.e. the upload client. The bill issuer must have a valid username and password. If possible these should be stored in a separate file or database and must on no account be accessible to unauthorized persons. First there is an initialization block in which the username, password and BillerID are read in. How you read them in is up to you. Invoice[] invoices = new Invoice[txtFilenames.Lines.Length]; NotProcessedInvoice[] npInvoices = null; String Username = ……; String Password = ……; String BillerID = ……; Next, the invoices array is filled with the FileType, TransactionID and Data of each file. This should present no problems. The WS-Security specification defines a username token which can be used for authenticating web services (for further information refer to ht tp://w ww.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os UsernameTokenProfile.pdf). 12/19
Because the web service is located behind a proxy, a redirection URL and a destination URL have to be specified when initializing the proxy class. UploadServiceDestination ht tps://ebill-test.yellowworld.ch:9443/B2BWebServices/UploadInvoice.asmx UploadServiceVia ht tps://ebill-test.yellowworld.ch/B2BWebServices/UploadInvoice.asmx UsernameToken token = new UsernameToken( Username, Password, PasswordOption.SendPlainText ); UploadInvoiceProxy.UploadInvoiceProxy uploadProxy = new UploadInvoiceProxy.UploadInvoiceProxy(); Microsoft.Web.Services2.Addressing.EndpointReference epr = new Microsoft.Web.Services2.Addressing.EndpointReference(new Uri(ConfigurationSettings.AppSettings["UploadServiceDestination"])); epr.Via = new Uri(ConfigurationSettings.AppSettings["UploadServiceVia"]); uploadProxy.Destination = epr; uploadProxy.RequestSoapContext.Security.Tokens.Add( token ); For stronger authentication security it’s fairly recommended to use additionally to the username token, the binary security token (for further information refer to ht tp://ww w.oasis-open.org/committees/download.php/16785/wss-v1.1-spec-os-x509TokenProfile.pdf). To use a binary security token, a client certificate is required. The following example shows how to implement a binary security token in a webservice client. // create SecurityToken X509SecurityToken x509Token = new X509SecurityToken(x509Certificate); // add SecurityToken uploadProxy.RequestSoapContext.Security.Tokens.Add(x509Token); // sign the message uploadProxy.RequestSoapContext.Security.Elements.Add(new MessageSignature(x509Token)); For a further level of security, WS-Security defines a timestamp ht tp://w ww.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf with which you can ensure that the request is only valid for a certain time period. uploadProxy.RequestSoapContext.Security.Timestamp.TtlInSeconds = 60; Now comes the actual web service call. npInvoices = uploadProxy.UploadFiles(invoices, BillerID); The client must have the time zone set to GMT +1 and the time difference between client and server may not exceed more than 1 minute. Finally, a simple evaluation of the returned value is performed. StringBuilder sb = new StringBuilder(); if (npInvoices != null && npInvoices.Length > 0) { sb.Append("Nicht eingelieferte Files!\r\n"); sb.Append("**************************\r\n\r\n"); for (int i=0; i
Page 1 and 2: E-bill Instruction for a client imp
Page 3 and 4: 1. Introduction Within the e-bill p
Page 5 and 6: A NotProcessedInvoice entry indicat
Page 7 and 8: public class ProtocolReport { publi
Page 9 and 10: 3.2.1.2 GetInvoiceByID This method
Page 11: 4. Implementation This section serv
Page 15 and 16: There is another configuration file
Page 17 and 18: Next, there is a simple evaluation
Page 19: Annex A Links relating to the integ

Handbuch ESR

Create successful ePaper yourself

Delete template?

Save as template?