ORVE WS (Dynamic) (13) Defiining property files and strategy

0. Introduction

In order to customize an application, it is quite interesting having a property file.

In this post, the strategy to retrieve records from ORVE is defined

1. Property file

Here is the property file


 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
#========================================================================================
#  1. TERALCO PROPERTIES 
#========================================================================================
persistence.unit.gexflow=PostgressGexflowJPAPU

#Teralco Properties
teralco.wsdl=http://TERALCO_SERVER_IP/gexflow/ws/Registro_v2.0?wsdl
teralco.registro.entrada.operation=registrarAsientoEntrada
teralco.registro.entrada.input.class=gexflow.reges.RegistrarAsientoEntrada
teralco.registro.entrada.output.class=gexflow.reges.RegistroEntradaWSV2JB
teralco.destinosinternos.class=gexflow.reges.DestinoRegistroEntradaWSJB

teralco.registro.entrada.adjuntar.documento.operation=adjuntarDocumentoARegistro
teralco.registro.entrada.adjuntar.documento.input.class=gexflow.reges.AdjuntarDocumentoARegistro
teralco.registro.entrada.adjuntar.documento.output.class=gexflow.reges.AdjuntarDocumentoARegistroResponse


#----- REAL ------
teralco.id.entidad=1000
teralco.cod.unidad.registral=GENERAL
teralco.cod.oficina=OFXX
teralco.usuario=myTeralcoUser
teralco.id.tipus.document=98  



#========================================================================================
#  3. ORVE SPECIFIC PROPERTIES
#
#  a. for production -> orve.mode=orve
#  b. for demo       -> orve.mode=demoorve 
# 
#                                           https://ssweb.seap.minhap.es/orve/WSExportacion.wsdl
#  c. to construct the complete wsdl url -> orve.base + orve.mode + orve.wsdl
#========================================================================================
persistence.unit.orve=sicresh2


#orve.wsdl=https://ssweb.seap.minhap.es/orve/WSExportacion.wsdl

#DEMOORVE OR PRODUCTION
orve.username=myUser
orve.password=myPassword
orve.dir3.unidad=LAXXXXXXX
orve.dir3.oficina=OXXXXXXXX
orve.states=RPC,RC

orve.fictitious.nif=XXXXXXX
orve.fictitious.cp=99999             

#orve.mode=demoorve
orve.mode=orve

orve.base=https://ssweb.seap.minhap.es/
orve.wsdl=WSExportacion.wsdl

orve.security.class=Security
orve.filtros.identificadores.class=FiltrosIdentificadores

orve.obtener.identificadores.operation=obtenerIdentificadores
orve.obtener.registro.operation=obtenerRegistro

teralco.orve.clase.documento=ORVE
teralco.orve.cod.unidad.organizativa.remitente=AXXX

orve.log.file=/home/ximodante/ORVE/LOG/orve.log


All the data in red should be changed by the client of services. Take into account that both ORVE and Teralco web services are being used, so suitable data should be provided.

2. Strategy 



Comments

Post a Comment

Popular posts from this blog

ORVE WS (Dynamic) (4) Jackson XML mapper

0. Introduction I love Jackson parser as it is easy to use and can be used to with some data formats such as CSV ,  JSON , YAML and XML . Just define a wrapper and a class for marshalling/unmarshalling. Although JAXB is a standard, in the Java ecosystem exists many solutions. And my decision is to use Jackson. 1. Defining MAVEN dependencies To use Jackson XML it is required this dependency in Maven. Note that  ${jackson.version} represents a variable that contains preferably the latest Jackson version. 1 2 3 4 5 <dependency> <groupId> com.fasterxml.jackson.dataformat </groupId> <artifactId> jackson-dataformat-xml </artifactId> <version> ${jackson.version} </version> </dependency> But if you want to use CSV, JSON or YAML in the project, it is as easy as including these dependencies 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 <!-- Jackson for CSV --> <de...
Read more

ENI (1) ENI Document OR the Spanish Electronic Administration Mafia

Image
0.Introduction. Getting the "xsd" schemas 1. Obtaining the afirma.xsd 2. Managing the "xsd" schemas. Changing  schemalocation  property from the  xsd  tag 3. Generating classes from xsd schema 4. Modifying the classes to solve operational problems 0. Old version 1. Generating the classes 0.Introduction. Getting the "xsd" schemas To obtain the correct URLs of the schemas: 1.For the document: https://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e in this URL it is shown these schemas (click on the link and download the schemas): http://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e/documentoEni.xsd http://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e/metadatos/metadatosDocumentoEni.xsd http://administracionelectronica.gob.es/ENI/XSD/v1.0/documento-e/contenido/contenidoDocumentoEni.xsd http://administracionelectronica.gob.es/ENI/XSD/v1.0/firma/firmasEni.xsd 2. For the file (expediente) https://administracionelectronica.gob.es...
Read more

ORVE WS (Dynamic) (12) Defiining the control tables

0. Introduction Our goals are: Retrieving the INPUT records (Received from other administrations) Retrieving the OUTPUT records (Sent to other administrations) To retrieve any record the WS requires at least these parameters   1. State (Estado). For INPUT these are the available states: RPC : Received but confirmation pending RR : Received and rejected RC : Received and confirmed RREEN : Received and resent      For OUTPUT : PE : Pending delivery EPC : Sent but confirmation is pending ER : Sent but rejected EC : Sent and confirmed 2. Date from in " YYYY-MM-DD HH:MM:SS " format 3. Date to in the same format. The system knows who is our administration (Oficina or Office) 1. Additional tables or entities We need to have control of: "Ids" that can identify the records and if the records have been saved and passed to the Gexflow application (an application that controls our records). To get the "Ids", the WS operation...
Read more