Service Directory Schema
There is a directory of the deployed CAs in the SICAS environments developed by RR, which can be viewed at the following link:
It is proposed to implement a new functionality for OpenESB Enterprise containing a services directory, which will facilitate knowledge of the CAs deployed in each environment and node.
Swagger will be used to design, build, document, and consume RESTful web services.
The goal is to support calls of this type and later translate a Swagger definition into a WSDL within the BPEL layer.
https://petstore.swagger.io/#/pet/uploadFile
OEESD-45bede474-1224-313c-a276-b172bf57fcf6System Jira
Syntax
Ecosystem is understood as: Intermediation, Training, and Guidance.
Environment is understood as: PRD, STG, FOR, DEV.
Node is understood as: one or more nodes for each environment.
The proposal, as a first version created by me, is the following. Please assess this schema:
<![CDATA[<?xml version="1.0" encoding="UTF-8"?>
<ecosistema xmlns="http://emprego.xunta.es/xpta/servicesDirectory"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://emprego.xunta.es/xpta/servicesDirectory file:/C:/Users/vico/Documents/Repo-OpenESB/Services%20Directory/servicesDirectory.xsd">
<ecosistemaName>Formacion</ecosistemaName>
<details>training ecosystem where services such as SIFO, SICAS, and DIPLOS are deployed and operational</details>
<state>ACTIVE</state>
<serviceAssembly>
<serviceAssemblyName>emphorlog-Mayordomo-ca</serviceAssemblyName>
<serviceAssemblyDescription>emphorlog-Mayordomo-ca-1.3.3-SNAPSHOT - Trace registration service - Validates and registers a request in the sending queue</serviceAssemblyDescription>
<state>Started</state>
<entornos>
<entornoName>PRD</entornoName>
<status>status0</status>
<nodo>
<nodoName>prd01</nodoName>
<version>1.3.1</version>
<status>Started</status>
</nodo>
<nodo>
<nodoName>prd02</nodoName>
<version>1.3.1</version>
<status>Started</status>
</nodo>
<connections>
<consumer>
<endpointName>emphorlog-MayordomoPort</endpointName>
<endpointName>PutPeticionPendientePortTypeRole_partnerRole</endpointName>
<endpointName>obtenerParametrosWSDLPortTypeRole_partnerRole</endpointName>
</consumer>
<provider>
<endpointName>emphorlogEsbWSRole_myRole</endpointName>
<endpointName>PutPeticionPendientePort</endpointName>
<endpointName>obtenerParametrosWSDLPortTypeRole_myRole</endpointName>
</provider>
</connections>
<serviceUnits>
<component>
<target>sun-http-binding</target>
<state>Started</state>
</component>
<component>
<target>sun-bpel-engine</target>
<state>Started</state>
</component>
<component>
<target>sun-jms-engine</target>
<state>Started</state>
</component>
</serviceUnits>
</entornos>
</serviceAssembly>
<serviceAssembly>
.....
</serviceAssembly>
</ecosistema>
]]>
Design:
