Object Key in Configuration Objects 

 

The object key enables you to identify a configuration object uniquely. Unlike in design objects, the structure of the object key in configuration objects is dependent on the object type.

The object key is assigned during creation and cannot be changed thereafter.

 

Collaboration Profile Objects

The objects of the collaboration profile define possible senders and receivers of messages and their (technical) communication options. SAP Exchange Infrastructure supports the addressing of senders/receivers (depending on the application case) in two ways:

·        As a party with assigned services

·        As services without a party

A communication channel defines the technical details of the inbound or outbound processing of a message for a sender or receiver. Therefore, depending on the chosen addressing type, you can define a communication channel for a party/service pair or for a service without a party.

This results in the following object keys:

Key Fields in Collaboration Profile Objects

(The fields marked with an X are key fields.)

Key Field	Party	Service	Communication Channel
Party (name)	X
Service (name)	X	X
Communication Channel (name)	X	X	X

Objects of the Logical Routing and the Collaboration Agreement

The objects of the logical routing (receiver determination and interface determination) and the collaboration agreement define rules for the routing and processing of messages for a particular combination of sender, receiver, and interface. These objects do not have their own names. The object key comprises the sender, receiver, and interface, and defines the range in which the configuration data contained in these objects is valid.

Since these objects do not have a name, the object key of each object is displayed in the navigation area of the Integration Directory instead. If there is a large number of objects to be displayed, you have the option of grouping the objects according to selected parts of the key.

 

You can define the objects of the logical routing and collaboration agreement generically for particular key attributes by masking the key fields. This enables you to specify a very general definition range for these objects.

The following table shows the parts of the object key for which you can define the objects of the logical routing and collaboration agreement generically.

Maskable Key Fields in Objects of the Logical Routing and Collaboration Agreement

(The fields marked with an * are maskable key fields.)

Key Field	Receiver Determination	Interface Determination	Receiver Agreement	Sender Agreement
Sender Party	*	*	*
Sender Service	*	*	*
Receiver Party	*	*		*
Receiver Service	*	*		*
Interface			*	*

Interface means the name and namespace of the interface in each case. Note that this refers to the interface at the sender, except in the receiver agreement.  In the receiver agreement, it refers to the receiver interface.

The object key is assigned during creation of the object, after which it can no longer be changed.

Note the special restrictions for the key fields of sender agreements that are assigned a sender JMS, sender JDBC, or sender File/FTP adapter.