Sun Microsystems eWay SAP BAPI - Manual (Page 92)

Chapter 6 Section 6.6
Reviewing the Sample Projects Building and Deploying the prjIDocInbound Sample Project
eWay™ Adapter for SAP BAPI User’s Guide 92 Sun Microsystems, Inc.
6.5.11
Build and Deploy the Project
The Build process compiles and validates the Project’s Java files and creates the Project
EAR file.
Build the Project
1 From the Deployment Editor toolbar, click the Build icon.
2 If there are any validation errors, a Validation Errors pane will appear at the
bottom of the Deployment Editor and displays information regarding the errors.
Make any necessary corrections, save and then click Build again.
3 After the Build has succeeded you are ready to deploy your Project.
Deploy the Project
1 From the Deployment Editor toolbar, click the Deploy icon. Click Yes when the
Deploy
prompt appears.
2 A message appears when the project is successfully deployed. You can now test
your sample.
3 You can also deploy applications using Enterprise Manager. For more information,
see the Sun SeeBeyond eGate™ Integrator System Administration Guide.
6.5.12
Run the Sample Project
Additional steps are required to run the deployed sample Project.
Steps required to run the sample Project:
1 Use the inputBAPIFlightGetList.txt trigger file included in the sample Project to
execute the SAP BAPI function module.
The File eWay polls the directory for the input file name (as defined in the Inbound
File eWay Properties window). The Business process then uses a Java Collaboration
to acquire a list of flight information from the designated carrier. The resulting
information is then saved to an output file outputFlight%d.dat.
2 Verify the output data by viewing the sample output files.
6.6
Building and Deploying the prjIDocInbound Sample
Project
The following sections provide instruction on how to manually create the sample
Project.You must have SAP ALE installed to run this sample Project.
This sample Project shows how to use the IDOC_INBOUND_ASYNCHRONOUS RFC
OTD to receive IDocs from SAP R/3 in a generic manner. It then checks for the message
type of the received IDoc and then unmarshals it to the appropriate OTD. The IDoc
data is then passed onto the respective JCDs for further processing.
Steps required to create the sample project include: