The "SM HTTPS URL Base Map" server parameter can be set in cases where the network name of the IC Server is not able to be resolved via DNS. This server parameter is a &-delimited list of |-delimited mappings. The format to follow is "machine name1|resolvable value1&machine name2|resolvable value2". An example value could be "server1|server1.domainname.com&server2|server2.domainname.com".

Note
When configuration-based files are uploaded via the HTTPS mechanism, they are first copied to the logged in user's personal storage on the IC Server. After a successful upload, the IC Server then moves the uploaded file to the appropriate location, as dictated by each object's server parameter path, which are listed with each object type below.

The ClientTemplateConfiguration..::..Commit()()()() method uses the HTTPS upload file transfer mechanism, and the ClientTemplateConfiguration..::..DownloadResource()()()() method uses the HTTPS download file transfer mechanism. The "ClientTemplateXmlPath" server parameter determines the location of client templates on the IC Server. If this server parameter is not set, then the "Resource Path" server parameter is used, and the client template file is stored in the "Resources\ClientTemplates" subfolder of the "Resource Path" path. If the "Resource Path" server parameter is not set, then the "Server Path" server parameter is used, and the client template file is stored in the "Resources\ClientTemplates" subfolder.

The ImageResourceConfiguration..::..Commit()()()() method uses the HTTPS upload file transfer mechanism, and the ImageResourceConfiguration..::..DownloadResource()()()() method uses the HTTPS download file transfer mechanism. The "ImageResourcePath" server parameter determines the location of image resources on the IC Server. If this server parameter is not set, then the "Resource Path" server parameter is used. If the "Resource Path" server parameter is not set, then the "Server Path" server parameter is used, and the image resource file is then stored in a "Resources" subfolder.

The HTTPS upload file transfer mechanism is used when calling the Commit()()()() method on a ResponseManagementDocumentConfiguration object. The ResponseManagementDocumentConfiguration..::..DownloadDocument()()()() method uses the HTTPS download file transfer mechanism. The "Rx Document Path" server parameter determines the location of response management documents on the IC Server. If this server parameter is not set, then the response management document is saved to the "Server\I3RxDocs" folder.

The CustomProfile class, when constructed via a call to CustomProfile..::..GetApplicationCustomProfile(Session), uses the HTTPS file transfer mechanism. The CustomProfile..::..CheckForApplicationBasedSettings()()()(), CustomProfile..::..GetProfileItem(String, String), and CustomProfile..::..GetNamespaceContents(String) methods use the HTTPS download file transfer mechanism. The CustomProfile..::..FlushChanges()()()() method uses the HTTPS upload file transfer mechanism. The application-based custom profile files are uploaded and downloaded directly to and from the "ApplicationSettings" folder located in the logged in user's personal storage.

The ProblemReporter..::..Submit()()()() method uses the HTTPS upload file transfer mechanism. The "ProblemReporterPath" server parameter determines the location of problem reporter files on the IC Server. If this server parameter is not set, then the "Server Path" server parameter is used, and the problem report is saved in the "ProblemReporter" subfolder.

The EmailInteraction..::..UploadFileAttachment(Stream, String, String) and EmailInteraction..::..UploadFileAttachment(String, String) methods use the HTTPS upload file transfer mechanism. Email attachments are uploaded directly to the "Email" folder under the logged in user's personal storage.

The StatusMessageDetails..::..Icon property uses the HTTPS download file transfer mechanism. Accessing the StatusMessageDetails..::..Icon property causes IceLib to attempt to read the current Icon from its local file cache. If it does not exist in the local file cache, IceLib will immediately return with a default icon, and will schedule a download of the updated icon. When the scheduled icon download completes, the StatusMessageList..::..WatchedObjectsChanged event is fired, with the StatusMessageProperty..::..Icon enumeration value indicated as part of the WatchedObjectsEventArgs<(Of <(<'TPropertyEnum>)>)>..::..Changed property. The location of icon files are set via Interaction Administrator, in the "Status Messages" section.

The TransactionClient..::..Execute(TransactionData%) method uses the HTTPS download file transfer mechanism. When TransactionData..::..ForceOutOfBand is set to true for the transaction being executed, and the IC Server has determined that Out of Band transfer requests are supported for the specified transaction, the TransactionData..::..WasOutOfBandUsed property will be set to true, indicating that the HTTPS transfer mechanism was used. There are no server parameters that affect the location of transaction data results; however, the "Out-of-band ThreadingPool Size" server parameter controls the number of simultaneous transactions that can run (default value is 4), and the "Out-of-band Resultset Expire Timeout" server parameter controls how long, in seconds, until an old result set is determined to be old and thus purged (default is 12 hours).