# Regarding new CKM version webservice

**Category:** [Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)
**Created:** 2013-03-07 10:35 UTC
**Views:** 2
**Replies:** 12
**URL:** https://discourse.openehr.org/t/regarding-new-ckm-version-webservice/14703

---

## Post #1 by @yampeku

Hello all,

Just to warn all potential CKM webservice users, CKM webservice
endpoint has changed from
'http://openehr.org/knowledge/services/.....' to
'http://openehr.org/ckm/services/......'
Changing the endpoint solves the problem\. The webservice itself seems
to be the same\. Are there any changes planed for it?

Regards

---

## Post #2 by @ian.mcnicoll

Hi Diego,

I think this is technical hitch\. The intention, AFAIK was to retain
the original endpint, as well as adding the new one\.

Ian

---

## Post #3 by @yampeku

It gives a 301 code "moved permanently"
http://en.wikipedia.org/wiki/HTTP_301

---

## Post #4 by @system

Thank you, Diego\.

getArchetypeIdsFromPartialId API seems not working here, but I will study more\.

Regards,

---

## Post #5 by @system

These web service APIs are not wroking now\. Are they obsoleted?
getArchetypeIdsFromPartialId
getArchetypeIdsFromPartialIdWithPositioning
getAllArchetypeIds
getAllArchetypeIdsWithPositioning

I would be very happy, if new APIs are figured\.

Regards,
Shinji

---

## Post #6 by @system

Hi Shinji,

No, they are certainly not obsolete.
This was just a curly bracket that moved one up accidentally.
I have fixed this locally and will be deploy asap.

Cheers
Sebastian

---

## Post #7 by @system

Hi Sebastian,

Thank you\.

I use getArchetypeIdsFromPartialId API to query archetypes by key word\.
Does web service APIs change?

Regards,
Shinji

---

## Post #8 by @system

Hi Diego,

This - in itself - is actually correct I believe: it has moved there and the 301 response is the recommended way of having the old url still in place as far as I know.

You'll notice that in a browser this redirects correctly, e.g.
[http://openehr.org/knowledge/services/ArchetypeFinderBean/](http://openehr.org/ckm/services/ArchetypeFinderBean/getAllArchetypeIdsWithPositioning?cursor=1&size=10)[getArchetypeADLURL?archetypeId=openEHR-EHR-OBSERVATION.blood_pressure.v1](http://openehr.org/ckm/services/ArchetypeFinderBean/getArchetypeADLURL?archetypeId=openEHR-EHR-OBSERVATION.blood_pressure.v1)

redirects from .../knowledge/... to .../ckm/... and then gives you the right response.

The problem is that e.g. the AE webservice client and likely others don't know what to do with this redirect (e.g. ask the user if they want to redirect or silently redirect).

We'll try to get the the webservice urls to silently redirect without giving a 301 response in between.

In any case, where it is possible, the webservice URL should be updated to [http://openehr.org/ckm/services/ArchetypeFinderBean?wsdl](http://openehr.org/ckm/services/ArchetypeFinderBean?wsdl) - saves you the redirect.

Cheers
Sebastian

---

## Post #9 by @system

Hi Shinji,

I don't think anything has changed there (once it works again).

Regards
Sebastian

---

## Post #10 by @system

These 4 webservices should work now as expected (using the /ckm url).
Sebastian

---

## Post #11 by @system

I confirmed, the web services working, too\.

---

## Post #12 by @system

It should now work with the old URL as well I believe (at least it works in the Archetype Editor).

I would still ask everybody to update to the new URL where this is possible, because then your request doesn't have to be forwarded from one server to the other and back again.
In Archetype Editor: Under Tools/Options set the URL for shared repository to [http://openehr.org/ckm/services/ArchetypeFinderBean?wsdl](http://openehr.org/ckm/services/ArchetypeFinderBean?wsdl)

Regards
Sebastian

---

## Post #13 by @system

Hi\!

Nice to see the CKM product and the openEHR installation of it being updated\!

> In Archetype Editor: Under Tools/Options set the URL for shared repository
> to http://openehr.org/ckm/services/ArchetypeFinderBean?wsdl

Just a thought:
Some time in a distant future when rethinking/refactoring archetype
handling beyond the CKM product it might be a good idea to exclude
specific company\-bound product names \(like "CKM"\) and specific
implementation\-bound techniques \(like "Bean"\) from openEHR
foundation\-controlled URIs\.

Best regards,
Erik Sundvall
erik\.sundvall@liu\.se http://www.imt.liu.se/~erisu/  Tel: \+46\-13\-286733

---


**Canonical:** https://discourse.openehr.org/t/regarding-new-ckm-version-webservice/14703
**Original content:** https://discourse.openehr.org/t/regarding-new-ckm-version-webservice/14703