Chapter 7 Section 7.3
Implementing the HTTPS eWay JCD Sample Projects Building and Deploying the prjHTTPClient_JCD Sample Project
HTTPS eWay Adapter User’s Guide 98 Sun Microsystems, Inc.
Project Operations
The prjHTTPClient_JCD Project operates as follows:
FileClientIn: The external file system that provides instructions to the inbound
File eWay; this eWay gets a text file containing the instructions and passes them to a
Business Process, jcdHttpClient1.
jcdHttpClient1: Sends instructions to the desired HTTP system via the HTTPS
eWay. jcdHttpClient1 also receives the information from the HTTPS system, via the
HTTPS eWay, then sends it to a File eWay, FileClientOut.
eaHTTPClient: The HTTP client external application or system; the HTTPS eWay
handles inbound and outbound communication with this system.
FileClientOut: The external file system that receives the information via HTTP;
another File eWay writes the received information to a text file on this system.
Input and Output Data
The HTTPS eWay Project uses the following data files:
Get_Sample.xml
Post_Sample.xml
Sample_In.dtd
These files have the following content:
GET Command: Get_Sample.xml
The input data file for the GET command is:
<website>
<method>GET</method>
<url>http://www.yahoo.com</url>
<data/>
</website>
POST Command: Post_Sample.xml
The input data file for the POST command is:
<website>
<method>POST</method>
<url>http://localhost:12000/examples/servlet/
RequestParamExample</url>
<data>firstname^MyFirstName|lastname^MyLastName</data>
</website>
Sample_In DTD: Sample_In.dtd
The eGate OTD wizard is used to create a DTD-based OTD. The input data file specifies
an URL for HTTP commands. The XML DTD code for this sample input data file is:
<!ELEMENT website (method, url, data)>
<!ELEMENT method (#PCDATA)>
<!ELEMENT url (#PCDATA)>
<!ELEMENT data (#PCDATA)>
