!--a11y-->
Building, Deploying, Configuring, and Running
Your Application 
You have now reached the last stage in the development of you example application. However, some preparation is still essential before you can deploy and run the application successfully on the J2EE engine. Go through each of the following prerequisites carefully.
|
|
You have made sure that the relevant ABAP system, which you will be accessing remotely to retrieve the flight data, is currently available and contains flight data. |
|
|
You have made sure that the SAP J2EE Engine has been launched. To do this, refer
to |
|
|
You have checked that the configuration settings for the J2EE server and for the SDM server are entered correctly in the Developer Studio. To check the server settings, choose the menu path Window ® Preferences ® SAP J2EE Engine. |
|
|
The connection parameters for the used SLD are defined in the J2EE Visual Administrator. |
...
1. If you have not already done so, save the metadata for your project in its current state.
2.
In the Web
Dynpro Explorer, from the context menu of the project node TutWD_FlightList_Init, choose
Rebuild
Project.
Make sure that the Tasks view does not display any errors for your project.
1.
In the Web
Dynpro Explorer, select the project node TutWD_FlightList_Init
and choose
Create Archive from the context menu.
2.
Choose
Deploy Project from the context menu of the project
node.
The logical system names used in the model declaration must be associated with an actual SAP system defined in the SLD before this application can be executed. For this reason you need to create JCO connections in the Web Dynpro Content Administrator. To use an adaptive RFC model in your Web Dynpro application you will define two connections:
· A connection to get the needed (dictionary) meta data information
· A connection to get the read the application data
To create the new JCO connections proceed as follows:
...
1. Open the Web Dynpro Content Administrator on your J2EE Engine using the URL: http://<host>:<port>/webdynpro/welcome.
2. If you are using the Content Administrator for the first time, you need to perform the self registration.
3. Select the Browse tab and navigate to the application node local® TutWD_FlightList_Init® Applications® FlightListApp.
4. Choose the JCO Connections tab.
Two destinations named WD_FLIGHTLIST_MODELDATA_DEST and WD_FLIGHTLIST_RFC_METADATA_DEST are shown in this view and both of them have the status red. This means that the JCO connection is not yet maintained in assigned SLD.

5. Select WD_FLIGHTLIST_MODELDATA_DEST and choose Create to configure a new JCO connection.
a. Go though the steps of the JCO connection creation wizard and specify the connection data.
b. After making the required entries, press Finish.
c. Test your configuration data by pressing the Test button.
6. Do the same for WD_FLIGHTLIST_RFC_METADATA_DEST.
The both destinations are ready to use and the

7. If the tests were successful, you can close the Content Adminstrator. Otherwise correct your connection entries.
1. In the Web Dynpro Explorer, open the context menu for the application object FlightListApp.
2. Choose Run.
The Developer Studio performs the deployment process and then automatically launches your application in the Web browser.
Test your Web Dynpro application by entering a valid city name for the Departure City and Arrival City and then clicking the Search button. Provided the system contains the appropriate flight data, it will display it in a table.
|
|