which requires representing them on the NMOS layer which may be also helpful outside of ProAV environments. Physical interfaces used in the ProAV industry provide such tools for these purposes as EDID, InfoFrames etc. Operating in this environment requires automated or semi-automated approaches which signalize about incompatibility between components and configure them to achieve this compatibility if possible. One of ProAV features is focusing on end users which integrate hardware and software on their own with a priori unknown components. ProAV environments differ from broadcast ones. The document provides definitions and network topologies related to the architecture. These elements are used as the basis to construct UML sequence diagrams for both EDID processing and related IS-04 discovery and IS-05 connection management. The document provides a list of user stories followed by static architectural elements. This document presents an architecture for Sink Metadata Processing operating in an overall NMOS environment. But the activiti and camunda both had extend these element in a similar way.Ĭurrently, the WF Designer can only generate bpmn files that are executed on the activiti engine because the VFC uses the activiti engine.AMWA INFO-003 NMOS Sink Metadata Processing Architecture The reason is that the bpmn specification does not define elements other than flow control, such as form field, formProperty etc. There are some activiti extend elements start with prefix 'activiti:'. The input parameter definitions of the task. Map value is the header paramter name, such as ''application/json. Map key is the header paramter name, such as ' Accept'. The header paramters of the rest api associated to the rest task. Valid value as follow: get, post, put, delete ![]() The method of the rest api to be called while the activity be executed on the workflow engine. The path of the REST API relative to the API router exposed path. In the condition of access the REST API via MircoServiceBus, The workflow engine can query the URL of the REST API exposed through the MircoServiceBus by name and version. The microservcie version of the REST API. Only for the condition of access the REST API via MircoServiceBus. The Base URL of the REST API exposed through the API router.Ĭhoose between the 'url' field and ('name', 'version') filed. The body of the save request must be in a json format that specifies the metadata. If the Authorization header is missing, then an HTTP “401 Unauthorized” with ‘If “Authorization” header is received, but the client‘s authentication fails ( due to either unknown “username” or invalid “password” ) the “403 Forbidden” response code will be returned This string is then Base64 encoded to produce the encoded credential which is communicated in the header after the string “Authorization: Basic “. The username and password are formed into one string as “username: password”. Valid values are: “application/octet-stream” If this header with non-null value is not supplied the HTTP Request will be rejected with '400 Bad Syntax’ response code.ĭetermines the format of the body of the response. If it is not sent it will be automatically generated by SDC on request receipt.įor auditing purpose each component calling the SDC API should identify itself by sending its identity ( e.g. This user must also have a Designer role in SDCĪccording to the general ECOMP agreement the "X-ECOMP-RequestID" header with the transaction UUID should be published by ECOMP component calling an exposed by other ECOMP component API in order to make possible the transaction traceability across ECOMP. The value for this header must be the MD5 checksum over the whole json body Open the an existed workflow and navigate to the '(ZTE) WF Designer'.įor a new workflow, before it be opened, the catalog should create it first.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |