This procedure enables the Technical Administrator to create configuration profiles and set runtime configuration settings in them. At a later stage, the Business Administrator assigns these configuration profiles to one or more service definitions.
More information about configuration profiles and configuration scenarios: Configuring Groups of Web Services.
If you want to create a profile version or to activate or deactivate a profile, the profile has to be available.
1. Log on to the SAP NetWeaver Administrator.
2. Choose SOA Management → Technical Configuration → Profile Management.
The Profile Management screen opens.
Alternatively, you can use the quick link /ProfileMgmt as follows:
http://<host>:<port>/nwa/ProfileMgmt.
...
1. Choose New Profile.
2. Enter a name and description of the configuration profile, and then choose Next.
3. On the tabs that open, set the configuration settings which suit your requirements.
○ Configuring Web service Security.
On the Security tab, specify the relevant options. More information: Recommended WS Security Scenarios.
○ Configuring Transport Settings
On the Transport Settings tab you specify the transport between the provider side and the consumer side. The table below lists the available options and explains their meaning.
Option |
Description |
Use ‘‘Connection: KeepAlive” http header |
Enables multiple requests and responses through a single HTTP connection. The provider system keeps the connection alive so that you can use the same connection for multiple request and response cycles. |
Support gzip responses |
Enables the provider side to return compressed responses to the consumer and in this way improves performance. This option is useful when you expect the provider to return responses whose size is several MB.
If you want to set this option, the provider system has to support compressed responses (gzip). |
Max wait-time for http response |
Denotes how long the consumer waits for a response from the provider. If you expect huge load on the provider system that would delay the responses to consumers, Increase the default value. |
Issue chunked requests |
Optimizes the method in which the client communicates to the provider the size of it own requests. If the option is selected, the client communicates the size of the message directly in the stream, and does not write it in memory. |
Alternative Hostname and Alternative Port Number |
The host name and the port to which SOAP messages directed to providers are sent.
By default, SOAP messages are sent directly to the provider system on which the Web service is running. This set-up is operational when you call the Web service from within the local network, for example. However, you have to explicitly configure the alternative location (host and port) for SOAP messages when the Web service you provide is behind a firewall, or a reverse proxy. |
○ Configure stateful communication
On the State Management tab, choose the method for session handling. Currently, only HTTP cookies are supported.
○ Configure Web Service Reliable Messaging
On the Messaging tab, set the relevant options. The table below lists the available options and explains their meaning.
Option |
Description |
RM Protocol |
Sets the protocol for reliable messaging. |
Confirmation Interval |
The interval (in milliseconds) at which the Web service has to send acknowledgements to the Web service client. Currently, the Web service sends acknowledgements to every call from the Web service client. |
ExponentialBackoff |
Exponential backoff sets an algorithm used by the client when it resends messages. If you choose this option, the retransmission interval increases exponentially after each unsuccessful transmission. |
Retransmission interval |
The interval at which the Web service client will try to resend each message which has not been acknowledged by the Web service. |
Inactivity Timeout. |
If the Web service receives no messages within this interval, it considers the sequence terminated due to the lack activity. |
Lifetime of a sequence |
The time for which a sequence will remain active. |
○ Configure Web service addressing
On the Web Service Addressing, specify the protocol for Web service Addressing.
4. Choose Finish
The system creates the configuration profile and records it as version 1. By default, it is with status active. The version number of every subsequent profile version that you create increases by 1.
...
1. From the Profiles table, select a configuration profile.
2. Choose New Version.
3. Enter a description of the new profile version, and then choose Next.
4. On the tabs that open, set the configuration settings which suit your requirements. More information: the procedure Creating a Configuration Profile above.
5. Choose Finish.
By default, every subsequent profile version you create is with status inactive. You can activate more than more than one version of a profile.
From the list of configuration profiles, choose an entry, and then to activate or deactivate a profile choose Activate or Deactivate respectively.
The table below outlines the effect of the possible changes you can make to the status of a profile.
User Action |
System Response |
You set the status of a configuration profile to Active. |
For every service definition in an active configuration scenario to which the activated profile is assigned, the system creates a service endpoint which has the runtime settings of the profile. |
You set the status of a configuration profile to Inactive. |
For every service definition to which the deactivated profile is assigned, the system deletes the service endpoint which has the runtime settings of the profile. |
In the Profiles table, proceed as follows:
● To delete a version of a profile, from the Profiles table, select the version, and then choose Delete Version.
● To delete all the versions of a profile, from the Profiles table, select any version of the profile you want to delete, and the choose Delete Profile.