Configuring components and policies

You can add components or policies to a virtual application, or view or edit components or policies.

About this task

This task is done within the Pattern Builder.

The Pattern Builder makes it simple to model a virtual application by placing components on a canvas, linking them together, and applying relevant policies to components.

Procedure

  1. Click Patterns > Virtual Application Patterns.
  2. Select a pattern type and then select a virtual application pattern.
  3. Click Open.
    On the Pattern Builder pane, complete one of the following actions:
    • To edit an existing component or policy, click the component or policy part on the canvas.
    • To add a component, select the component from the list of assets, then drag the component to the canvas.
    • After you add a component to the canvas, add a policy by either clicking Add policy for application on the canvas, or by clicking the Add a Component Policy icon in a component part on the canvas.

      You can apply a policy globally at the application level, or apply it to a specific component that supports the policy. When you apply a policy globally, it is applied to all components in the virtual application pattern that support it. If you apply a policy to a specific component and also apply it to the whole virtual application pattern, the configuration of the component-specific policy overrides the application level policy.

What to do next

In the Pattern Builder, you can make connections between objects on the canvas to define dependencies. For more information, see the documentation for the component that you are editing.
Note: You can also view properties for a component outside of the Pattern Builder by looking at the information for the associated plug-in. Click Cloud > System plug-ins and search for the plug-in that you want to view.
Table 1. Plug-ins associated with Application type components
Component Plug-in
Additional archive file (web application) file
Additional archive file (Java application) javafile
Enterprise application was
Existing Web Service Provider Endpoint webservice
Java application java
Policy Set webservice
web application was
Table 2. Plug-ins associated with Database type components
Component Plug-in
Data Studio web console dswc
Database db2
Existing database (DB2 or Informix) wasdb2
Existing database (Oracle) wasoracle
Existing IMS database imsdb
Table 3. Plug-ins associated with Messaging type components
Component Plug-in
Existing Messaging Service (WebSphere® MQ) wasmqx
Queue (WebSphere MQ) wasmqq
Queue (WebSphere MQ) wasmqt
Table 4. Plug-ins associated with OSGi type components
Component Plug-in
Existing OSGi bundle repository osgirepo
OSGi application was
Table 5. Plug-ins associated with Transaction processing type components
Component Plug-in
Existing CICS Transaction Gateway wasctg
Existing Information Management Systems Transaction Manager imstmra
Table 6. Plug-ins associated with User registry type components
Component Plug-in
Existing User Registry (IBM Tivoli Directory Server or Microsoft Active Directory) wasldap
User Registry tds
Table 7. Plug-ins associated with Other type components
Component Plug-in
Connect Out connect
Connect In connect
Monitored file filemonitor