Can Weasis work with 2 IPs?

[Dr Lawrence M Fox]

I have DCM4CHEE configured on a Windows 2008 Server in a Linux Virtual Machine. The VM has 2 IP addresses: 192.168.x.x for LAN services and 10.0.x.x for VPN services.

Images work fine on the LAN, but when I try to view them on my VPN, Weasis fails. I am able to log into the JMX console using the 10.0.x.x VPN IP; I am able to log into the Web3 interface using that IP, but when I try to download the images, Weasis fails seemingly because it is trying to download the images from the LAN IP. How do I configure Weasis to recognize which IP I'm on?

Thanks.

[nicolas...@gmail.com]

The servlet configuration take the parameter ${server.base.url} that is the base url of the servlet request. For instance, "http://192.168.x.x:8080/weasis-pacs-connector/viewer.jnlp?patientID=9702672" will use the local address.

This base url is built by dcm4chee-web3. The problem is if you get in the portal with http://10.0.x.x:8080/dcm4chee-web3, the url of the viewer button should be http://10.0.x.x:8080/weasis-pacs-connector/viewer.jnlp?patientID=9702672, but in your case is http://192.168.x.x:8080/...  Is it what you get?

Did you try to restart dcm4chee and access first from http://10.0.x.x:8080/dcm4chee-web3.

I think the best would be to have only one web address.

[Dr Lawrence M Fox]

Thanks, nicolas, but that's disappointing news. You are correct--if I access dcm4chee from 10.0.x.x first, then weasis works with that network but not with the 192.168.x.x

Is there a viewer other than weasis which I can use for access both by LAN and by VPN?

[nicolas...@gmail.com]

The problem is not the viewer but the URL given by the dcm4chee portal. I will ask dcm4chee developers how this issue can be fixed.

[Dr Lawrence M Fox]

That would be wonderful. Thank you!

[Alvaro G. [andor]]

May this arise if I have an external access to Weasis, and also people
accessing with the internal IP?

I think a client just contacted me because of a similar problem...

El 12/02/13 15:06, nicolas...@gmail.com escribi�:

> The problem is not the viewer but the URL given by the dcm4chee
> portal. I will ask dcm4chee developers how this issue can be
> fixed.
>
> On Tuesday, February 12, 2013 2:11:27 PM UTC+1, Dr Lawrence M Fox
> wrote:
>
> Thanks, nicolas, but that's disappointing news. You are
> correct--if I access dcm4chee from 10.0.x.x first, then weasis
> works with that network but not with the 192.168.x.x Is there a
> viewer other than weasis which I can use for access both by LAN and
> by VPN?
>
>
> This base url is built by dcm4chee-web3. The problem is if you get
> in the portal with http://10.0.x.x:8080/dcm4chee-web3

> <http://10.0.x.x:8080/dcm4chee-web3>, the url of the viewer button

> should be
> http://10.0.x.x:8080/weasis-pacs-connector/viewer.jnlp?patientID=9702672
>
>

<http://10.0.x.x:8080/weasis-pacs-connector/viewer.jnlp?patientID=9702672>,

> but in your case is http://192.168.x.x:8080/.

> <http://192.168.x.x:8080/>.. Is it what you get?

>
>
>
> Did you try to restart dcm4chee and access first from
> http://10.0.x.x:8080/dcm4chee-web3

> <http://10.0.x.x:8080/dcm4chee-web3>.

>
> I think the best would be to have only one web address.
>
>

> -- 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
> http://groups.google.com/group/dcm4che?hl=en. For more options,
> visit https://groups.google.com/groups/opt_out.
>
>


--
Alvaro "Andor" Gonzalez
an...@pierdelacabeza.com
GnuPG KeyID 0xa1e486f0

[nicolas...@gmail.com]

Yes, the problem is not about external or internal IPs, but to have more than one IP to access to the portals.

Why not using only one hostname for internal and external access?

On Tuesday, February 19, 2013 12:16:30 PM UTC+1, andor wrote:

May this arise if I have an external access to Weasis, and also people
accessing with the internal IP?

I think a client just contacted me because of a similar problem...

El 12/02/13 15:06, nicolas...@gmail.com escribi�:

[fabrizzi...@msn.com]

i am having the same problem, how do you fix it? or what do you do to make it work?
REgards

Fs

[Dr Lawrence M Fox]

I was not able to fix it. I am now using the MySQL/Windows version of DCM4CHEE (instead of Linux) but I continue to have the same problem. I believe Nicolas said he was going to request an enhancement, but I do not know the status of that request.

Larry

[nicolas...@gmail.com]

 Unfortunately, I haven't received any reply for that issue.

The configuration of WebConfig in jmx-console let you enter a base URL for the WADO service, but you can only enter one URL. If you let the default value, it takes the base URL of the first call of the service (after starting dcm4chee).

If you really need to have two base URLs, you can use the local network address by default and redirect the external address to the local one with a reverse proxy or by making your own proxy component that redirect the jnlp and WADO requests.

To increase the security over the WEB, with the last release of weasis-pacs-connector, you can activate the parameters encryption (uncomment encrypt.key and change the value) in the configuration (see http://www.dcm4che.org/confluence/display/WEA/Installing+Weasis+in+DCM4CHEE). This will encrypt all parameters of the weasis-pacs-connector servlets.
In the configuration, you can also add specific http tags for WADO requests, which can be filtered by the proxy.

[nicolas...@gmail.com]

 I found an issue in the code of weasis-pacs-connector. I built a new version available here. The configuration must be (it is the default values):

weasis.base.url=${server.base.url}

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

Could you try it and tell me if it works.

[fabrizzi...@msn.com]

testing, thanks

Fs

El martes, 12 de febrero de 2013 00:16:41 UTC-5, Dr Lawrence M Fox escribió:

[Antonio Lazaro]

Hi everyone,

I think that the problem is because the way that weasis`s developers passed parameters to Jnlp was by "System.setProperty("server.base.url", baseURL);". As is knowed, System.setProperty causes a global change, so, I don't understood yet why, just the first get the value write, but I think, that it is a problem. Because if you have concorrence, you problably will have serious problems, working with global configurations. I'm trying to rewrite this code, but it's complicated, because I have no reference about the code. 

Someone has any better suggestion?

[nicolas...@gmail.com]

This issue has been fixed (see here) and a new version of weasis-pacs-connector is available here. The problem was that the dynamic property "server.base.url" was copy only in the first request.

Let me know, If you still have problems with the new release.

[Antonio Lazaro]

Hi Nicolas,

It works! I suggest you publish it at Wiki documentation's DCM4CHEE. Thank you.

How can we help you with development? Is there some release's schedule ?

[nicolas...@gmail.com]

You can find information in the section developer on the main page. Just contact me if you want to contribute on a specific part.

[Dr Lawrence M Fox]

I can use some help, Nicolas. I had a working system, and I downloaded and installed the 2 files (weasis-pacs-connector.war and dcm4chee-pacs-weasis.jar) to my deploy subdirectory and  I downloaded and renamed weasis-pacs-connector.properties (and edited the pacs.aet from localhost to servername) and weasis-pacs.jnlp and placed them in the config subdirectory. I can log in through localhost:8080/dcm4chee-web3 or through the servername:8080/dcm4chee-web3 and also through jmxconsole, but I can no longer download and view jnlp files. Was I supposed to do more than overwrite those 4 files and edit the single configuration file?

Thank you.

[nicolas...@gmail.com]

No, except maybe restarting dcm4chee. You don't need to add the two configuration files, if you don't edit them. You can try without them, it should work.