rsinoida
|
Posted: January 09, 2012 15:27 by rsinoida
|
|
I want to consume the services in wsdl in my .NET client .Is it possible or not . If not what are the other alternatives available. |
Consume the services mentioned in wsdl files in my .NET client.
6 posts
Replies: 5 - Last Post: January 12, 2012 19:27
by: yiminxie
by: yiminxie
showing 1 - 6 of 6
Csaba Toth
|
Posted: January 09, 2012 21:46 by Csaba Toth
|
|
You question is not clear. WSDL is the service descriptor for a WebService. You don't consume anything "in wsdl", you consume a WebService. In order to do that you need the WSDL though. If you have a WSDL for a certain Service, you can generate proxy classes using Visual Studio features. In theory WebServices are platform independent, but you can run into some problems. You may need to work more if a method call involves collections. You may need to fine tune some other things. I don't see any exposed WSDL or WebService in the source code now (maybe PIXPDQ or NHIN Connact may have some). You can generate wrapper WebServices around the EJB services. |
|
rsinoida
|
Posted: January 10, 2012 09:13 by rsinoida
|
|
Let me rephrase the scenario and the question. Actually at the downloaded source code level we found following two folders: 1) OpenEmpi\openempi\nhin-adapter -> Under \src\main\java\org\openhie\openempi\nhinadapter we found OpenEmpiAdapter.java file 2) OpenEmpi\openempi\nhin-proxy -> Under \src\main\java\org\openhie\openempi\nhinproxy we found following file (a) AbstractComponentMpi.java (b) AdapterComponentMpi.java (C) AdapterComponentMpiSecured.java There are also few WSDL files lying under OpenEmpi\openempi\nhin-adapter\src\main\resources\wsdl -> AdapterComponentMpi.wsdl, AdapterComponentSecuredMpi.wsdl OpenEmpi\openempi\nhin-proxy\src\main\resources\ -> sample_request.xml So, our question is, 1) I am aware that you mentioned in your reply that "I don't see any exposed WSDL or WebService in the source code now", so are the above mentioned files of any use for us or they cann't be consumed directly/indirectly. 2) (If yes for 1), Are these files need to be hosted over tomcat? and then we need to write a SOAP wrapper on this ? 3) Or, if all together some other files are available on which we need to write a SOAP wrapper and what is the location of those files. 4) After installing OpenEMPI, I can see it running on my localsystem as http://localhost:8024/openempi-webapp-web-2.1.3/Application.html (a) So, question is Operations like 'Add Person' or Search are performed using some SOA service (hope it is not Business Layer methods) ? (b) And, where that service is located or how can I access that service separately/directly as a web url (or something) |
|
rsinoida
|
Posted: January 12, 2012 13:57 by rsinoida
|
|
Hi Toth As mentioned earlier we have deployed the nhin-adapter in tomcat .In the next leg we are facing issues relating to nhin-proxy. , these are questions to which we are grappling with: 1) Are there any supporting document for deployment of NHIN Proxy (Ejb) application on Glassfish instance as deploying the Secured version of NHIN Proxy application is still a challenge? 2)Do we have any documentation regarding communication of EJB Proxy with Webservice as how EJb client(Proxy) on glassfish will be able to call to webservice hosted on tomcat? 3)As per the provided documentation: http://kenai.com/projects/openempi/pages/InstallOpenEMPIAsTheEMPIWithinTheNHINConnectGateway “The internalConnectionInfo.xml file that needs to be modified is usually stored under SUNWappserver/domains/domain1/config/nhin.” We are not able to locate the above mentioned directory structure as well as the file mentioned on glassfish server. 4) We have consumed the nhin-adapter service but the classes in the proxy are not self describing. Is there any documentation related to it. Really appreciate your inputs and looking forward for your reply. |
|
yiminxie
|
Posted: January 12, 2012 19:27 by yiminxie
|
|
1. What problems are you having in item 1. The documentation on the web site that you are referencing explains how to install the proxy and it is basically a drop-in installation. 2. The proxy simply relays the request to the adapter that is hosted on tomcat or any other web container. 3. Every install of the NHIN gateway that is operational has the internalConnectionInfo.xml file. You may have stored it in an alternate location but if you do a search it should come up. The internalConnectionInfo file tells the gateway the web service endpoint for each service deployed on the gateway. The root directory for the structure should be relative to where you have installed the Glassfish server. 4. Both the adapter and the proxy implement the Patient Discovery service as specified by the NHIN specifications. I suggest you look at the documentation that is available at the CONNECT web site. Here is a link to the specs below. The WSDL documents are included in the CONNECT gateway source code (and also in our distribution of the adapter and proxy). http://www.connectopensource.org/product/connect-nhin-specs |
showing 1 - 6 of 6
Replies: 5 - Last Post: January 12, 2012 19:27
by: yiminxie
by: yiminxie
