Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

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

 

@RanjitIn 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.

...

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:

  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="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"

...

  1.  keystoreType="JKS"

...

  1.  keystorePass="

...

  1. password"

...

  1.  compression="

...

  1. on" noCompressionUserAgents="gozilla,

...

  1.  traviata"

...

  1.  compressableMimeType="text/html,text/xml,text/css,application/javascript,application/json" useSendfile="false" server="Adeptia"

...

  1.  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,

...


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

      ParameterValue
      Connector PortSet the port number.
      ProtocolSets the protocol to handle incoming traffic. The default value is HTTP/1.1.
      Max threadThe 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.

      SchemeSet 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".
      SecureSet this attribute to true if you wish to have calls to return true for requests received by this Connector. The default value is false.
      ClientAuthPut 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).


    Info

    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.


  1. Save the file.

  2. 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.

  3. 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.

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

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