TIBCO BWS

1.What are the modes of TIBCO BW Installations ? GUI mode Console mode Silent mode

2. If you have installed a particular version of TIBCO software e.g. TIBCO BW X.Y.Z, What are X, Y and Z number stands for? Integration can be at different application layers: X:Patch Y:Major Z:Minor

3. What is the role of TRA? TRA stands for TIBCO Runtime Agent. The TRA has two main functions: Supplies an agent that is running in the background on each machine. 1. The agent is responsible for starting and stopping processes that run on a machine according to the deployment information. 2. The agent monitors the machine. That information is then visible via TIBCO Administrator. Supplies the run-time environment, that is, all shared libraries including third-party libraries.

4. What are the resources that gets included in the EAR file, created by the TIBCO Designer? An EAR file can contain local project resources, LibraryBuilder resources, and files as specified in AliasLibrary resources. In addition, the TIBCO Designer classpath may include references to other files that are included in the EAR file.

5. What are the revision control system options available in TIBCO designer?

File sharing VSS Perforce XML Canon ClearCase iPlanet CVS PVCS

6. What are the different modes of service invocation? Services can be invoked in several ways. A one-way operation is executed once and does not wait for a response. A request-response operation is executed once and waits for one response. In a request-response service, communication flows in both directions. The complete interaction consists of two point-to-point messagesa request and a response. The interaction is only considered complete after the response has arrived. Publication (notification) means an operation sends information on an as-needed basis, potentially multiple times. Subscription means incoming information is processed on an as-needed basis, potentially multiple times.

7. What is vcrepo.dat? TIBCO Designer creates a file named vcrepo.dat in the project root directory when you first save the project. This file is used to store properties such as display name, TIBCO Rendezvous encoding, and description. This file can be used for identification in place of the project root directory and can be used as the repository locator string (repoUrl). 8. What are the TIBCO BW activities that can participate in transactions? Not all TIBCO BusinessWorks activities can participate in a transaction. Only the following types of activities have transactional capabilities: JDBC activities JMS activities ActiveEnterprise Adapter activities that use JMS transports EJB activities TIBCO iProcess BusinessWorks Connector activities

9. What are the different types of Transactions TIBCO provides? TIBCO BusinessWorks offers a variety of types of transactions that can be used in different situations. You can use the type of transaction that suits the needs of your integration project. When you create a transaction group, you must specify the type of transaction. TIBCO BusinessWorks supports the following types of transactions: JDBC Java Transaction API (JTA) UserTransaction XA Transaction

10. What activities are supported in JTA Transaction? The Java Transaction API (JTA) UserTransaction type allows: JDBC

JMS ActiveEnterprise Adapter (using JMS transports) EJB activities

to participate in transactions.

11. What activities are supported in XA Transaction ? The XA Transaction type allows: JDBC activities ActiveEnterprise Adapter activities that use the JMS transport JMS activities

to participate in transactions. Note:For JMS activities and ActiveEnterprise Adapter activities, request/reply operations cannot participate in an XA transaction. Also, EJB activities cannot participate in an XA Transaction group. 12. What are the possible Error output's of Read File activity? Integration can be at different application layers: FileNotFoundException :Thrown when yhe file does not exist. UnsupportedEncodingException:Thrown when the text files encoding is not valid and the content of the file is read into process data. FileIOException :Thrown when an I/O exception occurred when trying to read the file.

13. What is the purpose of the inspector activity ? The Inspector activity is used to write the output of any or all activities and process variables to a file and/or stdout. This is particularly useful when debugging process definitions and you wish to see the entire schema instead of mapping specific elements to the Write File activity. 14. What are the maximum/minimum of threads available for incoming HTTP ? The maximum/minimum of threads available for incoming HTTP : 75/10 15. How can unauthorized users be prevented from triggering a process ? Unauthorized users be prevented from triggering a process by giving 'write' access for the process engine to only selected users. Only users with 'write' access can do activities like deploying applications, starting/stopping process engines etc. 16. What are the mandatory configuration parameters for FTP Connection & FTP with firewall ? The mandatory configuration parameters for FTP Connection FTP host Port Username & Password>

If Firewall is enabled in addition the proxy host and port are required. 17. how to design a process such that depending on number of records updated in a database, 3 different subprocesses may be called ? Define 3 transitions from JDBC update with condition on the no of updates and call appropriate child processes.

18. How to use legacy .dat file format with latest designer ? Convert .dat file to multi file project using Administration tab while starting up Designer(Other one being Project tab) and then open the multifile project in the normal way. 19. What are the encodings supported by designer? Encodings supported by designer are ISO8859-1(Latin-1) UTF-8

20. What are the 4 main panels of the Designer window ? The 4 main panels of the Designer window are Project panel Palette panel Design panel Configuration panel

21. How do you determine if there are broken references in the project? Project -> Validate for deployment 22. Where are the Designer preferences stored? Designer preferences stored are stores in a file called 'Designer <ver>.prefs' in the user home directory. 23. Explain the process configuration parameters - Max Jobs, Flow Limit & Activation Limit ? Max Jobs : Max Jobs specifies the number of process instances that are kept in memmory. Once this limit is reached newly created process instances (subject to flow limit) are paged out to disk.0 specifies no limit and is the default. Flow Limit : Flow Limit specifies the maximum number of running process instances that are spawned before the process starter is suspended ie it enters a FLOW_CONTROLLED state and does not accept new events. This can be used to control the number of process instances running simultaneously and when the protocol generating the event can store the event till it is received, like email servers, JMS, RV etc. 0 specifies no limit and is the default. Activation Limit : Activation limit flag specifies that once a process instance is loaded it must be placed in memory till it completes execution. By default it is enabled. 24. What are the options for configuring storage for process engine's checkpoint repository ? The options for configuring storage for process engine's checkpoint repository are:

Local File Database. Fault tolerant engines can recover from a checkpoint only when database is used.

25. Process engines in a fault tolerant group can be configured as peers or master secondary. How do these differ? The options for configuring storage for process engine's checkpoint repository are: - Peer means all of them have the same weight. In this case when one engine fails another one takes over and continues processing till it fails. - In master secondary configuration weights are unequal, the secondary starts processing when master fails. But when master recovers, secondary stops and master continues processing.

26. What are the uses of grouping activities ? Uses of grouping activities are: Create a set of activities having a common error transition. Repeat group of activities based on a condition. 1. - Iterate over a list. 2. - Repeat until condition true. 3. - Repeat on Error until condition true. Group activities into a transaction. To create a critical section area that synchronizes process instances. A 'Pick First Group' allows you to wait for the occurence of multiple events and proceed along a path following the first event to occur.

27. What is the purpose of a Lock shared configuration resource? A Lock is specified for a 'Critical Section' group when the scope is 'Multiple'. It can be used to ensure synchronization across process instances belonging to multiple processs definitions or for process instances across engines(Check multi engine flag for lock in this case and the BW engine needs to be configured with database persistence while deployment). If synchronization is for process instances belonging to the same process definition inside one engine, just specify the scope as 'Single'. 28. How to control the sequence of execution of process instances created by a process starter? Use the sequencing key field in the Misc tab of any process starter. Process instances with the same value for this field are executed in the sequence in which they are started. 29. Can there be two error transitions out of an activity? No. There can be only one Error and one Success if no matching condition transition out of each activity. 30. When is a 'No Action' group used? 'No Action' group used to have a set of activities having a common error transition 31. What activity can be used to set the value of a 'User defined process variable' ? The 'Assign' activity can be used to set the value of a 'User defined process variable'. 32. Which are the two process variables available to all activities with inputs ? $_globalVariables $_processContext

32. Which mechanism can be used to pass data between a process instance and a called sub process other than mapping from/to the callee's input/output? This can be accomplished using job shared variables, unless in the call process activity the 'Spawn' flag is enabled in which case the called sub process is a new job and hence gets a fresh copy of the job shared variable initialized as per its configuration. A shared variable can overcome this limitation as it's scope is not limited to one job. 34. What are the three scenarios where BW engine has to be configured with database persistence instead of Local File? The three scenarios are: Shared Variables across BW engines. Locking across groups in multiple BW engines. Wait Notify across BW engines.

35. If you want a group to be executed if there is some unhandled error but subject to some max number of iterations which group do you use? We can use Repeat on Error until true 36. When is a 'Generate Error' activity useful? When you handle an error inside a called subprocess or group and want to rethrow the error to the caller (happens by default if you dont handle the error in the called process) 37. 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 comes 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. 38. Give an example where graceful migration of service from one machine to another is not possible. HTTP Receiver. In this case the receiver on new machine starts listening on the same port, but you need to redirect requests from the old machine to the new one. 39. What are the types of adapter services ? Types of adapter services are: Subscriber Service Publisher Service Request-Response Service Request-Response Invocation Service

40. If the business process needs to invoke another web service which resource do you use? SOAP request reply activity. If the business process needs to be exposed as SOAP service use SOAP Event Source in conjunction with SOAP Send Reply or SOAP Send Fault. 41. What is the functionality of the Retrieve Resources resource? It can be used to serve the wsdl file of a SOAP Event Source to a (http) client. Construct a process like: HTTP Receiver -> Retrieve Resources -> Send HTTP Response

Now the WSDL file for a SOAP service can be retrieved using the http request
http://<host>:<port>/<path>/<resourceName>?wsdl

where 'path' is the folder path to the SOAP Event Source process and 'resourceName' is the name of the process Example: http://purch:8877/Purchasing/GetPurchaseOrder?wsdl 42. What is the scope of user defined process variables? The scope of user defined process variables is only the process in which it is defined. (Not even inside a sub process that is invoked from this process) 42. What is difference between shared variable and job shared variable? Both of them can be manipulated via the palette resources 'Get shared variable' and 'Set shared variable'. A job shared variable is private to one instance of job or in other words each job has a fresh copy. In the case of shared variable the same copy is shared across all job instances. It can even be persisted and can survive BW engine restarts and even shared across multiple BW engines(when deployed using DB persistence).

44. How do wait-notify resources work ?

Basically wait and notify should share a common notification configuration which is just a schema definition for data that will be passed from notifier to waiter. Specific instances of waiter & notifier are corrrelated via a key. For example: when one process is in wait state for key 'Order-1', it waits till another process issues a notification with the same key value.

45. What is the default Axis in XPath ?

Child axis- What this means is that when you select "BOOK" from the current context, it selects a child node with that name, not a sibling with that name. Other axes are parent , self , sibling etc.

46. What are the output formats for XSLT?

XML HTML Text

47. What does ' Success if no matching condition' transition mean ?

Lets say between two nodes N1 and N2, there are 3 success transitions with condition and there is no success transition without condition. If none of the conditions match then a 'Success if no matching condition' transition can be used. Also if there is a success transition and also success transitions with condition and if the condition matches then both the success transition (no condition) as well as the transition(s) with matching conditions are followed. So you can use 'Success if no matching condition' to prevent duplicate paths of execution.

48. What is the Purpose of $_error variable?

$_error variable is available in the node following the error transition. It captures the error message, error code etc.

49. What are the cases where business process cant proceed correctly subsequent to restart from a checkpoint
? Sending HTTP response, confirming an email/jms message etc. This is because the confirmation or sending HTTP response has to done in the same session. When engine crashes these sessions are closed at their socket level. In such cases send response/confirm before checkpoint.

50. Which group do you use to wait for multiple events and proceed with the first to occur ?
A 'Pick First Group'.

These are some notes I have written in order to help myself to get ready to clear the TIBCO ActiveMatrix BusinessWorks 5 Certification Exam (TB0-123). More details about the exam, click here. This entry is about TIBCO BW Concepts document. Any comment or suggestion, please write toluisagcenteno@gmail.com. Further details can be found at TIBCO Documentation. I hope these notes can help you as well as they did to me... TIBCO ActiveMatrix BusinessWorks Notes - TIBCO ActiveMatrix is a scalable, extensible and easy to use integration platform that allows development of integration projects. - Integration platform requirements. - Short Development Cycle - Scalability and Extensibility - Ease of use - TIBCO ActiveMatrix BusinessWorks prerrequisites - TIBCO Runtime Agent -TIBCO Designer - TIBCO Administrator - TIBCO ActiveMatrix BusinessWorks engine runs the business process in test mode and at run-time. - TIBCO ActiveMatrix BusinessWorks Service Container hosts multiple application simultaneously. - TIBCO ActiveMatrix BusinessWorks design-time plug-in provides the palettes and resources to TIBCO Designer for creating processes. -TIBCO ActiveMatrix BusinessWorks was designed using a plug-in architecture. -TIBCO Administration domain is a collection of users, machines, and TIBCO ActiveMatrix BusinessWorks components that a TIBCO Administration Server monitors and manages. - There is only one Administration Server for each administration domain. - Although components within an administration domain can communicate with systems outside the domain, the administration domain is the administrative boundary for an enterprise integration project. - When administration Server goes down, all process engines and adapters continue to run. - Administration Domain Components - TIBCO Administration Server - Components. Component software includes TIBCO ActiveMatrix BusinessWokrs engine and adapters - Machines. Each administration domain contains one or more machines. One machine can be added to an administration domain when a TIBCO ActiveMatrix BusinessWorks component or adapter is installed. All machines within an administration domain are expected to be in the same network subnet. However, TIBCO Rendezvous rvrd can be set up and can then use TIBCO ActiveMatrix BusinessWorks across subnets. - User and access information. User and authorization information is specified with the TIBCO Administrator GUI and stored in the domain data store. - Projects. A project that is created with TIBCO Designer GUI, then created an EAR file and sent to the machine where the TIBCO Administration Server resides. The EAR file can be deployed and it becomes visible in the TIBCO Administrator GUI and its components can be starte, stopped and monitored from there. - The TIBCO Administration Server supports centralized authentication and authorization. Users with full administrative privileges can define which usersshould have access to which part of the system. - Authentication. Verification of identity - Authorization. Permission to view or execute. An administrator gives users

access rights to the functionality of the product they need. - Monitoring activities to perform with TIBCO Administrator over administration domain. - View, add and delete users and assign access privileges to each user - Monitor and manage the machines in the administration domain. - Monitor deployments. This includes viewing component status and throughput and looking at traces, which can also be exported to a file. - Manage deployment. This includes stopping and starting process engines and adapters. - TIBCO ActiveMatrix BusinessWorks Fundamentals - Support for Standards J2EE Compliant. JMS, EJB, JNDI Protocols. Web services (SOAP, WSDL), HTTP, HTTPS Messaging. JMS TIBCO Rendezvous Data Description. Native support for DTD, XSD and TIBCO AS Schema Data Representation and Expressions. Native support for XML, XPath Data Transformation. XSLT A plug-in for B2B interactions - Integrated Development Environment. With TIBCO ActiveMatrix BusinessWorks, the process design, deployment and runtime environment are tightly integrated even though the runtime environment supports a distributed architecture. - Extensibility and Scalability. Scalability to support higher volume of data and extensibility to support additional applications or a larger number of process engines or adapter instances. - Better Resource Utilization and Less Maintenance Overheads - TIBCO Designer contains four panels. - Project Panel - Design Panel - Configuration Panel - Palette Panel - Project. Consists of resources that contain the functionality needed for the integration system including services (producers and consumers) and any business logic that may be applied to that information. - Resources. Components of a project - Palettes. Organize resource into related groups. Which palette is displayed depends on the currently opened resource and on preferences. Palette panel can be displayed separately from the project panel via the Edit > Preferences menu. - Enterprise Archive. The Enterprise Archive resource allows to create an EAR file which can be deployed. It contains shared archives and process archives that you specify. - When project is deployed, each component is individually started from TIBCO Administrator. - After all adapters and process engines have been started, process instances are created by process starters. Process instances are created based on process definitions. - While different process instances are running, any alerts scheduled during deployment configuration are sent to the specified recipient by the TIBCO Administration Server. - TIBCO Administrator allows monitoring of the running project at different levels of detial and can collect tracing information for later analysis. - TIBCO ActiveMatrix BusinessWorks features - Messaging Guaranteed delivery and fault tolerance Distributed architecture High throughput Scalability

Protocols supported are TIBCO Rendesvouz, JMS and HTTP - Adapters. Help making information available to business process by adapting the applications to a common messaging system. Easy configuration with Design-Time adapter Easy inclusion in Business Processes Easy deployment and monitoring TIBCO ActiveMatrix BusinessWorks integrates with the following adapters: Technology adapters. Files or databases Application adapters. PeapleSoft, SAP R/3, Siebel, etc Other adapters can be loaded into TIBCO Designer, but cannot be installed nor monitored with Administrator though. - Business Process Modelling - Schemas and Data Mapping The process data is the list of available data for a specific activity. The input schema defines input values for an activity. Process data can be mapped to input schema using a drag and drop interface. XPath can be used to specify conditional mapping. - Manual Activities TIBCO Designer includes a ManualWork palette with activities for user interaction with business process. - As a rule, analysis, installation and services configuration are performed just once. - Analysis. Define and analyze problem Detailed analysis results in a faster over-all development Start with a business analysis that includes a problem definition stating project goals clearly.

TIBCO BW Concepts
These are some notes I have written in order to help myself to get ready to clear the TIBCO ActiveMatrix BusinessWorks 5 Certification Exam (TB0-123). More details about the exam, click here. This entry is about TIBCO BW Concepts document. Any comment or suggestion, please write toluisagcenteno@gmail.com. Further details can be found at TIBCO

Documentation. I hope these notes can help you as well as they did to me... TIBCO ActiveMatrix BusinessWorks Notes - TIBCO ActiveMatrix is a scalable, extensible and easy to use integration platform that allows development of integration projects. - Integration platform requirements. - Short Development Cycle - Scalability and Extensibility - Ease of use - TIBCO ActiveMatrix BusinessWorks prerrequisites - TIBCO Runtime Agent -TIBCO Designer - TIBCO Administrator - TIBCO ActiveMatrix BusinessWorks engine runs the business process in test mode and at run-time. - TIBCO ActiveMatrix BusinessWorks Service Container hosts multiple application simultaneously. - TIBCO ActiveMatrix BusinessWorks design-time plug-in provides the palettes and resources to TIBCO Designer for creating processes. -TIBCO ActiveMatrix BusinessWorks was designed using a plug-in architecture. -TIBCO Administration domain is a collection of users, machines, and TIBCO ActiveMatrix BusinessWorks components that a TIBCO Administration Server monitors and manages. - There is only one Administration Server for each administration domain. - Although components within an administration domain can communicate with systems outside the domain, the administration domain is the administrative boundary for an enterprise integration project. - When administration Server goes down, all process engines and adapters continue to run. - Administration Domain Components - TIBCO Administration Server - Components. Component software includes TIBCO ActiveMatrix BusinessWokrs engine and adapters - Machines. Each administration domain contains one or more machines. One machine can be added to an administration domain when a TIBCO ActiveMatrix BusinessWorks component or adapter is installed. All machines within an administration domain are expected to be in the same network subnet. However, TIBCO Rendezvous rvrd can be set up and can then use TIBCO ActiveMatrix BusinessWorks across subnets. - User and access information. User and authorization information is specified with the TIBCO Administrator GUI and stored in the domain data store. - Projects. A project that is created with TIBCO Designer GUI, then created an EAR file and sent to the machine where the TIBCO Administration Server resides. The EAR file can be deployed and it becomes visible in the TIBCO Administrator GUI and its components can be starte, stopped and monitored from there. - The TIBCO Administration Server supports centralized authentication and

authorization. Users with full administrative privileges can define which usersshould have access to which part of the system. - Authentication. Verification of identity - Authorization. Permission to view or execute. An administrator gives users access rights to the functionality of the product they need. - Monitoring activities to perform with TIBCO Administrator over administration domain. - View, add and delete users and assign access privileges to each user - Monitor and manage the machines in the administration domain. - Monitor deployments. This includes viewing component status and throughput and looking at traces, which can also be exported to a file. - Manage deployment. This includes stopping and starting process engines and adapters. - TIBCO ActiveMatrix BusinessWorks Fundamentals - Support for Standards J2EE Compliant. JMS, EJB, JNDI Protocols. Web services (SOAP, WSDL), HTTP, HTTPS Messaging. JMS TIBCO Rendezvous Data Description. Native support for DTD, XSD and TIBCO AS Schema Data Representation and Expressions. Native support for XML, XPath Data Transformation. XSLT A plug-in for B2B interactions - Integrated Development Environment. With TIBCO ActiveMatrix BusinessWorks, the process design, deployment and runtime environment are tightly integrated even though the runtime environment supports a distributed architecture. - Extensibility and Scalability. Scalability to support higher volume of data and extensibility to support additional applications or a larger number of process engines or adapter instances. - Better Resource Utilization and Less Maintenance Overheads - TIBCO Designer contains four panels. - Project Panel - Design Panel - Configuration Panel - Palette Panel - Project. Consists of resources that contain the functionality needed for the integration system including services (producers and consumers) and any business logic that may be applied to that information. - Resources. Components of a project - Palettes. Organize resource into related groups. Which palette is displayed depends on the currently opened resource and on preferences. Palette panel can be displayed separately from the project panel via the Edit > Preferences menu. - Enterprise Archive. The Enterprise Archive resource allows to create an EAR file which can be deployed. It contains shared archives and process archives that you specify. - When project is deployed, each component is individually started from TIBCO Administrator. - After all adapters and process engines have been started, process instances

are created by process starters. Process instances are created based on process definitions. - While different process instances are running, any alerts scheduled during deployment configuration are sent to the specified recipient by the TIBCO Administration Server. - TIBCO Administrator allows monitoring of the running project at different levels of detial and can collect tracing information for later analysis. - TIBCO ActiveMatrix BusinessWorks features - Messaging Guaranteed delivery and fault tolerance Distributed architecture High throughput Scalability Protocols supported are TIBCO Rendesvouz, JMS and HTTP - Adapters. Help making information available to business process by adapting the applications to a common messaging system. Easy configuration with Design-Time adapter Easy inclusion in Business Processes Easy deployment and monitoring TIBCO ActiveMatrix BusinessWorks integrates with the following adapters: Technology adapters. Files or databases Application adapters. PeapleSoft, SAP R/3, Siebel, etc Other adapters can be loaded into TIBCO Designer, but cannot be installed nor monitored with Administrator though. - Business Process Modelling - Schemas and Data Mapping The process data is the list of available data for a specific activity. The input schema defines input values for an activity. Process data can be mapped to input schema using a drag and drop interface. XPath can be used to specify conditional mapping. - Manual Activities TIBCO Designer includes a ManualWork palette with activities for user interaction with business process. - As a rule, analysis, installation and services configuration are performed just once. - Analysis. Define and analyze problem Detailed analysis results in a faster over-all development Start with a business analysis that includes a problem definition stating project goals clearly. Analysis should include expansion posibilities Ask these questions. What services will the process access? What are the transports being used? - Domain Setup and Installation. Install software and configure domain TIBCO Administration Domain is the set of software and hardware resources used by integration project. When installing a TIBCO ActiveMatrixBusinessWorks component administration

domain to which a machine belongs should be specified. Ask these questions. For development environments, Do I need to share work with other developers? What machines do I need to run my project? Which components should run on which machine? Where should I run TIBCO Administration Server? Who are the users that need to make changes to the project? Who are the users that need to view information about the running project? How will the project handle load balancing and fail-over? Installing components. 1. Install TIBCO Runtime Agent (TRA) on each machin in the domain 2. Install the Administration Server and specify the administration domain name/user/pwd. 3. Install other TIBCO ActiveMatrix BusinessWorks process engines into the administration domain. 4. Install adapters ubto the administration domain. - Services Configuration. Configure adapters TIBCO ActiveMatrix BusinessWorks uses different types of services that can be accessed from within the process - Adapter Services. Adapter Services are configured using TIBCO Designer and the Design-Time Adapter (DTA). A DTA allows to access the metadata provided by the adapter at design time. Each type of adapter has its own DTA. Only one DTA needs to run in a network, even if several users access different adapter instances of that adapter type. - Adapter Publisher Service. Sends data from source app to business process - Adapter Subscriber Service. Receives data in source app from business process - Adapter Client Service. Acts as a client in a request-response interaction. - Adapter Server Service. Acts as a server in a request-response interaction. - Web Services. Web Services can be configured from TIBCO ActiveMatrix or externally and accessed using SOAP Request-Reply activity. TIBCO ActiveMatrix BusinessWorks can function as a server and a client in a web services interaction. - Process Design. Implement and test business processes - Each process has a starting and ending point. - Activities are added to the process. - Conditional flow support. - Activities can be grouped for looping, transactional behavior, etc. - Most processes have one main process - Deployment configuration and Deployment. Deploy to runtime engine - During installation, all components are installed into the same administration domain. - An EAR file is created. It includes adapter configurations and process definitions to deploy. - A deployment configuration allows to assign processes and adapter services to different process engines and adapters installed on the machines in the administration domain. - Project is deployed when deployment configuration is complete.

- The project data store (repository) and the TIBCO Administration Server are updated with the new deployed components. - Production. Manage and monitor deployments Authorized users can monitor the administration domain using the TIBCO Administrator GUI. - User Management - Domain Monitoring - Deployment Monitoring and Management. - All the processes are isolated and independent of each other in a TIBCO ActiveMatrix BusinessWorks service container. TIBCO ActiveMatrix BusinessWorks Development Methodology. - Analysis 1. Define and delimit the problem. 2. Identify processes. 3. Identify components. Shared Resources Services and corresponding activities ManualWork Activities Transitions and conditions Mapping Exceptions 4. Describe Business Events and Objects. - Know the required data format at each place in the process - Know the required data content - Understand appropriate actions to take. 5. Design Business Processes. 6. Consider Domain Setup - Domain Setup Administration Servers main responsibilities. - Enforce Security for the domain (authentication and authorization) - Manage registration (Add deployed projects and machines to a domain) - Send appropriate information to each machines TRA when a project is deployed and pickup alerts sent by those TRAs. - Start and stop process engines and adapters. - Manage entries or adapters running in fault-tolerant mode if fault-tolerant setup has been performed. TIBCO Runtime Agent main responsibilities - Supplies an agent that is running in background on each machine Responsible of starting and stopping processes running on a machine The agent monitors the machine. That information is then visible in TIBCO Administrator - Supplies the run-time environment (shared libraries including third party) - Services Configuration - Service Characteristics Service Interface (WSDL/SOAP or AE Services) Transport (HTTP,JMS,TIBCO RV) Data Syntax (XML or ActiveEnterprise message format) Data Schema (DTD or XSD schema)

- Service invocation ways One way operation (do not wait for response) Request-response operation (waits for one response, point to point messages) Publication (notification). Sends information on as-needed basis, potentially multiple times Subscription (process incoming information on as-needed basis, potentially multiple times) - Publication and subscription are driven by events, usually the arrival or creation of data. Communication is in one direction (publisher to subscribers). - Service types Web Services (accessed by SOAP activities) TIBCO ActiveMatrix BusinessWorks supports WSDL TIBCO ActiveMatrix BusinessWorks can be create Web Service Server and clients Adapter Services (accessed by ActiveEnterprise Adapter activities) Technology adapters. Publication to or subscription from files and databases Enterprise application adapters. Siebel, SAP R/3, PeopleSoft, etc - Configuring Services 1. Installing the adapter TIBCO ActiveMatrix BusinessWorks, TIBCO Administration Server should be installed and Administration Domain should already be set up (administrative user/pwd is a must). After installation, a new palette for the adapter becomes available from TIBCO Designer. 2. Setting up the Design-Time Adapter Drag and drop an Adapter Configuration resource from Adapter palette to Design Panel, specify connection information. Click on the resource on the project tree panel and then select its Adapter Services folder to open it. Drag an Adapter Service from the Services palette into Design Panel. From a command prompt, start the design-time adapter and then specify the data the adapter should publish or subscribe to interactively. 3. Configuring the Run-Time Adapter Specify runtime connection information using the Runtime Connection tab. Define adapter services and choose schema from the pop-up list provided via the design-time adapter. Specify tracing information if desired. If adapter uses advanced features such as Advisories, they can be configured in Advanced folder. 4. Accessing the Adapter Service from the Process Activities that access the services. Publish to Adapter. Process => Adapter => Application. Adapter Subscriber. Process <= Adapter Invoke an Adapter Request-Response Service. Process=>Adapter;Process<=Adapter Adapter Request-Response Server Process<=Adapter;Process=>Adapter

Respond to Adapter Request (based on a previous request from adapter) Process=>Adapter Wait for Adapter Message Process<=Adapter Wait for Adapter Request Process<=Adapter - Business Process Design 1. Define Shared Resources 2. Create Process Definitions 3. Add a Process Starter Start activity is not a process starter 4. Add Activities 5. Optionally, Add Manuall Work Activities - Shared Resource - Workflow schema. Associated with a ManualWork task. This is the data that a user needs to complete the task. It supports string, int, date and document data types. - Workflow connection. Connection to TIBCO InConcert workflow server (tracks and manages tasks). - Manual Work Activities - Assign Work. Creates a new task with associated data and assigns it to the specified pool of users. - Download Document - Get Work Status. Retrieves the status of a task that was previously created with Assign Work activity. - Modify Work. Change status of existing task created with Assign Work activity. Update. Modifies the data associated with an uncompleted task Complete Reassign. Reassigns the task to a pool of users - Wait for Completion. Waits for the completion of the task for the specified period 6.Create transitions between activities Cannot create a transition to a previously executed activity. 7. Perform mapping and transformation for each activity 8. Optionally, Group Activities as needed. - Create a set of activities with only one condition for the group (Used for error transitions) - Create a set of activities to be repeated (For-Each, until a condition is true or if an error occurs) - Create a set of activities that participate in a transaction. 9. Test the process. - Entering the testing environment starts a TIBCO ActiveMatrix BusinessWorks engine. The engine starts process instances based on process definitions. - Deployment The TIBCO Administration Server sends all necessary information to the individual machines. Then, all components become visible in TIBCO Administrator GUI.

Every time project is changed, a new EAR file should be created for deployment. Then, desired deployment should be stopped and restarted for the changes to take effect. If more services or processes are going to be added to an already deployed and running TIBCO ActiveMatrix BusinessWorks service container, stop only the selected application, unload the EAR file and load the modified in the same service container. - Production -TIBCO Administrator consists of TIBCO Administration Server and TIBCO Administrator GUI. -TIBCO Administrator includes an application server component for HTTP communications and a repository server component for data store management. All three componend run as a single process. -TIBCO Administration Server and TIBCO Administrator GUI together support deployed TIBCO ActiveMatrix BusinessWorks products at runtime. -TIBCO Administration Server interacts with each machine in the Administration Domain by way of TIBCO Runtime Agent running on that machine. -TIBCO Administration Server and TIBCO Runtime Agent communication -The Administration Server receives information about CPU and memory usage, alerts and the process instances and components running on each machine and makes them available via the TIBCO Administrator GUI. -TIBCO Administrator GUI allows users to start and shut-down components. Start and shutdown commands are sent from Administration Server to the appropriate TRA which in turn starts or stops the process. - Monitoring and Management options At runtime, TIBCO Administrator allows to remotely access all deployments in administration domain. Depending on security privileges, the following activities can be performed. - User Management. Add users and passwords to the administration domain for authentication, then give each user view or execute privileges for TIBCO Administrator GUI elements or project repositories (data stores) - Domain Monitoring and Management. View the status of machines and components running on machines in the domain. Start an stop components as needed. - Deployment Monitoring. Monitor the status of each deployment component and process instance and the status of the machines executing them. View trace files and throughput. - Deployment Management. View all running components and stop and restart them as needed