TibcoBE-Development

Tibco B.E 5.2.0
Data Modelling 5.2.0
Decision Manager 5.2.0

of 212
Table of Content
1 Installation................................................................................................................. 3
2 Channels, Events, Destinations, Rules .................................................................. 3
3 Building a CDD file and archive file ...................................................................... 21
4 Starting Project Locally.......................................................................................... 26
5 Running BE engine without default event in channel ........................................ 36
6 Using Schema, Event, Concept............................................................................. 38
7 Output Event ........................................................................................................... 52
8 JMS Channel/Destination....................................................................................... 57
9 JMS Reply Destination........................................................................................... 62
10 JMS destination using routeTo function.............................................................. 65
11 Timer Event Interval Based ................................................................................... 66
12 Timer Event Rule Based......................................................................................... 70
13 Advisory Event........................................................................................................ 78
14 Log Configuration................................................................................................... 85
15 Concepts ................................................................................................................. 86
16 Create An Instance Of Concept From Ontology Function ................................. 94
17 Time to live.............................................................................................................. 96
18 Consuming Events ................................................................................................. 99
19 Contained/Referenced Concept .......................................................................... 100
20 ScoreCard.............................................................................................................. 113
21 RuleFunction......................................................................................................... 117
22 Rank ....................................................................................................................... 117
23 Evaluate As A String ............................................................................................ 122
24 GlobalVariable....................................................................................................... 124
25 Inferencing ............................................................................................................ 126
26 ConflictResolutionCycle ...................................................................................... 126
27 BE SOAP Server ................................................................................................... 126
28 Creating Webservice Using Concrete WSDL..................................................... 141
29 B.E as a client ....................................................................................................... 147
30 B.E invoking a BW WSDL .................................................................................... 155
31 Caching.................................................................................................................. 161
32 Multicast Discovery URLS's ................................................................................ 178
33 Unicast Discovery Url's........................................................................................ 179
34 Listen Url ............................................................................................................... 180
35 Agent Classes ....................................................................................................... 180
36 Datamodelling/Storing Concepts To DB ............................................................ 182
37 Debug Mode .......................................................................................................... 202
38 Decision Manager................................................................................................. 204

of 212
1 Installation
Install B.E 5.1.0
.
2 Channels, Events, Destinations, Rules
First open the B.E studio and create a workspace. This will be a place holder for the code created.
creating a new BE project. By right clicking in the Studio explorer

of 212
Events, Concepts, Rules, Runtime environment, Scorecards are called ontology objects.( ontology is a
formal naming and definition of the types, properties, and interrelationships)
Clients will have to submit a request (event) to the b.e engine.
The point of entry to b.e environment is channel. Clients submit xml request to the be environment
through a channel.
creating a channel

of 212
creating a shared HTTP resource

of 212
Now in the channel browse the HTTP shared resource that was just created

of 212
What we have achieved so far is we have created a connection to a server. At run time the tomcat start up
and the BE engine is creating a connection to the tomcat,
We also have to create destinations. In BE destinations are listeners for the incoming request.(Just like
"JMS Queue Receiver", "Soap Event Source " in tibco BW)
creating a destination

of 212
Now in the Include Event Type
When a client sends an xml string the channel converts it into a BE event this is called Deserializing
Converting Event into outgoing XML string by the channel is called Serializing
We will not select "Is Page Flow" in our case

of 212
Creating an event

of 212
We will look at events in detail below.

of 212
Now we will add properties in the event. If you want to have a great performance of the BE engine you can
communicate only by using properties instead of payload XML.

of 212
Now go back to the channel and select this event that we have created here

of 212
Creating a new Rule

of 212
Now writing the action that rule needs to perform
type "System." studio automatically shows the different functions available that can be used

of 212
3 Building a CDD file and archive file
Cluster deployment descriptor, you will configure your runtime configuration, the values that need to be
passed, whether it is an inference agent or cache agent, what destination should be added, what roles
should be added.

of 212
When deploying an ear you will associate the EAR with a CDD file.

of 212
Adding channels to the CDD

of 212
Below is the inference agent. Processing unit is nothing but the inference agent.

of 212
4 Starting Project Locally

of 212
Configuring the BW client

of 212
BW sent a request but BE did not send a response back.
to get a response back from BE we will tweak the rule.

of 212
rebuild the ear and then run the BE engine locally. Start the BW engine

of 212
5 Running BE engine without default event in channel
rebuild the ear and run the be engine locally and trigger a request from bw
So to over come this problem on the client side we can use the following BE name space

of 212
<Header>
<Name>_nm_</Name>
<Value>customer</Value> (Name of the event)
</Header>
<Header>
<Header>
<Name>_ns_</Name>
<Value>www.tibco.com/be/ontology/Events/customer</Value> (Name space of the event)
</Header>
_ns_ is the name space of the event that you are asking your client to invoke
_nm_ is the name of the event.
Start the BW engine
The request shows up in the BE console

of 212
What this means is BE will expose one destination, but the clients can invoke multiple events to that
destination.
6 Using Schema, Event, Concept
To import a schema into B.E

of 212
Edit the rule function to get data from this xml.

of 212
Rebuild the BE ear and start the BE engine locally
In the BW client add the customer schema and send it in the input body of HTTP post
the request is seen in the BE engine console.

of 212

Creating Concept

of 212
Now in the concept add the concept name that would match the incoming xml tag "OrderType"

of 212
Now edit the rule function.

of 212
Now click on "ctrl" key and click you will be able to browse the concept and map the payload

of 212
Now printing the value of OrderType to console. This value is got from the instance cpt which contains the
"OrderType" value from the Concept
Rebuild the BE ear and start the BE engine locally

of 212
Send a request from the BW client you will see the message from the instance cpt display on the console
for OrderType
We can get the data from an event directly. But using concepts we can write the data to a cache agent..
7 Output Event
Create a new event called OrderEvent
create an instance of the event and map the values

of 212
customer is the instance of incoming event
ord1 is the instance of outgoing event
rebuild the ear and start the b.e engine locally

of 212
Advantage of B.E is it has a powerful rule engine, at run time the rules with higher priority and ranking will
take a priority.

of 212
8 JMS Channel/Destination

of 212
Create a shared JMS connection resource
Plugin the ems details and test connection

of 212
the error means the jms.jar file is not in the BE libraries
Copy the jms.jar/tibjms.jar files to the tpcl folder
restart your studio

of 212
Browse the connection that has just been created
rebuild the CDD file add this channel

of 212
rebuild ear. Start the BE engine
Build the JMS client
create JMS application properties
the message shows up in the BE studio console

of 212
9 JMS Reply Destination
Create a new JMS reply destination
In the order event select the reply destination that was just created

of 212
Send a JMS message from the client
message shows up in BE
and the Order event sends out the message to the default outgoing destination

of 212
the message is picked up by BW JMS receiver.
10 JMS destination using routeTo function

of 212
rebuild the ear and start BE trigger the bw client
11 Timer Event Interval Based
Events are created in a cyclic manner at given intervals.
create a timer event

of 212
Create a rule that fires when the Timer event that was just created gets asserted into BE memory
Update the CDD file with the new rule

of 212
Build the ear and start the BE engine locally

of 212
thereafter for every 15 seconds an event gets created.
12 Timer Event Rule Based
Change the Timer event to rule based.

of 212
enable CatalogFunctions to show up in B.E if not already visible

of 212
now in the Timer rule add a condition with the closure string
build the ear and start BE engine
trigger a request.

of 212
Once the request is triggered you will see that the Customer rule gets fired which will trigger the timer
event. But it won't get asserted into the memory since the ClosureString do not match
Now edit the closer string to a different value in the "TimerEvent" and "CustomerRule"

of 212
trigger a request from BW

of 212
to map a value from incoming payload, it can be done as shown below

of 212
13 Advisory Event
When ever there is an issue that occurs in BE, the advisory event get created and gets asserted into BE
engine. If there are any rules listening for this event those rules get triggered.
AdvisoryEvents need not be created they will be asserted into the BE memory automatically by the BE
engine.
create a rule

of 212
to create this advisory event let us generate an error

of 212
rebuild the CDD
build and run the be.ear. Trigger a message from BW client

of 212
Sending an Advisory event to a JMS queue. Create an Event

of 212
create a new JMS destination

of 212
add this advisory event to the send Advisory event

