v2.4 Order Tracking API

Discussions related to order tracking development with the ProForm module.

Moderator: Phil Barton

Post Reply
muhsmann
Posts: 54
Joined: Thu Jan 15, 2009 5:41 pm

v2.4 Order Tracking API

Post by muhsmann »

When trying to create an instance of SelectServer class using the url "http://host:port/SelectServer" we're experiencing an exception stating
'http://host:port/SelectServer/Integration/v1/SessionManager.svc is too busy'

In the earlier version we defined and user to get network credentials - we have not changed that step and SDK help for 2.4 seems to still employ that method.
Hadi Chemaly

Re: v2.4 Order Tracking API

Post by Hadi Chemaly »

You need to use a url like this:

Code: Select all

http://<SelectServerMachineName>:<PortNumber>
You no longer need the "/SelectServer" part.

In other words:

Code: Select all

NetworkCredential credentials = new NetworkCredential("admin", "Passw0rd", SoftPro.ClientModel.Constants.ServerDomain);
SelectServer sps = new SelectServer("http://MACHINENAME:8080", credentials);
muhsmann
Posts: 54
Joined: Thu Jan 15, 2009 5:41 pm

Re: v2.4 Order Tracking API

Post by muhsmann »

Hadi,
Can you please explain the API technology used to handle this now compared to v 2.3 and earlier? It appeared to me that in the earlier versions the sever was a web service and now it looks like its a service we access via remoting or WCF.
Hadi Chemaly

Re: v2.4 Order Tracking API

Post by Hadi Chemaly »

The major change is that we are now using a Windows Service instead of IIS for the mid-tier.

Using the API is pretty much the same beyond the URL used to connect to the server. The URL modification was necessary to support side-by-side Select Servers on the same box, different ports.
roteague
Posts: 292
Joined: Thu Sep 25, 2008 4:49 pm
Location: Honolulu, Hawaii

Re: v2.4 Order Tracking API

Post by roteague »

muhsmann wrote:Hadi,
Can you please explain the API technology used to handle this now compared to v 2.3 and earlier? It appeared to me that in the earlier versions the sever was a web service and now it looks like its a service we access via remoting or WCF.
Both versions used WCF. Only the method of hosting it changed ... from IIS to a Windows Service.
Robert
Post Reply