Linked Model builder inputsAdded by IBM on June 28, 2011 | Version 1 (Original)
|This topic describes the inputs for the Linked Model builder.
This topic describes the inputs for the Linked Model builder.
Table 1. Linked Model builder inputs
|Name||Enter a name for this builder call. The WebSphere® Portlet Factory Designer displays this name in the builder call list.|
|Model||Select the model that the current model will link to. |
|Instance Rule||Determines whether the contained model instance is to be accessed using a linked model path from the topmost container model instance (Keep separate model data for each model container within a portlet session) or stored directly in the (portlet) session (Allow model data to be shared across model containers within a portlet session (session singleton)).|
Set the value of this input to one of the following:
Keep separate model data for each model container within a portlet session
Allows multiple instances of the linked model to be generated for requests in the same session. Always use this option unless you know that you need the other setting and are sure that it will not break anything.Allow model data to be shared across model containers within a portlet session (session singleton)
Have only one instance of this model generated for all the requests in a session.
|Inherit Explicit Profile||Enable this checkbox if you want the profiled builder call inputs in the linked model to get their values from the profile passed explicitly as part of the request for the host model. |
The model normal profile selection will not take place if you choose to inherit explicit profiles. All profiled inputs will get their values from the profile passed to the host model.
|Rename Existing||This input is useful to change the behavior of code that was placed in the WebApp by a high-level builder or by an Imported Model builder. |
For example, you might want to do this if you have a Domino View & Form builder in your model, and you want to use a different class for one of the LJOs that builder adds to the WebApp. The Domino View & Form builder does not provide an LJO Class Name input. But, you can place a new LJO builder in the model and give it the same name as that assigned by the Domino View & Form builder, thus replacing the existing LJO and specifying a new class.
When checked, this input causes the builder to replace an existing WebApp object with a new object. The builder locates the existing WebApp object (for example, a variable or LJO), renames it, and creates a replacement object. Note: This input is available on the following low-level builders that create WebApp objects: Action List, Imported Page, Linked Java Object, Linked Model, Method, Method Call, Page, Variable and Schema.
Parent topic: Linked Model builder