Multi-Mappings in SAP XI

Use

A multi-mapping is a mapping program that is not restricted to the transformation of one source message to one target message. You have the following options:

• You can use a multi-mapping in a transformation step in a integration process. In this case, the mapping runtime supports 1:n-, n:1, and n:m transformations. You can map any number of source messages to any number of target messages.
• You can use a multi-mapping to map a message to multiple different (and generally smaller) messages during logical routing. Only a 1:n transformation is possible in this case.

Integration

As is the case for all mapping programs, to be able to configure the mapping programs for source and target interfaces, you need to assign a multi-mapping program to an interface mapping that you will use later in the Integration Directory.

Processing Multi-Mappings at Runtime

Multi-mappings reference multiple message structures. To map these structures to one another, the mapping runtime gathers all the source messages of one multi-mapping in one source structure and all the target messages of one multi-mapping in one target structure. This means that instead of trying to map multiple messages to each other, you only have a source structure being mapped to a target structure.

Example

You can generally implement a multi-mapping with all types of mapping program. For simplicity, the following section assumes that you want to implement a multi-mapping as a message mapping.

Imagine the following are message types that you want to map to each other:

Message Types for the Source Structure

Message Type (Source Structure)	Message Type (Target Structure)
OrderHeader (1)	Order (1)
OrderItem (0..unbounded)	OrderInfo (1)

You can specify these message types on the Messages tab page in the mapping editor. You can also specify an occurrence rate for each message type. If the source or target structure can comprise multiple messages, the mapping editor creates a sub-structure for both the source and the target structure in which the source and target messages are stored. The root element is always in a case like this. The mapping editor inserts an element N> for each source or target message, where N is the position of the message according to the Messages tab page. A message instance for the message specified above looks as follows:

There is a N> element for each message schema (for each message type here). The message type can occur unbounded in the message instance as a sub-element of . The numbers specify which elements in the multi-mapping are mapped to each other.

At runtime, the message instances are collected in an integration process and then put in a structure. Once the mapping program has been executed, they are transferred to various message instances again.

Features

If you specify multiple source or target messages in the mapping editor, the mapping editor immediately displays the source or target structure described above in the structure overview. The mapping editor supports the following message schemata for multi-mappings:

· (Fault) message types

· IDocs, RFCs (request-, response, or fault messages), see Importing IDocs and RFCs

· Message structures from external definitions

You can also develop multi-mappings as external mapping programs by exporting the message schema of the request message from an interface mapping.

See also:

Developing Multi-Mappings for Integration Processes

Developing Multi-Mappings for Message Splits

Developing Multi-Mappings for Integration Processes in SAP XI

Purpose

This section describes how to develop a multi-mapping for a transformation step in an integration process. In this case, the mapping runtime supports 1:n, n:1, and n:m transformations.

Prerequisites

The procedure described below requires that the message schemas for the messages to be mapped already exist in the Integration Repository (see also Features in Multi-Mappings) and that they are assigned to asynchronous, abstract message interfaces. You can only use this interface type in integration processes.

Furthermore, all objects (integration process, interface mapping, and all objects referenced by the interface mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help) (see also: Underlying Software Component Versions).

Process Flow

Developing Multi-Mappings as Message Mappings

...

...

1. Create a message mapping.

2. In the mapping editor, switch to the Messages tab page.

3. Reference a (fault) message type, an IDoc, the request, response, or fault part of an RFC or an external message (External Messages originate from external definitions).

4. Specify the occurrence for each message.

5. Switch to the Design tab page and edit your message mapping as usual. The rules that apply to message mappings also apply here.

6. Create an interface mapping and reference the asynchronous abstract message interfaces that use these message schemas. Enter your message mapping in the interface mapping.

Developing Multi-Mappings Externally

Message mappings are not the only means of implementing multi-mappings. Develop the mapping program using the same approach that is described in Multi-Mappings:

...

1. Create an interface mapping and reference the asynchronous abstract message interfaces that reference the message schemas that are relevant for the multi-mapping.

2. Export the schema of the request message from the interface mapping.

3. Develop the multi-mapping by using the exported schema. The resulting target structure must be structured as is described in Multi-Mappings.

4. If the mapping is an XSLT or Java mapping (see: Imported Archive (XSLT/Java)), import the mapping program to the Integration Repository and reference it from the interface mapping.

Result

You have developed a multi-mapping program and included it in an interface mapping. You can now enter the interface mapping in a transformation step in an integration process.

Developing Multi-Mappings for Message Splits in SAP XI

Purpose

This section describes how to develop a multi-mapping for a message split (1:n transformation). You can specify the multi-mapping program by means of an interface mapping in logical routing. In this case, the interface mapping not only determines the mapping program, but also determines which target interface the target message is to be sent to in logical routing. Hence the term mapping-based message split.

Prerequisites

Multi-mappings require the interfaces involved to be asynchronous. There are no other restrictions on the outbound interface of the interface mapping.

Messages that result from the split in a mapping-based message split are sent using one Adapter Engine. For this reason, only those adapters that run on the Adapter Engine are supported. The Java proxy runtime is also not supported. This means that the selection of possible target interfaces is restricted to the corresponding adapter types. In particular, no target messages can be sent to an integration process.

See also: Enhanced (Mapping-Based) Interface Determination

The procedure described below requires that the message schemas for the messages to be mapped to each other already exist in the Integration Repository (see also Features in Multi-Mappings).

The following restriction applies for the source and target messages that you reference from a message mapping: the source and target messages can be in a different software component version to the message mapping, but must each originate from one software component version (and, if applicable, underlying software component versions).

A multi-mapping that has a message mapping in software component version CRM 3.0, all source messages in software component version APO 2.0, and all target messages in software component version CRM 2.0, complies with the precondition above.

This restriction also applies for the export function of interface mappings, which you use for developing multi-mappings externally, described below.

Process Flow

Developing Multi-Mappings as Message Mappings

...

Create a message mapping.

1. In the mapping editor, switch to the Messages tab page.

Reference a (fault) message type, an IDoc, the request, response, or fault part of an RFC or an external message (external messages originate from external definitions).

2. Specify the occurrence for each message.

3. Switch to the Design tab page and edit your message mapping as usual. The rules that apply to message mappings also apply here.

Create an interface mapping and reference the interfaces that use these message schemas. Enter your message mapping in the interface mapping.

Developing Multi-Mappings Externally

Message mappings are not the only means of implementing multi-mappings. Develop the mapping program using the same approach that is described in Multi-Mappings:

...

Create an interface mapping and reference the interfaces that reference the message schemas that are relevant for the multi-mapping. Only target interfaces of those adapter types that run on the Adapter Engine (excluding the Java proxy runtime) are supported.

1. Export the schema of the request message from the interface mapping.

2. Develop the multi-mapping by using the exported schema. The resulting target structure must be structured as is described in multi-mappings.

If the mapping is an XSLT or Java mapping (see: Imported Archive (XSLT/Java)), import the mapping program to the Integration Repository and reference it from the interface mapping.

Result

You have developed a multi-mapping program and included it in an interface mapping. You can now enter the interface mapping in an interface determination in order to configure a message split (see also: Enhanced (Mapping-Based) Interface Determination).

Mapping Development with the ABAP Workbench in SAP

Purpose

SAP XI customers can also develop mapping programs by using the ABAP Workbench. At runtime, these programs are executed on the ABAP Engine of the SAP Web AS on which the Integration Server is running.

At present there is no mechanism for shipping mapping programs of the ABAP Engine with SAP applications and importing them on the Integration Server. Therefore, only customers that can create such mapping programs directly on the SAP Web AS of the Integration Server or can transport them there can use ABAP Engine mappings. Unlike XSLT and Java mappings, which run on the J2EE Engine, mapping programs of the ABAP Engine cannot be imported to the Integration Repository. Therefore, there are no mappings shipped by SAP that run on the ABAP Engine.

You can implement the following mapping programs by using the ABAP Workbench:

● ABAP mappings in ABAP objects

● XSLT Mappings (ABAP Engine)

Integration

You must register mapping programs in the Integration Repository by using interface mappings. To do this, select a mapping type from the list box on the design maintenance screen of the Integration Builder. There are no entries for ABAP Workbench objects in the default settings.

To reference the corresponding development objects of the ABAP Workbench from interface mappings, customers must assign the following value to the parameter com.sap.aii.repository.mapping.additionaltypes in the exchange profile:

com.sap.aii.repository.mapping.additionaltypes=R3_ABAP|Abap-class;R3_XSLT|XSL (ABAP Engine)

For a description of how to access the exchange profile, see the Exchange Infrastructure Profile Parameters section in the Configuration Guide (see SAP Service Marketplace at service.sap.com/instguides).

Restrictions

Access to the value mapping table is not supported for mapping programs developed using the ABAP Workbench.

Transport and Versioning

ABAP mappings and XSLT mappings (ABAP Engine) are development objects of the ABAP Workbench on the SAP Web Application Server. This has the following consequences:

● You develop these development objects in the Object Navigator (transaction SE80) and transport them using ABAP transports. They must be available on the Integration Server at runtime. XI does not support these transports.

● ABAP mappings and XSLT mappings (ABAP Engine) can only exist in one active version on the Integration Server. In contrast, the Java, XSLT, and message mappings that are executed on the J2EE Engine can be used in multiple versions in parallel.

Message Mappings in SAP XI

Use

A message mapping refers to a mapping of messages and is supported by a graphical mapping editor. The editor enables you to design a structure mapping between any two XML structures and connect to a value mapping.

The mapping tool generates Java source code from the graphical mapping description, which is then compiled and packed in a JAR file that the Integration Engine executes at runtime.

Features

The mapping editor can load the following schemas into the structure overview:

· A schema from the Integration Repository: (Fault) message types, IDocs, the request, response, or fault part of RFCs, and message structures from external definitions. The latter are message structures from WSDL, XSD, or DTD documents.

· XML schema definitions (XSD) or XML files from a local file

In the case of XSD files (the repository schemas also use this format), the mapping editor generates an XML representation for both the source structure and the target structure. If the XSD file contains more than one global element, use a dialog box to select a global element as the root element.

If you want to load several XSD files that reference each other using the import and include XSD statements, you must first pack the files into a Zip file. If the file contains multiple global elements, you must select one global element as the root element in this case as well.

Main Function Area of the Mapping Editor

Once you have created a message mapping, the system navigates to the mapping editor Design tab page. The figure below illustrates the screen areas of the mapping editor (the tab page was detached from the Integration Builder beforehand):

You have the following options when defining a message mapping:

· The functions in the Object Toolbar relate to the entire mapping. For example, you can save your mapping or automatically assign fields with the same name to each other.

· When you create a new message mapping the Structure Overview in the mapping editor is initially empty. Here you must specify a repository schema for both the source structure and the target structure or import an XML or XSD file. The mapping editor imports the data and displays an XML representation for the mapping in the Structure Overview: In this screen area, the source structure is on the left and the target structure is on the right. Source structure fields then have to be mapped to target structure fields. You have various options for displaying the source and target structure (Tree View, Tree and Table View, display as a text document, or display in the browser) that you can select from.

· The structure overview is closely linked to the Data-Flow Editor, which you use to describe the mapping of one or more source fields to one target field. This type of mapping is also referred to as a Target-Field Mapping. If a field in the target structure has already been mapped, you can navigate to the respective mapping by double-clicking the corresponding target field in the structure overview.

Therefore, a message mapping comprises various target-field mappings. Once you have defined a mapping for each mandatory target field your message mapping is complete. To test your message mapping, navigate to the Test tab page (see: Test Environment).

Functions of the Object Toolbar

