You may want to publish a REST or a SOAP provider on a node other than the Connect GUI node. You may have this requirement in both single node and multiple nodes (clustered) environment. To achieve this, Adeptia Connect equips you with a feature to define a custom port and then publish the provider on that port. Doing this, you can have different web service providers running on different nodes.

The following section explains how to add a custom port and publish a provider on that port.

Defining custom port in Server.xml file

Follow the steps below to publish a web service provider to a custom port:

Go to ...<ConnectPortalInstallfolder>/<conf> location.
Open Server.xml file.

Define a custom port by adding and updating the following section:

<!-- <Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="5000" scheme="https" secure="true" compressionMinSize="128" connectionTimeout="20000" maxConnections="10000" clientAuth="false" sslProtocol="TLSv1.2" sslEnabledProtocols="TLSv1.2" keystoreFile="./keystore/adeptiaBPM.keystore" keystoreType="JKS" keystorePass="password" compression="on" noCompressionUserAgents="gozilla, traviata" compressableMimeType="text/html,text/xml,text/css,application/javascript,application/json" useSendfile="false" server="Adeptia" xpoweredby="false" />

In the code block, update the following parameters:

Parameter	Value
Connector Port	Set the port number.
Protocol	Sets the protocol to handle incoming traffic. The default value is `HTTP/1.1.`
Max thread	The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. If not specified, this attribute is set to 200.
SSLEnabled	Use this attribute to enable SSL traffic on a connector. To turn on SSL handshake/encryption/decryption on a connector set this value to `true`. The default value is `false`.
Scheme	Set this attribute to the name of the protocol you wish to have returned by calls. For example, you would set this attribute to "`https`" for an SSL Connector. The default value is "`http`".
Secure	Set this attribute to `true` if you wish to have calls to return `true` for requests received by this Connector. The default value is `false`.
ClientAuth	Put the value as true or false.
SSLProtocol	JSSE only. The SSL protocol(s) to use (a single value may enable multiple protocols - see the JVM documentation for details).

You can add multiple ports by adding the code block in the respective SoapService and RestService sections.

In case of the clustered environment, you need to define the custom ports on every node.

Save the file.
Restart the Connect Portal.
Once you have added the ports in the Server.xml file, they will be visible in the Select Port drop-down list while creating or editing the REST and SOAP Provider.
Select the port number other than the default port (Connect GUI port) while creating or editing a provider.
You can publish only on one port at a time.
Click Yes, Publish it to confirm.
Once published, a confirmation message is displayed.

If you are creating a SOAP Provider on the Connect Server side, you do not get an option to define a custom port.

You may be interested in...

Defining custom port in Server.xml file

What's new

Best practices

Training guides

Frequently asked questions

Adeptia Connect APIs

Adeptia security report

Browser not supported