Server Configuration
Before a completed OData service can be used, the OData provider must be enabled via the main menu "OData / Settings" or the corresponding context menu.
OData services are bound to a specified TCP/IP address and port and made available by Intrexx. Before an OData service can be accessed, the OData server must be configured and enabled accordingly.
Settings
Binding address
The service should be accessible at the binding address. The binding address defines who is allowed to access the OData service. If you select "localhost," the service will be available only from the local PC. Other options include "Any (IPv4)," "Any (IPv6)," or manually entering a specific IP address. You can use "localhost" to test an OData service locally.
Port
Select an available port here that is not being used by another service and is not blocked by a firewall. The port specifies the TCP port on which the OData service should be accessible.
Ideally, you should choose a port number between 49152 and 65535—one of the so-called private ports. These can be used in a variety of ways because they are not registered and are therefore not associated with any specific application. The host and port together form the endpoint URL at which the service should be accessible. The service can also be easily integrated for public use under the regular domain.
The port entered here must not be the same as the port used by the Intrexx portal server. It must not be in use by any other application either.
Context
Here, you can optionally specify a context that is used as part of the service endpoint URL, for example, to run services behind a reverse proxy. The context name must be URL-compliant. When a context is specified, the endpoint URL is formed as follows: https://hostname:port/context/service.svc.
Host
You can optionally specify a hostname here if the hostname of the public service URL differs from the server's hostname—for example, to run services behind a reverse proxy.
Use SSL
You can enable SSL encryption here. You can find all the information here.
Keystore
SSL connections require a keystore that contains the certificates. Enter the filename of the keystore here. The keystore file must be located in the portal directory "/internal/cfg/odata/producer".
Keystore Password
Enter the password for the keystore here.
The provider is active
Enables or disables the OData provider. The provider is disabled by default. Once activated, the services will start automatically.
Try the service
To test a service, you can enter the endpoint URL (e.g., for the example service described here ) in a browser. The OData XML document that is displayed shows the corresponding data set.
Alternatively, you can use the "OData / View Metadata" option in the main menu to view the OData XML document that lists the service metadata.
The next step is to consume the OData service.