Adapter Subscriber

Starts a process based on the receipt of a message from the publication service of the specified adapter. Publication services are configured during adapter configuration, and the activity uses the information in the adapter configuration to fill in most of the fields of this activity. See your adapter documentation for more information about creating adapter configurations and creating adapter publication services. Adapter Subscriber process starter starting a business process.

Adding Custom Hawk Microagents to Your Adapter

To add a custom Hawk Microagent to your adapter, you must edit the adapter’s
XML file.
The following example shows the elements and attributes required for a custom
Hawk Microagent. See the sdk/pubsub example for the actual XML:
+ hawk
- help=Java SDK Example pubsub
- microAgentName=hawkagent
- sessionName = hawkSession
+ method
- help = Retrieve Color Information
- name = getColor (this must match the method name in code)
- type = INFO
+ outputParameter
- help = Color Information
- name = color
- type = string (this must match the method's return
type in code)
+ method
- help = Set Color Information
- name = setColor (this must match the method name in code)
- type = ACTION
+ inputParameter
- help = set color Information
- name = color
- type = string (this must match the method parameter
type in code)

Global Variables
In many fields in the configuration panel, global variables surrounded by %% are
used. In most cases, you can change these global variables using the Global
Variables tab in the project panel.
Do not set values for the %%InstanceId%% and %%AppName%% global variables. The
variables are set at runtime by run-time adapters.

Defining Custom Adapter Schema

If you are configuring an adapter for which no palette is available, or if you are
creating an SDK-based adapter, you can configure Schema resources using the
AESchemas folder.
Defining Schema—Overview
This section gives an overview of the schema definition steps, pointing to other
sections as appropriate.
To define schema for your adapter, follow these steps:
1. In the project tree panel, select the AESchemas folder and double-click the ae folder.
2. From the palette panel, select a Folder resource (General palette) and drag it into the design panel.
3. Name the folder appropriately for your adapter.
4. From the palette panel, select an AESchema resource (Adapter Schemas palette) and drag it into the design panel.

The AESchema resource contains folders for the classes, sequences, etc. to be used by the adapter. Click the + below the resource in the project tree to see the folder hierarchy.

JMS SSL Configuration

You can configure secure transports for TIBCO Enterprise for JMS sessions.
To configure a JMS Session for SSL:
1. Open a project and drag a Generic Adapter Configuration resource into the design panel.
2. Select the Adapter Services folder and drag a Publication Service into the design panel
3. Choose JMS from the Transport Type pop-up, then click Apply.
4. Select the Advanced folder in the left panel to display resources associated with the adapter.
5. Expand the Sessions folder.
6. Select the DefaultJmsTopicSession resource
7. In the configuration panel. Check the Use SSL? option, then click the Configure SSL button.

TIBCO Rendezvous SSL Configuration

You can configure secure transports for TIBCO Rendezvous sessions. This
leverages the new Secure Daemon feature (using SSL) available in TIBCO
Rendezvous 7.0 and later.
The following steps will guide you through an SSL configuration of an RV
publication service as an example. The procedure is very similar for other
services.
To Configure a TIBCO Rendezvous Session for SSL:
1. Open a project and drag the Generic Adapter Configuration palette to the
design panel.
2. Select the Adapter Services folder and drag a Publication Service to the
design panel.
3. Select the Advanced folder in the left panel to display resources associated
with the adapter.
4. Expand the Sessions folder.
5. Select the DefaultRVCMSession resource
6. Check the Use SSL? option, then click the Configure SSL button. This gives
you access to the SSL Configuration option as is shown in Figure

Reading the Content Model Diagram

To view a content model, click the appropriate element in the element/type list (below the diagram). The content model diagram is updated to reflect the currently selected element or type's content model. The content model diagram uses a visual vocabulary to represent complex element content models.
Elements are displayed as objects (in boxes) within the content model diagram. The boxes contain element names, data type indicators, and occurrence indicators. An element’s content model may be composed of text, other elements, text and elements, data, or none of these (as defined in the element definition).
The icons used in the content model diagram are illustrated in Figure .

Which activity is used for detecting duplicate message processing

CheckPoint activity - Specify the uniqueID for the duplicate key field and engine maintains list of these key fields. When a process come to checkpoint activity with the same value for duplicate key which already exists, it throws a DuplicateException. An error transition can then handle this case

 

The Checkpoint activity performs a checkpoint in a running process
instance. 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 process instances can be recovered and resume
execution at the location of their last checkpoint in the process definition. If a
process instance fails due to an unhandled exception or manual termination, it
can optionally be recovered at a later time, if the process engine is configured to
save checkpoint data for failed processes. See TIBCO BusinessWorks Administration
for more information about recovering failed process instances.
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.

SOA – Physical Architecture