Configuration Of Weasis PACS Connector Files

[HM]

Hi

I am trying to install and configure Weasis 2.6.1 and Weasis PACS Connector 6.1.0 with conquest PACS Server. Everything is fine but i am facing some problems in the configuration of weasis pacs connector file. There are two files db-dcm4chee.properties and dicom-dcm4chee.properties.

In db-dcm4chee.properties, should i replace this portion with available table names

# Mandatory fields

arc.db.query.patientid=pat_id

arc.db.query.patientbirthdate=pat_birthdate

arc.db.query.patientbirthdate.type=VARCHAR2

arc.db.query.patientbirthdate.format=yyyyMMdd

arc.db.query.studyinstanceuid=study_iuid

arc.db.query.seriesinstanceuid=series_iuid

arc.db.query.sopinstanceuid=sop_iuid

And these with fields on which we run the search

# Patient

arc.db.query.setpatientname=pat_name

#arc.db.query.patientbirthtime=

arc.db.query.patientsex=pat_sex

And replace with SQL Query 

# SQL commands

arc.db.query.select=select pa.pat_id, pa.pat_name, pa.pat_sex, pa.pat_birthdate, st.study_iuid, st.study_id, st.study_datetime, st.accession_no, st.ref_physician, st.study_desc, se.series_iuid, se.modality, se.series_desc, se.series_no, im.sop_iuid, im.inst_no from instance im, series se, study st, patient pa

And in dicom-dcm4chee.properties

I updated this portion with my configuration

# AET, hostname and port of the archive (Mandatory properties)

arc.aet=DCM4CHEE

arc.host=localhost

arc.port=11112

And replace this portion with conquest wado

##### Base URL of the WADO server (Mandatory property)

##### For dcm4chee-arc-light 5: arc.wado.url=${server.base.url}/dcm4chee-arc/aets/DCM4CHEE/wado

arc.wado.url=${server.base.url}/wado

My question is that do i need to update both files as i have no idea about the queries and fields on which on queries are made or if i simply update the dicom-dcm4chee.properties the connector file will work for me.

Please guide.

--HM

[Nicolas Roduit]

It is recommended to use the DICOM connection to be independent of the PACS. You should have a look at the end of the file weasis-pacs-connector.properties  to see which configuration has been activated. Only one is necessary.

[HM]

Thanks for the link. But my question is if i want to use single archive  then i have to update this line arc.config.list=dicom-dcm4chee.properties. In that case what modification i need to make in the subject file.

Please guide.

--HM

[Nicolas Roduit]

Please ask a specific question if you expect an answer. I cannot determine which configuration you need.

[HM]

My question is that :: I had checked the link shared by you. But i cannot understand where should i configure the conquest PACS Server. So, that i can view images in Weasis.

--HM

[Nicolas Roduit]

I know there are people using the latest weasis-pacs-connector configuration with conquest. I will add the procedure here if somebody can provide it.

[HM]

Okie... I will do the testing with latest connector and please do update for conquest ..

[HM]

hi

I tried to connect the latest Weasis 3.0.3 with Conquest PACS server using the latest Weasis PACS Connector 6.1.3. But i failed to load the images whereas in older version 2.0.6 i was able to load and view images.

Attached is my configuration files for your review.

--HM

[Nicolas Roduit]

I have no experience with Conquest. The configuration you mentioned is made for dcm4chee. So please referrer to the way of configuring Weasis with conquest. If I understand well they don't use weasis-pacs-connector.

[HM]

Thanks for your prompt reply. Sorry i don't agree with your statement "If I understand well they don't use weasis-pacs-connector." As, in older version i update the PACS Connector file then i was able to view images. Othewrwise i get error.

--HM

[José Camacho]

I'm using Conquest and an our proprietary solution LyriaPACS with new weasis-connector. You need to do:

1) configure this part:

# AET, hostname and port of the archive (Mandatory properties)

arc.aet=DCM4CHEE ##HERE THE CONQUEST AET (ex: CONQUEST)

arc.host=localhost ##HERE THE IP OF CONQUEST SERVER (ex: 10.0.165.100)

arc.port=11112 ##HERE  THE PORT FOR CONQUEST REQUEST (ex:104)

########################

2) configure the wado url on dicom-dcm4chee.proprerties:

##### Base URL of the WADO server (Mandatory property)

##### For dcm4chee-arc-light 5: arc.wado.url=${server.base.url}/dcm4chee-arc/aets/DCM4CHEE/wado

arc.wado.url=${server.base.url}/lyriaViewer-web/wado ###(HERE is my solution LyriaViewer, put yours)

Other thing I had problems: 

1) the path of tomcat directory.  On windows was necessary installing on c:/tomcat8 without spacing caracters.

2) Java version. You need Java8 or higher 

Livre de vírus. www.avast.com.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

Livre de vírus. www.avast.com.

[wuwen...@gmail.com]

I am using weasis-pacs-connector to connect Weasis to dcm4chee-arc-light-5.7.2:

  -  weasis-pacs-connector/viewer?studyUID=1.3.6.1.4.1.5962.1.2.2.20031208063649.855;

  -  execute generated JNLP file 

 I am use dcm4chee-arc-light-5.15.0 and  weasis-pacs-connector 7.0

What am I missing?

Thanks in advance!

[HM]

On Tuesday, 9 January 2018 23:05:33 UTC+5, HM wrote: