1. import model/linked model/container model 1.1 Imported Model Builder: Host Model and target Model share the same WebApp,  target model are imported into the host model at generation time. The host model can invoke all the builder calls of the target model, but cannot change any of the builder imputs. 1.2 Linked Model Builder: Host model and Linked model use two separate WebApp. From a host model, we can access any public methods, Linked Java Objects(LJOs), and action lists in Linked Model. They are roughly analogous to classes in java. Linked Model builder is best suited for linking to data and logic that resides in another model. It is not suited for linking to any user interface elements(pages, buttons, forms, and so forth) that may reside in another model. 1.3 Model Container Builder: The Model Container builder allows a model to host another model at the named page location.  It is ideal for retrieving user interface components from another model. 2. app war/portal war/ dev war 3. lifecycle, profile -> generation time -> execution time 4. portal server/portlet container/portlet portal server: first received request from the client forward the request to portlet container aggregating the content produced by the protlets portlet Container: contains and run portlets, manages portlets lifecycle, provides portlets with the required runtime environment,provides persistent storage for portlet perferences 5. portlet container / servlet container portlets and servlets are java technology based web components both are managed by a specialized container both generate dynamic content lifecycle is managed by a container inteact with web client via a request/response paradigm difference: portlet only generate markup fragments, not complete documents. The portal aggregates portlet fragments into a complete portal page portlet are not directly bound to a URL web clients interact with portlets through a portal system portlets have a refined request handling, action requests and render requests portlets have predefined portlet mode and window states portlets can exist many times in a portal page portlets have means for accessing and storing persistent configuration and cusomization data portlets have access to user profile information 6. JSF Portlet Framework in RAD 7 7. Thems and stylesheet for portal server 8. configure Web service URL in WPF: first approach: 1. configure in the property file 2. load in LJO and set to share variables 3. in web service builder "advance" section, use the shared variables to override host,url,etc. there are no UI for editing second approach: 1. when export model to portlet, in portlet adapter builder, configure preference in "advance" section, each url associated with an item. 2. in LJO, get httpservlet request from webAppAccess; then get portlet request from http request; then get preference from portlet requet; last we can get the url we configurated in preference. I am not sure if we can configure the preference on UI