Skip to main content
Solved

FSM-PSO dataset error https

  • Feb 26, 2024 12:33 PM UTC
  • 8 replies
  • 168 views
Sidekick (Partner)
Forum|alt.badge.img+8

I integrated FSM and PSO using HTTPS method but received an error message when initializing the dataset for on-premises systems. PSO base URL also configured on web config

 

 

 

Below are my webconfig

<endpoint address="https://xxx-xxx-xxx-xx.xxx.com:8744/IFS/Scheduling/Gateway/Service/Data" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IDataRequest" contract="GatewayService.IDataRequest" name="WSHttpBinding_IDataRequest" />
      <endpoint address="https://oxxx-xxx-xxx-xx.xxx.com:8744/IFS/Scheduling/Gateway/Service/SystemManagement" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_ISystemManagementRequest" contract="GatewayService.ISystemManagementRequest" name="WSHttpBinding_ISystemManagementRequest" />
      <endpoint address="https://xxx-xxx-xxx-xx.xxx.com:8744/IFS/Scheduling/Gateway/Service/Session" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_ISessionRequest" contract="GatewayService.ISessionRequest" name="WSHttpBinding_ISessionRequest" />
      <endpoint address="https://xxx-xxx-xxx-xx.xxx.com:8744/IFS/Scheduling/Gateway/Service" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IRemotingInterface" contract="GatewayService.IRemotingInterface" name="WSHttpBinding_IRemotingInterface" />

Best answer by mihiran.p

It works once I change the below parameter to 'transport' in the web config file.

 

wsHttpBinding

 

WSHttpBinding_IRemotingInterface

 

WSHttpBinding_ISessionRequest

 

WSHttpBinding_ISystemManagementRequest

 

View original

8 replies

AdrianEgley
Hero (Customer)
Forum|alt.badge.img+14
  • AdrianEgley
  • Hero (Customer)
  • Feb 26, 2024 1:06 PM UTC

Hi @mihiran.p,

We recently made a similar change to HTTPS.

Can you check in PSO the value for the Parameter ‘TransportProtocol’. We set this to ‘BINDING_WS_HTTP’.

 

 

Ady

    Sidekick (Partner)
    Forum|alt.badge.img+8
    • mihiran.p
    • Author
    • Sidekick (Partner)
    • Feb 26, 2024 1:13 PM UTC

    @AdrianEgley 

    I changed the setting to BINDING_WS_HTTP, however, the issue still persists.

      AdrianEgley
      Hero (Customer)
      Forum|alt.badge.img+14
      • AdrianEgley
      • Hero (Customer)
      • Feb 26, 2024 2:10 PM UTC

      @mihiran.p 

      The only other thing that appears in the actions I completed was to add a certificate for HTTPS on the PSO server where the scheduling gateway is installed for the *:8744 (https).

      Ady

        Sidekick (Partner)
        Forum|alt.badge.img+8
        • mihiran.p
        • Author
        • Sidekick (Partner)
        • Feb 26, 2024 2:15 PM UTC

        Yes i already binded with 8744(Https) 

          Sidekick (Partner)
          Forum|alt.badge.img+8
          • mihiran.p
          • Author
          • Sidekick (Partner)
          • Feb 26, 2024 4:09 PM UTC

          @roklde 

          Do you any suggestion?

           

          roklde
          Superhero (Employee)
          Forum|alt.badge.img+27
          • roklde
          • Superhero (Employee)
          • Feb 27, 2024 8:18 AM UTC

          Hi @mihiran.p !

          Have you restarted the PSO GWY after making the above changes? Further, could you try to execute following command in PowerShell and check if the output correctly shows the binded certificate for Port 8744?

          netsh http show sslcert ipport="0.0.0.0:8744"


          If that’s correct, try to reboot the machine and check again.

          Do you have a Load Balancer in front of PSO? If yes, make sure that the port 8744 is allowed and uses HTTPS.

          Best regards
          Roman
           

            Sidekick (Partner)
            Forum|alt.badge.img+8
            • mihiran.p
            • Author
            • Sidekick (Partner)
            • Answer
            • Feb 27, 2024 12:26 PM UTC

            It works once I change the below parameter to 'transport' in the web config file.

             

            wsHttpBinding

             

            WSHttpBinding_IRemotingInterface

             

            WSHttpBinding_ISessionRequest

             

            WSHttpBinding_ISystemManagementRequest

             

              roklde
              Superhero (Employee)
              Forum|alt.badge.img+27
              • roklde
              • Superhero (Employee)
              • Feb 27, 2024 3:43 PM UTC

              It works once I change the below parameter to 'transport' in the web config file.

               

              wsHttpBinding

               

              WSHttpBinding_IRemotingInterface

               

              WSHttpBinding_ISessionRequest

               

              WSHttpBinding_ISystemManagementRequest

               

              That’s the reason why it’s recommended to use the FSM Installer to setup the PSO Gateway URL. The Installer will set all the bindings correctly and no fiddling around with the web.config is required. ;)

              Best regards
              Roman

                Terms & ConditionsAccessibility statement