If web service is designed to use HTTP(SOAP over HTTP) as transport then for sure it will need port.

You can use same port for more than one web service but make sure that you use different SOAP action or URL for each web service.

If u want to use JMS(SOAP over JMS) as transport then you will need EMS but port is not required for web services. It will need queues/topics for each web service.


For training on TIBCO BusinessWorks mail us at [email protected]

I have created an EAR file and deployed in Administrator.

I need to add a jar to the class.path.extended variable which is specific to my EAR file.

Solution Description :
We can do this in two ways.

1. We can specify the jar path in prepend to classpath under server settings tabs while deploying thru Admin GUI.

2. Edit the BWEngine.tra to add this jar so that the jar will be added to the classpath when you deploy your EAR.



For training on TIBCO BusinessWorks mail us at [email protected]

Publishing an event to TIBCO EMS topic from BusinessWorks.
We will look at the mechanism to publish the file processing completion events from the FileGateway. The following use case describes the flow.
Trigger: FileGateway finished writing the XML file to the outbound folder.
Flow:
1. FileGateway publishes event to FGW.FILEREADY topic.
2. End of use case.

What we need A target topic
We have configured the TIBCO EMS to address part of this requirement. Refer to this article for details of setting up the topic, user and access control list.

An xml schema for event message
This schema is used by both the producer and the consumer of the event message. The TIBCO BusinessWorks JMS Publish activity will publish the message according to this schema and the consumer will reference this schema when parsing the message.

As usual, create the schema using your favorite xml tool. Here is the completed schema.

view plaincopy to clipboardprint?

1. <?xml version=”1.0″ encoding=”UTF-8″?>
2. <XSD:SCHEMAxmlns:xsd=”http://www.w3.org/2001/XMLSchema&#8221;   xmlns:fgw=”http://soaplayground.kein.com/filegw/fileInfo&#8221; targetnamespace=”http://soaplayground.kein.com/filegw/fileInfo&#8221; elementformdefault=”qualified”>
3. <XSD:ELEMENT name=”fileInfo”>
4. <XSD:COMPLEXTYPE>
5. <XSD:SEQUENCE>
6. <XSD:ELEMENT name=”fileName” ”xsd:string”>
7. <XSD:ELEMENT name=”fileSize” ”xsd:int”>
8. <XSD:ELEMENT name=”fileDateTime” ”xsd:dateTime”>
9. <XSD:ELEMENT name=”transport”>
10. <XSD:COMPLEXTYPE>
11. <XSD:SEQUENCE>
12. <XSD:ELEMENT name=”property” maxoccurs=”unbounded”>
13. <XSD:COMPLEXTYPE>
14. <XSD:ATTRIBUTE name=”name” use=”required”>
15. <XSD:ATTRIBUTE name=”value” use=”required”>
16. </XSD:ATTRIBUTE></XSD:ATTRIBUTE></XSD:COMPLEXTYPE>
17. </XSD:ELEMENT>
18. </XSD:SEQUENCE>
19. <XSD:ATTRIBUTE name=”type” ”xsd:string” use=”required”>
20. </XSD:ATTRIBUTE></XSD:COMPLEXTYPE>
21. </XSD:ELEMENT>
22. </XSD:ELEMENT></XSD:ELEMENT></XSD:ELEMENT></XSD:SEQUENCE>
23. </XSD:COMPLEXTYPE>
24. </XSD:ELEMENT>
25. </XSD:SCHEMA>

<?xml version="1.0" encoding="UTF-8"?>

Import the xml schema into the TIBCO Designer project.

If you haven’t been following the series of articles on FileGateway, you can learn about the FileGateway in the following posts.

• Part 1
• Part 2

A JMS Publish activity in the BusinessWorks process
Here are the steps to add a publish JMS activity into the process
1. Create a JMS Connection shared configuration.
Under the PollEmpsCSV folder, create a JMS Connection. Uncheck the “Use JNDI for Connection Factory” as our consumers will be connecting directly without getting the resource handle from the JNDI. Enter the username and password of the fgwuser.

2. Add a JMS Topic Publisher activity.
In the PollDumpCompletion process, add a JMS Topic Publisher and name it as “PublishEvent”. In the configuration tab, enter “FGW.FILEREADY” in the Destination Topic field. In the “Message Type” dropdown, select “XML Text”.

Create a transition from WriteXMLFile to PublishEvent, and from PublishEvent to End activities.
With PublishEvent activity selected, go to the “Input Editor” tab. Click on the “+” icon and select “XML Element Reference” from the “Content” dropdown. Browse to the schema fileInfo.xsd and select the element “fileInfo”

Go to the “Input” tab, map the fileName, fileSize and fileDateTime elements of the activity input to the corresponding fields of $WriteXMLFile process data.
Duplicate the “property” element of the fileInfo instance to contain additional informations, such as the username and password of the ftp server where the output file is located, the url of the ftp server and so forth. The value of the “transport” element indicates how the output file is hosted. Possible values are ftp, http, https or even a “RESTful file server”?!. Well, the password is in plain-text, not an ideal implementation, but that is a separate exercise!

Here we are, done. A FileGateway that broadcasts the file conversion event to interested parties.



For training on TIBCO BusinessWorks mail us at [email protected]

When uploading service assembly, we can add the service units to two more nodes, that makes you load balanced.
But dont think so you can deploy in FT mode as service units are distributed one.

LB is better than FT in this case.

For training on TIBCO mail us at [email protected]