Integration Directory

Use

Feature	Type of Change	Description
Integration Directory programming interface	Changed	The Integration Directory programming interface supports the following additional configuration object types: Integrated configuration Receiver rule More information: Integration Directory Programming Interface
Model-based configuration of integration content	Changed	Model-based configuration of integration content ( “model configurator” ) in Integration Directory supports also scenarios using the Advanced Adapter Engine Extended and local message exchange using the Advanced Adapter Engine. The scope of generation covers integrated configurations as additional object type. This option is only supported in case you use process integration scenarios as configuration templates. More information: Configuring Process Integration Scenarios
Model-based configuration of process component interaction models	Changed	Model-based configuration of integration content ( “model configurator” ) in Integration Directory supports process component interaction models as additional model type. More information: Configuring Process Component Interaction Models
Cache Refresh	New	When the cache is refreshed, the configuration data maintained in Integration Directory is synchronized with the configuration data maintained by the runtime components. Parameters are available to control the following settings for cache refresh: Create statistics files Location of statistics files Location of the temporary files More information: List of Profile Parameters
Configuration of Principal Propagation	New	You can configure principal propagation based on Security Assertion Markup Language (SAML 1.1). Principal propagation based on the SAML 1.1 standard is supported for applications that use Web service runtime (WS RM). More information: Configuring Principal Propagation
Connectivity with Web service providers and consumers	New	In the Integration Directory you can configure systems that communicate using the Web service runtime based on standard Web Service Reliable Messaging (WS RM). The communication channel type (adapter type WS) is available for implementing the settings required. With the new communication channel you can configure not only enhanced communication between WS RM-capable systems using the Integration Server, but also direct communication between WS RM-capable systems. More information: Configuring the Communication Channel with Adapter Type WS
Connectivity with Web service providers and consumers	Changed	The adapter type WS has the following new features: Optimized XML transfer is supported. Transport binding SOAP1.2 Using HTTP is supported. Extended signature and header protection is now available also for asymmetric message signature/encryption. Authentication at message level based on the Security Assertion Markup Language (SAML 1.1) standard is supported. More information: Configuring the Communication Channel with Adapter Type WS
Configuring direct connections	New	To implement direct communication between WS RM -capable systems in the Integration Directory, direct connection is available as a new object type. More information: Define Direct Connection
Publishing sender agreements into the Services Registry	New	You can publish the WSDL description for a sender agreement from the Integration Directory to the Services Registry and thus make it readily available to a business partner. More information: Publishing Sender Agreements in the Services Registry
Operation-dependent receiver determination	Changed	It is now possible to configure a receiver determination that depends on the operation of the assigned service interface.
Integration Directory Programming Interface	New	In addition to the existing user interface (Integration Builder), a new programming interface is now available that you can use for accessing Integration Directory objects. The programming interface is based on the fundamental configuration options that are possible in the Integration Directory. This means that you use the interface to create, edit, and activate all configuration objects. Since you can now use a program to access the content of the Integration Directory, scenarios that were previously not possible with the existing user interface, or that required a lot of effort to realize manually are now possible (for example, mass changes to configuration objects). More information: Integration Directory Programming Interface
Simplified configuration of simple scenarios (integrated configuration)	New	Using Integrated Configuration you can specify the complete configuration settings for the clear exchange of a message in one single object. This object replaces the “classic” configuration objects (sender agreement, receiver determination, interface determination, and receiver agreements). You can only use Integrated Configuration to set up communication scenarios where the message is only to be transferred within an Advanced Adapter Engine from a sender to a receiver adapter. More information: Defining the Integrated Configuration
Creating folders	New	You can create a folder to structure Integration Directory content more clearly. Folders can be shown or hidden in the navigation area of the Integration Builder.
Display cache status for each object	New	In cache notifications you can now display the cache status for each individual object. More information: Analyzing Cache Notifications
User Interface	Changed	The following changes have been made to the Integration Directory user interface (Integration Builder): Creating folders You can create a folder to structure Integration Directory content more clearly. Folders can be shown or hidden in the navigation area of the Integration Builder. Display unassigned objects An unassigned object can occur when the folder to which the object was originally assigned has been deleted but the object itself has not. These objects are displayed in a separate folder. Display cache status for each object In cache notifications you can now display the cache status for each individual object. Further usability improvements The usability of the navigation area of the Integration Directory was improved. You can now choose between three views. An object view shows the configuration objects grouped according to the object type. A scenario view groups the Integration Directory content according to configuration scenarios, and a folder view groups all content according to folders.
Enhanced search capabilities for communication channels	Changed	The search function in the Integration Directory was improved in particular for communication channels. You can now search communication channels with adapter type specific attribute values. For example, you can now search channels with adapter type File/FTP who have configured a specific file name.
Collaboration Agreement	Changed	You can make settings to propagate principals from a sender to a receiver. To do this, you make the required settings in the collaboration agreement: In the sender agreement, you define that principals are to be propagated from the sender to the Integration Server. In the receiver agreement, you define that principals are to be propagated from the Integration Server to the receiver. This function is available for adapter types XI, RFC, and SOAP.
Collaboration Agreement	Changed	When using the SOAP adapter, you can specify the following additional settings for the security procedure in the collaboration agreement: Sender SOAP adapter: Decrypt and Decrypt and Validate Receiver SOAP adapter: Encrypt and Sign and Encrypt More information: Security Settings for the Sender SOAP Adapter , Security Settings for the Receiver SOAP Adapter