TechRef WCF Services Guide

[markdamen]

Hi

I’ve read and put together the code in Visual Studio that’s contained within the WCF Techref guide. I would however like to try connecting using Net.TCP and Windows auth. Can somebody give me the code required to connect in this manner. This is what is currently in my project, taken straight from the techref guide:

            private enum EndpointBindingType
    {
        SOAPHttp,
        BasicHttp,
        Windows
    }

    static void Main(string[] args)
    {
        ServicePointManager.ServerCertificateValidationCallback += (sender, certificate, chain, errors) => { return true; };
        EndpointBindingType bindingType = EndpointBindingType.SOAPHttp;

        string epicorUserID = "manager";
        string epiorUserPassword = "Epicor123";
        string scheme = "http";
        if (bindingType == EndpointBindingType.BasicHttp)
        {
            scheme = "https";
        }
        UriBuilder builder = new UriBuilder(scheme, "localhost");

        builder.Path = "ERP100500/Ice/Lib/SessionMod.svc";

        SessionModSvcContractClient sessionModClient = GetClient < SessionModSvcContractClient, SessionModSvcContract > (
            builder.Uri.ToString(),
            epicorUserID,
            epiorUserPassword,
            bindingType);
        builder.Path = "ERP100500/Erp/BO/AbcCode.svc";
        ABCCodeSvcContractClient abcCodeClient = GetClient < ABCCodeSvcContractClient, ABCCodeSvcContract > (
            builder.Uri.ToString(),
            epicorUserID,
            epiorUserPassword,
            bindingType);
        Guid sessionId = Guid.Empty;
        sessionId = sessionModClient.Login();
        sessionModClient.Endpoint.EndpointBehaviors.Add(new HookServiceBehavior(sessionId, epicorUserID));
        abcCodeClient.Endpoint.EndpointBehaviors.Add(new HookServiceBehavior(sessionId, epicorUserID));

Thanks so much,
Mark

[Bart_Elia]

If you want to use net.tcp you need to use the client DLL proxies. The examples use the SOAP protocol to interop nicely with other clients (Though not as nice as REST does now). Net.tcp does not have a SOAP flavor out of the box so you would need to use the custom binary serialization approach which means knowing the column order, etc on the client - a royal pain unless you want to rewrite the client generator.

So what is the interest in NET.TCP?

[markdamen]

Hi Bart, thanks for the reply. I’m a complete beginner when it comes to creating code outside of Epicor – I’ve done a some inside the Custom Code Blocks in BPMs and customisations with good results, but I want to expand my knowledge and capability to develop further. I thought a good place to start would be that guide, then build up different examples of interacting with data in our test environment.

No particular interested in Net.TCP, only that the app server is already configured and the desired usage is within the LAN. I can setup the HTTP binding, but if I’m just starting out to learn this should I be going straight for REST?

Regards
Mark

[josecgomez]

Go REST if you can. However I believe the WCF http endpoint is there even if you only have net.tcp setup.
Have you tried just calling the example without changing anything?
I don’t recall if you have to do anything special for that one. I don’t think so

[markdamen]

We’re only configured for Windows auth, not username/password. What changes would I need to make to the code for this? I can see in the enum that the options are only SOAPHttp and BasicHttp. I added Windows here, but would need help in creating the right connection.

Many Thanks

[bw2868bond (Bernie Walker)]

I would love to see this converted to REST (It would give me a clearer picture into converting quite a few web apps to REST)

QueryExecutionTableset _qeT = new QueryExecutionTableset();
ExecutionFilterRow _qeR = new ExecutionFilterRow();
_qeT.ExecutionFilter = new ExecutionFilterTable();
_qeR.DataTableID = “OrderHed”;
_qeR.FieldName = “PONum”;
_qeR.CompOp = “Like”;
_qeR.RValue = “%” + + “%”;
_qeR.RowMod = “A”;
_qeR.SysRowID = Guid.NewGuid();
_qeT.ExecutionFilter.Add(_qeR);
ExecutionFilterRow _qeR1 = new ExecutionFilterRow();
_qeR1.CompOp = “=”;
_qeR1.RValue = ;
_qeR1.DataTableID = “OrderDtl”;
_qeR1.FieldName = “POLine”;
_qeR1.RowMod = “A”;
_qeR1.SysRowID = Guid.NewGuid();
_qeT.ExecutionFilter.Add(_qeR1);

                    var dsTest = dqSvcClient.ExecuteByID("<my BAQ name>", _qeT);

[Olga (Olga Klimova)]

You will have to create custom WCF binding to do this. Both in the server and in the client .config

[Olga (Olga Klimova)]

If you go to the Rest API help for th DynamicQuery.ExecuteByID - address should be like
http://localhost/ice3/api/help/methods/Ice.BO.DynamicQuerySvc/index#!/Custom_methods/Op2
you will see the example of the parameters above.
You should use something like:

{
“queryID”: “string”,
“executionParams”: {
“ExecutionFilter”: [
{
“DataTableID”: “string”,
“FieldName”: “string”,
“Neg”: true,
“CompOp”: “string”,
“RValue”: “string”,
“SysRowID”: “00000000-0000-0000-0000-000000000000”,
“RowMod”: “string”
},
{
“DataTableID”: “string”,
“FieldName”: “string”,
“Neg”: true,
“CompOp”: “string”,
“RValue”: “string”,
“SysRowID”: “00000000-0000-0000-0000-000000000000”,
“RowMod”: “string”
}
]
}
}

[mathis1337 (Aaron Mathis)]

Mark,

I feel like this has become over complicated. Excuting code outside Epicor is quite easy.

First, you make a session using the Ice.Core.Session assembly.
Session session = new Session(“******“, “********”, Session.LicenseType.Default, @”.Sysconfig Location”);

Second, you choose your BO. Make a call to the WCF Service Support and bam. You can now call Epicor methods for that BO, like GetByID, or Update, or anything else. If you’d like to learn more about this I’d be happy to explain further.

var customerBO = WCFServiceSupport.CreateImpl<Erp.Proxy.BO.CustomerImpl>(session, Erp.Proxy.BO.CustomerImpl.UriPath);

Now you can do things like :
CustomerDataSet cds = new CustomerDataSet();

customerBO.GetCustomerTerritory(cds, 0);

	cds.Customer[0].CreditHold = false;
	cds.Customer[0].SalesRepName = "John Doe";
	
	//Required check to verify customer is not on credit hold. Credit hold must be set to false before this method.
	customerBO.CheckCreditHold(cds, out vMessage);

	customerBO.Update(cds);

My email is aaron.mathis@soferox.com
if you need further assistance.

[bw2868bond (Bernie Walker)]

So I tried that for a simple query and got no where

§ Curl

§ curl -X POST --header ‘Content-Type: application/json’ --header ‘Accept: application/json’ -d '{

§ “queryID”: “JobStatus”,

§ “executionParams”: {

§ “ExecutionFilter”: [

§ {

§ “DataTableID”: “JobHead”,

§ “FieldName”: “JobNum”,

§ “Neg”: false,

§ “CompOp”: “=”,

§ “RValue”: “108118”,

§ “SysRowID”: “00000000-0000-0000-0000-000000000000”,

§ “RowMod”: “A”

§ }

§ ]

§ }

}’ ‘https://epicor10demo/ERP101500/api/v1/Ice.BO.DynamicQuerySvc/ExecuteByID’

