CPO WSDL File location

[jvayda]

I recently had a request about the physical location of the web/appserver that services web requests on a CPO box.

Do you know what the phyical location where the things that service something like http://<CPO Server>/WS/process?wsdl would be located?

[Shaun Roberts]

I would believe it resides and is served up out of the code itself(or DLLs), but Svetlana might be able to answer this fully. Might want to email her directly.

[arayan]

Hi Chris,

Justin and myself  were looking for the access-log for these requests. If you could point us to the standard location of these log files , that would be great.

Thanks

Alex

[Svetlana Kryukova]

That is correct.

There is not "file" or "directory" that contains the WSDL returned by the Web Service.

The WSDLs are generated on demand and served by the Web Service itself.

[Von Jones]

I am not aware of an access log for these specific requests.  These are not the same as your typical web server which would have standard logging.  They go through lower levels of communications directly to the hosting program, in this case the PO server.  It's an API interface to the server.

[arayan]

We are load balancing between 2 servers and would like track which server the request went to via logs.

Currently we are looking into this particluar log..

C:\\Windows\\system32\\config\\systemprofile\\AppData\\Local\\Cisco\\Tidal Enterprise Orchestrator\\Tidal.Automation.Server(B).log"

Is this the only log or any other log available for the API interface.

thanks

Alex

[mischwa2 · Accepted solution]

That is the correct log file. 

However, you can also modify the Tidal.Automation.Server.exe.config file - try using a value of Information instead of error for the following.  You have to stop the service, modify the config file, and then restart the service:

        name="System.ServiceModel"

        switchValue="Error"

        propagateActivity="true">

If that does not work, then you can configure WCF logging per the following link:

http://msdn.microsoft.com/en-us/library/ms730064.aspx

I was able to modify the server.exe.config file in this way to produce logging in the Tidal.Automation.Server(B).log file:

Add a source within existing sources section:

            name="sdt"
            type="Tidal.Automation.Server.WebService.LoggingTraceListener,Tidal.Automation.Server.WebService" />

Add System.ServiceModel section:

         logEntireMessage="true" 
         logMalformedMessages="false"
         logMessagesAtServiceLevel="true" 
         logMessagesAtTransportLevel="false"
         maxMessagesToLog="3000"
         maxSizeOfMessageToLog="2000"/>

Note that when you call something like ListProcessDefinitions after restarting the service you will now see logging for this message:

||109|2013/08/05 11:19:52.183|8932||||WCF: System.ServiceModel.MessageLogging Information: 0 :

||110|2013/08/05 11:19:52.183|8932||||WCF: http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace

">POST"

http://tempuri.org/IProcessNorthbound/ListProcessDefinitions"Keep-

||109|2013/08/05 11:19:52.183|8932||||WCF: System.ServiceModel.MessageLogging Information: 0 :

||110|2013/08/05 11:19:52.183|8932||||WCF: http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace">POST"...."Keephttp://tempuri.org/IProcessNorthbound/ListProcessDefinitions