TestSocket Utility
search cancel

TestSocket Utility

book

Article ID: 88677

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Error Message: TestSocket.jar Utility
 
 
Detailed Description and Symptoms
 
TestSocket.jar is a utility to test socket connections between systems using SSL or non SSL connections. 

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Detailed Description and Symptoms
 
TestSocket.jar is a utility to test socket connections between systems using SSL or non SSL connections. 

Solution

Requirements for TestSocket:

1. Ports specified be free on the server and open through the firewall

2. Java 1.5+ be installed on the server and in $PATH (should be no problem since this is required for AM)

3. The jar file be transferred in binary to both machines and set up as a 'Server' on one machine and a 'client' on the other

Steps to implement:

1. Transfer the TestSocket.jar to both machines. Place it in $AW_HOME or somewhere easy to find.

2. Stop the processes (for checking exact ports)

3. Set up a server on one machine.

> java –jar TestSocket.jar server 49258 true

 4. Set up a client on the other machine:

*Note: this is in the format of Local_IP Local_Port RemoteIP RemotePort

> java -jar TestSocket.jar client <local IP address> 49151 <server IP address> 49258 true

 TestSocket Usage:

You can return the help/usage of this file by running the following. This provides examples of what order you should fill in the IP/Port values:

 > java -jar TestSocket.jar

First argument must be server or client then additional args

 Additional args for Server:

Usage: Port and optional SSL flag must be provided

EX: 10054

EX for non-SSL: 10054 false

 
Additional args for Client

Usage: Server IP, Server port, local IP and local Port must be provided

Optionally an encryption flag for non-SSL

In the example below the server is listening on machine remote1 on port 10054.

EX: 127.0.0.1 10014 remote1 10054

In the example below the client creates a Non-SSL socket. Make sure the server is also using non-SSL.

EX: 127.0.0.1 10014 remote1 10054 false


 

Attachments

1558536230305TestSocket.jar get_app