Hello,I am new to TDI, but so far I have been able to read and write to IBM Notes, set up a Http Server connector.But I cannot get beyond the first step in setting up the Http Client Connector as below:

Sorry for the delay. Was not able to respond earlier.As this is only the first step in setting up the AL and make the first and IBM suggests making small steps in setting up AL's, I expected that default settings as below would be sufficient.I have also tried the other content types, but still get the connection timed out.

Pon Power BV has its registered office in Papendrecht and is listed in theCommercial Register of Chamber of Commerce in Rotterdam under file number23060463. All legal relations of Pon Power will be governed by our generalconditions and they will upon request be made available without charge. Theconditions are deposited at the Chamber of Commerce Rotterdam and can befound on www.pon-cat.com. Pon Power rejects explicitly the applicability ofany general terms and conditions which its contractual parties may use.Jurisdiction: District Court Dordrecht, Netherlands.

Here is a verbal example, Tom, and it's a recipe for a simple AL that let's you play with HTTP comms.

Set up an AL with an HTTP Client Connector and set it to CallReply mode. This mode means you get an Output Map where you can set up the request, and an Input Map for response. Add a Dump Entry script after the Connector to view the response.

In the Output Map you can pass in the url by mapping out 'url' (of course, you can also set the parameter of the Connector). You can send any number of HTTP headers by mapping their names preceded by 'http.'. So for example, to pass the Accept header simply map 'http.Accept'.

The response you get back will contain the headers (http.*) and body (http.body). Note that depending on the Content-Type received, parsing of the http.body attribute may not be what you want. That is why the Connector always returns two more 'body' attributes: http.bodyAsBytes and http.bodyAsString. The 'bodyAsString' version is always returned as a Java String. This is what I always use to get the return payload. From there I use stuff like work.fromXML(body, "*", "") or work.fromJSON() to parse this payload into an hierarchical entry. You'll find several posts on my blog about dealing with hierarchical data.