Page Comparison

Here is the MOM of publishing SOAP/REST Provider in different port:

• ·         In cluster we need to configure web service ports in each node.
• ·         In server.xml file at Portal there are three connectors

o    Catalina  : which is used for GUI and by default web service use the same port.

o    SOAP Service : which is used for publishing web service on different port with HTTP and HTTPS Protocol.

o    REST Service : which is used for publishing web service on different port with HTTP and HTTPS Protocol

• ·         For publishing SOAP Service in different port

o    For HTTP, we can add multiple connectors and all connectors will be displayed in web service Provider GUI.

o    For HTTPS,

• ·         Add connector with client Auth = false for only server authenticated. We can add multiple connectors
• ·         Add connector with client Auth = true for only client authenticated.  And we have to give keystore and truststore file path. We can add multiple connectors

@Ranjit, In connector two client auth displayed with value as false/true. Kindly let us know which one is used and also share the link which describes the meaning of each property.

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

• ·         Message Level Security in SOAP Provider

o    We use security policy(at activity level) for message level security

o    For application level,

• ·         Either we use keystore/truststore defined in catalina port or in SSL configuration in server-configure.properties.

                           @Ranjit, As it is open question, kindly confirm which one is used.

• ·         Support of publish REST Provider on different port in AIS

o    For this, they added wsapi.xml at server.

o    We have create connector for HTTP/HTTPS in jetty.xml and configure the same connector in wsapi.xml file.

Let me know in case of any concern.

Thanks,

KratiIn a clustering environment, you may want to publish a REST or a SOAP provider on a node other than the Connect GUI node. You may also want the provider to be available on all the nodes in a cluster. Adeptia Connect equips you 

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

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

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

   Code Block
   <!-- <Connector port="XXXX" protocol="org.apache.coyote.http11.Http11NioProtocol" maxThreads="150" SSLEnabled="true/false" scheme="https/http" secure="true/false" clientAuth="false/true" sslProtocol="TLS" /> -->

   
   

   1. In the code block, update the following parameters:

      Parameter	Value
      Connector Port
      Protocol
      Max thread
      SSLEnabled
      Scheme
      Secure
      ClientAuth
      SSLProtocol

      
      

   Info
   You can add multiple ports by adding the code block in XXXX section.

   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.

4. Select the port number other than the default port (Connect GUI port).

5. Click Yes, Publish it to confirm.
6. Once published, a confirmation message is displayed.