Structure of the application package

The sample application files are installed when you install the adapter. They are packaged in an archive file that is installed in the samples folder.

Scenario 1: All-inclusive set of sample files

For Scenario 1, targeted at the Application Integrator, the sample application package includes all the required artifacts, so you do not need to use the enterprise service discovery wizard to obtain these. In a real-world deployment of the adapter, you would generate all these artifacts and configure the adapter using the enterprise service discovery wizard, as illustrated in Scenario 2

The files for Scenario 1 are archived in the following file: \samples\nonemdsample.zip.

Uncompress this .zip file to extract the file \BAPI\BapiCustomerApp.ear to the location of your choice. This filename is based on the module name specified in the enterprise service discovery wizard.

The following files are extracted from the .EAR file:

Scenario 2: Enterprise Service Discovery requirement

For Scenario 2, targeted at the Data Integrator, the sample application package provides the capability for you to create the SCA artifacts and configure the adapter using the enterprise service discovery wizard. You can, however, access copies all the files that you eventually generate using the Enterprise Service Discovery, as a way of verifying that what you create with the Enterprise Service Discovery is indeed correct and what the application expects in order to run properly.

All the necessary files, including copies of those you will generate with the enterprise service discovery wizard (for verification after you create your own copies) are archived in the following file: \samples\emdsample.zip.

Uncompress this file to extract the following files for Scenario 2:

Terms of use |

Last updated: Sun Mar 12 11:15:18 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)