# Adding Instances of Controls to Your Business Process Project

- To Add an Instance of a Control to Your Business Process Project
- To Edit or Delete an Instance of a Control

To Add an Instance of a Control to Your Business Process Project

Before you can specify the resource with which your business process interacts at this node, you must add an instance of the associated control to your project.

To add an instance of a control to your project:

1. In the Data Palette, click Add on the Controls tab. A drop-down list of controls is displayed. These controls represent the resources with which your business process can interact.

Note: If the Controls tab is not visible in WebLogic Workshop, choose View —> Windows —> Data Palette from the menu bar. Instances of controls already available in your project are displayed in the Controls tab.

2. Select a control from the main controls list or the Integrations Controls drop-down menu.

Note: This table contains information about the standard controls used in WebLogic Integration. Other custom and plug-in controls may be available.

Type of Control | Description
Application View | The Application View control allows WebLogic Workshop Web services and business processes to interact with enterprise applications using simple Java APIs. They allow access to an enterprise application even if they do not know any of the details of the application's implementation.The Application View control provides a means to invoke application view services both synchronously and asynchronously, and start a new business process when an EIS (Enterprise Information System) event occurs. In both the service and event cases, you use XML and mapping tools to interact with the Application View control. It is not necessary to understand the particular protocol or client API for the enterprise application or EIS. Events are delivered using the Message Broker Subscription control. Message Broker integration is provided by publishing all application view events to the Message Broker through its API. Note: The Application View control uses application views defined using the Application Integration Design console provided with WebLogic Integration. The Application View control is available in WebLogic Workshop only if you are licensed to use WebLogic Integration. To learn about Application View controls, application views, and their relationship to enterprise applications, see Application View Control.
Database | Database controls provide simplified access to a relational database, allowing your business process to call Java methods and operate on Java objects that are appropriate to the operations being performed. The Database control automatically performs the translation from Java objects to database queries and vice versa. Each Database control is customized to access a particular database and perform specified operations on that database. A Database control can operate on any database for which an appropriate JDBC (Java Database Connectivity) driver is available and for which a data source is configured in WebLogic Server. To find more information about Database controls, see Database Control.
Dynamic Transformation | The Dynamic Transformation control provides a business process with the ability to dynamically select and invoke a query during run time. Specifically, this control allows a business process to dynamically select a particular XQuery, XSLT, or MFL file at run time. You use this control after creating and testing your XQuery files with the Transformation control during design. To get information about Dynamic Transformation controls, see Dynamic Transformation Control.
ebXML | The ebXML control enables WebLogic Workshop business processes to exchange business messages and data among trading partners via ebXML (Electronic Business using eXtensible Markup Language). ebXML is a business protocol that enables enterprises to conduct business over the Internet. The ebXML control supports both the ebXML 1.0 and ebXML 2.0 messaging services. Note: The ebXML control is available in WebLogic Workshop only if you are licensed to use WebLogic Integration. For more information about ebXML controls, see ebXML Control.
EJB Control | EJB controls provide an interface to an existing EJB. It is a simplified way for your business process to act as a client of an existing EJB. After you create an EJB control, your business process can use it to access the EJB's business methods. The EJB control simplifies the work you need to do to use an EJB; the control manages communication with the EJB, including all JNDI lookup, interface discovery, and EJB instance creation and management. To find more about EJB controls, see EJB Control.
Email | The Email control enables WebLogic Workshop Web services and business processes to send e-mail to a specific destination. The body of the e-mail message can be text (plain, HTML, or XML) or can be an XML object. The control is customizable, allowing you to specify e-mail transmission properties in an annotation or to use dynamic properties passed as an XML variable. To learn more about Email controls, see Email Control.
File | File controls can be used to read and write XML and binary files to a local file system. In addition, through the use of a callback mechanism, the files in a specified directory can be read as they are created in a directory. For more information about File controls, see File Control.
Http | This control enables WebLogic Workshop and business processes to work with HTTP requests and to send responses to a specific URL. It supports two modes for data transfer: GET and POST. By using the GET mode, you can send your business data along with the URL. By using the POST mode, you can send binary, XML, and string documents. You can specify HTTP properties in an annotation, or pass dynamic properties via an XML variable. For more information, see HTTP Control.
JMS | Use this control to send and receive messages via a Java Message Service (JMS) queue or topic that is not involved in exchanging information with enterprise systems though an integration application. Using JMS controls, your business process can interact with any messaging system that provides a JMS implementation. To learn more about JMS controls, see JMS Control. To exchange JMS messages as part of an integration application, you use the WLI JMS. This control is available as part of the integration controls if you have a current WLI license. For more information, see WLI JMS.
Liquid Data | You can use the Liquid Data control in WebLogic Workshop to develop applications that use data from Liquid Data queries. For example, data from Liquid Data queries can be used as an input to business processes. To learn about BEA Liquid Data, see the Liquid Data documentation at http://edocs.bea.com/liquiddata/docs81/index.html. Specifically, to learn about the Liquid Data control, see Using Liquid Data Controls to Develop Workshop Applications.
MB Publish | Message Broker (MB) Publish controls allow your business process to publish messages to Message Broker channels. Publish and subscribe messaging to Message Broker channels is accomplished in similar fashion to publish and subscribe messaging to JMS topics, but a Message Broker channel is optimized for use with BPM (business process management) services. The Message Broker provides typed channels to which messages can be published and to which services can subscribe to receive messages. Message Broker also supports a message filtering capability. For more information about Message Broker Publish controls, see Message Broker Publish Control.
MB Subscription | Message Broker (MB) Subscription controls allow your business process to dynamically register for and receive messages from a Message Broker topic. In WebLogic Integration, subscriptions to Message Broker channels defined at a Start node are referred to as static subscriptions, and subscriptions defined using a Message Broker Subscription control are referred to as dynamic subscriptions. See "Note about Static and Dynamic Subscriptions" in @jpd:mb-static-subscription Annotation. Publish and subscribe messaging to Message Broker channels is accomplished in similar fashion to publish and subscribe messaging to JMS topics, but a Message Broker channel is optimized for use with BPM (business process management) services. The Message Broker provides typed channels to which messages can be published and to which services can subscribe to receive messages. Message Broker also supports a message filtering capability. To learn more about Message Broker Subscription controls, see Message Broker Subscription Control.
MQSeries | The MQSeries control enables WebLogic Workshop business processes to work with MQSeries for sending and receiving messages, to and from MQSeries queues. MQSeries is a middleware product from IBM that runs on multiple platforms and enables applications to send messages to other applications. For more information about the MQSeries control, see MQSeries Control.
Process | A Process control provides an interface to another business process in your project. Using a process control, your business process can invoke the methods and handle the callbacks on another business process. To create a Process control, on the Application tab in the Design View, right-click a business process (JPD) file to display a drop-down menu. Select Generate Process Control File from the drop-down menu. WebLogic Workshop creates a Business Process control file (JCX file) in your project. For more information about Process controls, see Process Control.
RosettaNet | The RosettaNet control enables WebLogic Workshop business processes to exchange business messages and data among trading partners via RosettaNet. RosettaNet is a business protocol that enables enterprises to conduct business over the Internet. Note: The RosettaNet control is available in WebLogic Workshop only if you are licensed to use WebLogic Integration. To learn more about the RosettaNet controls, see RosettaNet Control.
Service Broker | The Service Broker control allows a business process to send requests to and receive callbacks from another business process, a Web service, or a remote Web service defined in a WSDL file. The Service Broker control lets you dynamically set control attributes. This allows you to reconfigure control attributes without having to redeploy the application. To learn more about Service Broker controls, see Service Broker Control.
TPM | The TPM (Trading Partner Management) control provides read-only access to trading partner information stored in the TPM repository. For more information about how to use TPM controls, see TPM Control.
Task | The Task control creates a single Task instance, manages its state and data, and provides callback methods to report status. A Task control identifies intimately with a single Task instance; their relationship is one to one. You generally use a Task control in a JPD file like most other IDE controls. For more information about Task controls, see Worklist Controls.
Task Worker | The Task Worker control assumes ownership of Tasks, works on them, completes them, and provides administrative privileges—starting, stopping, deleting, assigning, and other functionality. Task Worker controls allow operations on several Task instances; the relationship between a Task Worker control and Task instance can be one to many. You generally use a Task Worker control with JSP user interfaces. For more information about Task Worker controls, see Worklist Controls.
Timer | A Timer control notifies your business process when a specified period of time has elapsed or when a specified absolute time has been reached. To learn more about how to work with Timer control, see Timer Control.
Transformation | Use a Transformation to achieve data transformations for data in your business processes. A Transformation is defined in a DTF file, which can be created and edited from within communication nodes in a business process and via the File —> New —> Transformation File option on the WebLogic Workshop menu. To learn more, see Note About Transformations.
Tuxedo | You can include one or multiple Tuxedo services in your business process logic by using a Tuxedo control. By creating connections to Tuxedo services, you can invoke the Tuxedo services and retrieve the responses, and convert your application's Java data types to and from Tuxedo buffer types. To learn about the Tuxedo control, see BEA Tuxedo Control.
Web Service | A Web Service control provides an interface to a Web service, allowing your business process to invoke the methods and handle the callbacks of the Web service. The Web service can be developed with WebLogic Workshop or any Web service for which a WSDL file is available. A Service control is defined in a CTRL file. A specific Service control CTRL file provides a way to communicate with a specific Web service. The name and location of the Web service are specified in the CTRL file. For more information about how to work with and configure Web Service controls, see Web Service Control and Controls and Transactions.
WLI JMS | The WLI JMS Control is an extension for the Workshop JMS control, it is used to exchange JMS messages as part of an integration application. Once a WLI JMS control is defined, Web services and business processes may use it like any other WebLogic Workshop control. For more information, see JMS Control. Note: The WLI JMS control is available in WebLogic Workshop only if you are licensed to use WebLogic Integration.If you do not have a current license, use the JMS control to send and receive messages via JMS. For more information, see JMS.
XML MetaData Cache | The XML MetaData Cache control only allows you to retrieve XML metadata from the XML cache. The XML cache is managed using the WebLogic Integration Administration Console. For more information, see XML MetaData Cache Control.

