Chapter 7 | Section 7.4 |
Implementing the HTTPS eWay JCD Sample Projects | Building and Deploying the prjHTTPServer_JCD Sample Project |
7.3.8Creating and Activating the Deployment Profile
Deployment Profiles are used to assign Collaborations and message destinations to the Integration Server and message server. Deployment profiles are created using the Deployment Editor.
Follow the steps outlined in “Creating and Activating the Deployment Profile” on page 80 to create and deploy a deployment profile for the prjHTTPClient_JCD Project.
7.3.9Creating and Starting the Domain
To deploy your Project you must first create a domain. After the domain is created, the Project is built and then deployed.
Follow the steps outlined in “Creating and Starting the Domain” on page 81 to create and deploy a domain for the prjHTTPClient_JCD Project.
7.3.10Building and Deploying the Project
The Build process compiles and validates the Project’s Java files and creates the Project EAR file. Follow the steps outlined in “Building and Deploying the Project” on page 82 to build and deploy the prjHTTPClient_JCD Project.
7.3.11Running the Sample
The prjHTTPClient_JCD Project includes the following sample files:
Get_Input.xml.~in (input file)
Post_Input.xml.~in (input file)
HttpClient_JCD_output0.htm (sample output file example)
HttpClient_JCD_output1.htm (sample output file example) To run your deployed sample Project, do the following:
1From your configured input directory, paste (or rename) the sample input file to trigger the eWay.
2From your output directory, verify the output data.
7.4Building and Deploying the prjHTTPServer_JCD Sample Project
The HTTPS eWay server sample Project prjHTTPServer_JCD demonstrates how the HTTPS eWay receives information via HTTP from a server. Resulting or confirming information is then written to a data file.
Project Overview on page 105
HTTPS eWay Adapter User’s Guide | 104 | Sun Microsystems, Inc. |