Function	Use
Select Messages	Loads schemas for source and target messages into the structure overview.
Map Selected Fields and Substructures if Names Are Identical	Before you execute this function, first select one node in both the source and target structures that belong to each other. You can then automatically assign subnodes that have identical names (names are case-sensitive here). This function is particularly useful for simple mappings, for example from RFC XML to proxy XML.
Clear Mapping	Deletes all target field mappings.
Data-Flow Editor	Use this button to switch between the data-flow editor, text preview, and mapping templates used, in the lower area of the data-flow editor: · In the data-flow editor, you edit target-field mappings. · You use the text preview to display all target-field mappings and the functions that they use as text. Lines in red indicate missing target-field mappings. The quick info for a green target field displays the corresponding mapping. · A message mapping can reuse mapping templates (for data type mappings). Using Mapping Templates Used you can display all the mapping templates used so far in the lower area of the mapping editor. Note that the target-field mappings of the mapping templates used may differ from those in the current message mapping.
Text Preview
Mapping Templates Used
Dependencies (Show, Show All, Hide All)	Use this function to graphically display which source fields are assigned to which target fields in the structure overview (for a selected node pair, or for all). The colors have the following meanings: · Red: The source field is directly assigned to the target field. · Green: A subnode of the source field is assigned to the target field. · Blue: The source field is assigned to a subnode of the target field. · Black: A subnode of the source field is assigned to a subnode of the target field.
Show Suitable Templates	Use this function to load a saved mapping template for an element pair as a copy.
Create Template Based on Mapping	Use this function to create a mapping template for an element pair that references a data type or a message structure. You must select the respective elements.
Dependencies (Show, Show All, Hide All)	Use this function to graphically display which source fields are assigned to which target fields in the structure overview (for a selected node pair, or for all). The colors have the following meanings: · Red: The source field is directly assigned to the target field. · Green: A subnode of the source field is assigned to the target field. · Blue: The source field is assigned to a subnode of the target field. · Black: A subnode of the source field is assigned to a subnode of the target field.
Edit Java Sections	Use this function to specify global variables and additional Java sections for all Java functions. First the mapping runtime includes the Java packages specified under Imports. You can enter the same packages entered for a user-defined function. Then the mapping runtime declares the variables entered as global variables and executes the sections in the following order: ... 1. Initialization section 2. Message mapping 3. Cleanup section

Functions in the Message Mapping Object Menu

Function	Use
Refresh	If you loaded a repository schema into the mapping editor that has since been changed in the Integration Repository, the changes are not visible in the mapping editor. To apply changes of this type to the source and target structures, choose Refresh.
Delete	This function deletes the message mapping object.

Additional Functions

Within the structure overview and in the data-flow editor you can call functions in the context menu. For all fields (in the data-flow editor and in the structure overview on both the Design and Test tab pages) you can copy the path for a field to the clipboard by choosing the context menu option Copy Path.

Activities

To define a mapping between two XML structures, proceed as follows:

...

1. Create a message mapping on the design maintenance screen of the Integration Builder (see: Creating a New Object).

2. Load a source and target structure in the mapping editor by either using the search help, or by using drag and drop to drag a name from the navigation tree and drop it on the corresponding hand.

For messages from external definitions, note that the mapping editor does not support the entire language range of XSD. For more information, see SAP Service Marketplace at service.sap.com/xi ® Media Library ® Documentation: SAP XI 3.0 (SP11) – Supported XML Schema and WSDL (EN).

3. Using the structure overview and the data-flow editor, assign one or more source fields to a target field. This type of mapping is also called a Target-Field Mapping. It is also possible to assign one source field to multiple target fields (see: Assigning a Field).

4. If necessary, enhance the target field mapping in the data-flow editor. To do so, connect the source fields to the target field by using the standard functions of the mapping editor. You can also create user-defined functions in Java in the mapping tool and then use them in the data-flow editor (see also: Data-Flow Editor).

5. Carry out the last two steps for all mandatory target fields at least.

Result

The mapping is complete and ready for testing when all the fields in the target structure have either green or white icons. A yellow icon indicates that a target-field mapping is incomplete, while a red icon indicates that target fields are unassigned.

Structure Overview in SAP XI Message Mappings

Use

The structure overview displays all fields (elements and attributes) in the source and target structures. In the structure overview, you can assign source and target fields to each other or include them in the data-flow editor (see: Assigning a Field). The structure overview also contains a variety of additional functions that are described below.

Features

Functions in the Header Area

You use the structure overview on both the Definition and Test tab pages. Most of the buttons available in the structure overview are available on both tab pages.

Structure Overview Buttons

Button	Use
Tree View (only on Definition tab page)	View that only displays nodes for fields (elements and attributes) and their names.
Tabular Tree View	When you select this view, on the Definition tab page the field attributes or their type are displayed in addition to the tree view. In the test environment, you can enter values for the test in an additional column in the source structure.
Source Text View	Displays the structure as text in the editor. You can edit the text document directly in the test environment.
Expand Tree Collapse Tree	Expands/collapses tree.
Pretty Print (only on the Test tab page in the source document view)	Makes the XML document more readable by using indentations.
Show/Hide Search Field	Shows or hides the input help to search for fields in the structure. The search function does not support wildcard characters. To search for a node, you simply need to enter the first letter of the node name.
Save Document Source	Saves the structure as an XML file.
Show Complete Path (only in Tree View or Tabular Tree View)	Displays prefixes for namespaces and numbering for duplicated fields in the structure overview (see also Duplicating Subtrees).
Hide Unused Fields (only in Tree View or Tabular Tree View)	Hides all fields in the structure that are not used in any target-field mapping.
Remove Unused Fields (only in the Tree View or the Tabular Tree View on the Test tab page)	Removes all fields from the structure of a test instance that are not used in any target-field mapping.

