|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
The Retrieve Resources activity generates a WSDL file containing a concrete service description of any process definition that has a SOAP Event Source process starter. This allows clients to access the WSDL for a web service that is implemented by a TIBCO ActiveMatrix BusinessWorks process definition. The client can then use the WSDL file to invoke the web service.
This activity is normally used in conjunction with an HTTP Receiver process starter and a Send HTTP Response activity. The HTTP Receiver process starter can receive an HTTP request and pass it along to the Retrieve Resources activity. When a request is made to retrieve a WSDL file for a process definition that has a SOAP Event Source process starter, Retrieve Resources creates a WSDL file dynamically. This file contains the concrete service definition of the specified BusinessWorks process definition. The WSDL file or other requested resources are then placed into the output for this activity.Figure 26 illustrates a process definition using the Retrieve Resources activity.
When sending the HTTP response, set the Headers/Content-Type item on the Input tab to the appropriate type for the type of resource retrieved. Use "text/xml" when this activity is used to retrieve a WSDL file. See Format of URLs for HTTP Requests for more information on the format of the URL for the HTTP request for retrieving resources.If you want to test a process definition containing this activity, you must load the process definition containing this activity along with the process definition containing the SOAP Event Source process starter into the test window. For more information about loading multiple process definitions when testing, see TIBCO ActiveMatrix BusinessWorks Process Design.
•
•
•
Note: Any special characters in the path or resource name (such as &, =, or space) are mangled in the generated WSDL file. It is a good idea to avoid special characters in the folder and resource names. If you are retrieving other resources (such as XSD files, images, and so on), specify the name of the resource, such as mySchema.xsd, myProcess.process, or myImage.gif.
See TIBCO ActiveMatrix BusinessWorks Process Design for more information about mapping and transforming input data.
This overrides to the <path> and <resourceName> portion of the incoming HTTP request that is used to retrieve TIBCO ActiveMatrix BusinessWorks resources. See Format of URLs for HTTP Requests for a description of the URL format for HTTP requests. Note: This value is used when creating the import statements (WSDL descriptions, WSIL, and XSDs). The port number to specify for the concrete service endpoint in the dynamically generated WSDL file.Note: This value is used when creating the import statements (WSDL descriptions, WSIL, and XSDs).
The Error Output tab lists the possible exceptions that can be thrown by this activity. See TIBCO ActiveMatrix BusinessWorks Error Codes for more information about error codes and corrective action to take.
This feature enables the BusinessWorks engine to listen on a configured port and retrieve resources such as a WSDL file, XSD file, Process file, Image file, and so on. This out-of-the-box solution performs tasks similar to that of the Retrieve Resource activity, but eliminates the need to create a process definition to use the Retrieve Resource activity. Refer to Figure 26, Process definition using the Retrieve Resources activity for details about the process definition.This property specifies the Identity resource that contains the HTTP Server’s digital certificate and private key. This property is available when the bw.platform.services.retreiveresources.isSecure property is set to true.
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |