Profiles showing in running config

[Hawk]

What is the significance of the profiles mounted in the running config?  Are they merely just so that they can be downloaded from flash & uploaded in to the anyconnect client app?  Is ASDM the only or best way to create client profiles?

webvpn
enable outside
anyconnect image disk0:/anyconnect-win-3.1.05152-k9.pkg 1
anyconnect image disk0:/anyconnect-linux-64-4.3.05017-k9.pkg 2
anyconnect image disk0:/anyconnect-macosx-i386-4.3.05017-k9.pkg 3
anyconnect profiles vendor-contractor disk0:/vendor-contractor.xml
anyconnect profiles localauth-users disk0:/localauth-users.xml
anyconnect profiles users-splittunnel disk0:/users-splittunnel.xml
anyconnect profiles 2factor-users disk0:/2factor-users.xml
anyconnect enable
tunnel-group-list enable
keepout "Service out temporarily."
cache
disable
error-recovery disable

[Rahul Govindan]

The configuration is to create a reference to the actual Anyconnect profile location. This reference can then be called under the group-policy so that you can download different profile for different group-policies. ASDM is the best way to create profiles since it automatically saves the created profile in flash.  You can also use the standalone Anyconnect profile editor application to create it outside of the ASA. You would then have to upload the profile and assign to the group-policy manually.