3. After you select a type of control from the drop-down list in the Controls tab, an Insert Control dialog box, which contains tasks specific for the control you selected, is displayed.
4. In the Insert Control dialog box, enter the information specific for the control you want to create and click Create. To learn about creating and configuring specific controls, see Using Integration Controls.

This step completes the creation of an instance of a specific control in your application. The controls you create are displayed in the Controls tab.

The methods available on the control are shown in the Controls tab.

Note About Transformations

Transformations handle mapping heterogeneous data types in your application. WebLogic Workshop provides a data mapping tool to map between heterogeneous data types. The data transformations you create using the tool are stored in Data Transformation Format (DTF) files. The DTF files can hold multiple transformations and are designed to enable packaging, sharing and reuse of transformation formats. When DTF files containing your data transformations are built, they are built as controls. The controls expose transformation methods, which business processes invoke to map the disparate data types.

In addition to creating Transformations from the Controls tab in the Design View, as described in this section, you can create them in the following ways:

- By choosing File —> New —> Transformation File from the WebLogic Workshop menu.
- By choosing File —> New —> Other File Types —> Processes —> Transformation File from the WebLogic Workshop menu.
- In the node builders for any Control or Client node in your business process. During the design of a node that sends or receives data in your business process, you can create a new Transformation, or write new methods to an existing instance of a Transformation control in your project. In this way you can create new Transformations or Transformation methods on an existing control from within a business process node. To learn about node builders, see Node Builders in How Do I: Use the Design View?

To learn about data transformations in business processes, see Guide to Data Transformation.

To Edit or Delete an Instance of a Control

In the Controls tab, right-click a control to display a drop-down menu. Select Delete or Edit from the menu. When you select Edit, the control, including its methods and callbacks, is displayed in the Design View. Click the Source View tab to view and edit the source code for your control.

Related Topics

Create Control Nodes in Your Business Process

Designing Your Control Nodes

Configuring Control Nodes

Setting Control Properties

Using Integration Controls

Using Built-In Java Controls