Controls: Using Resources from a Web Service

Controls provide a common model to interacting with resources from within a web service. If you access a resource such as a relational database through a control, your interaction with the resource is greatly simplified because the underlying control implementation takes care of most of the details for you.

All controls expose Java interfaces that may be invoked directly from web service code. So you use all controls the same way: you create an instance of the specific control you want to use and then invoke its methods and implement handlers for its callbacks.

All controls except Timer controls are implemented in CTRL files. To learn more about CTRL files, see CTRL Files.

# Control Types

WebLogic Workshop provides the following six types of controls to help you interact with resources:

## Application View Control

The Application View control allows your service to access an enterprise application using an Application View.

For more information on the Application View control, see Application View Control: Accessing an Enterprise Application from a Web Service.

## Timer Control

The Timer control notifies your service when a specified period of time has elapsed or when a specified absolute time has been reached.

For more information on the Timer control, see Timer Control: Using Timers in Your Web Service.

## Service Control

The Service control provides an interface to another web service, allowing a calling service to access the methods and handle the callbacks of the service represented by the Service control.

For more information on the Service control, see Service Control: Using Another Web Service.

## Database Control

The Database control provides simplified access to a relational database, allowing a web service to call Java methods and operate on Java objects that are appropriate to the operations being performed.

For more information on the Database control, see Database Control: Using a Database from Your Web Service.

## EJB (Enterprise Java Bean) Control

The EJB control provides access to an existing Enterprise Java Bean (EJB). Many repetitive details that must be addressed when using EJBs are hidden and automated by an EJB control.

For more information about the EJB control, see EJB Control: Using an Enterprise Java Bean from Your Web Service.

## JMS (Java Message Service) Control

The JMS control proves access to an existing Java Message Service (JMS) queue or topic. Many repetitive details that must be addressed when using JMS queues and topics are hidden and automated by the JMS control.

For more information about the JMS control, see JMS Control: Using Java Message Service Queues and Topics from Your Web Service.

Related Topics

CTRL Files: Implementing Controls