diff --git a/connector/doc/Amazon_AWS_CloudFormation.md b/connector/doc/Amazon_AWS_CloudFormation.md index 2aab269b..391ed3ae 100644 --- a/connector/doc/Amazon_AWS_CloudFormation.md +++ b/connector/doc/Amazon_AWS_CloudFormation.md @@ -67,19 +67,19 @@ Here is an example command using the **AWS CLI** to create a stack with the name > --parameters **ParameterKey=InstanceType,ParameterValue=t2.micro ParameterKey=KeyName,ParameterValue=my-key-pair \\** > --capabilities **CAPABILITY_IAM CAPABILITY_NAMED_IAM** -![createStack.JPG](~/images/Amazon_AWS_CloudFormation_createStack.JPG) +![createStack.JPG](~/connector/images/Amazon_AWS_CloudFormation_createStack.JPG) -![create stack.png](~/images/Amazon_AWS_CloudFormation_create_stack.png) +![create stack.png](~/connector/images/Amazon_AWS_CloudFormation_create_stack.png) During the creation process, the **Status** column will contain the value *Create in Progress*. If the creation was successful, it will contain the value *Created*. -![createStackProgress.JPG](~/images/Amazon_AWS_CloudFormation_createStackProgress.JPG) +![createStackProgress.JPG](~/connector/images/Amazon_AWS_CloudFormation_createStackProgress.JPG) If an error happens during the creation of a stack, a pop-up window will display an error message. You can then find more details on the **Stack Errors page** and in the **element log file**. -![createStackError.JPG](~/images/Amazon_AWS_CloudFormation_createStackError.JPG) +![createStackError.JPG](~/connector/images/Amazon_AWS_CloudFormation_createStackError.JPG) -![createStackErrorPage.JPG](~/images/Amazon_AWS_CloudFormation_createStackErrorPage.JPG) +![createStackErrorPage.JPG](~/connector/images/Amazon_AWS_CloudFormation_createStackErrorPage.JPG) ### Deleting a Stack @@ -91,9 +91,9 @@ The **Status** column will then display *Delete in Progress* until the stack is After you create a stack, you can link it to DataMiner Stack Deployment by right-clicking the relevant row in the Stacks table and selecting **Link with Stack Deployment.** You will then be able to select the right deployment in a dialog box. -![LinkStackDeploymentContextMenu.JPG](~/images/Amazon_AWS_CloudFormation_LinkStackDeploymentContextMenu.JPG) +![LinkStackDeploymentContextMenu.JPG](~/connector/images/Amazon_AWS_CloudFormation_LinkStackDeploymentContextMenu.JPG) -![LinkStackDeployment.JPG](~/images/Amazon_AWS_CloudFormation_LinkStackDeployment.JPG) +![LinkStackDeployment.JPG](~/connector/images/Amazon_AWS_CloudFormation_LinkStackDeployment.JPG) ### Unlinking a Stack from Stack Deployment @@ -103,7 +103,7 @@ To remove the link between a stack and a stack deployment, right-click the relev By default the element will hold 10 Stack Deployment entries. You can create, update, and delete entries via the right-click menu of the Stacks Deployment table. If you need to create many entries at the same time, use the **Create Stacks Deployments** button. -![StacksDeployment.JPG](~/images/Amazon_AWS_CloudFormation_StacksDeployment.JPG) +![StacksDeployment.JPG](~/connector/images/Amazon_AWS_CloudFormation_StacksDeployment.JPG) ### External Request - Create Stack diff --git a/connector/doc/Astro_U116_Edge_PAL.md b/connector/doc/Astro_U116_Edge_PAL.md index 89667b66..7b8db517 100644 --- a/connector/doc/Astro_U116_Edge_PAL.md +++ b/connector/doc/Astro_U116_Edge_PAL.md @@ -146,7 +146,7 @@ This is how you can upload/download configuration files to the device: - To **download** a file, click *Download*. The following pop-up window will be displayed: - ![Download.PNG](~/images/Download.PNG) + ![Download.PNG](~/connector/images/Download.PNG) Enter the name of the file then click on `OK'. The file will be saved at this location: @@ -154,7 +154,7 @@ This is how you can upload/download configuration files to the device: - To **upload** a file, click *Upload*. The following pop-up window will be displayed: - ![Upload.PNG](~/images/Upload.PNG) + ![Upload.PNG](~/connector/images/Upload.PNG) **Module Name** lists all the Astro elements of the same type in the system. @@ -166,7 +166,7 @@ This is how you can upload/download configuration files to the device: The connector allows the user to upload a firmware archive from the local disk of the DMA: -![SoftwareUpdate.PNG](~/images/Astro_U116_Edge_PAL_SoftwareUpdate.PNG) +![SoftwareUpdate.PNG](~/connector/images/Astro_U116_Edge_PAL_SoftwareUpdate.PNG) The **Firmware File** parameter is used to select which file to upload. The dropdown lists all the files present in the DMA hard drive at the location: C:\Skyline DataMiner\Documents\\Protocol Name\>. diff --git a/connector/doc/Astro_U124_Edge_FM.md b/connector/doc/Astro_U124_Edge_FM.md index 362dcb98..8723fe07 100644 --- a/connector/doc/Astro_U124_Edge_FM.md +++ b/connector/doc/Astro_U124_Edge_FM.md @@ -118,7 +118,7 @@ The following table provides more information on how to upload/download configur - To **download** a file, click *Download*. The following pop-up window will be displayed: - ![Download.PNG](~/images/Download.PNG) + ![Download.PNG](~/connector/images/Download.PNG) Enter the name of the file then click on `OK'. The file will be saved at this location: @@ -126,7 +126,7 @@ The following table provides more information on how to upload/download configur - To **upload** a file, click *Upload*. The following pop-up window will be displayed: - ![Upload.PNG](~/images/Upload.PNG) + ![Upload.PNG](~/connector/images/Upload.PNG) **Module Name** lists all the Astro elements of the same type in the system. @@ -138,7 +138,7 @@ The following table provides more information on how to upload/download configur The connector allows you to upload a firmware archive from the local disk of the DMA: -![SoftwareUpdate.PNG](~/images/Astro_U124_Edge_FM_SoftwareUpdate.PNG) +![SoftwareUpdate.PNG](~/connector/images/Astro_U124_Edge_FM_SoftwareUpdate.PNG) The **Firmware File** parameter is used to select which file to upload. The drop-down list contains all the files present in the following directory of the DMA: *C:\Skyline DataMiner\Documents\\Protocol Name\>*. diff --git a/connector/doc/Astro_U125_Edge_FM.md b/connector/doc/Astro_U125_Edge_FM.md index dadfc0ea..08cf33fe 100644 --- a/connector/doc/Astro_U125_Edge_FM.md +++ b/connector/doc/Astro_U125_Edge_FM.md @@ -124,7 +124,7 @@ This page allows you to upload or download config files to or from the device. Y To download a file, click **Download**. The following pop-up window will be displayed: -![Download.PNG](~/images/Astro_U125_Edge_FM_Download.PNG) +![Download.PNG](~/connector/images/Astro_U125_Edge_FM_Download.PNG) Enter the name of the file and click OK. @@ -134,7 +134,7 @@ The file will be saved in the following location: `C:\Skyline DataMiner\Document To download a file, click **Upload**. The following pop-up window will be displayed: -![Upload.PNG](~/images/Astro_U125_Edge_FM_Upload.PNG) +![Upload.PNG](~/connector/images/Astro_U125_Edge_FM_Upload.PNG) **Module Name** lists all the Astro elements of the same type in the system. @@ -146,7 +146,7 @@ The file to be uploaded is in the following location: `C:\Skyline DataMiner\Docu The connector allows you to upload a firmware archive from the local disk of the DMA: -![SoftwareUpdate.PNG](~/images/Astro_U125_Edge_FM_SoftwareUpdate.PNG) +![SoftwareUpdate.PNG](~/connector/images/Astro_U125_Edge_FM_SoftwareUpdate.PNG) The **Firmware File** parameter is used to select which file to upload. The drop-down box lists all the files present on the DMA hard drive in the following location: *C:\Skyline DataMiner\Documents\\Protocol Name\>*. diff --git a/connector/doc/Astro_U148.md b/connector/doc/Astro_U148.md index 6df637ce..e3c1ce92 100644 --- a/connector/doc/Astro_U148.md +++ b/connector/doc/Astro_U148.md @@ -142,7 +142,7 @@ The following table provides more information on how to upload/download configur - To **download** a file, click *Download*. The following pop-up window will be displayed: - ![Download.PNG](~/images/Download.PNG) + ![Download.PNG](~/connector/images/Download.PNG) Enter the name of the file then click on `OK'. The file will be saved at this location: @@ -150,7 +150,7 @@ The following table provides more information on how to upload/download configur - To **upload** a file, click *Upload*. The following pop-up window will be displayed: - ![Upload.PNG](~/images/Upload.PNG) + ![Upload.PNG](~/connector/images/Upload.PNG) **Module Name** lists all the Astro elements of the same type in the system. @@ -162,7 +162,7 @@ The following table provides more information on how to upload/download configur The connector allows you to upload a firmware archive from the local disk of the DMA: -![SoftwareUpdate.PNG](~/images/Astro_U148_SoftwareUpdate.PNG) +![SoftwareUpdate.PNG](~/connector/images/Astro_U148_SoftwareUpdate.PNG) The **Firmware File** parameter is used to select which file to upload. The drop-down list contains all the files present in the following directory of the DMA: *C:\Skyline DataMiner\Documents\\Protocol Name\>*. diff --git a/connector/doc/Astro_U154_Edge_QAM.md b/connector/doc/Astro_U154_Edge_QAM.md index dcad4ba8..17a9e4e0 100644 --- a/connector/doc/Astro_U154_Edge_QAM.md +++ b/connector/doc/Astro_U154_Edge_QAM.md @@ -134,7 +134,7 @@ The following table provides more information on how to upload/download configur - To **download** a file, click *Download*. The following pop-up window will be displayed: - ![Download.PNG](~/images/Download.PNG) + ![Download.PNG](~/connector/images/Download.PNG) Enter the name of the file then click on `OK'. The file will be saved at this location: @@ -142,7 +142,7 @@ The following table provides more information on how to upload/download configur - To **upload** a file, click *Upload*. The following pop-up window will be displayed: - ![Upload.PNG](~/images/Upload.PNG) + ![Upload.PNG](~/connector/images/Upload.PNG) **Module Name** lists all the Astro elements of the same type in the system. @@ -154,7 +154,7 @@ The following table provides more information on how to upload/download configur The connector allows you to upload a firmware archive from the local disk of the DMA: -![SoftwareUpdate.PNG](~/images/Astro_U154_Edge_QAM_SoftwareUpdate.PNG) +![SoftwareUpdate.PNG](~/connector/images/Astro_U154_Edge_QAM_SoftwareUpdate.PNG) The **Firmware File** parameter is used to select which file to upload. The drop-down list contains all the files present in the following directory of the DMA: *C:\Skyline DataMiner\Documents\\Protocol Name\>*. diff --git a/connector/doc/Astro_U158_Edge_QAM.md b/connector/doc/Astro_U158_Edge_QAM.md index 947d5d35..3984c4e1 100644 --- a/connector/doc/Astro_U158_Edge_QAM.md +++ b/connector/doc/Astro_U158_Edge_QAM.md @@ -144,7 +144,7 @@ To download a file: 1. Click **Download**. The following pop-up message will be displayed: - ![Download.PNG](~/images/Astro_U158_Edge_QAM_Download.PNG) + ![Download.PNG](~/connector/images/Astro_U158_Edge_QAM_Download.PNG) 1. Enter the name of the file and click OK. The file will be saved in the following location: @@ -154,7 +154,7 @@ To upload a file: 1. Click **Upload**. The following pop-up window will be displayed: - ![Upload.PNG](~/images/Astro_U158_Edge_QAM_Upload.PNG) + ![Upload.PNG](~/connector/images/Astro_U158_Edge_QAM_Upload.PNG) 1. In this window, **Module Name** lists all the Astro elements of the same type in the system. **Upload File Name** lists all the files available in the Documents folder of the selected module. @@ -164,7 +164,7 @@ To upload a file: The connector allows you to upload a firmware archive from the local disk of the DMA: -![SoftwareUpdate.PNG](~/images/Astro_U158_Edge_QAM_SoftwareUpdate.PNG) +![SoftwareUpdate.PNG](~/connector/images/Astro_U158_Edge_QAM_SoftwareUpdate.PNG) The **Firmware File** parameter is used to select which file to upload. The drop-down list contains all the files present in the following folder on the DMA: C:\Skyline DataMiner\Documents\\Protocol Name\>. diff --git a/connector/doc/Astro_U168_Edge_DVB-T.md b/connector/doc/Astro_U168_Edge_DVB-T.md index 4fb96960..ef0b2fdf 100644 --- a/connector/doc/Astro_U168_Edge_DVB-T.md +++ b/connector/doc/Astro_U168_Edge_DVB-T.md @@ -126,7 +126,7 @@ To download a file: 1. Click **Download**. The following pop-up message will be displayed: - ![Download.PNG](~/images/Astro_U168_Edge_DVB-T_Download.PNG) + ![Download.PNG](~/connector/images/Astro_U168_Edge_DVB-T_Download.PNG) 1. Enter the name of the file and click OK. The file will be saved in the following location: @@ -136,7 +136,7 @@ To upload a file: 1. Click **Upload**. The following pop-up window will be displayed: - ![Upload.PNG](~/images/Astro_U168_Edge_DVB-T_Upload.PNG) + ![Upload.PNG](~/connector/images/Astro_U168_Edge_DVB-T_Upload.PNG) 1. In this window, **Module Name** lists all the Astro elements of the same type in the system. **Upload File Name** lists all the files available in the Documents folder of the selected module. @@ -146,7 +146,7 @@ To upload a file: The connector allows you to upload a firmware archive from the local disk of the DMA: -![SoftwareUpdate.PNG](~/images/Astro_U168_Edge_DVB-T_SoftwareUpdate.PNG) +![SoftwareUpdate.PNG](~/connector/images/Astro_U168_Edge_DVB-T_SoftwareUpdate.PNG) The **Firmware File** parameter is used to select which file to upload. The drop-down list contains all the files present in the following folder on the DMA: C:\Skyline DataMiner\Documents\\Protocol Name\>. diff --git a/connector/doc/CISCO_D9854.md b/connector/doc/CISCO_D9854.md index 1c63c3bd..8dc37be7 100644 --- a/connector/doc/CISCO_D9854.md +++ b/connector/doc/CISCO_D9854.md @@ -133,7 +133,7 @@ Physical dynamic interfaces: When you set the demodulator Rx Frequency (on the Demodulator page) and the active Local Oscillator inputs (on the Inputs page), the absolute difference (\|Rx Frequency - LO\|) of both must result in a L-band frequency between 950 and 2150 Mhz. If the difference is not within the mentioned range, a message will be displayed (see image below) and the previous value will be used instead. -![2020-12-17 16_02_44-DataMiner - Internet Explorer.png](~/images/CISCO_D9854_2020-12-17_16_02_44-DataMiner_-_Internet_Explorer.png) +![2020-12-17 16_02_44-DataMiner - Internet Explorer.png](~/connector/images/CISCO_D9854_2020-12-17_16_02_44-DataMiner_-_Internet_Explorer.png) If you want to change the value of both Rx Frequency and Local Oscillator, you can do so as follows: @@ -141,12 +141,12 @@ If you want to change the value of both Rx Frequency and Local Oscillator, you c 1. Set the Rx Frequency to the desired value. - ![2020-12-17 16_18_44-DataMiner - Internet Explorer.png](~/images/CISCO_D9854_2020-12-17_16_18_44-DataMiner_-_Internet_Explorer.png) + ![2020-12-17 16_18_44-DataMiner - Internet Explorer.png](~/connector/images/CISCO_D9854_2020-12-17_16_18_44-DataMiner_-_Internet_Explorer.png) 1. Set the active Local Oscillator to the desired value. In case both Local Oscillator 1 and 2 are in use, you need to set both to 0. Note also that the procedure above only applies when you want to change both values while keeping a valid range, e.g. changing RX Frequency from 3 GHz to 7 GHz while also changing the Local Oscillator from 5 GHz to 8 GHz. You can also configure an alternative RF Input to the desired values and then switch the active input over to the new configuration, as depicted below. -![2020-12-17 16_15_29-DataMiner - Internet Explorer.png](~/images/CISCO_D9854_2020-12-17_16_15_29-DataMiner_-_Internet_Explorer.png) +![2020-12-17 16_15_29-DataMiner - Internet Explorer.png](~/connector/images/CISCO_D9854_2020-12-17_16_15_29-DataMiner_-_Internet_Explorer.png) When you select a different RF Input and the new L-band is out of the mentioned range, an information message will be displayed similar to the one displayed above. However, the value will be set even though the resulting L-band will be invalid. It is then up to you to properly define this. diff --git a/connector/doc/CISCO_DCM.md b/connector/doc/CISCO_DCM.md index 6ae781df..33872228 100644 --- a/connector/doc/CISCO_DCM.md +++ b/connector/doc/CISCO_DCM.md @@ -31,7 +31,7 @@ Please note the following: | Range | Supported Firmware | |--|--| -| 1.0.0.x 1.0.2.x 1.0.3.x | Supported firmware depends on each command. To check the minimum version necessary to run a command, refer to the **Minimum Required FW** column on the **Manager** page. If this column has the value "any", there is no information in the document "DCM_IDL.pdf" about the minimum version to run that command, so it is assumed to be compatible with all firmware versions. E.g. Command **Get Boards** requires firmware 6.9 or later. ![versions3.JPG](~/images/CISCO_DCM_versions3.JPG) | +| 1.0.0.x 1.0.2.x 1.0.3.x | Supported firmware depends on each command. To check the minimum version necessary to run a command, refer to the **Minimum Required FW** column on the **Manager** page. If this column has the value "any", there is no information in the document "DCM_IDL.pdf" about the minimum version to run that command, so it is assumed to be compatible with all firmware versions. E.g. Command **Get Boards** requires firmware 6.9 or later. ![versions3.JPG](~/connector/images/CISCO_DCM_versions3.JPG) | ## Configuration @@ -348,7 +348,7 @@ To configure these, a parameter is available above the relevant table where you For example: -> ![naming2.JPG](~/images/CISCO_DCM_naming2.JPG) +> ![naming2.JPG](~/connector/images/CISCO_DCM_naming2.JPG) > > In this example, the DisplayKey will be as follows: 'Board: (value of column 4 (User Name)) Type: (value of column 1 (Type))'. @@ -356,14 +356,14 @@ To find the column identifiers, check the corresponding Naming Format tooltips. > Based on the previous example: > -> ![naming4.JPG](~/images/CISCO_DCM_naming4.JPG) +> ![naming4.JPG](~/connector/images/CISCO_DCM_naming4.JPG) Note: - Because of the complexity of **display keys** (based on multiple tables), the connector will not check if generated formats will produce unique values. **This needs to be ensured by the user**. - There is dependency between tables, so if for instance the display key of **Board Info Table (Version 2)** is changed, this will be reflected in all tables that depend on it. In the previous example, the **Input TS Table** display key will be as follows: -> ![naming5.JPG](~/images/CISCO_DCM_naming5.JPG) +> ![naming5.JPG](~/connector/images/CISCO_DCM_naming5.JPG) - By default, all custom naming will be configured with the same values that were hardcoded before version 1.0.0.83. **No historic data will be lost**. diff --git a/connector/doc/CPI_K4D72C.md b/connector/doc/CPI_K4D72C.md index f8b8894a..77367d7c 100644 --- a/connector/doc/CPI_K4D72C.md +++ b/connector/doc/CPI_K4D72C.md @@ -46,7 +46,7 @@ SERIAL CONNECTION: ### System Setup -![2016-06-03 13_14_11-CPI Comm Protocols.vsdx - Visio Standard.png](~/images/CPI_K4D72C_2016-06-03_13_14_11-CPI_Comm_Protocols.vsdx_-_Visio_Standard.png) +![2016-06-03 13_14_11-CPI Comm Protocols.vsdx - Visio Standard.png](~/connector/images/CPI_K4D72C_2016-06-03_13_14_11-CPI_Comm_Protocols.vsdx_-_Visio_Standard.png) ## How to use diff --git a/connector/doc/Evertz_3080IPX.md b/connector/doc/Evertz_3080IPX.md index abb0d99b..6963399a 100644 --- a/connector/doc/Evertz_3080IPX.md +++ b/connector/doc/Evertz_3080IPX.md @@ -87,7 +87,7 @@ If the correct license is available, you can enable **IGMP polling**, **Inband C This page (illustrated below) contains general information about the video switch, such as the **Product Name**, **Product Features Table**, **MAC Address of the Interfaces**, etc. -![1. General.png](~/images/Evertz_3080IPX_Evertz_3080IPX_general.png) +![1. General.png](~/connector/images/Evertz_3080IPX_Evertz_3080IPX_general.png) ### Port Page diff --git a/connector/doc/Generic_KAFKA_Producer.md b/connector/doc/Generic_KAFKA_Producer.md index 36117df6..a2b1cb2d 100644 --- a/connector/doc/Generic_KAFKA_Producer.md +++ b/connector/doc/Generic_KAFKA_Producer.md @@ -182,21 +182,21 @@ Kafka message example: Row configuration example: -![Picture4.svg](~/images/Generic_KAFKA_Producer_Picture4.svg) +![Picture4.svg](~/connector/images/Generic_KAFKA_Producer_Picture4.svg) Based on the current configuration of the highlighted row, the Send Data column cell is set to *Enabled*, meaning that the polling cycle for the parameter with ID 2 is activated. The parameter value is polled from the element "Service test" every minute (as determined by the Forwarding Time column) and the value is only forwarded to the topic if the value changes (as determined by the On Change column). The current value is different from the previous one. It is possible to add parameters from all the elements with the same protocol name. -![row.svg](~/images/Generic_KAFKA_Producer_row.svg) +![row.svg](~/connector/images/Generic_KAFKA_Producer_row.svg) When you right-click the Parameters Configuration table, the following options are available: - **Add New Row**: Adds a default row with each cell value set to N/A except the Forwarding Time (with default value 30s), On Change (with default value *If Value Changes*) and Send Data (with default value *Disabled*). To properly set up a row, make sure to define the fields starting from the left-hand side: DataMiner ID first, then Protocol Name, and so on. This is because when you select the DataMiner ID, the discrete options for the Protocol Name are updated with the existing protocols on that DMA. The same occurs when you select a new Protocol Name: the discrete options for the Element Name are also updated. - ![1.svg](~/images/Generic_KAFKA_Producer_svg1.png) + ![1.svg](~/connector/images/Generic_KAFKA_Producer_svg1.png) - ![2.svg](~/images/Generic_KAFKA_Producer_2.svg) + ![2.svg](~/connector/images/Generic_KAFKA_Producer_2.svg) - **Enable Selected Row(s)**: The Send Data value will be set to *Enabled*, meaning that the parameter value will be sent to the parameter's topic in a Kafka message. diff --git a/connector/doc/Generic_Matrix_Virtualization.md b/connector/doc/Generic_Matrix_Virtualization.md index 9077d2b7..e7b9cf9c 100644 --- a/connector/doc/Generic_Matrix_Virtualization.md +++ b/connector/doc/Generic_Matrix_Virtualization.md @@ -40,7 +40,7 @@ This range allows you to select one of the following functionalities: **Concaten Note: It is possible to put a matrix virtualization on top of another matrix virtualization to **support multiple functionalities**. -![Overview.png](~/images/Generic_Matrix_Virtualization_Overview.png) +![Overview.png](~/connector/images/Generic_Matrix_Virtualization_Overview.png) To be able to build the matrix virtualization on top of matrix elements (which we will refer to as children) there has to be a **Status String** (which indicates the state of the matrix) available on these children. @@ -88,7 +88,7 @@ The **Output CSV** file must have the following columns: '*Output;Label;Matrix;C The above can be visualized as follows: -![Concat.png](~/images/Generic_Matrix_Virtualization_Concat.png) +![Concat.png](~/connector/images/Generic_Matrix_Virtualization_Concat.png) ### Configuration of CSV files for Tie-Lines method @@ -108,7 +108,7 @@ The **Tie-Line CSV** file must have the following columns: "*Tie-Line;Source (ma The above can be visualized as follows: -![TIELines.png](~/images/Generic_Matrix_Virtualization_TIELines.png) +![TIELines.png](~/connector/images/Generic_Matrix_Virtualization_TIELines.png) ### Configuration of CSV files for Dual Stream method @@ -124,7 +124,7 @@ The **Output CSV** file has to have the following columns: '"*Output;Label;Matri The above can be visualized as follows: -![DualStream.png](~/images/Generic_Matrix_Virtualization_DualStream.png) +![DualStream.png](~/connector/images/Generic_Matrix_Virtualization_DualStream.png) ### Configuration of element connections diff --git a/connector/doc/Generic_OPC_Data_Access.md b/connector/doc/Generic_OPC_Data_Access.md index fd3391c1..404dce4f 100644 --- a/connector/doc/Generic_OPC_Data_Access.md +++ b/connector/doc/Generic_OPC_Data_Access.md @@ -38,11 +38,11 @@ To set up DCOM correctly, make the following changes on the computer running the 1. Open the **Security** tab. 1. In **Launch and Activation Permissions**, select **Customize** and click **Edit**. This is necessary to grant permissions to users to start the OPC server. **Add** the same **user** (or **group**) as you created earlier. Use the **Check Names** button to check/select the correct user. Then make sure the Allow check boxes are checked for Local Launch, Remote Launch, Local Activation and Remote Activation: - ![Launch and Activation Permissions.png](~/images/Generic_OPC_Data_Access_Launch_and_Activation_Permissions.png) + ![Launch and Activation Permissions.png](~/connector/images/Generic_OPC_Data_Access_Launch_and_Activation_Permissions.png) 1. In **Access Permissions**, select **Customize** and click **Edit**. This is necessary to grant permission to users/groups to make calls to the OPC server. **Add** the same **user** (or **group**) as you created earlier. Use the **Check Names** button to check/select the correct user. Then make sure the Allow check boxes are checked for Local Access and Remote Access: - ![Access Permission Permissions.png](~/images/Generic_OPC_Data_Access_Access_Permission_Permissions.png) + ![Access Permission Permissions.png](~/connector/images/Generic_OPC_Data_Access_Access_Permission_Permissions.png) - Configuring the **Application Identity**: @@ -54,7 +54,7 @@ To set up DCOM correctly, make the following changes on the computer running the See the example below: - ![Identity Example.png](~/images/Generic_OPC_Data_Access_Identity_Example.png) + ![Identity Example.png](~/connector/images/Generic_OPC_Data_Access_Identity_Example.png) - Configuring the **System**: @@ -62,16 +62,16 @@ To set up DCOM correctly, make the following changes on the computer running the 1. Navigate to **Console Root \> Component Services \> Computers \> My Computer** and right-click **Properties**. 1. In the **Default Properties** tab, select the option **Enable Distributed COM on this computer**: - ![Default Properties.png](~/images/Generic_OPC_Data_Access_Default_Properties.png) + ![Default Properties.png](~/connector/images/Generic_OPC_Data_Access_Default_Properties.png) 1. In the **COM Security** tab, select all the buttons one by one, each time adding the user you created earlier. Again you can use the **Check Names** button. 1. In **Access Permissions**, make sure all options are enabled, as illustrated below, for the created user and for the **ANONYMOUS LOGON user**. - ![Access Permission.png](~/images/Generic_OPC_Data_Access_Access_Permission.png) + ![Access Permission.png](~/connector/images/Generic_OPC_Data_Access_Access_Permission.png) 1. In **Launch and Activation Permissions**, make sure all options are enabled, as illustrated below, for the created user and for the **ANONYMOUS LOGON user**. - ![Launch and Activation Permission.png](~/images/Generic_OPC_Data_Access_Launch_and_Activation_Permission.png) + ![Launch and Activation Permission.png](~/connector/images/Generic_OPC_Data_Access_Launch_and_Activation_Permission.png) Finally, you must validate the **firewall** on the client and server computer: @@ -79,21 +79,21 @@ Finally, you must validate the **firewall** on the client and server computer: - Create an **inbound** exception that allows computers using **TCP** on **all ports.** - ![Client_OPCInbound.png](~/images/Generic_OPC_Data_Access_Client_OPCInbound.png) + ![Client_OPCInbound.png](~/connector/images/Generic_OPC_Data_Access_Client_OPCInbound.png) - Create an **outbound** exception that allows computers using **TCP** on **port** **135.** Note that this port number could be different. - ![Client_OPCOutbound.png](~/images/Generic_OPC_Data_Access_Client_OPCOutbound.png) + ![Client_OPCOutbound.png](~/connector/images/Generic_OPC_Data_Access_Client_OPCOutbound.png) - Server side: - Create **inbound** exceptions as illustrated below. This should normally be fine because **all ports** are allowed. - ![Server_OPCInbounds.png](~/images/Generic_OPC_Data_Access_Server_OPCInbounds.png) + ![Server_OPCInbounds.png](~/connector/images/Generic_OPC_Data_Access_Server_OPCInbounds.png) - Create an **outbound** exception that allows computers using **TCP** on **port** **135.** Note that this port number could be different. - ![Server_OPCOutbound.png](~/images/Generic_OPC_Data_Access_Server_OPCOutbound.png) + ![Server_OPCOutbound.png](~/connector/images/Generic_OPC_Data_Access_Server_OPCOutbound.png) ## Usage \[1.0.0.x\] diff --git a/connector/doc/Generic_Ping.md b/connector/doc/Generic_Ping.md index 1356c047..af174b5f 100644 --- a/connector/doc/Generic_Ping.md +++ b/connector/doc/Generic_Ping.md @@ -47,7 +47,7 @@ The number of ping requests per poll cycle can be specified in the **Pings per C In the **Jitter** section of the table, you can configure the size (number of ping commands) and frequency intervals of ping bursts that will be used to measure jitter. There is also a separate **Jitter** **Admin Status** that can be used to enable or disable the measuring of jitter. This is because the measurement is done via a separate polling engine. In terms of configuration, jitter permits the modification of three key values that will modify the behavior of this separate polling engine. **Jitter Interval** and **Jitter Ping** **Interval** refer to the amount of time (in seconds and milliseconds respectively) that should pass between each burst of pings sent by the polling engine, as well as each individual ping in that burst. **Jitter Pings per Cycle** refers to the quantity of pings to be sent out as part of the jitter measurement. For example, the image below depicts a sequence of 3 ping bursts. The default settings use a **Jitter Interval** of 2 seconds, a **Jitter Ping Interval** of 15 milliseconds, and 4 **Jitter Pings per Cycle**. -![ping sequence.jpg](~/images/Generic_Ping_ping_sequence.jpg) +![ping sequence.jpg](~/connector/images/Generic_Ping_ping_sequence.jpg) To calculate the jitter, the polling engine sends out a burst of pings in accordance with the **Jitter Pings per Cycle** value. The latency value of these pings is stored in a buffer, and the delta between consecutive latency values is calculated. The table will then display the minimum and maximum of these delta values, as well as the average delta value, which will represent the measured jitter of the burst of pings. A key aspect of the jitter features is that the calculations can arrive at more or less precise measurements based on the input values. For example, if you want highly accurate information about the jitter in the communication with a device, you can configure the number of pings in a burst to be high and the intervals between each burst and its pings to be low. Alternatively, you can reduce the number of pings in a burst and raise the intervals to derive a less precise jitter measurement but not saturate a device with frequent communication. @@ -95,7 +95,7 @@ The older available operations are: - Example (underlined values are mandatory for this operation): - ![Example](~/images/Generic_Ping_example.png) + ![Example](~/connector/images/Generic_Ping_example.png) - **EditConfigs**: This command can update the follow configuration: @@ -117,4 +117,4 @@ The older available operations are: - Example (underlined values are mandatory for this operation; configuration values must be within the specific parameter's range): - ![Example](~/images/Generic_Ping_example2.png) + ![Example](~/connector/images/Generic_Ping_example2.png) diff --git a/connector/doc/Grass_Valley_Trinix.md b/connector/doc/Grass_Valley_Trinix.md index c6d15d1b..0938c31a 100644 --- a/connector/doc/Grass_Valley_Trinix.md +++ b/connector/doc/Grass_Valley_Trinix.md @@ -49,9 +49,9 @@ SERIAL CONNECTION: Before you create the element in DataMiner, you must configure an RCP client in the Encore system. To do this, you need to know the IP address of the DMA that will be communicating with the Encore controller. Until you configure the DataMiner server (DMA) as an RCP client, the Encore controller will refuse any attempts to connect, and this connector will fail. The Encore controller screen should look like the screenshots below. -![Encore configuration.png](~/images/Grass_Valley_Trinix_Encore_configuration.png) +![Encore configuration.png](~/connector/images/Grass_Valley_Trinix_Encore_configuration.png) -![Encore configuration flags.png](~/images/Grass_Valley_Trinix_Encore_configuration_flags.png) +![Encore configuration flags.png](~/connector/images/Grass_Valley_Trinix_Encore_configuration_flags.png) ## Usage diff --git a/connector/doc/IEC_60870_5-104.md b/connector/doc/IEC_60870_5-104.md index ca3d886e..a45f1060 100644 --- a/connector/doc/IEC_60870_5-104.md +++ b/connector/doc/IEC_60870_5-104.md @@ -55,7 +55,7 @@ A configuration file shall be imported with metadata of RTU's parameters. The fi As per example, below you may find a metadata file: -![Capture.GIF](~/images/IEC_60870_5-104_Capture.GIF) +![Capture.GIF](~/connector/images/IEC_60870_5-104_Capture.GIF) Note that the metadata columns above will be displayed in the Parameter table. diff --git a/connector/doc/Kubernetes_Manager.md b/connector/doc/Kubernetes_Manager.md index 7c50c677..d27315a9 100644 --- a/connector/doc/Kubernetes_Manager.md +++ b/connector/doc/Kubernetes_Manager.md @@ -75,7 +75,7 @@ In this range, a virtual connection is used with HTTPS support via QAction. Data To set up the connection, enter the Kubernetes server address and a valid bearer token on the General page, as depicted below. -![2019-03-08 13_14_47-Window.png](~/images/Kubernetes_Manager_2019-03-08_13_14_47-Window.png) +![2019-03-08 13_14_47-Window.png](~/connector/images/Kubernetes_Manager_2019-03-08_13_14_47-Window.png) ### Creation (v1.2.1.x and v1.2.2.x) @@ -91,7 +91,7 @@ HTTP CONNECTION: To set up the connection, enter a valid bearer token on the General page, as depicted below. If the token is valid, the Authorization State will change to "Authorized". -![kubernetesManagerSetupV1.2.1.x.png](~/images/Kubernetes_Manager_kubernetesManagerSetupV1.2.1.x.png) +![kubernetesManagerSetupV1.2.1.x.png](~/connector/images/Kubernetes_Manager_kubernetesManagerSetupV1.2.1.x.png) ### Web Interface (v1.0.0.x and v1.1.0.x) diff --git a/connector/doc/Miranda_Imagestore_750.md b/connector/doc/Miranda_Imagestore_750.md index e6c604ad..719737fa 100644 --- a/connector/doc/Miranda_Imagestore_750.md +++ b/connector/doc/Miranda_Imagestore_750.md @@ -123,4 +123,4 @@ From version 1.0.2.20 onwards, the connector can prevent a potential problem whe This is an example of what this should look like: -![MirandaImagestore750.png](~/images/Miranda_Imagestore_750_MirandaImagestore750.png) +![MirandaImagestore750.png](~/connector/images/Miranda_Imagestore_750_MirandaImagestore750.png) diff --git a/connector/doc/Miranda_Kaleido_IP_X310.md b/connector/doc/Miranda_Kaleido_IP_X310.md index 00d1ab09..688ea6ed 100644 --- a/connector/doc/Miranda_Kaleido_IP_X310.md +++ b/connector/doc/Miranda_Kaleido_IP_X310.md @@ -116,7 +116,7 @@ The page also contains two page buttons: > - **Output Service name:** Take this from the Kaleido configuration. If you cannot find this information, leave this the same as the Input Service Name. > - **Source Friendly Name**: Take this from the Stream Name. Replace each whitespace by a "+". Range 1.0.1.x only. > -> ![2022-07-05 15_26_05-Clipboard.png](~/images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png)![Clipboard](~/images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png) +> ![2022-07-05 15_26_05-Clipboard.png](~/connector/images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png)![Clipboard](~/connector/images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png) > > Finally, go to the **Alarm Table** page and enable the alarm table polling if necessary. By default, the connector should enable alarm monitoring for the necessary parameters. > diff --git a/connector/doc/Miranda_Kaleido_IP_X320.md b/connector/doc/Miranda_Kaleido_IP_X320.md index 3da7b76f..7f6aeaf5 100644 --- a/connector/doc/Miranda_Kaleido_IP_X320.md +++ b/connector/doc/Miranda_Kaleido_IP_X320.md @@ -112,7 +112,7 @@ The page also contains two page buttons: Note that the Transport Stream, Services, Teletext and Card health tables are filled via the imported Excel file, located in the folder indicated by the File Path parameter or in the element document folder. After these are filled in, the data is polled. - ![Example Excel Sheet Kaleido.png](~/images/Miranda_Kaleido_IP_X320_Example_Excel_Sheet_Kaleido.png) + ![Example Excel Sheet Kaleido.png](~/connector/images/Miranda_Kaleido_IP_X320_Example_Excel_Sheet_Kaleido.png) - **On-Air Services**: Opens a window where you can edit the on-air service times. diff --git a/connector/doc/Paneda_DAB_Monitor_Orchestration.md b/connector/doc/Paneda_DAB_Monitor_Orchestration.md index 73a0fc9f..34ebb027 100644 --- a/connector/doc/Paneda_DAB_Monitor_Orchestration.md +++ b/connector/doc/Paneda_DAB_Monitor_Orchestration.md @@ -74,7 +74,7 @@ To create or remove items, use the right-click menus of the tables. Entities can When you create a new DAB monitor container, you can configure multiple sources in the source list by separating them with a comma, as shown in the following screenshot: -![image](~/images/Paneda_DAB_Monitor_Orchestration_image.png) +![image](~/connector/images/Paneda_DAB_Monitor_Orchestration_image.png) ### UDP Proxies Page diff --git a/connector/doc/Paneda_Mux_Orchestration.md b/connector/doc/Paneda_Mux_Orchestration.md index 5501f17e..2de1cf02 100644 --- a/connector/doc/Paneda_Mux_Orchestration.md +++ b/connector/doc/Paneda_Mux_Orchestration.md @@ -72,4 +72,4 @@ To create or remove items, use the right-click menus of the tables. Entities can When you create a new mux, you can assign multiple network interfaces and static routes. To do so, separate the values with a comma (,) as shown in the following screenshot: -![image](~/images/Paneda_Mux_Orchestration_image.png) +![image](~/connector/images/Paneda_Mux_Orchestration_image.png) diff --git a/connector/doc/SCTE_UPS.md b/connector/doc/SCTE_UPS.md index 346e819c..7f88d3de 100644 --- a/connector/doc/SCTE_UPS.md +++ b/connector/doc/SCTE_UPS.md @@ -30,7 +30,7 @@ In the sections below, you can find more information on the different data pages This page displays general information about the UPS, such as the **Name**, **Vendor**, **IP**, and **MAC**, as illustrated in the example below. -![General.jpg](~/images/SCTE_UPS_General.jpg) +![General.jpg](~/connector/images/SCTE_UPS_General.jpg) Some considerations regarding the parameters on this page: @@ -61,7 +61,7 @@ This page displays relevant information regarding the UPS device, such as: The page also contains other parameters such as the **Input Voltage**, **Output Voltage**, and **Alarms**, as illustrated in the example below. -![Main.jpg](~/images/SCTE_UPS_Main_2.jpg) +![Main.jpg](~/connector/images/SCTE_UPS_Main_2.jpg) ### Batteries @@ -69,7 +69,7 @@ This page displays all relevant information about the batteries of the UPS devic This page also contains the **Battery String Table** and the **Batteries Table**, as illustrated below. -![Batteries DVE.jpg](~/images/SCTE_UPS_Batteries_DVE.jpg) +![Batteries DVE.jpg](~/connector/images/SCTE_UPS_Batteries_DVE.jpg) The **Battery Age** parameter needs to be properly configured by the operator, as it is one of the key parameters to calculate the **Predicted Remaining Time**. @@ -79,19 +79,19 @@ A page button provides access to the **Temperature Sensors** subpage, where you This page displays relevant information regarding the output of the UPS device, such as the **Output Current** and the **Output Voltage**, as illustrated below. -![Output DVE.jpg](~/images/SCTE_UPS_Output_DVE.jpg) +![Output DVE.jpg](~/connector/images/SCTE_UPS_Output_DVE.jpg) ### Modem This page displays information about the modem transponder of the UPS device, such as the **SNR Quality**, and **Rx** and **Tx Power**. -![Modem.jpg](~/images/SCTE_UPS_Modem.jpg) +![Modem.jpg](~/connector/images/SCTE_UPS_Modem.jpg) ### Test This page displays a summary of the last result of the tests performed by this connector. It contains parameters such as the **Predicted Remaining Time**, **Battery Quality**, **Float State**, and **Battery Temperature Variation**, as illustrated below. -![Test.jpg](~/images/SCTE_UPS_Test.jpg) +![Test.jpg](~/connector/images/SCTE_UPS_Test.jpg) About the different kinds of tests: @@ -125,7 +125,7 @@ To do so: 1. Unless the test is to be executed *One Time*, define the **End Date**, which indicates until when the test will be valid. 1. If you want to execute the scheduled test immediately, click the button **Start Test** in the row. - ![Schedule Tests.jpg](~/images/SCTE_UPS_Schedule_Tests.jpg) + ![Schedule Tests.jpg](~/connector/images/SCTE_UPS_Schedule_Tests.jpg) #### Create Test subpage (connector version \>= 1.0.2.21) @@ -136,13 +136,13 @@ From version 1.0.2.21 of the connector onwards, UPS tests are integrated in the 1. Set the **Duration**, **Duration Unit**, and **Maximum Voltage Difference**. You can also define if the test must take into account the **Minimum Voltage Threshold** or the **Full Drain Minimum Voltage Threshold**. These are mutually exclusive, so only one can be selected. 1. Click the **Add** button. An entry will be created in the Scheduled Test table. -![New test.jpg](~/images/SCTE_UPS_New_test.jpg) +![New test.jpg](~/connector/images/SCTE_UPS_New_test.jpg) #### History subpage The History subpage contains the **Battery History** table, which displays a summary of the results of the tests performed by this connector on the UPS device. Each entry in this table displays the **Status** of the test, the **Total Output**, the **Temperature**, and the **Capacity**. -![History DVE.jpg](~/images/SCTE_UPS_History_DVE.jpg) +![History DVE.jpg](~/connector/images/SCTE_UPS_History_DVE.jpg) ### Input Failure @@ -151,7 +151,7 @@ This page displays the tables **Input Failure Registration** and **Input Failure - The **Input Failure Registration** table keeps track of the input failure occurrences of the device. The table indicates when each failure started and ended, as well as the failure duration and impact on the network. A UPS device loses contact with the network when the batteries are fully depleted during an AC failure. - The **Input Failure Registration Summary** table contains a monthly summary of the failures of the device. The values here are aggregated based on all the occurrences during the month. -![Input Failure DVE.jpg](~/images/SCTE_UPS_Input_Failure_DVE.jpg) +![Input Failure DVE.jpg](~/connector/images/SCTE_UPS_Input_Failure_DVE.jpg) ### Threshold Configuration @@ -159,7 +159,7 @@ This page displays the Property Table, which contains the alarm threshold inform The alarm threshold data can be configured directly in the Property Table, or in bulk using the Export and Import functionality. -![Threshold DVE.png](~/images/SCTE_UPS_Threshold_DVE.png) +![Threshold DVE.png](~/connector/images/SCTE_UPS_Threshold_DVE.png) #### Exporting Threshold Parameters @@ -175,7 +175,7 @@ To export the content of the **Property Table**: The file will be placed in the following directory: *C:\Skyline DataMiner\Documents\SCTE UPS Collector\Property* - ![Export Property DVE.jpg](~/images/SCTE_UPS_Export_Property_DVE.jpg) + ![Export Property DVE.jpg](~/connector/images/SCTE_UPS_Export_Property_DVE.jpg) #### Import Threshold Parameters @@ -193,7 +193,7 @@ To update the content of the **Property Table** in bulk: The **Import Progress** bar will display the progress of the import, until it reaches 100. Once the import is done, you will also be able to see additional information, such as the number of **Errors** generated. - ![Import Property DVE.jpg](~/images/SCTE_UPS_Import_Property_DVE.jpg) + ![Import Property DVE.jpg](~/connector/images/SCTE_UPS_Import_Property_DVE.jpg) ### Web Interface diff --git a/connector/doc/SCTE_UPS_Collector.md b/connector/doc/SCTE_UPS_Collector.md index 366c8c33..0f282521 100644 --- a/connector/doc/SCTE_UPS_Collector.md +++ b/connector/doc/SCTE_UPS_Collector.md @@ -65,7 +65,7 @@ This page also contains the parameter **Number of Devices**, which indicates how On the Provisioning page, you can manage the list of UPS devices monitored by the collector. The page consists of several different sections, for which you can find more information below. -![Provisioning Update.jpg](~/images/SCTE_UPS_Collector_Provioning_Update.jpg) +![Provisioning Update.jpg](~/connector/images/SCTE_UPS_Collector_Provioning_Update.jpg) #### Add/Update Devices @@ -122,7 +122,7 @@ To **update devices**, follow the steps below. When the process is finished, the number of **Updated Devices** and **Failed** **Lines** will be displayed. - ![Add-Update Device.jpg](~/images/SCTE_UPS_Collector_Add-Update_Device.jpg) + ![Add-Update Device.jpg](~/connector/images/SCTE_UPS_Collector_Add-Update_Device.jpg) #### Delete Devices @@ -138,7 +138,7 @@ To **delete devices** in bulk from the SCTE UPS Collector element, follow the st When the process is finished, the number of **Deleted Devices** will be displayed. - ![Delete Devices.jpg](~/images/SCTE_UPS_Collector_Delete_Devices.jpg) + ![Delete Devices.jpg](~/connector/images/SCTE_UPS_Collector_Delete_Devices.jpg) #### Export Devices @@ -150,7 +150,7 @@ To **export the UPS device information** available in the Device Table to a CSV After this, the exporting of the devices will begin. When the process is finished, the **Export Status** will change to *Done*. - ![Export Devices.jpg](~/images/SCTE_UPS_Collector_Export_Devices.jpg) + ![Export Devices.jpg](~/connector/images/SCTE_UPS_Collector_Export_Devices.jpg) #### DVE Properties @@ -165,7 +165,7 @@ To update the element properties of the DVEs created per UPS device, follow the - Place - Region - ![Properties.jpg](~/images/SCTE_UPS_Collector_Properties.jpg) + ![Properties.jpg](~/connector/images/SCTE_UPS_Collector_Properties.jpg) - **Step 2**: Click the **Update** button. @@ -173,13 +173,13 @@ To update the element properties of the DVEs created per UPS device, follow the When the process is finished, the **Update Properties Status** will change to *Done*. - ![DVE Properties.jpg](~/images/SCTE_UPS_Collector_DVE_Properties.jpg) + ![DVE Properties.jpg](~/connector/images/SCTE_UPS_Collector_DVE_Properties.jpg) #### Geocoding This function can be used to determine the latitude and longitude of the UPS devices based on their address, using a GOOGLE API. -![Geocoding.png](~/images/SCTE_UPS_Collector_Geocoding.png) +![Geocoding.png](~/connector/images/SCTE_UPS_Collector_Geocoding.png) #### Advanced Device Configuration @@ -190,7 +190,7 @@ The export file will be created in the following directory: *C:\Skyline DataMine Modify this file and then upload it by selecting the file name in the **Import Advanced File** drop-down box and clicking the **Import** button. -![Advaned configuration.jpg](~/images/SCTE_UPS_Collector_Advaned_configuration.jpg) +![Advaned configuration.jpg](~/connector/images/SCTE_UPS_Collector_Advaned_configuration.jpg) #### Group Configuration @@ -198,13 +198,13 @@ This feature is available from version 1.0.2.21 of the connector onwards. It all You can first export the CSV file in order to get the template with the list of the current UPS devices of the collector. After configuring the groups in the file, you can then import the CSV file to update the Custom Group Column in the Device table. -![Group Config.jpg](~/images/SCTE_UPS_Collector_Group_Config.jpg) +![Group Config.jpg](~/connector/images/SCTE_UPS_Collector_Group_Config.jpg) #### Add New Device On the Provisioning page, the **Add New Device** page button opens a subpage where you can add a new UPS device to the collector element manually. -![Add New Device.jpg](~/images/SCTE_UPS_Collector_Add_New_Device.jpg) +![Add New Device.jpg](~/connector/images/SCTE_UPS_Collector_Add_New_Device.jpg) To add a new device, fill in the general information of the device. The **IP Address** and the **Name** of the UPS device must be filled in in order to create the device in the collector. The rest of the information is not mandatory. @@ -216,7 +216,7 @@ This page contains general information about the devices polled by the SCTE UPS Finally, the page also includes the threadpool statistics of the collector, including the **Threadpool Usage**, **Threadpool Max Duration**, etc. -![System Overview.png](~/images/SCTE_UPS_Collector_System_Overview.png) +![System Overview.png](~/connector/images/SCTE_UPS_Collector_System_Overview.png) #### Multithread Logic @@ -240,7 +240,7 @@ The Batteries page displays the **Battery String Table** and the **Batteries Tab The page also has a page button to the Temperature Sensors subpage, which contains the **Temperature Sensor Table**. -![Batteries.jpg](~/images/SCTE_UPS_Collector_Batteries.jpg) +![Batteries.jpg](~/connector/images/SCTE_UPS_Collector_Batteries.jpg) ### Input Failure @@ -250,13 +250,13 @@ The **Input Failure Registration** table keeps track of input failure occurrence The **Input Failure Registration Summary** table contains a monthly summary of the failures of all the devices. This table displays the **Total Duration** of the **Input Failure**, the **Failure Standby Events**, the **Impact on Network**, and the **Availability of Input Power** and **Network**. -![Input Failure.jpg](~/images/SCTE_UPS_Collector_Input_Failure.jpg) +![Input Failure.jpg](~/connector/images/SCTE_UPS_Collector_Input_Failure.jpg) ### Output The Output page contains the **Output Table**, which displays the power and current of all the UPS devices that are monitored by the collector. -![Output.jpg](~/images/SCTE_UPS_Collector_Output.jpg) +![Output.jpg](~/connector/images/SCTE_UPS_Collector_Output.jpg) ### Threshold Configuration @@ -264,7 +264,7 @@ The Threshold Configuration page displays the **Property Table**, which contains The alarm data can be configured directly in the **Property Table** or in bulk using the **Export** and **Import** functionality. -![Property Table.jpg](~/images/SCTE_UPS_Collector_Property_Table.jpg) +![Property Table.jpg](~/connector/images/SCTE_UPS_Collector_Property_Table.jpg) #### Export Threshold Parameters @@ -276,7 +276,7 @@ To export the content of the Property Table, follow the steps below. Once the process is finished, the **Device Export Status** will change to *Done*. The file will be placed in the following directory: *C:\Skyline DataMiner\Documents\SCTE UPS Collector\Property* - ![Export Properties.jpg](~/images/SCTE_UPS_Collector_Export_Properties.jpg) + ![Export Properties.jpg](~/connector/images/SCTE_UPS_Collector_Export_Properties.jpg) #### Import Threshold Parameters @@ -294,10 +294,10 @@ To update the content of the **Property Table** in bulk, follow the steps below. The **Import Progress** bar will display the progress of the import until it reaches 100. The number of **Updated Devices** and generated **Errors** will then also be displayed. - ![Import Properties.jpg](~/images/SCTE_UPS_Collector_Import_Properties.jpg) + ![Import Properties.jpg](~/connector/images/SCTE_UPS_Collector_Import_Properties.jpg) ### History The History page contains the **Battery History** table, which contains a summary of the results of the tests performed by this connector. Each entry in this table displays the **Status** of the test, the **Total Output**, the **Temperature**, and the **Capacity**. The tests can be configured on the SCTE UPS DVE elements, which each represent a UPS device. -![History.jpg](~/images/SCTE_UPS_Collector_History.jpg) +![History.jpg](~/connector/images/SCTE_UPS_Collector_History.jpg) diff --git a/connector/doc/SCTE_UPS_Manager.md b/connector/doc/SCTE_UPS_Manager.md index ba68488f..54050c27 100644 --- a/connector/doc/SCTE_UPS_Manager.md +++ b/connector/doc/SCTE_UPS_Manager.md @@ -100,13 +100,13 @@ This page displays a tree view of the available **SCTE UPS Collectors** and the For each selected **SCTE UPS Collector** element, basic identification data is displayed, as well as the DVEs that the **SCTE UPS Collector** has in its devices table. -![ONENOTE_kCxlJ0OyV5.png](~/images/SCTE_UPS_Manager_ONENOTE_kCxlJ0OyV5.png) +![ONENOTE_kCxlJ0OyV5.png](~/connector/images/SCTE_UPS_Manager_ONENOTE_kCxlJ0OyV5.png) ### Collectors This page displays the **Collector Table**, which contains the information of all the available SCTE UPS Collectors within the DataMiner System, such as the number of devices per collector and the corresponding thread information. -![Collector Table.jpg](~/images/SCTE_UPS_Manager_Collector_Table.jpg) +![Collector Table.jpg](~/connector/images/SCTE_UPS_Manager_Collector_Table.jpg) It is possible to modify the **Name** of the collector elements in this table. @@ -114,7 +114,7 @@ It is possible to modify the **Name** of the collector elements in this table. This page contains the **Provisioned Devices** table, which displays the devices that are provisioned in the available SCTE UPS Collectors. In this table, you can modify the **Name** and the **IP Address** of the UPS devices. -![New_Provisioned Devices.jpg](~/images/SCTE_UPS_Manager_New_Provisioned_Devices2.jpg) +![New_Provisioned Devices.jpg](~/connector/images/SCTE_UPS_Manager_New_Provisioned_Devices2.jpg) Below the table, a **Deletion Prefix** can be defined. If the name of a UPS device has this prefix, it will be deleted when the **Delete Devices** button is pressed. @@ -128,13 +128,13 @@ If a device has not been provisioned, the manager will determine if **Automatic - If **Automatic Provisioning** is *Disabled*, an entry will be created in the **Detected Devices** table. - ![Detected devices.jpg](~/images/SCTE_UPS_Manager_Detected_devices.jpg) + ![Detected devices.jpg](~/connector/images/SCTE_UPS_Manager_Detected_devices.jpg) This table displays basic information about the detected device, such as the **System Name**, **System Location**, **Serial Number** and the reason why the device was not automatically provisioned (e.g. because Manual mode was active, like in the image above). You can manually provision the devices in this table by right-clicking a specific entry and selecting **Provision**. A pop-up window will then be displayed where you can fill in the basic information of the device. The **DMS View** and **Collector** must always be specified. - ![Provision Device.jpg](~/images/SCTE_UPS_Manager_Provision_Device.jpg) + ![Provision Device.jpg](~/connector/images/SCTE_UPS_Manager_Provision_Device.jpg) When you click **OK**, the manager will provision the device in the selected collector. If an error occurs during this process, the details will appear in the **Failure Description** of the corresponding entry in the table. @@ -144,7 +144,7 @@ If a device has not been provisioned, the manager will determine if **Automatic This page contains the **Traps** Table, which displays the received Cold and Warm Traps that have not been processed yet. These traps are processed with the help of multithreaded logic. The thread statistics can be found on the General page. -![Traps.jpg](~/images/SCTE_UPS_Manager_Traps.jpg) +![Traps.jpg](~/connector/images/SCTE_UPS_Manager_Traps.jpg) In order for a trap to be processed and removed from the table, the device must respond to SNMP requests. @@ -154,11 +154,11 @@ The subpage **Auto Clear** is available via a page button on this page. On this This page displays the **Alarm Template Table**, where you can configure the parameters that determine which alarm template must be assigned to the UPS devices that are **automatically provisioned**. -![Alarm Table.jpg](~/images/SCTE_UPS_Manager_Alarm_Table.jpg) +![Alarm Table.jpg](~/connector/images/SCTE_UPS_Manager_Alarm_Table.jpg) To create an entry in this table, right-click the table and select **Add**. In the pop-up window, you will be able to configure the alarm template parameters. -![Alarm Template Config.jpg](~/images/SCTE_UPS_Manager_Alarm_Template_Config.jpg) +![Alarm Template Config.jpg](~/connector/images/SCTE_UPS_Manager_Alarm_Template_Config.jpg) When you have specified the configuration parameters, click **Save**. @@ -166,7 +166,7 @@ When you have specified the configuration parameters, click **Save**. This page contains the **Scheduled Test** table. -![Scheduled Tests.jpg](~/images/SCTE_UPS_Manager_Scheduled_Tests.jpg) +![Scheduled Tests.jpg](~/connector/images/SCTE_UPS_Manager_Scheduled_Tests.jpg) In this table, you can configure the tests that will be created in bulk in all the SCTE UPS Collector elements. To do so, follow the steps below. @@ -210,7 +210,7 @@ In version **2.0.0.12** of the connector, the Scheduler module is integrated wit 1. Click **OK**. - ![Create Test Manager.jpg](~/images/SCTE_UPS_Manager_Create_Test_Manager.jpg) + ![Create Test Manager.jpg](~/connector/images/SCTE_UPS_Manager_Create_Test_Manager.jpg) 1. Once all the tests have been created, click **Update UPS Tests**. This will replicate the tests in all the available UPS elements. The following logic will be applied in order to avoid all tests getting executed at the same time: diff --git a/connector/doc/ScheduAll_Manager.md b/connector/doc/ScheduAll_Manager.md index 777bb669..33b97f7f 100644 --- a/connector/doc/ScheduAll_Manager.md +++ b/connector/doc/ScheduAll_Manager.md @@ -78,7 +78,7 @@ The **web service** API is an XML interface over HTTP. DataMiner can send reques The connector combines data coming from several tables in ScheduAll. Below, you can find an overview of the different tables in ScheduAll: -![ScheduAll Structure.png](~/images/ScheduAll_Manager_ScheduAll_Structure.png) +![ScheduAll Structure.png](~/connector/images/ScheduAll_Manager_ScheduAll_Structure.png) ## Usage (range 2.0.0.x / 2.0.1.x) diff --git a/connector/doc/Skyline_Cassandra_Validator.md b/connector/doc/Skyline_Cassandra_Validator.md index f757d192..ddeb3f87 100644 --- a/connector/doc/Skyline_Cassandra_Validator.md +++ b/connector/doc/Skyline_Cassandra_Validator.md @@ -102,7 +102,7 @@ This error is thrown if you specified a **local user** in the settings instead o *For example, for an internal Failover setup, this looks like this: - ![failover.png](~/images/Skyline_Cassandra_Validator_failover.png) + ![failover.png](~/connector/images/Skyline_Cassandra_Validator_failover.png) **NOTE**: Only do this if there is absolutely no other option, as it may degrade security. See also: @@ -124,7 +124,7 @@ Write-Output $r ``` If this does not result in any problems, then you probably have no issues with the PowerShell commands. Otherwise, you may get an issue when sending the *Invoke-Command: -![validator error.png](~/images/Skyline_Cassandra_Validator_validator_error.png)* +![validator error.png](~/connector/images/Skyline_Cassandra_Validator_validator_error.png)* This error message simply means that the Windows Remote Management has not been configured on the remote or local server. Use the following command, followed by a "y": diff --git a/connector/doc/Skyline_ICMP_Platform_Manager.md b/connector/doc/Skyline_ICMP_Platform_Manager.md index 91cead56..8204104c 100644 --- a/connector/doc/Skyline_ICMP_Platform_Manager.md +++ b/connector/doc/Skyline_ICMP_Platform_Manager.md @@ -85,7 +85,7 @@ To configure the entire system properly, as a **DataMiner** **System Administrat **If the folder defined in the parameter does not exist, you will need to create it**. - ![Captura de pantalla 2021-10-19 174320.png](~/images/Skyline_ICMP_Platform_Manager_Captura_de_pantalla_2021-10-19_174320.png) + ![Captura de pantalla 2021-10-19 174320.png](~/connector/images/Skyline_ICMP_Platform_Manager_Captura_de_pantalla_2021-10-19_174320.png) Note that headers must be capitalized, and the file name should follow the format **DMAID_ElementID_ICMP**. diff --git a/connector/doc/Skyline_IP_Network_Manager.md b/connector/doc/Skyline_IP_Network_Manager.md index 6d1bb14d..0141f510 100644 --- a/connector/doc/Skyline_IP_Network_Manager.md +++ b/connector/doc/Skyline_IP_Network_Manager.md @@ -14,7 +14,7 @@ In order to use the IP Network Manager, you will need at least DataMiner version Initially, the application will not hold any devices to manage. It is therefore necessary to perform a discovery before you can start using the IP Network Manager. For this, you can use the **Discovery Wizard** of the application. -![IPNetworkManager_Flow.png](~/images/Skyline_IP_Network_Manager_IPNetworkManager_Flow.png) +![IPNetworkManager_Flow.png](~/connector/images/Skyline_IP_Network_Manager_IPNetworkManager_Flow.png) ## How to Use @@ -28,7 +28,7 @@ The map page shows the network devices that the application is managing. An icon | Icon | Device Type | |--|--| -| ![IPNetworkManager_IconServerLinked.png](~/images/Skyline_IP_Network_Manager_IPNetworkManager_IconServerLinked.png) | Server | +| ![IPNetworkManager_IconServerLinked.png](~/connector/images/Skyline_IP_Network_Manager_IPNetworkManager_IconServerLinked.png) | Server | | | Router | | | Switch | | | Unknown | diff --git a/connector/doc/Slack_Messaging.md b/connector/doc/Slack_Messaging.md index 9e33a0e5..6f47e348 100644 --- a/connector/doc/Slack_Messaging.md +++ b/connector/doc/Slack_Messaging.md @@ -87,19 +87,19 @@ This page displays general information on the Slack team to which the element is This page contains a table with all users that are part of the Slack team. -![Users.jpg](~/images/Slack_Messaging_Users.jpg) +![Users.jpg](~/connector/images/Slack_Messaging_Users.jpg) ### Conversations This page contains a table listing all possible conversations (public channels, private channels, instant messaging) that messages can be sent to. The "Send Message" column allows you to quickly send a message to a specific conversation. The last received message is shown in the "Last Message" column. -![Conversations.jpg](~/images/Slack_Messaging_Conversations.jpg) +![Conversations.jpg](~/connector/images/Slack_Messaging_Conversations.jpg) ### Automation Scripts This page contains a table with all existing Automation scripts in DataMiner that can be executed via commands in Slack. -![Scripts.jpg](~/images/Slack_Messaging_Scripts.jpg) +![Scripts.jpg](~/connector/images/Slack_Messaging_Scripts.jpg) To refresh the content of this table, use the **Refresh** button. @@ -128,7 +128,7 @@ The number of days that messages should remain in the table can be customized. On this page, the **OAuth access token** that should be used to communicate with the Slack API must be configured. The page also contains some parameters that display the current status of the authentication. -![authentication.jpg](~/images/Slack_Messaging_authentication.jpg) +![authentication.jpg](~/connector/images/Slack_Messaging_authentication.jpg) ### Websocket diff --git a/connector/doc/Sunrise_UPC_NetCracker_Interface.md b/connector/doc/Sunrise_UPC_NetCracker_Interface.md index 82e7426c..fd296400 100644 --- a/connector/doc/Sunrise_UPC_NetCracker_Interface.md +++ b/connector/doc/Sunrise_UPC_NetCracker_Interface.md @@ -39,7 +39,7 @@ This connector uses a virtual connection and does not require any configuration Any incoming job is registered in the Message Log table where the primary key is the Job Message Correlation ID. -![Capture2.JPG](~/images/Sunrise_UPC_NetCracker_Interface_Capture2.JPG) +![Capture2.JPG](~/connector/images/Sunrise_UPC_NetCracker_Interface_Capture2.JPG) The possible values for the Type column are: Activate, Replace or Deactivate, whereas for the State column are: Error or OK. diff --git a/connector/doc/Sunrise_UPC_RPD_Jobs.md b/connector/doc/Sunrise_UPC_RPD_Jobs.md index 80ba99bc..a8eb61da 100644 --- a/connector/doc/Sunrise_UPC_RPD_Jobs.md +++ b/connector/doc/Sunrise_UPC_RPD_Jobs.md @@ -36,7 +36,7 @@ This connector uses a virtual connection and does not require any configuration An incoming job is registered in the Job Events table where the primary key is the Job Message Correlation ID. -![Capture.JPG](~/images/Sunrise_UPC_RPD_Jobs_Capture.JPG) +![Capture.JPG](~/connector/images/Sunrise_UPC_RPD_Jobs_Capture.JPG) The possible values for the Type column are: Activate, Replace or Deactivate, whereas for the State column are: Executed or Cancelled. diff --git a/connector/doc/Tektronix_SignalVu.md b/connector/doc/Tektronix_SignalVu.md index 96ddb5cc..41f242ff 100644 --- a/connector/doc/Tektronix_SignalVu.md +++ b/connector/doc/Tektronix_SignalVu.md @@ -43,7 +43,7 @@ Due to the nature of this device, several packages need to be installed and conf You should see the following applications (the ones marked with a red box are the ones we will use): - ![TekVisa AppList.png](~/images/Tektronix_SignalVu_TekVisa_AppList.png) + ![TekVisa AppList.png](~/connector/images/Tektronix_SignalVu_TekVisa_AppList.png) ## Installation and configuration @@ -55,7 +55,7 @@ For this system to be accessed from the DataMiner server, some configuration is There you should see a GPIB interface under **Instruments**. It should be something like this: - ![01_Configuration.png](~/images/Tektronix_SignalVu_01_Configuration.png) + ![01_Configuration.png](~/connector/images/Tektronix_SignalVu_01_Configuration.png) If there is no GPIB present, go to the SignalVU User Manual and follow the Troubleshooting guide. @@ -63,17 +63,17 @@ For this system to be accessed from the DataMiner server, some configuration is This application does not run in a normal window. To see if it is running, go to the taskbar (near the clock) and right-click the TekVISA icon. - ![02_Configuration.png](~/images/Tektronix_SignalVu_02_Configuration.png) + ![02_Configuration.png](~/connector/images/Tektronix_SignalVu_02_Configuration.png) 1. Click **Start VXI-11 Server** (option surrounded by the red square in the image above). 1. Click **Server Properties** and ensure that both options are set to start when Windows starts, as illustrated below. - ![03_Configuration.png](~/images/Tektronix_SignalVu_03_Configuration.png) + ![03_Configuration.png](~/connector/images/Tektronix_SignalVu_03_Configuration.png) 1. Hover the mouse over the TekVisa LAN Server icon to check if you see an IP address (the same as your computer). - ![04_Configuration.png](~/images/Tektronix_SignalVu_04_Configuration.png) + ![04_Configuration.png](~/connector/images/Tektronix_SignalVu_04_Configuration.png) This indicates that the server is ready to pass the packets to the SignalVU Virtual GPIB. You can find more technical information on the Tektronix home page or in the SignalVu User Manual. @@ -85,23 +85,23 @@ On the DataMiner server, the National Instruments NiVISA package must be configu 1. Open the NiMax application that was previously installed on the server. - ![04b_Configuration.png](~/images/Tektronix_SignalVu_04b_Configuration.png) + ![04b_Configuration.png](~/connector/images/Tektronix_SignalVu_04b_Configuration.png) 1. In the tree view on the left, go to **Devices and Interfaces** \> **Network Devices**. 1. Right-click Network Devices and select **Create New VISA TCP/IP Resource**. - ![05_Configuration.png](~/images/Tektronix_SignalVu_05_Configuration.png) + ![05_Configuration.png](~/connector/images/Tektronix_SignalVu_05_Configuration.png) A new window will open with several options. 1. In the new window, select **Auto-Detect of LAN Instrument** and click **Next**. - ![06_Configuration.png](~/images/Tektronix_SignalVu_06_Configuration.png) + ![06_Configuration.png](~/connector/images/Tektronix_SignalVu_06_Configuration.png) 1. Select **Select intrument(s) detected on local subnet**. - ![07_Configuration.png](~/images/Tektronix_SignalVu_07_Configuration.png) + ![07_Configuration.png](~/connector/images/Tektronix_SignalVu_07_Configuration.png) 1. When all results are displayed in the box below, select the desired device. @@ -111,7 +111,7 @@ On the DataMiner server, the National Instruments NiVISA package must be configu The options tree will be updated and a LAN device will be created. - ![09_Configuration.png](~/images/Tektronix_SignalVu_09_Configuration.png) + ![09_Configuration.png](~/connector/images/Tektronix_SignalVu_09_Configuration.png) 1. Close the window. diff --git a/connector/doc/Telefonica_UDO_Ticketing_System.md b/connector/doc/Telefonica_UDO_Ticketing_System.md index 0414d7ce..9fc065a2 100644 --- a/connector/doc/Telefonica_UDO_Ticketing_System.md +++ b/connector/doc/Telefonica_UDO_Ticketing_System.md @@ -48,7 +48,7 @@ In order to use the **Telefonica UDO Ticketing System** connector, you must firs When the script has been imported, create a Correlation rule that will execute the Automation script whenever the Ineoquest iVMS generates or clears an alarm related to the video channels. The screenshot below illustrates how to do so. -![Correlation.jpg](~/images/Telefonica_UDO_Ticketing_System_Correlation.jpg) +![Correlation.jpg](~/connector/images/Telefonica_UDO_Ticketing_System_Correlation.jpg) For more information on the Correlation module, see [DataMiner Correlation](https://aka.dataminer.services/Correlation). @@ -88,8 +88,8 @@ This range introduces a change to where the **CATV Channels** information comes This range also introduces the possibility to choose elements that run the **Ineoquest iVMS ASM** connector. This means that the following change to the Correlation rule is needed: -![Alarm filter configuration](~/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-19_174320.png) +![Alarm filter configuration](~/connector/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-19_174320.png) You can also disable the Correlation rule that creates and closes the tickets, in order to do this manually instead. For this purpose, you need to save a **HyperLinks.xml** file in the *C:\Skyline DataMiner* folder and add the Automation script **Update Manual UDO Ticket** on the DMA. After that, you just have to right-click the corresponding alarm and select **Ticket UDO** \> **Create/Close UDO Ticket** as shown in the image below. -![Ticket UDO menu](~/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-20_134522.png) +![Ticket UDO menu](~/connector/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-20_134522.png) diff --git a/connector/doc/Vodafone_Service_Notes.md b/connector/doc/Vodafone_Service_Notes.md index 1e233cb3..7df87b70 100644 --- a/connector/doc/Vodafone_Service_Notes.md +++ b/connector/doc/Vodafone_Service_Notes.md @@ -62,8 +62,8 @@ This connector has a Visio file available to allow more user-friendly interactio Visio icons reference: -![notes.png](~/images/Vodafone_Service_Notes_notes.png) Opens the note visualizer. +![notes.png](~/connector/images/Vodafone_Service_Notes_notes.png) Opens the note visualizer. -![add.png](~/images/Vodafone_Service_Notes_add.png)Opens a dialog where you can specify the title and the note you want to add. +![add.png](~/connector/images/Vodafone_Service_Notes_add.png)Opens a dialog where you can specify the title and the note you want to add. -![edit.png](~/images/Vodafone_Service_Notes_edit.png)Opens a dialog where you can edit a title and content. +![edit.png](~/connector/images/Vodafone_Service_Notes_edit.png)Opens a dialog where you can edit a title and content. diff --git a/connector/doc/WISI_Optopus.md b/connector/doc/WISI_Optopus.md index 87e77401..35f8d196 100644 --- a/connector/doc/WISI_Optopus.md +++ b/connector/doc/WISI_Optopus.md @@ -81,7 +81,7 @@ A pair of keys must be provided to the WISI elements. By default they must be lo The key files should be created using **Putty Key Generator**. They must be of type *RSA,* using the *Open SSH* format and with *1040* bits (see "1" in the picture below). Save the public key from the panel by copying it to a file with the name provided in **RSA Public Key File Name.** Then export the private key to a file using the menu and save the file with the same name as **RSA Private Key File Name** (see "2" in the picture below). There is no need to set a **Key passphrase**. -![Untitled.png](~/images/WISI_Optopus_Untitled.png) +![Untitled.png](~/connector/images/WISI_Optopus_Untitled.png) Notes: diff --git a/images/Amazon_AWS_CloudFormation_LinkStackDeployment.JPG b/connector/images/Amazon_AWS_CloudFormation_LinkStackDeployment.JPG similarity index 100% rename from images/Amazon_AWS_CloudFormation_LinkStackDeployment.JPG rename to connector/images/Amazon_AWS_CloudFormation_LinkStackDeployment.JPG diff --git a/images/Amazon_AWS_CloudFormation_LinkStackDeploymentContextMenu.JPG b/connector/images/Amazon_AWS_CloudFormation_LinkStackDeploymentContextMenu.JPG similarity index 100% rename from images/Amazon_AWS_CloudFormation_LinkStackDeploymentContextMenu.JPG rename to connector/images/Amazon_AWS_CloudFormation_LinkStackDeploymentContextMenu.JPG diff --git a/images/Amazon_AWS_CloudFormation_StacksDeployment.JPG b/connector/images/Amazon_AWS_CloudFormation_StacksDeployment.JPG similarity index 100% rename from images/Amazon_AWS_CloudFormation_StacksDeployment.JPG rename to connector/images/Amazon_AWS_CloudFormation_StacksDeployment.JPG diff --git a/images/Amazon_AWS_CloudFormation_createStack.JPG b/connector/images/Amazon_AWS_CloudFormation_createStack.JPG similarity index 100% rename from images/Amazon_AWS_CloudFormation_createStack.JPG rename to connector/images/Amazon_AWS_CloudFormation_createStack.JPG diff --git a/images/Amazon_AWS_CloudFormation_createStackError.JPG b/connector/images/Amazon_AWS_CloudFormation_createStackError.JPG similarity index 100% rename from images/Amazon_AWS_CloudFormation_createStackError.JPG rename to connector/images/Amazon_AWS_CloudFormation_createStackError.JPG diff --git a/images/Amazon_AWS_CloudFormation_createStackErrorPage.JPG b/connector/images/Amazon_AWS_CloudFormation_createStackErrorPage.JPG similarity index 100% rename from images/Amazon_AWS_CloudFormation_createStackErrorPage.JPG rename to connector/images/Amazon_AWS_CloudFormation_createStackErrorPage.JPG diff --git a/images/Amazon_AWS_CloudFormation_createStackProgress.JPG b/connector/images/Amazon_AWS_CloudFormation_createStackProgress.JPG similarity index 100% rename from images/Amazon_AWS_CloudFormation_createStackProgress.JPG rename to connector/images/Amazon_AWS_CloudFormation_createStackProgress.JPG diff --git a/images/Amazon_AWS_CloudFormation_create_stack.png b/connector/images/Amazon_AWS_CloudFormation_create_stack.png similarity index 100% rename from images/Amazon_AWS_CloudFormation_create_stack.png rename to connector/images/Amazon_AWS_CloudFormation_create_stack.png diff --git a/images/Astro_U116_Edge_PAL_SoftwareUpdate.PNG b/connector/images/Astro_U116_Edge_PAL_SoftwareUpdate.PNG similarity index 100% rename from images/Astro_U116_Edge_PAL_SoftwareUpdate.PNG rename to connector/images/Astro_U116_Edge_PAL_SoftwareUpdate.PNG diff --git a/images/Astro_U124_Edge_FM_SoftwareUpdate.PNG b/connector/images/Astro_U124_Edge_FM_SoftwareUpdate.PNG similarity index 100% rename from images/Astro_U124_Edge_FM_SoftwareUpdate.PNG rename to connector/images/Astro_U124_Edge_FM_SoftwareUpdate.PNG diff --git a/images/Astro_U125_Edge_FM_Download.PNG b/connector/images/Astro_U125_Edge_FM_Download.PNG similarity index 100% rename from images/Astro_U125_Edge_FM_Download.PNG rename to connector/images/Astro_U125_Edge_FM_Download.PNG diff --git a/images/Astro_U125_Edge_FM_SoftwareUpdate.PNG b/connector/images/Astro_U125_Edge_FM_SoftwareUpdate.PNG similarity index 100% rename from images/Astro_U125_Edge_FM_SoftwareUpdate.PNG rename to connector/images/Astro_U125_Edge_FM_SoftwareUpdate.PNG diff --git a/images/Astro_U125_Edge_FM_Upload.PNG b/connector/images/Astro_U125_Edge_FM_Upload.PNG similarity index 100% rename from images/Astro_U125_Edge_FM_Upload.PNG rename to connector/images/Astro_U125_Edge_FM_Upload.PNG diff --git a/images/Astro_U148_SoftwareUpdate.PNG b/connector/images/Astro_U148_SoftwareUpdate.PNG similarity index 100% rename from images/Astro_U148_SoftwareUpdate.PNG rename to connector/images/Astro_U148_SoftwareUpdate.PNG diff --git a/images/Astro_U154_Edge_QAM_SoftwareUpdate.PNG b/connector/images/Astro_U154_Edge_QAM_SoftwareUpdate.PNG similarity index 100% rename from images/Astro_U154_Edge_QAM_SoftwareUpdate.PNG rename to connector/images/Astro_U154_Edge_QAM_SoftwareUpdate.PNG diff --git a/images/Astro_U158_Edge_QAM_Download.PNG b/connector/images/Astro_U158_Edge_QAM_Download.PNG similarity index 100% rename from images/Astro_U158_Edge_QAM_Download.PNG rename to connector/images/Astro_U158_Edge_QAM_Download.PNG diff --git a/images/Astro_U158_Edge_QAM_SoftwareUpdate.PNG b/connector/images/Astro_U158_Edge_QAM_SoftwareUpdate.PNG similarity index 100% rename from images/Astro_U158_Edge_QAM_SoftwareUpdate.PNG rename to connector/images/Astro_U158_Edge_QAM_SoftwareUpdate.PNG diff --git a/images/Astro_U158_Edge_QAM_Upload.PNG b/connector/images/Astro_U158_Edge_QAM_Upload.PNG similarity index 100% rename from images/Astro_U158_Edge_QAM_Upload.PNG rename to connector/images/Astro_U158_Edge_QAM_Upload.PNG diff --git a/images/Astro_U168_Edge_DVB-T_Download.PNG b/connector/images/Astro_U168_Edge_DVB-T_Download.PNG similarity index 100% rename from images/Astro_U168_Edge_DVB-T_Download.PNG rename to connector/images/Astro_U168_Edge_DVB-T_Download.PNG diff --git a/images/Astro_U168_Edge_DVB-T_SoftwareUpdate.PNG b/connector/images/Astro_U168_Edge_DVB-T_SoftwareUpdate.PNG similarity index 100% rename from images/Astro_U168_Edge_DVB-T_SoftwareUpdate.PNG rename to connector/images/Astro_U168_Edge_DVB-T_SoftwareUpdate.PNG diff --git a/images/Astro_U168_Edge_DVB-T_Upload.PNG b/connector/images/Astro_U168_Edge_DVB-T_Upload.PNG similarity index 100% rename from images/Astro_U168_Edge_DVB-T_Upload.PNG rename to connector/images/Astro_U168_Edge_DVB-T_Upload.PNG diff --git a/images/CISCO_D9854_2020-12-17_16_02_44-DataMiner_-_Internet_Explorer.png b/connector/images/CISCO_D9854_2020-12-17_16_02_44-DataMiner_-_Internet_Explorer.png similarity index 100% rename from images/CISCO_D9854_2020-12-17_16_02_44-DataMiner_-_Internet_Explorer.png rename to connector/images/CISCO_D9854_2020-12-17_16_02_44-DataMiner_-_Internet_Explorer.png diff --git a/images/CISCO_D9854_2020-12-17_16_15_29-DataMiner_-_Internet_Explorer.png b/connector/images/CISCO_D9854_2020-12-17_16_15_29-DataMiner_-_Internet_Explorer.png similarity index 100% rename from images/CISCO_D9854_2020-12-17_16_15_29-DataMiner_-_Internet_Explorer.png rename to connector/images/CISCO_D9854_2020-12-17_16_15_29-DataMiner_-_Internet_Explorer.png diff --git a/images/CISCO_D9854_2020-12-17_16_18_44-DataMiner_-_Internet_Explorer.png b/connector/images/CISCO_D9854_2020-12-17_16_18_44-DataMiner_-_Internet_Explorer.png similarity index 100% rename from images/CISCO_D9854_2020-12-17_16_18_44-DataMiner_-_Internet_Explorer.png rename to connector/images/CISCO_D9854_2020-12-17_16_18_44-DataMiner_-_Internet_Explorer.png diff --git a/images/CISCO_DCM_naming2.JPG b/connector/images/CISCO_DCM_naming2.JPG similarity index 100% rename from images/CISCO_DCM_naming2.JPG rename to connector/images/CISCO_DCM_naming2.JPG diff --git a/images/CISCO_DCM_naming4.JPG b/connector/images/CISCO_DCM_naming4.JPG similarity index 100% rename from images/CISCO_DCM_naming4.JPG rename to connector/images/CISCO_DCM_naming4.JPG diff --git a/images/CISCO_DCM_naming5.JPG b/connector/images/CISCO_DCM_naming5.JPG similarity index 100% rename from images/CISCO_DCM_naming5.JPG rename to connector/images/CISCO_DCM_naming5.JPG diff --git a/images/CISCO_DCM_versions3.JPG b/connector/images/CISCO_DCM_versions3.JPG similarity index 100% rename from images/CISCO_DCM_versions3.JPG rename to connector/images/CISCO_DCM_versions3.JPG diff --git a/images/CPI_K4D72C_2016-06-03_13_14_11-CPI_Comm_Protocols.vsdx_-_Visio_Standard.png b/connector/images/CPI_K4D72C_2016-06-03_13_14_11-CPI_Comm_Protocols.vsdx_-_Visio_Standard.png similarity index 100% rename from images/CPI_K4D72C_2016-06-03_13_14_11-CPI_Comm_Protocols.vsdx_-_Visio_Standard.png rename to connector/images/CPI_K4D72C_2016-06-03_13_14_11-CPI_Comm_Protocols.vsdx_-_Visio_Standard.png diff --git a/images/Docs_ConnectorDocumentation.svg b/connector/images/Docs_ConnectorDocumentation.svg similarity index 100% rename from images/Docs_ConnectorDocumentation.svg rename to connector/images/Docs_ConnectorDocumentation.svg diff --git a/images/Download.PNG b/connector/images/Download.PNG similarity index 100% rename from images/Download.PNG rename to connector/images/Download.PNG diff --git a/images/Evertz_3080IPX_Evertz_3080IPX_general.png b/connector/images/Evertz_3080IPX_Evertz_3080IPX_general.png similarity index 100% rename from images/Evertz_3080IPX_Evertz_3080IPX_general.png rename to connector/images/Evertz_3080IPX_Evertz_3080IPX_general.png diff --git a/images/Generic_Gestel_dcp)![]( b/connector/images/Generic_Gestel_dcp)![]( similarity index 100% rename from images/Generic_Gestel_dcp)![]( rename to connector/images/Generic_Gestel_dcp)![]( diff --git a/images/Generic_KAFKA_Producer_2.svg b/connector/images/Generic_KAFKA_Producer_2.svg similarity index 100% rename from images/Generic_KAFKA_Producer_2.svg rename to connector/images/Generic_KAFKA_Producer_2.svg diff --git a/images/Generic_KAFKA_Producer_Picture4.svg b/connector/images/Generic_KAFKA_Producer_Picture4.svg similarity index 100% rename from images/Generic_KAFKA_Producer_Picture4.svg rename to connector/images/Generic_KAFKA_Producer_Picture4.svg diff --git a/images/Generic_KAFKA_Producer_row.svg b/connector/images/Generic_KAFKA_Producer_row.svg similarity index 100% rename from images/Generic_KAFKA_Producer_row.svg rename to connector/images/Generic_KAFKA_Producer_row.svg diff --git a/images/Generic_KAFKA_Producer_svg1.png b/connector/images/Generic_KAFKA_Producer_svg1.png similarity index 100% rename from images/Generic_KAFKA_Producer_svg1.png rename to connector/images/Generic_KAFKA_Producer_svg1.png diff --git a/images/Generic_Matrix_Virtualization_Concat.png b/connector/images/Generic_Matrix_Virtualization_Concat.png similarity index 100% rename from images/Generic_Matrix_Virtualization_Concat.png rename to connector/images/Generic_Matrix_Virtualization_Concat.png diff --git a/images/Generic_Matrix_Virtualization_DualStream.png b/connector/images/Generic_Matrix_Virtualization_DualStream.png similarity index 100% rename from images/Generic_Matrix_Virtualization_DualStream.png rename to connector/images/Generic_Matrix_Virtualization_DualStream.png diff --git a/images/Generic_Matrix_Virtualization_Overview.png b/connector/images/Generic_Matrix_Virtualization_Overview.png similarity index 100% rename from images/Generic_Matrix_Virtualization_Overview.png rename to connector/images/Generic_Matrix_Virtualization_Overview.png diff --git a/images/Generic_Matrix_Virtualization_TIELines.png b/connector/images/Generic_Matrix_Virtualization_TIELines.png similarity index 100% rename from images/Generic_Matrix_Virtualization_TIELines.png rename to connector/images/Generic_Matrix_Virtualization_TIELines.png diff --git a/images/Generic_OPC_Data_Access_Access_Permission.png b/connector/images/Generic_OPC_Data_Access_Access_Permission.png similarity index 100% rename from images/Generic_OPC_Data_Access_Access_Permission.png rename to connector/images/Generic_OPC_Data_Access_Access_Permission.png diff --git a/images/Generic_OPC_Data_Access_Access_Permission_Permissions.png b/connector/images/Generic_OPC_Data_Access_Access_Permission_Permissions.png similarity index 100% rename from images/Generic_OPC_Data_Access_Access_Permission_Permissions.png rename to connector/images/Generic_OPC_Data_Access_Access_Permission_Permissions.png diff --git a/images/Generic_OPC_Data_Access_Client_OPCInbound.png b/connector/images/Generic_OPC_Data_Access_Client_OPCInbound.png similarity index 100% rename from images/Generic_OPC_Data_Access_Client_OPCInbound.png rename to connector/images/Generic_OPC_Data_Access_Client_OPCInbound.png diff --git a/images/Generic_OPC_Data_Access_Client_OPCOutbound.png b/connector/images/Generic_OPC_Data_Access_Client_OPCOutbound.png similarity index 100% rename from images/Generic_OPC_Data_Access_Client_OPCOutbound.png rename to connector/images/Generic_OPC_Data_Access_Client_OPCOutbound.png diff --git a/images/Generic_OPC_Data_Access_Default_Properties.png b/connector/images/Generic_OPC_Data_Access_Default_Properties.png similarity index 100% rename from images/Generic_OPC_Data_Access_Default_Properties.png rename to connector/images/Generic_OPC_Data_Access_Default_Properties.png diff --git a/images/Generic_OPC_Data_Access_Identity_Example.png b/connector/images/Generic_OPC_Data_Access_Identity_Example.png similarity index 100% rename from images/Generic_OPC_Data_Access_Identity_Example.png rename to connector/images/Generic_OPC_Data_Access_Identity_Example.png diff --git a/images/Generic_OPC_Data_Access_Launch_and_Activation_Permission.png b/connector/images/Generic_OPC_Data_Access_Launch_and_Activation_Permission.png similarity index 100% rename from images/Generic_OPC_Data_Access_Launch_and_Activation_Permission.png rename to connector/images/Generic_OPC_Data_Access_Launch_and_Activation_Permission.png diff --git a/images/Generic_OPC_Data_Access_Launch_and_Activation_Permissions.png b/connector/images/Generic_OPC_Data_Access_Launch_and_Activation_Permissions.png similarity index 100% rename from images/Generic_OPC_Data_Access_Launch_and_Activation_Permissions.png rename to connector/images/Generic_OPC_Data_Access_Launch_and_Activation_Permissions.png diff --git a/images/Generic_OPC_Data_Access_Server_OPCInbounds.png b/connector/images/Generic_OPC_Data_Access_Server_OPCInbounds.png similarity index 100% rename from images/Generic_OPC_Data_Access_Server_OPCInbounds.png rename to connector/images/Generic_OPC_Data_Access_Server_OPCInbounds.png diff --git a/images/Generic_OPC_Data_Access_Server_OPCOutbound.png b/connector/images/Generic_OPC_Data_Access_Server_OPCOutbound.png similarity index 100% rename from images/Generic_OPC_Data_Access_Server_OPCOutbound.png rename to connector/images/Generic_OPC_Data_Access_Server_OPCOutbound.png diff --git a/images/Generic_Ping_example.png b/connector/images/Generic_Ping_example.png similarity index 100% rename from images/Generic_Ping_example.png rename to connector/images/Generic_Ping_example.png diff --git a/images/Generic_Ping_example2.png b/connector/images/Generic_Ping_example2.png similarity index 100% rename from images/Generic_Ping_example2.png rename to connector/images/Generic_Ping_example2.png diff --git a/images/Generic_Ping_ping_sequence.jpg b/connector/images/Generic_Ping_ping_sequence.jpg similarity index 100% rename from images/Generic_Ping_ping_sequence.jpg rename to connector/images/Generic_Ping_ping_sequence.jpg diff --git a/images/Grass_Valley_Trinix_Encore_configuration.png b/connector/images/Grass_Valley_Trinix_Encore_configuration.png similarity index 100% rename from images/Grass_Valley_Trinix_Encore_configuration.png rename to connector/images/Grass_Valley_Trinix_Encore_configuration.png diff --git a/images/Grass_Valley_Trinix_Encore_configuration_flags.png b/connector/images/Grass_Valley_Trinix_Encore_configuration_flags.png similarity index 100% rename from images/Grass_Valley_Trinix_Encore_configuration_flags.png rename to connector/images/Grass_Valley_Trinix_Encore_configuration_flags.png diff --git a/images/IEC_60870_5-104_Capture.GIF b/connector/images/IEC_60870_5-104_Capture.GIF similarity index 100% rename from images/IEC_60870_5-104_Capture.GIF rename to connector/images/IEC_60870_5-104_Capture.GIF diff --git a/images/Kubernetes_Manager_2019-03-08_13_14_47-Window.png b/connector/images/Kubernetes_Manager_2019-03-08_13_14_47-Window.png similarity index 100% rename from images/Kubernetes_Manager_2019-03-08_13_14_47-Window.png rename to connector/images/Kubernetes_Manager_2019-03-08_13_14_47-Window.png diff --git a/images/Kubernetes_Manager_kubernetesManagerSetupV1.2.1.x.png b/connector/images/Kubernetes_Manager_kubernetesManagerSetupV1.2.1.x.png similarity index 100% rename from images/Kubernetes_Manager_kubernetesManagerSetupV1.2.1.x.png rename to connector/images/Kubernetes_Manager_kubernetesManagerSetupV1.2.1.x.png diff --git a/images/Miranda_Imagestore_750_MirandaImagestore750.png b/connector/images/Miranda_Imagestore_750_MirandaImagestore750.png similarity index 100% rename from images/Miranda_Imagestore_750_MirandaImagestore750.png rename to connector/images/Miranda_Imagestore_750_MirandaImagestore750.png diff --git a/images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png b/connector/images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png similarity index 100% rename from images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png rename to connector/images/Miranda_Kaleido_IP_X310_2022-07-05_15_26_05-Clipboard.png diff --git a/images/Miranda_Kaleido_IP_X320_Example_Excel_Sheet_Kaleido.png b/connector/images/Miranda_Kaleido_IP_X320_Example_Excel_Sheet_Kaleido.png similarity index 100% rename from images/Miranda_Kaleido_IP_X320_Example_Excel_Sheet_Kaleido.png rename to connector/images/Miranda_Kaleido_IP_X320_Example_Excel_Sheet_Kaleido.png diff --git a/images/Paneda_DAB_Monitor_Orchestration_image.png b/connector/images/Paneda_DAB_Monitor_Orchestration_image.png similarity index 100% rename from images/Paneda_DAB_Monitor_Orchestration_image.png rename to connector/images/Paneda_DAB_Monitor_Orchestration_image.png diff --git a/images/Paneda_Mux_Orchestration_image.png b/connector/images/Paneda_Mux_Orchestration_image.png similarity index 100% rename from images/Paneda_Mux_Orchestration_image.png rename to connector/images/Paneda_Mux_Orchestration_image.png diff --git a/images/SCTE_UPS_Batteries_DVE.jpg b/connector/images/SCTE_UPS_Batteries_DVE.jpg similarity index 100% rename from images/SCTE_UPS_Batteries_DVE.jpg rename to connector/images/SCTE_UPS_Batteries_DVE.jpg diff --git a/images/SCTE_UPS_Collector_Add-Update_Device.jpg b/connector/images/SCTE_UPS_Collector_Add-Update_Device.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Add-Update_Device.jpg rename to connector/images/SCTE_UPS_Collector_Add-Update_Device.jpg diff --git a/images/SCTE_UPS_Collector_Add_New_Device.jpg b/connector/images/SCTE_UPS_Collector_Add_New_Device.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Add_New_Device.jpg rename to connector/images/SCTE_UPS_Collector_Add_New_Device.jpg diff --git a/images/SCTE_UPS_Collector_Advaned_configuration.jpg b/connector/images/SCTE_UPS_Collector_Advaned_configuration.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Advaned_configuration.jpg rename to connector/images/SCTE_UPS_Collector_Advaned_configuration.jpg diff --git a/images/SCTE_UPS_Collector_Batteries.jpg b/connector/images/SCTE_UPS_Collector_Batteries.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Batteries.jpg rename to connector/images/SCTE_UPS_Collector_Batteries.jpg diff --git a/images/SCTE_UPS_Collector_DVE_Properties.jpg b/connector/images/SCTE_UPS_Collector_DVE_Properties.jpg similarity index 100% rename from images/SCTE_UPS_Collector_DVE_Properties.jpg rename to connector/images/SCTE_UPS_Collector_DVE_Properties.jpg diff --git a/images/SCTE_UPS_Collector_Delete_Devices.jpg b/connector/images/SCTE_UPS_Collector_Delete_Devices.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Delete_Devices.jpg rename to connector/images/SCTE_UPS_Collector_Delete_Devices.jpg diff --git a/images/SCTE_UPS_Collector_Export_Devices.jpg b/connector/images/SCTE_UPS_Collector_Export_Devices.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Export_Devices.jpg rename to connector/images/SCTE_UPS_Collector_Export_Devices.jpg diff --git a/images/SCTE_UPS_Collector_Export_Properties.jpg b/connector/images/SCTE_UPS_Collector_Export_Properties.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Export_Properties.jpg rename to connector/images/SCTE_UPS_Collector_Export_Properties.jpg diff --git a/images/SCTE_UPS_Collector_Geocoding.png b/connector/images/SCTE_UPS_Collector_Geocoding.png similarity index 100% rename from images/SCTE_UPS_Collector_Geocoding.png rename to connector/images/SCTE_UPS_Collector_Geocoding.png diff --git a/images/SCTE_UPS_Collector_Group_Config.jpg b/connector/images/SCTE_UPS_Collector_Group_Config.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Group_Config.jpg rename to connector/images/SCTE_UPS_Collector_Group_Config.jpg diff --git a/images/SCTE_UPS_Collector_History.jpg b/connector/images/SCTE_UPS_Collector_History.jpg similarity index 100% rename from images/SCTE_UPS_Collector_History.jpg rename to connector/images/SCTE_UPS_Collector_History.jpg diff --git a/images/SCTE_UPS_Collector_Import_Properties.jpg b/connector/images/SCTE_UPS_Collector_Import_Properties.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Import_Properties.jpg rename to connector/images/SCTE_UPS_Collector_Import_Properties.jpg diff --git a/images/SCTE_UPS_Collector_Input_Failure.jpg b/connector/images/SCTE_UPS_Collector_Input_Failure.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Input_Failure.jpg rename to connector/images/SCTE_UPS_Collector_Input_Failure.jpg diff --git a/images/SCTE_UPS_Collector_Output.jpg b/connector/images/SCTE_UPS_Collector_Output.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Output.jpg rename to connector/images/SCTE_UPS_Collector_Output.jpg diff --git a/images/SCTE_UPS_Collector_Properties.jpg b/connector/images/SCTE_UPS_Collector_Properties.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Properties.jpg rename to connector/images/SCTE_UPS_Collector_Properties.jpg diff --git a/images/SCTE_UPS_Collector_Property_Table.jpg b/connector/images/SCTE_UPS_Collector_Property_Table.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Property_Table.jpg rename to connector/images/SCTE_UPS_Collector_Property_Table.jpg diff --git a/images/SCTE_UPS_Collector_Provioning_Update.jpg b/connector/images/SCTE_UPS_Collector_Provioning_Update.jpg similarity index 100% rename from images/SCTE_UPS_Collector_Provioning_Update.jpg rename to connector/images/SCTE_UPS_Collector_Provioning_Update.jpg diff --git a/images/SCTE_UPS_Collector_System_Overview.png b/connector/images/SCTE_UPS_Collector_System_Overview.png similarity index 100% rename from images/SCTE_UPS_Collector_System_Overview.png rename to connector/images/SCTE_UPS_Collector_System_Overview.png diff --git a/images/SCTE_UPS_Export_Property_DVE.jpg b/connector/images/SCTE_UPS_Export_Property_DVE.jpg similarity index 100% rename from images/SCTE_UPS_Export_Property_DVE.jpg rename to connector/images/SCTE_UPS_Export_Property_DVE.jpg diff --git a/images/SCTE_UPS_General.jpg b/connector/images/SCTE_UPS_General.jpg similarity index 100% rename from images/SCTE_UPS_General.jpg rename to connector/images/SCTE_UPS_General.jpg diff --git a/images/SCTE_UPS_History_DVE.jpg b/connector/images/SCTE_UPS_History_DVE.jpg similarity index 100% rename from images/SCTE_UPS_History_DVE.jpg rename to connector/images/SCTE_UPS_History_DVE.jpg diff --git a/images/SCTE_UPS_Import_Property_DVE.jpg b/connector/images/SCTE_UPS_Import_Property_DVE.jpg similarity index 100% rename from images/SCTE_UPS_Import_Property_DVE.jpg rename to connector/images/SCTE_UPS_Import_Property_DVE.jpg diff --git a/images/SCTE_UPS_Input_Failure_DVE.jpg b/connector/images/SCTE_UPS_Input_Failure_DVE.jpg similarity index 100% rename from images/SCTE_UPS_Input_Failure_DVE.jpg rename to connector/images/SCTE_UPS_Input_Failure_DVE.jpg diff --git a/images/SCTE_UPS_Main_2.jpg b/connector/images/SCTE_UPS_Main_2.jpg similarity index 100% rename from images/SCTE_UPS_Main_2.jpg rename to connector/images/SCTE_UPS_Main_2.jpg diff --git a/images/SCTE_UPS_Manager_Alarm_Table.jpg b/connector/images/SCTE_UPS_Manager_Alarm_Table.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Alarm_Table.jpg rename to connector/images/SCTE_UPS_Manager_Alarm_Table.jpg diff --git a/images/SCTE_UPS_Manager_Alarm_Template_Config.jpg b/connector/images/SCTE_UPS_Manager_Alarm_Template_Config.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Alarm_Template_Config.jpg rename to connector/images/SCTE_UPS_Manager_Alarm_Template_Config.jpg diff --git a/images/SCTE_UPS_Manager_Collector_Table.jpg b/connector/images/SCTE_UPS_Manager_Collector_Table.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Collector_Table.jpg rename to connector/images/SCTE_UPS_Manager_Collector_Table.jpg diff --git a/images/SCTE_UPS_Manager_Create_Test_Manager.jpg b/connector/images/SCTE_UPS_Manager_Create_Test_Manager.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Create_Test_Manager.jpg rename to connector/images/SCTE_UPS_Manager_Create_Test_Manager.jpg diff --git a/images/SCTE_UPS_Manager_Detected_devices.jpg b/connector/images/SCTE_UPS_Manager_Detected_devices.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Detected_devices.jpg rename to connector/images/SCTE_UPS_Manager_Detected_devices.jpg diff --git a/images/SCTE_UPS_Manager_New_Provisioned_Devices2.jpg b/connector/images/SCTE_UPS_Manager_New_Provisioned_Devices2.jpg similarity index 100% rename from images/SCTE_UPS_Manager_New_Provisioned_Devices2.jpg rename to connector/images/SCTE_UPS_Manager_New_Provisioned_Devices2.jpg diff --git a/images/SCTE_UPS_Manager_ONENOTE_kCxlJ0OyV5.png b/connector/images/SCTE_UPS_Manager_ONENOTE_kCxlJ0OyV5.png similarity index 100% rename from images/SCTE_UPS_Manager_ONENOTE_kCxlJ0OyV5.png rename to connector/images/SCTE_UPS_Manager_ONENOTE_kCxlJ0OyV5.png diff --git a/images/SCTE_UPS_Manager_Provision_Device.jpg b/connector/images/SCTE_UPS_Manager_Provision_Device.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Provision_Device.jpg rename to connector/images/SCTE_UPS_Manager_Provision_Device.jpg diff --git a/images/SCTE_UPS_Manager_Scheduled_Tests.jpg b/connector/images/SCTE_UPS_Manager_Scheduled_Tests.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Scheduled_Tests.jpg rename to connector/images/SCTE_UPS_Manager_Scheduled_Tests.jpg diff --git a/images/SCTE_UPS_Manager_Traps.jpg b/connector/images/SCTE_UPS_Manager_Traps.jpg similarity index 100% rename from images/SCTE_UPS_Manager_Traps.jpg rename to connector/images/SCTE_UPS_Manager_Traps.jpg diff --git a/images/SCTE_UPS_Modem.jpg b/connector/images/SCTE_UPS_Modem.jpg similarity index 100% rename from images/SCTE_UPS_Modem.jpg rename to connector/images/SCTE_UPS_Modem.jpg diff --git a/images/SCTE_UPS_New_test.jpg b/connector/images/SCTE_UPS_New_test.jpg similarity index 100% rename from images/SCTE_UPS_New_test.jpg rename to connector/images/SCTE_UPS_New_test.jpg diff --git a/images/SCTE_UPS_Output_DVE.jpg b/connector/images/SCTE_UPS_Output_DVE.jpg similarity index 100% rename from images/SCTE_UPS_Output_DVE.jpg rename to connector/images/SCTE_UPS_Output_DVE.jpg diff --git a/images/SCTE_UPS_Schedule_Tests.jpg b/connector/images/SCTE_UPS_Schedule_Tests.jpg similarity index 100% rename from images/SCTE_UPS_Schedule_Tests.jpg rename to connector/images/SCTE_UPS_Schedule_Tests.jpg diff --git a/images/SCTE_UPS_Test.jpg b/connector/images/SCTE_UPS_Test.jpg similarity index 100% rename from images/SCTE_UPS_Test.jpg rename to connector/images/SCTE_UPS_Test.jpg diff --git a/images/SCTE_UPS_Threshold_DVE.png b/connector/images/SCTE_UPS_Threshold_DVE.png similarity index 100% rename from images/SCTE_UPS_Threshold_DVE.png rename to connector/images/SCTE_UPS_Threshold_DVE.png diff --git a/images/ScheduAll_Manager_ScheduAll_Structure.png b/connector/images/ScheduAll_Manager_ScheduAll_Structure.png similarity index 100% rename from images/ScheduAll_Manager_ScheduAll_Structure.png rename to connector/images/ScheduAll_Manager_ScheduAll_Structure.png diff --git a/images/Skyline_Cassandra_Validator_failover.png b/connector/images/Skyline_Cassandra_Validator_failover.png similarity index 100% rename from images/Skyline_Cassandra_Validator_failover.png rename to connector/images/Skyline_Cassandra_Validator_failover.png diff --git a/images/Skyline_Cassandra_Validator_validator_error.png b/connector/images/Skyline_Cassandra_Validator_validator_error.png similarity index 100% rename from images/Skyline_Cassandra_Validator_validator_error.png rename to connector/images/Skyline_Cassandra_Validator_validator_error.png diff --git a/images/Skyline_ICMP_Platform_Manager_Captura_de_pantalla_2021-10-19_174320.png b/connector/images/Skyline_ICMP_Platform_Manager_Captura_de_pantalla_2021-10-19_174320.png similarity index 100% rename from images/Skyline_ICMP_Platform_Manager_Captura_de_pantalla_2021-10-19_174320.png rename to connector/images/Skyline_ICMP_Platform_Manager_Captura_de_pantalla_2021-10-19_174320.png diff --git a/images/Skyline_IP_Network_Manager_IPNetworkManager_Flow.png b/connector/images/Skyline_IP_Network_Manager_IPNetworkManager_Flow.png similarity index 100% rename from images/Skyline_IP_Network_Manager_IPNetworkManager_Flow.png rename to connector/images/Skyline_IP_Network_Manager_IPNetworkManager_Flow.png diff --git a/images/Skyline_IP_Network_Manager_IPNetworkManager_IconServerLinked.png b/connector/images/Skyline_IP_Network_Manager_IPNetworkManager_IconServerLinked.png similarity index 100% rename from images/Skyline_IP_Network_Manager_IPNetworkManager_IconServerLinked.png rename to connector/images/Skyline_IP_Network_Manager_IPNetworkManager_IconServerLinked.png diff --git a/images/Slack_Messaging_Conversations.jpg b/connector/images/Slack_Messaging_Conversations.jpg similarity index 100% rename from images/Slack_Messaging_Conversations.jpg rename to connector/images/Slack_Messaging_Conversations.jpg diff --git a/images/Slack_Messaging_Scripts.jpg b/connector/images/Slack_Messaging_Scripts.jpg similarity index 100% rename from images/Slack_Messaging_Scripts.jpg rename to connector/images/Slack_Messaging_Scripts.jpg diff --git a/images/Slack_Messaging_Users.jpg b/connector/images/Slack_Messaging_Users.jpg similarity index 100% rename from images/Slack_Messaging_Users.jpg rename to connector/images/Slack_Messaging_Users.jpg diff --git a/images/Slack_Messaging_authentication.jpg b/connector/images/Slack_Messaging_authentication.jpg similarity index 100% rename from images/Slack_Messaging_authentication.jpg rename to connector/images/Slack_Messaging_authentication.jpg diff --git a/images/Sunrise_UPC_NetCracker_Interface_Capture2.JPG b/connector/images/Sunrise_UPC_NetCracker_Interface_Capture2.JPG similarity index 100% rename from images/Sunrise_UPC_NetCracker_Interface_Capture2.JPG rename to connector/images/Sunrise_UPC_NetCracker_Interface_Capture2.JPG diff --git a/images/Sunrise_UPC_RPD_Jobs_Capture.JPG b/connector/images/Sunrise_UPC_RPD_Jobs_Capture.JPG similarity index 100% rename from images/Sunrise_UPC_RPD_Jobs_Capture.JPG rename to connector/images/Sunrise_UPC_RPD_Jobs_Capture.JPG diff --git a/images/Tektronix_SignalVu_01_Configuration.png b/connector/images/Tektronix_SignalVu_01_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_01_Configuration.png rename to connector/images/Tektronix_SignalVu_01_Configuration.png diff --git a/images/Tektronix_SignalVu_02_Configuration.png b/connector/images/Tektronix_SignalVu_02_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_02_Configuration.png rename to connector/images/Tektronix_SignalVu_02_Configuration.png diff --git a/images/Tektronix_SignalVu_03_Configuration.png b/connector/images/Tektronix_SignalVu_03_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_03_Configuration.png rename to connector/images/Tektronix_SignalVu_03_Configuration.png diff --git a/images/Tektronix_SignalVu_04_Configuration.png b/connector/images/Tektronix_SignalVu_04_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_04_Configuration.png rename to connector/images/Tektronix_SignalVu_04_Configuration.png diff --git a/images/Tektronix_SignalVu_04b_Configuration.png b/connector/images/Tektronix_SignalVu_04b_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_04b_Configuration.png rename to connector/images/Tektronix_SignalVu_04b_Configuration.png diff --git a/images/Tektronix_SignalVu_05_Configuration.png b/connector/images/Tektronix_SignalVu_05_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_05_Configuration.png rename to connector/images/Tektronix_SignalVu_05_Configuration.png diff --git a/images/Tektronix_SignalVu_06_Configuration.png b/connector/images/Tektronix_SignalVu_06_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_06_Configuration.png rename to connector/images/Tektronix_SignalVu_06_Configuration.png diff --git a/images/Tektronix_SignalVu_07_Configuration.png b/connector/images/Tektronix_SignalVu_07_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_07_Configuration.png rename to connector/images/Tektronix_SignalVu_07_Configuration.png diff --git a/images/Tektronix_SignalVu_09_Configuration.png b/connector/images/Tektronix_SignalVu_09_Configuration.png similarity index 100% rename from images/Tektronix_SignalVu_09_Configuration.png rename to connector/images/Tektronix_SignalVu_09_Configuration.png diff --git a/images/Tektronix_SignalVu_TekVisa_AppList.png b/connector/images/Tektronix_SignalVu_TekVisa_AppList.png similarity index 100% rename from images/Tektronix_SignalVu_TekVisa_AppList.png rename to connector/images/Tektronix_SignalVu_TekVisa_AppList.png diff --git a/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-19_174320.png b/connector/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-19_174320.png similarity index 100% rename from images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-19_174320.png rename to connector/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-19_174320.png diff --git a/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-20_134522.png b/connector/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-20_134522.png similarity index 100% rename from images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-20_134522.png rename to connector/images/Telefonica_UDO_Ticketing_System_Captura_de_pantalla_2021-10-20_134522.png diff --git a/images/Telefonica_UDO_Ticketing_System_Correlation.jpg b/connector/images/Telefonica_UDO_Ticketing_System_Correlation.jpg similarity index 100% rename from images/Telefonica_UDO_Ticketing_System_Correlation.jpg rename to connector/images/Telefonica_UDO_Ticketing_System_Correlation.jpg diff --git a/images/Upload.PNG b/connector/images/Upload.PNG similarity index 100% rename from images/Upload.PNG rename to connector/images/Upload.PNG diff --git a/images/Vodafone_Service_Notes_add.png b/connector/images/Vodafone_Service_Notes_add.png similarity index 100% rename from images/Vodafone_Service_Notes_add.png rename to connector/images/Vodafone_Service_Notes_add.png diff --git a/images/Vodafone_Service_Notes_edit.png b/connector/images/Vodafone_Service_Notes_edit.png similarity index 100% rename from images/Vodafone_Service_Notes_edit.png rename to connector/images/Vodafone_Service_Notes_edit.png diff --git a/images/Vodafone_Service_Notes_notes.png b/connector/images/Vodafone_Service_Notes_notes.png similarity index 100% rename from images/Vodafone_Service_Notes_notes.png rename to connector/images/Vodafone_Service_Notes_notes.png diff --git a/images/WISI_Optopus_Untitled.png b/connector/images/WISI_Optopus_Untitled.png similarity index 100% rename from images/WISI_Optopus_Untitled.png rename to connector/images/WISI_Optopus_Untitled.png diff --git a/docfx.json b/docfx.json index ee0f435b..07d6f0d3 100644 --- a/docfx.json +++ b/docfx.json @@ -17,7 +17,7 @@ "resource": [ { "files": [ - "images/**" + "connector/images/**" ] } ],