General inputs

Enter a name for this builder call. The WebSphere® Portlet Factory Designer displays this name in the builder call list.

Model

Select the model you want to import.

Profiled Inputs

Table 2. Profiled Inputs

Input name

Description

Profile Handling

Determines how to handle any profiled inputs in the model that is being imported. In the descriptions below, the model that contains the Imported Model builder is referred to as the parent and the model that is being imported is called the child. You can choose: None

Allows the child model to use the default values for its profiled builder inputs. The parent model does not inherit any profile sets from the child. No profiling or input substitution is performed for the child model.

Note: If the parent model has one or more applied profiles, the child model uses, for the default values of its profiled builder inputs, the values from the applied profiles of the parent.

Set individual inputs

Adds builder inputs to the Imported Model builder for each profiled input in the child model. The values given in these inputs replace the corresponding profiled values in the child model.

Use parent profiling

Forces the profiles applied to the parent model to be used to resolve the profiled inputs in the child model when the parent and child use one or more of the same profile sets. In addition, the Imported Model builder is itself profiled with the profile sets that are used by the child model. This action causes the parent model to expose for profiling all profile sets that the child model uses at the time you select this input. It also ensures that the same profiles are applied to the parent and child for those profile sets that they have in common.

Note: If the child model subsequently has profile sets added or deleted, the Imported Model builder is not synchronized with the new set of profiles in the child model. To synchronize the Imported Model builder and the child model, open this builder, select None for the Profile Handling input, re-select Use parent profiling, and save the model.

Multiple Instance Support

Table 3. Multiple Instance Support inputs

Input name

Description

Pattern to replace

Use this input when you need to import the same model multiple times. This input allows you to rename the input names of certain builder calls in the imported model and thus avoid namespace collisions in the parent model.

Enter the builder-call naming pattern used by the incoming model. This pattern is recognized and all incoming model builder call inputs displaying the pattern are renamed.

Note: To use this input effectively, you should have established a builder call naming pattern in the model you are importing. For example, builder calls in the incoming model might be named as follows: forImport_XXX.

Examples of this kind of pattern could include: forImport_orders,forImport_sales, forImport_summary.

Advanced

Table 4. Advanced inputs

Input name

Description

Import Once

Enable this input to limit importation to a one-time operation.

When enabled, the builder examines the WebApp to see if the artifacts being imported already exist from a previous import operation. If they do, they are not imported again.

This input is useful to import a common piece of code, but want this code to be imported only once per outer model. This situation might occur when you are creating a builder.

Reset Values from Profiles

Click this button to populate the profiled inputs from one of the profiles in the profile sets associated with the imported model. When you click this button, a small dialog appears, allowing you to choose the profile from which you want to set the profiled input values.