Saturday, November 20, 2010

General procedure to create Web service in TIBCO

  1. Create XSDs to define the input, output, and fault messages for the web service.
  2. Create a WSDL File resource that defines the interface to the web service.
  3. Create a process definition that performs the work of the web service. Use the SOAP Event Source process starter for this process definition. Use the SOAP Send Reply activity to return a reply or the SOAP Send Fault activity to return a fault to the client.
  4. Create a process definition that retrieves the concrete WSDL file and sends it to web service clients. Use the HTTP Receiver process starter and the Retrieve Resources activity for this process definition.


Sunday, November 14, 2010

Redeploying an Application: Changes Made to EAR and Deployment Files

If you change both the TIBCO Designer project and the deployment configuration file, you must upload both when redeploying. For example, you may want to make the following changes:
  • add new services or delete existing services (adapter, process or form flow archives)
  • add or remove deployment level or service level variables (including Adapter SDK properties)
  • change checkpoint storage from File to JDBC or JDBC to JDBC, where the new JDBC Shared Resource was not part of the Shared Archive in the original EAR file

If you have changed both the TIBCO Designer project and the deployment configuration file, complete the following steps to redeploy the changed application:

  1. Build an EAR file using the buildear utility. For example:buildear -s -ear /filenotify.archive
  2. Generate a new deployment configuration file using the EAR file created in the previous step, the deployment configuration file used when previously deploying the application and specify a new deployment configuration file.
  3. After you have made the changes to your deployment configuration file, you are ready to deploy the application.


Popular Posts

  © Blogger templates The Professional Template by 2008

Back to TOP