Making a Web Service App be able to connect to any LL/CS server

Hello again,

I'm working through a lot of the sample code and one thing has sort of stood out: When you create the project, you are creating references to your local sandbox CS instance. Where would you specify a different CS instance? For example, I build an app for a client where my service references point to http://localhost... but in the field you will be connecting to https://myclientsinstance/? Where does one specify the new server address?

Thanks

-hugh

Find more posts tagged with

Comments

Jason_Smith

I assume you are talking about the C# samples using Visual Studio. If you want to change the endpoint you are connecting to you can change it in the app.config file (this file is created when first adding your service reference defaulting to the endpoint you used when creating it).

You can also change the endpoint in your code. The LLTreeView sample does this since it asks for the endpoint on startup.

Kyle_Swidrovich

Hi Hugh,

What environment are you working in?

If it’s .NET, the app.config file is the result of your project references.

There is a way to write .NET apps such that they use dynamic references, but it gets really ugly.

Kyle

Hugh_Ferguson

I did look at the tree-view example (BTW, for LL971 and visual studio 2010, you need to recompile with .NET 3.0). On my dev sandbox, I'm forced to use Apache since I'm trying to connect from a Win 7 client to my sandbox instance (I have to keep both client dev environment and LL Server on same instance as running two VMs overheats my CPU).

Using the tree view example, I am trying to get it to use a Tomcat URL but that doesn't seem to work. If I didn't know better, you are still dependent on the service endpoints defined in app.config (which may not be available in a finished application). Am I correct in assuming that when dynamically setting your endpoints, that you are restricted to having your client connect to whatever type of endpoint (IIS or Tomcat) that was defined in the app.config? I did try editing the example to set the Service end-points to the tomcat convention.

-Hugh

Jason_Smith

From a client perspective it doesn't matter what application server is being used on the server side. So no, you are not restricted there. Send over a code snippet of what you tried and we should be able to figure out how to fix it.

Hugh_Ferguson

My client app connects fine, it's the LLTreeView sample that doesn't work. I want to be sure that I can connect my app to any LL instance. Here is what I changed in the Tree View app:

fAuthService = new AuthenticationClient();

System.Diagnostics.Debug.WriteLine("Connecting to service root {0}", serviceRoot);

if (serviceRoot.Contains(":8080"))

{

// assume tomcat

System.Diagnostics.Debug.WriteLine("Tomcat host assumed");

fAuthService.Endpoint.Address = new EndpointAddress( serviceRoot + "Authentication?wsdl" );

isTomcat = true;

}

else

{

fAuthService.Endpoint.Address = new EndpointAddress( serviceRoot + "Authentication.svc" );

}

Similarly, I did the following with the initialization of the various clients:

private void InitServices( string serviceRoot, string token )

{

string serviceEnding = ".svc";

fDocManService = new DocumentManagementClient();

fMemberService = new MemberServiceClient();

fWorkflowService = new WorkflowServiceClient();

fCollaborationService = new Collaboration.CollaborationClient();

if (isTomcat)

serviceEnding = "?wsdl";

fDocManService.Endpoint.Address = new EndpointAddress( serviceRoot + "DocumentManagement" + serviceEnding );

fMemberService.Endpoint.Address = new EndpointAddress(serviceRoot + "MemberService" + serviceEnding);

fWorkflowService.Endpoint.Address = new EndpointAddress(serviceRoot + "WorkflowService" + serviceEnding);

fCollaborationService.Endpoint.Address = new EndpointAddress(serviceRoot + "Collaboration" + serviceEnding);

From there on, it's the same as the stocked example.

-Hugh

Jason_Smith

I think the value of serviceRoot in your code snippet would clear things up. With Tomcat there is an extra 'services' directory in the URL before the name of the service.

The default endpoint for CWS hosted in IIS would look like this:

http://localhost/les-services/Authentication.svc

The default endpoint for CWS hosted in Tomcat would look like this:

http://localhost:8080/les-services/services/Authentication?wsdl

Hugh_Ferguson

Actually, that turned out to be it. I discovered it the other day but didn't have a chance to post a follow-up. Thanks for the confirmation.

-Hugh