Client Request nodes provide a way for a client to make a request to a business process.
The tasks you must complete to design a Client Request node include:
Your business process is displayed in the Design View.
Note: As you drag your selection onto the Design View, targets appear on your business process. Each target represents a location in the flow where you can place the node. As you drag the node near a location, the target is activated and the cursor changes to an arrow . When this happens, you can release the mouse button and the node snaps to the business process at the location indicated by the active target. If the location you chose is not a valid one, an will appear next to your node. If you place your cursor over this icon,WebLogic Workshop will display a message about the violation.
The Client Request node is displayed in your business process in the Design View.
Note the following properties for the Client Request node:
After you add any node to your business process, you can design its properties and behavior by invoking the node builder and completing the tasks appropriate for that node. The following sections describe how to complete the design of interactions with clients in your Client Request nodes:
To Specify General Settings
The node builder is displayed. It contains two tabs: General Settings and Receive Data.
The name you assign to the method is the name of the method that is exposed via the Web Services Description Language (WSDL) when you make your business process available as a Web service. To learn more about how the methods in your project are exposed to clients, see Components of Your Application.
Lists the XML Schemas that are available in your business process project and the untyped XMLObject and XMLObjectList data types. To learn how to import a Schema into your project, see Importing Files into the Schemas Project.
Lists the Message Format Language (MFL) files available in your business process project and the untyped RawData data type. WebLogic Integration uses a metadata language called Message Format Language (MFL), based on XML, to describe the structure of non-XML data. Every MFL file available in your project is listed in Non-XML Types. Note that an XML Schema representation of each MFL file is built by WebLogic Workshop and is also available in the XML Types listing.
For more detailed descriptions of the data types, see Working with Data Types.
After you select a data type, the field is populated with the parameter types you added in the preceding steps.
Note: If you selected a typed XML or typed non-XML data type in the previous steps, you can select the Validate box to have the incoming message validated against your specified schema before the message is received by the node. For more information about schemas, see Validating Schemas and Importing Files into the Schemas Project.
To Specify Receive Data
This tab allows you to define one or more variables to hold the data your business process receives from clients.
The Client Sends field is populated with the parameter(s) you specified on the General Settings tab.
The node builder transformation screen is displayed with the data types expected by your method displayed in the Client Sends pane.
Note: To remove a variable from the node builder pane, select the variable in the list and then click Remove. This action removes the variable from the node builder, not from your business process. The variable is still included in your business process; it is visible in the Variables pane in the Data Palette.
When designing a business process, you use a Transformation to create maps between disparate data types. Your project must contain an instance of a Transformation control (defined by a DTF file) for you to create the map.
The mapping tool displays a representation of the source schema and target schema in Source and Target panes. You can create a map between the data type of the method parameter and the data type of the variable, or variables, to which you assign the data. To learn how to create and test a map using the mapping tool, see Guide to Data Transformation.
Note: To return to node builder, in the Application pane, double-click the JPD file.
In the Design View, the icon indicates that you completed the configuration and design of this node.
Note: To learn about changing the configuration you design in the Transformation pane of a node builder, see About Editing Node Configurations.
The names that you assign to methods on your Client Request nodes correspond to the names of the methods that are exposed via the Web Services Description Language (WSDL) when you make your business process available as a Web service. The name must be a valid Java class name.
Sending Messages to Clients
Buffering Client Messages
Client Operations and Control Communication Methods
Adding Message Paths
Adding Timeout Paths