Prev
Next
Forums Infor / Lawson Platforms Lawson Landmark

Can't configure Infor Lawson connection

 2 Replies
 0 Subscribed to this topic
 32 Subscribed to this forum
Sort:
Author
Messages
Xin Li
Veteran Member
Posts: 133
Veteran Member
9/14/2016 1:19 PM

    Our Lawson System Foundation and Landmark are federated and Landmark as primary authentication service. When I tried to configure Infor Lawson connection to Lawson system foundation at system configuration on landmark and tried to test connection it failed with error below. I was able to configure connection to other S3 environments that are not federated with landmark. Any idea what is wrong?

    ViewException:
      Class Name: PfiClassicConnection
      View Name: PfiClassicConnection
      Set Name: PfiClassicConnection.SymbolicKey
       Sort Field: PfiConfiguration = main
       Sort Field: PfiClassicConnection = com.lawson.rdtech.type.NoRepresentation@1304a27
      Field: PfiConfiguration = main
      Field: PfiClassicConnection = com.lawson.rdtech.type.NoRepresentation@1304a27
      Field: (Destination translation) = https://lsftrain.baylorhealth.edu:443 (LSFLMK)
      Field: User = lawson
      Field: Host = 
      Field: PageSize = 10
      Field: ConnectionFactory = 
      Field: Password = ***************
      Field: ResourceID = lawson
      Field: EJBUser = 
      Field: ConnectionType = 0
      Field: WebRoot = https://lsflmk.baylorhealth.edu:443
      Field: ServerNamespace = 
      Field: UAOverrideWebRoot = https://lsftst.baylorhealth.edu:443
      Field: RetryCount = 3
      Field: DataArea = LSFLMK
      Field: IIOPPort = 
      Field: TimeOut = 50
      Field: RetryPauseTime = 1000
      Field: ConfigurationSetIsMain = true

    ViewException:
      Class Name: PfiClassicConnection

    Stack Trace:

    java.lang.Exception: Connection to server failed - Host: https://lsflmk.baylorhealth.edu:443
    at [remote node Node:LmrkDeferred/10.107.160.39:60360-24969522 on host GridHost] com.lawson.bpm.eprocessserver.grid.TestConnectionsImpl.testInforLawsonConnection(TestConnectionsImpl.java:314)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
    at java.lang.reflect.Method.invoke(Method.java:620)
    at com.lawson.grid.proxy.ProxyServerImpl$ProxyRequestThread.invoke(ProxyServerImpl.java:2715)
    at com.lawson.grid.proxy.ProxyServerImpl$ProxyRequestThread.processRequest(ProxyServerImpl.java:2502)
    at com.lawson.grid.proxy.ProxyServerImpl$ProxyRequestThread.runThread(ProxyServerImpl.java:2425)
    at com.lawson.grid.util.thread.PooledThread.run(PooledThread.java:137)
    at java.lang.Thread.run(Thread.java:801)


     

    JimY
    Veteran Member
    Posts: 510
    Veteran Member
    9/14/2016 4:27 PM

      Here is a screen shot of what we have.  We use the same name on both landmark and lsf for our data area/product line.

       

      Xin Li
      Veteran Member
      Posts: 133
      Veteran Member
      9/14/2016 7:37 PM
        The connection works in IPD S3 query node. Below is what Lawson support said.


        This means the connection with Lawson is working. The test connection button in Rich Client Configuration does not always work. This is probably the reason why you got the error when clicking on the test button.