of 212
Once the destination is added into the Event. we will have to sendEvent
Build ear and run locally, trigger a JMS message from BW.
Create a BW JMS Receiver that will get a message from the BE jms channel created.

of 212
14 Log Configuration
the log get created in the working directory folder

of 212
15 Concepts
Concepts are place holders.
In BW we create mapper/SharedVariables, which are place holders, you don't store the data in concept but
will let you add incoming values to your concept and store in memory or if needed then persist them to DB.

of 212
Create a new event
Create a new Rule add a declaration

of 212
create a new JMS channel

of 212
create ear and run the BW client.
16 Create An Instance Of Concept From Ontology Function
In the point 15 the values for the concept were instantiated manually, here we are going to see to create
them from ontology functions.

of 212
Rebuild the ear and run the BW client

of 212
17 Time to live
-1 the event never expires
0 the event expires at the end of RTC
+ number the event expires after set number of seconds (+1 after 1 second, +10 after 10 seconds)

of 212
rebuild the ear and run the BE engine and BW client

of 212
18 Consuming Events
build ear and trigger bw client

of 212
19 Contained/Referenced Concept

of 212
ContainedConcept :- Say there are two concepts "A" and "B". Concept "B" can be contained inside
concept "A", concept "A" is called Container/ParentConcept and "B" is called child concept.
RefrencedConcept :- Say there are two concepts "A" and "C". Concept "A" refers concept "C", put both
are in different locations not on the same RAM, which means A is referring concept C.
Create three concepts

of 212
1)
2)
3)
Now in the concept "CustomerInfo" the property "CustomerDetails" will contain the "CustomerDetails"
concept

of 212
Now in the concept "CustomerDetails" the property "Address" will reference the "Address" concept

of 212
create a simple event matching the properties in the concepts.

of 212
Create a rule
Add the address concept first in the rule

of 212
Next add the CustomerDetails concept

of 212
create a JMS destination and add the EVENT
redo the CDD
rebuild the EAR and send a request from BW

of 212
20 ScoreCard
The main difference between Concept and ScoreCard is scorecard has no inheritance type

of 212
using the score card value in rule
Now create a rule function

of 212
21 RuleFunction
RuleFunctions can be used to group a bunch of common actions together to be used inside a rule. Fore
example say you want to log ever event to a file, the logic can be maintained in a RuleFunction and then
called in the rule. Startup and Shutdown functions can be mentioned inside the rule function.
22 Rank
Say there are two rules that are going to get triggered due to same event and also have the same priority,
in that case if you want to have the say in which rule first gets triggered you will use RuleFunction.

of 212
create a RuleFunction that will return a double value (Rank can be 1,2,3 or 1.1,1.2,1.3,1.4)

of 212
creating another RuleFunction and adding to second rule having same event and priority value.
adding the RuleFunction to the priority in the rule

of 212
Build the ear and trigger a request, the Rule with the higher rank get executed first (Rank 4 vs Rank 3)
23 Evaluate As A String
To use an xpath function such as dateTime() as a string.

of 212
24 GlobalVariable
GlobalVariablesView you can look at the current global variables in the project
GlobalVariablesEditor you can edit the global variables in the project.
creating a GV

of 212
adding GV in project

of 212
25 Inferencing
Pre-RTC
Messages are received through Channels with specified destinations.
Event PreProcessor is executed first (if it exists in the project).
RTC
Incoming message is converted to an event.
Rules are triggered based on event.
Post-RTC
Acknowledge message, Write to Cache.
26 ConflictResolutionCycle
A rule agenda that get created based on the multiple rules that needs to be executed. Once all the rules in
a RuleAgenda are executed based on the configurations/priority/ranking then it is stated as one
ConflictResolutionCycle is completed.
27 BE SOAP Server
Create a new project

of 212
import a schema into BE
create a Event

of 212
this event was to receive the webservice request.
Now create an event that will send the response.

of 212
create a new HTTP connection

of 212
add the http connection to the channel and create a destination
now create a rule function

of 212
creating a CDD file

of 212
exporting WSDL

of 212
now import the wsdl into a BW client

of 212
build EAR and run the BE engine

of 212
28 Creating Webservice Using Concrete WSDL.

of 212
create a new CDD file

of 212
build a new ear
and start the BE engine.
Export the WSDL from BE

