Difference between revisions of "Webservices Guide - OpenKM 6.2"
From OpenKM Documentation
m (→OpenKM 5.1 and olders) |
|||
Line 36: | Line 36: | ||
== OpenKM 6.0 == | == OpenKM 6.0 == | ||
+ | * [[Java client 6.0|Java client 6.0]] | ||
* [[C Sharp client 6.0|C# client 6.0]] | * [[C Sharp client 6.0|C# client 6.0]] | ||
Line 41: | Line 42: | ||
'''Sample clients''' | '''Sample clients''' | ||
* [[XML client]] | * [[XML client]] | ||
− | * [[Java client]] | + | * [[Java client 5.1|Java client 5.1]] |
* [[Android client]] | * [[Android client]] | ||
* [[Python client]] | * [[Python client]] |
Revision as of 15:03, 5 June 2012
OpenKM has a complete API exposed via Webservices. This means you can call any of these API methods from any programming language which supports the SOAP protocol, like Java, PHP or Python among others. This feature makes it possible to create a custom client, or integrate with third-party applications like a CRM or a CMS.
These are the WSDL available:
- http://localhost:8080/OpenKM/OKMAuth?wsdl
- http://localhost:8080/OpenKM/OKMBookmark?wsdl
- http://localhost:8080/OpenKM/OKMDocument?wsdl
- http://localhost:8080/OpenKM/OKMFolder?wsdl
- http://localhost:8080/OpenKM/OKMMail?wsdl
- http://localhost:8080/OpenKM/OKMNote?wsdl
- http://localhost:8080/OpenKM/OKMNotification?wsdl
- http://localhost:8080/OpenKM/OKMProperty?wsdl
- http://localhost:8080/OpenKM/OKMPropertyGroup?wsdl
- http://localhost:8080/OpenKM/OKMRepository?wsdl
- http://localhost:8080/OpenKM/OKMSearch?wsdl
- http://localhost:8080/OpenKM/OKMWorkflow?wsdl
In the upcoming OpenKM 6.0 webservices will be listed at http://localhost:8080/OpenKM/services. |
OKM Webservices API
- OKMAuth
- OKMBookmark
- OKMDocument
- OKMFolder
- OKMMail
- OKMNote
- OKMNotification
- OKMProperty
- OKMPropertyGroup
- OKMRepository
- OKMSearch
- OKMWorkflow
Sample clients
OpenKM 6.0
OpenKM 5.1 and before
Sample clients
Changing of soap:address location
By default, JBoss set the soap:address to the bind address. Usually this cause problems because the SOAP client will try to connect to a incorrect address. To change this, edit the file $JBOSS_HOME/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml and take a look a these values:
<property name="webServiceHost">your.company.com</property>
<property name="webServicePort">80</property>
<property name="modifySOAPAddress">true</property>