Web services are services that provide functionality and data
via the internet. Similarly to a search engine, queries will be sent
from a sender, which in this case is not a person, rather a software
program. The web service returns the results to the program querying
it. Web services can be provided for use either internally or
externally to the company.
If you would like to, for example, find the name of a bank based on a
routing code, a web service can determine and return the desired data
using an operation. The operations are described using WSDL (Web
Services Description Language) files. The exchange of information takes
place via an exchange of XML files.
In order to use a web service, the URL with which the web service is
identified must be known. Additionally, special software is required to
interpret the information that is delivered.
With Intrexx, web service provisions can be consumed without requiring additional
programming efforts. Furthermore, you can provide your own web services.
The current version of Intrexx exclusively supports web
services that are specified under the WSI Basic Profile Version 1.1. Here you can find information on this topic:
http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
2. Provide web service
A new web service can by added via the context menu.
To be able to configure web services, the user needs to have the
portal permissionProvide web services and
permission to access the Tools module.
4. HTTPS certification
In the following it is assumed in the following that the relevant certificate and keystore and truststore are already present. It should be noted that both keystore and truststore have the file type Java Keystore (file ending jks).
4.1 AXIS2 configuration
To setup a transport using HTTPS, modifications to the Axis2 configuration file need to be carried out. Switch to the directory
Beneath this entry is another <transportsender> element that is currently commented out. Remove the comment tags to activate the entry.
<!-- the non-blocking https transport sender based on HttpCore + NIO SSL extensions-->
<transportSender name="https" class="de.uplanet.lucy.server.webservice.provider.axis2.transport.nhttp.Http
CoreNIOSSLSender">
<parameter name="non-blocking" locked="false">true</parameter>
<parameter name="keystore" locked="false">
<KeyStore>
<Location>KEYSTORE.jks</Location>
<Type>JKS</Type>
<Password>KEYSTORE_PASSWORD</Password>
<KeyPassword>KEY_PASSWORD</KeyPassword>
</KeyStore>
</parameter>
<parameter locked="false" name="truststore">
<TrustStore>
<Location>TRUSTSTORE.jks</Location>
<Type>JKS</Type>
<Password>TRUSTSTORE_PASSWORD</Password>
</TrustStore>
</parameter>
<parameter name="HostnameVerifier">DefaultAndLocalhost</parameter>
;<!--supports Strict|AllowAll|DefaultAndLocalhost or the default if none specified-->
</transportSender>
The following values need to be filled in correctly:
Parameter
Description
KEYSTORE.jks
Path to the Keystore in the format JKS. The path must be entered relevant to the directory <intrexx>\org\<portal>\internal\webservice\provider\
KEYSTORE_PASSWORD
Password for the stated Keystore.
KEY_PASSWORD
Password for the used key.
TRUSTSTORE.jks
Path to the Truststore in the format JKS. The path must be entered relevant to the directory <intrexx>\org\<portal>\internal\webservice\provider\
TRUSTSTORE_PASSWORD
Password for the stated Truststore.
Save the file and then restart the portal service. Afterwards, call up the WSDL file in the browser to test the HTTPS authentication. When doing this, make sure that the entries are correct, i.e. the port and https instead of http. If the URL has been correctly entered, the applied certificate must be accepted. Subsequently, the WSDL file will be shown in the browser.