of 212
Import the WSDL into BW client and trigger a request

of 212
b.e sends the response back to b.w.
29 B.E as a client
Create a webservice receiver in b.w using soap event source.
use the WSDL created in point 27

of 212
now creating a connection object in B.E
creating a send request

of 212
endpoint URL is
http://localhost:7786/TibcoBEClient/SOAPEventSource

of 212
Adding SOAP Action
/TibcoBEClient/SOAPEventSource
A SOAPAction property needs to be added in the input event.

of 212
now in the RuleFunction/EventPreprocessor we need to add the SOAPAction value.

of 212
adding the response event

of 212
30 B.E invoking a BW WSDL
Create a WebService in BW which will add two numbers. Then import this WSDL into B.E

of 212
now in the request event comment out the request event in declaration we will use timer event.

of 212
now we need to capture the response for which we will have to do a HTTP.sendrequest(String url,
SimpleEvent requestEvent, String responseEventURI, long timeoutMillis, Object httpConnectionInfo)

of 212
build a CDD file
build the ear.
Run be engine.
Every 15 seconds the timer event gets triggered and sends a webservice call.

of 212
31 Caching
Concept data can be stored in cache. In the backend B.E uses activespaces to store cache.
Cache is JMV only store. The cache can also be stored in backend DB, for data persistence.
inferenceEngine > cacheAgent(seeder(store and provides data from database)).
Channels will not get activated until one cache agent is not available in the cluster. It is always a good
practice to start the cache agent first then inference agent.
Before we proceed further with caching. Create a simple http project with request reply event and a bw
client.

of 212
now create a new CDD and select ObjectManagement as "Cache"

of 212
below are important properties of caching

of 212
create a concept with a customerName

of 212
edit the rule function

of 212
now build the cdd first with the following options

of 212
save the CDD
build the ear.
first start the cache agent
the cache server becomes activated

of 212
now start the inference agent by selecting the default processing unit

of 212
you will see two agents running.
trigger a request from BW the concept will get created

of 212
if a concept with the same extId is present in memory then new instances of that concept won't be created.
To check if an instance of a concept is already existing in memory we need to do the following.

of 212
rebuild the ear. And trigger request from BW.

of 212
Active space monitoring tool can used view the cache.
32 Multicast Discovery URLS's
There are two types of discovery url's Multicast(by default be uses Multicast) and Unicast
Multicast:- tibpgm://destinationport/network
tibpgm://7888/;239.8.8.9
tibpgm://7888/10.1.2.3;239.8.8.9

of 212
33 Unicast Discovery Url's
There are two types of discovery url's Multicast(by default be uses Multicast) and Unicast
If there are four engines in cluster then you will have to give the url as follows. (3 inference agents and 1
cache agent)
unicast:- tcp://10.1.2.3.4:7888,tcp://10.1.2.3.5:7888,tcp://10.1.2.3.6:7888;tcp://10.1.2.3.7:7888

of 212
34 Listen Url
35 Agent Classes

of 212
36 Datamodelling/Storing Concepts To DB
For this part we will also need the data modelling to be installed
Once the DataModeling is installed you will be able to see it in studio

of 212
First make sure the necessary DB jar file is copied to the tpcl folder.
Copy the ojdbc6.jar to the tpcl folder in case you are using oracle DB
Create a shared DB connection in shared resources

of 212
now create a Database Concept.

of 212
create a new rule

of 212
inserting the concept properties to the DB

of 212
changed the Event in default destination
/Events/TIBCO/CUSTOMER

of 212
build the ear and start the BE inference and cache engine

of 212
build the BW client and trigger a request
check the DB table you will see the value will be inserted into DB

of 212
Now retrieving a concept from DB

of 212
build ear, run cache and inference engines send a request from BW
37 Debug Mode

of 212
38 Decision Manager
First install the decision manager
create a rule function

of 212
a virtual rule function that is created will have a symbol "v"

of 212
now create a new decision table

of 212
now create a rule

of 212
build the cdd, ear, run your b.e engine and trigger a bw request
but the value gets printed from DecisionTable

TibcoBE-Development

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (9)

Similaire à TibcoBE-Development

Similaire à TibcoBE-Development (20)

TibcoBE-Development