TIBCO ADMINISTRATOR

January, 2010

AgendaOverviewComponentsComponents User Management Resource Management Application Managements

TIBCO Administrator Domain Administration Server TIBCO Hawk Agent and Runtime AgentDeployment Choices

Creating Administrator DomainTIBCO Admin GUIUser ManagementApplication ManagementSample System Architecture using TIBCO Administrator

January, 2010

OverviewTIBCO Administrator is a component of BusinessWorksTIBCO Administrator supports deployment , security administration, monitoring and management of BW processes and machines. TIBCO Administrator includes two components :

TIBCO Administration Server Web browser based TIBCO Administrator GUI.

January, 2010

ComponentsAdministration Server: Manages resources in an administration domain.

TIBCO Administrator GUI: Web browser interface that allows you to configure users and applications, deploy applications, and monitor processes and machines in administration domain. The following modules are provided in the TIBCO Administrator GUI:

User Management Resource Management Application Management

January, 2010

User ManagementManage users, roles and security for an administration domain. Specify users and roles using Users and Roles consoles Specify users and roles access (Read, Write and Administer) to individual components (e.g. folders, Application Management) in a domain using the Security console.

January, 2010

Resource Management 1/2Multiple application domains can be created and applications can be assigned to use them. Get information about installed TIBCO software on each domain machineEnable/ Disable installed softwareAdd custom software's.Add/Delete machines from domain View the status (OK, -\\- ) of each domain machine Specify monitoring options for each machine in the domain. You can specify alert events or TIBCO Hawk rulebases.Customize the machines display. Customize the Installed Software Display

January, 2010

Resource Management 2/2

January, 2010

Application Management Upload an Applications Enterprise Archive (EAR) file. Change value of global variables that were set for the application. Define monitoring rules for each application. Deploy the application and start/ stop it.

January, 2010

TIBCO Administrator DomainCollection of users, machines, and services.Managed by an administration server, which is assisted by a TIBCO Hawk agent running on each machine.Add/Remove machines to/from a domain using TIBCO Domain Utility.

January, 2010

Administration Server 1/2 Manages all resources in the administration domain. Runs on Tomcat web server Each time a domain is created , a new server is created for the domain and named with the domain name. Manages transport options - HTTP and local TIBCO Enterprise Message Service(EMS) : supports only Local Transport TIBCO Rendezvous(RV) : supports both transport options Manages domain data storage TIBCO RV: file-based /database repository TIBCO EMS: database repository Enforces security for the domain : Authentication and authorization of users that require read access or write access to applications.

January, 2010

Load Balancing

Domain can be configured with one primary server and multiple secondary servers using domain utility. Primary server allows read and write operations, while secondary servers only support read operations. Only one primary server can be running for each administration domain. Multiple secondary servers are allowed, but each must be on a different machine than the primary server. Fault Tolerance

Load-balanced administration servers can be used for failure recovery, where secondary administration servers continue serving requests even with the primary administration server down.

Administration Server 2/2

January, 2010

TIBCO Hawk Agent and Runtime AgentTIBCO Hawk Agent being a part of TIBCO Run time Agent package is installed on each machine in an administration domain. TIBCO Hawk Agent is an autonomous process that monitors applications and systems activity. TIBCO Runtime Agent provides the runtime environment required for TIBCO applications. Runtime Agent includes many software tools including TIBCO Domain Utility, TIBCO Designer, TIBCO Rendezvous as well as libraries used by many TIBCO applications.

January, 2010

Deployment Choices 1/3When configuring an administration domain, you can set how the administration server creates and stores application data.

1. Using Local Application Data 2. Using Server-based Application Data

For TIBCO EMS, only local application data choice is available

January, 2010

Deployment Choice 2/3Using Local Application dataDeployment files for an application are sent to target machines. This allows the application to run independently of the administration server.

Benefits Local service instances use no memory, thread or CPU resources on the administration server, the solution is infinitely scalable. No communication between the deployed application and the administration server, a server failure has no effect on the runtime application.

ConcernsSynchronization: if few target machines are unavailable during deployment and later started, their service instances, metadata and configurations can be out of syncSecurity : Repository instances can contain sensitive information such as database or application user ids and passwords, a strong file system security is needed on each machine to protect the data.

January, 2010

Deployment Choice 3/3Using Server Based Application data A repository instance for the application is created on the administration serverNo significant issues related to synchronization

Concerns :

Each repository instance on the administration server consumes memory and threads. With many applications starting simultaneously, the server could become overwhelmed causing time-outs and application failures. Runtime applications can not start, and in some cases can not function without being able to communicate with the administration server. This makes the administration server a single point of failure at runtime.Increased network trafficDifficult in maintaining network and administration security.

January, 2010

Creating Administrator Domain 1/7After installing TIBCO Administrator, the installer starts TIBCO Domain Utility, which is used to create the initial administration domain.TIBCO Domain Utility prompts you to create a master or secondary administration server.

January, 2010

Requires Administration Domain to be given, which will serve as Server(domain name)Creating Administrator Domain 2/7

January, 2010

Requires server portsCreating Administrator Domain 3/7

January, 2010

Provide the User name and password for the domainCreating Administrator Domain 4/7

January, 2010

If domain data storage configuration is selected as database, provide the database detailsCreating Administrator Domain 5/7

January, 2010

Confirmation screen to ensure that the domain details so selected are correctCreating Administrator Domain 6/7

January, 2010

This screen shows that administration domain is successfully createdCreating Administrator Domain 7/7

January, 2010

TIBCO Administrator Login Page : Enter user credentials provided at the time of domain creation.TIBCO Administrator GUI

January, 2010

User Management 1/6

Add a New User

January, 2010

Set permissions for User1/1 1/1

User Management 2/6

January, 2010

Add a new Role

User Management 3/6

January, 2010

Assign a Role to User (continued..) User Management 4/6

January, 2010

User Management 5/6 Assign a Role to User (continued..)

January, 2010

In User - Role Permission, the roles will be enlisted that has been assigned to a user User Management 6/6 Assign a Role to User

January, 2010

Upload an applicationSelect New ApplicationFor creating a new folder select 'New Folder' tabUpload an ear file created form designerSelect 'OK' button Application Management 1/6

January, 2010

Deploy an application Select uploaded Application to be deployed from Application Management Click on 'configuration' Click on 'Deploy' as shown below. Application Management 2/6

January, 2010

undeploy, redeploy and delete an application Application cannot be deleted with out undeploying the EAR file, therefore undeploy ear file and then delete the application undeploy and redeploy EAR files process is done under Application Configuration Application Management 3/6 EAR FilesDeployRedeployUndeployDelete

January, 2010

Monitor deployed applicationSelect the deployed application which you want to monitor Select service instances of the selected application

Application Management 4/6

January, 2010

Update Global Variables (continued)In 'Application Management', select the applicationOnce an application is selected, the screen shows two 'tabs'- General and AdvancedSelect 'Advance' tab

Application Management 5/6

January, 2010

Application Management 6/6 Update Global VariablesOn selecting the 'Advanced tab, screen shows the list of global variables.Change the value of global variables ,if requiredOnce value is changed , click on 'Save' buttonTo reflect the changed value, redeploy the application

January, 2010

Sample System Architecture using TIBCO Administrator

January, 2010

Thank You

*****************************************