Publishing Web service providers to a custom port
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.
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.
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:
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.