A profile is general configuration of security and transport aspects. For web service communications, the provider and the consumer have to use the same profile so that the calling system uses the exact authentication, encryption, and other settings that are offered by the provider system. A profile is created once, distributed to all relevant servers in a landscape, and then used for the configuration of each web service on the provider and consumer side.
If you are using SAP Basis release 700, it is not possible to use Mass Configuration for the services of that system. In such case, you need to manually create logical ports.
In the SAP CRM system go to transaction SOAMANAGER, choose .
Enter a profile name in the Profile Name field under the Profile Properties section.
Check for the settings for reliable messaging, transport binding and authentication that fulfill the needs of your company and landscape. The selected authentication method must support single sign-on. This may also require trust to be configured between the GSDO and the SAP systems.
Save and activate the profile.
Select the new profile you have created, and choose Export to export it to a file.
If you do not have the option to export the files, you need to create logical ports manually on the consumer system.
Log on to all relevant systems in the landscape, go to transaction SOAMANAGER, and import the profile.
If you want to change a profile, you must create a new version of it. By activating a new version, the provider system and all other pieces of configuration that use the profile still use an old version. You must go to the configuration of each provider system and configure it to use the new version of the profile. You must also reactivate all dependent objects as required. This has to be done in all systems in the landscape after the distribution of the new profile version.