Scenario - How can you design the fallowing requirements in BW ?

There is an XML with a root element for employment details.

In this XML ,the 'employerDetails' is the root element and its having an repeated attribute 'employeeID'

How can you design the fallowing requirements in BW.

1.Once we recieve this XML ,we need to make it as record in database.

Answer: Queue Reciever--->Parse XML --->JDBC Update/SQL Direct (we can put it in group for JDBC).


2.The employeeID is  unique constraint in database table.So if we want to filter data  before you sent to JDBC ,How can do this in BW?.

Answer: We can use the check point activity to check the duplicate values for employeeID, before sending to JDBC.

3.How can handle the Parse XML Exception in this flow. If there is possible unexpected values occuring in xml some times. But they can resolve the issue if it can process once again.

Answer: To handle this situation we can put Parse XML in JDBC/XA transaction group and  set max redelivery for queue,So it can re- sends the message for execution. if still error exists then the message in  Undelivered queue.

Can we invoke a web service without using SOAP Request Reply activity ?

Yes, we can use Invoke Partner activity. 

The Invoke Partner activity can be used in a Business Works Process Definition to invoke external services over SOAP.

Can we invoke a web service without transport ?

If we will use LOCAL as the End Point type in Service configuration then no need of transport.

End Point type LOCAL - A local endpoint is available to consumers within the same process engine. This type of endpoint provides a highly efficient way for local services to invoke each other without incurring the overhead of using a network transport.

How can we provide Security without using SSL/ HTTPS for web services in tibco bw ?

We can use the Security Policy and Security Policy Association of Policy Palette. 

The Security Policy shared configuration resource specifies a security policy that can be used for inbound or outbound SOAP messages.

How can we make an attribute optional in XML manually without using tibco designer ?

We can do by changing the minOccurs of XSD.

In XSD Schema source ‘minOccurs’ specifies the optional or mandatory.

Example:

  <xs:element name="a" type="xs:string" minOccurs="0"/> 

  <xs:element name="b" type="xs:string" minOccurs="0"/>