Changing the Service Definition Configuration

Procedure

In the Configuration tab, you will find the features that were assigned at interface, security, and operation level using the service wizard profiles. Make the changes you require. No changes can be made to service interfaces.

Interface Profile

In the interface profile, choose the required processing type: Stateful or Stateless.

A stateful service retains its status within the framework of a HTTP session throughout several calls from the same service consumer. The default value for services is stateless. If you require stateful communication, you can choose this instead.

If you choose the name of the configuration, the ICF (Internet Communication Framework) service node of the SOAP runtime is displayed on the right-hand side in the Path Prefix field.

The message identifier has the standard value True. Using the IF_WSPROTOCOL_MESSAGE_ID protocol, you can query the sent message.

For more information, refer to the section Protocols.

Security Profile

In the security profile, choose the type of authentication for calling the Web service through a service consumer. You define how transport security (making sure the data transfer is secure) between the consumer and the provider is to take place (refer also to Making a Web Service Secure).

Operation Profile

The operation profile has the default value Synchronous. If you choose the status stateful in the interface profile, you can choose also Synchronous Commit and Synchronous Rollback for all operations except Synchronous.

The assignments of the following (non-changeable) properties of operations can be displayed.

Property:	Meaning:
Blocking	Calling a proxy (more precisely, transmitting a message to the message infrastructure) causes the caller to be blocked until the business reply has been received and returned to the caller.
Commit Handling	Commit/Rollback Control Through the Framework The Framework is responsible for closing transactions (commit or rollback). The application signalizes only whether a COMMIT or ROLLBACK is to be executed.
Transaction Handling	Description of the Transactional Behavior of the Message Infrastructure Transactional processing means that the messages that are passed to the messaging infrastructure are collected up until the end of the transaction (LUW). Depending on the type of transaction completion (commit/rollback), the messages are discarded or stored for subsequent processing. The transactional connection is not passed to the server side.
Reliable Message Exchange	With Web Services Reliable Messaging, the following is possible: The sender of a message can determine whether a message was received by the desired receiver and can then trigger appropriate measures if this is not the case. The receiver of the message can be sure that he or she receives the message, despite unforeseen problems with networks or the software.
RT Intrinsic Features	Type of Message Exchange One Way Data is transferred from the sender to the receiver without a reply being expected from the application. RequestResponse The message exchange consists of a query and a reply at application level. For more information, refer to the section Types of Message Transmission.