Solved

FSM-PSO dataset error https

  • 26 February 2024
  • 8 replies
  • 52 views
M
Rank
Userlevel 1
Badge +6

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

icon

Best answer by mihiran.p 27 February 2024, 13:26

View original

8 replies

AdrianEgley
Rank
Userlevel 5
Badge +14

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

M
Rank
Userlevel 1
Badge +6

@AdrianEgley 

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

AdrianEgley
Rank
Userlevel 5
Badge +14

@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

M
Rank
Userlevel 1
Badge +6

Yes i already binded with 8744(Https) 

M
Rank
Userlevel 1
Badge +6

@roklde 

Do you any suggestion?

 

roklde
Rank
Userlevel 6
Badge +23

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
 

M
Rank
Userlevel 1
Badge +6

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

 

wsHttpBinding

 

WSHttpBinding_IRemotingInterface

 

WSHttpBinding_ISessionRequest

 

WSHttpBinding_ISystemManagementRequest

 

roklde
Rank
Userlevel 6
Badge +23

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


Terms & ConditionsCookie settings