Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
This topic is 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

  1. Go to ...

...

  1. <AdeptiaInstallfolder>/AdeptiaServer

...

  1. /ServerKernel

...

  1. /etc

...

  1. /jetty location.

...

  1. Open jetty.xml file.

...

  1. Define a custom port by adding and updating the following section:
    <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>
  2. Save the file.

Changes in wsapi.xml file

Below are the following changes which are needs to do in jetty.xml file:-a)

  1. Mention new id for the id parameter in following block code

<New id="HttpsConnectorB" class="org.eclipse.jetty.server.ServerConnector"> 
Bydefault, it is " HttpsConnectorB".

...

Mention id (which is defined in the jetty.xml file) in the following block code:-
  <Item>@HttpConnectorA</Item>  

8. Save the file9. Restart the Server.

Once you have done the changes in the both jetty.xml and wsapi.xml files, the port restart the Server.
The port will be visible in the Select Port drop-down list while creating or editing the REST Provider.

10. 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.11.

Click Yes, Publish it to confirm.

Once published, a confirmation message is displayed.