General Functions in the Source and Target Structures

Differentiating Field Names on the Same Hierarchy Level

The field names of the source and target structure must be unique. The mapping editor supports identical field names on the same hierarchy level in the following way:

● Fields of the source and target structure can be qualified by namespaces

● Attributes are differentiated from elements by way of a preceding at symbol (@) in the mapping editor.

Access Paths for Fields

For fields in the structure overview (on both the Definition and Test tab pages) you can copy the path for a field to the clipboard by choosing the context menu option Copy Path. This also applies to fields in the data-flow editor.

Recursive Structures

The mapping editor does not fully support the mapping of recursive structures (data types that reference themselves). In the structure overview, elements of this type are indicated by means of an icon ().

Due to their recursive nature, the substructures of these elements can theoretically be infinitely long. It is possible to map these elements in the mapping editor in a rudimentary fashion by using the context menu to expand a specific number of subnodes and then use them in target-field mappings.

Special Functions: Source Structure

Where-Used List

● You can display the fields of the source structure in a where-used list:

● Position the cursor on a field to display a quick info that contains information about the target fields this particular field is assigned to by means of a target-field mapping.

● To display a where-used list for a particular field, call the context menu and choose Where-Used List. You can navigate directly to the target fields that a particular field is assigned to.

Special Functions: Target Structure

Navigating to Target-Field Mappings

If a field in the target structure is green or yellow, this indicates that an incomplete target-field mapping already exists. Double-click a field to display it in the data-flow editor.

Target-Field Mappings for Particular Positions

To define target-field mappings for different positions of a target element that occurs frequently, the context menu for the target structure has the function Duplicate Subtree (see: Duplicating Subtrees). You have the option of deleting any duplicates that you create.

Disabling Fields

A mapping is complete when there is a target-field mapping for all obligatory target fields. In cross-system scenarios where the values for such fields are not entered during mapping, but at a later point in time, this specification is too restrictive. To disable a target field and all its subnodes, choose the context menu option Disable Field in the structure overview. The mapping editor shows disabled fields crossed out. The check and the mapping runtime ignore disabled fields.

Assigning a Field in SAP XI Message Mappings

Use

Using the structure overview and the data-flow editor you can map source fields of the source structure to a target field.

Features

You can:

● Use drag and drop to select a source field in the structure overview and map it to a target field, or the other way around. The mapping editor displays this simple assignment in the data-flow editor.

● Drag a target field and one or more source fields from the structure overview to the data-flow editor. The data-flow editor automatically assigns the first source/target field pair. If a target field has already been mapped, then the mapping is displayed in the data-flow editor.

● Select a source and target field from the structure view by double-clicking. Note that you always transfer source fields to the data-flow editor by double-clicking. However, this is only possible for target fields if they have not already been assigned a source field. When you double click a target field that has already been assigned, the system navigates to the corresponding mapping.

In the data-flow editor you can then connect source fields with standard functions or with your own functions (see: Functions in the Data-Flow Editor). In the simplest instance, assign a source field to a target field. The value of the source field is then transferred to the target field at runtime.

A source field can also be mapped to multiple target fields. Simply define multiple target field mappings in which the source field is assigned to the respective target field.

Status Display

Icon Types

Icon	Description
	Attribute
	Element
	Element with maxOccurs = unbounded

Icon Colors

Color	Description
White	Attribute or element not assigned
red	Attribute or element must be assigned to complete the mapping
yellow	Attribute or element has already been assigned but the corresponding mapping in the data-flow editor is not complete
green	Mapping to target field complete

Furthermore, collapsed target field names in the mapping editor are displayed in red if target field mappings for subnodes of the marked field name are still missing.

