Hareen, you could try what Joel suggested. But I must ask you, isn't switching to REST connector instead of HTTP connector an option for you? We are encouraging our customers to prefer REST connectors to HTTP connectors as REST is more actively maintained and enhanced.
invokeHTTPConnector activity step 2 has the protocol hard coded as "TLS".
Below changes were made to fix this:
1. Updated step 2 in the activity InvokeHTTPConnector to comment out the hard-coding of the protocol "TLS" 2. Updated SSL outbound calls at websphere to send the requests in TLS 1.2 for the specific outbound URL.
Requests are going in TLS 1.2 after these changes.