Related to Max size of Content Porter Import and how can we increase it, I understand Content Porter uses the Core Service to export and import items between machines.
Is there any difference when running Content Porter on a local machine (i.e. laptop) versus on a DTAP (Dev, Test, Acceptance, or Production) server in terms of time outs?
Or in other words, can Content Porter use different Core Service endpoints based on where it runs? Based on below maybe we can configure a single endpoint for Content Porter?
The documentation describes a channel setting in the configuration:
Note that if you change this port number, you must also change the same value in the file web.config located in
%TRIDION_HOME%\Content Porter\web\ImportExportService\. In that file, the port number is part of the URL in a url attribute in the following XML fragment:
<client> <wellknown type="comma-separated strings" url="http://localhost:50500/ProcessManager" /> </client>
The config "...also contains the Core Service client configuration for communication with the Content Manager. To configure the client, refer to the SDL Tridion platform documentation for more information."
Also when importing, does the size of the export package matter in terms of
maxAllowedContentLength (IIS) and/or
Based on Raj's answer and Bart's comment my misunderstanding was on the impact of the timeout settings. The package import, handled by .NET and IIS (and the above time out settings) is separate from the Core Service import/upload. See examples of the Core Service timeout settings in this separate answer.