Steps to configure Fault Tolerance mode in TIbco Admin GUI

1. Create an EAR file using Tibco Designer.
2. Using Application Management, click New Application to Browse and upload the ear file into Tibco administrator GUI.
3. Go to Configuration(Application's) and click on process archive.
4. Click on 'Add to Additional Machines' in General tab to select the machine name. when you add, the FT section (Run Fault Tolerant) will be enabled in FT Group Settings.
5. Specify the weights to the process instance in FT Weight and time intervals in FT Group Settings.
6. Using Monitoring tab, we can add Rulebases and Events if needed.
7. Save and Deploy.
8. In Service Instances, we observe that one instance gets started in active mode and another would be in Standby mode by starting the application

Read more...

Uses of AppManage utility in Scripting Deployment

• The AppManage utility creates an XML based deployment configuration file in which deployment options can be defined.
• The utility also uploads the deployment file and EAR file into a TIBCO Administrator administration domain.
• Create a deployment configuration file based on information in an EAR file, or from an application already configured in the TIBCO Administrator GUI.
• Upload an EAR file to an administration domain without specifying deployment configuration options. After the file is imported, it is ready to be configured with deployment options and deployed using the TIBCO Administrator GUI.
• Upload an EAR file and a deployment configuration file and deploy the application in one operation. Using this method, you can quickly deploy your applications in multiple domains.
• Export all application archives and deployment configuration files within adomain, so they can be batch deleted, started, stopped, undeployed, or deployed in another domain. For TIBCO Rendezvous administration domains, you can change the transport set for application to administration server communication, from rv (Rendezvous) to local, or the reverse.
• Undeploy a deployed application.
• Delete an application from an administration domain.
• Start a service instance of an application.
• Stop a successfully deployed service instance of an application.

Read more...

Controlling Execution of TIBCO BW services

• Process instances typically remain in memory as long as they are executing an activity. If the process instance is waiting for an incoming event (for example, a Wait for Adapter Message activity), the process instance can be paged out to disk and resumed later after the event arrives.
• New process instances are paged out to disk until there is available memory and resources to accommodate them.
• Use TIBCO admin to control execution of TIBCO BW process instances. Useful if system has limited resources & memory or to restrict process instances to run sequentially.

Go to --> Application Mgmt --> Application configuration --> click proccess service -> Advanced Tab

• Max Jobs : Specifies the maximum number of process instances that can concurrently be loaded into memory. Any process instances created once the maximum is reached must be paged out to disk.
• Activation Limit : Specifies that once a process instance is loaded, it must remain in memory until it completes. useful if you wish to specify sequential processing of incoming events, or if you want to enforce limited concurrent execution of process instances.
• Max Jobs (FLow Limit) : Specifies the maximum number of currently running process instance to start before suspending the process starter. Max Jobs (Flow Limit) field limits the number of process instances created by a process starter. This allows you to control the flow of processing so that incoming events are no longer accepted when the limit is reached. This is useful in protocols like TIBCO RVCM, JMS Durables TOpic, JMS Queue, Recceive Mail etc.

Read more...

Main Responsibilities of TIBCO Admin Server

1. Manage Storage for the domain -- Storage can be file based repository or in a database repository.
2. Enforce Security for the domain -- User authentication & authorization
3. Provide Load balancing -- each domain can be configured with one primary & multiple secondary servers. Primary server allows read & write operations while secondary servers only supports read operations.
4. Provide Failure recovery -- When primary server is down, secondary server continue serving.
   

Read more...

Elements of TIBCO Admin domain

1. Administration Server - Manages admin domain.Each administration server manages only one domain. Multiple secondary servers are allowed. Server can be accessed with web browser based TIBCO Administrator.
2. Machines - By default all machines in an admin domain are expected to be in same subnet. However TIBCO RVRD can be used to communicate to the machines on different subnet.
3. User & Acces Information - stored in domain repository. Also syncronize with LDAP server for users & groups
4. Runtime Application - Start, stop & monitor individual process engines & service instances.
5. TIBCO Hawk Agent -- Monitors local resources & conditions. Hawk Agent is an autonomous process & uses collection of locally loaded rules organized into rulebases to apply monitoring logic.

Read more...

Overview of TIBCO Administrator

Functions of TIBCO Administrator:

1. User Management -- creates users & roles, assign them access rights to TIBCO Admin console, application & application repository
2. Resource Management -- manage TIBCO software installed on other machines in domain & monitors machines in domain
3. Application Management -- upload, deploy & monitor applications

TIBCO Administrator Architecture includes:

• Tomcat web server -- manage basic communiaction & makes TIBCO Admin available
• Administrator Server -- Manage domain & application repositories
• User Management
• Resource Management
• Application Management

Read more...