[Koha-bugs] [Bug 25965] Create SIP2 client daemon with HTTPS API endpoint

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25965

--- Comment #13 from Lari Strand <lmstrand at gmail.com> ---
Here a quick how-to:

For this module to work you obviously need to apply the patch. Then there's a
configuration file called sip2ohttp-conf.xml attached that needs to be put into
the same configuration file folder as the environment variable KOHA_CONF points
to (where koha-conf.xml file is located).

The xml validation requires an xml schema file (sipschema.xml). The schema file
should be located in the koha-tmpl folder (the parent directory of koha-tmpl
folder gets read like this: C4::Context->config('intranetdir');) When the REST
endpoint receives an XML message, it will be validated against this schema file
before further processing.

In the configuration file sip2ohttp-conf.xml there's a short description on how
to use it. You need to add the devices that you want to use sipohttps with
here. The module SIPoHTTP.pm will search for device parameters from here when
the REST endpoint /sipmessages receives a POST request with an XML in the
request body.

example config parameters for a device login with an ID "SIPDEVICE" (also
configured in SIPdevices.xml by the same ID):

                <SIPDEVICENAME>
                        <host>127.0.0.1</host>
                        <port>6009</port>
                </SIPDEVICENAME>

Host and port are the sip server's address you want the device to talk with.
Obviously you need a sip server running in that address.

As mentioned, the device should also be configured to be able to use the sip
servers in the SIPconfig.xml file. The device login id's configured in the
sip2ohttp-conf.xml file need to match the login id's defined in SIPconfig.xml.

That's about it. Now you can communicate with the sip server/servers via the
REST endpoint by passing it an XML file like in the Postman attachment I
included.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.