<BR>
While I was conducting trainings across different locations in our company it became mandatory for me to train both EP5 iView development and EP6 iView development as we have projects in both the environments.
This Weblog discusses about pdk and development environments of EP5 and EP6 which will be helpful for the developers who were already working in EP5 to start EP6 iView development and for new learners who want to learn both as most of the EP implementations still are in EP5.<br><br>
EP5 or EP6 we will be using Dynpage or JSPDynpage. There is no change on that. Only the difference is in the folder structure, pdk and development environment. So, this Weblog describes all the changes in EP6.
<BR>
<BR>
<CENTER>
<table cellpadding="2" cellspacing="0" border="1" width="80%" title="Detail">
<tbody>
<tr>
<td valign="Top"><small><b>Component
<br>
</b></small></td>
<td valign="Top"><small><b>Detail <br>
</b></small></td>
<td valign="Top"><small><b>EP5 <br>
</b></small></td>
<td valign="Top"><small><b>EP6</b></small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small>PDK</small><small><br>
</small></td>
<td valign="Top"><small>Download</small><small><br>
</small></td>
<td valign="Top"><small>Zip file which can be downloaded from sdn.</small><small><br>
</small></td>
<td valign="Top"><small>Zip file which contain sca files can be downloaded
from sdn. </small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top" nowrap="nowrap"><small><br>
</small></td>
<td valign="Top"><small>Pre- requisite</small><small><br>
</small></td>
<td valign="Top"><small>Running tomcat</small><small><br>
</small></td>
<td valign="Top"><small>Running EP6</small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small><br>
</small></td>
<td valign="Top"><small>Installation</small><small><br>
</small></td>
<td valign="Top"><small>This zip file has to be extracted inside the
Jakarta-tomcat installation folder.</small><small><br>
</small></td>
<td valign="Top"><small>These are the business packages which have
to be deployed in EP6.</small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small><br>
</small></td>
<td valign="Top"><small>Content</small><small><br>
</small></td>
<td valign="Top"><small>It contains required libraries (runtime for
java-irj), java docs, examples, detailed documentation and tools for iView
development.</small><small><br>
</small></td>
<td valign="Top"><small>As it is deployed on EP pdk doesn’t contain
any libraries since the required libraries are already available in EP.</small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small>Development Environment</small><small><br>
</small></td>
<td valign="Top"><small><br>
</small></td>
<td valign="Top"><small>Eclipse 2.0</small><small><br>
</small><small>EP 5 pdk plug in.</small><small><br>
</small><small>(Eclipse 3.0 doesn’t support EP5 plugins)</small><small><br>
</small></td>
<td valign="Top"><small>Netweaver Developer Studio </small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small>Component Profiles</small><small><br>
</small></td>
<td valign="Top"><small>File name</small><small><br>
</small></td>
<td valign="Top"><small>default.properties </small><small><br>
</small></td>
<td valign="Top"><small>portalapp.xml</small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small><br>
</small></td>
<td valign="Top"><small>Number of files</small><small><br>
</small></td>
<td valign="Top"><small>Requires one .properties file for each iView
in a par file.</small><small><br>
</small><small><br>
</small><small>For example if one par file has two iViews namely Cmp01
and Cmp02 then we need to have one default.properties for Cmp01 and one more
Cmp02.properties for Cmp02.</small><small><br>
</small><small><br>
</small></td>
<td valign="Top"><small>Only one portalapp.xml file for a par file.</small><small><br>
</small><small>All iViews in a par file can be mentioned in the same
file.</small><small><br>
</small><small><br>
</small><small>Example:</small><small><br>
</small><small>………</small><small><br>
</small><small><components></small><small><br>
</small><small> <component name="Cmp01"></small><small><br>
</small><small> ......</small><small><br>
</small><small></component></small><small><br>
</small><small><component name="Cmp02"></small><small><br>
</small><small> ......</small><small><br>
</small><small></component></small><small><br>
</small><small></components></small><small><br>
</small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small>Portal Service development</small><small><br>
</small></td>
<td valign="Top"><small><br>
</small></td>
<td valign="Top"><small>Create zar files and deploy in deploynment
folder of the pdk and restart the tomcat.</small><small><br>
</small></td>
<td valign="Top"><small>Create par files and deploy in the portal from
NWDS.Then go to SystemAdministration -->systemconfiguration</small><small><br>
</small><small>-->ServiceConfiguration</small><small><br>
</small><small>-->Applications in portal and start the application.</small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small>Debugging</small><small><br>
</small></td>
<td valign="Top"><small><br>
</small></td>
<td valign="Top"><small>Start tomcat in debug mode.</small><small><br>
</small><small>Tomcat –debug. Then use debug perspective in eclipse.</small><small><br>
</small><small><br>
</small></td>
<td valign="Top"><small>Log in to Visual Administrator of SAPJ2EE and
set debug mode enable and configure a port for debug mode and restart J2EE.
Then use debug perspective in NWDS.</small><small><br>
</small></td>
</tr>
<tr>
<td valign="Top"><small>Connecting to R/3 Systems</small><small><br>
</small></td>
<td valign="Top"><small><br>
</small></td>
<td valign="Top"><small>To configure R/3 connections we have to edit
systems.xml and jcodestinations.xml file.</small><small><br>
</small></td>
<td valign="Top"><small>We can configure in System Landscape Editor
of EP6.</small><small><br>
</small></td>
</tr>
</tbody>
</table>
</CENTER>
<BR>