Request URL

https://epicor10demo/ERP101500/api/v1/Ice.BO.DynamicQuerySvc/ExecuteByID

Response Body

no content

Response Code

0

Response Headers

{
“error”: “no response from server”
}

[Olga (Olga Klimova)]

Were you able to run this from help page?

[bw2868bond (Bernie Walker)]

No – I think I need to have the FQDN in the url not just the server name

[Olga (Olga Klimova)]

Unfortunately, it is not clear what problem you have with FQDN. Probably you need to create separate topic and describe what is not working for you.

[markdamen]

Seems like different people have different preferences and are suggesting different methods. Aaron is saying use the client dlls, Bart saying don’t, and then choice between REST and not.

Is there a REST guide on EpicWeb somewhere?

[bw2868bond (Bernie Walker)]

Will do
all I wanted was a OData single line url to retrieve the results for a dynamic query

the ‘help’ page crafts the url to be ‘https://servername/share name/’ etc
I need ‘https://servername.mydomain.com/share name/’ for it to work - it is not including .mydomain.com in the url

[Bart_Elia]

Sitting in an airport heading home for a week off to rest my vocal chords

I promise all an overview and trade off doc (I owe our docs team too so thanks to all in advance for volunteering to proof read).

Quick Sumnary from whay had seen said.
The session based using net tcp is the first approach ever documented and released. It’s is still the fastest and works fine. You have to deploy the dlls somehow, keep them updated. You have to have same dotnet version. You have to be on windows in as well. So more deployment maintenance.

Next is the service approach. You use soap so can call from most any os. Its just that soap is not that friendly in all clients. It’s also not as fast as raw net.tcp where we control both sides of the wire.

This week we released the REST approach. With opt in columns you can speed things unlike the options. It can speak json or xml so is very flexible and easy to get going from any platform.

Does that help while I jump on a plane?
(And yes we owe you those examples in github)

[markdamen]

Perfect, thanks Bart. Some examples of each, to get started in Visual Studio would be the icing on the cake. That would be useful for all customers I’m sure! Thank you.

[Olga (Olga Klimova)]

Help creates address from the browser URL

[bw2868bond (Bernie Walker)]

It sure doesn’t look like it on my system

[Olga (Olga Klimova)]

interesting. And what if you use short computer-only name in the browser;s address line? will it work (if you suppress certificate error)