We are trying to explain each and every activity in depth, so stay tuned to this site. This Site is Under Construction!!!

Thursday, August 9, 2012

Soap Send Fault Activity

The SOAP Send Fault activity sends a SOAP fault to the client if an error occurs during processing of a SOAP request. This activity is used when the SOAP Event Source process starter handles incoming SOAP requests. The WSDL file for the request can have one or more fault messages defined for an operation. The SOAP Send Fault activity can use the fault schema to send application-specific data about the fault back to the client that made the SOAP request. This activity cannot be used if the SOAP request is one way. SOAP faults are required to send the fault code and the fault string. These values are required input items on the Input tab. For example, "Client" can be used for client faults and "Server" can be used for server faults. See the SOAP specification at www.w3.org/TR/SOAP for more information about the syntax of SOAP fault codes.

Soap Request Reply Activity

The SOAP Request Reply activity performs a request on the specified web service and optionally expects a reply from the web service. You can invoke both document and RPC web services with this activity.

Soap Event Source Activity

The SOAP Event Source process starter creates a process instance for incoming SOAP requests. SOAP is a standard protocol for invoking web services. This allows you to create a web service using process definitions. At runtime, a client can retrieve the WSDL file for a process containing this process starter using an HTTP request. Once the WSDL file is retrieved, the client can perform a SOAP request to invoke the web service.

Retrieve Resources Activity

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. The Retrieve Resources activity can also be used to retrieve any other resources, including XSDs and WSIL. Using Retrieve Resources 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. You can then pass the output of the Retrieve Resources activity to the Send HTTP Response activity to send the response back to the requestor.

Rendezvous Transport Activity

The Rendezvous Transport resource describes a TIBCO Rendezvous transport. This resource is used when specifying activities from the Rendezvous palette.

Wait for Rendezvous Message Activity

The Wait for Rendezvous Message activity waits to receive a TIBCO Rendezvous message with the given subject.

Send Rendezvous Request Activity

The Send Rendezvous Request activity publishes a TIBCO Rendezvous message on the given subject with the given message content, and it expects a reply to the message on the given reply subject and with the given reply message content. This activity waits for a reply on the reply subject and outputs the content of the reply.

Reply to Rendezvous Request Activity

The Reply to Rendezvous Request activity is used to send a reply to a received TIBCO Rendezvous message.

Rendezvous Subscriber Activity

The Rendezvous Subscriber process starter creates a process when a TIBCO Rendezvous message on the given subject is received.

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More