Sunday, March 16, 2014

Monitoring Messages in TIBCO EMS

  • You can monitor messages processed by a destination as they are sent, received, or acknowledged
  • The $sys.monitor topic for monitoring messages has the following format. $sys.monitor.(D).(E).(destinationName). Where D is the type of destination, E is the event you wish to monitor, and destinationName is the name of the destination whose messages you wish to monitor.


Sunday, February 23, 2014

what is the difference between service and soap pallete in TIBCO BW?

  • The Service resource allows you to create a web service that implements multiple operations offered over multiple transports.
  • where as Soap resource allows you to create a web service that implements single operation over single transport.


Sunday, February 16, 2014

Implementing TIBCO BW Cache and Advantages

  • All the frequently used data can be placed in the cache. 
  • For Example, data frequently used in multiple processes for every page navigation.  Also combo box value drop down also frequently accessing the DB to get the values.
  • To avoid the frequent access db, at the time of server start-up, all these values can be keeping it in Cache for frequent usage.
Also we can setup Cache refresh for every 1 hr or 3 hr to make the updated values available in Cache without restarting the server.

  1. Minimize the DB hit.
  2. Improve the system performance.


Sunday, January 26, 2014

Best practices of Checkpoint activity in TIBCO BW: HTTP, Transactions and CalledProcesses

To know the function of checkpoint Click Here
  • Do not place checkpoint right after a HTTP activity. 
In general, HTTP activities do not require a checkpoint as the socket for the HTTP request is closed when the process engine crashes. So on a restart, HTTP response activity will return an error.
  • Checkpoint should be placed outside of a transaction group
Checkpoint should not be placed within or in parallel to a transaction. Checkpoint activity should be placed outside of any transaction group.
  • You should be aware of the implication of a checkpoint when calling a process from another.
Checkpoints save the state of an entire process instance. By default when a process calls another process, the called process is executed in the same process instance as the calling process.
  1. When a checkpoint occurs in a sub-process, the checkpoint saves the state of the current process instance.
  2. When a checkpoint occurs in a spawned sub-process, the checkpoint saves only the state of the spawned process


Sunday, January 19, 2014

About Checkpoint in TIBCO BW

  • A checkpoint saves the current process data and state so that it can be recovered at a later time in the event of a failure.
  • If a process engine fails, all the process instances can be recovered and resume execution at the location of their last checkpoint in the process definition.
  • Only the most-recent state is saved by a checkpoint. If you have multiple checkpoints in a process, only the state from the last checkpoint is available for recovering the process.
  • If you have checkpoints in your process definition, you must consider the side effects when you change your process definition and redeploy it because the check-pointed data during the previous engine runtime could be loaded into the modified process definition. Thus, the result could be unpredictable.
  • Checkpointing is an expensive operation because the engine’s process data should be written to and read from the database which is IO intensive.
  • The checkpoint data will be written to the database and can be shared between 2 fault tolerant engines.


Wednesday, January 15, 2014

Iteration Group vs For Each Function in TIBCO BW

  • A potential misuse of iteration group is to put an iteration group around a mapping activity, as shown in Figure below. This will decrease the performance if iteration count is  more.
  • It is possible to iterate through the data using an xsl:for-each or xsl:for-each-group statement instead of using a group around a Mapper activity.
  • These functions obviously does not apply if multiple activities must be executed for each iteration.
  • If this is not the case it is much more efficient to use a single mapping activity utilizing the for-each function.


    Sunday, January 12, 2014

    Worked examples of shared variable and job shared Variable in TIBCO BW

    Shared Variables:
    • Shared Variable resource allows sharing data across process instances.
    • All process instances can read and update the data stored in a shared variable.
    • Shared variable is useful if a common set of values needs to be passed across all process instances 
    Example: A list of approval codes. A shared variable can be created to hold the current list of approval codes and create one process definition for setting the codes. You can then retrieve the shared variable in all processes that require the current approval codes.

    Job Shared Variables:
    • A Job Shared Variable resource is similar to a Shared Variable, but data CANNOT be shared across process instances. its scope is limited to the current job (A Job or Instance is nothing but one complete execution from START to END activity in a Process definition).
    • A copy of the variable is created for each new process instance (Variable is Initialized for every Job or Instance ).
    • This type of shared variable is useful for passing data to and from sub-processes without creating an input or output schema for the called process. 
    Example: Get Shared Variable and Set Shared Variable activities should be used to access the data instead of mapping data to a called processes input or output schemas. New process instances receive a copy of the Job Shared Variable, so data cannot be shared across process instances.

    If a called process has the Spawn configuration field checked, a new process instance is created and the process instance receives a new copy of the Job Shared Variable.


    Tuesday, January 7, 2014

    TIBCO iProcess Interview Questions

    To read the topics on TIBCO's product called "TIBCO iProcess" and interview questions Click on TIBCO iProcess Interview questions.

    keep in touch with this blog for daily updates.


    Monday, January 6, 2014

    TIBCO BW Interview questions

    Hi Folks,

    To read the topics on TIBCO's product called "TIBCO ActiveMatrix BusinessWorks"(BW) and interview questions Click on TIBCO BW Interview questions.

    keep in touch with this blog for daily updates.


    Sunday, January 5, 2014

    What is TIBCO iProcess Modeler?

    • The TIBCO iProcess Modeler is used to analysis and document business processes as simple as possible, it is used for visual representation of your business process that is easy to follow and that can be enhanced or modify at any time.
    • The TIBCO iProcess Modeler is automatically started by the TIBCO iProcess Client when you want to create or edit procedures. From the TIBCO iProcess Modeler you can access the Step Definer, which enables you to design the forms for each step in your procedure.
    • Procedures are at the basics of Staffware operations and as a procedure/process definer .You are the one who will decide how to make manual procedures and paper documents into Staffware procedures and forms.
    To know about Tibco iProcess Engine Architecture Click Here.


    Popular Posts

      © Blogger templates The Professional Template by 2008

    Back to TOP