The Enterprise Portal development consists of the following parts:
? Portal Application Module
? Portal Application Standalone
For Enterprise Portal Application development with SAP NetWeaver Development Infrastructure (NWDI), a track with the following Software Component Build dependencies has to be configured:
? DI BUILD TOOL 7.00
? SAP J2EE ENGINE 7.00
? SAP JAVA TECH SERVICES 7.00
? EP BUILD TOOL 7.0
Some basic portal applications (like HTMLB or Portal Runtime Technoloy (PRT)) are part of the SAP JAVA TECH SERVICES Software Component. For the usage dependencies of all other standard portal applications (added as SharingReference in the portalapp.xml), the public JAR files of the referenced portal applications have to be wrapped in an External Library DC project. For more information, see External Library DC. You have to perform this to be able to reference the JAR files as the public part (of type compilation) within the NWDI component model.
Deployment is not needed because the standard portal applications are already deployed during the installation of the Enterprise Portal server.
A Portal Application Module DC contains the model classes and structures for an Enterprise Portal Application project.
When you create a Portal Application Module DC, the SAP NetWeaver Developer Studio will automatically create a public part for assembly that contains the Portal Archive (PAR) archive and a public part for compilation that contains the API part.
You should not modify automatically generated public parts.
Compiled classes and PAR files. The build result is not directly deployable using the SDM to the configured J2EE Engine or the runtime systems configured within the NWDI tracks. Therefore it has to be packaged in an Enterprise Application (an EAR) project. For more information, see Development Configuration. Multiple Portal Application Module projects can be referenced in one Enterprise Application project so that they can be deployed together.
The PAR file can also be uploaded to the portal using direct “PAR Upload” to the configured Portal Runtime.
To process Enterprise Portal Module DCs, use the Portal DC Explorer in the Enterprise Portal perspective.
A Portal Application Standalone DC contains the model classes and structures for an Enterprise Portal Application project. The difference from the Portal Application Module is the fact that these projects are automatically built in deployable archives (SDA).
When you create a Portal Application Standalone DC, the SAP NetWeaver Developer Studio will automatically create a public part for assembly that contains the PAR archive and a public part for compilation that contains the API part.
Compiled classes and SDA (contains PAR); they are immediately deployable on the server.
To process Enterprise Portal Standalone DCs, use the Portal DC Explorer in the Enterprise Portal perspective.