Comments (6)
Did you try the build the package from the last commit?
There are several commits not published by me between 7.1.1 and 7.1.2. So I have to investigate.
I will try to make a new release next week.
from weasis-pacs-connector.
Please provide a description of the context and a reproducible use case. What are the errors.
baseUrl
is not a property and arc.wado.url
is the Base URL of the WADO server (for downloading image). Check the configuration instructions.
from weasis-pacs-connector.
Hello.
I mean. The same weasis-pacs-connector.properties
file, containing arc.config.list=arc1,arc2
, and the corresponding arc1
and arc2
configuration files, with 7.1.1 works, while with 7.1.2 it doesn't work.
arc1
configuration file contains
arc.wado.url=http://arc1:8080/wado
while arc2
contains
arc.wado.url=http://arc2:8080/wado
weasis-pacs-connector is installed on a third server (that is not arc1 or arc2).
If I invoke, for instance, https://server.example/weasis-pacs-connector/manifest?accessionNumber=123.456
In the resulting file (with 7.1.2) I obtain
<arcQuery arcId="1000" baseUrl="https://server.example/dcm4chee-arc/aets/DCM4CHEE/wado" requireOnlySOPInstanceUID="false" additionnalParameters="&transferSyntax=*" >
that is wrong.
While with 7.1.1 I correctly get
<arcQuery arcId="1000" baseUrl="http://arc1:8080/wado" requireOnlySOPInstanceUID="false" >
Like if: or the arc.wado.url=
in the properties file is not taken into account, or the files listed in arc.config.list=
are not taken into account.
Where can I grab possible error messages?
from weasis-pacs-connector.
Check the configuration instructions.
So the point could be this one?
This file named weasis-pacs-connector.properties and dicom-dcm4chee.properties must be placed in the classpath of the application:
...
In Tomcat just specify the directory in shared.loader property of /conf/catalina.properties
With 7.1.1, I placed these files in ${catalina.home}/lib
and it was working.
Now with 7.1.2 it doesn't take into account these files anymore.
from weasis-pacs-connector.
However, even defining the shared.loader
property in /conf/catalina.properties
, and placing weasis-pacs-connector.properties
and dicom-dcm4chee.properties
in there, these files are not taken into account.
from weasis-pacs-connector.
Well.
While deploying 7.1.1, in the Tomcat log I can see
2021-12-20 13:43:41,521 [06-8080-exec-12] INFO o.w.s.ManifestManager External weasis-pacs-connector configuration: file:/opt/apache-tomcat-8.5.38/shared/weasis-pacs-connector.properties
2021-12-20 13:43:41,526 [06-8080-exec-12] INFO o.w.s.ManifestManager Archive configuration: file:/opt/apache-tomcat-8.5.38/shared/pacs1-dcm4chee.properties
2021-12-20 13:43:41,526 [06-8080-exec-12] INFO o.w.s.ManifestManager Archive configuration: file:/opt/apache-tomcat-8.5.38/shared/pacs2-dcm4chee.properties
2021-12-20 13:43:41,526 [06-8080-exec-12] INFO o.w.s.ManifestManager Archive configuration: file:/opt/apache-tomcat-8.5.38/shared/pacs2-dcm4chee.properties
(In this case, /opt/apache-tomcat-8.5.38/shared/
is the directory defined in shared.loader
property of /conf/catalina.properties
).
While deploying 7.1.2 i see
2021-12-20 13:47:57,103 [06-8080-exec-34] INFO o.w.s.ManifestManager Path of weasis-pacs-connector configuration: file:/opt/apache-tomcat-8.5.38/webapps/weasis-pacs-connector/WEB-INF/classes/weasis-pacs-connector.properties
2021-12-20 13:47:57,108 [06-8080-exec-34] INFO o.w.s.ManifestManager Archive configuration: file:/opt/apache-tomcat-8.5.38/webapps/weasis-pacs-connector/WEB-INF/classes/dicom-dcm4chee-arc.properties
And the Tomcat instance/configuration is the same.
from weasis-pacs-connector.
Related Issues (20)
- Uploading manifest encoding issue
- Add weasis protocol (replacing Java Webstart)
- Allow to transmit an authorization in GetWeasisProtocol
- Update to weasis-dicom-tools 5.17.0
- Update to weasis-dicom-tools 5.17.1
- Fix issue when cbd is empty
- Fix java 11 issue by removing javax.xml.bind dependency
- Connecting Weasis to DICOMCloud HOT 3
- weasis clearcanvas HOT 4
- dcm4chee-arc-light 5.19.0-secured HOT 1
- integration with dcm4chee-arc v5.22.6 HOT 26
- open weasis
- Open weasis:// protocol on a machine different than that requested the URL HOT 1
- pacs-connector master branch jdk 1.8 and dcm4chee 2.18.3 HOT 1
- I met the issue 'The requested resource (/weasis-pacs-connector/viewer) is not available' when I try to open DICM files in dcm4che HOT 1
- Custom preset trouble.
- cdb-ext url crashes local native client on startup if not nullified HOT 1
- Using new PACS Connector
- Can't get ML manifest with dcm4chee-arc 5.31.2 + WildFly 29.0.1 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from weasis-pacs-connector.