Verify the Secure Proxy Connections for FTP SSO

Edit online

About this task

After you configure the basic single sign-on environment, to verify that the engine can receive and initiate communication sessions, you have to establish a connection between an FTP client and the engine, initiate a session from the engine to the Sterling B2B Integrator server in the trusted zone, and review the Secure Proxy audit log for the results.

Note: Configuration files must be available on the engine for communication sessions to be established.
This procedure enables you to verify that the engine can:
  • Establish an FTP session initiated by a trading partner using an FTP client
  • Initiate an outbound session to an Sterling B2B Integrator FTP Server Adapter on behalf of the FTP client connection

To verify the communications sessions:

Procedure

  1. Make sure the engine is running.
  2. Initiate an FTP client session to the Sterling B2B Integrator server in your trusted zone.
  3. View the Inbound Node Log and the Outbound Node Log.
  4. Confirm that the data transfer was successful, as illustrated in the sample log below:

    Sample Inbound Node Log

    11 Sep 2009 11:38:28,914 [ProxyNearScheduler-Thread-2] INFO 
sys.SESSION_NODE.HTTP_Netmap_Any - protocol=http SID=1 
SNAME=server1.csg.stercomm.com SIP=10.20.246.121 SPORT=40134 SSP104I 
Session: 1 - Session Proceeding after Node match: Any 
11 Sep 2009 11:38:31,557 [ProxyFarScheduler-Thread-4] INFO 
sys.SESSION_NODE.HTTP_Netmap_Any - protocol=http SID=1 
SNAME=server1.csg.stercomm.com SIP=10.20.246.121 SPORT=40134 
DNAME=server2.csg.stercomm.com DIP=10.20.246.42 DPORT=10054 SUID=admin 
DUID=admin SSP102I Session: 1 - Control:ServerAgent Connection closed 
(CloseCode.EOF): Elapsed Time: 2.13 (s) 
: Bytes Received: 194 [at: 7.286384976525821E-4 MBPS] 
Bytes Sent: 20480595 [at: 76.92242253521127 MBPS]

    Sample Outbound Node Log

    11 Sep 2009 11:38:28,914 [ProxyNearScheduler-Thread-2] INFO 
sys.SESSION_NODE.HTTP_Netmap_Any - protocol=http SID=1 
SNAME=server1.csg.stercomm.com SIP=10.20.246.121 SPORT=40134 SSP104I 
Session: 1 - Session Proceeding after Node match: Any 
11 Sep 2009 11:38:31,557 [ProxyFarScheduler-Thread-4] INFO 
sys.SESSION_NODE.HTTP_Netmap_Any - protocol=http SID=1 
SNAME=server1.csg.stercomm.com SIP=10.20.246.121 SPORT=40134 
DNAME=server2.csg.stercomm.com DIP=10.20.246.42 DPORT=10054 SUID=admin 
DUID=admin SSP102I Session: 1 - Control:ServerAgent Connection closed 
(CloseCode.EOF): Elapsed Time: 2.13 (s) 
: Bytes Received: 194 [at: 7.286384976525821E-4 MBPS] 
Bytes Sent: 20480595 [at: 76.92242253521127 MBPS]

    If your session was unsuccessful, review the log information to determine the likely cause of the failure and the corrective action to take.