Designer (Data Flow)
The function of the Data Flow Designer is either to automatically visualise existing elements (profiles and profile chains, Content Inspection entries, ASM entries, ETL/ELT entries , workflows , partner channels) that are available in Lobster_data as diagrams. All profiles in a profile chain (and, if applicable, Content Inspection and ASM entries, etc.) and their connections are inserted in the diagram.
Alternatively, you can model new diagrams (e.g. profile chains) manually. Connections made between profiles (and Content Inspection entries, ASM entries, etc.) are all entered automatically in the involved components (e.g. connecting Message Response Routes) after the diagram has been saved.
Later, in the Process View, the concrete sequence of a profile chain can be visualised on the basis of the jobs involved.
(1) Before you can create a design (Data Flow entry), you must first create a group using the context menu. All designs must be assigned to a group.
(2) Subsequently, you can use the context menu to create a Data Flow entry (design) in the new group.
(3) See section Expert Search.
Context Menu
Context Menu Group
|
Create new Data Flow entry |
Self-explanatory. |
|
Import package |
Imports a previously exported package (→ see Export package).
(1) In another dialogue you can then select which elements of the Data Flow entry from the package you actually want to import. |
|
Import Transport Manager package |
If Data Flow entries were transferred via Transport Manager, they can be imported here. |
|
Create new group |
Self-explanatory. |
|
Change group |
Self-explanatory. |
|
Delete group |
Self-explanatory. |
Context Menu Entry
|
View/edit |
Self-explanatory. |
|
Open in new window |
Opens the Data Flow entry in another browser tab. Attention : Your browser might block this as an unauthorised popup. Check your browser settings if necessary. See also section Help. |
|
Duplicate entry |
Creates a copy of the Data Flow entry. Only a copy of the Data Flow entry itself is created. The elements it contains, such as profiles, are not copied (→ see also Complete deep copy ). |
|
Quick view |
Shows a list of all elements used in the Data Flow entry. |
|
To clipboard |
Allows copying the name and ID of the Data Flow entry in another dialogue. |
|
Set entries to 'active' |
Self-explanatory. |
|
Set entries to 'inactive' |
Self-explanatory. |
|
Complete deep copy (including all entries) |
Creates a copy of the Data Flow entry . A copy is created of the Data Flow entry itself and of all the elements it contains, such as profiles (→ see also Duplicate entry). The copy created in this way, with all the elements it contains, is completely referenced in itself and thus completely separate from the copied Data Flow entry and its elements . Note: Used channels are not copied .
(1) Refers to the name of the Data Flow entry and the names of all elements used in it (e. g. profiles). The prefix is always placed in front or replaces the substring to be replaced if it is found. Example: My_DataFlow becomes V2_My_DataFlow and V1_My_DataFlow becomes V2_My_DataFlow. (2) Refers to the name of the Data Flow entry and the names of all elements used in it (e. g. profiles). The suffix is always appended or replaces the substring to be replaced if it is found. (3) Refers to profiles used in the Data Flow entry with Input Agents HTTP time-driven (→ field URL) and HTTP event-driven (→ field URL address suffix). The suffix is always appended or replaces the substring to be replaced if it is found. (4) If the Data Flow entry contains an ASM entry, this suffix is appended (or replaced) there in the Main settings in field Directory and in the name of the copied ASM entry. (5) This can be used to replace system constants that are used in the Data Flow entry itself or in elements contained therein (e.g. profiles). The system constants must be selected manually, no automatic list is created. |
|
Export package (including all entries) |
Exports the Data Flow entry and all elements contained in it (→ see also Import package). Another dialogue will appear for this purpose.
(1) and (2) Select the elements to be exported here. |
|
Import package |
Imports a previously exported package (→ see Export package).
(1) In another dialogue you can then select which elements of the Data Flow entry from the package you actually want to import. |
|
Import Transport Manager package |
If Data Flow entries were transferred via Transport Manager, they can be imported here. In another dialogue you can then select which elements of the Data Flow entry from the package you actually want to import, see Import package. |
|
Delete |
Deletes the Data Flow entry itself, but not elements contained in it (→ see also Delete with references). |
|
Delete with references |
Attention: This deletes the Data Flow entry itself and also any elements (profiles, ASM and Content Inspection entries, etc.) contained in it. However, another dialogue appears for this purpose, in which you can select the elements to be deleted. |
|
Create new Data Flow entry |
Self-explanatory. |