The colors used for the data-flow objects in the data-flow editor have the same meanings as those used above.

Data-Flow Editor in SAP XI Message Mappings

Use

You use the data-flow editor (at the bottom of the mapping editor) to describe the flow of data from one or more source fields to one target field. Since this mapping is only a part of the actual message mapping and refers to a particular target field, this type of mapping is known as a Target Field Mapping.

Features

The data-flow editor comprises the following:

· An editor window in which you can insert functions and source and target fields as rectangles, and move them as required. These rectangles are known as data-flow objects because you use them to describe the data-flow between source fields and target fields.

· A function chooser in the lower screen area of the data-flow editor that contains the functions of various function categories. Using this function chooser, you can drag functions as new data-flow objects and drop them in the editor window. Furthermore, by clicking on an empty space in the data-flow editor you can call a function menu to access frequently used functions.

On the left-hand side of the editor window there are general functions that are useful when editing a target field mapping:

General Functions of the Data-Flow Editor

Function	Meaning
Delete Floating Objects	Deletes all data-flow objects that are not connected to a source and target field. Floating data-flow objects are displayed in orange.
Lay Out Mapping	Produces an ordered representation of the target field mapping. You can also call this function by selecting the right mouse button on an empty area of the data-flow editor and moving the mouse quickly back and forth.
Delete Current Mapping	Deletes the target field mapping currently displayed.

Functions of the Context Menu

Function	Use
General functions (see above)	You can also access the general functions explained in the table above by calling the context menu in empty areas of the data-flow editor.
Delete	Deletes one or more data-flow objects (to select multiple objects with the mouse, hold down the CTRL key).
Copy and Insert	Copy from one or more data-flow objects (also to other target field mappings) to reuse the whole or part of the target field mapping. The function copies the data-flow object for which the context menu was called, and the entire ‘object tree’ that determines the input values for the data-flow object. The target field cannot be copied.
Display Queue	Displays the queue for a field or a function for complete target field mappings, if an XML instance has been loaded or entered on the Test tab page. The result queue is displayed for functions, while the results values are displayed for target fields before they are written to the target structure. The target structure specifies which values are taken from this queue, for example, depending on the occurrence value specified in the target structure. You can display multiple queues in parallel in separate windows. Within a queue window, you can update the queue, and number the entries of the queue consecutively.
Context	Sets the context for source fields. In the default setting, each field is in the context of the next higher-level field. If this default setting was overwritten by the menu, the data-flow editor displays the field names in the data-flow object in italics. For more information, see Structure Mapping by Setting the Context.
Find Field	Searches for and selects a field in the structure overview.
Copy Path	Copies the access path for a field to the clipboard to reuse it in another location (insert it using CTRL+V).
Where-Used List	You can call this function from the context menu for the function chooser. The menu shows whether the function is used, and if so, where.

Activities

...

1. Once you have selected the source fields and the target field you want (see: Assigning a Field), select a function category from the function chooser:

¡ If you have already created a user-defined function, it is located in the User-Defined function category.

¡ All other categories contain the most important standard functions for message mappings.

2. Select a function from the function chooser either by double-clicking, or by using drag and drop to drag it to the editor area.

3. Connect the selected function to the other data-flow objects for the source fields and the target field by connecting the small rectangles for the input and output values using drag and drop. However, if you use the secondary mouse button, you do not actually have to connect to the box; instead you can let this connection be created for you within the data-flow object. Arrows represent connected elements.

4. To undo a connection, remove the arrow from the corresponding rectangle and drop it anywhere outside the data-flow object.

5. To delete any data-flow objects that you no longer require, choose Delete in the context menu. To delete all floating data-flow objects (displayed in light-blue), choose Delete Floating Objects.

6. Once all data-flow objects are green the mapping for the target field mapping is complete from a logical point of view.

Example

In the example above, a mapping to the target field name was selected that is connected to the source fields firstName and lastName using the standard function concat. Input values of any data-flow objects are displayed in small rectangles on the left of the object, while output values are displayed on the right of the object. You use these small rectangles to connect data-flow objects to each other so as to define a data flow between multiple source fields and exactly one target field. Technically speaking, a target field mapping is complete once at least one source field has been assigned to a target field and all arguments for each connecting function have values. Since this is the case in the example illustrated here, the data-flow editor displays the connected objects in green.