Skip to main content
Solved

FSM-PSO dataset error https

  • February 26, 2024
  • 8 replies
  • 115 views

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
Did this topic help you find an answer to your question?

8 replies

AdrianEgley
Hero (Customer)
Forum|alt.badge.img+14
  • Hero (Customer)
  • 169 replies
  • February 26, 2024

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


Forum|alt.badge.img+8
  • Author
  • Sidekick (Partner)
  • 42 replies
  • February 26, 2024

@AdrianEgley 

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


AdrianEgley
Hero (Customer)
Forum|alt.badge.img+14
  • Hero (Customer)
  • 169 replies
  • February 26, 2024

@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


Forum|alt.badge.img+8
  • Author
  • Sidekick (Partner)
  • 42 replies
  • February 26, 2024

Yes i already binded with 8744(Https) 


Forum|alt.badge.img+8
  • Author
  • Sidekick (Partner)
  • 42 replies
  • February 26, 2024

@roklde 

Do you any suggestion?

 


roklde
Superhero (Employee)
Forum|alt.badge.img+26
  • Superhero (Employee)
  • 745 replies
  • February 27, 2024

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
 


Forum|alt.badge.img+8
  • Author
  • Sidekick (Partner)
  • 42 replies
  • Answer
  • February 27, 2024

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+26
  • Superhero (Employee)
  • 745 replies
  • February 27, 2024
mihiran.p wrote:

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


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings