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 Suite 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.
| Note |
|---|
| The instructions given below are applicable only for the users who are using standalone AIS. |
The following section explains how to add a custom port and publish a provider on that port.
Defining custom port
...
in jetty.xml and wsapi.xml files
...
Changes in jetty.xml
...
file
- Go to ...
...
- <AdeptiaInstallfolder>/AdeptiaServer
...
- /ServerKernel
...
- /etc
...
- /jetty location.
...
- Open jetty.xml file.
...
Define a custom port by adding
...
the following section:
Code Block <Call
...
name="addConnector">
...
<Arg> <New id="HttpsConnectorB" class="org.eclipse.jetty.server.ServerConnector">
...
<Arg name="server"><Ref refid="Server" /></Arg>
...
<Arg name="sslContextFactory"><Ref refid="sslContextFactory2" /></Arg>
...
<Arg name="factories">
...
<Array type="org.eclipse.jetty.server.ConnectionFactory">
...
<Item> <New class="org.eclipse.jetty.server.HttpConnectionFactory">
...
<Arg name="config"><Ref refid="httpConfig" /></Arg>
...
</New> </Item> <Item> <New class="org.eclipse.jetty.http2.server.HTTP2CServerConnectionFactory">
...
<Arg name="config"><Ref refid="httpConfig" /></Arg>
...
</New> </Item> </Array> </Arg> <Set name="name">HttpsConnectorB</Set>
...
<Set name="port"><SystemProperty name="abpm.webserver.https.port" default="8443"/></Set>
...
<Set name="idleTimeout"><Property name="solr.jetty.http.idleTimeout" default="120000"/></Set>
...
<Set name="soLingerTime"><Property name="solr.jetty.http.soLingerTime" default="-1"/></Set>
...
<Set name="acceptorPriorityDelta"><Property name="solr.jetty.http.acceptorPriorityDelta" default="0"/></Set>
...
<Set name="acceptQueueSize"><Property name="solr.jetty.http.acceptQueueSize" default="0"/></Set>
...
<Set name="reuseAddress">false</Set>
...
</New>
...
</Arg>
...
</Call>
Below are the following changes which are needs to do in jetty.xml file:-
...
In the code block, update the following parameters:
Update the value of New id for the id parameter in following block code:
<New id="HttpsConnectorB" class="org.eclipse.jetty.server.ServerConnector">
...
By default, the value of New id is "HttpsConnectorB".
...
Mention the
...
same New id value in the following block code:
...
<Set name="name">HttpsConnectorB</Set>
...
Set the port number in following block code:
...
...
<Set name="port"><SystemProperty name="abpm.webserver.https.port" default="8443"/></Set>
...
For example, in case you want to configure 5443 as a custom port, update the code block as below:
<Set name="port">5443</Set>
- Save the file.
Changes in wsapi.xml file
- Go to ...
...
- <AdeptiaInstallfolder>/AdeptiaServer
...
- /ServerKernel
...
- /etc
...
- /jetty
...
- /contexts location.
...
- Open
...
- wsapi.xml file.
...
- Define a custom port by adding and updating the following section:
...
<Set name="virtualHosts">
<Array type="String">
<Item>@HttpConnectorA</Item>
</Array>
</Set>
Mention id (which is defined in the jetty.xml file) in the following block code:
...
<Item>@HttpConnectorA</Item>
...
- Save the file
...
- .
Once you have done the changes in the both jetty.xml and wsapi.xml files, the port restart the Server.
| Note |
|---|
The port will be visible in the Select Port |
...
list while creating or editing the REST Provider. |
...
Select the port number other than the default port (ServerGUI port) while creating or editing a provider. |
...
You can publish only one port at a time |
...
. |