Integration Model Editor - Revision history

Jen at 18:06, 22 October 2025

2025-10-22T18:06:30Z

← Older revision		Revision as of 14:06, 22 October 2025
Line 85:		Line 85:
	Once dragged in, it behaves like the other context blocks and can be connected to any of the other blocks and even other composed block context instances. The ports represent the composed ports modeled in the actual composed block context.		Once dragged in, it behaves like the other context blocks and can be connected to any of the other blocks and even other composed block context instances. The ports represent the composed ports modeled in the actual composed block context.
	[[File:Imeditor - ComposedInstance.png\|none\|thumb\|831x831px]]		[[File:Imeditor - ComposedInstance.png\|none\|thumb\|831x831px]]

			[[Category:UserGuide\|0031_Integration_Model_Editor]]

Derek: /* Transport Nodes */

2024-07-23T19:25:56Z

Transport Nodes

← Older revision		Revision as of 15:25, 23 July 2024
Line 25:		Line 25:
	The IM Editor lets you work on one '''Context''' at a time. First, drag and drop to insert a '''UoP Instance'''. (Technically, the UoP Instance exists outside the Context, but since it's connected to things inside, it will be useful to have it here).		The IM Editor lets you work on one '''Context''' at a time. First, drag and drop to insert a '''UoP Instance'''. (Technically, the UoP Instance exists outside the Context, but since it's connected to things inside, it will be useful to have it here).

	=== ~~Transport Nodes~~ ===		=== Processing Blocks ===
	~~Transport nodes~~ come in several flavors which can be created by dragging and dropping from the Stencil tool on the left-hand side.		Processing blocks come in several flavors which can be created by dragging and dropping from the Stencil tool on the left-hand side.

	~~Once placed in the '''Context''', the Node Inspector on the right-hand side is used to give the nodes names, descriptions, and other data specific to its type.~~
	~~[[File:Imeditor - Sidepanel.png\|none\|thumb\|916x916px]]~~

			Once placed in the '''Context''', the Block Inspector on the right-hand side is used to give the blocks names, descriptions, and other data specific to its type.
			[[File:Imeditor - Sidepanel2.png\|none\|thumb\|915x915px]]
	*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.		*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.
	* '''Transforms''' consume one type of View and produce another. The ~~Node~~ Inspector is used to adjust settings. Notably, the Transform type is used to change from		* '''Transforms''' consume one type of View and produce another. The Block Inspector is used to adjust settings. Notably, the Transform type is used to change from
	** Automatic transform that draws on semantic and measurement information to mediate between the two Views:		** Automatic transform that draws on semantic and measurement information to mediate between the two Views:
	*: [[File:Imeditor - AutoTransform.png\|none\|200px]]		*: [[File:Imeditor - AutoTransform.png\|none\|200px]]
Line 49:		Line 48:
	Connections are created by dragging from an output port to an input port:		Connections are created by dragging from an output port to an input port:
	[[File:Imeditor - Connection1.png\|none\|thumb\|678x678px]]		[[File:Imeditor - Connection1.png\|none\|thumb\|678x678px]]
	If the data types are inconsistent then the connection will turn red and you won't be allowed to save. In this situation, we have a UoP Instance ~~node~~ outputting BasicTypes, and sending it to an Endpoint expecting ComplexTypes:		If the data types are inconsistent then the connection will turn red and you won't be allowed to save. In this situation, we have a UoP Instance block outputting BasicTypes, and sending it to an Endpoint expecting ComplexTypes:
	[[File:Mismatched.png\|none\|thumb\|511x511px]]		[[File:Mismatched.png\|none\|thumb\|511x511px]]

	=== Ports ===		=== Ports ===
	Ports facilitate the type that is used during context ~~node~~ connections and can be either input or output endpoints. Ports can accessed from the ~~Node~~ Inspector on the right-hand side when selecting a ~~node~~ with ports. All ports have rolename, flowtrigger, type, and a special identifier field depending on which type is selected. Additionally, ports can be dragged around a context ~~nodes~~ border from within the context.		Ports facilitate the type that is used during context block connections and can be either input or output endpoints. Ports can accessed from the Block Inspector on the right-hand side when selecting a block with ports. All ports have rolename, flowtrigger, type, and a special identifier field depending on which type is selected. Additionally, ports can be dragged around a context blocks border from within the context.

	There are two types of ports:		There are two types of ports:
Line 67:		Line 66:

	== Composed Block Integration Contexts ==		== Composed Block Integration Contexts ==
	The composed block integration context is a special kind of context that can be nested inside another context of any type, treating it as a context ~~node~~ via a composed block instance.		The composed block integration context is a special kind of context that can be nested inside another context of any type, treating it as a context block via a composed block instance.

	Any high-level context can include a composed block instance to simplify complex modeling and connections. This setup lets viewers understand the overall flow without getting overwhelmed by the modeling details held within the composed block context.		Any high-level context can include a composed block instance to simplify complex modeling and connections. This setup lets viewers understand the overall flow without getting overwhelmed by the modeling details held within the composed block context.
Line 76:		Line 75:

	=== Composed Ports ===		=== Composed Ports ===
	From within the composed block context, the user may drag in any number of Composed In/Out port ~~nodes~~. The composed ports ~~nodes~~ have only one respective input/output port and can be connected to the other context ~~nodes~~. They need to be configured similarly to normal ports and require a Type and designated identifier (DataType or TemplateType).		From within the composed block context, the user may drag in any number of Composed In/Out port blocks. The composed ports blocks have only one respective input/output port and can be connected to the other context blocks. They need to be configured similarly to normal ports and require a Type and designated identifier (DataType or TemplateType).

	These composed port ~~nodes~~ are identical to the ones utilized by a composed block instance.		These composed port blocks are identical to the ones utilized by a composed block instance.
	[[File:Imeditor - trimmedComposedPort1.png\|none\|thumb\|794x794px]]		[[File:Imeditor - trimmedComposedPort1.png\|none\|thumb\|794x794px]]

Line 84:		Line 83:
	After the user is finished creating their composed block context and either saves or commits it, the composed block context can be seen in the NavTree and is ready to be dragged in as an instance to another context of any type.		After the user is finished creating their composed block context and either saves or commits it, the composed block context can be seen in the NavTree and is ready to be dragged in as an instance to another context of any type.

	Once dragged in, it behaves like the other context ~~nodes~~ and can be connected to any of the other ~~nodes~~ and even other composed block context instances. The ports represent the composed ports modeled in the actual composed block context.		Once dragged in, it behaves like the other context blocks and can be connected to any of the other blocks and even other composed block context instances. The ports represent the composed ports modeled in the actual composed block context.
	[[File:Imeditor - ComposedInstance.png\|none\|thumb\|831x831px]]		[[File:Imeditor - ComposedInstance.png\|none\|thumb\|831x831px]]

Derek at 19:01, 23 July 2024

2024-07-23T19:01:04Z

← Older revision		Revision as of 15:01, 23 July 2024
Line 86:		Line 86:
	Once dragged in, it behaves like the other context nodes and can be connected to any of the other nodes and even other composed block context instances. The ports represent the composed ports modeled in the actual composed block context.		Once dragged in, it behaves like the other context nodes and can be connected to any of the other nodes and even other composed block context instances. The ports represent the composed ports modeled in the actual composed block context.
	[[File:Imeditor - ComposedInstance.png\|none\|thumb\|831x831px]]		[[File:Imeditor - ComposedInstance.png\|none\|thumb\|831x831px]]


	~~== Code Generation ==~~
	~~CinC generation targets a different type of element called a '''Main Program'''. These are created from the main 'CREATE' dropdown.~~
	~~[[File:Imeditor - Codegen1.png\|none\|thumb\|830x830px]]~~
	~~Once your Main Program exists, you can associate UoP Instances to it so they become part of the generated code.~~
	~~[[File:Imeditor - Codegen2.png\|none\|thumb\|834x834px]]~~

	~~Similarly, Main Programs can be placed in '''Processing Elements''' - but these are not incorporated into generation yet.~~

Nathalie: /* Transport Nodes */

2024-07-23T18:31:08Z

Transport Nodes

← Older revision		Revision as of 14:31, 23 July 2024
Line 33:		Line 33:
	*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.		*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.
	* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from		* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from
	** Automatic transform that draws on semantic and measurement information to mediate between the two Views: ~~test~~		** Automatic transform that draws on semantic and measurement information to mediate between the two Views:
	[[File:Imeditor - AutoTransform.png\|none\|~~thumb\|221x221px~~]]		*: [[File:Imeditor - AutoTransform.png\|none\|200px]]

	** Manual transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:		** Manual transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:
	++[[File:Imeditor - ManualTransform.png\|none\|~~thumb\|282x282px~~]]		*:[[File:Imeditor - ManualTransform.png\|none\|200px]]

	* '''Filters''' require a 'Test' field that will filter out Views for which the test evaluates to False.		* '''Filters''' require a 'Test' field that will filter out Views for which the test evaluates to False.

Nathalie: /* Transport Nodes */

2024-07-23T18:25:38Z

Transport Nodes

← Older revision		Revision as of 14:25, 23 July 2024
Line 33:		Line 33:
	*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.		*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.
	* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from		* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from
	** Automatic transform that draws on semantic and measurement information to mediate between the two Views:		** Automatic transform that draws on semantic and measurement information to mediate between the two Views: test
	++[[File:Imeditor - AutoTransform.png\|none\|thumb\|221x221px]]		[[File:Imeditor - AutoTransform.png\|none\|thumb\|221x221px]]

	** Manual transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:		** Manual transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:

Derek: /* Transport Nodes */

2024-07-23T18:21:42Z

Transport Nodes

← Older revision		Revision as of 14:21, 23 July 2024
Line 41:		Line 41:
	* '''Filters''' require a 'Test' field that will filter out Views for which the test evaluates to False.		* '''Filters''' require a 'Test' field that will filter out Views for which the test evaluates to False.
	* '''Transporters''' allow you to select a '''Transport Channel''' to transmit across.		* '''Transporters''' allow you to select a '''Transport Channel''' to transmit across.
	* '''~~Fanins~~''' allow for several input connections and only outputs one type.		* '''FanIns''' allow for several input connections and only outputs one type.
	* '''''Generics''''' can have any number of input or output connections.		* '''Generics''' can have any number of input or output connections.
	* '''SIM Adapters''' for Single Instance Messaging communication style.		* '''SIM Adapters''' for Single Instance Messaging communication style.
	* '''Queuing Adapters''' for Queuing communication style.		* '''Queuing Adapters''' for Queuing communication style.
Line 56:		Line 56:
	Ports facilitate the type that is used during context node connections and can be either input or output endpoints. Ports can accessed from the Node Inspector on the right-hand side when selecting a node with ports. All ports have rolename, flowtrigger, type, and a special identifier field depending on which type is selected. Additionally, ports can be dragged around a context nodes border from within the context.		Ports facilitate the type that is used during context node connections and can be either input or output endpoints. Ports can accessed from the Node Inspector on the right-hand side when selecting a node with ports. All ports have rolename, flowtrigger, type, and a special identifier field depending on which type is selected. Additionally, ports can be dragged around a context nodes border from within the context.

	There are two ~~views when editing a~~ ports ~~Type~~:		There are two types of ports:

	a) ~~Default &~~ Data Type		a) Data Type

	Data Type must be given from an existing view type from the model.		Data Type must be given from an existing view type from the model.
	[[File:Imeditor - PortDefault.png\|none\|thumb]]		[[File:Imeditor - PortDefault.png\|none\|thumb]]
	b) ~~Templated &~~ Template type		b) Template type

	Template type ~~must be typed into the input and~~ is determined by the user.		Template type is determined by the user.
	[[File:Imeditor - PortTemplated.png\|none\|thumb]]		[[File:Imeditor - PortTemplated.png\|none\|thumb]]

Nathalie: /* Transport Nodes */

2024-07-23T18:14:47Z

Transport Nodes

← Older revision		Revision as of 14:14, 23 July 2024
Line 34:		Line 34:
	* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from		* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from
	** Automatic transform that draws on semantic and measurement information to mediate between the two Views:		** Automatic transform that draws on semantic and measurement information to mediate between the two Views:
	[[File:Imeditor - AutoTransform.png\|none\|thumb\|221x221px]]		++[[File:Imeditor - AutoTransform.png\|none\|thumb\|221x221px]]

	** Manual transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:		** Manual transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:
	[[File:Imeditor - ManualTransform.png\|none\|thumb\|282x282px]]		++[[File:Imeditor - ManualTransform.png\|none\|thumb\|282x282px]]

	* '''Filters''' require a 'Test' field that will filter out Views for which the test evaluates to False.		* '''Filters''' require a 'Test' field that will filter out Views for which the test evaluates to False.

Nathalie: /* Transport Nodes */

2024-07-23T18:07:28Z

Transport Nodes

← Older revision		Revision as of 14:07, 23 July 2024
Line 32:		Line 32:

	*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.		*'''Sources''' / '''Sinks''' have only one port. These represent elements that simply produce or consume Views.
	* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from ~~A) an~~ Automatic transform that draws on semantic and measurement information to mediate between the two Views:		* '''Transforms''' consume one type of View and produce another. The Node Inspector is used to adjust settings. Notably, the Transform type is used to change from
			** Automatic transform that draws on semantic and measurement information to mediate between the two Views:
	[[File:Imeditor - AutoTransform.png\|none\|thumb\|221x221px]]		[[File:Imeditor - AutoTransform.png\|none\|thumb\|221x221px]]

	~~B) manual~~ transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:		** Manual transform, which allows arbitrary assignment fields which will be parsed and incorporated into the generated transformation code:
	[[File:Imeditor - ManualTransform.png\|none\|thumb\|282x282px]]		[[File:Imeditor - ManualTransform.png\|none\|thumb\|282x282px]]

Derek: /* UoP Instances */

2024-07-23T18:06:49Z

UoP Instances

← Older revision		Revision as of 14:06, 23 July 2024
Line 8:		Line 8:
	'''UoP Instances''' are, as the name suggests, instantiated Units of Portability. They can be created from the IM Editor or from the 'Create' dropdown in regular Navigate mode.		'''UoP Instances''' are, as the name suggests, instantiated Units of Portability. They can be created from the IM Editor or from the 'Create' dropdown in regular Navigate mode.

	Each one is given a name and a Configuration URI. You are also expected to select some subset of the UoP's Connections to use as '''Endpoints''' in the '''UoP Instance'''.		Each one is given a name and a Configuration URI (optional). You are also expected to select some subset of the UoP's Connections to use as '''Endpoints''' in the '''UoP Instance'''.
	[[File:Imeditor - UoPInstance.png\|none\|thumb\|920x920px]]		[[File:Imeditor - UoPInstance.png\|none\|thumb\|920x920px]]

Line 16:		Line 16:
	Currently UDP channels are supported.		Currently UDP channels are supported.

	At the moment, you are expected to use the description field to populate the following comma-~~seperated~~ values: '''ip, local port, destination ip, destination port, ttl'''.		At the moment, you are expected to use the description field to populate the following comma-separated values: '''ip, local port, destination ip, destination port, ttl'''.

	== Integration Contexts ==		== Integration Contexts ==
Line 27:		Line 27:
	=== Transport Nodes ===		=== Transport Nodes ===
	Transport nodes come in several flavors which can be created by dragging and dropping from the Stencil tool on the left-hand side.		Transport nodes come in several flavors which can be created by dragging and dropping from the Stencil tool on the left-hand side.
	~~[[File:Imeditor - TransportNodes.png\|none\|thumb\|916x916px]]~~
	Once placed in the '''Context''', the Node Inspector on the right-hand side is used to give the nodes names, descriptions, and other data specific to its type.		Once placed in the '''Context''', the Node Inspector on the right-hand side is used to give the nodes names, descriptions, and other data specific to its type.
	[[File:Imeditor - Sidepanel.png\|none\|thumb\|916x916px]]		[[File:Imeditor - Sidepanel.png\|none\|thumb\|916x916px]]

Derek: /* Composed Ports */

2024-07-22T18:59:43Z

Composed Ports

← Older revision		Revision as of 14:59, 22 July 2024
Line 79:		Line 79:

	These composed port nodes are identical to the ones utilized by a composed block instance.		These composed port nodes are identical to the ones utilized by a composed block instance.
	[[File:Imeditor - ~~ComposedPort1~~.png\|none\|thumb\|794x794px]]		[[File:Imeditor - trimmedComposedPort1.png\|none\|thumb\|794x794px]]

	=== Composed Block Context Instances ===		=== Composed Block Context Instances ===