Documentation Center

Client Tools Stability and Performance

Some Client Tools stability and performance improvements explained.

General

There are various small improvements ranging from small tweaks like what happens if you press cancel when trying to check in an invalid XML file in XMetaL to bigger entries as explained here.

Overall the Client Tools are at the top of the pyramid, they inherit all improvements from the lower levels like the new API calls, redesigned interfaces, optimizations on the federated services, database and operating system improvements.

New logging library

We standardized on NLog logging library. For Client Tools this means that logging configuration moved out of the application's .config file into a dedicated NLog.config file like for example C:\Program Files (x86)\Trisoft\11.1\Publication Manager\Nlog.config.
Allowed log levels are: Trace, Debug, Info, Warn, Error and Fatal. These can be configured in the <rules> element.
<rules>
  <logger name="*" minLevel= "Trace" writeTo="File"/>
</rules>

SOAP compression for slower or high-latency network connections

From now on out-of-the-box the Client Tools will ask the web services to respond with a compressed SOAP response. This effect is mostly visible for metadata retrieval calls (like used when opening a publication in Publication Manager) over slower or high-latency network connections where transferring less data results in a more responsive application. Technically the Client Tools will send a request header Accept-Encoding: gzip, deflate where an out-of-the-box web/app server will return the same uncompressed result as before. To have the web/app server answer with a compressed SOAP response you have to reconfigure your Microsoft IIS. [TS-6894]

If your system administrator did a "Configuring IIS applicationHost.Config", then InstallTool will have configured the remaining steps for you. Otherwise, you can configure your web/app servers as documented in section "Configure IIS to support gzip on SOAP responses".

Proxy server authentication support

Proxy server support verified and extended for the Client Tools and the GeckoFX-based preview. [TS-8001|TS-7956|SRQ-1306]

  • When proxy authentication is required, the user is presented with the login dialog from Architect. The credentials for the proxy are now pushed to the browser control.
  • A user can select Remember password, to avoid getting prompted for the proxy credentials again by the Client Tools across application restarts. If Remember password remains unselected, the value will only be kept for the session. The separate browser control will no longer prompt.
  • Overall the Internet Explorer settings are used (see Internet Properties > Connections > LAN Settings). This behavior can be overwritten by adapting the application's .config file and introducing standard .NET runtime system.net/defaultProxy entries. This could be a full disable; a single proxy specification for the http protocol or a PAC file (Proxy Auto Configuration). All settings will be pushed by the Client Tools into the GeckoFX-based browser control.

Publication Manager showing comments

The retrieval of comments inSDL LiveContent Reach is no longer based on a shared UI but data API driven. [TS-8407|TS-8248]

We tweaked the integration that in case the SDL LiveContent Reach link is not responding that the Client Tools' preview does respond better. Any data retrieval is disabled until a refresh (F5) happens. [TS-8403]

Less, parallel or optimized calls

  • Skipping unnecessary Folder25.RetrieveMetadataByIshFolderRefs for the where used report of Current Publication and Entire Repository. [TS-7630]
  • Parallel execution of DocumentObj25.ContainingLogicalId and PublicationOutput25.Containing for the Where Used reporting.
  • Parallel execution upon Publication Manager initialization. [TS-8040]
  • Optimized group retrieval of 300 items (typically) results in faster loading of the baseline views. [TS-8457]
  • Optimized the creation of warning objects. Viewing the folder content in English when not all objects have English yet is more performant. [TS-8027]
  • Resolving @conrefs (and possibly variables, xrefs, ...) could be slow because the version check happened for every @conref. [TS-7629]